Reply from Morgana99 on Mar 15 at 11:48 AM Hi Divya
I see. Well, I think the standard SAP system sets the dependent field in IT0021 as relevant for retroactive accounting for country grouping 10. Presumably if you intend to scramble it in the live system, this field is not relevant for you in respect of payroll or benefits calculations? I have not previously come across this requirement in a live system. If the data you intend to scramble is not payroll or benefits administration relevant, you could configure the field on the infotype so it does not trigger retroactive accounting. However, you must check with all relevant parts of the business to ensure scrambling the data in production will not cause unwanted impacts. Without knowing all the details, it is hard to give precise advice, but it sounds high risk to me and perhaps other options such as an authorized person in HR exporting the data and then scrambling it outside the system before distribution to managers (or whoever is the report recipient) might be a less risky option, rather than manipulating data in a live environment.
KR, Alison
| | | ---------------Original Message---------------
From: Divya Narayan
Sent: Thursday, March 15, 2012 10:55 AM
Subject: Change Before Earliest Retro. Date 10/25/2010 Acc. to Control Rec. to Py Area 10
Hi Group,
I need to scramble the master data for HR data security.
I am facing problem while changing the date of birth of the dependents in
IT0021. I am getting an error message as :
Change before earliest retro. date 10/25/2010 acc. to control rec. to py
area 10
Please suggest if it is advisable to go for this master data change.What
would be its adverse effect?
--
Regards,
Divya |
| Reply to this email to post your response. __.____._ |  _.____.__ |
