on 2013 Feb 21 11:24 AM
Hello all,
I'm in SRM 7.0 extended classic scenario. PRs are create on ECC and sent to SRM by PI message (Interface PurchaseRequestERPSourcingConfirmation_In).
The problem is:
PR is created with material item and sent to SRM; in SRM Shopping cart is created with material item.
User modifies PR in ECC: material item is changed to service item. PR is approved and sent again to SRM system. In SRM, these changes are not correctly updated:error 'Functional item not allowed below functional item’ is displayed on transaction /SAPPO/PPO2 - Edit Postprocessing Order.
As consequence, the item of SC is updated but not completly; when user try to create Purchase order by using the SC, backend error is displayed (Please maintain services or limits) for the item belonging from PR.
May you kindly suggest a Sap note in order to avoid this situation? I searched but i didn't find it.
Thanks
regards
Daniela
Request clarification before answering.
Hi Daniel,
I hope its not available in standard.
1. You have to do validation during creation of PO from ECC PR in SOCO. So that it will check whether the PR is in released status or not . Please check with ABAP consultant for respective enhancement point/Badi .
2. Appropriate configuration has to be done in PI , so that it will send the updated ECC PR back to SRM as a change version. Please check with PI consultant.
Regards
Ashok
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ashok,
thanks for your replay.
Yes, it's available on standard.
The PR release status is checked when Buyer create PO, the PR is released: this is not the point.
Problem is that changes are not correctly updated on SRM when item type is modified from material item to service item. As ECC allows user to do it ( standard behavior), i thinks that Note exist in order to have SC correctly updated.
Regards
Daniela
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.