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_FUBNAME_ANALYZE |
| Short Description | Business Check Module |
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 | Bus. Check |
| Medium | 19 | Bus. Check Module |
| Long | 20 | Bus. Check Module |
| Heading | 30 | Business Check Module |
Documentation
Definition
This module is called by the Archiving Engine in the analysis phase. This check module implements a business check. It receives a package of business object headers (more precisely, a partial view or projection of the business object header) in the analysis phase. The check module decides whether the objects can or cannot be archived. If an object cannot be archived, a rejection reason is set in the relevant field.
All business object headers in T_TABLE have the default starting status "Archivable".
Caution:
When can the resubmission date for a business object header in T_TABLE be determined?
Example:
Business object A references business object B. Therefore, A must be archived first, then B.
B must always remain in the system longer than A. The resubmission date for B is always later than or the same as the resubmission date for A.
If A exists in the system, B needs to be set to "Not Archivable" in the check.
If B is currently in T_TABLE to be checked, the resubmission date for A can be set as the resubmission date for B, if A references B (non-archivability).
Such references need to be checked in the check module (which business objects reference B).
If more than one business object references B, the resubmission date furthest in the future is selected for this business object.
The further in the future a resubmission date is, the better the Archiving Engine can manage mass data volumes. This avoids multiple time-consuming analyses for a specific business object over time.
Note: The resubmission date can also be initial in the check module. In this case, there are more analyses for the individual business objects over time. (Performance losses in the archiving scenario).
Use
Dependencies
Example
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 30 |
