Confirming Transfer Orders 

Transfer orders that have been executed can be reported to the SAP system using the IDoc WMTCID01 (WMTCID02 in Release 4.0). These are then confirmed in the SAP system.

The partner profile input must be maintained for the message type WMTOCO.

Not every transfer order must be confirmed, i.e. it is not always necessary to report the transfer orders sent. A customizing setting in the WM system specifies whether or not a generated transfer order is to be confirmed. This information is transferred with the field 'KZQUI' in the segment E2LTORI using the IDoc WMTOID01(WMTCID02 in Release 4.0). The confirmation requirement refers to the individual items and not to the entire transfer order.

The IDoc comprises three segments, namely E2LTCOX for confirming entire storage units, E2LTCOH for the transfer order headers and E2LTCOI for the TO item data.

A storage unit can, in the event of mixed storage, be moved with several transfer orders. Under normal circumstances, however, one transfer order with one item corresponds to one storage unit. The simplest solution is to confirm the entire storage unit (see version 1).

If you are working without storage unit management, simply confirm entire transfer orders (see version 2). This type of confirmation is usually used for stock removal. Item-by-item confirmation is recommended for stock placements if several pallets are placed into stock with one transfer order (see version 4).

If differences are established within a storage unit (e.g. picking from storage unit), confirm the entire storage unit with those items with differences (see version 5). Differences can also be entered explicitly for the individual items when the entire transfer order is reported (see version 3).

The following matrix indicates the various confirmation options. The individual segments of the IDoc are then described in more detail.

E2LTCOX = 1, E2LTCOH = 2; E2LTCOI = 3. These abbreviations also correspond to the hierarchical levels of the segments in the IDoc.

IDoc Set up for confirmation

Version

Segment

Number

Meaning

1

1

1

Confirm entire storage unit

2

2

1

Confirm entire transfer order

3

2

3

1

1... n

Confirm entire transfer order except for 1 to n items with difference

4

2

3

1

1 (... n)

Confirm one or several transfer order items

5

 

1

2

3

1

1... n

1... m

Confirm entire storage unit except for a number of transfer orders that have items with differences.

 

E2LTCOX relevant for version 1 and 5

Fields

Format

Designation

Req.

Comment

LGNUM

CHAR 3

Warehouse number

X

 

LENUM

CHAR 20

Storage unit number

X

 

QNAME

CHAR 12

User name for confirmation

 

 

SQUIT

CHAR 1

Flag: Confirm entire storage unit (actual = target)

X

Value "X"

NLPLA

CHAR 10

Dest. bin

  

See note below

NPPOS

CHAR 2

Dest. item

  

See note below

Nlpla and Nppos are the destination storage bin and the item in that bin. For this, the destination storage bin and item are referenced to the deviating destination storage bin of the entire storage unit.

 E2LTCOH relevant for version 2, 3, 4 and 5

Fields

Format

Designation

Req.

Comment

LGNUM

CHAR 3

Warehouse number

X

 

TANUM

CHAR 10

Transfer order number

X

 

QNAME

CHAR 12

User name for confirmation

 

 

SQUIT

CHAR 1

Flag: Confirm entire transfer order (actual = target)

x

If the entire transfer order is to be confirmed (version 2, 3 + 5)

KOMIM

CHAR 1

Copy pick quantities into the delivery / post goods issue (from Release 4.0)

 

 

EINLM

CHAR 1

Copy putaway quantity into inbound delivery

  

See note below

TBELI

CHAR 1

Closes TR

  

Sets the originating TR to "processing complete" when TO is confirmed

 

For confirming a TO created for an inbound delivery, the switch Einlm determines whether or not the putaway quantity will be copied into the inbound delivery document and the goods receipt posting will take place. It behaves like the KOMIM for the outbound delivery.

 

E2LTCOI relevant for version 3, 4 and 5

Fields

Format

Designation

Req.

Comment

TAPOS

CHAR 4

Transfer order item

x

 

SQUIT

CHAR 1

Indicator: confirmation of a transfer order item

x

If item is to be confirmed without difference

NISTA

CHAR 15

Dest.act.qty

x

If difference in destination storage bin

NDIFA

CHAR 15

Dest.difference qty

x

If difference in destination storage bin

RISTA

CHAR 15

Returned actual quantity

x

If difference in destination storage bin

RDIFA

CHAR 15

Diff.quantity for returned stock

x

If difference in destination storage bin

KZNUL

CHAR 1

Indicator: bin empty at zero stock check

x

If zero stock check

PISTA

CHAR 15

Remaining quantity after zero stock check

x

If zero stock check

ALTME

CHAR 3

Unit of measure

x

If any quantities are specified

KZDIF

CHAR 1

Difference indicator

x

If posting to interim record for differences is required

LENUM

CHAR 20

Storage unit number

x

If confirmation in block storage area

VQUIT

CHAR 1

Confirmation in block storage area: removal of complete SU

x

If confirmation in block storage area

PICKM

CHAR 15

Picking quantity for block storage confirmation

 

 

DIFFM

CHAR 15

Difference from block storage confirmation

 

 

RESTM

CHAR 15

Remaining quantity after block storage confirmation

 

 

BQUIT

CHAR 1

Confirmation in block storage area: no further items

 

 

KZFOL

CHAR 1

Indicator subseq.action

 

 

NLPLA

CHAR 10

Dest. bin

  

See note below

NPPOS

CHAR 2

Dest. item

  

See note below

Nlpla and Nppos are the destination storage bin and the item in that bin, in case the destination storage bin deviates from the bin suggested by the system. In the segment E1LTCOI the bin is referenced to one TO item.

  E2LTCOG

