General information about transfer order processing

Transfer order processing and confirmation in the WM system are divided into the following programs:

1. SAPML03T Screens, transactions
2. SAPLL03A Item creation (TO core)
3. SAPLL03B Function modules for external purposes
4. SAPLL03T Update tasks

These four programs work together as follows:

SAPML03T contains all the transfer order processing screens. All related transactions are initiated using screens from this program. All corresponding data is read, checked and recorded here (transportation requirements in transfer order: transportation requirements, transfer order: confirmation, etc.)

Actual creation or confirmation of items occurs via function modules in SAPLL03A , where the transfer orders are first created and recorded internally as the putaway and picking strategies and several checks are run. Changes in storage location, storage unit or stock that may arise from individual transfer order items are simulated in internal tables.
Item creation and confirmation occurs in two steps. First, the item is generated internally and all checks are carried out. Then, the internal tables are updated via a second function module and the transfer order items are added internally. You can view this two-step process by running transfer order creation in the foreground (screen SAPML03T 102). First, the system generates the transfer order item, then issues a warning. If entries are made on the screen, the system regenerates the transfer order item (including all checks) and the previous one is discarded. The internal tables are updated after the warning disappears.
The confirmation process follows a similar procedure.

User action 'post' in SAPML03T is carried out after an item is created or confirmed, which in turn calls up function module SAPLL03A , which then activates the update function modules in SAPLL03T. These function modules are normally processed asynchronously (supplement IN UPDATE TASK), but can also occur synchronously (see below). All changes in storage location, storage unit, stock, transportation requirements or transfer orders are made in these function modules.

SAPLL03B contains function modules for creating and confirming transfer orders which can be used instead of transactions. First, the normal screen run of the parameters transmitted is reviewed. Reading, checking and recording of the data and part of the flow logic occurs via external performs in SAPML03T and in a common data area, to avoid redundant code. Item creation and confirmation takes place in function modules found in SAPLL03A.
Function modules L_TO_CREATE_TR and L_TO_CREATE_DN, for example, are used in collective processing in the SAP standard system. Updating occurs synchronously in this case.

Transactions in SAPLL03A and SAPML03T

Some checks within the transfer order creation and confirmation processes depend on the transaction concerned. This transaction (field VORGA) is placed at the disposal of all user exits so that the system can react as required for the transaction involved.

Relevant values:

1. "TB" Transfer order for transfer requirement
2. "LF" Transfer order for delivery note
3. "TL" Transfer complete storage unit

Homogeneous storage units can also be transferred explicitly. In this case, the value of the field is LTAP-HOMVE = 'X'.

1. "IV" Clear inventory
2. "U1" Create first item for posting change
3. "U2" Create second item for posting change
4. "QB" Confirm storage unit for stock removal from SU-managed block storage area

Within the SU-managed block storage ares, the item type (POSTY) of a TO item is of interest. It is set when the source data is determined and can have the following values:

1. " " Normal transfer order item
2. "1" Quant-neutral stock removal that requires verification of storage units during the confirmation process
3. "2" Storage unit verified during confirmation

Items with item type "1" are deleted as soon as confirmation is complete.

Call transaction and other important requirements

In order to remove a certain quantity of a material from stock (starting from the preparation screen for the stock removal), TO items are created iteratively until requested quantity is met. Sometimes (for example, During the stock removal of quantities that cannot be split up, such as barrels or bales), it is useful to cancel this process before the requested quantity is reached.
The user exit is performed after the successful creation of (almost) every TO item starting from this preparation screen. If storage bins are entered manually on this screen or by picking them up from the stock list, the user exit will only be performed when the last of these items has been created. Only abend or system messages should be sent within the function module. Error messages or warnings messages are generally not useful because at this time no fields are ready for input on the screen.

Parameters and options

The user exit in the program is function module EXIT_SAPML03T_001. In order to be able to use the user exit, you must create Include ZXLTOU11 and activate the enhancement with transaction CMOD.
The following parameters are available:

Import parameters

1. I_AUSML The entire quantity of this material that is to be removed
2. I_OFFML The open quantity that has not yet been scheduled
3. I_SUMTL The quantity for which TO items have already been created

