1. R12 General Ledger Management Fundamentals
Consolidations
R12 General Ledger Management Fundamentals
<Course name> <Lesson number> - 1

2. <Course name> <Lesson number> - 2
Objectives
After completing this lesson, you should be able to:
Identify how the consolidation process is positioned within the Oracle General Ledger business flow
Identify the key implementation issues regarding consolidations
Identify the features and functionality of Global Consolidation System (GCS)
Describe the elements of the Consolidation Workbench
Create eliminating entries
Identify reports and inquiry options available for consolidations
<Course name> <Lesson number> - 2

3. Overview of Consolidations
With Oracle General Ledger, you can consolidate any number of subsidiaries that use different ledgers, even those with different charts of accounts, currencies, and calendars
Subsidiary 1
Subsidiary 2
Subsidiary 3
Parent
Run Consolidation
Overview of Consolidations
The consolidation process combines the financial results of different companies, typically combining subsidiary accounting information into a parent company for reporting purposes.
<Course name> <Lesson number> - 3

4. <Course name> <Lesson number> - 4
Consolidation Tools
You can use the method that best suits your needs to consolidate financial information.
Financial Statement Generator (FSG)
Global Consolidation System (GCS)
Consolidation Tools
Financial Statement Generator (FSG)
Use Financial Statement Generator (FSG) to consolidate financial information for businesses using a single ledger or businesses using different ledgers that share the same calendar and chart of accounts.
Use recurring journals, mass allocation journals, and standard journals to create intercompany elimination journal entries for multiple companies sharing the same ledger.
Global Consolidation System (GCS)
Use Global Consolidation System (GCS) to consolidate financial information for multiple ledgers, diverse financial systems, and geographic locations, including both Oracle and non-Oracle applications.
Use the Consolidation Workbench in GCS to:
Access windows used to perform each consolidation activity.
Monitor the status of your consolidation.
View history of past consolidations.
GCS
FSG
<Course name> <Lesson number> - 4

5. Consolidating Multiple Companies Sharing a Single Ledger
Parent company
Structure: Co - CC - Acct
Calendar: Monthly
Currency: USD
Use FSG to consolidate data
Subsidiary 1
Subsidiary 2
Subsidiary 3
Co-CC-Acct Monthly USD
Co-CC-Acct Monthly USD
Co-CC-Acct Monthly USD
Consolidating Multiple Companies Sharing a Single Ledger
Use the Financial Statement Generator (FSG) to create consolidated financial statements at the parent level if:
Your companies share the same ledger. Because all of your companies' information is already contained in the same ledger, you do not need to create mapping rules or transfer data. You simply need to enter the elimination journal entries to eliminate any intercompany transactions, then run FSG reports.
Your companies use different ledgers on the same database instance, that share the same chart of accounts and accounting calendar, but have different currencies. Because FSG reports can be defined across ledgers, you can still use FSGs to create consolidated statements. Simply run translation in the subsidiaries' ledger, then define FSGs across ledgers using the "Translated" currency type.
You can segregate eliminating entries by creating an elimination company and using parent/child hierarchies to address FSG consolidations.
For more information, refer to the Oracle General Ledger User Guide or 11i General Ledger Financial Management Fundamental Financial Reporting.
Use FSG to consolidate subsidiaries that share the same ledger
<Course name> <Lesson number> - 5

6. Consolidating Multiple Companies with Multiple Ledgers
Parent company
Structure: Co - CC - Acct - Prd
Calendar: Monthly
Currency: USD
Use GCS to map and consolidate
Subsidiary 1
Subsidiary 2
Subsidiary 3
Co-CC-Acct Quarterly USD
Co-Acct-Prd Monthly Euro
Co-Acct-CC-Prd Weekly AUD
Consolidating Multiple Companies with Multiple Ledgers
Companies do not share the same currency, calendar, or chart of accounts reside in separate ledgers, and, possibly, separate instances, or non-Oracle applications. With the Global Consolidation System, you can:
Consolidate the results of multiple organizations, with different ledgers that use different currencies, calendars, and charts of accounts.
Initiate consolidations from your parent ledger or subsidiary ledger.
Consolidate actual amounts as well as budget amounts.
Consolidate account balances or transactions.
Create automatic intercompany eliminations.
Note: You may use the Advanced Global Intercompany System (AGIS) to enter intercompany transactions. Then, you use GCS to create your eliminating entries.
Consolidate the results of multiple organizations on multiple database instances.
Note: If you want to consolidate budgets, your parent and subsidiary ledgers must share the same calendar and functional currency.
<Course name> <Lesson number> - 6

7. Global Consolidation System (GCS) Features and Benefits
Global Consolidation System provides:
A workbench to view the consolidation status of your subsidiaries
Sophisticated consolidation mapping rules to map accounts and specify transfer rules from the subsidiary to the parent
A color-coded consolidation monitor that guides you through the consolidation steps
A Consolidation Hierarchy Viewer to graphically display your consolidation structure
The Interface Data Transformer makes importing data from external feeder systems easier
Global Consolidation System (GCS) Features and Benefits
Consolidation Workbench:
View the status of your consolidation and monitor subsidiary account balances for any changes that occur after the subsidiary data has been transferred.
Mapping Rules:
Determine how your subsidiary account balances roll up into the parent.
State Controller:
Access to every form you need for consolidations and guides you through the consolidation process.
Consolidation Hierarchy Viewer:
View the multilevel structure of your consolidation mapping in a graphical format to see relationships and analyze ledger information.
Interface Data Transformer:
The Interface Data Transformer (IDT) is a user-friendly tool that makes importing of data from external feeder systems into Oracle General Ledger or Oracle Global Consolidation System much easier and less time-consuming.
<Course name> <Lesson number> - 7

8. Global Consolidation System (GCS) Features and Benefits (continued)
Global Consolidation System provides:
Automatic generation of eliminating entries
Multilevel drilldown capabilities to subsidiary balances and subledgers
Interface Data Transformer (IDT)
Powerful report publishing capabilities using FSG and Web ADI
Integrated multidimensional analysis using Oracle Enterprise Planning and Budgeting
Global Consolidation System (GCS) Features and Benefits
Automatic Elimination Entries:
Automatically generate journal entries to eliminate intercompany balances based on rules you define.
Multilevel Drilldown:
Drill down to access account balances, journal entries, and subledger transactions.
Reporting:
Generate standard or custom reports that can be published to a text file, spreadsheet, or web site for review and analysis.
Integrated Analysis:
Perform multidimensional analysis of consolidated financial data using Oracle Enterprise Planning and Budgeting.
Oracle Enterprise Planning and Budgeting is tightly integrated with Oracle General Ledger.
After consolidating your companies' information, you can analyze the data using multiple scenarios.
<Course name> <Lesson number> - 8

