SAP ABAP Data Element LRM_POLICY_MANDATORY_FIELDNAME (Mandatory Condition Field for Policies of an ILM Object)
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

⤷

⤷

Basic Data
Data Element | LRM_POLICY_MANDATORY_FIELDNAME |
Short Description | Mandatory Condition Field for Policies of an ILM Object |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | FDNAME | |
Data Type | CHAR | Character String |
Length | 30 | |
Decimal Places | 0 | |
Output Length | 30 | |
Value Table | DD03L |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | DFD | |
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Mand. Fld. |
Medium | 20 | Mandatory Field |
Long | 40 | Mandatory Field for Policies |
Heading | 30 | Mandatory Field |
Documentation
Definition
In this table you can define which condition fields are mandatory in the policies of an object category. Mandatory condition fields are not made available to the user when creating policies.
Use
Dependencies
If you register a mandatory condition field, you must ensure in the code of this object category that it is filled with a value before a rule query is started in IRM for rule determination.
Example
Examples for condition fields such as System ID and Client are mandatory. In the case of the client, this means that cross-client data in the ILM store always has a client in its path.
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 712 |