Processing TOs using Function Modules

Processing TOs using Function Modules

You can create, confirm and change transfer orders in Warehouse Management using the function modules listed below.

The online transfer order processing is divided into three reports.

Report SAPML03T contains all the screens and tasks necessary to process external documents.

Function group L03A contains essential internal data for creating and confirming transfer orders and calls up the update program. The function modules from group L03A are for internal use only, and are therefore not released to customers.

Function group L03B contains function modules that you should use instead of batch input or CALL TRANSACTION USING, since they are considerably easier to manage.

The following function modules are available for WM:

Function Modules for Transfer Orders

Use...	to...
L_TO_CREATE_SINGLE	Create a transfer order with one item
L_TO_CREATE_MULTIPLE	Create a transfer order with two or more items
L_TO_CREATE_MOVE_SU	Create a transfer order to move a storage unit
L_TO_CREATE_MOVE_LSR	Initiate a stock transfer of storage units from an external system
L_TO_CREATE_TR	Create a transfer order for a transfer requirement
L_TO_CREATE_DN	Create a transfer order for a delivery
L_TO_CONFIRM	Confirm a transfer order
L_TO_CONFIRM_SU	Confirm a transfer order for a storage units
L_TO_CANCEL	Cancel a transfer order
L_TO_CANCEL_SU	Cancel a transfer order for a storage unit
L_REF_CREATE	Create transfer orders using multiple processing
L_TO_CREATE_2_STEP_PICKING	Create transfer orders for 2-step picking
L_TO_CREATE_POSTING_CHANGE	Create transfer orders for posting changes

For more information, please refer to the documentation in the individual function modules.

Further Instructions

It is possible to post data in the system without running COMMIT WORK from the function module.

The system posts the data using synchronous data updates via SET UPDATE TASK LOCAL. This means that the data is not posted and the system also cannot read from your own follow-on programs until the program reaches COMMIT WORK. A database COMMIT will not work to start the posting; instead, you must use the ABAP command COMMIT WORK.

Due to the resulting delayed posting, you cannot call up several function modules from the group L03B without having a COMMIT between them. This could result in data inconsistencies, for example, because the same empty storage bin or the same stock might be used in consecutive transfer orders.