9. Consolidating Data in Multiple Instances
Use Web ADI or IDT to copy data from another instance to another
Oracle Instance A
Oracle Instance B
Web ADI Extract
"Subsidiary 1"
Web ADI Journal Entry Spreadsheet
Subsidiary 1 Ledger
Consolidate
Parent company ledger
Consolidating Data in Multiple Instances
If you have companies that do not share the same instance, you can do the following:
Revalue and translate subsidiary amounts if you want to normalize the currency to the parent's functional currency.
Run a trial balance in the subsidiary ledger and use the trial balance to create journal entries in a spreadsheet.
Use Web ADI to upload the journal entry created in the spreadsheet data to a dummy ledger defined in the parent company's instance.
Note: The dummy ledger is defined like any other ledger. The structure should match that of the original ledger in the other instance.
As an alternative to the Web ADI extract, you can also use SQL*Plus and load the contents of the flat file into the GL_INTERFACE table. You can then upload the data into the GCS instance using journal import. This method requires support from your MIS department.
After you have all the data in a single instance, you can:
Use GCS to map accounts from your dummy ledger to your parent ledger.
Transfer data.
Create eliminating entries.
Consolidate results.
Note: The same concepts apply for non-Oracle Instances. If you have subsidiary data using non-Oracle systems, you can map and load the data through Web ADI or SQL*Plus into the GL Interface table.
<Course name> <Lesson number> - 9

10. Interface Data Transformer (IDT) Description
User-friendly tool that facilitates the importing of data from external feeder systems into Oracle General Ledger and Global Consolidation System
GL_INTERFACE Table
External Data
IDT Rules Transform Data
External Data loaded into GL_Interface
GL Journals
Reformatted Data Imported to GL
Interface Data Transformer (IDT) Description
The Interface Data Transformer (IDT) is a user-friendly tool that makes importing of data from external feeder systems into Oracle General Ledger or Oracle Global Consolidation System much easier and less time-consuming.
IDT takes data from external feeder systems that have been loaded into the GL_INTERFACE table and transforms it into the proper format for import into Oracle General Ledger based on rules you define. Instead of having to manually map the values from the external system into a format acceptable by the target system, you can create Transformation Rules and apply them to the external data to have them automatically mapped for you. Each time you import data, you can simply reapply the same rules.
<Course name> <Lesson number> - 10

11. Interface Data Transformer (IDT) Benefits
Easier Integration with Non-Oracle Systems:
Automatic data conversion that converts disparate data formats into an Oracle format
Reapplication of the same rules each time you transfer
Automatic data validation on imported data provides greater flexibility!
Conditions allow you to control when Transformation Rules should be applied
Interface Data Transformer (IDT) Benefits
The following benefits can be achieved by using the Interface Data Transformer:
Interface Data Transformer makes importing data from Non-Oracle Systems much easier because it reduces the manual effort required to convert disparate data formats into a format Oracle recognizes and accepts.
By defining reusable rules, you can reapply the same rules each time you transfer data from external systems into Oracle General Ledger or Global Consolidation System.
You can feel safe that the data is valid and will not corrupt your existing data because IDT validates the imported data for you every time.
IDT is very flexible. By applying conditions, you can address those special circumstances and control when the Transformation Rules should be applied.
<Course name> <Lesson number> - 11

12. Interface Data Transformer (IDT) Rule Set Description
Rule Sets provide instructions to transform data in the GL_INTERFACE table:
Use String Functions to parse and concatenate substrings
Call PL/SQL Functions to perform sophisticated transformations
Reference Lookup Tables to convert one value into another
Interface Data Transformer (IDT) Rule Set Description
Rule Sets control how your data in the GL_INTERFACE table is transformed.
A rule set is composed of a stage, which is a grouping of rules.
The output of a stage in a rule set is used as an input in the subsequent stage.
Rules are composed of conditions, derivations, and a validation.
Conditions determine when a derivation should be applied.
A derivation can be performed either through string manipulation, a PL/SQL function, or through a Lookup Table.
Validation can be performed to check the results of a rule. You can use a value set or a lookup table to validate the results of a rule.
Users must first define a Ledger in Oracle GL to act as the target for mapping. The new Transformation Rule Set feature will allow users to transform data from a source to a target, regardless of the table structure of the source or target table.
<Course name> <Lesson number> - 12

13. Interface Data Transformer String Function Example
Parses and concatenates substrings
Column1
Column2
Column3
Column4
Source
100C B
540
20%
Column1 and Column2 are
concatenated, placing the
results in Column1.
Interface Data Transformer String Function Example
String functions enable you to parse and concatenate substrings. For example, you can take values from multiple columns in the external system and combine them into a concatenated value in the target system.
Target
100CB
Budget
108
20%
<Course name> <Lesson number> - 13

14. Interface Data Transformer PL/SQL Function Example
Performs sophisticated transformations
Column1
Column2
Column3
Column4
Source
Column3 is multiplied by Column4, placing the results in Column3
540 X 20% = 108
100C B
540
20%
Interface Data Transformer PL/SQL Function Example
PL/SQL Functions perform more sophisticated transformations, such as calculations. You can calculate amounts stored in separate columns in the external system and store the result in the target system.
Target
100CB
Budget
108
20%
<Course name> <Lesson number> - 14

15. Interface Data Transformer Lookup Table Example
Converts one value into another
Column1
Column2
Column3
Column4
Source
100C B
540
20%
A lookup table maps "B" to "Budget,"
placing the results in Column2
Interface Data Transformer Lookup Table Example
Lookup Tables convert one value into another. Thus if value "B" is specified in the external system, you can convert that value to "Budget" in the target system.
Target
100CB
Budget
108
20%
<Course name> <Lesson number> - 15

16. Interface Data Transformer Steps
Define Rule Set
Load Interface Table
Load the external data into the GL_INTERFACE table using SQL Loader or another program
Specify a Source and Group ID in the flat file
Run Transformer Program
SQL
Interface Data Transformer Steps
(N) Interface Data Transformer > Define
The first step is to define a Transformation Rule Set. Here, you specify how you want to transform the data using Lookup Tables, PL/SQL Functions, or String Functions.
Then you need to load your raw external data into the GL_INTERFACE table using SQL Loader or some other loader program.
Be sure to specify a Source and Group ID in your flat file. This information will be referenced when you apply the Transformation Rule Set to this data.
The last step is to run the program called GL Interface Data Transformer.
(N) Interface Data Transformer > Run
The GL Interface Data Transformer program takes the data in the GL_INTERFACE table and transforms it into the correct format based on your Transformation Rule Set.
Here, you can also choose to submit the Journal Import program. You can also run Journal Import separately after the transformation has occurred.
If there are any errors, you can correct them in the Correct Journal Import form and rerun Journal Import.
<Course name> <Lesson number> - 16

