Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ MGW (Package) Application development R/3 material master Retail
Basic Data
Data Element | NO_APPL_LOG |
Short Description | Do Not Write an Application Log |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | NO_APPL_LOG | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | No log |
Medium | 15 | No appl. log |
Long | 20 | No application log |
Heading | 4 | NoAL |
Documentation
Definition
Use
Determines whether the messages that occur during data transfer are written to the application log. It is not possible to set this indicator when distributing data by ALE, where an application log is always written.
- Indicator set
The success or failure of processing is reported only in the parameter RETURN or in the IDoc's status record.
If the data transferred was processed successfully, the parameter RETURN or the IDoc's status record returns an S (success) type message.
If errors occurred during processing, the parameter RETURN or the IDoc's status record returns the first logged error as an E (error) type message.
- Indicator not set
All messages that occurred are stored in the application log. The parameter RETURN or the IDoc's status record returns the number of the application log and tells you whether the data was processed successfully or not.
Procedure
Examples
Dependencies
In data transfer, where it may be necessary to transfer very large quantities of data from a legacy system, setting this indicator can reduce the runtime because writing the application log can be a significant time factor.
The information in the application log is of help during the test phase in particular, since it indicates the cause of the error if problems occur. Once the data can be processed without errors, you can dispense with logging during the actual data transfer.
History
Last changed by/on | SAP | 19990421 |
SAP Release Created in |