AUTOMATION OF STO PROCESS.

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 Delivery type: NL

PO type:

In two steps

Delivery item category: NLN

> UB Stock transport ord., with "U" item category

Billing relevance: Not relevant

> NB Standard PO, with "blank" item category

Movement type: 641

Intra-company STO Delivery type: NL

PO type:

In two steps

Delivery item category: NLN

> UB Stock transport ord., with "U" item category

Billing relevance: Not relevant

> NB Standard PO, with "blank" item category

Movement type: 647

Cross-company STO Delivery type: NLCC

PO type:

in one step

> NB Standard PO, with "blank" item category

Delivery item category: NLC

Billing relevance: relevant to billing Movement type: 643

Cross-company STO Delivery type: NLCC
in two steps

Delivery item category: NLC

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

Billing relevance: relevant to billing Movement type: 645

o
o

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.
4.

Material Master Data

Delivery Type
(IMG -> MM -> Purchasing -> Purchasing Order -Set up Stock Transfer Order -> Assign Delivery Type and Checking Rule)

o
1.
2.

Shipping data determination:

Sales Area: from supplying plant (T001W) (See SAP notes 169586, 170029, 170075, 170082, 303957)
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.

o
o
o
o

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

o
o

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

o
o
o
o

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) doesnt 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)

o
o

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. (EKETWAMNG).

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.

LOG_MM_SIT: Inbound Delivery with Stock in Transit (New) ( RELNMM_605_LOGMMSIT_INB )

Fill RESBD Structure from EBP Component Structure ROGBILLS - Synchronize billing plans
This documentation is copyright by SAP AG.

Short text

LOG_MM_SIT: Inbound Delivery with Stock in Transit (New)

