Enterprise Resource Planning Blogs by Members
Gain new perspectives and knowledge about enterprise resource planning in blog posts from community members. Share your own comments and ERP insights today!
Showing results for 
Search instead for 
Did you mean: 
Former Member

In this blog, I am sharing my experience in one of my project. This is relating to functionality of EHP5, LOG_MM_SIT.

Business Process


     The standard process in regular Sales process in Order, Delivery, PGI & Billing. In standard cases,  during the Post Goods Issue (PGI), the accounting entries would be Debiting the Cost of Goods Sold (COGS) and crediting the inventory. Sometimes, client may have the requirement to recognize the COGS not during the time of PGI, but once the material reaches the customer. In that case, during the time of PGI, Inventory will be credited by debiting stock in transit or an alternate G/L account and COGS will be debited at the time of Proof of Delivery (PoD).

Customer Delivery Stock in Transit


     The process is similar to standard process till the time of PGI. In the standard flow, at the time of PGI, the movement type will be 601. In this process, at the time of PGI the movement type is 687 and at the time of PoD the movement type is 601.

After the PGI, the quantity would be reduced from the stock. It can be seen under the plant level as a special stock “Valuated Stock in Transit”. Once the PGI is carried out the stock would be removed from plant.

In our project, we had the requirement to Automate the PoD process based on the requested delivery date.We had used the program to WSPODLIST4 (VLPODQ) in the batch job for the same. When this job was executed in background the ‘Scheduled for Delivery’ column in MMBE was getting updated after PoD was carried which should not have been updated otherwise.

Details of the Error:

In general flow, the ‘Scheduled for Delivery’ stock will be seen once the delivery is created for the order and/or picked till PGI is completed. After that the stock gets reduced once the PGI is created.

Scenario 1: VLPOD / VLPODQ is carried out manually

At first, we will note down the stock levels for the material & carry out the PoD manually.

Material: P-100

Customer: 1000 (1000/10/00 – Sales Area)

Initial Stock for Material P-100, 948 PC - Unrestricted use & 191 PC – Scheduled for Delivery

Sales Order # 19699 was created with Qty 100 PC.

Delivery # 80020265 was created & quantity was picked & delivery was saved.

After PGI was done, the scheduled for delivery stock gets knocked off & stock from unrestricted gets reduced.

After PoD is carried out through VLPODQ, there are no changes in stock.

Scenario 2: VLPOD / VLPODQ is carried out through program WSPODLIST4

As done earlier, we will note down the initial stock & check the stock updates in MMBE throughout the process.

Material: P-100

Customer: 1000 (1000/10/00 – Sales Area)

Initial Stock for Material P-100, 848 PC - Unrestricted use & 191 PC – Scheduled for Delivery

Sales Order 19700 was created with qty 50 PC.

Picking was done & delivery number 80020266 was created.

PGI was carried out for the delivery & unrestricted stock got reduced to 798 PC & Scheduled for Delivery – 191 PC.

After program WSPODLIST4 was executed & POD was done using SE38, the scheduled for delivery stock has got increased to 241PC with unrestricted stock remaining unaffected.


After our analysis, we found that it may be system bug & raised an OSS note to SAP. 


It was then resolved by SAP by releasing an OSS note 1749755.

After the note was applied, the ‘Scheduled for Delivery’ stock was not updated after PoD.




Labels in this area