Setup Data Import and Export for Oracle Fusion Financials
The following table describe the manual tasks that you must complete as part of the setup data export and import processes for the Oracle Fusion Financials offering.
Section |
Description |
---|---|
Setup tasks performed before export |
Perform these tasks prior to starting export processes for the Financials offering. |
Setup tasks performed before import |
Perform these tasks prior to starting import processes for the Financials offering. |
Setup tasks performed after import |
Review and perform the manual setup steps on the target instance as required. Setup data for these tasks isn't imported from the source instance. |
Setup tasks not requiring data import |
Perform these tasks on the target instance as required. These setup tasks don't require data import. |
Refer to the Oracle Fusion Functional Setup Manager User's Guide for the steps to perform setup data export and import processes.
Setup Tasks Performed Before Export
Prior to starting the export processes from the source instance, you must verify and update setup for the following task described in the table. Verifying the setup ensures that data is correctly imported into the target instance.
Activity Name |
Task Name |
Setup Steps |
---|---|---|
Define Chart of Accounts |
Manage Account Combinations |
Account combinations aren't exported from the source instance. Before exporting, navigate to the Manage Chart of Accounts Instance page on the source instance and verify that dynamic insertion is enabled for your charts of accounts. As long as dynamic insertion is enabled, account combinations are created automatically as needed on the target instance. |
Setup Tasks Performed Before Import
Prior to starting import processes into the target instance, you must verify and update setup for the following task described in the table.
Activity Name |
Task Name |
Setup Steps |
---|---|---|
Define Common Applications Configuration for Financials |
Define Implementation Users |
The import process doesn't include implementation users and roles associated with them. For more information, see Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management. |
Setup Tasks Performed After Import
Setup data for the following tasks listed in the table aren't imported. Review these tasks for relevance to your implementation. For relevant tasks, open the corresponding setup pages from your implementation project to create the setup on the target instance as needed.
Activity Name |
Task Name |
---|---|
Define General Ledger Options |
Manage Journal Approval Rules |
Define Approval Management for Financials |
|
Define Tax Geographies |
Manage Tax Geographies |
Define Payables |
|
Define Image Processing |
Configure Document Capture Parameters |
Define Customer Billing Configuration |
Manage Salesperson Account References |
Define Customer Payments |
Manage Receivables Specialist Assignment Rules |
Setup data for the following tasks listed in the table aren't imported from the source instance. Review the steps in the following table to create the setup on the target instance as needed.
Activity Name |
Task Name |
Setup Steps |
---|---|---|
Define Credit Card Data |
Extend Employee Matching Rules |
Write user-defined PL/SQL code to extend the predefined criteria for automatically matching new corporate cards to employees to incorporate your company-specific criteria. If you use a user-defined matching rule, then the PL/SQL package isn't imported to the target instance. You can create the package in the target instance or copy the package to the target instance and compile it. |
Define Customer |
Create Customer |
Manually create customers, using the Create Customer task in Functional Setup Manager, or import customer information by running the Trading Community Model Data Import program. |
Define Customer |
Manage Customers |
Manually maintain customer information using the Manage Customer task in Functional Setup Manager, or by running the Trading Community Model Data Import program. |
Configure Payment System Connectivity |
Manage BI Publisher Templates |
Manually import any new or updated BI Publisher templates. Use the BI Publisher archiving feature, or alternatively perform the following steps:
|
Define Subledger Accounting Rules |
Import Supporting Reference Initial Balances |
This task allows upload of initial subledger balances for supporting references. These balances aren't imported from the source instance, but can be loaded directly to the target instance. For more information, see Oracle Fusion Accounting Hub Implementation Guide, Define Accounting Transformation. |
Configure Payment System Connectivity |
Integrate External Payment Systems |
Setup entities resulting from this integration are exported and imported through the Transmission Configuration service. However, any work performed outside of Oracle Fusion Applications to integrate with a payment system must be applied to the production environment manually. Examples include user-defined code, routers, or dedicated lines to facilitate communication. |
Define Payments Security |
Manage System Security Options |
This setup can't be imported and must be set up again in a production instance. Use the steps documented in the Oracle Fusion Applications Post-Installation Guide. |
Define Financial Reporting Center Configuration |
Configure Smart View Client for Users |
Manually reconfigure the Smart View client to point to the production instance. For more information about configuring the Smart View client for users, see:
|
Define Financial Reporting Center Configuration |
Define Essbase Database Connection in Workspace |
Manually reconfigure the Essbase database connection in Hyperion Workspace. For more information about configuring the Hyperion Workspace Database Connection, see Oracle Fusion Accounting Hub Implementation Guide, Define Financial Reporting, |
Define Financial Reporting |
Create Financial Statements |
Export the financial report definitions from Workspace in the source environment. When exporting, you can export a single report, multiple reports in a .zip file, or an entire folder structure in a .zip file.
Import the file into Workspace in the target environment.
If you import the folder structure, the entire structure from the source instance is imported into the existing structure on the target instance. This could result in some redundant folders. In this case, you can reorganize child folders in the structure on the target instance and delete any unneeded folders. |
Define Period Close Components |
Manage Allocations and Periodic Entries |
Export the allocation rules, rule sets, variables, and run time prompt definitions from Calculation Manager in the source environment. When exporting, you can export at the application level or at a single rule or rule set level. Note: You must export and import rules for each application
on the Essbase server separately.
Import the file into Calculation Manager in the target environment.
|
Define Hyperion Financial Management Integration |
Define Hyperion Financial Management Configuration |
Manually import the rules using the Oracle Enterprise Performance Management Lifecycle Management tool. For more information, see the Oracle Hyperion Artifact Lifecycle Management Utility User's Guide. |
Define Hyperion Financial Management Integration |
Define ERP Integrator Configuration for Hyperion Financial Management |
Manually import the rules using the Oracle Enterprise Performance Management Lifecycle Management tool. For more information, see the Oracle Hyperion Artifact Lifecycle Management Utility User's Guide. |
Define Budget Configuration |
Define Budget Configuration in Hyperion Planning |
Manually import the rules using the Oracle Enterprise Performance Management Lifecycle Management tool. For more information, see the Oracle Hyperion Artifact Lifecycle Management Utility User's Guide. |
Define Budget Configuration |
Define ERP Integrator Configuration for Hyperion Planning |
Manually import the rules using the Oracle Enterprise Performance Management Lifecycle Management tool. For more information, see the Oracle Hyperion Artifact Lifecycle Management Utility User's Guide. |
Setup Tasks Not Requiring Data Import
The following tasks in the setup task list are available to support your overall implementation approach. These tasks listed in the following table don't require any data to be imported. You can perform these tasks on the target instance as required.
Activity Name |
Task Name |
---|---|
Define Tax Configuration |
|
Define Fixed Assets Configuration |
Verify Data Role Generation for Asset Books |
Define Disbursements |
Grant Payment Function Access |
Configure Payment System Connectivity |
View Validations |