This HR/GRC tip comes from a presentation that Richard Hunt will be delivering at our upcoming Financials, HR, and GRC conferences 7 - 9 June in Amsterdam. The title of the presentation is "Improve data privacy compliance and segregation of duties (SoD) controls in an SAP ERP Human Capital Management environment"
Unable to attend the event in Amsterdam or anxious to have your questions on this subject answered sooner? Richard will be hosting a live Q&A on "Protecting HR data privacy" here on Insider Learning Network!
Ask your questions in a Q&A on "Protecting HR data privacy," with Richard Hunt and Heinrich Wilking of Turnkey Consulting, in the HR Forum on Insider Learning Network. Join your peers on Thursday, May 26, from 11:00 am – 12:00 pm ET and bring your questions about protecting employee data in your SAP HR environment.
Register for this Forum sapinsider.wispubs.com/HuntWilkingHRforu...> and you'll also receive access to exclusive take-home materials from Richard Hunt’s GRC 2011 presentation “Improve Data Privacy Compliance and Segregation of Dut
ies (SoD) Controls in an SAP ERP Human Capital Management Environment,” previously only available to conference attendees. Register today, then ask your questions on Thursday, May 26, 11:00 am-12:00 pm ET.
Configuring a data privacy popup is a good way to mitigate compliance with data privacy legislation
- A data privacy popup can be configured to be activated when a user first logs on
- This requires the user to actively confirm the context in which they will use the data they are about to access
- Confirmed acceptance from the user forms a “contract for data use”
- Since data privacy rules vary between countries, it is possible to use different texts for different countries or to only require acceptance in certain countries
- The popup can be configured using an SAP-delivered customer exit in the logon routine: EXIT_SAPLSUSF_001
Customer exits are configured using transaction CMOD
Define a custom function module in the user exit
Define text for your data privacy statement as a “General Text” in transaction SE61