Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-ILM-IRM (Application Component) Information Retention Manager⤷
S_ILM_OBSOLETE_DDIC_OBJECTS (Package) Obsolete objects for IRM
Basic Data
| Data Element | IRM_POLICY_TYPES_COMPLETE |
| Short Description | IRM: Object Type Has All Required Policy Types |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | BOOLE | |
| 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 | Complete. |
| Medium | 20 | Pol. Types Complete |
| Long | 40 | Policy Types are Complete |
| Heading | 1 | C |
Documentation
Definition
Attribute specifying that the policy types of a specific policy category for an object type are completely maintained. Completely maintained means that at least one policy is registered for each relevant policy type. From this point on, the archiving attempts to access productive rules stored in IRM.
Use
Archiving is only possible if information on the retention period is stored for every policy category stored in IRM for this object type. If there are policies of different origins for a policy type, a rule for every object instance to be archived must be found in at least one of these policies. Here only those policies are considered that have the "Policy Productive# flag (see Policy is used in production).
If no productive rule is stored for an object instance of a required policy type, then it cannot be archived. This means that the person responsible for a policy type in IRM not only has to store rules for the object instances that they think need to be retained, but they also have to indicate that they see no necessity to retain other object instances. They do so by entering a correspondingly short retention period.
Dependencies
Example
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 710 |
