Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-BW-SRV (Application Component) BW Generation Tool and Set Object⤷
SBIS (Package) Multidimensional Set Object
Basic Data
| Data Element | RSMDS_CHAR9 |
| Short Description | Character Field of Length 9 |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | CHAR | Character String |
| Length | 9 | |
| Decimal Places | 0 | |
| Output Length | 9 | |
| 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 | CHAR 9 |
| Medium | 15 | CHAR 9 |
| Long | 20 | CHAR 9 |
| Heading | 7 | CHAR 9 |
Documentation
Definition
Test mode
If you choose this option, the cross-archiving-object check program or delete program is executed in test mode. This means that the check or deletion is simulated according to your selection criteria. The result of the test run, for example whether a business object can be archived or deleted, is not saved persistently in a database table.
The application log that you reach from the start screen for the cross-archiving-object check or delete program provides information on the number of business objects that can be archived or deleted. If you are happy with the test results, you can perform the check or deletion in productive mode.
It is recommended that you do not use mass data when testing as this has a negative effect on performance.
Productive mode
If you choose this option, the cross-archiving-object check program or delete program is executed in productive mode; it is actually executed. With the check program, the result is updated to a database table as a status change. The subsequent write program or delete program evaluates this table and selects all business objects with a particular status and writes them to archive files or deletes them.
Use
Dependencies
Example
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 700 |
