Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-CCM-ADK (Application Component) Archive Development Kit⤷
S_ARCH_SEL_SCREEN_STANDARD (Package) Archiving: Standards for Selection Screens
Basic Data
| Data Element | ARCH_DETAIL_LOG |
| Short Description | Archiving/Data Destruction: Detail Log |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ARCH_DETAIL_LOG | |
| 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 | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Detail Log |
| Medium | 15 | Detail Log |
| Long | 20 | Detail Log |
| Heading | 20 | Detail Log |
Documentation
Definition
Choose No Detail Log, if you want to see a summary of the processed objects.
Choose without Success Message, if you want a detail log without success messages.
The success messages generally make up the bulk of the detail log. This option allows you to see the other messages completely without the log getting too large.
Choose Complete, if you want to see a full detail log, which will contain all processed objects including their corresponding messages.
Only generate detail logs for small amounts of data, for example if you are working in the test mode and you are processing few objects. Otherwise the program may terminate, because the load on the memory is too large.
Independent of which kind of detail log you have chosen, the program will produce a summarized log. This contains every message only once. In addition it lists the number of affected objects and one of these objects as an example.
Use
Dependencies
Example
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 630 |
