SAP ILM: Process customer-specific time references SAP ILM analogously to HCM_TERMN_DATE
Initial situation and problem:
When using/processing the customer-specific time reference HCM_TERMN_DATE (leaving date) in the SAP standard, a hard check is carried out for this time reference. The intention of this check is to also include the Highdate datasets (31.12.9999) to process and log.
However, if a customer-specific time reference is defined, these highdate data sets will not be processed/logged correctly. In a concrete example, we have created a customer-specific time reference for retirement for you. This returns the employee's retirement date. However, since the leaving date (HCM_TERMN_DATE) is only checked hard, the high date data records could not be processed/logged correctly for the customer-specific time reference.
Solution:
Since there is no suitable BAdI for this, an enhancement implementation was created for the "MODIFY_EXCEEDS_LIMIT_FLAG" method, in which the Z_TERMN_R2 is now also checked in the same way as the HCM_TERMN_DATE.
Subject:
Class: CL_HRARCH_DESTRUCTION_LOG
Methods: WRITE_DESTRUCTION_LOG and MODIFY_EXCEEDS_LIMIT_FLAG
Current processing:
In class CL_HRARCH_DESTRUCTION_LOG method MODIFY_EXCEEDS_LIMIT_FLAG hard check for HCM_TERMN_DATE and remove flag of cv exceeds_limit_date. The flag is set to X if it is a high-end data set.
The destruction log is called for each data record using the WRITE_DESTRUCTION_LOG method. A general check for the destruction (GET_RETENTION_RULES) and the check for the exit date (MODIFY_EXCEEDS_LIMIT_FLAG) takes place here.
A correct log entry is only written if both variables (lv_destructible, lv_endda_adjusted) are empty.
Do you have any questions on the subject of "customer-specific time references in SAP ILM" or do you need further help? Contact us via the contact form and send us a message.
