Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-FS-ARE (Application Component) Archiving Engine⤷
ARFA_ARCHIVING_FACTORY (Package) Archiving Factory
Basic Data
| Data Element | TYP_ACTION18 |
| Short Description | Check Plug-In |
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 | 18 |
| Medium | 15 | 18 |
| Long | 20 | 18 |
| Heading | 2 | 18 |
Documentation
Check Plug-In
A check plug-in is a group of check modules and is primarily used as a structuring aid when many check modules are involved (for complex archiving and deletion objects).
A check plug-in can be used by multiple scenarios (reuse, check plug-in sharing, central definition of check modules and reuse in multiple scenarios). This should usually be avoided.
One check plug-in is preferable for lightweight scenarios. It can have the same name as the scenario itself (standard naming convention).
The business rejection reasons are defined on the level of check plug-ins. These rejection reasons can only be started by the check modules defined below the check plug-in.
The rejection reasons are defined in a domain with a descriptive text. Use the range 01-99. The rejection reasons for check plug-ins within a scenario cannot overlap.
Check plug-ins can have a sorting criterion (freely-definable two-character field). The check plug-ins (with the underlying check modules) are then executed by the Archiving Engine in ascending lexicographic sequence. This is particularly important if the analysis strategy "stop at first rejection" is set. The check plug-ins that are very selective should be executed chronologically, that is, those with a high probability of leading to a business rejection.
In the analysis strategy "optimum resubmission date", the sorting criterion is not important.
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 40 |
