Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-FS-ARE (Application Component) Archiving Engine⤷
ARFA_ARCHIVING_METADATA (Package) Archiving Metadata
Basic Data
| Data Element | TYP_ARFA_ORDER |
| Short Description | Dynamic Package Formation - Sorting |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | TABNAME | |
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 30 | |
| 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 | DynPackage |
| Medium | 15 | Dynamic Package |
| Long | 40 | Dynamic Package Formation - Sorting |
| Heading | 40 | Dynamic Package Formation - Sorting |
Documentation
Definition
Sorting sequence for dynamic package formation.
If a structure is stored here, dynamic package formation is active.
The business objects are read in the context of analysis or writing in the sorting sequence predefined by this structure. Each dynamic package contains all entries in the header table for the sorting attributes.
A dynamic package is formed for each group level change.
A dynamic package can either be archived completely or not archived completely.
If a dynamic package contains at least one business object that cannot be archived, the business objects that are indicated as 'can be archived' are set to 'cannot be archived'. The rejection reason is 'UZ'. This ensures that the whole package cannot be archived.
If all business objects in a dynamic package can be archived, each individual dynamic package is written to a data container in the write phase.
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 40 |
