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.