Performing Financial Consolidations

This chapter provides an overview of consolidations with related equitization functionality and discusses how to:

• Determine consolidation ChartFields.

• Select an approach to intercompany and intracompany transactions.

• Define consolidation trees.

• Set up elimination units.

• Specify consolidation ledgers.

• Define elimination sets.

• Define subsidiary ownership and minority interest sets.

• Set up consolidation sets.

• Use ChartField value sets.

• Perform consolidation.

• Consolidate across summary ledgers.

• Map dissimilar charts of accounts.

• Use equitization.

• Define business unit trees and elimination units for equitization.

• Specify ledgers for each business unit in an equitization.

• Define ownership sets for equitization.

• Define equitization rules.

• Define an equitization group and journal options.

• Perform equitization.

• Produce consolidation and equitization reports.

• Use the ledger interface utility.

Understanding Consolidation and Equitization

This section discusses:

• Organizational structure and consolidations.

• Elimination of intercompany transactions.

• Elimination of intercompany investments and calculating minority interests.

• Components of the consolidation process.

• Incremental processing of Consolidations.

• Equitization and Changes in Subsidiary Ownership.

• TimeSpans in the Consolidation and Equitization Processes.

• Effective Dates and Ownership Sets in Consolidation and Equitization.

Organizational Structure and Consolidations

Organizations often have complex structures with multiple business or operating units and legal entities with varying degrees of ownership. If your organization comprises more than one business unit or operating entity, you can consolidate these organizations when you report on overall operations, presenting financial statements that accurately describe your financial status.

For example, assume Consolidated Manufacturing is a multinational company that has a controlling interest in a United States business, as well as numerous other subsidiaries worldwide. The balance sheet for Consolidated Manufacturing lists its United States investment as an asset. Consolidated Manufacturing also owns several buildings used by subsidiaries that record the payment of rent to corporate headquarters through intercompany accounts. While these companies are separate legal entities, they represent one unified economic entity. To gain a complete picture of the entire organization, you combine (consolidate) all the assets and liabilities of each business unit, eliminating intercompany transactions and minority interest relationships by creating consolidation elimination journal entries.

You use trees to define the relationships among business units in a consolidation, creating a separate consolidation tree for each configuration. Included in each consolidation tree are the business units being consolidated and the elimination units to which eliminating journal entries are directed.

In the following example operating business units 1 and 2 are consolidated in consolidated business entity B and operating business units 3 and 4 are consolidated in business entity D. Consolidated entity D is further consolidated with an additional operating business unit not directly related to business unit 3 and 4 to consolidated business entity C. Finally, the consolidated business entities B and C are combined in the overall consolidation business entity A.

Consolidate any combination of business units

Elimination of Intercompany Transactions

While there may be situations that require you to report gross consolidations (combining business unit ledger balances without eliminations), in most cases, you want to eliminate or cancel out the effect of intercompany transactions.

In General Ledger, you can track intercompany transactions using Due From and Due To accounts that are automatically created by the Journal Edit process, which calls the Inter/IntraUnit Processor. These Due From and Due To rows in the ledger are candidates for elimination when you run the Consolidations process. The following example shows such a transaction when company B0002 buys software for company B0001:

When the transactions are exclusively within the organization, you can eliminate the whole transaction when you set up your Consolidations process. In the following example, Company B0001 sold services to Company B0002. The Revenue and Expense accounts need to be eliminated in addition to the Due From and Due To accounts:

Using the Affiliate ChartField with a Single Due From/To Account

The Affiliate ChartField is specifically reserved to map transactions between business units when using a single intercompany account. This table provides an example of intercompany payables and receivables among three business units that each use the Affiliate ChartField:

Using Different Due From/To Account Values

Another method of tracking activity between business units is to use different ChartField values—typically different accounts—for intercompany transactions. Instead of using the Affiliate ChartField, you could use the following accounts to identify the same transactions that were shown in the previous exhibit:

In both examples, the same accounting information is present, but fewer account numbers are required when the Affiliate ChartField is populated. This also means that you need to define fewer elimination sets. An elimination set represents a related group of intercompany accounts that record both sides of each transaction between units.

In the case of the following intercompany receivable and payable relationship, you require only one elimination set if you use the Affiliate ChartField:

If you do not use the Affiliate ChartField, three elimination sets are required:

See Also

Defining Elimination Sets

Using Inter/Intraunit Processing in General Ledger

Using Interunit and Intraunit Accounting and ChartField Inheritance

Elimination of Intercompany Investments and Calculating Minority Interests

In consolidating the books of a subsidiary with those of the parent company, you credit the parent with the portion of the subsidiary that it actually owns and exclude what outside investors own. The value of minority interests is reported in terms of the aggregate net assets (equity) rather than in terms of a fractional equity in each of the assets and liabilities of the subsidiary.

To reflect minority interest, General Ledger generates an adjustments entry that debits the investment of the parent in the subsidiary account and credits a minority interest account. The system calculates the adjustment by multiplying the percentage of minority interest in the subsidiary by the total equity of the subsidiary.

Effectively, the combined result of the adjustments and eliminations entries is to express the value of the parent investment in terms of the assets and liabilities of the subsidiary offset by a minority interest liability. The equity ownership for each subsidiary in the consolidation is eliminated, with only the parent company's equity accounts and minority interest account remaining. Consolidated capital stock and retained earnings is equal to the balances of the parent.

Components of the Consolidation Process

Consolidations are made up of four elements: data, scopes, rules, and process.

Incremental Processing of Consolidations

PeopleSoft Enterprise General Ledger provides incremental processing of consolidations by recognizing lower level tree nodes that were previously processed when running the current consolidation. The Consolidation process uses the Consolidation Set, As Of Date, currency, and tree name of the process request to identify the tree nodes that have been processed, thereby enabling processing of only the nodes under a specified higher-level tree node that have not yet been processed. Incremental processing of consolidations enables you to consolidate in stages while avoiding reprocessing of portions of the overall organization that have already been successfully consolidated.

When reprocessing a consolidation that was previously run (commonly done for late transactions or discovery of errors) and you need to reprocess lower-level nodes, you can select the Undo Previous Process and the Include All Lower Level Nodes check boxes on the Consolidation Request page. When you select the Include All Lower Level Nodes check box, the undo process identifies all previously processed lower-level nodes and reverses them. If this option is not selected, the undo process only reverses the entries that were created from a single process by matching Consolidation Set, As Of Date, currency, tree name, tree level, and tree node as indicated on the current run control.

Equitization and Changes in Subsidiary Ownership

