IDoc for Creating and Canceling Transfer Requirements
Definition
Using IDoc WMTRID01, you can send data on
transfer requirements from the external system to the Warehouse Management system (WMS), so that the WMS can create TRs on the basis of the data. You can also use the IDoc to cancel TRs that have already been created in the WMS.We recommend simulating construction and sending of the IDocs to the WMS in order to test the relevant activities. Report RLTREQ00 is available for the test.
Use
Creating Transfer Requirements
Take the following into account when creating transfer requirements via IDoc WMTRID01:
Segment E1LTRQH (IDoc header data)
Field |
Note |
TBNUM |
You do not transfer the TR number, since the WMS issues the TR number |
BETYP |
You transfer this field if the movement type used expects a requirement number, in order to generate the link to the initiator of the stock movement. |
BENUM |
You transfer this field if the movement type used expects a requirement number, in order to generate the link to the initiator of the stock movement. |
VLTYP |
You use this field to define the source of the stock movement. |
VLPLA |
You use this field to define the source of the stock movement. |
NLTYP |
You use this field to define the destination of the stock movement. |
NLPLA |
You use this field to define the destination of the stock movement. |
PDATU |
You define when the TR should be converted to a TO. |
PZEIT |
You define when the TR should be converted to a TO. |
LZNUM |
To keep the TR clearly identifiable from the point of view of the external system, the external system assigns a reference number and transfers this to the WMS. You can only cancel TRs in the WMS from the external system via a unique reference number. |
TBRUE |
This field is designed for customer modifications in case confirmation of processed TRs to the external system is required. |
E1LTRQI (IDoc item data)
Field |
Note |
ABLAD |
You define the destination of the goods movement for individual items in the TR. |
WEMPF |
You define the destination of the goods movement for individual items in the TR. You generate a transfer requirement (TR) in order to stage several materials for a production order within production. You define the production storage type in the transfer order header. However, you define the work center where the material is to be staged for each individual TR item. You enter the individual work centers in field WEMPF. |
WENUM |
You use this field if you want to send notification of a goods receipt or plan a goods receipt with the TR. |
WDATU |
You use this field if you want to send notification of a goods receipt or plan a goods receipt with the TR. |
Canceling Transfer Requirements
Take the following into account when canceling transfer requirements (TRs) via IDoc WMTRID01:
E1LTRQH (IDoc header data)
Field |
Note |
LGNUM |
Required entry |
LZNUM |
Required entry |
E1LTRQI (IDoc item data)
Field |
Note |
TBPOS |
The external system does not transfer any TR item numbers during creation of TRs in the SAP system. The SAP system assigns the TR item numbers on creation of the TR. The system cancels TRs item by item. The external system must therefore transfer the TR item number of the TR item that is to be cancelled. If the number is know in the external system, the entire quant ID of a TR item must be transferred to the SAP system with the IDoc. In this case, you must fill fields MATNR, BESTQ, CHARG, SOBKZ and LSONR. |
ELIKZ |
This indicator must be set if the TR item is to be completely cancelled. If you only want to cancel a partial quantity of the item, transfer the quantity to be cancelled. To increase the quantity of an item, transfer a negative quantity for cancellation. You transfer fields MENGE and MEINS. |
Structure
Message Type
You define message type WMREQ for the inbound partner profile.
Segments
IDoc WMTRID01 is made up of two segments:
Segment definition E2LTRQH (as of release 3.0A)
Field |
Data Type |
Description |
Required Entry |
Note |
LGNUM |
CHAR 3 |
Warehouse number |
X |
|
TBNUM |
CHAR 10 |
Transfer requirement number |
||
TRART |
CHAR 1 |
Transfer type |
||
TBPRI |
CHAR 1 |
Transfer priority |
||
TBKTX |
CHAR 40 |
Transfer requirement header text |
||
BNAME |
CHAR 12 |
User name |
||
BETYP |
CHAR 1 |
Requirement type |
||
BENUM |
CHAR 10 |
Requirement number |
||
BWLVS |
CHAR 3 |
Movement type Warehouse Management |
X |
|
VLTYP |
CHAR 3 |
Source storage type |
||
VLPLA |
CHAR 10 |
Source storage bin |
||
NLTYP |
CHAR 3 |
Destination storage type |
||
NLPLA |
CHAR 10 |
Destination storage bin |
||
PDATU |
CHAR 8 |
Date of planned execution |
||
PZEIT |
CHAR 6 |
Time of planned execution |
||
LZNUM |
CHAR 20 |
Additional reference number |
X |
On cancellation |
TBRUE |
CHAR 1 |
Indicator: Confirm transfer requirement |
||
KTBAE |
CHAR 1 |
Indicator: Cancel transfer requirement |
X |
On cancellation |
Segment definition E2LTRQI002 (as of release 4.6C)
Field |
Data Type |
Description |
Required Entry |
Note |
TBPOS |
CHAR 4 |
Transfer requirement item |
||
MATNR |
CHAR 18 |
Material number |
X |
|
WERKS |
CHAR 4 |
Plant |
X |
|
BESTQ |
CHAR 1 |
Stock category in warehouse |
X |
If stock has category |
CHARG |
CHAR 10 |
Batch number |
X |
If material is subject to batch management |
SOBKZ |
CHAR 1 |
Special stock indicator |
X |
If special stock |
LSONR |
CHAR 24 |
Special stock number |
X |
If special stock |
MENGE |
CHAR 15 |
Transfer requirement quanitity |
X |
|
MEINS |
CHAR 3 |
Unit of measure |
X |
|
WEMPF |
CHAR 12 |
Goods recipient |
||
ABLAD |
CHAR 25 |
Unloading point |
||
WENUM |
CHAR 10 |
Goods receipt number |
||
WDATU |
CHAR 8 |
Goods receipt date |
||
ZEUGN |
CHAR 10 |
Certificate number |
||
ELIKZ |
CHAR 1 |
Indicator: Final delivery |
||
VFDAT |
CHAR 8 |
Shelf life expiration date |
X |
If there is a SLED requirement |
LGORT |
4 R |
Storage location |
||
L2SKR |
1 R |
Relevance for two-step picking |
Can have value ‘2’ or ‘blank’ |
|
MATNR_EXTERNAL |
CHAR 40 |
Long material number (future development) for field MATNR |
||
MATNR_VERSION |
CHAR 10 |
Version number (future development) for field MATNR |
||
MATNR_GUID |
CHAR 32 |
External GUID (future development) for field MATNR |
The external system may also have to transfer other data, as well as the required entries. The extent of the IDoc data that is required depends on the type of requirement (for example, putaway from production or staging for production) and above all on the entries and settings in the WMS.