Establishing Consolidation Options and Supporting Objects

This chapter provides an overview of consolidation options and supporting objects and discusses how to:

Define system-wide security and processing options.
Define user preferences.
Define ChartField value sets.
Define elimination entities.

Defining System-Wide Security and Processing Options

This section provides an overview of system-wide security and processing options and discusses how to establish system-wide security and processing options.

Note. Consult a database administrator or a similar information technology professional within your organization when establishing these options.

Understanding System-Wide Security and Processing Options

You can establish system-wide options for:

Row-level security.
Book codes.
Load balancing for the Ledger Preparation process.

Security Options

You can establish row-level security for specific ledger business units, scenarios, operating units, accounts, book codes, locations, line of business, and departments. If enabled, a user's access to specific data is controlled by the PeopleSoft Enterprise Performance Warehouse row-level security that you establish for that field. This security applies to these objects:

Inquiry pages.
Structured Query Report (SQR) reports.
Manual Journal page.
Matching Tag page.
Trial Balance page.

For example, if you enable row-level security by business unit, users are only able to view data on the inquiry pages for the ledger business units that you permit them to access. Row-level security is set up within PeopleSoft Enterprise Performance Warehouse, but you must enable it within PeopleSoft Enterprise Global Consolidations in order to use it. It is recommended that you select no more than two fields on which to enforce row-level security, or system performance may degrade.

Note. Use PeopleSoft security to limit access to menus or pages.

Book Codes

A book code is a dimension that you can use to segregate the source ledger and the harmonization adjustments. Harmonization adjustments are journal entries that adjust the local statutory balance to consolidation reporting under IAS or US GAAP requirements. Harmonization adjustments give you the ability to maintain multiple accounting methods that allow you to separate local and consolidation reporting books. You combine book codes together into book code groups in order to couple source plus harmonization adjustment balances and amounts for consolidation reporting purposes.

In order to establish book codes, you must first determine at a system level whether or not you want to use the book code functionality as this affects all online inquiries. You have the option to turn book code functionality on the General Options setup page at anytime. You must manually adjust historical data if you want to go back and establish book codes for entries prior to turning on the book code functionality.

Like other dimensions, you can restrict access to book codes according to the way you define the row level security setup on the General Options page after assigning your users to roles and setting up your EPM Security user roles in the PeopleSoft Enterprise Performance Warehouse. You can assign users to security groups that you tie to book codes restricting the ability of users to enter and make inquiries of data to these specific book codes.

The book code functionality affects the trial balance and other inquiry pages by enabling the book code group option to be available within the inquiry selection page. When enabling the book code functionality, the trial balance report contains two separate columns for the primary and secondary book codes within the book code group.

Load Balancing Options

To optimize performance during ledger preparation processing, the system does load balancing to control the number of ledger business units that are processed concurrently using the Spawn (PF_SPAWN) application engine.PF_SPAWN. Load balancing is based on the total number of ledger business units, the number of record suites that are assigned, the size of your temp tables, and the maximum number of load cycles.

The formula used to determine how many concurrent ledger business units are processed is:

(total number of ledger business units) ÷ ((record suites assigned) – 1)

The reason why you subtract 1 from the record suites assigned is because one of the assigned record suites is always used as the controlling record suite; this reduces the number of available records suites by one.

There are two fields in which you can specify factors that impact load balancing: Minimum Number of Ledger Business Units and Maximum Number of Load Cycles. If the processing run contains only a few ledger business units, there is no real benefit gained by using PF_SPAWN and processing concurrently. Therefore, if the result of the concurrent ledger business units calculation is less than the minimum number of ledger business units, the system processes everything in sequence. However, when the result of the concurrent ledger business units calculation is greater than the minimum number of ledger business units, the resulting amount is the number that the system processes concurrently, with the size of the chunk equal to that number divided by the maximum number of load cycles.

