on 11-06-2008 10:14 AM
Hi,
I am facing a problem with requirements appearing in sourcing cockpit.
I have created a PO from sourcing cockpit for a requirement. However, the requirement still appears in the sourcing cockpit but it should've been removed.
This seems to be an inconsistent behaviour as it does not happen for all requirements. Infact, it works fine when I create another PO for the requirement which reappeared in the sourcing cockpit.
Could someone please give me any suggestion or clue on this?
Thanks & Regards
Saravanan.
we had similar issue.
but in out case all the SC items for which sourcing is carried out & PO created
used to reappear in SOCO sourcing cockpit.
The reason is standard BBP_GET_STATUS_2 again flags the SOURCE_REL_IND
and the SC item starts appearing in cockpit.
we modified std programme to ZBBP_GET_STATUS_2
then it was fine.
BR
Dinesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@ Muthu
Shouldn't the sourcing indicator be set for the item to appear in the sourcing cockpit? I am debugging the report to see what happens there but could you please clarify the indicator usage?
@ Akash
The PO is available in the system. Though I am not sure what steps they had followed to create the PO. It had been created by our client and I need to get that information from them. I searched for POs with the SC reference and the first PO was listed.
@ Dinesh
Could you please share what the problem in BBP_GET_STATUS_2 was and what you had changed in it? It would be very helpful. I am struggling with the test data as the problem doesn't happen consistently all the time.
Thanks & Regards
Saravanan.
Hi
What is your Technical deployement mode ?
check BBP_GET_STATUS_2 job running fine?
reagrds
Muthu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@ Pradeep,
The SOURCE_REL_IND in table BBP_PDIGP is set. This means that the item requirement is relevant for sourcing and would be done from SOCO. Am I correct?
If that is the case, is it relevant to remove the requirement from SOCO once a PO has been created? I am creating a local PO.
@ Muthu,
This is an extended classic scenario. The PO created is a local PO. Would BBP_GET_STATUS_2 help? Currently, this problem does not happen for every requirement. It is happening sporadically. Would there be any data based condition which would make it do or is it because the BBP_GET_STATUS_2 report hasn't run properly?
Many Thanks
Saravanan.
Hi Sarvanan,
Check the value of sourcing relevent indicator SOURCE_REL_IND in table BBP_PDIGP.
Also see the following notes:
940495 Requirements not removed from the sourcing cockpit
933742 Requirement not removed from SOCO when a contract is created
1001882 BID: Requirement reappears in sourcing cockpit
Also go through this link:
Thanks,
Pradeep
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.