Business Suite-Specific Settings for ILM Objects

In Customizing for ILM rules of SAP NetWeaver ILM, specific settings are defined for an object category (an application area) in addition to the general settings for each ILM object. This means assignments and specifications for value determination that the system needs at runtime for rule evaluation.

To view the settings in the SAP Business Suite (OT_FOR_BS) object category in the standard SAP delivery, call up the transaction for the Customizing of ILM objects as follows:

In the ILM Retention Management Cockpit or ILM Retention Warehouse Cockpit for Administrators under the menu option Services for Settings
In the application system with the transaction code IRM_CUST

Prerequisites

Since some object category-specific settings (such as value determination) are based on the general settings for ILM objects, you have familiarized yourself with these.

For more information, see General Settings for ILM Objects.

Structure

When you call up the list of ILM objects in the object category SAP Business Suite (OT_FOR_BS), you can view the following object category-specific settings for each ILM object.

Mapping ILM Objects to Archiving Objects

This is where the relevant ILM-enabled archiving object is assigned to the ILM object. The settings of the ILM object determine the application of the ILM rules to the archiving object (for example, for the data object it contains).

Note Note

Multiple ILM-enabled archiving objects can be assigned to an ILM object. However, an ILM-enabled archiving object must be assigned to only one ILM object.

End of the note.

Mapping ILM Objects to Data Destruction Objects

This is where the data destruction object is assigned to the ILM object. The settings of the ILM object determine the application of the ILM rules to the data destruction object (for example, for the data object it contains).

Note Note

An ILM object can be assigned to exactly one data destruction object. However, a data destruction object must be assigned to only one ILM object.

End of the note.

Mapping ILM Objects to BOR Object Types

This is where you find the names of the BOR object types that are assigned to the ILM object. A BOR object is a business object that is registered in the Business Object Repository (BOR).

Any number of BOR object types can be assigned to an ILM object. A BOR object type can also be assigned to more than one ILM object. The assignment is necessary for finding all BOR object types that are linked to an ILM object instance and to check whether any legal holds exist. If legal holds exist, you cannot destroy the corresponding ILM object instance.

Join Definitions

For the system to be able to derive values for rule evaluation at runtime, the source fields of the ILM object for value determination are specified for condition fields, time references, and time offsets.

If these fields come from more than one source table, the system uses a join operation to link their values from the relevant source tables at runtime. The system evaluates the ILM rules of the relevant ILM object for each record that results from this relationship.

In certain cases, for instance, when the data of two source tables should be linked by a Full Outer Join instead of the Cartesian product and also take additional equality conditions for the source fields into account, the relevant join definitions are defined.

For more information, see Linking Source Tables for Value Determination.

Value Determination for Condition Fields

You need to specify from which source fields of a table (source table) the system derives the values for the condition fields for available standard condition fields and condition fields of the ILM object.

Direct Value Determination

During direct value determination, the system takes the value of a condition field directly from the data of each object instance. To do so, a unique assignment of the condition field must be made to the corresponding source field of the object instance in the source table.

Indirect Value Determination

During indirect value determination, the system derives the value of the condition field from one or more source fields. This type of value determination is necessary if direct value determination is not possible or if values with nonpermissible characters could be returned. The logic for value determination is specified in the implementation of the following BAdIs:

BADI_IRM_OC_SF (for available standard condition fields; the implementation cannot be changed)
BADI_IRM_OT_FLD (for available condition fields; application-specific implementations are required)

Value Determination for Time Offsets

You need to specify from which source fields of a table (source table) the system derives the relevant reference date for the available time offsets of the ILM object (constants of the IRM rule engine delivered by SAP).

Direct Value Determination

During direct value determination, the system takes the value of a time reference (the reference date) directly from the data of each object instance. To do this, a unique assignment of the time reference must be made to the corresponding source field of the object instance in a source table. Data fields of the type DATS or TIMESTAMP (domains DATS or TZNTSTMPS) are permitted.

Indirect Value Determination

During indirect value determination, the system derives the value of the time reference (the reference date) from one or more source fields. The logic for value determination is specified in the implementation of one of the following BAdIs:

BADI_IRM_STT (Start date: Standard value determination from time offset)
BADI_IRM_OT_STT (Reference date: Determination from time reference; application-specific implementations are required)

For more information, see Explicit and Implicit Start Date Determination

Value Determination for Time Offsets

The logic for start date determination with the use of a time offset on the reference date is specified in the relevant implementations of the BAdI BADI_IRM_TO.

For some of the available time offsets for the ILM object, data other than the reference date and the time offset is required for the relevant ILM object instance. You need to specify which source fields in a table (source table) the system needs to calculate the start date for this type of time offset.

Determination of BOR Key

For the system to be able to check whether a legal hold exists when determining retention rules for an ILM object instance and related, linked BOR object types, the key for the BOR object types to be checked must be determined. For the automatic determination of the BOR key, you need to enter the source tables and source fields whose values are required for the determination of the key of the current ILM object instance.

The logic for value determination is specified in the implementation of the BAdI BADI_IRM_RELATIONS.

Determination of Bequeathing Instances

This dialog is available in the Business Suite-specific settings of the ILM object only if the ILM object permits the inheritance of rules. You can view this setting in the list of ILM objects for the SAP Business Suite object category in addition to the name and description of the ILM object under the Inheriting Possible indicator.

For the system to be able to determine the business key of the bequeathing object instance, you need to specify the relevant source fields of the source tables.

Note Note

To bequeath ILM rules, the following prerequisites must be fulfilled:

Implementations of the following Business Add-Ins (BAdIs):
- BADI_IRM_OT_INHERITANCE_OFFER for the bequeathing ILM object
- BADI_IRM_OT_INHERITANCE_USE for the inheriting ILM object
Activation of the archive infostructure of the bequeathing ILM objects. The archive infostructures need to contain the specified source fields as key fields.
For more information, see Providing Archive Infostructures for Data Access.

End of the note.

More Information

Business Add-Ins for the Evaluation of ILM Rules