Skip to Content

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.

Customer Delivery - Stock in Transit.JPG

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

Initial stock.JPG

Sales Order # 19699 was created with Qty 100 PC.

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

After Delivery - S1.JPG

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

After PoD - S1.JPG

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 PGI - S2.JPG

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 POD - S2.JPG


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.


To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Jyoti Prakash

    Nice document.

    I liked the way you described your business process & the issue associated to it. And subsequently the solution.

    Well, you can still improve on representation of the document. Like, instead of adding hyperlinks, instead of putting full link in the doc.

    Also, please make change in first line:

    In this blog, document

    Best wishes for your future contribution.

    Cheers, JP

  2. ' MoazzaM '

    Dear Umesh

    You really deserve 5 start rating and one like for this document. How we can use stock in transit in sales order process is interesting. Automatic POD and its impacts are also something new for me but I liked stock in transit in delivery process. It will be very helpful for a lot of users. Thank you for sharing and keep up the good work.


  3. Suman Sardar


    Such a nice feature to know from the medium of your document.Your presentation is also nice.

    Thanks for sharing this valuable info.Really appreciate your contribution.

    Waiting for your next doc “ functionality LOG_MM_SIT” 🙂

      1. Umesh Ghanekar Post author

        Hi Karthick,

             Addressing PoD difference is standard process. If there is difference in PoD from customer, based on the input, we can enter underdelivery / overdelivery in VLPOD with reason.




    Hi Umesh Ghanekar

    In our project, the client recognize the COGS at the time the material reaches the customer. We plan to use LOG_MM_SIT.

    But there’s a problem I don’t know how to solve it. The customer don’t comfirm the delivery at one time. For example, the Sales Order raised 100 qty and Delivery made 100 qty. The first month, the customer comfirm 40 qty and we billed 40 qty, and then the next month, the customer comfirm the rest 60 qty and we billed 60 qty. As the customer confirm the stock in transit irregularly, so I need to POD one delivery more than once.

    Could you help me or is there some other way to solve the problem.


Leave a Reply