on 06-18-2012 9:50 AM
Hi,
In the standard PO Collaboration scenario (SNC 7.02), when the supplier confirms the PO with no change, it is still triggering both ROC_Out and RON_Out. My Ron_Out which comes into ECC as PORDCH is failing in ECC with a variety of messages - that are not accurate. However if the supplier makes a change while confirming - and the customer approves it - both ROC_Out and RON_Out triggered are successfully processed in ECC. ROC_Out is successful in both scenarios.
Why this difference?
No Change RON_Out --> Fails in ECC
Change & Approval RON_OUt --> Successful in ECC.
Can anybody shed any light on this. OR alternatively tell me how I can switch off RON_Out if there is no change in the supplier confirmation.
Thanks!
Nandita
Additional Information: If I collect the PORDCH idocs when they come into ECC and process them via bd87 or even reprocess the failed idocs via bd84 - they are successful. They only seem to fail when they are processed automatically. Buth the RFC user and my ID have SAP_ALL and SAP_NEW access
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Not sure why only the PORDCH Idoc (generated when no chnages are made) fails when processed automatically but gets posted manually. Try assigning ur id to the (PI - ECC) RFC connection and test it.
You can prevent the geenration of RON_Out when changes are not made by implementing the SAP Note # 1336077. The Note adds the Validation Check - PO_PUBLISH_CHANGED_ITEMS_RON. This check when active (for Profile POC3), only those purchase order items whose schedule lines have changed will be transferred using ReplenishmentOrderNotification messages.
Regards,
Bharath
User | Count |
---|---|
8 | |
4 | |
3 | |
2 | |
2 | |
1 | |
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.