17. Other Uses for Global Consolidation System
Use Global Consolidation System (GCS) to transfer balances if you make changes to your chart of accounts or accounting calendar
Other Uses for Global Consolidation System
You can use the Global Consolidation System for other activities besides consolidation.
Changing Charts of Accounts
If you decide to change your chart of accounts after it has been implemented, you can use GCS to map account values from the old chart of accounts to the new chart of accounts.
To do this, you must:
Create a new ledger with the desired chart of accounts structure.
Use GCS to map account values from the old ledger' chart of accounts to the new ledger.
Transfer historical balances or transactions from the old ledger into the new ledger.
Changing the Accounting Calendar
If you change your accounting calendar after it has been implemented, you can use GCS to map account balances from the periods in the old ledger into the new periods in the new ledger. This is similar to the previous process used when changing your chart of accounts.:
Create a new ledger with the desired accounting calendar.
Use GCS to copy account values from the old ledger’s chart of accounts to the new ledger.
Transfer historical balances or transactions from the period in the old ledger to the period in the new ledger.
Considerations for Using GCS When Making Changes
GCS is particularly useful during implementations after you have uploaded historical balances into Oracle General Ledger. If the accounting calendar or chart of accounts changes, you can use GCS to perform account mapping and then transfer balances period by period into a new ledger.
Caution: If you decide to change your ledger after you have turned on Multi-Org for your subledgers and entered transactions using your subledgers, you should take additional precautions. Switching your ledger under these conditions may have serious ramifications to your data integrity because all historical subledger transactions point to the old ledger and all new subledger transactions point to a new ledger.
Using GCS with the Subledger Accounting
Companies using the Subledger Accounting Dual Posting solution can use Global Consolidation System (GCS) to transfer subledger transactions, other than Payables and Receivables transactions, to another ledger to create alternative accounting representations of their accounting data.
The Subledger Accounting Dual Posting solution enables you to transfer a single Payables or Receivables transaction to two ledgers that use different accounting rules. Subledger Accounting Dual Posting only addresses transactions from Payables and Receivables. Other transactions that require a second accounting representation can be transferred to the second ledger using GCS. Global Consolidation System (GCS) allows you to synchronize transactions between the source and target ledgers by allowing you to retain journal batch names and descriptions and allowing you to exclude the transfer of journals by journal category.
<Course name> <Lesson number> - 17

18. Consolidation Workbench
The Consolidation Workbench and State Controller provide a central point of control for consolidating an unlimited number of subsidiaries to your parent ledger
Access all
consolidation steps
Monitor consolidation
process
View mappings
and hierarchies
Consolidation Workbench
The Consolidation Workbench provides a central point of control for consolidating an unlimited number of subsidiaries to your parent. This window provides feedback on the state of the consolidation process, keeping you informed about each subsidiary's consolidation status. The workbench also monitors subsidiary account balances for any changes that occur after the subsidiary data has been transferred to your parent ledger.
Consolidation Sets
You can even create consolidation sets which launch multiple consolidations in a single step for overall streamlining of the consolidation process.
Consolidation Hierarchies
Finally, you can create consolidation hierarchies, or multilevel hierarchies, and view your consolidation hierarchies using a graphical Consolidation Hierarchy Viewer.
State Controller
From the Consolidation Workbench you can access the State Controller, which is a color-coded navigation tool to guide you through the consolidation process.
<Course name> <Lesson number> - 18

19. Consolidation Workbench (continued)
Find Consolidation Processes
Consolidation Workbench
Preparation/Transfer
Elimination
State Controller
Mapping
Mapping Set
Translation Status
Transfer
Transfer Set
Review Journal
Post
Elimination Set
Elimination
Report
Consolidation Workbench (continued)
(N) Consolidation > Workbench
When you navigate to the Consolidation Workbench, the Find Consolidation Processes window opens. This window works with the Consolidation Workbench to help you find consolidation and elimination processes. Enter a query in the Find Consolidation Processes window. The results are displayed in the Consolidation Workbench.
Using the Find Consolidation Processes Window
To narrow the search for a consolidation process, enter search criteria in as many of the following fields as you like:
Parent: Parent ledger.
Parent Period: Consolidation period.
Balance Type: Actual, Balance, or Any.
Mapping Set: Group of mappings.
Mapping: Single mapping.
Subsidiary: Subsidiary ledger.
Status: Consolidation status.
Elimination Set: Fully reciprocal elimination entries.
Elimination Status: List of eleven different status of eliminations.
Note: Using the Find Consolidation Processes window refreshes data displayed in the Consolidation Workbench. When you generate, post, or reverse consolidation journals, navigate to the Find Consolidation Processes window and select the Find button to refresh the data displayed. Alternatively, you can choose View > Find All from the menu bar.
<Course name> <Lesson number> - 19

20. Using the State Controller
Button Name
Consolidation Step
Mapping
Mapping Set
Map consolidation data
Translation Status
Prepare consolidation data
Transfer
Transfer Set
Transfer consolidation data
Review Journal
Post
Review and post to consolidate
data and update consolidated
balances
Elimination Set
Eliminate
Create eliminating entries
Using the State Controller
Use the State Controller as a short cut to navigate directly to consolidation mapping and elimination definition windows.
The State Controller buttons correspond to one of the functional steps of a consolidation so you can quickly access the consolidation step you want to perform.
When you select a subsidiary from the Consolidation Workbench, the State Controller buttons change color based on which steps you have performed or need to perform for the subsidiary.
Each button on the State Controller opens the related General Ledger window.
(N) Consolidation > Define > Mapping
There are navigation paths corresponding to the buttons that open General Ledger forms and windows:
Button—Mapping
General Ledger Window—Consolidation Mappings
Navigation—(N) Consolidation > Define > Mapping
Button—Mapping Sets
General Ledger Window—Consolidation Mapping Sets
Navigation—(N) Consolidation > Define > Mapping Sets
Button—Translation Status
General Ledger Window—Translation Statuses
Navigation—This is available only with the State Controller
Button—Transfer
General Ledger Window—Transfer Consolidation Data
Navigation—(N) Consolidation > Transfer > Data
Button—Transfer Set
General Ledger Window—Transfer Consolidation Data Set
Navigation—(N) Consolidation > Transfer > Data Set
Button—Review Journal
General Ledger Window—Enter Journals
Navigation—(N) Journals > Enter
Button—Post
General Ledger Window—Post Journals
Navigation—(N) Journals > Post
Button—Elimination Set
General Ledger Window—Elimination Set
Navigation—(N) Consolidation > Elimination > Define
Button—Eliminate
General Ledger Window—Generate Eliminations
Navigation—(N) Consolidation > Elimination > Generate
Button—Report (Standard)
General Ledger Window—Submit Request
Navigation—Reports > Request > Standard
Button—Report (Financial)
General Ledger Window—Run Financial Report
Navigation—Reports > Request > Financial
Report
Report on consolidated balances
<Course name> <Lesson number> - 20