(You need this segment if you intend to enter planned and actual processing times for transfer orders.)

Fields

Format

Designation

Req.

Comment

LGNUM

CHAR 3

Warehouse number

 

 

TANUM

CHAR 10

Transfer order, for which the data is confirmed/verified

 

 

SOLEX

CHAR 15

Planned processing time from external system

 

 

PERNR

CHAR 8

Processor of the TO (personnel number)

 

 

STDAT

CHAR 8

Start date of the transfer order

 

 

ENDAT

CHAR 8

End date of the transfer order

 

 

STUZT

CHAR 6

Start time of the transfer order

 

 

ENUZT

CHAR 6

End time of the transfer order

 

 

ISTWM

CHAR 15

Actual processing time for the WM transfer order

 

 

AUSFB

CHAR 4

      

When you confirm transfer orders, the actual processing time of the TO can be reported to the system. The planned processing time for TO is normally determined in the SAP system, but it can also be amended by the planned processing time that is reported from the external system (SOLEX). The format in which the actual times can be reported is dependent upon the data transmitted in the transfer order IDoc (KZLEI and KISTZ).

 Actual data can be reported for KZLEI = 2, 3 or 4. This can take place independently of the actual confirmation by transmitting the E2LTCOG segment. Depending on the indicator KISTZ from the TO IDoc, the reporting can take place in the following form:

KISTZ = 1 => Fields: ISTWM, PERNR.

KISTZ = 2 or 3 => Fields: STDAT, STUZT, ENDAT, ENUZT, PERNR.

In this case, the unit from SOLEX and ISTWM is related to the time unit that is in the field ZEIEI in the TO IDoc.

 With KOMIM = 1, the pick quantities in the delivery item are adjusted when the TO is confirmed and, additionally, the goods issue is initiated with KOMIM = 2. The goods issue posting does not take place until all of the delivery items have been confirmed.

Important: If you want to initiate the goods issues for the delivery, only one transfer order per IDoc and communication process may be provided. KOMIM = 2 thus reduces the "mass" capability of the IDoc.

Goods Movements

There are a number of goods movements that must be discussed separately with regard to their confirmation.

  1. Reporting differences.

    2. If differences are detected when a goods movement is executed, these must be transferred by the external system in the segment E2LTCOI via the IDoc WMTCID01 when the movement is reported. The following fields must be sent:

    SQUIT

    Empty

    NISTA

    Actual quantity of the goods movement, i.e. the quantity that is actually moved or withdrawn

    NDIFA

    Difference quantity of the goods movement, i.e. the difference between the quantity transferred in the transfer order and the actual quantity

    RISTA

    Actual quantity for the return sub-item (only if return sub-item is present)

    RDIFA

    Difference quantity for the return sub-item

    ALTME

    Unit of measure to which the quantities refer (from the transfer order sent by the WM system)

    KZDIF

    If the storage type and storage bin for which the difference is posted, are to be overridden Versions 3, 4 and 5 must be used to report differences

    To report differences, versions 3, 4 and 5 must be used.

    As a rule, the entire target quantity of the respective TO item must be verified. This applies to E2LTORI-VSOLM:

    VSOLM = NISTA + NDIFA + RISTA + RDIFA. If a remaining quantity PISTA has been found, it is not entered here but specified separately.

  2. Reporting with zero stock check

    3. When stock is removed from a storage type with zero stock check, the storage bin that becomes empty as a result of the goods movement to be confirmed, must be reported explicitly.

    If an X is transferred in the field 'KZNKO' in the segment E2LTORI in the transfer order sent from the WM system, the zero stock check must be reported in the segment E2LTCOI in the IDoc WMTCID01. If the storage bin is empty after withdrawal has taken place, an X must be transferred in the field 'KZNUL'. If there is any remaining stock in this bin, the following fields must be transferred in the segment E2LTCOI:

    KZNUL

    Empty

    PISTA

    Counted remaining stock

    ALTME

    Unit of measure to which the quantities refer (from the transfer order sent by the WM system)

    If no zero stock check is requested by the WM system, the zero stock check can still be reported by the WM system if the storage bin is empty after withdrawal has taken place (stock in the system deviates from physical stock). The field 'KZNKO' in the segment E2LTCOI in the IDoc WMTCID01 must be set to 'X' in this case as well.

    Version 3 or 4 must be used when confirmations are made with zero stock check.

  3. Confirmation in the block storage area with storage unit management

When the transfer order is confirmed in the block storage area with storage unit management, the storage units that have been withdrawn must be reported.

If a storage unit that has been completely withdrawn is to be reported, the following fields must be transferred in the segment E2LTCOI:

LENUM

Number of the withdrawn storage unit

VQUIT

X

If the withdrawn storage unit is to be reported with the difference and/or remaining quantity, the following fields must be transferred in the segment E2LTCOI:

LENUM

Number of the withdrawn storage unit

'PICKM

Picking quantity

'DIFFM

Difference quantity

'RESTM

Remaining quantity

ALTME

Unit of measure to which the quantities refer (from the transfer order sent by the WM system)

Transmission of the confirmation from the external system can be simulated in the SAP system. We recommend that the confirmation procedures that are relevant for you be tested first in this way. You can use the report RLTOCO00 to test transfer order confirmations and the report RLTOCO10 for storage unit confirmations.

The field 'KZFOL' in the segment E2LTCOI can be used in accordance with the individual requirements of the customer.

The intention here is that customers use this indicator by means of a user exit in the WM system for their own purposes. It can be used, for example, to initiate follow-up actions in the event of differences. How this follow-up action is defined and executed is left entirely to the customer.