Data Masking in Test Environments

What is Data masking?
when you raise SR (Service Request) for P2T (Production to Test) request, you will be asked, do you want
to apply data masking for your backup or not.


Data masking is a function applied by oracle in order to hide sensitive personal information on Test
Instance.

This data masking will protect your data from accidentally being accessed by non-authorized people
while using your test environment.
For example, consultant who is applying some configurations or developing reports should not be
allowed to see employees salaries, address or any personal data.
By applying data masking, All employee’s name, salaries, and bank information will be changed to non-
meaningful data.
For sure this will not affect the configurations as you can complete any cycle normally exactly as
configured on production.
Data masking is allowed for HCM modules only, any other modules like finance and SCM are not
applicable for this function.

P2T Refresh:
P2T refers to production to test cloning, which allows you to copy all your production transactions and
configurations to your test Environment.
This process usually takes around three weeks at least in order to be completed by oracle support, this
duration reflects time between your request and the day your test environment will be refreshed.
Some oracle customers raise P2T request every month in order to keep their test instance updated as
much as they can.
Actually this is the regular way of cloning your applications in oracle fusion cloud.
In order to raise P2T request, you just need to sign to your oracle support account and raise a new SR
including the source environment which is your production and the target environment which is your
test instance.

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.