Hierarchy
![](/abap/icon/s_instal.gif)
⤷
![](/abap/icon/s_b_tree.gif)
⤷
![](/abap/icon/s_pckstd.gif)
Basic Data
Data Element | IRM_POLICY_ORIGIN |
Short Description | IRM: Policy Origin |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | IRM_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 | Pol. Orig. |
Medium | 20 | Policy Origin |
Long | 40 | Policy Origin |
Heading | 30 | Policy Origin |
Documentation
Definition
In addition to the type, the specification of the origin is necessary fro the unique identification of a policy.
Use
For an object type, policies can exist for data retention for different origins. Every policy is therefore identified by the specification of the policy origin. This means that in a system, rules of different origins can be present for an object type. For residence time policies, this subdivision is not necessary as there can only be one or no policy of this category for an object type.
Dependencies
Example
In a company, a decision is made that before the destruction of data, the following departments must agree to this: tax, product liability and risk management. Every department uses different sources for their rules, for example, in order to take country-specific differences into account. For example, the tax department could have a Germany-specific policy taken from the SAP user association DSAG, whereas it might use a policy from ASUG for the USA. Initially no polices will be used for other countries.
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in | 710 |