For example, suppose that you have 2,000 ledger business units to process, and 10 record suites allocated to ledger preparation. The Minimum Number of Ledger Business Units = 20. The Maximum Number of Load Cycles = 5. Applying the formula to determine the number of concurrent ledger business units processed, this calculates to 2000 ÷ (10 – 1) = 222.22, or 223 when rounded up to the nearest whole number. Because 223 is greater than 20 (the minimum number of ledger business units to process), concurrent processing occurs. The system includes 223/5 (the maximum number of load cycles), or, when rounded, 45 ledger business units within each chunk.

By default the system does general load balancing when you set both the minimum number of ledger business units and the maximum number of load cycles to 1. This means that the system simply balances across the available record suites.

Page Used to Define System-Wide Security and Processing Options

Page Name	Object Name	Navigation	Usage
General Options	GC_INSTALLATION	Global Consolidations, Define Consolidations, Common Definitions, General Options	Establish on which fields to enforce row-level security and if you want to enforce row-level security for report processing, whether to implement book code functionality, whether to do comparisons between consolidation runs during processing, and enter load balancing options.
Maintain Book Code	BOOK_CODE_D00	EPM Foundation, Business Metadata, OW-E Dimension Maintenance, Common, Book Code, Maintain Book Code	Set up and maintain book code dimensions. Book codes are dimensions used to accommodate the separation of source ledger and adjustments.
Book Code Group	GC_BKCD_GRP	Global Consolidations, Define Consolidations, Common Definitions, Book Code Group	Assign book code dimensions to a book code group. Book code groups can couple source plus adjustment balances/amounts for consolidation reporting purposes. Book code groups are for reporting purposes (online inquiries or reports). You can group as many book codes together as possible. When setting up a book code group, you must specify primary and secondary book codes.
Book Code Group-Notes	GC_BKCD_GRP_NOTES	Global Consolidations, Define Consolidations, Common Definitions, Book Code Group, Notes	Enter notes about book group setup.

Establishing a Book Code Group

Access the Book Code Group page.

Primary Description

The primary description is used for the trial balance inquiry and reports.

Secondary Description

The secondary description is used for the trial balance inquiry and reports.

Book Codes

Enter rows for each book code you want to include in the book code group.

Blank

Select this option if you want to include blank book codes in the book code group.

When selecting this option, the system interprets blank book codes as belonging to that book code group. If this option is selected, you have the option to specify whether the book code is a primary or secondary book code.

Book Code

Select a book code from the list previously defined on the Maintain Book Code page.

Value

Select a value for the corresponding book code. You have a choice of Primary or Secondary.

In the example above, Blank and COMN are primary values and COAJ is a secondary value. In this case, the Blank and COMN book codes are combined on the trial balance inquiry and reports.

Note. You can have multiple primary and secondary values in the grid but not multiple entries for the same book codes using different values.

Note. The underlying book code group table (GC_BKCD_GRP) contains the date/timestamp and user ID information for audit purposes.

Establishing System-Wide Security and Processing Options

Access the General Options page.

Get Prior Run Differences

Select this option to do comparisons between consolidation runs during processing. As a result, the Get Prior Run Differences check box is available on the Eliminations and Equitizations run control pages.

Book Code Group Functionality

Select this option to activate the book code dimension for capturing multi-GAAP reporting functionality. This allows you to capture and segregate data for statutory consolidation or regulatory consolidation reporting. By selecting this option, the inquiry pages and reports will have an additional column for book code designation. Specifically, the Trial Balance Inquiry page will contain primary and secondary book codes where primary book codes are made up of source ledger (LOC) data and secondary book codes (IAS) are made up of journal adjustment entries. You can turn this option on at anytime but the system will not update historical data with book code information. You must go back and manually adjust this data if you so require.

Row Level Security

Within this region, select the fields on which to enforce row-level security. It is recommended that you select two fields at most; performance degrades if you select more than two. When viewing consolidation inquiry pages, you are limited to viewing only those rows to which you have access, based on the defined row level security set up in PeopleSoft Enterprise Performance Warehouse, for the fields that you specify. The Business Unit check box is used to control security to specific ledger business units, not the consolidation ledger business unit.