21. State Controller Button Colors
Mapping
Mapping Set
Blue
Recommended
Translation Status
Gray
Not Recommended
Transfer
Transfer Set
Red
Warning
Review Journal
Post
Elimination Set
State Controller Button Colors
Selecting a State Controller button accesses the General Ledger window to complete that step. To help guide you in completing your consolidation steps, the State Controller buttons are displayed in one of three colors:
Blue - Recommended
Gray - Not recommended
Red - Warning
When you select a subsidiary from the Consolidation Workbench, the State Controller's buttons change color based on which steps you have performed or need to perform for that subsidiary. After you successfully complete a consolidation step, the State Controller buttons may change color to reflect the current status.
For example, the Review Journal button is light gray until data has been transferred. After the consolidation journal entry is generated, it appears in blue, to indicate that reviewing the consolidation journal is now a recommended step. If previously translated data has changed since the transfer, or the translation rate has changed, the translation status button turns red to warn you that you need to re-run translation.
Eliminate
Report
<Course name> <Lesson number> - 21

22. Defining a Consolidation Mapping
A consolidation mapping is a set of instructions for mapping accounts or entire account segments from a subsidiary ledger to the parent ledger
Define a consolidation mapping for each subsidiary you want to consolidate
Mapping Rules
Defining a Consolidation Mapping
(N) Consolidation > Define > Mapping
You must define or modify a consolidation mapping for each subsidiary ledger you want to consolidate. The mapping identifies the parent and subsidiary ledgers. The mapping rules control the consolidation of data into the parent ledger.
Consolidation mappings include identifying the parent and subsidiary, the method, currency, effective dates, consolidation run options, segment mapping rules, account mapping rules and usage type.
Selecting a Consolidation Method
When the consolidation is run, consolidation journal entries are created in the parent ledger.
Balances:
Select Balances to consolidate actual, average, translated, budget, or statistical balances. This method does not include journal entry detail. If you choose the Balances method, the resulting consolidation journal entries includes the account balances for all the subsidiaries that were run. For example, if a subsidiary had five transactions that made up the balance of the sales account, the consolidation journal entry includes the balance of the sales account, not the individual transactions.
Note: You must use this method if you want to consolidate balances from your subsidiaries' summary accounts.
Transactions:
Select Transactions to consolidate actual journal entry detail from a subsidiary ledger. This method allows you to selectively consolidate individual journal entries. This method is particularly useful if you want to make incremental updates if new journals are entered after you run consolidation. Instead of reversing the original consolidation batch, which is the case for the Balances consolidation method, you can transfer the additional journal entry and post it to update the consolidated balances. If you choose the Transactions method, the resulting consolidation journal entries include the transactions for all the subsidiaries that are run. For example, if a subsidiary has five transactions booked to the sales account, the consolidation journal entry includes the summation of all five transactions. If you want each transaction to be listed in the parent ledger as five separate transactions, you need to run the transfer five separate times.
Note: You can only use this method if both ledgers have the same functional currency.
If you have average balance processing enabled, your parent should be defined as a non-consolidation ledger with average balances enabled.
Entering a Currency
Enter the currency to use for the consolidation. This is the same as the functional currency for the parent. You can also select STAT.
Consolidating Books with Average Balance Processing Enabled
For average balance processing, optionally select a default Usage type such as standard, average, or both to transfer standard, average, or both balances to the parent ledger.
Hint: You can create separate consolidation mappings for standard and average balances. This is helpful if you want to use different mapping rules to get different levels of detail. For example, you might map standard balances to view consolidated totals for each cost center or average balances to view consolidated totals for each company.
Note: Standard defaults if you choose Transactions as the consolidation method. For more information, refer to the Oracle General Ledger User Guide or the 11i General Ledger Financial Management Advanced Topic Average Balance Processing.
Subsidiary
Ledgers
Parent
Ledger
<Course name> <Lesson number> - 22

23. <Course name> <Lesson number> - 23
Mapping Rules
You can define segment rules, account rules or a combination of both
If you use segment rules you must define a segment rule action for each segment in the parent's chart of accounts, but you cannot define more than one action
Account rules override segment rules, if there is a conflict. Suggestion:
Use segment rules to define the default mapping
Use account rules to define exceptions
Mapping Rules
Selecting a Mapping Rule
Select a Mapping Rule to specify how to consolidate balances or transactions from your subsidiary to your parent. Your choices include segment rules, account rules, or a combination of both.
Segment rules are preferable to account rules because:
Defining consolidation mapping is quicker and easier. For example, if your parent account has only three segments, you can map an entire subsidiary's chart of accounts with just three segment rules.
Running consolidations based on segment rules is faster than those based on account rules.
Changing Mapping Rules
Save your work after you have set up your consolidation mapping. Once saved, you cannot modify your rollup rules, except to change the parent and subsidiary segment detail values. To change a rollup rule, delete it and create a new one.
<Course name> <Lesson number> - 23

24. Using Account Mapping Rules
Account rules map a specific subsidiary account or range of accounts to a specific account in the parent ledger
Subsidiary
maps to
Parent
Low
High
Using Account Mapping Rules
Account Rules: Enter the Subsidiary Accounts and the Parent Account to which you want to map each subsidiary account range.
Example 1: Map subsidiary account to account in your parent ledger.
Example 2: Map the entire range of subsidiary accounts through to account in your parent ledger.
Note: Run new consolidations in audit mode to ensure that your account mappings are correct. The audit mode allows you to run several audit reports to help you verify that your mappings are set up correctly.
<Course name> <Lesson number> - 24

25. Using Segment Mapping Rules
Segment rules map subsidiary account segments to parent account segments
Subsidiary
Maps to
Parent
Department
Account
Product
Cost Center
Location
Using Segment Mapping Rules
Segment Rules
Enter the parent segment name to which each subsidiary is mapped, an Action, and the Subsidiary segment name. For example, you can map your subsidiary's Department segment to your parent's Cost Center segment. You can use only one action for each parent segment.
Mapping Rule Actions Rule Description
Copy Value From Copies all values in your subsidiary segment to the same values in your parent segment. The segments do not have to use the same value set, but must use the same segment values.
Assign Single Value Assigns one specific value that is used for the parent segment. You must enter the value that the parent chart of accounts uses. Use this rule when your parent account has more segments than your subsidiary account.
Use Rollup Rules From Maps values from your subsidiary segments to your parent segments using the rules specified in the Rollup Rules region.
<Course name> <Lesson number> - 25