The Equitization process generates the entries to reflect the equity pickup of subsidiary earnings on the parent's books. It updates the value of the parent's investment and equity income accounts for changes in the subsidiary's value. When the value of an investment in a subsidiary changes for a parent company during the fiscal year, often it is without a physical event (transaction) having been recorded; however, the value of the investment of the parent in the subsidiary must be modified. You can use the PeopleSoft Equitization process when no physical accounting event will have occurred, but the value of the parent investment in the subsidiary has changed.

For example, net income or net loss of a subsidiary increases or decreases the investment value and affects the equity of the parent in that subsidiary.

PeopleSoft General Ledger enables you to set up multiple equitization rules for multiple business units that have complex parent-subsidiary relationships and create journal entries to record the changes within a single process. A ledger for a parent entity can be different from that of its subsidiary but you have the option to generate elimination entries for consolidated reporting.

Equitization can be run alone or in conjunction with consolidation and can share the consolidation tree with the Consolidations process, as well as the ownership sets.

Note. Equitization supports only the Business Unit field as the processing entity. This is unlike the Consolidation process, which allows consolidation of fields other than business unit, such as the Operating Unit field.

TimeSpans in the Consolidation and Equitization Processes

You can specify a TimeSpan on the Consolidation Set and the Equitization Group to indicate the type of balances to be posted for consolidation and equitization. If the TimeSpan is a year-to-date type of TimeSpan (for example, BAL), then a valid Journal Reversal Option should be selected; otherwise, there should be no reversal of the consolidation or equitization entries if they are intermediate periods. This is because distinct periods are consolidated that do not include prior periods in the current process. A warning message is issued by the system if the reversal option is selected with a TimeSpan option other than BAL.

Using intermediate TimeSpans (other than year-to-date types) is generally more efficient for processing consolidation and equitization; however, exercise caution when using non-year-to-date type TimeSpans. If changes have been made in ledgers for accounting periods that were previously processed for intermediate periods, it will be necessary to reprocess consolidation and equitization for those periods.

The following conditions must be met to have valid TimeSpans for Consolidation or Equitization:

• The TimeSpan calendar must be the same as the Calendar for the Business Unit and Ledger Group to be processed.

• The TimeSpan must be for the current year, that is, the Start Year and End Year must be 0, with Type defined as Relate to Current Year.

• If the Time Span is a year to date time span for the Consolidation Set and the Equtization Group, then the reversal option must be either the Beginning of Next Period or the End of Next Period. For any TimeSpan other than BAL or YTD, the reversal option must be Do Not Generate Reversal.

Note. Incremental processing of consolidations occurs regardless of what TimeSpan is selected for processing. Incremental processing is not available for the equitization process.

Effective Dates and Ownership Sets in Consolidation and Equitization

Consolidation and Equitization support the use of multiple effective-dated subsidiary ownership sets. Effective dates dictate to which period of the fiscal year a certain ownership set is applied. There are two options for selecting the dates within the Consolidations Set and Equitization Group:

• By Period End Dates.

• By Process Request as of Date.

If you choose to select ownership sets by Period End Dates, the process selects the effective ownership date to use based on each accounting period being processed.

Adjustment Periods are processed with the current (latest) accounting period.

The effective ownership date can also be determined By Process Request As of Date and only the most recent Ownership Set definition is used. Regardless of the option selected, the journals that are created by the consolidation process are dated as of the process request date.

When changing parents and percentages, always add a new effective dated row for the new ownership set so as not to change history. That is to say, do not change the effective date on an existing ownership set that has been used in a previous run if you want to retain the consolidated information, nor should you change the subsidiary entity on an existing ownership set.

Common Elements Used in This Chapter

Determining Consolidation ChartFields

You can base your consolidations on the business unit or another ChartField.

This section discusses how to:

• Consolidate on business unit.

• Consolidate on a ChartField other than business unit.

Consolidating on Business Unit

Although you can consolidate based on any ChartField, General Ledger is delivered with consolidations enabled for the business unit. If you use a different ChartField for your consolidations, substitute that ChartField name when you see a reference to business unit.

Consolidating on a ChartField Other Than Business Unit

For some organizations, the system is set up to use ChartFields such as operating unit or department instead of business unit to function as separate units. Because they are all conducting the same or similar business practice and have the same structure, all the units are under one PeopleSoft business unit setup. Transactions between these operational units are recorded and need to be eliminated for financial reporting of the business unit. General Ledger enables you to set up the consolidation among the operational units the same way you would to consolidate among business units.

For example, to consolidate on the operating unit ChartField:

1. If you are using an affiliate field to mark interoperating unit transactions, activate the Operating Unit Affiliate field on the Standard ChartField Configuration page, and associate the Operating Unit field to it.

2. Add operating units that function as the elimination operating units to the operating unit definition.

   Assign the attribute ELIM_UNIT equal to Y for these elimination units.

3. Build a consolidation tree that rolls up operating unit values, including regular and elimination operating units.

4. Set up elimination sets.

   When you define an elimination set using the Affiliate approach, do not include the ChartField on which you are consolidating.

5. Set up the consolidation set.

   Specify Operating Unit in the Entity field, and enter the business unit for the operating units.

6. Define and process a consolidation request.

7. Create reports that are based on the consolidation tree to show consolidated results.

See Also

Elimination of Intercompany Transactions

Summarizing ChartFields Using Trees

Enterprise PeopleTools PeopleBook: PeopleSoft Application Engine, "Using Meta-SQL and PeopleCode"

Enterprise PeopleTools PeopleBook: PeopleSoft Tree Manager, "Creating Trees"

Selecting an Approach to Intercompany and Intracompany Transactions

You can record activity between business units with the use of the Affiliate ChartField or with separate accounts. The Affiliate ChartField maps transactions between business units while using a single intercompany account. Alternatively, you can use different ChartField values, typically different accounts, for intercompany transactions.

If the consolidation is on business unit, the consolidation process assumes that it is an intercompany consolidation, and the affiliate is the Affiliate field name.

If the consolidation is on anything other than business unit, the process assumes that it is an intracompany consolidation within a single business unit. For intracompany elimination when the Affiliate method is used or where the Affiliate field is required for querying the ledger data, the field name is the associated affiliate field for that ChartField, as defined on the Standard ChartField Configuration page.

See Also

Using Interunit and Intraunit Accounting and ChartField Inheritance

Using Inter/Intraunit Processing in General Ledger

Elimination of Intercompany Transactions

Defining Consolidation Trees

You define a consolidation based on relationships among the business units and their related elimination units (units to which eliminating journal entries are directed). Each consolidation hierarchy uses a separate consolidation tree. You can consolidate an unlimited number of business units within each tree, and you can define an unlimited number of consolidation trees.

