Data Destruction of Infotypes

[former_member741507]

Hello,

I have just started looking into the ILM modules and currently trying to figure out how i can use the Data Destruction functionality to delete data directly from the database. There is no need for archiving it.

Is it possible to delete information from IT0009 (Banking Details) for inactive employee? If so, does anyone have information or tips on how i can achieve this? Will it be through the Destruction Object (TCODE DOBJ) and then do i run this through the Data Destruction program (TCODE ILM_DESTRUCTION)?

If someone can help answer the questions or point me to some useful tutorials it would be greatly appreciated.

Thanks!

[veesatya1975 · Accepted solution]

hi,

for this infotype, the table is PA0009 & the ilm object is HRPA_PYDTL. you can check t.codes DB15 & IRM_CUST. yes ILM_DESTRUCTION is used for data destruction, but you also need to configure the ILM policy before . it requires ILM & archiving knowledge

[former_member741507 · Accepted solution]

Hi Satya,

Thank you for your reply. I was able to achieve the data destruction of IT0009 with the Archiving Object HRPA_PYDTL. In order to do so i have to run the pre-process, then write and then the delete step runs automatically. Based on my understanding, even if i create an object for Destruction i would have to create a ABAP program that would need to execute with it. At the time of this post, i was wondering if there was a standard program already that would do the deletion of IT0009 from ILM_DESTRUCTION.

I tried to make a copy of HRPA_PYDTL to a Z Object, however when i run it, it still creates the log in HRPA_PYDTL. Would you know why that is? do i need to also copy the programs and make adjustments in there?

Thanks for you input!

[veesatya1975]

HI Janelle,

Generally speaking the data is completely destroyed if its not available in DB or Archive file.

are you using this object with regard to GDPR ? if yes then data destruction from both DB & archive files apply. you need to discuss with business & legal departments , on the retention periods to be used for the data in question.

also I don't think just using this object alone for data destruction of HR records is sufficient.

there will be other infotypes & objects that may need to be configured.

regarding the changes to the standard object. it is not recommended & yes it would be overwritten with SP upgrade.

Thanks & Regards,

Satya

[former_member741507]

Hi Satya,

I agree that there are many other infotypes to be maintained. My clients current need is based on their internal policies to only delete data related to IT0009. I have created a new Audit Area ZHCM_DP and attached HRPA_PYDTL to it. Within that object i have selected the IT0011 and IT0057 to not be deleted. I then maintained the Policy based on their retention period for IT0009. As mentioned this work exactly as i would have liked it to.

My concern was that i was not able to copy HRPA_PYDTL in order to make the changes for IT0011 and IT0057 to a copied version and not the original.

I can see my client having other needs like this in the future where they might want to delete some data and i will find a standard object that has that data, however these standard objects (such as HRPA_PYDTL or HRTIM_QUOT) will have other infotypes as well which i do not want to impact. I am trying to figure out a long term solution for such situation.

Thanks!

[veesatya1975]

Hi Janelle,

what you have performed is archiving, not a complete data destruction.

if you have noticed, within the write job, a file must have been created. this file contains those records deleted from IT0009.

the standard programs are already provided for archive objects, you can check AOBJ t.code.

when you activate business function ILM, additional options appear within the write programs of archiving objects,( with archiving, data destruction & snap shot). you need to choose the option data destruction within the program & then run it.

this is the actual method of using data destruction within SAP ILM..

trying to make copy of the standard object is not recommended.

regards,

Satya

[former_member741507]

Hi Satya,

correct it did create a write file however the delete job i configured to run automatically so immediately after the write file was created, it was then subsequently deleted.

Thanks for the tip on not copying the standard object. The object HRPA_PYDTL works great for what i want, however it also looks at the table PA0011 and PA0057. I do not want to delete the those 2 tables only PA0009. So i checked the box to "Not Delete" for PA0011 and PA0057. However if i change this on the standard object, don't i run the risk of having this change overwritten on the next SP upgrade?

Thanks again for your valuable input Satya.

Cheers!