26. Using Segment Rollup Rules
A rollup rule consists of the following:
Parent Segment
Detail Value
Transfer Level
Using
Subsidiary
Segment Parent
Value or
Segment Ranges
Subsidiary values rollup into the specified
parent detail segment value.
Specifies whether to rollup detail or
summary data.
Specifies whether Parent, Detail Ranges, or
Parent Ranges from subsidiary are mapped.
Dependent on Transfer Level selected.
• If you specify Parent in the Using field, enter
the parent account value for the subsidiary.
• If you specify Detail Ranges or Parent Ranges,
enter the account ranges for the subsidiary.
Rule
Description
Using Segment Rollup Rules
You must define a rollup rule for any segment value mapping rules that are assigned the action Use Rollup Rules From.
A rollup rule tells General Ledger what detail level of information to transfer and how to roll that information up into the parent. There are four rollup rules possible:
Transfer Level—Detail
Using—Detail Ranges
Results—Maps a range of detail values from subsidiary ledger into one detail value in parent ledger.
Using—Parent
Results—Maps a parent value from subsidiary ledger into a detail value in parent ledger.
Transfer Level—Summary
Results—Maps a subsidiary segment parent value into a segment value in parent ledger to consolidate balances from the summary account associated with the subsidiary segment parent value. This rollup rule can only be used with the Balances consolidation method.
Using—Parent Ranges
Results—Maps one or more ranges of subsidiary segment parent values into a segment value in parent ledger. This consolidates balances from the summary accounts associated with the subsidiary segment parent values. This rollup rule can only be used with the balances consolidation method.
<Course name> <Lesson number> - 26

27. Defining a Consolidation Mapping Set
Create a mapping set to transfer data for multiple subsidiaries simultaneously
Transfer to Parent Company Ledger
Mapping Set
Subsidiary 1 Mapping Rules
Subsidiary 2 Mapping Rules
Subsidiary 3 Mapping Rules
Defining a Consolidation Mapping Set
(N) Consolidation > Define > Mapping Set
Mapping Sets are create to transfer data for multiple subsidiaries simultaneously. After the Mapping Set is created the results can be viewed in the Consolidation Hierarchy Viewer.
<Course name> <Lesson number> - 27

28. Consolidation Hierarchy Viewer
Vision Corporation (UK) (Vision Corporate Mapping)
Currency: GBP
Calendar: Fiscal
Chart of Accounts: Co-Dept-Acct
Vision Operations (USA) (Vision Operations Mapping)
Currency: USD
Calendar: Accounting
Chart of Accounts: Co-Dept-Acct-Sub-Acct-Prod
Vision Services (USA) (Services to Corporate)
Calendar: Weekly
Chart of Accounts: Co-Serv Dept-Serv Acct-Prod
Vision Services (SNG) (Distribution to Corporate)
Currency: SGD
Chart of Accounts: Co-Dept-Acct-Prod + -
Consolidation Hierarchy Viewer
(N) Consolidation > Workbench (B) State Controller (B) Mapping Set (B) View Consolidation Hierarchy
The Consolidation Hierarchy Viewer displays your consolidation structure in a graphical format. You can easily access your consolidation structure, mapping, parent/subsidiary relationship, and ledger information, even for complex, multilevel consolidations that include intermediary parents.
You launch the Consolidation Hierarchy Viewer from the Consolidation Mapping Set window to display your multilevel consolidation structure in a graphical format. You can expand or collapse the hierarchy
There are three ways you can review consolidation hierarchies:
Ledger Only: Displays your hierarchy using only the company's ledger name plus the three components that make up that ledger: the currency, calendar, and chart of accounts structure.
Sets and Mappings Only: Displays your hierarchy using only the consolidation mapping rules name that comprises the mapping set.
Both: Displays your hierarchy using both the company's ledger name and components and the mapping rules name.
Note: You can only view consolidation hierarchies for consolidations in a mapping set.
<Course name> <Lesson number> - 28

29. Preparing Subsidiary Data
Before you transfer balances from a subsidiary ledger:
Revalue balances
Translate to functional currency
Run trial balance reports
Revalue balances
Preparing Subsidiary Data
Prepare your subsidiary data by revaluing and translating balances before you transfer the balances to your parent.
Revalue Balances:
If any of your ledgers have balance sheet accounts that have foreign currency balances, revalue the balances to reflect the impact of any changes in exchange rates. Post the resulting revaluation journal.
Translate Balances:
Select the State Controller's Translation Status button to check the current status of your subsidiary translations. If any of your subsidiary ledgers uses a functional currency different from your parent, you should translate the account balances before you transfer the subsidiary data to your parent ledger.
Note: Translation must be run in the subsidiary ledger the first time. Subsequent runs can be done from the Translation Status window.
Run Reports:
Run a trial balance report for each subsidiary ledger, using the parent ledger' functional currency.
Run after revaluation and translation have been processed in the consolidation currency.
Review the trial balance to ensure the data is accurate.
Use these reports to reconcile subsidiaries to the parent.
If subsidiary data has been translated, review the trial balance to ensure the data is accurate.
Translate balances
Subsidiary
Ledger
Run reports
<Course name> <Lesson number> - 29

30. <Course name> <Lesson number> - 30
Revaluation Process
Revaluation is the process that:
Reviews a foreign currency balance
Reconverts the functional currency using the Revaluation Rate
Creates a journal entry to adjust the functional balance to the reconverted amount
Foreign
currencies
Revaluation Process
Revaluation should be completed before translation so the values are correct before they are translated. The revaluation process performs the following:
Locates all accounts (within a range of specified accounts) in which all or a portion of the balance is derived from foreign currency transactions.
Revalues the foreign currency portion of the account balance using the revaluation rate defined in the Period Rates table. The Revaluation Rate is the inverse of the Period End Rate (expressed as 1/Period End Rate).
Calculates the difference between the current cumulative functional currency balance of these foreign transactions and the revalued functional currency balance calculated using the Revaluation Rate.
Creates an unposted journal batch to adjust the account balance to the new revalued balance. The offset account is the Unrealized Gain/Loss account specified when you run the revaluation process.
You must post the revaluation journal entries. Optionally, at the beginning of the next period, you can reverse the journal entries and revalue the balances again at the end of the next period.
Notes: Some companies do not reverse the revaluation journal and choose to only revalue the activity for the period. Also, revaluation is run each period until the obligation is settled. The Realized Gain/Loss is recorded by the appropriate subledger (Accounts Payable or Accounts Receivable) at the time the obligation is settled.
Functional
currency
<Course name> <Lesson number> - 30

31. <Course name> <Lesson number> - 31
Translation
Foreign currency translation is the process that restates the functional currency account balances into another currency
Subsidiary
functional
currency
Parent
functional
currency
Translation
If any subsidiary's ledger uses a functional currency different from the currency of the parent ledger, translate the account balances to the parent's functional currency before transferring them to the parent ledger.
The first time translation is run for a period, it should be initiated from the subsidiary. However, subsequent translations, if they are needed, can be initiated from the parent, using the State Controller Translate button.
Notes:
When running consolidation for the first time, it is best to consolidate Year-to-Date (YTD) amounts for balance sheet accounts to capture the subsidiary book's beginning balances. Period-to-Date (PTD) consolidation lacks the historical information needed to distinguish the translated beginning balances from the translation adjustment for the new rate.
For income statement account balances, run period-to-date (PTD) consolidation.
If the period rate changes, or additional data is posted to a subsidiary after translation has been run, the translation becomes obsolete. This is indicated by the red color of the Translation button. You need to retranslate the data, delete the previous transfer, then run the transfer again.
<Course name> <Lesson number> - 31

