Downtime Announcement: Please note the SAP Community Wiki will be unavailable due to a system upgrade on Thursday, September 24th between 6 and 7 AM CEST
Skip to end of metadata
Go to start of metadata
  • Stock Transport Process in SAP ERP System


  • Basic Scenarios  

STO can be categorized into four types depending on different scenarios.

Scenarios

SD/LE

MM

Intra-company STO
In two steps

Delivery type: NL
Delivery item category: NLN
Billing relevance: Not relevant

PO type:
> UB  Stock transport ord., with "U" item category
> NB  Standard PO, with "blank" item category
Movement type:  641

Intra-company STO
In two steps

Delivery type: NL
Delivery item category: NLN
Billing relevance: Not relevant

PO type:
> UB  Stock transport ord., with "U" item category
> NB  Standard PO, with "blank" item category
Movement type:  647

Cross-company STO
in one step

Delivery type: NLCC
Delivery item category: NLC
Billing relevance: relevant to billing

PO type:
> NB  Standard PO, with "blank" item category
Movement type:  643

Cross-company STO
in two steps

Delivery type: NLCC
Delivery item category: NLC
Billing relevance: relevant to billing

  PO type:
> NB  Standard PO, with "blank" item category
Movement type:  645


  • Shipping Data and Delivery Due Index

    • To deliver STO, it's necessary to have shipping data (EKPV table entry) tab in the STO.
    • If there is still open quantity to be delivered, "deliv. creation date" (EKPV-LEDAT) filled has value. When all the quantity has been delivered, the date will be cleared.
    • If STO is ready to be delivered, system will update delivery due index table VETVG.
  • Shipping Data Determination

    • Shipping data (table EKPV) in STO is determined depending on:
      1. Supplying Plant
      2. Ship-to (customer of the receiving plant)
        (IMG -> MM -> Purchasing -> Purchasing Order -Set up Stock Transfer Order -> Define Shipping Data for Plants)
      3. Material Master Data
      4. Delivery Type
        (IMG -> MM -> Purchasing -> Purchasing Order -Set up Stock Transfer Order -> Assign Delivery Type and Checking Rule)
    • Shipping data determination:
      1. Sales Area: from supplying plant (T001W) (See SAP notes 169586, 170029, 170075, 170082, 303957)
      2. Shipping Condition: default order type (‘DL’) for delivery type (TVLK-DAART), otherwise customer master data (KNVV-VSBED)Delivery priority: material/customer/distribution chain (KNMT), otherwise customer master data (KNVV-LPRIO)
      3. Unloading Point: from Ship-to, if available
      4. Shipping Point: loading group/shipping condition/supplying plant (TVSTZ)
      5. Route: usual criteria for route determination (TROLZ)
      6. Delivery Type: Purchase order category/document type/supplying plant (T161V, different delivery types)
      7. Route Schedule: with delivery scheduling (T161V)
      8. Loading Group and Transportation Group: material master data (MARA, MARC)
      9. Language of Material Description: customer master data (KNA1-SPRAS) (to read material master data from MAKT)
      10. Incoterms: customer master data, from purchase order
      11. Indicator for Order Combination: customer master data
      12. Indicator for Partial Deliveries: material/customer/distribution chain (KNMT), otherwise customer master data (KNVV-KZTLF)
  • Delivery Due Index VETVG

    • Different from delivery due index of sales document, VETVG is the delivery due index for stock transport orders and contains the POs that are due for delivery.
    • Index VETVG is needed for selection in VL10*/VL04. If a STO cannot be listed in VL10* / VL04, please check whether the index are updated correctly.
    • Report ZKORVETV of note 61148 can be used to reorganize the delivery due index VETVG.
    • Precondition of VETVG:
      VETVG will be filled (STO is relevant to delivery) if:
      > shipping data (EKPV) is filled,
      > delivery date in EKPV is not 00.00.0000
  •  Create Replenishment Delivery

    • Replenishment delivery can only be created by collective transaction.
    • Tcodes:
      1. VL10* (VL10B, VL10D, VL10F...)  In user role, "with purchase orders" indicator is flagged.
      2. VL04 (Out of date)
      3. There is no dialog transaction to deliver STO.
      4. Characteristics of replenishment deliveries from STO (Note:  842829)
  • Control of Replenishment Delivery

  • Goods Movement

    • Goods issue with 641 creates a special stock type, called “stock-in-transit” in the receiving plant (MB5T)
    • If replenishment delivery contains HU, after goods issue with 641 movement, the HU will have status "in transit". (VEKP-STATUS = 40).
    • Goods issue with 643 (cross-company) doesn’t create such a stock and contains only one line in the GI material document
    • Goods issue with 643 (cross-company) is nearly the same as goods issue with 601 to an external customer; you can only sum up the stock transport orders that are open for goods receipt to determine what is “in transit” (stock type: “stock-in-transit-CC”)
    • Goods receipt (with 101) is done via MB0A/MIGO with respect to the replenishment delivery.
    • You can also use inbound delivery to post goods receipt. (Similar as normal purchasing order)
  • How Replenishment Delivery Updates STO

    • PO History (table EKBE)
      > When replenishment delivery is created, it will update PO history with delivery number, item number and delivery quantity.
      > When posting GI, the material document will also be updated to PO history.

    • PO Delivery Schedule (table EKET)
      > When replenishment delivery is created, the delivery quantity will be cumulated to corresponding delivery schedule. (EKET-GLMNG field).
      > When posting GI, the quantity will be cumulated to corresponding delivery schedule. (EKET-WAMNG).
       
    • Delivery schedule (EKET) must be consistent with PO history (EKBE), otherwise, short dump (message_type_x ME803) might occur.
  • One-step Goods Issue

    • Set T161W-UML1S = ‘X’ for supplying and receiving plant (and purchasing document category, e.g. ‘F’ for purchase order)
       
    • set TVEP-BWA1S = 645/647 for SD schedule type NC/NN that belongs to item category NLC/NLN in TVEPZ (tcode VOV6)
  • Automatically Creation of Inbound Delivery during 2-step STO

As of Release ECC 6.00, you can also use the automatic inbound delivery creation during two-step stock transfers. The inbound delivery is created using the output determination in the outbound delivery. After the goods issue has been posted successfully,
the system uses a special function (output type SPED) to create the inbound delivery. 
Please read SAP note 965176 for more information.

  • No labels

1 Comment

  1. Thank you  Harry Wu, for your post it helped a lot to understand the process of STO