Note. If the Ledger Record and Ledger Template do not contain all of the fields listed for row level security enforcement, then the system ignores the Row-Level Security setting for those fields. For Example, Location and Line of Business are available for row level security enforcement, but those fields are not delivered in the Global Consolidations sample Ledger Records and Ledger Templates. Selecting those fields for the Row Level Security setting does not impact the sample ledgers. If you include these fields on the Ledger Record and Ledger Template, then the system enforces Row Level Security when accessing your ledger.

Report Row Level Security

Select this option if you want to enforce row level security during report processing.

This allows processing of selected dimensions based on the row level security setup. For example, your user ID that you log onto the system may prevent you from processing reports for specific business units or accounts.

Preparation Load Balancing

Enter the minimum number of ledger business units that you want to process concurrently, and the maximum number of load cycles.

Defining User Preferences

This section provides an overview of user preference settings and discusses how to:

Define user preferences for inquiry pages.
Define user preferences for portal pagelets.

Understanding User Preference Settings

Completing the user preferences pages enables the system to use the field values that you specify as the default data that appears on various inquiry pages. For example, if you know that you'll want to review data for a specific business unit most of the time, then you would specify that business unit here. When you use an inquiry page, the business unit field is already populated with the value that you provided. This enables default values to be set by user ID; you can always override them.

Pages Used to Define User Preferences

Page Name	Object Name	Navigation	Usage
User Preferences - Inquiry	GC_USER_PREF_INQ	Global Consolidations, Define Consolidations, Common Definitions, User Preference, Inquiry	Define user preferences for inquiry pages.
User Preferences - Pagelets	GC_USER_PREF_PLETS	Global Consolidations, Define Consolidations, Common Definitions, User Preference, Pagelets	Define user preferences for PeopleSoft Global Consolidations pagelets. These pagelets are available on various portals.

Defining User Preferences for Inquiry Pages

Access the User Preferences - Inquiry page.

Primary Inquiry Options

Specify the default business unit, tree name, scenario ID, and fiscal year, ledger preparation phase. For the period, either select Most Recent Period, so that the latest period appears by default, or clear Most Recent Period, and enter a specific period in the Period field.

Prep Phase is optional and allows you to specify the ledger preparation phase that you want to select as a primary inquiry.

Your options for Prep Phase are Ledger Enrichment or Preparation Manager.

Additional Inquiry Options

Specify the default options to use for inquiry pages that enable you to compare data.

Enter the scenario ID, and for the time frame to compare, select one of these options:

Prior Period of the Primary Period: Compares with data from the previous period.

Prior Year of Primary Period: Compares with data from the previous year.

Same as Primary Period: Compares with data from the previous year.

Specify: Compares with the fiscal year and period that you enter.

Book Code Group

Specify the default book code group.

Book Code Group appears on the User Preferences - Inquiry page when book code functionality is enabled on the General Options page.

Detail fields to show when drilling to ledger

Insert rows within this grid and specify which dimension to display when viewing details for the data. Select Show Description to display the dimension value's description.

Display Tree using Description

Select if, on pages with trees, you prefer to see the description for the nodes rather than the node IDs.

Defining User Preferences for Portal Pagelets

Access the User Preferences - Pagelets page.

The fields in the Primary Pagelet Options and Additional Pagelet Options group boxes are the same as those listed in the section for the User Preferences - Inquiry page.

Because pagelets have limited space, you can specify the default dimensions to include. Insert rows into the Include Dimensions grid, and specify which dimensions to display. Select Show Description to view the dimension values instead of the IDs. Only the first dimension that is inserted appears on pagelets.

Optionally, you can limit the default data shown in pagelets by selecting the Use Values Specified Below check box. Click Refresh, and insert one or more rows to enter the criteria for which data to view (based on the dimensions specified in Include Dimensions grid).

Defining ChartField Value Sets