32. Transferring Subsidiary Data to Parent Ledger
You can transfer data from your subsidiary ledgers by:
Consolidating balances
Consolidating transactions
Transferring consolidation sets
Transferring Subsidiary Data to Parent Ledger
(N) Consolidation > Workbench
To transfer consolidation data to your parent ledger, use the Transfer button on the State Controller to launch a concurrent process.
You can optionally select the following Run Options:
Run Journal Import: Automatically creates journal entries in your parent ledger.
Create Summary Journals: Summarizes all journals lines for the same account into a single debit line and credit line.
Audit Mode: Creates an audit trail of transferred data that can be reviewed in Consolidation Audit Report, Unmapped Subsidiary Account Report, and the Disabled Parent Accounts Report.
Consolidating Balances
The mapping selected for consolidation must use the balances consolidation method in order to transfer balance data. When you submit the transfer process with the Run Journal Import option enabled, General Ledger creates an unposted consolidation journal batch in your parent ledger that includes all the valid accounts with the range selected for the transfer. If your consolidation range excludes some accounts from your subsidiary ledger, and consolidation is run in audit mode, you can review any excluded accounts in the Unmapped Subsidiary Accounts Report.
If you do not select the Run Journal Import option for your transfer, you must manually import the journal using the Import Journals window from your parent ledger.
Note: When running consolidation for the first time, you need to run a year-to-date (YTD) consolidation for balance sheet accounts. This allows you to consolidate the subsidiary's beginning balances. For each subsequent consolidation, run consolidation using PTD balances to get the net change for the period.
Consolidating Transactions
You can consolidate transactions only if the mapping you want to transfer uses the transactions consolidation method. In addition, you must use the Balance Type of Actual. For average balance processing books, you should consolidate into a non-consolidations ledger with average balances enabled.
In the Consolidation Workbench, select the consolidation mapping you want to run. General Ledger automatically enters Actual for the Balance Type, Standard for the Usage type, and PTD for the Amount Type. Then select the journal batches you want to consolidate. You can search subsidiary ledgers for all unconsolidated journal batches, previously consolidated batches or both.
Transferring Consolidation Set Data
If you have numerous subsidiaries, you can group them into a consolidation mapping set and then transfer the set to the parent ledger. You can use the Query Mappings button to review the mappings contained in a specific mapping set, the subsidiary period and date. Select the mappings you want to transfer by selecting the check box to the left of each mapping name. Then select the Transfer button to launch the transfer program.
<Course name> <Lesson number> - 32

33. Consolidation Tracking and Reversals
(N) Consolidation > Workbench (B) Find
Consolidation Tracking: The Transferred Balances column on the Consolidation Workbench indicates whether the balances for a mapping are current or obsolete. The workbench monitors subsidiary account balances for any changes that occur after the subsidiary data has been transferred to the parent ledger.
Consolidation Reversals: If you reverse a subsidiary consolidation process, the Status column displays Reversed for that process if all the following conditions have been met:
The original consolidation journal is posted.
A reversal of the original consolidation journal is generated and posted.
The order of the operations is not important. A reversal can be performed before posting the original consolidation journal, but all three operations must all be complete for a status display of Reversed.
Note: If you need to rerun consolidation or re-transfer data from your subsidiaries, be sure to reverse the original consolidation journal entries to avoid double-counting balances.
<Course name> <Lesson number> - 33

34. Posting Consolidation Journal Entries
Run Journal Import
Review
Posting Consolidation Journal Entries
After you have transferred subsidiary data to the parent ledger:
Run Journal Import, if not chosen as a consolidation run option.
Review the unposted consolidation.
Post the consolidation journal entries in the parent ledger. This launches a concurrent process.
Request standard or FSG reports to review the consolidated results.
Run Reports
Post
<Course name> <Lesson number> - 34

35. Global Consolidation System Cross Instance Data Transfer
Transfer Subsidiary Data
Remote Parent Instance
Cross Instance Data Transfer enables you to transfer subsidiary data to your remote parent instance over your corporate intranet
Global Consolidation System Cross Instance Data Transfer
Enterprises that manage their business operations in multiple database instances need an automated way to transfer data from remote subsidiary database instances to a central consolidation database instance.
The Global Consolidation System Cross Instance Data Transfer features the following:
Automatic transfer of consolidation data from one instance to another using database links
Import and post consolidation journals in one step
Notify users of the transfer status using Workflow Notifications
The Global Consolidation System facilitates the consolidation of data from remote subsidiary ledger database instances to a central consolidation database instance. Using database links, Global Consolidation System allows you to automatically transfer consolidation data from one instance to another, as well as optionally import and post the data automatically in the consolidation database instance. You no longer have to manually transfer consolidation data files from the remote subsidiary instances to the consolidation database instance and manually import and post the data into the parent ledger. 
This feature automates the entire process and also includes workflow notifications providing notification of the cross instance consolidation status.  Global companies with operations on multiple database instances can use this feature to consolidate their subsidiaries in a more efficient and automated manner.
<Course name> <Lesson number> - 35

36. Cross Instance Data Transfer Security
Using Cross Instance Data Transfer Security:
You create a specific username for the central consolidation database instance with limited access to specific objects in the database
Subsidiaries use this username to define database links for cross instance data transfers
Cross Instance Data Transfer Security
Global companies with operations on multiple database instances require security of database objects from unauthorized users to do the following:
Prevent users from modifying tables and other objects in the parent consolidation instance
Limit users to only transferring, importing, and posting consolidation data
Using this security, there is no need to re-enter your username and password every time you transfer consolidation data, saving time and redundancy. And, the username/password is now validated at the time you sign on to Oracle Applications.
<Course name> <Lesson number> - 36

37. Global Consolidation System Parallel Consolidation
Parallel Consolidation enables organizations to:
Run multiple concurrent consolidation processes in parallel for different subsidiaries
Uses separate GL_INTERFACE tables to increase processing speed
Must select the Run Journal Import option in the Transfer Consolidation Data or Transfer Consolidation Data Set forms
Global Consolidation System Parallel Consolidation
Global companies who transfer data for a large number of subsidiaries want to:
Improve the performance of consolidation transfers from different subsidiaries
Speed the close process by running consolidation transfers in parallel
Global Consolidation System Parallel Consolidation allows users to run multiple concurrent consolidation transfer processes in parallel for different subsidiaries and to consolidate a high volume of detail.  The Global Consolidation System Parallel Consolidation feature takes advantage of using separate GL_INTERFACE tables to speed up the transfer and import of consolidation data into the target ledgers using multiple parallel processes. This allows global companies, who often need to transfer data for a large number of subsidiaries, to increase processing efficiency and save time during the critical close process. 
To use Global Consolidation System Parallel Consolidation, you must select the Run Journal Import option in the Transfer Consolidation Data or Transfer Consolidation Data Set forms.
<Course name> <Lesson number> - 37

