Migrate Joint Venture Setup Data to Production

Oracle recommends that you set up the following joint venture components in a test environment before you implement them in a production environment:

• System options

• Invoicing partners

• Joint venture definitions

• Overhead methods

• Account sets

You can then test your setup by running the ESS processes that are used to identify and distribute joint venture transactions, and verify that distribution records were generated successfully. After testing, migrate the joint venture setup data to a production environment. If you prefer, you can test one or two joint ventures in a test environment, migrate them to production, and then set up your remaining joint venture definitions directly in production.

As you work through these steps, refer to Setup Data Export and Import for more information about the FSM migration services.

Before You Begin

To use migration services in Functional Setup Manager (FSM) to export and import joint venture data, you must have the Application Implementation Consultant (ORA_ASM_APPLICATION_IMPLEMENTATION_CONSULTANT_JOB) role.

You can migrate joint venture setup data only for the business units you're authorized to manage through data security. See Set Up Data Security for Oracle Joint Venture Management for more information.

Oracle Joint Venture Management is a functional area in the Oracle Fusion Cloud Financials offering. Before you can migrate Joint Venture Management setup data, you must migrate the Oracle Financials offering setup data that is applicable to your implementation. The setup data includes supporting references and other values in Oracle Financials that you might have set up in a test environment. This also might include supporting references for Oracle Project Costing if your Joint Venture Management implementation includes an integration with Project Costing.