How To Fix ILM_STANDARDS016 - Time ref. &1 (dynamic registr.): Indirect value det., BAdI impl. missing

ILM_STANDARDS016 - Overview

• Message type: E = Error

• Message class: ILM_STANDARDS - ILM Standard Checks

• Message number: 016

• Message text: Time ref. &1 (dynamic registr.): Indirect value det., BAdI impl. missing

What causes this issue?

You have defined a time reference for the ILM object by using the BAdIs
which were intended for it. (That is, you did not create it with
transaction IRM_CUST.) By doing so, you have decided that value
determination for the time reference is to be indirect. This means that
you must also offer an active BAdI implementation in which value
determination can take place. The following time references are still
missing an active BAdI implementation: &V1& &V2& &V3& &V4&

System Response

INCLUDE ILM_STNDRD_CHECK_SYS_RESP_1 OBJECT DOKU ID TX

How to fix this error?

Create an active BAdI implementation for the BAdI <LS>BADI_IRM_OT_STT</>
. Specify your ILM object as the filter.
INCLUDE ILM_STNDRD_CHECK_WHATODO_1 OBJECT DOKU ID TX

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message ILM_STANDARDS016 - Time ref. &1 (dynamic registr.): Indirect value det., BAdI impl. missing ?

  The SAP error message ILM_STANDARDS016 indicates that there is an issue related to the implementation of a Business Add-In (BAdI) for indirect value determination in the context of Information Lifecycle Management (ILM). This error typically arises when the system is trying to perform a dynamic registration for a time reference, but it cannot find the necessary BAdI implementation.
  
  Cause:
  
  Missing BAdI Implementation: The primary cause of this error is that the required BAdI implementation for indirect value determination is not available or has not been activated in the system.
  
  Configuration Issues: There may be configuration issues in the ILM settings that prevent the system from correctly identifying or using the BAdI.
  Transport Issues: If the BAdI implementation was recently transported from another system, it may not have been properly activated or may have dependencies that are not met.
  
  
  Solution:
  
  
  Check BAdI Implementation:
  
  Go to transaction code SE18 (BAdI Definition) and check for the BAdI related to indirect