This section provides an overview of ChartField value sets and discusses how to establish ChartField value sets.

Understanding ChartField Value Sets

A ChartField value set is a group of related ChartField values (specific accounts, departments, and so on) that you use as input into many of the consolidation rules. They enable you to specify a set of ChartField values for the various rules that drive consolidations, instead of having to specify each one individually. You can define which ChartField values comprise a ChartField value set by selecting a tree node, a range of values, or a set of individual values. For example, you can define a ChartField value set for all of your equity accounts, based on an account rollup tree. Later, if you need to change the ChartField values included in that set, simply update it once in the ChartField value set definition; you don't have to update each consolidation rule. You must set up the trees upon which you base the ChartField value sets before you can use those trees within your ChartField value set definitions.

Pages Used to Define ChartField Value Sets

Page Name	Object Name	Navigation	Usage
ChartField Value Set	GC_CF_VALUE_SET	Global Consolidations, Define Consolidations, Common Definitions, ChartField Value Set	Define a group of ChartField values.
ChartField Value Set - Notes	GC_CFV_SET_NOTES	Global Consolidations, Define Consolidations, Common Definitions, ChartField Value Set, Notes	Enter details about a ChartField value set.

Page Name

Object Name

Navigation

Usage

ChartField Value Set

GC_CF_VALUE_SET

Global Consolidations, Define Consolidations, Common Definitions, ChartField Value Set

Define a group of ChartField values.

ChartField Value Set - Notes

GC_CFV_SET_NOTES

Global Consolidations, Define Consolidations, Common Definitions, ChartField Value Set, Notes

Enter details about a ChartField value set.

Establishing ChartField Value Sets

Access the ChartField Value Set page.

Select the ledger template associated with this ChartField value set. This must be the same ledger template that you use for your consolidation ledger. The ledger template controls which ChartFields are valid.

In the Values by ChartFields group box, specify the specific values to include in this ChartField value set. Insert multiple rows as needed to define all the ChartField values that comprise the ChartField value set that you are defining. You can specify the ChartField values by using a tree or by selecting specific values from a list. The method by which you specify the ChartField values depends on your selection in the How Specified field, as do the active fields in the grid:

In Field Name, select which ChartField to use for this ChartField value set.

This setting limits lookups to valid values from this ChartField.

In How Specified, indicate your method for specifying the values to include, then specify your values by using the fields in the Select Values/Nodes grid. Select from these options:

Detail - Selected Parents	Use this option to specify values by using parent nodes of a specific tree. If you select this option, the Tree ID field becomes active. Select the tree that contains the values to include.
Range of Values	Use this option to specify a range of values to include. When you select this option, the Select Values/Nodes grid contains both a Select Value field (the beginning value to include in the range) and a To Value field (the last value to include in the range).
Selected Detail Values	Use this option to specify individual detail values to include. When you select this option, the Select Values/Nodes grid contains a single Select Value field.

Specify values by using the fields in the Select Values/Nodes grid, by selecting a value or a tree node.

	Click the Detail button to select the value from the list of available values. You can use this button to select a tree node or a specific value.
	Click the Tree button to open an interactive view of the tree specified in the Tree ID field. Expand the nodes as needed to view the parent that you want to insert. Click the node description to insert it into the Select Values/Nodes grid.
	Click the Refresh button to update your tree view. For example, if you change the tree ID, you need to click this button.

Defining Elimination Entities

This section provides an overview of elimination entities and discusses how to establish elimination entities.

Understanding Elimination Entities

Elimination entities are used to book the journal entries that result from consolidation processing. These entities are part of your consolidation tree; there must be a single elimination entity for each branch or parent node on the tree. The elimination entity doesn't necessarily represent an actual object within your organization, rather it is a logical object that the system uses to book elimination journals. The objects that you use as elimination entities must be defined to the system. For example, if you are consolidating by business unit, you would need to establish a warehouse business unit for each elimination business unit (by using the Warehouse Business Unit page). Likewise, if consolidating by department, each elimination department would need to be established (by using the EPM Foundation OW-E Department Dimension Maintenance page).

