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_ANALYZE_STRATEGY |
| Short Description | Strategy (Analysis) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | TYP_ANALYZE_STRATEGY | |
| 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 | 9 | Strategy |
| Medium | 17 | Analysis Strategy |
| Long | 17 | Analysis Strategy |
| Heading | 17 | Analysis Strategy |
Documentation
Definition
In the business check (analysis phase), there are two different analysis strategies:
a) Best possible calculation of resubmission time
b) Best possible performance
The analysis strategy determines the sequence of check modules. In a), all check modules are run. The resubmission times calculated by the check modules are consolidated, and the resubmission date furthest in the future is then relevant for the current business object.
Advantage of a)
The quality of the resubmission date is very good. Business objects with business rejections are not included in the next analysis phase until way into the future.
Disadvantage of a)
All check modules must be run, even if it is already obvious during the sequence that a business object cannot be archived.
Advantage of b)
As soon as the first business rejection occurs in the check sequence, this sequence is ended. This saves performance-intensive execution of further check modules where possible.
Disadvantage of b)
The resubmission date is not optimal, since later check modules might have determined a resubmission date further in the future.
Use
Dependencies
Example
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 30 |