All three quantities refer to the base unit of measure. I_AUSML generally equals the total of I_OFFML and I_SUMTL, unless an item exists on the preparation screen for which the TO creation was cancelled. These three quantity fields are relevant if active ingredient processing is not active (I_LTAP-WIRME is set to its initial value).

1. I_AUSME The entire quantity of this material that is to be removed
2. I_OFFME The open quantity that has not yet been scheduled
3. I_SUMTM The quantity for which TO items have already been created

All three quantities refer to the base unit of measure. I_AUSME generally equals the total of I_OFFML and I_SUMTL, unless an item exists on the preparation screen for which the TO creation was cancelled. These three quantity fields are relevant if active ingredient processing is active (I_LTAP-WIRME is not set to its initial value).

1. I_LTAK The respective TO header that contains, for example, the reference documents such as transfer requirement number or the like. Please refer to the interface documentation of function module L_TO_PREPARE_ITEM_INT for more information on the filled fields in I_LTAK.
2. I_LTAP The last created TO item
3. I_MLVS Material master
4. I_MGEF Hazardous material master
5. I_T333 Movement type with which the TO is created
6. I_T340D Warehouse number control
7. I_VORGA Transaction within the TO processing

Export parameters

1. E_EXIT E_EXIT = 'X' cancels the item creation for this material. Otherwise, it is continued.

Table parameters

1. T_LTAPA Table of the items that are displayed on the preparation screen. This table must not be changed. It contains the most important information on the TO items for this material that have already been created. Items for which the TO creation was cancelled are indicated with T_LTAPA-XTAPS = ' '. Items for this material that refer to transfer requirement or delivery note items other than the current one are not contained in the table.

Information on the status of transfer order processing

Using the function module L_TO_CREATE_GET_INFO you can obtain information on the current status of transfer order processing. In addition to Table TAP with the transfer order items already created, you can use the following tables: PSPERR, LSPERR, QSPERR and SSPERR. These tables contain the storage bins, storage units and quants affected by the transfer order. However, the contents of the more important fields do not match the status in the database. Instead, they appear as if the transfer order items created up to now have been posted. The update of the item currently being posted is not included in the table.

If, for example, a bin is read in the user exit, we recommend that you have the system first check in Table PSPERR and then, only if data access is unsuccessful, to read the database. If this is not possible (for example, the bin is read by the index for empty bins), a bin that has been read should still be compared with Table PSPERR.

The only exception to this rule is a quant affected by blocking logic B. In this case, QSPERR has the status that would exist on the basis of the current transfer order. Changes that arise from parallel transfer orders are only partially included. If, for example, transfer orders 1 and 2 (in this sequence) access the same quant and the respective items have already been created internally, QSPERR contains the stock of transfer order 1 minus the current item and for transfer order 2 the stock is minus both items. Therefore, to have the current stock in each case, the database stocks must be compared with the global blocking table (blocking object ELLQUAY via function module "ENQUEUE_READ" read and evaluate). Whether or not this exact stock reading is required should be decided in each individual case.

The following example of a stock removal via user exit may be of help in making this decision:

Bin stock database: 10 pieces
TO 1 removes 5 pcs and first creates the item internally
TO 2 wants to have 10 pcs removed from stock.

The user exit also decides on this bin. The quant is not in the internal table because no internal item yet exists. Irrespective of whether the user exit proposes the bin with a stock of 5 pcs or 10 pcs, transfer order 2 (providing there is a positive stock balance) would at most take 5 pieces and would try to supply the remaining 5 pieces by means of a further item. Within the user exit, the correct stock is not important for the stock removal to be "correct". It is only important if it affects a decision, that is, if the user exit proposes another bin because only 5 pieces could be removed from the first bin.

Table IBDBATCH is available for you to create your own stock removal strategy. This table is important for batch-neutral documents if you want your own stock removal strategy to be influenced by the standard batch search function.

All the above tables are predefined for the user exit. If the system is to access one of these tables within the user exit, the current version must be called up via the function module L_TO_CREATE_GET_INFO. The following example shows you how to call up Tables PSPERR, QSPERR and TAP. The other two tables are not of importance because there is no SU management involved:

The table parameters must always be specified; only the marked tables (with "X") are copied.

Table IBDBATCH can only be called up by user exits from SAPLL03A. Otherwise the content is undefined.

• EXIT_SAPML03T_001: Underdelivery With Customer Exit