This section discusses how to:

• Define consolidation scopes with trees.

• Add detail values.

Defining Consolidation Scopes With Trees

Because you likely have several consolidation configurations to accommodate management and statutory requirements, General Ledger enables you to set up any number of consolidation trees. Consolidated business entities appear as nodes, and business units and eliminations units appear as detail values on the tree.

For example, World Wide Consolidation comprises 22 business units in Europe, Asia Pacific, and North America. For financial reporting requirements, the company created a tree that defines the legal entity relationships among these business units, as well as those located elsewhere (Tree Manager, Tree Manager).

The World Wide Consolidation node (WW_Consolidation) represents the final point of consolidation and the relationship among consolidated entities—Europe, ASIA/PAC, and NORTH_AMERICA—and the corporate level elimination unit, ELIM1.

Adding Detail Values

The detail values in a Consolidations tree always consist of the ChartField values that form the basis for consolidation and elimination units. Elimination units are stored in the same table as consolidating ChartField values because they share identical attributes; that is to say, if your consolidating ChartField values are business units, the elimination entities are also defined as business units.

In such a case, the system maintains all your detail values in the general ledger Business Unit table. You can, however, set up consolidations based on any other ChartField.

See Also

Summarizing ChartFields Using Trees

Setting Up Elimination Units

With Consolidations, you can automate intercompany eliminations and more accurately analyze consolidated results. When you consolidate business units, the system creates eliminating journal entries. Eliminating journals are directed to an elimination unit, a type of business unit that is designed specifically to support consolidated reporting.

Eliminating journal entries are directed to the elimination unit

The consolidated business entity does not have its own ledger. It is actually a reporting construct made up of the combined ledger balances of the selected business units and the intercompany offset amounts posted to the ledger for the elimination unit.

This section discusses how to:

• Add an elimination unit.

• Assign ledgers to elimination units.

Page Used to Add an Elimination Unit

Adding an Elimination Unit

Access the General Ledger Definition - Definition page (Set Up Financials/Supply Chain, Business Unit Related, General Ledger, General Ledger Definition, Definition).

Add and maintain elimination business units the same as you would add any business unit on the General Ledger Definition page. Make sure to select the Consol - For Elimination Only check box, as this is what distinguishes an elimination unit from other units and its treatment for the consolidation process. You can also add elimination units to the consolidation tree in the same way that you add any detail ChartField value.

The placement of the elimination units on the tree tells the consolidation process what business units' intercompany activity is eliminated within the elimination unit. For example, the ELIM5 elimination unit in the consolidated management reporting tree, CONSOLIDATE_CORP, is defined as the elimination unit for the ASIA/PAC consolidation; therefore, intercompany activity between Japan and Australia are eliminated within ELIM5 .

Assigning Ledgers to Elimination Units

Assigning a ledger to an elimination unit is done the same way that you handle regular business units. The base currency of the ledger must be the same currency used for consolidation.

See Also

Defining Ledgers for a Business Unit

Defining Your Operational Structure

Specifying Consolidation Ledgers

To specify a consolidation ledger, use the Consolidation Ledger Sets component (LEDGER_SET).

For each business unit involved in Consolidations, you can specify one ledger as the Consolidation ledger. The Consolidations process uses this ledger as the source and identifies transactions to be eliminated. Consolidation journals reference this ledger for elimination units.

In cases where business units have different base currencies in their primary ledgers, and translation ledgers are maintained for reporting on a single currency, you can use Translation ledgers as Consolidation ledgers. Consolidation does not perform any currency translation. The currency that you specify must have complete balances in place resulting from regular journal posting or from the Currency Translation process.

You specify a ledger for a business unit on the Ledger Sets page. With a common Consolidation chart of accounts, you can also consolidate at a summary level.

Page Used to Define Ledger Sets

Defining a Ledger Set

Access the Ledger Set page (General Ledger, Consolidate Financial Data, Consolidation, Consolidation Ledger Sets, Ledger Set).

Automatic Populate Scroll

The Automatic Populate Scroll section enables you to select the parameters that will populate the scroll with the ledgers that you can use. After you choose parameters, click the Refresh button to populate the page.

Note. When you click the Refresh button, the system provides you with only the best guess of ledger names. Review the ledger names populated by the system . and select the ledger that you want to use in the consolidation.

Specify Ledgers to Use

When you click Refresh, the system populates the scroll area with the following:

You can also enter business units and their associated ledgers individually by adding a row. The new business unit does not have to be part of the earlier specified tree.

Note. All business units involved in the consolidation process must have a row defined on the Ledger Set page so that the system knows which ledger to use for each business unit during the consolidation process.

See Also

Specifying Consolidation Journal Options

Defining Elimination Sets

The elimination set defines a related group of intercompany accounts. When eliminated, the balances of this group of accounts should normally net to zero. To maintain a balanced journal entry, the system posts any amounts that remain after the elimination to a user-defined out-of-balance ChartField. When you run the consolidation, the system processes each elimination set specified in your consolidation definition.

To define elimination sets, use the Elimination Sets component (ELIMINATION_SET).

This section discusses how to:

• Define an elimination set.

• Enter an elimination set.

• Audit elimination sets.

Pages Used to Define Elimination Sets

Defining an Elimination Set

Access the Elimination Set page (General Ledger, Consolidate Financial Data, Consolidation, Elimination Sets, Elimination Set).

Ledger Template	Select the ledger template that is used by the ledgers in your consolidation. If you specify a Summary Ledger template as the ledger template, the system displays the Ledger field, where you enter the summary ledger name. The system also displays a detail link; click it to access the Summary Ledger Definition page.
Description	Identifies the elimination for prompt lists.
Comments	Describe what the elimination set does. This field is particularly useful for documenting each set in a complex consolidation.

Out of Balance Debit and Out of Balance Credit

If the activity within a given elimination set does not net to zero, PeopleSoft General Ledger directs the out-of-balance amount to the Out of Balance field values that you specify on this page.

Entering an Elimination Set

Access the Elimination Lines page (General Ledger, Consolidate Financial Data, Consolidation, Elimination Sets, Elimination Lines).

Match Affiliate Value

Select the check box if you use the Affiliate approach for elimination. For a summary ledger that does not have an Affiliate ChartField, the Match Affiliate Value check box is deselected and display-only.

Values to Eliminate

Auditing Elimination Sets

Access the Audit Elimination Sets page (General Ledger, Consolidate Financial Data, Reports, Elimination Sets Audit, Audit Elimination Sets).

Report Request Parameters

Defining Subsidiary Ownership and Minority Interest Sets