38. Creating Eliminating Entries
Company A
Company B
Creating Eliminating Entries
There are several methods you can use to create eliminating entries in your consolidated parent or elimination ledger.
Use the Automatic Intercompany Eliminations to create elimination sets. Elimination sets are used for fully reciprocating eliminations. For example, use elimination sets to fully offset each subsidiary's Intercompany Payables and Intercompany Receivables accounts.
Other options for eliminating entries are to use Oracle General Ledger's journaling features to do the following:
Create recurring journal entries for eliminations that are not fully reciprocated. Recurring journals allow you to create formula-based eliminations that only partially offset intercompany transactions, such as minority interest eliminations.
Create standard journal entries to eliminate intercompany balances.
Create elimination journal entries in Web ADI. Use the power of Excel to enter elimination entries, link worksheets and create complex calculations. You can upload them from Web ADI, then post them in Oracle General Ledger.
Note: If you want to segregate elimination entries from operational accounting entries, you should create a single elimination company. For example, if you have Company 01, 02, and 03, create a fourth elimination company, such as Company 99. Enter all eliminating entries using the elimination company. Then you can report consolidated results before and after eliminations.
<Course name> <Lesson number> - 38

39. Formula-Based Eliminations
Use recurring journal entries set up with specific formulas or partial eliminating entries, such as those for:
Intercompany profit eliminations
Minority interest eliminations
Cross-ownerships
Intercompany transactions with partially owned subsidiaries
You cannot use the Automatic Intercompany Eliminations program to eliminate formula–based eliminations or average balances
Formula-Based Eliminations
Recurring journals must be used to eliminate average daily balances. For more information, refer to the Oracle General Ledger User Guide or the 11i General Ledger Financial Management Advanced Topic Average Balance Processing.
<Course name> <Lesson number> - 39

40. Automatic Intercompany Eliminations Program
Define Elimination Set
Run Elimination
Target Account in Parent or Elimination Company
Source Account from Subsidiary
Source Account from Subsidiary
Target Account in Parent or Elimination Company
Automatic Intercompany Eliminations Program
The Automatic Intercompany Eliminations program eliminates intercompany balances. It is used only for fully reciprocating eliminations that repeat every accounting period.
To use this program create an elimination set. An elimination set is a batch of one or more related elimination entries. If an elimination company is used as the target company when booking elimination entries, you must specify the balancing segment value for the elimination company.
The Automatic Intercompany Eliminations program automatically generates eliminating entries per the rules specified in the Define Elimination Accounts window.
An elimination set is defined with a source account to eliminate, and a target account to eliminate it into.
When the elimination is run, journal entries are created for all values in the source account to zero them out and post them to the target account.
You can use the Consolidation Workbench and State Controller to track the elimination status of elimination sets and post any generated elimination sets.
<Course name> <Lesson number> - 40

41. Defining an Elimination Set
Required Components:
Batch name
Description
Elimination journals
Currency
Amount type
Source Account
Type Account
Optional Components:
Elimination company
Track Elimination Status
Effective From and To dates
Balancing options
Defining an Elimination Set
Elimination sets can contain a single eliminating journal entry, or a group of related elimination entries.
Elimination entries are comprised of individual lines mapped to fully eliminate balances from source accounts to target accounts.
Note: You cannot use the Automatic Intercompany Eliminations program to eliminate average balances.
Elimination Set Components
Elimination Company:
Choose a balancing segment value to represent the elimination company. This company is used as the target company when booking elimination entries and the value cannot be overridden. You can leave this field blank if you do not wish to use an elimination company. If you leave this field blank, the balancing segment value of the target account is used.
Track Elimination Sets:
If you want the elimination set to be part of the checklist for determining which eliminations are completed for the period, select the Track Elimination Status check box.
Period Last Run:
General Ledger populates this field to indicate the period in which you last executed an elimination set.
Effective From and To dates:
Enter a range of effective dates that includes only those periods for which you want the eliminating entry to be used. Oracle General Ledger generates eliminating journal entries only when you choose a date that falls within the Effective Dates range.
Currency:
Select the functional currency of the parent ledger or STAT. The currency you specify is for both source and target accounts.
Amount Type:
Enter period-to-date, (PTD), quarter-to-date (QTD), year-to-date (YTD), or project-to-date (PJTD). Average Balances cannot be used.
Source Account:
The Source Account balance is fully eliminated into the target account. The elimination program takes the negative balance of the source account and places the balance in the target account. For each account segment, choose a detail account value, a parent value, or leave the segment blank.
Note: Use parent values to reduce account maintenance because the elimination set automatically accommodates changes in the child values associated with a particular parent value. Parent values save you time in defining elimination sets because you can specify one elimination line which includes the parent value, instead of multiple lines for each child value. If you use parent values, the elimination functionality automatically loops through each of the child values for those segments and creates its detailed or summarized offset in your elimination journal.
Target Account:
Specify a target account for your elimination entry. For each account segment, choose a detail account value or leave the segment blank.
Note: If you specify an elimination company in the Elimination Sets window, the balancing segment value for the target account is set for you. You cannot override this default. If you do not specify an elimination company in the Elimination Sets window, the source account balancing segment value defaults as the target balancing segment value and you can override this value.
Specifying an Elimination Company
If you specify an elimination company in the Elimination Sets window, the balancing segment value for the target account is set for you. You cannot override this default.
If you do not specify an elimination company in the Elimination Sets window, the source account balancing segment value defaults as the target balancing segment value and you can override this value.
<Course name> <Lesson number> - 41

42. Source and Target Account Examples
If Source Account
Is mapped to Target Account
The outcome is
Null
Source accounts 100, 200, 300, and 400 eliminate into individual target accounts 100, 200, 300, and 400
100
Source accounts 100, 200, 300, and 400 eliminate into target account 100
200
Source account 200 eliminates into target account 200
999
Source accounts 100, 200, and 300 (children of 999) eliminate into individual target accounts 100, 200, and 300
Source account 200 eliminates into target account 100
Source accounts 100, 200, and 300 (children of 999) eliminate into target account 100
Parent Cost Center 999
100
Child Accounts
200
300
400
Source and Target Account Examples
The examples above illustrate how various mapping rules work based on the account structure shown above for a single account segment, in this case, the cost center segment. The same concepts apply to all segments in your chart of accounts.
The parent cost center 999 has three child accounts, 100, 200, and 300. Cost center 400 does not have a parent.
<Course name> <Lesson number> - 42

