In the previous post about stock transfer between plants, I have explained that we can transfer stock between two plants in SAP ERP with:
- Stock transfer posting (which solely can be done with SAP MM Inventory Management function). You can read Procedures of Stock Transfer Posting between plants and Intra and Cross Company-Codes Stock Transfer Posting to know more details about stock transfer posting.
- Stock transport order (which involves SAP MM Purchasing function, and can also involve SAP SD module). Stock transport order can be done: without SD delivery / with SD delivery / with SD delivery and billing.
In this post I will explain stock transport order without Sales & Distribution (SD) delivery function.
Stock transport order (STO) is actually a Purchase Order (PO) with “Transport (T)” as Control indicator for purchasing document type (in the document type configuration) and “U” item category (in the purchasing document item). The standard document type for STO in SAP ERP is “UB”, but you can create new one as you need.
PO document type configuration can be accessed with “S_ALR_87002197” transaction code, or with “SPRO” tcode’s menu path: SAP Customizing Implementation Guide – Materials Management – Purchasing – Purchase Order – Define Document Types.
Stock transport order without delivery can only be done with two-steps procedure.
Procedure of stock transport order without delivery:
- Stock Transport Order (STO) is created at receiving plant (the plant which needs the material from the issuing/supplying plant).
STO can be created with or without reference document (a Stock Transfer Request/STR, which is actually a Purchase Requisition document). STO can be created with ME21N tcode or ME57 tcode (if only there is a PR as reference document).The main information in an STO are: supplying plant, material number, quantity, delivery date, plant (receiving plant), storage location (of receiving plant), etc.We can apply a release strategy to the STO based on our needs. If we apply one, STO must be fully released/approved before it can be processed to the next step.
- Based on STO, the supplying/issuing plant will post the Goods Issue transaction.
Goods issue can be done with MIGO tcode. The movement type of goods issue of an STO is 351 (352 to cancel it).
On the MIGO screen, we have to determine the issuing storage location before posting the goods issue transaction. As long as there is sufficient stock on the issuing storage location, we can post the goods issue transaction.
The transaction will create a material document; and decrease the unrestricted-stock on the storage location of the supplying plant and increase the “stock in transit” in the receiving plant.
We can monitor the stock in transit that caused by the goods issue of STO (before it’s GR by the receiving plant) with MB5T tcode.
We can also monitor the total “stock in transit” quantity of a material in a plant (receiving plant) with MB52 tcode. The quantity on the “stock in transit” column of MB52 tcode can come from one of several STOs which have not been GR on that plant.
We can also see the total “stock in transit” quantity of a material in a plant (receiving plant) from MARC table, TRAME field.
- Once the material arrives at the receiving plant, Goods Receipt transaction must be posted refers to the STO. Goods Receipt can be done with MIGO tcode. The movement type of goods receipt of an STO is 101 (102 to cancel it).
The transaction will create a material document; and increase the unrestricted-stock on the storage location of the receiving plant and decrease the “stock in transit” in the receiving plant.
STO without delivery can be used to transfer stock between two plants in a same company code or cross company codes.
We can enter a vendor (freight vendor) in the stock transport order.
Delivery costs can be entered in the stock transport order.