Hierarchy

⤷

⤷

Basic Data
Data Element | LRM_SOURCE_TABLE_NAME_KOW |
Short Description | Source Table for Determining the Object Instance Key |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | AS4TAB | |
Data Type | CHAR | Character String |
Length | 30 | |
Decimal Places | 0 | |
Output Length | 30 | |
Value Table | DD02L |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | DTB | |
Default Component name | TABNAME | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | SourceTabl |
Medium | 20 | Source Table |
Long | 40 | Source Table |
Heading | 30 | Source Table |
Documentation
Definition
To make it possible to check, when determining retention rules, for example, whether an object instance is involved in a legal hold case, the key of this instance must be recognizable in BOR format (Business Object Repository). This conversion is always necessary as the BOR key does not need to be transferred when calling IRM methods to determine retention rules.
To do so, enter the source tables (Source Tables column) and their source fields (Source Fields column), whose value you need to determine the key of the current object instance, in the dialog Determination of an Object Instance Key.
The BOR key is usually created by linking the values of these fields. Define at which position the field value is used in the BOR key (Field Position column).
The actual determination of the BOR key takes place at runtime in the default implementation of the method GET_RELATED_OBJECTS of the BAdI BADI_IRM_RELATIONS, to which the above mention values were transferred.
If the BOR key is not created correctly in the default implementation, then you can create your own implementation of the BAdI for the corresponding ILM object. This is then called up automatically instead of the default implementation.
The BOR format is a typical example. Other formats such as KPRO or ArchiveLink documents are also possible.
Use
Dependencies
Example
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 712 |