on 09-29-2009 1:48 PM
How to do the stock transport order.give me step by step.
Thanks,
Maran.d
hi maran,
Follow the below steps to to make STO between two plants ( different company codes).It is also called as Inter Company STO.....
1) Create one Customer Master in XD01 with respect to Supplying Plant Sales Area and assign this Customer no with Receiving Plant in OLME->PO-> set up STO->Define shipping data for plant and for the supplying Plant assign the above sales area.( Make sure, In Customer Master, sales Area Tab: you are maintaining shipping condition)
2) For Receiving Plant Pur. Org and Co.Code Combination create Vendor master in XK01 and in this vendor master assign the Supplying plant in Pur.Org.Data screen->Extras--> Add.Pur.data
3) OLME->PO-> Set up STO------>For your supplying plant assign document type NB, Delivery type NLCC and Checking Rule RP
4)then For your supplying Plant and receiving Plant assign Document type NB
5)Make sure you are maintaining Sales View for the material at supplying Plant and in Sales /Gen plant Data view maintain Availability check, Loading group and Transportation group.
6) In SPRo-->Logistics execution> Shipping->Basic shipping functions->Shipping point Determination>assign shipping points-> For your Loading group, Shipping Condition and Supplying plant combination, Assign shipping point
these are the configuration settings you have to do in background.
Then Create STO from Receiving Plant in ME21N with document type NB.
Based on that STO, Create Delivery in VL10B from supplying Plant
Do PGI in VL02N from Supplying plant
Do GR in MIGO at Receiving Plant keeping Outbound delivery as a ref. document.
Now your STO bet. two plants belongs to diff. Co.Codes will be completed.
2)Follow the below steps to to make STO between two plants belongs to same company codes).It is also called as Intra- Company STO.....**
1)Create one Customer for Supplying Plant Sales area and assign this Customer no with Receiving Plant in OLME---> PO -
> Set up STO -
> define Shipping Data for plants. and maintain the same sales area in your Supplying plant.
2) In OLME---> PO -
> Set up STO.....for your Document Type: UB and Suppying plant Combination assign Del. Type NL and Checking rule RP
3) In OLME---> PO -
> Set up STO...for your Supplying Plant and Receiving Plant combination Maintain Doc. Type : UB
Make sure you are maintaining Sales View for your Material at Supplying Plant.
4) Maintain Shipping point at, SPRO----> Logistics Execution -
> Shipping -
> Basic Shipping Functions -
> Shipping Point Determination for Plants.....there for your Loading group, Shipping Condition, Shipping Plant combination maintain Shipping plant..
Now Create STO in ME21N with Doc.type: UB at Receiving Plant.
Then Create Delivery in VL10B from Supplying Plant...
Then Do PGI in VL02N from supplying Plant.
Then do GR at Receiving Plant based on Outbound Delivery at Receiving Plant...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear,
Two-step movement Plant to 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: Lets 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.
Regards,
Syed Hussain.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear,
Continuation...
Using Transfer Postings (TP)
Steps:
Process a Transfer Posting (MIGO > Transfer Posting) âu20ACu201C movement type 303
Process a Transfer Posting (MIGO > Transfer Posting) âu20ACu201C 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 different
351 & 101 for STO
303 & 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âu20ACu2122s
Configuration required to use STO
Config: MM > Purchasing > Purchase Order > Set up Stock Transport Order > Assign Document Type, One-Step Procedure, Underdelivery Tolerance
Here the source plant, destination plant and allowed STO document type is specified.
Regards,
Syed Hussain.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
95 | |
11 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.