ferrobikini.blogg.se

Custom sap movement type
Custom sap movement type






STO can be initiated with a Planned Order or Purchase Requisition.Where no purchasing document is used for TP STO is based on Stock Transport Order (type of Purchase Order).STO must be configured for the sending plant / receiving plant where no plant specific configuration exists for TP.For STO, 351 and 101 is group together where for TP there is no link between 303 and 305.Stock types at receiving plants are different.After first step, goods are already reflected in receiving plant and not availableĭifferences between Stock Transport Orders (STO) and Transfer Postings (TP).Both use transaction MIGO for both steps.Similarities between Stock Transport Orders (STO) and Transfer Postings (TP) The Transfer Posting can be done with reference to a Reservation. Process a Transfer Posting ( MIGO > Transfer Posting) - movement type 305.Process a Transfer Posting ( MIGO > Transfer Posting) - movement type 303.The use of Planned Orders and Purchase Requisitions are optional. Process Goods Receipt against STO ( MIGO > Goods Receipt > PO) - movement type 101.Process Goods Issue against STO ( MIGO > Goods Issue > PO) - movement type 351.Create a Stock Transport Order ( ME21N, Purchase Order doc type UB).Need to control when goods leave plant A but not received at plant B.Long time span between leaving Plant A and arriving at Plant B.Some reasons for using 2-step movements (and not 1 step): Only after the second transaction is it available for use in Plant B. After the first transaction, stock has left plant A but it is not yet available at Plant B. Two step means that two transactions will be used to move the stock. Within SAP Inventory Management, there are two methods how stock are moved between plants using a 2-step process:Įxample: Lets assume stock is moving from Plant A (Storage Location 0001) to Plant B (storage location 0002).








Custom sap movement type