General Ledger evaluates minority interest relationships at the time a consolidation is run, based on the data in the minority interest sets and Ownership table. It calculates the adjustment prior to generating elimination entries.

You define the relationship for the subsidiary business unit, the parent company that owns the majority of that subsidiary, and any other minority owners. You do not specify minority owners that exist outside your organization.

If a minority parent exists in the same consolidation tree as a majority parent, General Ledger makes a second adjustment to reflect the minority parent's ownership percentage. Because the original adjustment creates a liability for the minority interest, the second adjustment effectively reduces that liability because a minority parent is included in the consolidated results. This means that you do not overstate your minority interest liability.

General Ledger supports any number of minority parents and generates the adjustment entry at the appropriate point in the consolidation according to the consolidation tree level.

To define subsidiary ownership and minority interest sets, use the Subsidiary Ownership component (CONSOL_OWNERSHIP) and the Minority Interest Sets component (MINORITY_INTEREST).

This section discusses how to:

• Define subsidiary ownership.

• Define the minority interest source.

• Define a minority interest target.

Pages Used to Define Subsidiary Ownership and Minority Interest Sets

Defining Subsidiary Ownership

Access the Subsidiary Ownership page (General Ledger, Consolidate Financial Data, Consolidation, Subsidiary Ownership).

Entity Field	Select the consolidating entity field. This is usually the business unit, but you can consolidate based upon other fields, like Operating Unit. This field should be the same field upon which your consolidation tree is based.
Subsidiary Entity	Organizational unit owned by the parent.

Note. Add a new effective-dated row to reflect valid changes in subsidiary ownership. When adding new effective-dated rows, make changes only to the Specify Parents group box. The Subsidiary Entity field must stay constant, as that is the subsidiary for which you are defining ownership.

Specify Parents

Note. To prevent duplication, the system does not allow you to enter the same parent entity value twice.

Defining the Minority Interest Source

Access the Minor Int Source (minority interest source) page (General Ledger, Consolidate Financial Data, Consolidation, Minority Interest Sets, Minor Int Source).

Subsidiary Equity	Specifies the ChartField value set that identifies the subsidiary's equity accounts.
Parent Investment	Specifies the ChartField value set that identifies the asset account where the subsidiary is carried on the parent company's books.
Match Affiliate Value	Select the check box if you are using a single investment account and have populated the Affiliate ChartField with the subsidiary.

See Also

Using ChartField Value Sets

Defining a Minority Interest Target

Access the Minor Int Target (minority interest target) page (General Ledger, Consolidate Financial Data, Consolidation, Minority Interest Sets, Minority Int Target).

Minority Interest

Out of Balance Debit and Out of Balance Credit

Setting Up Consolidation Sets

After you define consolidation relationships in your tree and specify intercompany elimination and minority interest sets, you are ready to define the options and controls that tell General Ledger how to process the consolidation.

To set up consolidation sets, use the Consolidation Set component (CONSOL_DEFINITION).

This section discusses how to:

• Specify consolidation journal options.

• Specify set options.

Pages Used to Set Up Consolidation Sets

Specifying Consolidation Journal Options

Access the Journal Options page (General Ledger, Consolidate Financial Data, Consolidation, Consolidation Set, Journal Options).

Entity Field	Select the consolidating entity field. This is usually the business unit, but you can consolidate based upon other fields, like Operating Unit. This field should be the same field upon which your consolidation tree is based.
Business Unit	When consolidating on other than BUSINESS_UNIT, General Ledger displays a Business Unit field that enables you to designate the business unit as the high order key in the consolidation.
Ledger Set	Specifies a combination of business units and ledgers that act as a centralized location for consolidations.
TimeSpan	Select a user-defined TimeSpan for which to process the consolidation. You can select to process year-to-date balances or quarterly and period balances (such as QTR1 , QTR2, QTR3, QTR4 or PER). If you select a year-to-date TimeSpan, the Consolidation Reversal option must be either Beginning of Next Period or End of Next Period; otherwise, the reversal option must be Do Not Generate Reversal. A warning message is issued if the reversal option is not appropriate for the selected TimeSpan. Note. Performance may be impacted when using a BAL or YTD TimeSpan due to increased volume of data when processing effective-dated ownership sets. Using quarterly or period TimeSpans improves performance. When upgrading to 9.1, be careful to use BAL as the TimeSpan, as Consolidations has historically processed BAL balances.

Elimination Journals

In the following example, Department is the additional ChartField, and the elimination lines contain the following amounts:

During Consolidations, the system generates journal entries that represent year-to-date (YTD) elimination amounts based on the type of account specified in the elimination set. For profit and loss accounts, the system totals the YTD amount based on the sum of periods 1 through n, and for balance sheet accounts periods 0 through n. To facilitate period-based reporting, General Ledger generates a reversing journal for the subsequent period. The resulting net amount on the elimination unit ledger represents the current period YTD amount less the reversal amount generated by the eliminations for the prior period.

Elimination Reversals

Elimination Includes ChartFields

Select the ChartFields that you want to include in elimination. The ChartFields that are defined for a consolidation definition relate to the ChartFields that are specified for the elimination set:

• If elimination set ChartFields provide more detail than consolidation definition ChartFields, the system summarizes the elimination journal entries at the level of detail defined by the elimination set.

  For example, if you specify Account as the consolidation definition and Account and Project for your elimination set, the system includes account and project detail when it summarizes elimination journal entries.

• If consolidation definition ChartFields provide more detail than elimination set ChartFields, the system expands the elimination journal entries, summarizing at the level of detail defined by the consolidation definition.

  For example, if you specify Account, Department, and Product as the consolidation definition and Account and Project as the elimination set, the system expands the elimination journal entries to include account, department, and product detail when it summarizes them.

See Also

Defining Document Types

Defining Journal Source

Specifying Set Options

Access the Set Options page (General Ledger, Consolidation, Consolidation Set, Set Options).

All Elimination Sets Apply	Select to indicate that you want to use all of the elimination sets that are defined for the setID when processing this consolidation set.
Default Minority Int Set (default minority interest set)	Specifies which minority interest set to use for the calculation. Based on the Subsidiary Ownership setup, Consolidations includes all parent and subsidiary sets, provided that all entities involved are within the consolidation scope (the consolidation tree).
Effective-Date Ownership Sets	Select one of the following options for the effective dates that dictate to which period of the fiscal year the Ownership Sets apply: by Period End Date(s) - the Consolidation process applies the ownership definitions that are effective as of the respective accounting period end dates of the periods that are being processed. by Process Request As Of Date - the Consolidation process applies the ownership definitions that are effective as of the process request date. Note. The journal entries that are created by the Consolidation process are dated as of the process request date, regardless of the effective date of the ownership sets. To illustrate the Period End Date(s) option, assume that you are running the Consolidation process through June 30, 2009. Additionally, assume that there are two effective-dated ownership sets with one dated January 1, 2009 and the other dated April 15, 2009. Given these effective dates, the Consolidation process applies the Ownership Set that is effective from January 1 to periods 1 through 4 balances, and uses the April 15 Ownership Set for periods 5 through 6 balances. If using the Process Request As Of Date option, the Consolidation process applies the April 15 ownership set for all periods that are included in the consolidation.

