IDoc for Confirming Transfer Orders
Definition
Several IDocs are available for confirming a transfer order (TO) from the external system to the Warehouse Management system (WMS).
The following only describes IDoc WMTOID03.
Use
Using these IDocs, you confirm transfer orders that have been executed to the WMS. Based on the confirmed data, the WMS confirms these TOs.
Prerequisite
You have defined which transfer orders require confirmation in the Customizing for Warehouse Management under Master Data ®
Define Storage Type or Activities ® Transfers ® Define Movement Types. For more information, see Confirming Transfer Orders.When sending the TO data, the WMS first transferred the data which requires confirmation in IDoc WMTOID01 or WMTOID02 in segment E1LTROI with field KZQUI to the external system.
We recommend that you simulate sending a cancellation reply from the external system to the WMS, in order to test the relevant cancellation processes. Reports RLCATO00 and RLCATO10 are available for testing cancellation.
Confirming Storage Units
If you work with storage units (SUs) in the warehouse and you move the entire storage unit, you confirm one transfer order for the entire SU for this stock movement.
If a storage unit with mixed storage is involved and you move individual materials from it, there are several transfer orders for this storage unit. You confirm the corresponding transfer order for each stock movement.
If you determine that there are differences in the SU when you execute the TO, confirm the entire storage unit and enter the difference quantities for the items for which differences occurred.
Confirmation Without SU-Management
For stock removals, you normally confirm entire transfer orders.
For putaways, you can confirm TOs item by item if you put away several pallets with one TO.
If you confirm entire TOs, you can enter differences for individual TO items.
IDoc construction for confirmation
Case |
Segment |
Quantity |
Meaning |
A |
E1LTCOX |
1 |
Confirm complete SU |
B |
E1LTCOH |
1 |
Confirm a complete TO |
C |
E1LTCOH E1LTCOI |
1 1 to n |
Confirm an entire TO and enter differences for items 1 to n. |
D |
E1LTCOH E1LTCOI |
1 1 to n |
Confirm one or more TO items |
E |
E1LTCOX E1LTCOH E1LTCOI |
1 1 to m 1 to n |
Confirm a complete SU and enter differences for TOs 1 to n with TO items 1 to n |
Confirming Performance Data
You confirm performance data (actual TO processing time) to the WMS via segment E1LTCOG. Normally, the WMS determines the planned TO processing time and adds to this the planned processing time reported by the external system.
You can also report the actual data to the WMS independently of the confirmation, by only sending segment E1LTCOG.
You can report actual data if the transfer order data was transferred to the external system with the value 2, 3, or 4 for indicator KZLEI in IDoc WMTOID01 or WMTOID02.
Depending on the value of indicator KISTZ in IDoc WMTOID01 or WMTOID02, you confirm the actual data in segment E1LTCOG as follows:
Value of Indicator KIST |
Relevant Fields |
1: Actual time as net duration |
ISTWM PERNR |
Start and end time manual Start and end time automatic |
STDAT STUZT ENDAT ENUZT PERNR |
Confirming Differences
If you determine during a stock movement that a difference exists, transfer these references via IDoc WMTCID03 in segment E2LTCOI000, by filling the following fields:
Segment definition E2LTORH003 (TO header) (released as of SAP R/3 4.6C)
Field |
Value |
SQUIT |
Blank |
NISTA |
Actual moved or removed quantity |
NDIFA |
Difference quantity of the stock movement: Difference between the quantity in the TO and the actual quantity moved |
RISTA |
Actual quantity of the return item if applicable |
RDIFA |
Difference quantity for return item |
ALTME |
Unit of measure to which the quantities refer (from the TO that was already send) |
KZDIF |
If you want to override the storage type and the storage bin to which the difference is posted |
To confirm differences to the WMS, use case 3, 4, or 5.
You must confirm the entire actual quantity of the relevant TO item. The following is valid for field VSOLM in structure E1LTORI:
VSOLM = NISTA + NDIFA + RISTA + RDIFA.
Confirmation for Zero Stock Check
For confirmation with zero stock check, use case 3 or 4.
For stock removal from a storage type with zero control, you must explicitly confirm the bin, which has become empty as a result of the confirmed stock movement.
If the indicator KZNKO was set for the stock movement in IDoc WMTOID01 or WMTOID02, IDoc WMTCID03 must confirm the zero stock check to the WMS in segment E1LTCOI.
If the storage bin is empty following the stock removal, set the indicator KZNUL in the IDoc.
If there is a remaining quantity in the storage bin, transfer the following fields in segment E1LTCOI:
Field |
Value |
KZNUL |
Blank |
PISTA |
Remaining stock counted The system issues any remaining stock found separately |
ALTME |
Unit of measure to which the quantities refer (from the TO that was already send) |
Even if the zero stock check was not required, the external system can confirm the zero stock check to the WMS if the storage bin becomes empty as a result of the stock movement. In this case, the physical stock level differs from the stock level in the system. For this, you set indicator KZNKO in IDoc WMTCID02.
Confirming Batch-Managed Material
If, during goods movements, you confirm batch-managed material in SU-managed bulk storage or in a warehouse with lean WM, you transfer the batch number of the materials that have been removed with the confirmation data. To do this, you use field CHARG in segment E2LTCOI004 (confirm batch for lean WM or bulk storage).
Stock Overview in SU-Managed Bulk Storage
You confirm the storage units (SUs) that have been removed to the WMS along with the confirmation of the transfer order.
Confirm withdrawal of a complete SU
Field |
Value |
LENUM |
Number of storage unit removed |
VQUIT |
X |
Confirm withdrawal of the SU with difference and remaining quantity
Field |
Value |
LENUM |
Number of storage unit removed |
PICKM |
Pick quantity |
DIFFM |
Difference quantity |
RESTM |
Remaining quantity |
ALTME |
Unit of measure upon which the quantities are based |
When confirmation of the individual SUs is complete for a TO item, set the field BQUIT in segment E1LTCOI.
In this case, you confirm the TO item by item (see case 4). This means that there can be several TO items per confirmation. Only one confirmation is permitted per storage unit withdrawn.
If a material with batch management is involved, you transfer the batch number along with the confirmation data. To do this, you use field CHARG in segment E2LTCOI004 (confirm batch for lean WM or bulk storage).
Confirmation in Bulk Storage with Mixed Storage
If you confirm transfer orders for a bulk storage type with mixed storage, you must transfer the quant data to the WMS for the material that has been moved. The WMS can only confirm the transfer order if the goods movement is clearly assigned to certain quants.
Special Features of Confirmation for Lean WM
If you use lean WM, we recommend confirming the quant number to the WMS, since no quant data is known in a warehouse with lean WM.
You transfer the batch number of a batch-managed material with the confirmation data via field CHARG in segment E2LTCOI004.
If you use handling units, field PAPOS, along with TAPOS, serves as a pointer to the HU data records that belong to the TO item in table T_LTAP_CONF_HU.
Structure
Message Type
You define message type WMTOCO for the inbound partner profile.
Segments
The IDoc for transferring confirmation data is constructed as follows:
Segment definition E2LTCOX002: Confirm storage unit (as of release 4.6A)
Field |
Data Type |
Description |
Required Entry Field |
Note |
LGNUM |
CHAR 3 |
Warehouse number |
X |
|
LENUM |
CHAR 20 |
Storage unit number |
X |
|
QNAME |
CHAR 12 |
User name for confirmation |
|
|
SQUIT |
CHAR 1 |
Confirm entire storage unit |
X |
Value ‘X’ |
NLPLA |
CHAR 10 |
Destination storage bin |
The destination storage bin is based on the deviating storage bin of the complete SU (Customizing) |
|
NPPOS |
CHAR 2 |
Destination position |
The destination storage bin position is based on the deviating storage position of the complete SU (Customizing) |
|
ENAME |
CHAR 12 |
User name of the pick confirmation |
||
QUKNZ |
CHAR 1 |
Confirmation indicator for separate confirmation |
1 = Confirm stock removal only 2 = Confirm material transfer only |
Segment definition E2LCOHU000: HU data per TO item (as of release 4.5A)
Field |
Data Type |
Description |
Required Entry Field |
Note |
TANUM |
NUMC 10 |
TO number |
||
TAPOS |
NUMC 4 |
TO item |
||
VONHU |
CHAR 20 |
Source HU |
||
NACHU |
CHAR 20 |
Destination HU |
||
SERNR |
CHAR 18 |
Serial number |
||
PAPOS |
NUMC 4 |
Current number of HU data row within TO item |
Segment definition E2LCOSE000: Confirm with serial number (as of release 4.5A)
Field |
Data Type |
Description |
Required Entry Field |
Note |
TANUM |
NUMC 10 |
TO number |
||
TAPOS |
NUMC 4 |
TO item |
||
VONHU |
CHAR 20 |
Source HU |
||
NACHU |
CHAR 20 |
Destination HU |
||
HUENT |
CHAR 1 |
HU is removed completely |
||
MENGA |
QUAN 15 |
Quantity for repacking in alternative unit of measure |
||
ALTME |
UNIT 3 |
Alternative unit of measure to stock keeping unit |
||
DMGEA |
QUAN 15 |
Source difference quantity in alternative unit of measure |
||
PAPOS |
NUMC 4 |
Current number of HU data row within TO item |
Segment definition E2LTCOG001: Report performance data (as of release 4.5A)
Field |
Data Type |
Description |
Required Entry Field |
Note |
LGNUM |
CHAR 3 |
Warehouse number |
||
TANUM |
CHAR 10 |
Transfer order for which data is confirmed |
||
SOLEX |
CHAR 15 |
Target processing time from external system |
||
PERNR |
CHAR 8 |
TO processor (personnel number) |
||
STDAT |
CHAR 8 |
TO start date |
||
ENDAT |
CHAR 8 |
TO end date |
||
STUZT |
CHAR 6 |
TO start time |
||
ENUZT |
CHAR 6 |
TO end time |
||
ISTWM |
CHAR 15 |
WM-TO actual processing time |
||
AUSFB |
CHAR 4 |
TO processing comment code |
Segment definition E2LTCOH003: TO header (as of release 4.6A)
Field |
Data Type |
Description |
Required Entry Field |
Note |
LGNUM |
CHAR 3 |
Warehouse number |
X |
|
TANUM |
CHAR 10 |
Transfer order number |
X |
|
QNAME |
CHAR 12 |
User name for confirmation |
||
SQUIT |
CHAR 1 |
Indicator: Confirm entire transfer order |
X |
If the entire transfer order is to be confirmed. (Versions 2, 3, and 5) |
KOMIM |
CHAR 1 |
Transfer pick quantities to delivery / post goods issue (as of release 4.0) |
GI posting (2) occurs only after all of the items in the delivery have been confirmed |
|
EINLM |
CHAR 1 |
Transfer putaway quantity to inbound delivery |
(See following note) |
|
TBELI |
CHAR 1 |
Complete TR |
Set the source TR to "completed" on confirmation of TO |
|
ENAME |
CHAR 12 |
User name of the pick confirmation |
||
QUKNZ |
CHAR 1 |
Confirmation indicator for separate confirmation |
1 = Confirm stock removal only 2 = Confirm material transfer only |
<NOTE>
If you set the indicator KOMIM to 2, the IDoc can no longer be use for mass processing: If you want to post the goods issue for an outbound deliver via the IDoc, you can only transfer a single transfer order in the IDoc, for each IDoc and communication activity.
If you confirm a TO for an inbound delivery, indicator EINLM determines whether the putaway quantity is to be transferred to the inbound delivery and the goods receipt is to be posted.
This indicator acts in the same way as indicator KOMIM for the outbound delivery.
Segment definition E2LTCOI004: TO items (as of release 6.20)
Field |
Data Type |
Description |
Required Entry Field |
Note |
TAPOS |
CHAR 4 |
Transfer order item |
X |
|
SQUIT |
CHAR 1 |
Indicator: Confirm without difference |
X |
If the item is to be confirmed without any differences |
NISTA |
CHAR 15 |
Destination actual quantity |
X |
If there are differences in the destination storage bin |
NDIFA |
CHAR 15 |
Destination difference quantity |
X |
If there are differences in the destination storage bin |
RISTA |
CHAR 15 |
Return actual quantity |
X |
If there are differences in the destination storage bin |
RDIFA |
CHAR 15 |
Return difference quantity |
X |
If there are differences in the destination storage bin |
KZNUL |
CHAR 1 |
Indicator: Bin empty on zero stock check |
X |
If there is a zero stock check |
PISTA |
CHAR 15 |
Remaining quantity after zero stock check |
X |
If there is a zero stock check |
ALTME |
CHAR 3 |
Unit of measure |
X |
If quantity is entered |
KZDIF |
CHAR 1 |
Differences indicator |
X |
If you want to post differences to certain interim record for differences |
LENUM |
CHAR 20 |
Storage unit number |
X |
In case of confirmation in bulk storage |
VQUIT |
CHAR 1 |
Confirmation in bulk storage, removal of entire SU |
X |
In case of confirmation in bulk storage |
PICKM |
CHAR 15 |
Pick quantity for bulk storage confirmation |
|
|
DIFFM |
CHAR 15 |
Difference quantity in bulk storage |
|
|
RESTM |
CHAR 15 |
Remaining quantity on bulk storage confirmation |
|
|
BQUIT |
CHAR 1 |
Confirmation in bulk storage, no further items |
||
KZFOL |
CHAR 1 |
Indicator: Subsequent actions |
You can use this field individually, for example to trigger a user-defined process via a user exit. You can, for example, trigger a user-defined follow-up action for differences. |
|
NLPLA |
CHAR 10 |
Destination storage bin |
If the destination storage bin differs from that suggested by the system |
|
NPPOS |
CHAR 2 |
Destination position |
If the destination storage bin differs from that suggested by the system |
|
PAPOS |
NUMC 4 |
Current number of HU data row within TO item |
||
PARTI |
CHAR 1 |
Confirming a partial quantity for a TO item |
Only relevant for handling units (HUs) |
|
CHARG |
CHAR 10 |
Confirm batch number for lean WM or bulk storage |