IDoc for Receiving TOs from an External System (SAP Library

IDoc for Receiving TOs from an External System

Definition

You use IDoc WMTOID01 or WMTOID02 to send transfer order relevant data from the external system to the Warehouse Management system (WMS).

Note

The following describes IDoc WMTOID02 only.

Use

The external system triggers warehouse movements in a warehouse type and executes the physical transportation of materials. Only then does the external system transfer the data on the warehouse movements to the WMS.

You construct IDoc WMTOID02 in the external system, in order to transfer the warehouse movement data to the WMS. The WMS receives the IDoc and creates a TO from it, in order to execute the physical warehouse movements and post the storage bins involved. The WMS creates a transfer order from the IDoc data it has received and immediately confirms it.

You can also create transfer orders with incomplete entries in the external system and send these to the WMS. In this case, the WMS, as leading system, adds the missing entries (for example, the coordinates of the destination storage bin) and sends the complete TO back to the external system. The external system confirms the TO, completing the warehouse movement.

Structure

Message Type

You define message type WMTORD for the inbound partner profile.

Segments

IDoc WMTOID02 is made up of the following segments:

E1LTOIRH (transfer order header)
E1LTOIRI (transfer order items)
E1LPHUX (pick handling unit)

For more information in segment definition, see IDoc for Sending TOs to an External System.

The external system may sometimes have to transfer additional data other then the segment fields which are indicated as required entry fields. The extent to which this is the case depends on some of the Customizing settings in Warehouse Management. For example, these can include:

Entry	Effect on the IDoc
The movement type for putaway determines the destination storage type and the source storage type.	You must not transfer the source data (source storage type, source storage area, and source storage bin) in segment E1LTORI. However, you must enter the destination data with the destination storage type and destination storage bin.
The movement type determines a stock removal in a dynamic interface, which corresponds to the cost center.	Segment E1TORI must contain the source storage type and the source storage bin. To determine the dynamic interface, segment E1LTORI must contain requirement type K and the requirement number of the cost center assigned to the account.
The movement type determines a stock transfer within a warehouse number	Segment E1LTORI contains a source storage type and source storage bin, and also a destination storage type and destination storage bin.
The movement type requires the goods receipt date during putaway.	Segment E1LTORI must contain the goods receipt date.
The movement type or the storage types involved in the IDoc allow a return transfer.	If a return transfer has taken place, segment E1LTORI contains the return transfer date.
A storage type is SU-managed.	If you add stock to an SU in this storage type, segment E1LTORI contains the SU number in field NLENR. If you pick from an SU in this storage type, segment E1LTORI contains the SU number in field VLENR. If you transfer a material quantity from an SU in this storage type to another SU, segment E1LTORI contains both SU numbers. If you transfer a material quantity from an SU in this storage type to another SU, segment E1LTORI contains both SU numbers. If you move a complete SU, use IDoc WMSUID01 for the transfer.

Recommendation

Only use movement types for this IDoc, which allow immediate confirmation. Usually, the physical warehouse movement has already taken place when you receive information on a transfer order from the external system in the WMS.