Elimination Sets to Process

Minority Interest Sets Override

Using ChartField Value Sets

Use ChartField value sets to define sets of ChartFields used in consolidation and equitization processes. You can specify individual values, select values from specified tree levels and nodes, or use ranges of detail values. You should use trees or ranges whenever possible to reduce future maintenance if ChartField values change.

You can set up ChartField value sets with the same name but different setIDs for different groups of business units, if ChartField values as part of the consolidation rules are different by business units. For example, Parent Investment on the Minority Interest Set Definition page is specified as a ChartField value set entry. You can define two ChartField value sets both named ACCT_INVESTMENT, but one under setID SHARE and one under SET01 with each having its own set of accounts specified. The setID for the ChartField value set is resolved at runtime, based on the TableSet Control for Record Group FS_12, for each business unit processed.

You can set up ChartField value sets for either detail ledgers or summary ledgers. Specify the summary ledger name, as well as the ledger template. You cannot use a tree to select values for summary ledgers.

See Also

Defining and Using ChartField Value Sets

Performing Consolidation

This section discusses how to:

• Initiate consolidation processing.

• View the consolidation process log.

• Use the consolidation dashboard.

Pages Used to Perform a Consolidation

Initiating Consolidation Processing

Access the Consolidation Request page (General Ledger, Consolidate Financial Data, Consolidation, Request Consolidation, Consolidation Request).

Request Parameters

Consolidation Options

Note. If the process ends prematurely during an Undo process, unlock the journals for the process instance before rerunning the Undo process.

Scope of Consolidation

Tree Effective Date Option

See Also

Using Commitment Control in General Ledger

Defining Document Sequencing

Viewing the Consolidation Process Log

Access the Consolidation Process Log page (General Ledger, Consolidate Financial Data, Review Results Online, Consolidation Process Log).

This information is useful if you want to undo a previous consolidation process, but have forgotten what parameters were used for that process.

The fields on this page are the same as those found on the Consolidation Request page.

See Also

Initiating Consolidation Processing

Using the Consolidation Dashboard

Access the Consolidation Dashboard page (General Ledger, Consolidate Financial Data, Review Results Online, Consolidation Dashboard).

The Consolidation Dashboard provides an easy way to view and analyze the results of a given consolidation set by date.

Calculation Log Criteria

Consolidation Calculation Log

Consolidating Across Summary Ledgers

Processing consolidation on summary ledgers offers the following advantages:

• The process time is reduced because the volume of summary ledgers usually is much smaller than detail ledgers.

  This is especially true if you are using existing summary ledgers that you are already maintaining.

• You can achieve the purpose of consolidating business units with dissimilar charts of accounts through summarizing detail ledgers using trees.

The following are the main differences when setting up or running the consolidation process using summary ledgers:

• Whenever a ledger template needs to be specified, instead of using a detail ledger template (for example, STANDARD), use the summary ledger template of your choice (for example, S_ACTDIV).

  This includes your elimination set, minority interest set, consolidation ledger set, and consolidation set.

• Because detail ledgers are not involved, the system does create journals.

  The consolidation calculation log holds the information about how summary ledgers are updated.

• Summary ledgers used for consolidation must be up-to-date before you process the consolidation so that, for example, any last-minute journals are rolled up to the summary ledgers properly when posted to its detail ledgers.

  Summary ledgers can be incrementally updated either through journal posting or by running a separate Summary Ledger process.

Specifying Summary Ledger Consolidations

To set up consolidation on summary ledgers:

1. Specify the summary ledger template.

   For all the summary ledgers that are used for consolidation, you must specify the consolidation log and consolidation equity temporary records for summary ledger templates on the Ledger Template − Record Definitions page. If you plan to use the Affiliate field to identify intercompany transaction balances in summary ledger, your summary ledger must retain the affiliate values.

2. Define elimination sets on the summary ledger.

   To consolidate on the summary ledger, use the Elimination Sets page to define elimination sets based on a summary ledger. You must specify both a ledger template and the name of the summary ledger so that the system knows how to prompt for ChartField and ChartField values.

   If the affiliate value is kept in the summary ledger table, and you want to use the Affiliate method of elimination, check the Match Affiliate Value option on the Elimination Lines page. If the Affiliate field is not one of the fields in the summary ledger template, you must specify the business unit value in the elimination set.

3. Define minority interest sets on the summary ledger.

   Specify the appropriate ledger template and ledger for the summary ledger on the Minor Int Source (minority interest source) page.

   On the Minor Int Target (minority interest target) page, ensure that the Subsidiary Equity and Parent Investment values are ChartField value sets based on the same summary ledger.

4. Define consolidation ledger set.

   Use the Consolidation Ledger Set page to specify the summary ledger names to be used for each business unit for consolidation.

5. Define consolidation sets on the summary ledger.

   Use the Journal Options page to specify the appropriate ledger template and ledger for the summary ledger. The ledger set used for consolidation processing should be based on the same summary ledger.

6. On the Set Options page, ensure that elimination sets are based on the same summary ledger.

See Also

Defining a Ledger Template

Mapping Dissimilar Charts of Accounts

You can perform consolidations across an organization's ledger balances when entities have different ChartField structures. This is important when consolidations must be performed over entities that are not maintained in PeopleSoft General Ledger.

Create a Consolidation chart of accounts that represents a single, common reporting structure. This Consolidation chart of accounts must be mapped to each business unit's different chart of accounts to be included in the consolidation rules.

The Consolidation chart of accounts can be structured at any level of summarization. This flexibility enables you to define a Consolidation chart of accounts at a lower level of detail than is required for reporting, but at a higher level than the individual business unit chart of accounts. Using trees over the Consolidation account, you can summarize up to the required level of external reporting.

The real value of consolidations functionality is the ability to bring in data from many disparate ledger systems and map to a common parent company chart of accounts.

To map dissimilar charts of accounts, use the ChartField Mapping Set component (CF_MAPPING_SET) and the ChartField Value Mapping component (CF_VALUE_MAPPING).

This section provides an overview of a consolidation and discusses how to:

• Define a ChartField mapping set.

