Functionality
With this function module you can confirm a transfer order orindividual items of a transfer order. It is also possible to confirmstorage units that have been removed from block storage or to executethe zero stock check. For more information, refer to the detaileddocumentation of the individual parameters. The parameters that arepassed on are first submitted to a plausibility check. Then the actualconfirmation takes place.
If you only set the exception ERROR_MESSAGE when calling thefunction module, the system only reacts to error messages andtermination messages during confirmation. The system ignores thefollowing messages unless they are covered explicitly by one of theexceptions:

• S (Success)


• I (Information)


• W (Warning)

Further information
For the most part, this function module behaves in the same way as thetransaction used to confirm a transfer order. If the information inthe detailed documentation for the individual parameters is notsufficient, you can find additional information in the F1 help for theindividual fields.

Description
If I_COMMIT_WORK is set, the COMMIT WORK occurs within the functionmodule, otherwise the calling program is responsible for the COMMIT.
INCLUDE MM_WM_COMMIT

Description
If I_SQUIT is set, all open TO items for a transfer order, which werenot explicitly transferred in T_LTAP_CONF, are confirmed withoutdifferences. This can lead to errors if items with zero stock check, orwithdrawals from storage unit managed bulk storage are contained inthis 'remaining quantity', since these items must be confirmedexplicitly via T_LTAP_CONF.

Description
I_SUBST controls the reaction to subsystems. If I_SUBST is set ('X'),these items are confirmed. Otherwise they remain unconfirmed.

Description
If I_UPDATE_TASK is set, the data is updated asynchronously via theupdate task, otherwise directly online.
INCLUDE MM_WM_COMMIT

Description
Data for explicitly confirming a TO item.
The following data must always be filled:


• TANUM: Transfer order number


• TAPOS: Transfer order item

There are seven different cases.
RESET N1
Confirmation of an item without differences.
The following field must also be filled:
SQUIT: confirm target = actual
Confirmation of an item with difference.
The following fields must also be filled:
NISTA: Subsequent actual quantity
NDIFA: Subsequent difference quantity
ALTME: Unit of measure upon which the quantities are based
RISTA: Return actual quantity (only for existing return items)
RDIFA: Return difference quantities (only for existing return items)
KZDIF: Difference indicator
Confirmation of a storage unit during withdrawal from SU-managed bulkstorage.
The following fields must also be filled:
LENUM: Storage unit number
VQUIT: Removing the complete quant or storage unit (if homogeneous)
LQNUM: Quant number (only necessary for mixed pallets)
PAPOS: Current number (only necessary for handling units). Togetherwith TAPOS, this serves as a pointer to the HU data records in tableT_LTAP_CONF_HU that belong to the TO items.
Confirmation of a storage unit with difference quantities and/orremaining quantities during withdrawal from SU bulk storage.
You must also fill the following fields:
LENUM: Storage unit number
PICKM: Pick quantity
DIFFM: Difference quantity
RESTM: Rest quantity
KZDIF: Difference indicator (only for difference quantities > 0)
ALTME: Unit of measure upon which the quantity is based
LQNUM: Quant number (only necessary for mixed pallets)
PAPOS: Current number (only necessary for handling units). Togetherwith TAPOS, this serves as a pointer to the HU data records in tableT_LTAP_CONF_HU that belong to the TO items.
'Declare finished' a withdrawal from SU-managed bulk storage.
The following field must also be filled:
BQUIT: No further confirmations for withdrawal from SU-managed bulkstorage
Confirmation of batches or consignment in lean WM without difference
The following fields must also be filled:
SQUIT: Confirm target = actual
CHARG: Batch
SOBKZ: Special stock indicator (K)
SONUM: Special batch number (vendor)
PAPOS: Current number (not necessary for handling units). Together withTAPOS, this serves as a pointer to the HU data records in tableT_LTAP_CONF_HU that belong to the TO items.
Confirmation of several batches, or consignment or confirmation withdifference in lean WM.
The following fields must also be filled
NISTA: Subsequent actual quantity
ALTME: Unit of measure upon which the quantity is based
KZDIF: Difference indicator
CHARG: Batch
SOBKZ: Special stock indicator (K)
SONUM: Special stock number (vendor)
PAPOS: Current number (only necessary for handling units). Togetherwith TAPOS, this serves as a pointer to the HU data records in tableT_LTAP_CONF_HU that belong to the TO items.
Optionally, zero stock check can be predefined for confirmation of anormal item (regardless of whether with or without difference).
The following fields can also be filled:

• KZNUL: Bin is empty (manual or automatic zero stock check)


• PISTA: Remaining quantity in bin (only for automatic zero control
check)

• ALTME: Unit of measure upon which the quantity is based


• KZDIF: Difference indicator (only for difference)

Only KZNUL or PISTA can be set
Optionally, the putaway storage bin can be changed during putaway ifpredefined in Customizing.

• NLPLA: New destination storage bin for the relevant TO items


• NPPOS: Item in the new destination storage bin for strategy P

As far as the possibilities for changing the destination storage bin onconfirmation is concerned, there are many restrictions. If storageunits are involved, the parameter can only be set in one table entryper SU. Alternatively, you can enter it directly via function moduleL_TO_CONFIRM_SU.
TO item split during confirmation
Optionally, you can split a TO item during confirmation into two ormore items. In doing so, one or more new TO items (referred to here assplit items) are added to the TO items that already existed (referredto from here on as original items). The quantity in the original itemis thus reduced accordingly.
If you confirm TO items in a two step process, note that the TO itemcan only be split in the first confirmation step.
So that a TO item can be split, certain prerequisites must be met.There are basically two possible scenarios:

• The TO item is based on a storage location where handling unit
management is active (in this case the data field FHUTA is not blank inthe TO item) or

• The TO item is based on a storage location where HU management is not
active (in this case the data field FHUTA is blank in the TO item).
Split where HU management is active:
So that a TO item can be split, the following prerequisites must bemet:

• The destination quant should not yet be updated on creation of the TO
item. The destination quant is updated when the TO is created if thedestination storage type has a putaway strategy that is not SPACE, "R",or "C", or if a capacity check is activated in the destination storagetype. In these cases, the TO item cannot be split. Otherwise thedestination quant is split if the destination quant or the destinationstorage unit is manually specified during TO creation.

• For some processes, splitting the TO item cannot be split. These
include inventory TOs, TO items that are based on a posting changenotice, or TO items that were created on the basis of an HU repackingprocess.

• Splitting TO items is also not possible when putting away handling
units.
Split for non-active HU management:
In this case, splitting a TO item is basically only possible if the TOis based on an outbound delivery and if the Pick&Pack switch isactivated in the Customizing for the warehouse number. Likewise in thiscase, the TO item can only be split if the destination storage type hasthe putaway strategy SPACE, R or C, and no capacity check is activatedin the destination storage type. The destination quant must not bespecified during TO creation.
Procedure:
To create one or more split items for a TO item, an entry must be madein table T_LTAP_CONF for every split item. In doing so, the followingfields must be filled:

• TANUM: TO number


• TAPOS: Number of the TO item


• NISTA: Quantity that is to be split from the original item


• ALTME: Unit of measure


• PAPOS: Pointer to the HU packing data in table T_LTAP_CONF_HU that
belongs to this item.

• PARTI: Indicator split item (must be set to "X" for split items)

You must not fill any other fields. (In particular, you must not enterany difference quantities. Difference quantities may only be enteredfor the original item.)
Special case: SU-managed bulk storage
In this case the following fields must be filled:

• TANUM: TO number


• TAPOS: Number of the TO item


• LENUM: Number of the storage unit


• PICKM: Pick quantity


• ALTME: Unit of measure, upon which the pick quantity is based


• LQNUM: Quant number (only necessary for mixed pallets)


• PAPOS: Current number (not necessary for handling units). Together with
TAPOS, this serves as a pointer to the HU data records in tableT_LTAP_CONF_HU that belong to the TO items.

• PARTI: Indicator split item (must be set to "X" for split items)

You must not fill other fields.
Special case: Confirmation of batches or consignment in lean WM
In this case, the following fields must be filled:

• TANUM: TO number


• TAPOS: Number of TO item


• CHARG: Batch


• SOBKZ: Special stock indicator (K)