Page Used to Define Elimination Entities

Page Name	Object Name	Navigation	Usage
Elimination Entity	GC_ELIM_TBL	Global Consolidations, Define Consolidations, Common Definitions, Elimination Entity	Establish elimination entities by identifying the entities to which elimination journal entries that result from consolidation processing are booked.

Establishing Elimination Entities

Access the Elimination Entity page.

To access the page, specify the setID, consolidation dimension, ledger template, and value. The value is equivalent to the name of the elimination entity, and represents its value within the consolidation dimension.

Specify the effective date and status.

Primary Description	The primary description is used for the trial balance inquiry and reports.
Secondary Description	The secondary description is used for the trial balance inquiry and reports.

Get Prior Run Differences	Select this option to do comparisons between consolidation runs during processing. As a result, the Get Prior Run Differences check box is available on the Eliminations and Equitizations run control pages.
Book Code Group Functionality	Select this option to activate the book code dimension for capturing multi-GAAP reporting functionality. This allows you to capture and segregate data for statutory consolidation or regulatory consolidation reporting. By selecting this option, the inquiry pages and reports will have an additional column for book code designation. Specifically, the Trial Balance Inquiry page will contain primary and secondary book codes where primary book codes are made up of source ledger (LOC) data and secondary book codes (IAS) are made up of journal adjustment entries. You can turn this option on at anytime but the system will not update historical data with book code information. You must go back and manually adjust this data if you so require.
Row Level Security	Within this region, select the fields on which to enforce row-level security. It is recommended that you select two fields at most; performance degrades if you select more than two. When viewing consolidation inquiry pages, you are limited to viewing only those rows to which you have access, based on the defined row level security set up in PeopleSoft Enterprise Performance Warehouse, for the fields that you specify. The Business Unit check box is used to control security to specific ledger business units, not the consolidation ledger business unit. Note. If the Ledger Record and Ledger Template do not contain all of the fields listed for row level security enforcement, then the system ignores the Row-Level Security setting for those fields. For Example, Location and Line of Business are available for row level security enforcement, but those fields are not delivered in the Global Consolidations sample Ledger Records and Ledger Templates. Selecting those fields for the Row Level Security setting does not impact the sample ledgers. If you include these fields on the Ledger Record and Ledger Template, then the system enforces Row Level Security when accessing your ledger.
Report Row Level Security	Select this option if you want to enforce row level security during report processing. This allows processing of selected dimensions based on the row level security setup. For example, your user ID that you log onto the system may prevent you from processing reports for specific business units or accounts.
Preparation Load Balancing	Enter the minimum number of ledger business units that you want to process concurrently, and the maximum number of load cycles.

Primary Inquiry Options	Specify the default business unit, tree name, scenario ID, and fiscal year, ledger preparation phase. For the period, either select Most Recent Period, so that the latest period appears by default, or clear Most Recent Period, and enter a specific period in the Period field. Prep Phase is optional and allows you to specify the ledger preparation phase that you want to select as a primary inquiry. Your options for Prep Phase are Ledger Enrichment or Preparation Manager.
Additional Inquiry Options	Specify the default options to use for inquiry pages that enable you to compare data. Enter the scenario ID, and for the time frame to compare, select one of these options: Prior Period of the Primary Period: Compares with data from the previous period. Prior Year of Primary Period: Compares with data from the previous year. Same as Primary Period: Compares with data from the previous year. Specify: Compares with the fiscal year and period that you enter.
Book Code Group	Specify the default book code group. Book Code Group appears on the User Preferences - Inquiry page when book code functionality is enabled on the General Options page.
Detail fields to show when drilling to ledger	Insert rows within this grid and specify which dimension to display when viewing details for the data. Select Show Description to display the dimension value's description.
Display Tree using Description	Select if, on pages with trees, you prefer to see the description for the nodes rather than the node IDs.