Professional Documents
Culture Documents
Customer Delivery - Stock in Transit (EHP5 - LOG - MM - SIT Functionality)
Customer Delivery - Stock in Transit (EHP5 - LOG - MM - SIT Functionality)
2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
Get Started
Solutions Support Training Community Developer
Partner About
Community / Blogs
Customer Delivery – Stock in
Transit (EHP5 – LOG_MM_SIT
functionality)
November 11, 2013 | 1,708 Views |
Umesh Ghanekar
more by this author
SD (Sales and Distribution)
Sales | cogs | deferrred | deffered revenue | delivery | ehp6 ecc6 | goods issue | ifrs | log
mm sit | mb5sit | pod | proof of delivery | recognition | revenue; | sit | stock in
transit | transit
share
0 share
0 tweet share
0
Follow
Introduction
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 1/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
material values are recorded transparently and can be displayed in the stock
overview, the purchase order history, and the individual stock accounts. The
functions are also available for the corresponding intracompanycode and
crosscompanycode return stock transfers.
This document covers the customer delivery with transfer of title at
customer location. The customer deliveries with valuated stock in transit, is
used to pin point the exact time of the transfer of title. The transfer of title
depends on the delivery type. The system determines this based on the
sales document type. The system finds the item categories and thereby the
corresponding schedule line categories, using Customizing for item category
determination in the delivery. The process is controlled by the movement
types that are assigned to the respective schedule line categories.
Client Requirement
The requirement for our project was to recognize the COGS & Sales
revenue at the same time based on the Incoterms. Incoterms were divided
into two categories as ‘Immediate Risk transfer’ & ‘Delayed risk transfer’.
ICC Incoterms like EXW & FCA were classified as immediate risk transfer
as the risk transfer lies with ‘Buyer’ once the Goods are loaded onto carrier
from plant. The other incoterms like FOB, CPT, CIF, etc.. were classified
are Incoterms with Delayed Risk Transfer.
Based on the Delayed Risk Transfer Incoterms, the item category in the
sales order would get determined. This was one of the key developments of
the project. Based on the item category the posting to COGS / SiT account
would happen at the time of PGI.
The Requested delivery date would be maintained by the Customer
Service Representative while processing the Sales Order. Based on the
RDD & route information in the sales order, the PoD is carried out through a
program scheduled automatically.
Features of Business Function LOG_MM_SIT
Business Function LOG_MM_SIT covers below business processes. In
the following processes, valuated stock in transit specifies the exact time of
the transfer of title.
Intra Company Code Stock Transfer: Transfer of title at goods
issue / goods receipt / during transit.
Cross Company Code Stock Transfer: Transfer of title at goods
issue / goods receipt / during transit.
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 2/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
Delivery with transfer of title at the customer location.
PreRequisites
A. SD Customizing requirments:
i. Defining new Sales Order Type
IMG Menu path: IMG –> Sales and Distribution –> Sales –> Sales
Documents –> Sales Document Header –> Define Sales Document Types
Create the new sales document type Delivery from Issuing Valuated
Stock in Transit (ORNC) as a copy of the sales document type Standard
Order (TA/OR).
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 3/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
ii. Defining new Delivery Type
IMG Menu path: IMG –> Logistics Execution –> Shipping –> Deliveries
–> Define Delivery Types
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 4/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
at Customer Location.
iii. Assigning the New Delivery Type to New Sales Order Type
IMG Menu path: IMG –> Sales and Distribution –> Sales –> Sales
Documents –> Sales Document Header –> Define Sales Document Types
In the Shipping section of the detail view, assign the appropriate delivery
type, NCCU to the sales document type Outbound Delivery from
Issuing Valuated Stock in Transit (ORNC).
iv. Defining new Item Categories
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 5/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
IMG Menu path: IMG –> Sales and Distribution –> Sales –> Sales
Documents –> Sales Document item –> Define Item Categories
For this solution, the item category is important configuration. Item
category is assigned to schedule line category which has movement
type. We can define new item categories or use the existing item
categories as per the client’s requirement. But it has to be ensured
that proper schedule line category is determined.
Ensure that the new item category Delivery from Issuing Valuated Stock
in Transit (NCCU) has been created as a copy of the item category
Standard Item (TAN).
v. Defining Item Categories in Deliveries
IMG Menu path: IMG –> Logistics Execution –> Shipping –> Deliveries
–> Define Item Category Determination in Deliveries
When the item category is copied from reference & if made relevant for
copy control i.e., “Is this entry also relevant for copying control?” – If
yes, then the delivery item category will be created, else define
delivery item category manually.
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 6/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
Ensure that for all entries with delivery type Outbound Delivery
(LF), a copy has been created and altered as follows:
Delivery type LF has been changed for each entry to delivery type
Delivery from Issuing Valuated Stock in Transit (NCCU).
Item category Standard Item (TAN) has been changed for each
entry to item category Delivery from Issuing Valuated SiT (NCCU).
vi. Defining Schedule Line categories
IMG Menu path: IMG –> Sales and Distribution –> Sales –> Sales
Documents –> Sales Document item –> Define Item Categories
One of the important configurations of this solution is defining the
Schedule line category. When you define the schedule line category,
you see the changes in the screen with addition of fields MvT
Iss. Val. SiT & Spec. Iss. Val. SiT. Ensure that for the process
Outbound Delivery from Issuing Valuated Stock in Transit the
new schedule line category NU has been created as a copy of
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 7/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
schedule line category Material Requirements Planning (CP),
detailed data:
Movement type = 687 (Goods Delivery to Issuing Valuated Stock in
Transit)
Movement Type for Issuing Valuated Stock in Transit = 601 (Goods
Issue for Delivery)
vii. Assigning New Schedule Line Categories to the New Item
Category
IMG Menu path: IMG –> Sales and Distribution –> Sales –> Sales
Documents –> Schedule Lines –> Define Schedule Line Categories
Ensure that a new entry has been created as a copy of the entry
with item category Standard Item (TAN) and schedule line category
Material Requirements Planning (CP) with the
following changes:
Item category TAN has been changed to item category Delivery
from Issuing Valuated Stock in Transit (NCCU).
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 8/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
Schedule line category CP has been changed to schedule line
category Delivery from Issuing Valuated Stock in Transit (NU).
IMG Menu path: IMG –> Sales and Distribution –> Sales –> Sales
Documents –> Sales Document item –> Assign Item Categories
Normally when the Sales Order type OR is copied & item category
is copied from TAN all the related settings are copied & the
assignment will take place. In case, if the item category is
created newly without any reference, then maintain the assignment to
the Order Type.
ix. Assign PoD relevance to the Delivery Item Category
IMG Menu path: IMG –> Logistics Execution –> Shipping –>
Deliveries –> Proof of Delivery –> Set PODRelevance Depending on
Delivery Item Category
Maintain the PoD relevance for the delivery item categories which
are created.
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 9/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
B. MM & FI Customizing requirments:
i. Create G/L account
The necessary G/L accounts has to be created by FI team for posting of
the Stock in Transit Account.
ii. Define Valuation Class
IMG Menu path: IMG –> Materials Management –> Valuation and
Account assignment –> Account Determination –> Account
determination without wizard –> Define Valuation classes
The valuation class is a group of materials with the same account
determination. If a transaction is to be posted to different accounts
depending on the valuation class. The valuation classes allowed
depend on the material type. Several valuation classes are generally allowed
for one material type. A valuation class can also be allowed for
several material types. The link between the valuation classes and the
material types is set up via the account category reference.
iii. Automatic Postings – BSX & GBB
IMG Menu path: IMG –> Materials Management –> Valuation and
Account assignment –> Account Determination –> Account
determination without wizard –> Configure Automatic Postings
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 10/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
These settings are required for automatic posting of the Stock in
Transit account & the Cost of Goods Sold at the time of PGI & POD
respectively.
C. Master Data requirments:
i. Customer Master
The Customer Master Data has to have the PoD relevance for this
solution. This can be maintained by using Transaction Code XD02 /
VD02. Go to the Sales Area Data, under the shipping tab,
you find the Relevant for PoD checkbox as shown below. Check the
box, to make the customer relevant for PoD.
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 11/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
ii. Material Master
Based on the requirement of the client to identify the stocks & for their
reporting purposes, the valuation class can be maintained against the
VC:Sales Order Stk field as shown below. The maintenance of this
Valuation Class is to account for separate G/L when the Goods issue is
done & the stock is moved to Stock in Transit.
Process Demo
We will create the sales order and delivery to check the process
flow. The following values are used for this:
Sales Area: 1000 / 10 /00
Material: P100; Plant: 1000
Order Type: ORNC
Create the Sales order & save the order.
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 12/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
Before proceeding further, we shall note down the stock of the
material considered in MMBE & MB5SIT.
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 13/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
Detials of MB5SIT before Delivery
Now, create the delibery (VL01N).
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 14/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
Notice that the Post Goods Issue Icon is greyed out in create mode
as compared to our standard process. Do the picking / WH TO & save
the delivery.
Now, go to VL02N & do the Post Goods Issue (PGI)
Check the document flow once the PGI is done.
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 15/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
Check the posting, the finished goods inventory has been credited
& Stock in Transit G/L has been debited.
Now, we will have a look at the stock level MMBE & report MB5SIT
You will see the qty under Iss. SiT column in the MB5SIT report,
against the delivery.
Now, carry out Proof of Delivery (PoD) – Transaction VLPOD
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 16/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
Now, we shall look into the document flow again.
Now, the Stock in Transit G/L has been credited & Cost of Goods
Sold (Inventory change –fin) has been debited.
After PoD check the report MB5SIT
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 17/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
In this way, based on the requirement of the client, the posting to
the COGS & thereby Sales revenue (at the time of billing) can be
controlled using the Proof of Delivery.
References:
www.help.sap.com
Please let me have your feedback on the suggestions &
improvements for this document further, if necessary.
Alert Moderator
68 Comments
You must be Logged on to comment or reply to a post.
Arvind Kottu
November 11, 2013 at 5:52 am
HI Umesh
Good Document
Arvind
Sukant Chakraborthy
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 18/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
November 11, 2013 at 10:42 am
Thanks umesh for sharing the document. New learning of having POD
relevance in CMR.
Thanks
Sukant Chakraborthy.
milk bike
November 26, 2013 at 8:31 am
Thanks a lot Umesh for the fantastic documentation. One question, we are
having EHP5 (SAPKH60506) now but how come I don’t see the same
movement type possibility in Schedule Line Category configuration step?
There is one ‘movement type’ and another one called ‘Movement Type 1
Step’.
==============================
Delivery block
Movement Type 601 GD goods issue:delvy
Movement Type 1Step
Order Type
Item Category
Acct Assgt Cat.
==============================
Anonymous
November 26, 2013 at 9:00 am
Hi The specified item was not found.
Thanks for you comments.
Check if the business function ‘LOG_MM_SIT’ is activated in
the system (Tcode SFW5). Once you activate the business
function, you will be able to see the the difference in screen of
schedule line category as shown below.
Without
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 19/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
Regards,
Umesh
Ju Yang
January 19, 2014 at 12:48 am
Dear Umesh,
Need your help. When I do PGI, I got the error
message:M7226 Update control of movement type
is incorrect (entry 687 X X _ L _ V). I could not
figure it out.
I saw your picture it seems when you do PGI, there
are two entry to BSX. My question is how do you
configure GBB for movement type “687”, do I need
deactive all the account check in 687 movement
type?
Kindly help.
Many thanks
Sayantan Pal
February 17, 2014 at 6:10 am
There are few table please check
Table T156B, view V_156B_VC
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 20/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
Table T156N, view V_156N_VC
Table T156S, view V_156S_VC
Table T156T, view V_156T_VC
Table T156X, view V_156X_VC
Table T157H, view V_157H_VC
Table T158B, view V_158B_VC
Or refer SAP note no 120321.
To tell more how 687 is linked up BSX
and GBB check SAP transaction OMJJ
(account grouping tab) and OBYC.
Umesh Ghanekar Post author
February 17, 2014 at 10:21 am
Hi Ju Yang,
Sorry for delay in reply, hope you
would have resolved the issue. I had
not seen your query.
I didn’t have to do any other
additional entries for what I have
mentioned in my document under “iii.
Automatic Postings – BSX & GBB”. You
dont hv to deactivate any other check.
Regards,
Umesh
Ju Yang
February 25, 2014 at 10:07 am
Dear Umesh,
Thanks very much for
your reply. Finally, got the
solution, it is a program
error. after do the
correction as the note
1610260 – VL02N:
Message M7 226 when
posting goods issue.
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 21/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
The issue is solved. There
is nothing wrong related
movemen type 687.
Umesh Ghanekar Post author
November 26, 2013 at 9:16 am
Hi milk bike,
Thanks for you comments.
Check if the business function ‘LOG_MM_SIT’ is activated in the system
(Tcode SFW5). Once you activate the business function, you will be able to
see the the difference in screen of schedule line category as shown below.
Without
Regards,
Umesh
milk bike
November 26, 2013 at 9:20 am
You are right Umesh – it is deactivated… and
unfortunately I don’t have authorization to activate
it… Thanks for the information anyway!
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 22/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
Finbarr O'Donovan
February 13, 2014 at 9:06 am
Hi Umesh,
This is a good document.
MB5SIT gives you the quantity of stock in transit. Do you know of a report /
transaction that gives both the quantity and value of the stock in transit?
Thanks,
Finbarr
Lynn Guan
February 14, 2014 at 3:38 pm
Dear all,
do do you all have any issue per forming vlpod for
overdeliverry?
thanks Lg
Umesh Ghanekar Post author
February 16, 2014 at 1:08 pm
Hi Lynn Guan,
I have not tested that, are you facing any
specific issue?
Regards,
Umesh
Lynn Yoke Ling Guan
March 5, 2014 at 5:35 pm
The system doesn’t allow me to
perform an overdelivery. Was
wondering if anyone had solved this. If
i perform a normal PGI with mvt 601,
then a PoD, it works fine.
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 23/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
What I saw in the posting is that it
doesn’t have sufficient stock to knock
off as when PGI, the stock are being
posted with stock type T. Appreciate if
someone do have solution.
Thanks
LynnG
Umesh Ghanekar Post author
February 16, 2014 at 1:07 pm
Hello Finbarr O’Donovan,
Thanks.
We had developed a Z report as customer needed some more
fields than available in standard report MB5SIT including value
& other 9 fields in the report.
You can check out reports MBBS, MC.1. As I don’t have
system access now, I don’t remember exactly which report gives
the value.
Regards,
Umesh
Sayantan Pal
February 16, 2014 at 1:29 am
Good document cheers!!!
Umesh Ghanekar Post author
February 16, 2014 at 1:09 pm
Thanks Sayantan Pal
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 24/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
' MoazzaM '
February 25, 2014 at 12:24 pm
Hi Umesh Ghanekar
I have seen this requirement many times here in SCN and some users asked
me this directly. From now onward I will share this document with them and
this would be very helpful for those who are looking for stock in transit
function in SD process.
Thank$
Umesh Ghanekar Post author
February 26, 2014 at 3:15 am
Thanks ‘ MoazzaM ‘. Hope it would be helpful.
Lynn Yoke Ling Guan
March 27, 2014 at 4:14 pm
Dear Zhuo Wei,
Haven’t still trying to fix it. Do share if you figure it out. Else I would need to
stick to the normal PGI stock then vlpod only.
Kumar R
March 27, 2014 at 4:44 pm
Thanks for sharing this document.
Regards, Kumar
RAVILOCHAN KITCHAMSETTY
May 3, 2014 at 1:16 pm
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 25/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
superb documentation……………..Thanks for sharing
Sridhar Vijjhalwar
May 14, 2014 at 4:36 pm
Hi Umesh,
Everything went fine untill at VLPOD where the stock difference was
recorded and billed and invoiced perfectely for the right qty, but the MB5SIT
is showing:
History:
SiT order for 20 case ( 1 case= 6 ea)
Delivery made for 20 cases
VLPOD for 15 caes
Invoiced for 15 case
so what happend to the 5 cases (30 ea), where its gone?
No in MMBE is showing ( without tick mark on ” No zero line”)
How to clear from Issuing Valuated stock, Can you throw some light on it
please?
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 26/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
Kind Regards,
Sridhar.
Peixi jiang
January 6, 2015 at 9:15 am
I have same question as yours, Did you have slove it? Could
you tell me how to clear the “Issuing Valuated stock”?
Kind Regards
Peixi.jiang
Murali Ramagoni
May 20, 2014 at 7:11 pm
Hi Umesh,
Nice Document, Thanks for sharing. My question is we are good upto the
scenario you have explained, our issues starts after the GI is completed, We
need to pay the Vendor (issuing Plant) as soon as the goods have been
Shipped (or the invoice program runs the next day). Once we make the
goods movement the PO with 107 mvmt type the invoice is set to block,
cannot release invoice for payment. we need to pay the vendor before the
Physical receipt is done. Do you have any requirement or came across this
scenario.
I would also like to understand what are the financial postings look like and
can a Invoice be created for intercompany billing in the scenario you
explained before even the goods are received?
Appreciate if you can share some thought on this.
Thanks
Murali
Faizan Yaqoob
May 21, 2014 at 1:07 pm
Hi,
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 27/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
I have activated Business Function LOG_MM_SIT in EHP 7. I have maintained all
settings as defined for this business function. In case of MTS process it executed
smoothly but when we go for MTO scenario system behave differently.
While goods movement from production to inventory against in MTO
scenario system is debited Stock In Transit (SIT) GL rather than Inventory
GL and using same (SIT) GL for credit posting while processing PGI, and
after doing PoD system uses COGS GL for debit and Stock in Transit GL for
credit posting.
As per my understanding at time of goods received from production to
inventory accounting entry should be:
Dr Inventory
Cr Inventory Change
At time of doing PGI accounting entry should be:
Dr Stock In Transit (SIT)
Cr Inventory
And entry at time of Proof of Delivery (PoD) entry should be:
Dr COGS
Cr Stock In Transit (SIT)
The issue is that why system is not debited Inventory GL in case of MTO
scenario after activating business function.
fortian .
July 30, 2014 at 2:45 pm
Thanks Umesh Ghanekar for this great document.
I’m very interested in this process but I’m a bit surprised that this process
starts by choosing the right order type…
Don’t you agree that having stock in transit or not after the goods issue
should depen on the incoterms or the customer (if it’s relevant for POD or
not)? And not in the sales order type (item category)?
Sayantan Pal
August 1, 2014 at 12:55 am
Hi Fortian,
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 28/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
Its true it does not depend on the order type but the controlling
factors is the schedule line ,the movement type you assign and
the POD relevancy in the customer master.
To separate this new process SAP has given with a new Order
type. In my project i did with the existing order type just by
controlling the schedule line. Thus without hampering the
current business flow.
I am not sure how incoterm can help but POD is relevant as it
an indicator if the product has reached customer and a delivery
acceptance receipt taken from him. In between it is considered
as transit.
regards,
Sayantan
fortian .
August 1, 2014 at 7:01 am
Hello Sayantan Pal
You are right, the main controlling factor is the
schedule line. But as there is no way, as far as I
know (and leaving aside userexits), to determine it
according to any customer master data we could
say it’s Sales Order dependent (or material). Well…
it could also be Customer/Material dependent if we
use the “Item Usage ” in the customer inforecord to
determine the item category type.
But I believe once the schedule line type NU has
been determined it doesn’t really matter whether
the customer is POD relevant or not, system will
post the stock in transit anyhow… Am I wrong?
Best regards,
Fortian
Sayantan Pal
August 1, 2014 at 7:35 am
Hi Fortian,
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 29/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
The customer should be POD relevant.
As when you do the PGI in delivery it
will trigger the movement type 687 (not
601 as in most PGI cases). This
makes the stock move in SIT which
gets complte with the 601 as the POD
comes in.
regards,
Sayantan
fortian .
August 1, 2014 at 8:03 am
Correct, if the customer is
not POD relevant the
delivery cannot be
created. Even if the sales
order is flagged as POD!
relevant.
Thanks Sayantan Pal.
fortian .
October 6, 2014 at 11:15 am
Dear Sayantan Pal (and
Umesh Ghanekar),
Do you think it would be a
good idea to determine
the schedule line category
according to the whether
the item is POD relevant
or not? (using a user
exit).
Regards,
Fortian
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 30/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
Sayantan Pal
October 8, 2014 at 9:21 am
hi fortan,
It is not very clear why
you want to use userexit
nither is your requirement.
As a consultant i dont not
prefer to do an
enhancement at the first
go. Rather try to make it
as much standard as
possible. If the solution
can not be achiveable by
the standard then only i
do.
regards,
Sayantan
fortian .
October 8, 2014 at 9:32 am
I also like to avoid user
exits.
But how is the user
supposed to know if this
process (customer – stock
in transit) should be
triggered or not?
Should the user check
every time if the “Proof of
Delivery” field is flagged
or not (or the incoterms)
and then manually switch
the the schedule line
category? In our case this
is not feasible.
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 31/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
Sayantan Pal
October 8, 2014 at 10:13 am
hi,
I agree totally that the
user will not this. The
requirement is first
chalked out and the
applicability for the plants
and the relevant countries
are taken first. Then as
per that you take those
data from the system and
do a MASS upload or do
an LSMW for those
customers marking
relance to POD.
regards,
Sayantan
fortian .
October 8, 2014 at 10:41 am
Sorry, I don’t understand
what you are trying to
explain… The question
was “would be a good
idea to use userexit to
select the schedule line
category according to the
POD field?”
Annis Lee
March 4, 2015 at 2:40 am
Dear Umesh,
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 32/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
Would like to learn from you how could we avoid using userexit
and INCOTERM to determine item category for POD.
Appreciate your sharing on this.
Thanks.
Annis
Marta Redelinghuys
August 6, 2014 at 10:55 am
Thank you for sharing this documentation.
sam paton
August 7, 2014 at 5:13 am
very informative
Peixi jiang
January 6, 2015 at 2:00 am
hi,Sayantan Pal
I have a question about PoD difference.
If Vl02N & PGI qty is 10pc, but VLPOD qty is 9pc, so there will general 1pc
stock which is in Iss.SIT. How to deal with this 1pc stock?
Best Regards
Peixi.jiang
Lynn Yoke Ling Guan
January 8, 2015 at 1:31 am
Dear Peixi,
I created one movement type to clear the SiT stock and the
value of this SiT stock is posted to one dedicated GL account for
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 33/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
differences
Thanks
Regards
Lynnn Guan
Peixi jiang
January 8, 2015 at 2:27 am
I found one bug of the reporter MB5SIT
My test step as follow:
If the quantity of DN is 10pc:
1. After posted DN with VL02N, 10pc unrestricted
stock will move to Issuing.SIT as follow:
2.There is 1pc damaged during transportation, so
customer received 9pc ,and we will confirmed 9pc
in sap with VLPOD, the MB5SIT as follow:
3. For 1pc damaged stock ,I process it with MB1B
411T, then the MB5SIT as follow:
The quantity of Issuing Valuated SIT is cleared,
but the delivered Stock is reduced form “9” to
“8”, why ?
RAHEEM BAKSH
March 17, 2015 at 7:34 am
Dear Umesh Ghanekar,
I appreciated your effort!
Could you share and update the possibility of Billing (invoice ) without POD
confirmation. If it i possible what will be accounting entry here and process of billing after
POD confirmation.
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 34/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
Regards
Raheem
Umesh Ghanekar Post author
March 17, 2015 at 5:25 pm
Hi Raheem,
Thanks.
One of the option is to manage billing with proforma invoice.
This will have no entries in accounting.
Regards,
Umesh
RAHEEM BAKSH
March 18, 2015 at 4:44 am
Hi Umesh,
That is ok but how we can handle “VAT rules and subsequent
liability”.
Umesh Ghanekar Post author
March 19, 2015 at 1:45 am
Sorry, I am not sure.
RAHEEM BAKSH
April 16, 2015 at 4:13 am
Hi Umesh,/ All,
Where we assign Inventory as well as
Stock in Transit GL in BSX as per your
snap shoot, and also Mvt type 601 T,
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 35/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
Sayantan Pal
April 26, 2015 at 2:28 pm
hi Raheem,
Please take help of your
MM team in your project.
OMJJ and the respective
account posting in the
OMS2.
SIT completes as you do
a POD.
regards,
Sayantan
Sam P
March 17, 2015 at 10:09 am
Umesh, You are amazing. Thanks for this article.
Umesh Ghanekar Post author
March 17, 2015 at 5:26 pm
Thanks Sam P
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 36/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
Annis Lee
March 27, 2015 at 3:52 am
Hi Umesh,
Can you share more on how Incoterms is using to identify if the customer is
subject to POD beside the POD indicator in customer master?
Thanks.
Annis
Umesh Ghanekar Post author
March 27, 2015 at 6:25 am
Hello Annis,
We did a development to meet the requirement within an
user exit for item category determination based on the incoterm.
In case of incoterms like EXW, item category not relevant for
POD was used & if like CFR item category relevant for POD was
determined. Since I don’t have access to that system now, I
don’t know exactly which exit was used.
Regards,
Umesh
Annis Lee
April 1, 2015 at 5:50 am
Hi Umesh,
Thank you for sharing your experience.
Annis
Deepthi Kancharthi
March 31, 2015 at 10:04 am
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 37/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
Hi Umesh ,
Thanks for the wonderful document.
While using VLPOD transaction , I want to enter the POD quantity multiple
times. This would enable me to create multiple goods issue documents. With
the current config , am not able to do this. Any inputs will be helpful !
Regards,
Deepthi
Chetan S Pai
March 31, 2015 at 2:46 pm
Hi Umesh,
I have a basic question on one of your statements:
“The requirement for our project was to recognize the COGS & Sales revenue at the
same time based on the Incoterms.”
Is it possible to bill the customer for the partial quantity immediately after
601T and meanwhile continue to process the delivery with approved and
rejected quantity?
regards,
CSP
Vadim Kleonsky
May 22, 2015 at 12:25 pm
Thank you very much, Umesh.
I did this customizing and achieved this result.
But.
There is large problem.
I am about status delivery. After GI (687) the delivery get status C – issue
completed.
For POD designed another status – relevant for POD ‘C”
It’s not correctly for out business processes.
Our processes consider status GI completed for delivery ‘C’ when transfer of
title is completed
Because of this problem all our report would display not correct information.
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 38/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
The good is yet ours (stock in transit), but status GI is ‘C’
what can you say about this problem?
regards
Kleonsky Vadim
Sayantan Pal
May 31, 2015 at 11:22 pm
Hi,
As I understand from your statement’s u r business follow the
standard processes. If u r planning to implement SIT u need to
change ur report else follow the standard processes without SIt.
Sayantan
Vadim Kleonsky
June 1, 2015 at 6:11 am
thanks again, gurus
Another question, help, pls
We used business scenario – delivery without sales order.
But I can’t customizing SIT for our business process – for delivery without sales order.
My question is follows: can I customizing delivery without sales order with SIT
regards
Kleonsky Vadim
Sayantan Pal
June 4, 2015 at 3:21 pm
Hi Vadim,
Technically specking ,yes you can do it. There are a couple of
customisation you need to do to achive this.
In standard, delivery without sales order is LO. When you open
up the delivery document type you will find the reference sales
order DL. You copy DL and create custome sales order say ZDL
and you put the confiruration of schedule line for SIT.
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 39/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
I hope you will be able to do this with the given set of
information.
Now can you please let me know what is the business
requirement ? Why do you wnat to impliment this in delivery
without sales order scenario.
regards,
Sayantan
Vadim Kleonsky
June 5, 2015 at 6:20 am
Hi Sayantan
In our scerario we use sap as system for data
aggregion . We receive data from foreign system:
contract, invoice, delivery and others through idoc
But we don’t receive sales order.
Meantime. I tried do as you tell in the message, but
don’t success.
I did conclusion, may be wrong, that scenario SIT
without sales order was not possible
I think, system dont find 2 movement types for
schedule line category because we have no
schedule line categories in delivery without order
regards, Vadim
Da Thang
April 13, 2016 at 1:04 am
thx to share, it’s very useful for us
Ian Liponhay
April 13, 2016 at 3:03 pm
Hi Umesh – Thanks for this document, very helpful indeed.
Hi All,
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 40/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
Good day!
I have an issue related to POD.
The business function LOG_MM_SIT is activated in our system.
Customer master is POD relevant and line item as well. Schedule line
category is setup for POD that it will determine movement type 687. However
when I create the delivery, the movement type determined was 601(instead
of 687). I was able to replicate the issue once in our development system,
however, the issue now cannot be replicated anymore. It seems like this is
an intermittent issue, we experience this thrice now in our production system.
Does anyone experience this issue? If yes, kindly share your solution/inputs.
Thanks and regards,
Ian
Kiran Kumar Vadrevu
April 16, 2016 at 7:30 am
Hi All,
Any one tested following scenario?
Movement Type = 687 – (move into “Stock inTransit”)
Type for Issuing Valuated Stock in Transit = 631 ( move into Customer Consignment Stock)
Thanks,
Kiran.
Shiva Vasireddy
April 21, 2016 at 10:40 am
Thank you for sharing
Rohan Gudavalli
May 20, 2016 at 9:57 am
Hi,
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 41/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
Can you please suggest what should be the movement types for tracking
Intercompany – SIT?
I have tried using 681 and 685 movement types with Spec.Iss. Val. SiT field
as 1.
Can you please confirm if this is correct?
Thanks & Regards,
Rohan Gudavalli
Konstantin Dudura
July 9, 2016 at 1:47 pm
Hello LOG_MM_SIT gurus.
I have activated BF in SFW5, new delivery types become available, but
purchasing document types are missing.
What could go wrong?
Günter Lins
October 4, 2016 at 4:08 pm
Hello gurus,
same on our side. The MMPUR orders are not installed.
Does anyone know a MMPUR blog?
Kind Regards,
Günter
Mikel Ortega
January 17, 2017 at 7:39 am
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 42/43
13.02.2017 Customer Delivery – Stock in Transit (EHP5 – LOG_MM_SIT functionality) | SAP Blogs
Hi Umesh,
Just what I was looking for. Spot on manual. Thank you!
Kind Regards,
Mikel
https://blogs.sap.com/2013/11/11/customerdeliverystockintransitehp5logmmsitfunctionality/ 43/43