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_PACKAGE_DYNAMIC_EXTENSION |
| Short Description | DO NOT USE ANYMORE |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | FUNCNAME | |
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 30 | |
| Value Table | TFDIR |
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 | Package Ex |
| Medium | 16 | Package Ext. |
| Long | 27 | Dynamic Package Extension |
| Heading | 30 | Dynamic Package Extension |
Documentation
Definition
Dynamic package extension is relevant in the analysis phase.
The Archiving Engine forms packages with a fixed size as standard (according to the parameter on the Archiving Engine UI). It can sometimes be necessary to add to business objects beyond this package limit.
Dynamic package extension enables business objects to be packaged semantically. This means that all business objects that belong together semantically have the same archiving status in the business check.
The right package limit is increased until the semantic package is completely included in the overall package.
The input for the module for dynamic package extension is the database cursor P_CURSOR and T_TABLE. T_TABLE contains business objects at the call-up time.
T_TABLE is sorted by the PRIMARY KEY as standard. If you predefine a sorting sequence, T_TABLE is sorted according to this.
Within the module, more business objects can be added to T_TABLE using group level change.
A group level change can be determined by reading single records according to
FETCH NEXT CURSOR P_CURSOR INTO CORRESPONDING FIELDS OF F_NEXT.
T_TABLE must have business objects added from within the group.
Once F_NEXT is on a business object that does not belong to the semantic group, the process of reading single records is ended. T_TABLE contains the semantic package and F_NEXT is on a business object that belongs to the next semantic package.
Use
Dependencies
Example
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 40 |
