Professional Documents
Culture Documents
Stock Transport Process in SAP ERP System
Stock Transport Process in SAP ERP System
Stock Transport Process in SAP ERP System
Basic Scenarios
STO can be categorized into four types depending on different scenarios.
Scenarios SD/LE MM
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)
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.
VOV6)