HR Data Destruction Issue for Retiree Employee (status 2)

[rahul_gupta08]

Hello Experts,

We have encountered with an error while destructing the retiree employees (employment status: 2). Rules and policies are configured as enclosed and status is live. It works for withdrawn employee (employment status: 0) with same configurations.

Has anyone come across with such issues? rules-created.png

[rahul_gupta08]

dharshan.a Do you have any idea why are we getting this issue?

[former_member289103]

Hi Rahul,

I am not a HR expert, hence cannot say whether its a functionality gap or customer specific. If its a gap ( Your thought: SAP should have provided that entry), then you can raise a message to the right component requesting for the enhancement.

On the other hand, If you already have a date field in mind ,then there is no need for BADI implementation. You can enhance in IRM_CUST to handle such cases where we might need adding new date fields than the delivered, either by enhancing the standard content( conditions apply 🙂 ) or by building custom content. Any customization in IRM_CUST done the right way , if gives unexpected result, SAP should support it. So you need thorough understanding of IRM Customization. Please reach out to SAP Consulting if you need guidance in this matter.

Thanks and Regards,

Dharshan A

[rahul_gupta08]

Hi Dharshan,

This seems a gap from SAP.

As I believe not all the customers are using the SAP for payroll and if the employee is retired, its personal data is not required in SAP. All payroll related data is already maintained in third party system and benefits will be given to employee accordingly.

I have raised the message to SAP.

BR,

Rahul