• Map ChartField values.

Understanding a Consolidation

Consider this example of three mutually exclusive and disparate charts of accounts. Assume that all business units are set up in General Ledger, and there is a different chart of accounts for each setID.

SetID MFG represents a manufacturing company, FS is a financial institution, and HC is a healthcare facility.

Notice the difference in the numbering of accounts and the account descriptions. For example, account number 500000 is used for a different purpose in each setID. For purposes of consolidation, we must map each set of accounts to a single, common Consolidation chart of accounts.

This table illustrates a subset of a Consolidation chart of accounts to which individual accounts by setID must be mapped:

As a result of the mappings, each setID has been correlated to a single, common Consolidation chart of accounts.

The example illustrates mapping at the setID level, which presumes that there are one or more business units that share a common chart of accounts under a specific setID.

Pages Used to Map Dissimilar Charts of Accounts

Defining a ChartField Mapping Set

Access the ChartField Mapping Set page (General Ledger, Consolidate Financial Data, Load Ledgers, ChartField Mapping Set).

Mapping Set Details

Ledger Template ChartFields

When you specify a ledger template, the system populates this area with the ledger template ChartFields. You can select which ChartFields are associated with mapping.

Mapping ChartField Values

Access the ChartField Value Mapping page (General Ledger, Consolidate Financial Data, Load Ledgers, ChartField Value Mapping).

Target SetID

Select value to indicate the setID to which you are mapping.

Mapped Business Units

Mapped Values

A conversion process reads the mapping setup and converts external data that is either loaded to the Staging table, or to the Ledger table itself but under certain ledger names, and populates the PeopleSoft Ledger table. Consolidation is then performed on the Ledger table.

Using Equitization

During the accounting year the equity of a subsidiary can change affecting the ownership value of a parent in that subsidiary. For example, net income or losses of a subsidiary increases or decreases the investment and owner equity of the parent. General Ledger enables you to set up multiple equitization rules for multiple business units that have complex parent-subsidiary relationships and create journal entries within a single process. A ledger for a parent entity can be different from that of its subsidiary and, as one of the options, you can generate elimination entries for consolidated reporting.

Note. Equitization supports only the Business Unit field as the processing entity. This is unlike the Consolidation process, which allows consolidation of fields other than business unit, such as the Operating Unit field.

This section discusses a:

• Review of an equitization example.

• Review of components of the Equitization process.

Reviewing of an Equitization Example

In this example, Company M0004 owns 70% of company M0002. In January of 2003, M0002 had a net income of 100 in period 1. An equitization rule is set up to select expense and revenue accounts as the equitization source, and investment and equity income as the target (debit and credit, respectively). The Equitization process creates journals to book 70 to the M0004 ledger investment account and −70 to its equity income account, as indicated by the entries in this table:

Viewing an Example of Multiple Parent/Subsidiary Ownership

If, in addition to the M0002 to M0004 relationship, F0001 owns 20% of M0002 and 60% of M0004, the equity income from subsidiaries for F0001 is 200, with 20 from M0002 and 180 from M0004, as indicated by the b entries:

The Equitization process determines the correct sequence to process. It equitizes from M0002 to M0004 and F0001 first, and then M0004 to F0001, so that the 70 from the first step is included as part of the net income in the second.

Creating Elimination and Minority Interest Entries

An option of the Equitization process enables you to generate elimination and minority interest entries as by-products. If specified, the Equitization process creates the elimination entries that reverse target amounts. As in the Consolidations process, these entries go to the proper elimination business units in the consolidation tree and are used in consolidated reporting. In the following example, elimination entries are generated for elimination business unit ME001:

If year-to-date elimination for investment is handled in the Equitization process, the Consolidations process should not generate eliminations again.

Offsetting the Source

This option creates entries to offset the equitized source amount for subsidiary entities. It may be useful for special reporting purposes:

Reviewing of Components of the Equitization Process

The Equitization process includes the following components:

See Also

Defining Equitization Rules

Defining Business Unit Trees and Elimination Units for Equitization

If you are running the consolidations process as well as Equitization, you can use the consolidations business unit tree to specify which business units to include in the Equitization process. Elimination business units must be part of the tree for elimination entries to be generated. Unlike Consolidations, the order in which Equitization business units are processed is determined by ownership sets (that is, who owns whom) and not by their location in the tree.

See Also

Defining Consolidation Trees

Setting Up Elimination Units

Specifying Ledgers for Each Business Unit in an Equitization

For each business unit involved in the Equitization process, you can specify one ledger as the source or target ledger, the same as you would for the consolidation process. You specify the ledger for a business unit on the Ledger Sets page.

See Also

Specifying Consolidation Ledgers

Defining Ownership Sets for Equitization

Use the Subsidiary Ownership page to define ownership sets, which indicate relationships among the parent company, subsidiary business unit, and any other minority owners.

Use the Equitize check box on this page to indicate whether Equitization should be run for specified parent entities.

See Also

Defining Subsidiary Ownership and Minority Interest Sets

Defining Equitization Rules

You can define multiple equitization rules for a process. For example, you can define one rule for subsidiary net income and another rule for unrealized gain and loss. Equitization processes all the rules in one ownership set and then proceeds to the next set.

To define equitization rules, use the Equitization Rules component (EQUITIZATION_RULE).

This section discusses how to:

• Specify the equitization source.

• Specify the equitization target.

• Specify the subsidiary offset.

• Specify minority interest.

Pages Used to Define Equitization Rules

Specifying the Equitization Source

Access the Source page (General Ledger, Consolidate Financial Data, Equitization, Equitization Rules, Source).

Ledger Template

Specify the template to limit ChartFields applicable to setting up the equitization rule.

Equitization Source

See Also

Defining and Using ChartFields

Specifying the Equitization Target

Access the Target page (General Ledger, Consolidate Financial Data, Equitization, Equitization Rules, Target).

Parent Investment and Investment Offset

The system summarizes source amounts (debits) at the level specified by the parent investment ChartField and books them to the account specified in the Value field. However, it creates only one row (with the investment offset Value field) for the credit side.

If the Affiliate ChartField is used in the ledger, the system populates the target entries with the subsidiary business unit value.

When creating an equitization rule, you can establish one or more investment and equity offsets by setID and business unit.

Specifying the Subsidiary Offset

Access the Subsidiary Offset page (General Ledger, Consolidate Financial Data, Equitization, Equitization Rules, Subsidiary Offset).

You can use these accounts as an income summary on the subsidiary. The equitization summary represents the gross change in an individual subsidiary's value. In the case of net income, you can place the value in the minority interest definition for equity. In this way, you avoid a minority interest elimination entry for each detail value in the net income node.

