When you create a consolidation definition or consolidation set you can select any of four run options listed below and transfer your consolidation journals to the parent ledger. 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 ledger automatically. General Ledger names your batch in the following format: <Date> <Consolidation 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.
Create Summary Journals: Check this option to summarize all journal lines that affect the same account code combination into one line in the parent ledger. Since this is a summary action, General Ledger creates one journal entry line showing debits and credits for each account combination.
Audit Mode: Check this option to keep a record of how accounts from your subsidiary ledger map to accounts in your parent ledger. 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 ledgers' charts of accounts are mapped 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.
AutoPost: Check this option to automatically post your consolidation journals in the parent ledger. For more information, see: AutoPost.
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 ledger on the source and target instances share the same calendar, currency, and chart of accounts.
Note: The run options for the Remote Instance Signon only appear in the Run Options window for the Transfer Consolidation Data and Transfer Consolidation Data Sets windows.