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_CONDENSE |
| Short Description | AIS Summarization in Dynamic Package Formation |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| 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 | Summariz. |
| Medium | 15 | Summarization |
| Long | 20 | Summarization |
| Heading | 11 | Summariz. |
Documentation
Definition
This option enables you to build a summarized AIS information structure.
Basis:
During archiving, AIS information structures are filled with the aim of being able to display data by individual document access.
Since archiving (= removing) data from one application table and inserting it one-to-one at another location (in this case, the AIS information structure) does not help to reduce data in the database and improve performance, it is better to store the business object data summarized in the AIS information structure. This can then be used to access the individual records in the archive.
In addition to performance aspects, this also results in a lasting reduction in data in the database. For this reason in particular, this procedure is useful if an archiving object includes one database table only.
Prerequisites:
a) The sorting attributes are defined (F_SORTATTRIBUTES).
b) The AIS information structure contains these exact sorting attributes.
c) The virtual structure for the sorting attributes needs to be registered as a table in the read section in the 'Archive' category with the associated read module.
d) All read modules select the data on the basis of sorting attributes (not on the basis of the business key).
Caution:
The read modules do not receive the business key, but the extended business key. This is the business key itself and the sorting attributes. The fields for the sorting attributes can be accessed using
MOVE-CORRESPONDING F_BUSINESSKEY INTO F_SORTATTRIBUTES
The Select with these sorting attributes must be executed according to:
SELECT * FROM (P_TABNAME) INTO T_TABLE
WHERE attrib1 = F_SORTATTRIBUTES-attrib1
AND attrib2 = F_SORTATTRIBUTES-attrib2
...
AND attribn = F_SORTATTRIBUTES-attribn.
Technical Background:
The read modules are called once by the Archiving Engine every time the group level is changed (in the sorting attributes). All data for a group level is read with the read modules. This data is then placed in the archive container and saved in an archive file using ARCHIVE_SAVE_OBJECT. For each archive container, one summarized AIS entry is written in the corresponding information structure.
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 40 |