See Also

Specifying the Equitization Target

Specifying Minority Interest

Access the Minority Interest page (General Ledger, Consolidate Financial Data, Equitization, Equitization Rules, Minority Interest).

If you select Create Equitization Eliminat'n (create equitization elimination), the system generates elimination entries to eliminate the equitization target entries. If you want to generate minority interest entries, specify their value, and the system generates minority interest as part of the elimination. Elimination entries are booked to elimination business units in the consolidation tree.

See Also

Specifying the Equitization Target

Defining an Equitization Group and Journal Options

Within an ownership set, the consolidation process creates one journal for each business unit involved. If rounding errors occur, Equitization adjusts the amount of the last journal line of each journal to make the total debit amount equal to the total credit amount.

To define equitization group and journal options, use the Equitization Group component (EQUITIZATION_GROUP).

This section discusses how to create an equitization group.

Page Used to Define an Equitization Group and Journal Options

Creating an Equitization Group

Access the Equitization Group page (General Ledger, Consolidate Financial Data, Equitization, Equitization Groups, Equitization Group).

TimeSpan

Select a TimeSpan for which to process the Equitization entries. If you select a year-to-date TimeSpan, the Equitization Reversal option must be either Beginning of Next Period or End of Next Period; otherwise, reversal option must be Do Not Generate Reversal. A warning message is issued if the reversal option is not appropriate for the selected TimeSpan. Note. Performance may be impacted when using a BAL or YTD TimeSpan due to increased volume of data when processing effective-dated ownership sets. Using PER or QTR TimeSpans improves performance.

Effective-Date Ownership Sets

Select one of the following options for the effective dates that dictate to which period of the fiscal year the Ownership Sets apply: by Period End Date(s) - the Equitization process applies the ownership definitions that are effective as of the respective accounting period end dates of the periods that are being processed. by Process Request As Of Date - the Equitization process applies the ownership definitions that are effective as of the process request date. Note. The journal entries that are created by the Equitization process are dated as of the process request date, regardless of the effective date of the ownership sets.

Journal Options

Equitization Rules

Select one or more rules from those that you defined previously in the Equitization Rules component to include in your equitization.

Equitization Reversal

Select either the Beginning of Next Period or End of Next Period for reversal journal entries if processing year- to-date balances.

Select Do Not Generate Reversal if you are using TimeSpan to process for intermediate periods (QTR, PER, and so on).

See Also

Defining Document Sequencing

Performing Equitization

After you define equitization rules, an equitization group, and related options, you can proceed to perform an equitization.

This section discusses how to:

• Initiate equitization processing.

• View the equitization process log.

Pages Used to Perform Equitization

Initiating Equitization Processing

Access the Equitization Request page (General Ledger, Consolidate Financial Data, Equitization, Request Equitization).

Equitization Parameters

Equitization Options

Note. If the process ends prematurely during an undo, unlock the journals for the process instance before rerunning the undo process.

Scope of Equitization

Tree Effective Date Option

For the Equitization process to identify the correct journals to unpost and delete, information on the Run Equitization page must match the information specified for a previous process. The items that you must match are setID, currency, equitization group, As of Date, and scope of consolidation. This information is stored in a process log.

See Also

Using Commitment Control in General Ledger

Viewing the Equitization Process Log

Initiating Consolidation Processing

Viewing the Equitization Process Log

Access the Equitization Process Log page (General Ledger, Consolidate Financial Data, Review Results Online, Equitization Process Log).

Select an Equitization Group, Tree, and the start date for the list of processes as Search criteria. The first row of each process contains the keys that you use for matching on the Run Equitization page. The fields on this page are the same as those found on the Run Equitization page, with the addition of Instance, DateTime, and Request No. These fields are created after the process is completed.

See Also

Performing Equitization

Producing Consolidation and Equitization Reports

General Ledger delivers standard consolidation and equitization reports designed to provide the kind of business information many companies need. Running a report entails selecting it from a menu and entering any necessary parameters. After you have entered the report parameters, you use Process Scheduler to manage the processes, track the status, and generate the report.

Pages Used to Produce Consolidation and Equitization Reports

See Also

General Ledger Reports

Using the Ledger Interface Utility

General Ledger users often need to send the contents of their regional databases to a corporate location where the data is consolidated into a single database. Using PeopleSoft Application Messaging, the Ledger Interface Utility can send data from either PeopleSoft or non-PeopleSoft databases. The Ledger Interface Utility is delivered with General Ledger.

This section discusses how to:

• Set up the Ledger Interface Utility.

• Publish ledger data.

• Load external ledger data.

• Review the process.

Note. Review the PeopleTools Integration Broker PeopleBook. The backporting utility enables you to backport PeopleTools 8.5 message queues to message channels used in previous PeopleTools 8.4x releases. It also enables you to backport PeopleTools 8.5 handlers to integration PeopleCode constructs used in previous PeopleTools 8.4x releases.

See Also

General Ledger Reports

Pages Used to Set Up the Ledger Interface Utility

Setting Up the Ledger Interface Utility

The Ledger Interface Utility transfers both detail and summary ledgers from one database to another. The utility extracts multiple ledger data from a regional database, sends it to the corporate location, and provides for ChartField mapping of detail ledgers. This is done for each regional database in preparation for consolidating all regional data into one corporate database.

PeopleSoft Application Messaging requires that the source and target databases have identical ledger table structures to communicate. This is true for all publish and subscribe application messages. Ledger ChartFields must be the same for summary ledgers. The scope of the Ledger Interface Utility is limited to the transfer of data.

Setting up the utility to send regional databases to a corporate location requires completing several tasks.

Task 1 - Define Message Nodes

Message nodes represent publishing or subscribing entities such as databases or application servers, and they are most often associated with a database name. Both corporate and regional locations need to define message nodes. Corporate defines its own local node and one remote node for each regional location that sends data. Each regional location defines its own local node and defines one remote node for the corporate location.

To define the necessary message nodes:

1. Define a local message node.

   As delivered, the Ledger Interface Utility publishes data to the standard PSFT_EP message node. Rename the standard local node with a unique node name that is associated with your database.

2. Verify that the node, as you renamed it, is the local node.

   There can be only one local node at a location. If you attempt to save a second local node, the system displays an error message.

3. Define remote message node locations.

   A region defines one remote node for its corporate location, and the corporate location defines multiple remote nodes, one for each regional database to be consolidated. If the corporate list is missing a URL for one of the regional databases, the corporate location does not receive the data for that region.

Task 2 - Define the Service Operation Queues

