on 03-05-2015 11:19 PM
What are the proper validation settings to prevent a Replenishment Order (created using Min/Max monitor) from exceeding the remaining amount on a contract? I have activated RO_CONTRACT_ASSIGN, so it finds the contract. However, it will allow replenishment orders and ASNs exceeding the contract quantity. Is there a setting I can use so that it will respect the contract limits?
Hi Scott,
There is no standard SAP validation check to check contract amount while creating RO in SNC.
Regards,
Nikhil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nikhil,
Thanks for your quick response.
Is there a best practice for respecting contract limits in SMI (specifically in min/max monitor)? Is there any way to prevent a supplier from exceeding contract limits, or will SNC allow suppliers to create RO/ASN/Invoice for unlimited amounts of a material, as long as a valid contract exists?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Scott,
To avoid this scenario, you need to have some kind of development.
option 1) create workflow in ECC to capture RO for the contract which is exceeding contract limit.
and automatically send RO rejection to SNC (custom mapping from ECC --- ORDRSP.ORDERS05-->PI---ROC_In----> SNC).
In SNC create custom alert to notify the supplier.
Option 2) Enhance the CIF transfer for contract in ECC and send contract limit information to SNC.(In SNC you need extend /SAPAPO/TPSRC table to stored these data)
Now you have contract limit value in SNC.
Create Z-validation in SNC. say ZRO_CON_Limit
Go to Tocde:SPRO
Supply Network Collaboration >> Basic Settings >> Validation >> Own Settings >> Maintain Setings in Validation Profiles
Val.prf=P0S1
Validation check=ZRO_CONT_LIMIT
Check status=Active
Val.prf=P0S2
Validation check=ZRO_CONT_LIMIT
Check status=Active
Val.prf=TLB6
Validation check=ZRO_CONT_LIMIT
Check status=Active
and implement the Badi /SCMB/BOL_VALFRMWRK with logic to stop creation RO exceeding contract limit.
Regards,
Nikhil
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.