• SONUM: Special stock number (vendor)


• PAPOS: Current number (not necessary for handling units). Together with
TAPOS, this serves as a pointer to the HU data records in tableT_LTAP_CONF_HU that belong to the TO items.

• NISTA: Subsequent actual quantity


• ALTME: Unit of measure upon which the subsequent actual quantity is
based

• PARTI: Indicator split item (must be set to "X" for split items)

You must not fill any other fields.
Example
A TO item (not lean WM and not SU-managed block storage) with TANUM1234 and TO item number 5 is to be split. The subsequent targetquantity in the TO item is 15PC. After confirmation, there should bethree items available with the subsequent actual quantities 3ST, 4STand 6ST: The confirmation should be transferred with a differencequantity of 2PC.
Table T_LTAP_CONF is filled as follows:
TANUM ,,TAPOS ,,NISTA ,,NDIFA ,,ALTME ,,PARTI,, ,,PAPOS
1234,,5,,3,,,,PC,,X,,,,1
1234,,5,,4,,,,PC,,X,,,,2
1234,,5,,6,,2,,PC,,,,,,3
The first two entries make sure that the split items (PARTI = X) arecreated with the quantities 3 and 4 PC. The original item (PARTI =SPACE) is confirmed with the last entry. Note that differencequantities may only be confirmed with the original item.
Confirming a partial quantity:
It is possible to create split items for a TO item without confirmingthe original item at the same time. This means that it is possible toconfirm partial quantities for a TO item. In this case, entries for theTO item to be confirmed are only entered in table T_LTAP_CONF, if theindicator PART is set to X. Make sure that the sum of the quantity issmaller than the subsequent target quantity in the original item. Onconfirmation, only split items are created. The original item remainsan open TO item with the corresponding reduced subsequent targetquantity and can be confirmed at a later time.

Description
For each TO item, the table contains information on the quantity of thematerial that was removed, from which handling unit it was removed, andin which handling unit the material was packed. You can enterdifference quantities here too.
Exactly when you need to provide entries for this table depends onwhether the TO item is based on a storage location with or without HUrequirement.
Storage location without HU requirement:
You should only fill this table if the TO item is based on an outbounddelivery and the Pick&Pack flag is activated in the warehouse number.In all other cases, you should not fill the table.
Storage location with HU requirement:
You should generally fill the table. If you are working with two-stepconfirmation, you should not fill the table if the first confirmationstep (confirmation of the material withdrawal) has already occurred forthe TO item.
If there are no entries in the table for a TO item which is concernedwith handling units, the function module tries to determine the HU dataautomatically. In the following cases this is not possible:
There is a transfer order in lean WM,
There is a withdrawal from SU-managed bulk storage, or
The storage unit or handling unit, from which the withdrawal is to bemade, is a nested handling unit.
The following data fields must always be filled:


• TANUM: Transfer order number,


• TAPOS: Transfer order item,


• VONHU: Handling unit or lower level handling unit from which the stock
is removed, or which itself is removed. If the stock is removed from astorage location that is not HU-managed, do not fill this field.

• NACHU: Number of the destination handling unit.


• MENGA: Material quantity that will be removed


• ALTME: Corresponding unit of measure

You can optionally fill the following fields:

• HUENT: If the indicator is set, the source handling unit is transferred
to the destination handling unit. Otherwise only the material istransferred to the handling unit. You should only fill this field ifthe storage location has HU requirement.

• DMGEA: Difference quantity (only for differences and only if the
storage location is HU required)

• PAPOS: Together with TAPOS, serves as a pointer to the corresponding TO
items. This must always be filled if the same field is filled in thecorresponding TO items in table T_LTAP_CONF.

Description
The table contains the serial number taken from a handling unit. Youonly have to fill the table if
The TO item is concerned with handling units,
There is no serial number requirement for the material, and if
Only a partial quantity of the material is removed from a handlingunit.
You must enter the following data:


• TANUM: Transfer order number


• TAPOS: Transfer order item


• VONHU: Number of the source handling unit


• NACHU: Number of the destination handling unit


• SERNR: Serial number


• PAPOS: Only has to be filled if the corresponding field in table
T_LTAP_CONF_HU is filled.