Ansicht
Dokumentation

MWMTOAU3 - Separate selection of posting changes for autom.TO creation

MWMTOAU3 - Separate selection of posting changes for autom.TO creation

BAL Application Log Documentation   PERFORM Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

With this user exit you can select posting change notices for automatic TO creation according to your own criteria using the report RLAUTA11.

General information on automatic TO creation

Using the movement type, you can determine whether the TO creation for a posting change notice is to take place automatically in the background. These posting change notices are marked accordingly during the creation process (field AUTTA). On the basis of this indicator, the relevant posting change notices are selected by the report RLAUTA11, which must be planned as a batch job. Here you can use the relevant indicator for background processing to determine that an addition selection of posting change notices is to take place according to your own criteria.

Call position and important requirements

The user exit is called from the report RLAUTA11 if the indicator for automatic TO creation provides for a selection according to your own criteria. In the report RLAUTA11, all posting change notices with the respective indicator are preselected. The final selection of posting change notices takes place in this user exit. In the report RLAUTA11, the transfer orders are created for the selected posting change notices and, if required, you can have a log or error log generated and even send it to particular users via the mail function.

Parameters and options

The user exit in the program is the function module EXIT_RLAUTA11_003. To fill this with data, you must create the include ZXLATU03 and activate the user exit using Transaction CMOD. The selection criterion (import parameter I_BEAR2) and the preselected posting change notices (Tabellenparameter T_LUBU) are passed on as parameters. Within this table, the additional selection of posting changes must take place, that is, this table must contain all the transfer requirements for which transfer orders are to be created in the report RLAUTA11. Posting changes that are not relevant must therefore be removed from this table.






Fill RESBD Structure from EBP Component Structure   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 2240 Date: 20240329 Time: 125117     sap01-206 ( 66 ms )