on 03-21-2010 3:04 AM
Hi,
I am working on a program which sends SRM PO and Contract data to a non-SAP system, one of the requirements is to send SRM data immediately after PO / Contract's status changed to Ordered / Released ( workflow is used here ).
I tried to used BBP_DOC_CHANGE_BADI, but noticed throuhg debugger that the last time this BADI get called, I still didn't see Ordered / Released status in the Status table.
Is any way to know status change for PO / Contract ?
Thanks a lot,
Wayne Liu
Wayne,
If its a standard workflow then schedule the job RSPPFPROCESS (with BBP_CTR) and check the tasks for exact emails that are required.
Let me know if you have futher questions..
Regards
Rakesh Palle
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, Guy,
Thanks a lot for help, I am going to try your suggestions, and will update with my findings.
Also , I want correct my post that the BADI I used is CHECK BADI, not the CHANGE BADI. so I will try to implement CHANGE BADI, to see how it behave in my scenario.
Edited by: Wayne Liu on Mar 24, 2010 1:11 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Try your data transfer logic in BBP_DOC_SAVE_BADI and make it a function call in update task. This way should ensure that your logic is invoked later than the status change by workflow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Wayne,
Solution 1:
You can use the SRM Alert Mangament to know when a contract was released, specifically the following events RELEASED_AGAIN
RELEASED_NEWLY.
Check IMG Cross-Application Basic Settings-> Event and Event Schema for Alert Management
For PO I could not find a similar event, but there is a APPROVAL_PROCESS_DOC_APPROVED event which can be used if the PO was approved after ordering.
In any case you can create your own events and event handlers using the SRM Alert Management BAdi BBP_ALERTING.
Solution 2: Only for Contracts
You can use the existing Distribution mechanism to distribute contracts to Non-SAP systems.
Distribution of contracts is triggered whenever significant changes are done to the Contract (like Release, Lock, Unlock).
Implement function module NOR3_CTR_TRANSFER for this purpose.
Edited by: Sushil Kumar on Mar 22, 2010 9:41 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.