A stock transfer order (STO) in SAP is a document that records the movement of materials between different storage locations, plants, or company codes within the same organization. It enables controlled, auditable tracking of inventory transfers without immediate financial posting.
STOs are created in the Materials Management (MM) module of SAP ERP. They serve as planning and execution tools for internal logistics, ensuring accurate inventory levels across multiple sites. The process begins with a purchase requisition or demand forecast, leading to a confirmed STO that triggers physical movement and system updates.
For example, if a warehouse in Chicago needs 500 units of product P-1234 from a plant in Atlanta, a planner creates an STO in SAP. The system reserves the material in Atlanta's inventory and updates the receiving location in Chicago. Only after the goods are physically delivered and confirmed does the system update the actual stock levels.
When a stock transfer order is initiated, SAP validates the availability of material at the source location. If sufficient stock exists, the system generates a delivery document and assigns a unique internal number. This number appears in transaction codes like MB31 (create STO) or MB32 (display STO).
The receiving site receives a notification to expect the shipment. Upon receipt, the warehouse staff confirms the delivery using transaction MB31 with action "Goods Receipt." At this point, SAP updates both the sender's and receiver's inventory balances in real time. The transfer is then marked as complete in the system.
Each STO includes key fields: material number, quantity, source and destination storage locations, plant codes, and delivery dates. These ensure traceability and compliance with internal controls. For instance, a retail distributor may use STOs to move seasonal apparel from regional hubs to stores before holiday sales.
STOs fall into two primary categories based on organizational structure:
| Type | Scope | Use Case | Example |
|---|---|---|---|
| Intercompany STO | Between different company codes | Transfers between legal entities | Plant A (US) sends goods to Plant B (Germany) |
| Intra-company STO | Within the same company code | Internal movement across plants or storage bins | Warehouse in Dallas ships to warehouse in Houston |
Intercompany STOs require additional steps for accounting. They generate separate financial postings in FI (Finance) and may involve intercompany billing. In contrast, intra-company STOs typically do not affect financial accounts unless configured otherwise.
Another distinction lies in whether the STO is planned or executed. A planned STO serves as a forecast and is not yet committed. An executed STO reflects actual movement and is closed upon confirmation. SAP allows users to cancel or modify open STOs before physical delivery.
Many users confuse STOs with goods issue (GI) or goods receipt (GR). A GI removes material from inventory due to production or consumption. A GR adds material to inventory after receiving. An STO is neither-it's a movement instruction between locations.
Another frequent error is assuming STOs automatically trigger deliveries. They don't. The STO must be released to create a delivery document. Without release, the system holds the order pending approval or scheduling.
STOs do not update financial values unless configured for valuation. In most cases, only inventory quantities change. This keeps the balance sheet stable during internal transfers. According to SAP Help Portal, "Material movements via STO are not posted to the general ledger unless the transfer involves different company codes."
For example, a manufacturer in Ohio uses an STO to send 1,000 units of component C-555 to a plant in Michigan. The sending plant reduces its stock by 1,000 units. The receiving plant increases its stock by 1,000 units. No accounting entries occur unless the two plants belong to different legal entities.
STOs are widely used in manufacturing, distribution, and retail. A large retailer might use them to redistribute high-demand electronics from central warehouses to local stores ahead of a sale. This ensures timely availability while maintaining accurate inventory records.
I once worked with a client who had inconsistent stock counts across their network. After auditing their STO processes, we discovered that many orders were being manually entered without proper validation. We implemented automated checks using SAP's workflow engine and reduced discrepancies by 68% over six months.
Best practices include setting up default values for frequently used materials, enabling batch management where applicable, and integrating STOs with warehouse management systems (WMS). When integrated, WMS can auto-generate STOs based on picking requirements.
For advanced users, STOs can be triggered by MRP runs or demand planning tools. This enables proactive inventory balancing across locations. However, manual review remains essential to prevent unintended transfers.