Transferring Subsidiary Data to Your Parent

Submitted by Anonymous on Fri, 12/11/2009 - 15:28
Tag:
Transfer the balances or transactions to be consolidated from your subsidiary set of books to your parent. General Ledger accumulates your subsidiary information based on the mapping rules you defined, then populates the GL_INTERFACE table with the consolidation data. Choose the Run Options button to define consolidation run options and enter remote instance signon parameters if applicable. For example, you can run Journal Import and AutoPost automatically at the time you
transfer your subsidiary data.

Note: You can initiate a subsidiary–to–parent transfer from the subsidiary set of books or from the parent set of books only
when transferring within the same instance. The source instance must initiate a cross instance data transfer.

Consolidation Run Options
When you create a consolidation mapping or mapping set you can select any of four run options listed below and transfer your consolidation journals to the parent set of books. You can override these selections when you transfer subsidiary data to your parent.

Run Journal Import: Checking this option launches Journal Import after your subsidiary data has been transferred. This creates an unposted consolidation batch in your parent set of books automatically.
General Ledger names your batch in the following format: <Date> <Consolidation Mapping Name> Consolidation <Request ID>: <Balance Type> <Group ID>; for example, 31–JAN–95 US to Global Consolidation 50835:A 534. You may not want to run Journal Import if you want to schedule your batch processes to run later or if you want to transfer consolidating data across different machines or databases. If you choose not to run Journal Import, the transfer process populates
the GL_INTERFACE table so that you can run Journal Import later.

 
Note: If you are utilizing the Feature for Alternative Accounting Representations, General Ledger preserves up to
50 characters of the source batch name plus batch ID in the format <original batch name>:<batch ID>. If applicable, the following information is added after the first 50 characters: <Source><Request ID>:<Actual Flag><Group ID>; for example, Travel Summary:7708 Consolidation 1677754: A 3822.
 
Audit Mode: Check this option to keep a record of how accounts from your subsidiary set of books map to accounts in your parent set of books. You can then run the Consolidation Audit Report, the Disabled Parent Accounts Report, and the Unmapped Subsidiary Accounts Report to see consolidation audit information.

Suggestion: Use audit mode for new consolidations to ensure that your definition is correct and your sets of books are
mapping as you expected. Once you have verified this, you can improve performance by disabling audit mode.
After your subsidiary data has been transferred and you have requested the audit reports, purge your consolidation audit data using the Purge Consolidation Audit Data window.

Create Summary Journals: Check this option to summarize all journal lines that affect the same account code combination into one line in the parent set of books. Since this is a summary action, General Ledger creates one journal entry line showing debits and credits for each account code combination.

AutoPost: Check this option to automatically post your consolidation journals in the parent set of books.

Remote Instance Signon Region
Complete the following fields and choose the Validate button to verify that you can transfer consolidation data from your source instance to your parent instance. Note your parent instance must be on the same corporate intranet.

Database: Select the remote instance database.

Responsibility: Enter the remote instance responsibility that allows you to transfer consolidation data to the remote parent instance. Choose the Validate button to verify that the parent set of books on the source and target instances share the same calendar, currency, and chart of accounts.

Comments

Post new comment

The content of this field is kept private and will not be shown publicly.
All Rights Reserved. Copyright 2008-11 OracleUG.com.