Hierarchy
⤷ BC-CCM-MON-SHM (Application Component) IMS: Agents and related topics
⤷ SAPWL_TOOLS (Package) SAP Workload Analysis: Various Programs
Basic Data
Data Element | CHAR1_ALV |
Short Description | Single-Character Flag |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR1 | |
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 | 0 | |
Medium | 0 | |
Long | 0 | |
Heading | 0 |
Documentation
Definition
Test Mode
If you choose this option, the cross-archving object check or deletion program is performed in test mode. This means that a simulation of the check or deletion is performed in accordance with your selection criteria. The result of the test run, that is, for example, whether a Business Object is archivable or deletable is not stored persistently in a database table.
The application log, which you can call from the initial screen for the cross-archiving object checking and deletion provides information about how many Business Objects can acutally be deleted or deleted. If you are satisifed with the test result, you can then perform the check or deletion in productive mode.
Zum Testen empfehlen wir, möglichst keine Massendaten zu verwenden, weil dies die Performance der Programme stark beeinträchtigen würde.
Productive Mode
If you choose the option, the cross-archiving object check or deletion program is performed in productive mode; that is, actually performed. With the check, the result is written as a status change in a database table. The subsequent write or delete program evaluates this table and can therefore select all and write to archive files or delete all Business Objects with a certain status.
Use
Dependencies
Example
History
Last changed by/on | SAP | 20041219 |
SAP Release Created in | 700 |