Skip to Content
Author's profile photo Vaibhav Kulkarni

Left on Truck – Gain postings in SAP IS-Oil shipment processing

Hi All,

Sharing a very basic case study which is about SAP IS-Oil shipment processing. I will also share on IS-Oil forum.

Business scenario – SAP IS-OIL TD shipment processing

Problem statement – During the fuel delivery to customer (unloading of first delivery), there is some fuel quantity left on truck due to various uncontrollable reasons. The truck goes to another customer (second delivery) with this quantity inside truck. This is “left on truck” qty. During the delivery confirmation step of the second delivery, system was throwing an error due to quantity tolerance exceeding.

Reason – This is because, vendor did not declared the “left on truck” quantity after the first delivery. Hence for second delivery, when the delivered quantity was reported to ERP, the delivered quantity is much more than loaded quantity.

In Standard SAP IS-Oil, for a TD action of “gain/loss”, the gain quantity is termed as “transport loss/gain” and was having considerable tolerance. But, In our case, the quantity gain (during second delivery confirmation) was not a “transport” gain, it was quantity gain due to quantity left on truck from previous trip. Our client wanted the gain to be reported as “left on truck” gain and not transport gain. Hence had to resolve using new non-standard solution.

Solution – For TD action ‘8’ (gain/loss), new reason code was created for left on truck gain when quantity is not declared during load confirmation. when second delivery is posted, this new reason code is used to post the gain.

Assigned tags

      3 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Jürgen L
      Jürgen L

      This document is lacking details, for knowledge sharing it should have much more content, right now it is the story I would tell a boss who is not interested in any details but wanted to know what issue I solved the day.

      A business scenario is certainly more than just word, read for example here what a scenario has to have: Business Scenarios

      Next phrase: you could at least mention one of your "various uncontrollable reasons"

      you could have named the error message that was issued in SAP instead of just "system was throwing an error due to quantity tolerance exceeding." and show where this setting is made.

      For the reason you just wrote "This is because, vendor did not declared the “left on truck” quantity after the first delivery. " you could have shown how this declaration is done and in which transaction.


      You resolved it then with "...using new non-standard solution."

      Without going into the details  the readers can just stop reading here. You could have explained why SAP standard SAP has nothing to solve this issue and of course much more detail about what you did.

      Then you are saying that the "client wanted the gain to be reported as “left on truck” gain and not transport gain" . I thought it was an error message, now it looks as if it is only a different category in a report. How can this solve the error message? Details and screenshots are required.


      Author's profile photo Vaibhav Kulkarni
      Vaibhav Kulkarni
      Blog Post Author

      Thanks for your input. I will incorporate your suggestions in my next case study sharing.

      Author's profile photo Jürgen L
      Jürgen L

      why only in the next? why not improving this one right away?