P2T Refresh:
P2T refers to production to test cloning, which allow 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 reflect time between your request and the day your test environment will be refreshed.
Some oracle customers raising 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.
Why oracle takes too much time to clone your production?
their are many reasons why this may be scheduled to be late,
Usually this cloning takes too much time due to receiving too many requests for cloning environments from many customers in short time which causing to set cloning date to be late – in most cases three weeks, and some times two months.
Most of the customers ask for cloning by the end of financial years and end of quarters,
that’s’ why you should raise this request early as you can when you need to clone your instance on these periods.
What is Data masking?
when you raise SR for P2T 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 accidently 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 employees name , salaries, 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 masing is allowed for HCM modules only, any other modules like finance and SCM are not applicable for this function.
What is T2P?
T2P refers to test to production cloning, this sometimes required when you need to overwrite or delete your data on production.
The are many cases when some oracle customers need to override their production data with test environment.
These cases may include the following:
Customers start implementation on test instance and complete all configurations and now they need to move every thing to production in order to go live.
Customers who have data migration corruption with no option to delete or no returning points as a correction action.
In this case oracle always reject any request to delete any data or recover their database to earlier checkpoint,
oracle policy is clear, they will not interact or access your data in anyway.
In this situation the only option you have is to raise T2P SR and ask oracle to override your production with test.
If you have already data on both instance test and production and you are on implementation phase, you can buy new license for additional test environment for this purpose.
keep in mind that T2P should go throw some approvals on oracle before Appling it,
in addition they will ask you for some singed approvals from authorized managers in your company.
Read More:
Recent Posts:
- Query to get bank account details in Oracle E-business R12 CM, quick results.
- What is the oracle fusion list of modules now?
- What is Microsoft dynamics 365? Is it good for your business? All you need to know!
- How to become oracle expert – developer? steps to start your career, All you need to know!
- Reasons why to upgrade from EBS to Oracle Fusion Cloud now.
