Global Consolidation System lets you transfer subsidiary data to your remote parent instance over your corporate intranet. Optionally, the system can notify a user on the remote instance of transfer results. You can also choose to import and post your consolidation journals automatically. You can enhance security by setting up a user with only limited access to specific objects in the central consolidation database instance by setting up the Cross Instance Data Transfer.
The Global Consolidation System supports the transfer of subsidiary data to your remote parent instance over your corporate intranet.
For security purposes, the following instructions tell you how to set up a database username with only limited access to specific objects in the central consolidation database instance. Use this database username when defining a database link from the remote subsidiary to the central consolidation database instance.
To create the database username, perform the following steps.
On the central consolidation database instance, login to SQL Plus as the System Administrator to create the database username and to grant the following rights to the database username:
SQL>CONNECT system/manager@target_databasename
SQL>CREATE user IDENTIFIED BY password;
SQL>GRANT CREATE SESSION TO user;
SQL>GRANT CREATE TABLE TO user;
SQL>GRANT CREATE SYNONYM TO user;
SQL>COMMIT;
SQL>EXIT;
On the central consolidation database instance, login to SQL Plus as the database user and create a synonym for the fnd_oracle_userid table in the APPLSYS schema:
SQL>CONNECT user/user@target_databasename
SQL>CREATE SYNONYM fnd_oracle_userid FOR
applsys.fnd_oracle_userid;
SQL>COMMIT;
SQL>EXIT;
On the central consolidation database instance, login to SQL Plus as the APPS user and grant the following rights to the database username:
SQL>CONNECT apps/apps@target_databasename
SQL>GRANT EXECUTE ON GL_CI_REMOTE_INVOKE_PKG TO user;
SQL>GRANT EXECUTE ON GL_JOURNAL_IMPORT_PKG TO user;
SQL>GRANT SELECT ON gl_je_batches TO user;
SQL>GRANT SELECT ON fnd_oracle_userid TO user;
SQL>COMMIT;
SQL>EXIT;
On the remote subsidiary database instance, login to Oracle Applications as an Oracle Applications user and define a database link to your central consolidation database instance with the database username you just created.
Note: If you use the Global Consolidation System Cross Instance Data Transfer feature and you are transferring consolidation data to a target database that is not implemented with Oracle RDBMS 9iR2 or higher, you must set the MO: Distributed Environment profile option to Yes and the FND:Debug Log Enabled profile option to No for the target responsibilities. If you transfer consolidation data to a target database that is not implemented with Oracle RDBMS 9iR2 or higher, you will be unable to automatically import or post journals to the target instance.
On the source instance, define a Database Link to your remote parent database using the Define Database Link window.
(N) Setup > System > Database Links
On the target instance, create an application user who has a user name and password that are identical to the user on the source instance who will initiate the cross instance transfer process. Assign to the target instance user the responsibility that includes the parent ledger.
(Optional) On the source instance, navigate to the System Profile Values window. In the Profile field, query the profile option GL Consolidation: Cross-Instance Workflow Notification Contact. In the Application, Responsibility, or Site fields, enter the target instance user name entered in Step 2 and save your work.
On the target instance, verify that a valid e-mail address exists in the Users window for the user name entered in Step 2.
Define a parent ledger on the source instance that shares the same currency, calendar, and chart of accounts as the parent ledger on the target instance.
Navigate to the Transfer Consolidation Data or the Transfer Consolidation Data Set window. Complete the parameters in the window.
Choose the Consolidation Run Options button.
Enable the options you want to use: Run Journal Import, Audit Mode, Create Summary Journals, and AutoPost.
Select the database for your remote instance parent.
Enter the responsibility for your remote instance parent. This field is case sensitive. The parent ledger must be the default ledger for the data access set assigned to the responsibility.
Choose the Validate button to verify that the parent ledger on the source and target databases share the same currency, calendar and chart of accounts.
Choose OK.