43. Balancing Options for Eliminations
Outcome
Allow out of Balance
Journal
Balance with Net
Differences Account
with threshold rules
Allows out of balance journal entries
to be created. Journal review required.
Difference in out of balance journals are posted to net difference accounts you specify for debits and credits. Threshold rules can be applied.
• If the difference < threshold, a balanced
journal entry is created with the
difference posted to the net difference
account.
• If difference > threshold, an out of
balance journal entry is produced for
your review. _
Balancing Options for Eliminations
If elimination journals are out of balance, you can specify balancing options to either allow out of balance journals to be created or to post the net difference to an alternative account.
Balancing options apply to all journals created for the elimination set.
Allow Out of Balance Journal: Allows the creation of an unbalanced journal entry to be reviewed and corrected before posting.
Balance with Net Difference Account: Specifies an account template to use if the difference is a net debit or credit.
In addition, threshold rules can be applied to prevent the automatic balancing of elimination journals if the net difference exceeds a specific amount, a percentage of a particular account, or a percentage of the journal.
Enter one of the following parameters to specify the threshold amount:
Constant amount: Specify a fixed amount
Percentage of account: Enter a number and an account. The number represents a percentage of the period-to-date (PTD) balance of the selected account. This account must be a detail account.
Percentage of journal: Enter a number that represents the percentage of the lesser total debit or total credit of the unbalanced journal.
If multiple balancing segments are involved, General Ledger creates specific balancing accounts by balancing segment value.
<Course name> <Lesson number> - 43

44. Allow Out of Balance Journal
Elimination Journal Entry
DR CR
I/C AR
I/C Sales 87
Out of Balance
Review and analyze difference
<Course name> <Lesson number> - 44

45. Balance with Net Difference
Elimination Journal Entry Balance with Net Difference Account Threshold = 5
DR CR
I/C AR 205
I/C Sales 199
Out of Balance 6
Review and analyze difference
Elimination Journal Entry Balance with Net Difference Account Threshold = 15
DR CR
I/C AR
I/C Sales
Net Difference Account
Balance with Net Difference
If you use the Balance with Net Difference option, you can select different net difference accounts for debit differences and credit differences.
You can also enter threshold rules with the Balance with Net Difference option:
If the difference does not exceed the amount specified in the threshold rule, the elimination journal is automatically balanced.
If the difference exceeds the amount specified in the threshold rule, you can examine the difference in the out of balance journal entry and decide what needs to be done.
<Course name> <Lesson number> - 45

46. Consolidated Balances Inquiry
From your consolidated parent ledger, you can view consolidated balances, journals, subsidiary details, and subledger details
Total Consolidated Sales
Total Sales – Company A
Sales Account 2
Sales Account 1
Consolidated Balances Inquiry
With General Ledger's drill down functionality, you can view any subsidiary, account, journal, or subledger transaction. From your parent ledger, you can drill between:
Consolidated and subsidiary entities
Detail accounts and journal entries
Summary and detail account balances
Journals and subledger transactions
Note: To be able to use drill down, select the Import Journal References check box in the Journal Sources window, in the parent ledger, for the consolidation journal source. To drilldown to subledger transactions, you must also select the Import Journal References check box for each subledger source.
Drilldown Example
Suppose while analyzing total consolidated sales in your parent ledger, you want to determine how much each subsidiary contributed to the total amount. You drill down from the consolidated sales balance to any subsidiary sales account balance. From there, you can view account details and journal entries. If you need further information, drill down further to the Accounts Receivable subledger transactions that contributed to your total consolidated sales balance.
A/R
Subledger
A/R
Subledger
<Course name> <Lesson number> - 46

47. Performing Consolidated Balances Inquiry
Consolidation
Subsidiary
Source Account
Display
translated
currency
Display
original
currency
Switch
amount
type
Performing Consolidated Balances Inquiry
(N) Inquiry > Account
Perform an account inquiry in your consolidated parent ledger.
Select the Show Journal Details button to drill down to the Journals window.
Search for journal batches with a journal source of Consolidation to locate your consolidation journal entries.
Select the Drilldown button to open the Consolidation Drilldown window.
Select Detail Translated Balances button to view the translated balance amounts.
To view amounts in original currency entered, select the Entered Balances button.
To change the amount type to Year-to-Date (YTD), Period-to-Date (PTD), Quarter-to-Date (QTD), or Project-to-Date (PJTD), select the Switch Amount Type button.
<Course name> <Lesson number> - 47

48. Running Consolidation Reports
You can generate standard consolidation reports from the State Controller or Submit Request window
Consolidation Audit Report
Consolidation Exceptions Reports:
Unmapped Subsidiary Report
Disabled Parent Accounts Report
Consolidations Rules Report
Consolidations Journals Report
Running Consolidation Reports
Select the Report button on the State Controller to submit standard consolidation reports.
Consolidation Audit Report:
Use this report to review the mapping of account balances from your subsidiary ledger into accounts in your parent ledger for a specific consolidation mapping. It reports the total of all subsidiary account balances that were consolidated into each account in your parent ledger.
Consolidation Exception Reports
Unmapped Subsidiary Report—Use this report to determine if your consolidation is complete prior to posting. It reports any subsidiary accounts, included in the account range you specified for your consolidation transfer, with non-zero balances that were not consolidated into your parent ledger because the accounts were not mapped.
Disabled Parent Account Report—Use this report to review all disabled accounts in your parent ledger for which you tried to consolidate balances or transactions.
Consolidation Rules Report—This report prints the segment and account rules defined for a specific consolidation mapping.
Consolidation Journals Report—This report lists subsidiary journal lines and the parent accounts used for your consolidation. Use this report to review journal batches consolidated across multiple ledgers. You must run this report from your parent ledger. You can only run this report if your consolidation uses the Transactions method and you do not select the Create Summary Journals option.
Notes:
The Consolidation Audit Report, Unmapped Subsidiary Report, and Disabled Parent Account Report are available only if you select the audit mode run option when transferring your subsidiary data.
<Course name> <Lesson number> - 48

49. Creating Custom Consolidation Reports
To define customized consolidation reports, use Web Applications Desktop Integrator (Web ADI), or Financial Statement Generator (FSG)
Creating Custom Consolidation Reports
You can use Financial Statement Generator (FSG) or Web Applications Desktop Integrator (Web ADI) to define custom consolidation reports for your parent ledger. You can report on multiple ledgers in the same report as long as each ledger shares the same account structure and calendar.
<Course name> <Lesson number> - 49

50. <Course name> <Lesson number> - 50
Summary
In this lesson, you should have learned how to:
Identify how the consolidation process is positioned within the Oracle General Ledger business flow
Identify the key implementation issues regarding consolidations
Identify the features and functionality of Global Consolidation System (GCS)
Describe the elements of the Consolidation Workbench
Create eliminating entries
Identify reports and inquiry options available for consolidations
<Course name> <Lesson number> - 50