SAP ABAP Data Element LRM_POLICY_ORIGIN (Policy Name)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-ILM-IRM-RT (Application Component) IRM Run Time
⤷ S_LRM_OBJ_CAT_INDEPENDENT (Package) Information Retention Manager - Cross-Object Category
⤷ BC-ILM-IRM-RT (Application Component) IRM Run Time
⤷ S_LRM_OBJ_CAT_INDEPENDENT (Package) Information Retention Manager - Cross-Object Category
Basic Data
Data Element | LRM_POLICY_ORIGIN |
Short Description | Policy Name |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | LRM_POLICY_ORIGIN | |
Data Type | CHAR | Character String |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 10 | |
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 | Policy |
Medium | 20 | Policy Name |
Long | 40 | Policy Name |
Heading | 30 | Policy Name |
Documentation
Definition
In addition to the audit area, it is necessary to specify a name to uniquely identify a policy.
Use
You can create more than on policy for the data retention of an ILM object. Every policy is therefore identified through specification of its Policy Name, among other things.
Dependencies
Example
A company decides that the following departments must be consulted before data is destroyed: Tax, product liability, and risk management. Every department has different sources for its rules, for example, to take account of country-specific differences. The tax department, for instance, applies a Germany-specific policy from the German SAP User Group (DSAG) for its German operations and a policy from ASUG for the USA. At present, no policies are in use for other countries.
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 712 |