STO

Do settings at SPRO-MM--Purchasing -purchase order--set up stock transport order and do the settings for all the nodes under. Delivery type NL for intra company and NLCC for inter company. Document type UB for intra co. and NB for inter co. 1. Define shipping data for plant 2. make sure that the checking rule you assign over here is the same as the one defined in the material master. otherwise you cannot make a delivery against the order. 3. You have to match the availability check and checking rule 4. Assign delivery type checking rule plant wise Transaction side: Step 1.there should be a supplying plant defined as a vendor with vendor account group 0007 and in that vendor you have to assign the plant number in add.purchasing data tab. ( you can create a vendor same as the plant name) step 2. Define Receiving plant as customer with ship to party account group . ( you can create the customer same as the receiving plant) step 3:create a sto P.O step 4. create a delivery @ VL10b, do picking at VL02n and PGI STep 5: Create a billing document ( also can be printed as a document for materials delivery) step6: create an excise invoice at J1iiN and print step 7: Do carryout GR at the receiving plant.



_________________________________________________________________




Within SAP Inventory Management, there are two methods how stock are moved between plants using a 2-step process:
Stock Transport Orders (UB)
Transfer Posting
What does 2-step mean?Example: Let’s assume stock is moving from Plant A (Storage Location 0001) to Plant B (storage location 0002).Two step means that two transactions will be used to move the stock. After the first transaction, stock has left plant A but it is not yet available at Plant B. Only after the second transaction is it available for use in Plant B.Some reasons for using 2-step movements (and not 1 step):
Long time span between leaving Plant A and arriving at Plant B
Need to control when goods leave plant A but not received at plant B
Using Stock Transport Orders (STO)Steps:
Create a Stock Transport Order (ME21N, Purchase Order doc type UB)
Process Goods Issue against STO (MIGO > Goods Issue > PO) – movement type 351
Process Goods Receipt against STO (MIGO > Goods Receipt > PO) – movement type 101
The use of Planned Orders and Purchase Requisitions are optional.Using Transfer Postings (TP)Steps:
Process a Transfer Posting (MIGO > Transfer Posting) – movement type 303
Process a Transfer Posting (MIGO > Transfer Posting) – movement type 305
The Transfer Posting can be done with reference to a Reservation. Although this is not used a lot.Similarities between Stock Transport Orders (STO) and Transfer Postings (TP)
Both use transaction MIGO for both steps
After first step, goods are already reflected in receiving plant and not available
Differences between Stock Transport Orders (STO) and Transfer Postings (TP)
Movement types are different351 & 101 for STO303 & 305 for TP
Stock types at receiving plants are different- In Transfer (MARC-UMLMC) for TP- Stock in Transit (MARC-TRAME)for STO
For STO, 351 and 101 is group together where for TP there is no link between 303 and 305
STO requires more transactions than TP
STO must be configured for the sending plant / receiving plant where no plant specific configuration exists for TP
STO is based on Stock Transport Order (type of Purchase Order). Where no purchasing document is used for TP
STO can be initiated with a Planned Order or Purchase Requisition
Planning (MRP) can be used to initiate movements, but only STO’s
Configuration required to use STOConfig: MM > Purchasing > Purchase Order > Set up Stock Transport Order > Assign Document Type, One-Step Procedure, Underdelivery ToleranceHere the source plant, destination plant and allowed STO document type is specified. The post is based on SAP ECC6