Best Practices from Oracle Development's A‑Team
-
/ A-Team Chronicles
February 27, 2021
How to Separate your Oracle Fusion Applications Cloud for divestiture?
Introduction
In the recent economic and unexpected pandemic situation, many companies are considering divestiture or merger & acquisitions.
The most common scenarios for divestiture are:
- Sell-Off – Sale of one or more business areas/units to another company
- Spin-Off – A company divests into multiple units (Example: PayPal from eBay)
- Split-Off – Breaking a company into separate companies (Example: Synchrony Financial from GE)
Let us consider the following scenarios:
1) Two companies are live in the same Oracle Cloud ERP Production environment. A business decision is made to separate one of the two entities to a new Oracle Cloud ERP Production environment.
2) A leading company has successfully implemented Oracle Fusion Applications Cloud solution and now considering a strategic initiative to separate one of its business units & its operations as an independent business. One or more modules of Oracle Fusion Applications Cloud (Enterprise Resource Planning (“ERP”), Human Capital Management (“HCM”), Customer Experience (“CX”)) have been deployed in one Global Single Instance (“GSI”) production instance. For additional information about GSI and Instance strategy refer to my other blog on "Oracle Fusion Applications Cloud Instance Strategy and Global Single Instance Guidelines".
Business divestiture is a program based on your management decisions. To enable information and technology for the new company, you need a project for getting the required application and data separated from your existing Oracle Fusion Applications Cloud. Separating the application, setup, configuration, users, security roles, functional processes, integrations, and relevant data to the new company is an implementation project by itself.
Please refer to my updated blog "An approach to separate your Oracle Fusion Applications Cloud for divestiture"