Purchasing Document Adjustment
Purchasing document adjustment functionality helps to re-price the purchase order, whenever its corresponding valid source condition records gets updated. Valid source includes Info records, Purchasing contracts or other independent condition records. This article will explain key activities related to the new process implementation of purchasing document adjustment.
Sources of Purchasing:
Business normally uses Info records or purchasing contracts to maintain agreed prices with vendors apart from individual condition records based on vendors.
Price update for open purchase orders – Lots of manual activity, Such as extract open PO’s and update price for each purchase orders manually using purchase order change transaction codes
Purchasing Document Adjustment:
SAP has provided a standard transaction code MEI1 to update latest price from Info record or Contract. A set of prerequisite configuration (of course it needs Authorization too) is required to make use of this transaction code. Otherwise user will end up getting the following error
IMG > Materials Management > Purchasing > Conditions > Automatic Document Adjustment > Direct Entry for Creating Worklist > Activation of the Direct Entry for Creating the Worklist
Set Direct entry indicator for the Purchase order document category (01) by using Program “RMEBEMIG” before completing activation of the Direct Entry worklist configuration.
IMG > Materials Management > Purchasing > Conditions > Automatic Document Adjustment > Control Document Adjustment > Control Purchasing Document Adjustment
The priority for the source for the price change:
2.) Info record
IMG > Materials Management > Purchasing > Conditions > Automatic Document Adjustment > Activate Change Pointer for Message Category CONDBI
Process to update Price for Open Purchase order:
Open purchase order is the one which does not have goods receipt posted. Transaction MEI1 will pick the list open purchase orders whenever its corresponding valid info record or contract price gets changed.
The following activities needs to be completed before executing MEI1.
Set “Doc. Index active”
Select “Price date Category” (Mandatory, other than PO creation date)
MEI3 – Recompilation of document index
With this, entries for the open purchase orders will be updated to the index table.
Two Step Control Process:
With this process, first worklist will be created for the price change before processing the transaction MEI1. Note, Direct entry indicator for the Purchase order document category (01) needs to be deactivated by using Program “RMEBEMIG”.
This article explained configuration settings and process steps required to process open purchase orders for price update from Contract/Info record. In case of any queries and clarifications requesting the aspirant consultants to contact the author without any hesitation.
Mohamed Hasan Rifaie M, a Lead consultant at Larsen & Toubro Infotech Ltd (LTI) with overall 18 years experience, out of which around 12 years in SAP P2P, WM, SCM, SRM, Ariba Integration and exposure in to Utilities, Media, Food/Chemical, Pharma industries. He has business experience in Manufacturing, Electro-mechanical and Process industries as a Procurement Executive.
Thank you for this document that give all keys to activate and use this functionality.
I have one question that you may have some clue.
Using the direct approach, no entry is created in the worklist (table WIND) when a modification is done on the supplementary condition, whereas using change pointer the same change create an entry (after the launch of MEI4). Is it normal to not have the same behavior?
Thank you so much. Nice Blog
Can you please post any test case for this?
Can we get this to work with STO's?
Dear Mohamed, dear all
I have configured the system for Direct Creation of Worklist Entries - table WIND.
I think everything is set properly and for purchase orders it works fine.
LFM1-BLIND - set
T6I2-BLTYP=01 Purchase order/Scheduling agreement, WIND_DIR=X, WIND_MIG=X
T6I1 set as follow:
But if a new scheduling agreement is created no entry in the Table S111 is created. The new entries are created for purchase orders only.
Does anyone have a similar experience?
Thank you in advance
Same experience. Does somebody still have an idea?
01 A M 10 PB00 016 2
01 A M 20 PB00 017 2
01 A M 30 PB00 018 2
01 A M 40 PB00 068 2
thanks. It works for me only one record (1st) to update the amended price in the PO. 2nd record onwards not updating.
user xxx already processing contract 46**
Any workaround to update all the POs at one shot
now it works -direct data base changes per purchasing (sync update)-enable option