Effects of an Oracle Cloud ERP P2T Refresh on Embedded Banking
Use these FAQs to understand how an Oracle Cloud ERP production-to-test (P2T) refresh affects Embedded Banking Services enablement, test-environment setup changes, payment templates, and bank files.
What happens if a P2T refresh occurs while Embedded Banking Services enablement is in progress?
What happens if a P2T refresh occurs after Embedded Banking Services enablement is complete and testing is in progress?
The P2T refresh doesn't affect your Embedded Banking Services enablement status. Embedded Banking Services remains enabled. However, if you made changes in the test environment to support Embedded Banking Services, any changes that you didn't promote to production are lost during the P2T refresh. If bank statements or acknowledgment files are scheduled for delivery to the test environment, the files continue to flow to the test environment after the refresh. However, file processing might fail if the setup is incomplete.