When material master data is transferred/distributed, the system logs the messages occurring during material data processing in the application log.
Especially during initial data load with which very large datasets are transferred to the R/3 system, writing the messages in the application log represents a not inconsiderable period of time.
The information in the application log is quite helpful especially in the test phase in order to get a hint on the error cause when problems occur.
If the IDocs can be posted without errors after the test phase, the information logged is not so important.Therefore, the thing to do is to deactivate the message logging for the time of initial data load.
This note describes the changes which must be executed so that no application log is written during initial data load.Nevertheless, if errors still occur when processing IDocs, the error first occurred is stored in the status record (Status 51) of the IDocs.Using variable WRITE_NO_APPL_LOG it is very easy to switch between the two variants (with/without application log):
DATA: WRITE_NO_APPL_LOG TYPE C VALUE ' '.
The variant with application log is active
DATA: WRITE_NO_APPL_LOG TYPE C VALUE 'X'.
The variant without application log is active
As of Release 4.7, application logs can be created in the receiving system via Customizing (Transaction OMT0).