A service operation queue is a logical group of messages. Each message must belong to one (and only one) queue, which specifies a routing. Both publishing and subscribing nodes use this service operation queue.

To define the necessary queue:

1. Use the delivered service operation named LEDGER.

2. As delivered, the Ledger service operation contains one routing rule for the standard PSFT_EP message node.

   You can delete the delivered routing rule and create rules that apply to your databases. Regional and corporate locations define different routing rules.

3. At the local regional location, define one routing rule with a message node name for your corporate location, with Publish To as the direction.

4. At the corporate location, define a routing rule with one message node name for each regional database that is involved in the consolidation.

   All routing rule definitions must be Subscribe From. If the corporate list is missing a routing rule for one of the regional databases, corporate does not receive data for that region.

Task 3 - Define the Message

A Ledger Interface Utility message contains a general ledger database. The message is the vehicle of transport that carries the database from the regional entity at one URL to the corporate entity at another URL.

The system inserts application data into the message according to the records that you specify in the message definition. Regional message definitions must match corporate message definitions. If you change your table in the database, the changes are automatically inherited by the message definition as long as table names remain the same.

To define the message:

1. View the LEDGER_LOAD message.

   Because consolidation does not support PeopleSoft Projects or Commitment Control, no ledger record names for Projects or Commitment Control are listed under LED_PUB_REQ in the message definition.

2. Keep the delivered record names in the LEDGER_LOAD message definition because changing them is considered a customization.

   If you must use a different table name, the table name listed below LED_PUB_REQ must match the ledger table name on the ledger template. For detail ledgers, the record definitions of your new ledger table and your staging table must be identical.

3. Activate the LEDGER_PUBLISH message at regional and corporate offices.

Task 4 - Create Staging Tables

Because summary account ChartField values are the same for regional and corporate summary ledgers, the summary ledger subscription process writes the subscribed data directly into the consolidated ledger table. Access the Setup Financials/Supply Chain, Business Unit Related, General Ledger, Definition page and select the Allow Ledger Load Updates check box.

Because detail ledgers frequently contain account ChartField values that differ between regional and corporate entities, the regional accounts need to be mapped to corporate accounts. To accomplish the mapping, detail ledger data is subscribed into staging tables. A ChartField mapping process reads the staging table, maps it, and writes the resultant data to the consolidated detail ledger table.

To create staging tables:

• Define staging table names at the corporate location.

  For detail ledgers, create record definitions for the staging tables that are identical to the record definitions of their corresponding ledger tables.

• At the corporate location, create a message record alias for each staging table.

  The alias names for the corporate node must match the alias names at the remote nodes.

Task 5 - Publish the Ledger Data

Publishing ledger data is done at regional locations. To publish a regional database, use the Publish Ledger page to select criteria and process options.

Task 6 - Subscribe from the Ledger Data

Using Application Messaging, data is published by initiating a process request on the regional general ledger database. At the corporate location, the subscription process is run automatically on the application server of the subscribing node.

Summary ledger data is written to the summary ledger file, and detail ledger data is written into the staging tables that are defined at the corporate location.

Before you run the ChartField mapping process (task 7), verify the detail ledger data. Add a view to the query tree for the staging table, and save it so that you can query the staging table to ensure that the data is written properly.

Task 7 - Perform ChartField Mapping

Regional detail and summary ledgers must have the same ChartFields and use the same calendar when you assign them to a business unit. Because account numbers often differ between detail and summary ledgers, run the ChartField Mapping process against the detail ledger data that is written to the staging tables. After mapping, run the consolidation process.

For detail ledgers, the system checks the staging table alias against the ledger template definition. If the staging table alias is pointing to the ledger template definition, it is possible for data to be written to an application table in error. To prevent such an error, the subscription process rejects any message whose staging table alias points to an application table that is defined in the ledger template.

If the staging table alias does not point to the ledger template definition, the system writes data into the staging table as specified by the alias.

To perform ChartField mapping:

1. Verify that the proper detail ledger data resides in the staging table (recommended).

   Add views to the query tree for the staging tables, and save them only once. Query the staging tables to verify that the data is written properly.

2. Run the ChartField mapping process against the staging tables.

Note. For summary ledgers, the system writes data directly to the application table only if the Allow Ledger Load option on the ledger group is selected.

Task 8 - Load Ledger Data

Loading ledger data is done at the corporate location. To load ledger data, use the Load Ledgers Request page to select criteria and process options.

Publishing Ledger Data

Access the Publish Ledger page (General Ledger, Consolidate Financial Data, Load Ledgers, Publish Ledgers, Publish Ledgers Request).

Select run criteria and processing options. An Application Engine process called GL_LED_PUB extracts ledger data from the selected ledger table and publishes an application message according to your request options.

Loading External Ledger Data

Access the Load Ledgers Request page (General Ledger, Consolidate Financial Data, Load Ledgers, Request Ledger Load, Load Ledgers Request).

Select run criteria and processing options. An Application Engine process called GL_LED_LOAD loads external ledger data into the corporate database through Application Messaging.

Consolidation of ledger data is done at the corporate location.

Note. Consolidations does not support PeopleSoft Projects or Commitment Control.

See Performing Consolidation.

Reviewing the Process

This section describes important things to consider concerning your detail ledgers, summary ledgers, and the process setup before you use the Ledger Interface Utility process.

Detail Ledgers

Considerations:

• Detail ledger ChartField values from regional databases can differ from the corporate database because the data is transmitted to the staging table.

  The ChartField mapping process reconciles these differences.

• For staging tables, add and save a view to the query tree.

  Query the staging table to verify that the data loaded properly before performing ChartField mapping.

• Regional detail ledgers must use the same calendar when you assign them to a business unit.

  Verify the calendar on the Ledgers for a Unit page.

• Regional detail ledgers must have the same ChartFields when you assign them to a business unit.

  Verify detail ledger ChartFields by navigating to the Detail Ledger Group - ChartField page: General Ledger, Ledgers, Ledger Groups. Select the ChartField tab. The Detail Ledger Definition report (FIN0022) also shows the structure of the detail ledgers.

Summary Ledgers

Considerations:

• ChartField values must be valid in both corporate databases and regional databases for the summary ledger.

• Regional summary ledgers must use the same calendar when you assign them to a business unit.

  Verify the calendar on the Ledgers for a Unit page.

• Regional summary ledgers must have the same ChartFields when you assign them to a business unit.

  Verify summary ledger ChartFields using the Summary Ledger Definition report (GLC1000), which shows the ChartField structure of summary ledgers.

Setup

To complete setup and verify the publication and subscription of information, refer to the PeopleTools documentation for the PeopleSoft Integration Broker, and see the section on using the Service Operations Monitor.