We have a process where the requisition is automatically closed when the PO is created. However, we have a few situations where the PO quantity will not match the requisition quantity leaving an open quantity. It could be that the requisition was created incorrectly (or the PO was created a different way for the same item) and there is really nothing open anymore. Is there a quick way to remove the commitment on the open quantity without actually going in and changing the requisition? Checking the closed box will not remove the commitment. We don't have many scenarios like this but I would like to find out if there is something that can be done automatically. The process I'm taking right now is to go into the requisition, delete the line, undelete the line, and save. This removes the commitment and leaves the history on the requisition alone.
Request clarification before answering.
I have looked at all the notes and believe the system is behaving as it should. Since the PO quantity does not match the PR quantity, there remains an open quantity on the req regardless of closing the req. I don't think we have too many situations like this so my only solution is to go into each requisition, delete the line, undelete the line, and save. That seems to remove the commitment without changing the actual requisition.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The commitment values are saved in the database table COOI. For purchasing orders, the commitments can be value based or quantity base handled, based on the unit of measure used on the PO.
For positions that are using quantity-based commitments, the commitments will be reduced based on the quantity from the goods receipt/invoice and not in the value.
In customizing, the unit of measure can be checked via transaction CUNI [since 40A], or in the field T006-KZWOB (set means value related).
(Customizing -> General settings -> Check unit of measurement).
For purchasing requisitions, the commitments reduction can only be valued based for service items. For non-service items, the purchasing requisitions commitments reductions is always quantity based (note 355793).
But in order to reduce the balance commitment, I would recommend you to create a background program that will collect the purchase requisitions that have valid PO created and put a close indicator. I would recommend to set up a time frame so that program take very old PRs into considerations and even newly created PRs.
You can also explore use of ML91 to activate commitments for services at services line items.
Also Refer some additional notes below:-
355793 - Note:qty-based reductn of purchase requistn commtmt
639523 - Commitments reduction behavior for Purchasing
534993 - Short instructions RKANBU01
152571 - Composite Note: Missing or Incorrect Commitments- CO side
670489 - Commitments for delivery costs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you are not adopting the full quantity, then PR balance commitments will still stay, also which ever have the higher value in the commitment that document commitments will stay.e.g. if PR is have higher value then PO, then PR commitment will stays even close indicator is checked.
I am asking you to create a new background program for the PRs that are still open due partial quantity adoption in PO.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Monique,
Sorry - I read it too fast.
In SAP help, it states that requisition commitments are always reduced on a quantity basis when you create a PO, implying (to me), that automatic zeroing isn't possible in standard SAP: http://help.sap.com/saphelp_erp60_sp/helpdata/en/44/0bf6b7ec732d2fe10000000a11466f/content.htm.
I'd suggest looking into an enhancement to reset the commitment in these cases. Maybe someone else has advice on doing something with standard SAP.
- Jeff
| User | Count |
|---|---|
| 14 | |
| 13 | |
| 7 | |
| 6 | |
| 5 | |
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.