Use
As of SAP enhancement package 5 for SAP ERP 6.0 (SAP_APPL_605), Business Function MM, Stock in Transit, and Actual Costing, you can use condition type SPED (Stock
Transfer Generates Inbound Delivery to specify that inbound deliveries with reference to an outbound delivery are automatically created for stock transfer processes with
receiving valuated stock in transit. The following functions are available for inbound deliveries with stock in transit:

At goods receipt you can post an inbound delivery either in the standard way (movement type 101), or via the receiving stock in transit to the receiving plant
(movement type 109).
If the quantity changes during the proof-of-delivery, the system updates the inbound delivery. In transaction VLPOD (Proof of Delivery), the system displays the
difference (POD Overview tab, Variance from Actual Delivered Quantity in Sales Unit).

The new transaction MB5SIT (Display Stock in Transit) allows you to

o
o

Display receiving stock in transit for the intra-company and cross-company process, by entering the inbound delivery number
Display issuing valuated and receiving valuated stock in transit

If you have created an inbound delivery using condition type SPED, you can post the material from issuing valuated stock in transit to receiving valuated stock in
transit in transaction VLPOD. To post into the receiving plant, you must use movement type 109 in transaction VL32N or MIGO.
Note:

If you have to enter a handling unit for the storage location in the receiving plant, post first into the valuated stock in transit of the receiving plant. From the valuated stock in
transit of the receiving plant, you can then post the goods receipt with reference to the inbound delivery into the storage location with mandatory handling unit.

Effects
Effects
Effects
Effects
1.

on
on
on
on

Existing Data
Data Transfer
System Administration
Customizing

To set up inbound deliveries with stock in transit, you need to make the following settings in Customizing:
Check confirmation control key:
In Customizing, choose Materials Management -> Purchasing -> Confirmations -> Set Up Confirmation Control
For the confirmation control key 0004 (Inbound Delivery), the following must be flagged under Confirmation Sequence:

o
o
1.

Confirmation is GR-Relevant checkbox

GR with Reference to Confirmation checkbox

Define condition type SPED:

In Customizing, choose Logistics Execution -> Shipping -> Basic Shipping Functions -> Output Control -> Output Determination -> Maintain Output Determination
for Outbound Deliveries -> Maintain Output Determination Procedure.
Select schema V10000 (Header Output) and choose Control Data. Check that an entry exists with condition type SPED (Stock Transfer Generates Inbund
Delivery) and Requirement 408 (Stock Transfer Attachment ID).

1.

Define delivery type

In Customizing, choose Materials Management -> Purchasing -> Confirmations -> Define Internal Confirmation Categories.
Check that for confirmation category LA (Inbound Delivery), the new fieldDelivery Type Inbound Stock in Transit (SiT) contains a delivery type for the process with
stock in transit (for example Inbound Delivery of Receiving Valuated Stock in Transit (ELST). This delivery type must use an item category (for example ELST) that
uses movement type 109 or another movement type with posting string reference 109. Check the following:

In Customizing for Logistics Execution, under Shipping -> Deliveries -> Define Item Category Determination in Deliveries, check the item category that is
assigned to this delivery type.

o
1.

In Customizing, under Logistics Execution -> Shipping -> Deliveries ->Define Item Categories for Deliveries, check that movement type 109 or a

movement type with posting string reference 109 is assigned to this item category.
Set up condition record
You create inbound deliveries with this item category when processing output type SPED during the goods issue of an outbound delivery.
In transaction VV22 (Change Output - Condition Records: Shipping), ensure that the correct condition records for the outbound delivery type used (NCCR, NCC3,
NLIR, or NLI3) have been created for output type SPED for output determination.
Output type SPED with role WE (Goods Receiver), medium 8 (Special Function) and time 4 (Send Immediately (When Saving Application).
For more information, see the following release notes:

o
o

Cross-Company-Code Stock Transfer and Customer Delivery (New)

Intra-Company-Code Stock Transfer (New)

Further Information
SAP Library for SAP ERP on Help Portal under http://help.sap.com/erp -> SAP ERP Central Component -> SAP ERP Enhancement Packages -> ERP Central
Component Enhancement Package 5 -> SAP ERP Central Component -> Logistics -> Materials Management (MM) -> Inventory Management (MM-IM) -> Managing Special
Stocks (MM-IM) -> Stock Transfer Using a Stock Transport Order ->Processes with Valuated Stock in Transit

Release note LOG_MM_SIT: Business Function MM, Stock in Transit and Actual Costing

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up Addresses (Business Address Services)
This documentation is copyright by SAP AG.

1. SPRO > MM > Purchasing > PO > Set up STO > Activate Automatic Delivery Creation and CRM Billing
Make sure that you use the proper document type ("F"), supplying plant, and creation indicator ("Y" in /SPE/V_T161V-AUTO_DELV)

Activate Automatic Delivery Creation and CRM Billing

Use

In this IMG activity, you can activate the automatic creation of

replenishment deliveries and CRM Billing for stock transport orders.

Requirements

o You must use SAP CRM to execute CRM Billing.

o When you create an inbound delivery from an outbound delivery in

SPM, you must define a new document type in Customizing for
Materials Management, by choosing Purchasing -> Purchase Order ->
Define Document Type. You may copy the document type Stock transport
order ('UB'), but you must set the Vendor indicator, to ensure that
the intra-company stock transport order copies the values from the
vendor information record. This, in turn, ensures that the
Confirmation Control field in the stock transport order is set to
Inbound delivery ('0004').

Activities

If you want to create a replenishment delivery immediately after

creation of the stock transport order, set the Auto Delv. indicator.
This does not apply for purchase orders that are not yet released and on

hold.

If billing is required in CRM Billing (for example, for cross-company

and cross-border stock transfers), set the CRM Bill indicator.

Further notes

o If you use this function the system does not perform an availability
(ATP) check when it creates the delivery. It assumes that the
availability has already been checked during stock transport order
processing.

o The route is determined in Extended Warehouse Management (SAP EWM)

only if the automatic creation of replenishment deliveries is
active.

2. SPRO > MM > Purchasing > PO > Set up STO > Activate Automatic Delivery Creation for PO type and Shipping Point

NOTE -There's one prerequisite: please check OSS note 1069448.

3. Go to the transaction VL10CUC, choose the delivery creation profile 'STOA' and uncheck the indicator 'Georoute'.

Auto picking

1) Shipping points(V_TVST) details screen enter the below details under "Print picking List"
Output Type
EK00
Message Language
EN
Number of Messages
1
Send Time
4
Transmission Medium
1

2)

via transaction VP01SHP under

"shipping (special case)(V4) and picking list (EK00)

enter your shipping point, output device, Name, Suffix1, Suffix 2
Shipping Point OutputDevice - LP01
Name LIST1S
Suffix 1 EK00
Suffix 2 KOMMILISTE

The above setting should trigger automatic picking in DO

Automatic PGI
you can create the PGI Atomatically by BATCH JOB using the program nder the VL23 transaction code.
Goto the Transaction code SM36 to create a job for the program SAPMSSY0 which is the program for the AUTO PGI
create a variant for the Delivery document types and sales organisation combinatioans and add this variant to the bath job created in SM36.
Set the time of the Job to run after every 5 minutes, so once the job exected it will pcik all the Deliveries which are pending for the PGI.
Automatic Billing
After the PGI done you can run SDBILLDL program to create the Billing for all the document which were cleared and due for Billing.VF04

1.
2.
3.
4.
5.
6.
7.
8.

RM06BB30(ZME59N)
SDV03V02(ZSTOV_V2)
RVV50R10C(ZVL10B/ZVL10D)
WS_MONITOR_OUTB_DEL_GDSI(ZVL23)
SDBILLDL/ RV60SBAT(ZVF06)/ BAPI_BILLINGDOC_CREATEMULTIPLE(ZBAPI_BILLINGDOC_CREATEMULTIPL)
J1I3/J_1I_BATCH_UTILIZATION_MODVAT(ZJ1I3)/ Z_J1I3- ZJ1I3
J1IP/J_1IPRNE(ZJ1IP)
WS_MONITOR_INB_DEL_GDRC(VL06IG)

00 06 589

FM - RV_INVOICE_CREATE