Understanding Consolidation Processing

This section lists prerequisites and discusses:

Consolidation processing.
Reconciliation for consolidation processes.
Delivered application engines and job streams.

Note: This topic assumes that you are already familiar with run controls, jobstreams, and PeopleSoft Enterprise Process Scheduler.

See the product documentation for PeopleTools: PeopleSoft Process Scheduler

Prerequisites

Before processing consolidations, you must:

Prepare ledgers (including all related rules and processing).
Define consolidation models and include elimination, equitization, flows, and non-controlling interest groups.

Consolidation Processing

There are three main consolidation application engines: eliminations, data flows, and equitization. Each application engine is launched by a separate run control page. You can initiate and monitor consolidation processing from the Consolidation Manager page.

See Managing Consolidation Processing.

As with all application engines within the PeopleSoft EPM environment, you specify the following run control parameters: unit, scenario, fiscal year, and accounting period for each application engine. The system uses these parameters to determine which consolidation model to use.

For PeopleSoft Global Consolidations processes, the specified unit must be the common consolidation business unit. Depending on the processing method that you specify for the consolidation ledger template, the system processes either a single period or all periods for that fiscal year that are less than or equal to the specified run control period.

Global Consolidations uses several record objects during processing: the consolidation ledger (CLED), the input log (ILOG), the output log (OLOG), the journal table, and related temporary tables. During processing, the general data flow is:

The system retrieves data that matches the run control parameter criteria from the consolidation ledger and stores it in the input log (ILOG).
Processing occurs, using the consolidation model rules that apply.
The system writes results to the output log (OLOG) and calculates any out-of-balance amounts.
The system writes the resulting journal lines to the journal table that you define in the ledger template for the consolidation ledger.
Depending on the processing options that you select, the system posts the journals to the consolidation ledger as the last processing step, or you can run the Ledger Post application engine at a later time.

The system does not update the consolidation ledger with the results until you run the ledger post process.

Image: Overview of the Consolidation Process Flow

The following diagram illustrates the Consolidation Process Flow:

Spawning

When you process eliminations and equitization, the system uses spawning to process multiple jobs, optimizing performance. The main application engines, or parent jobs, spawn the child jobs.

During elimination processing, the system assigns one record suite to the parent elimination manager (GC_ELIMMGR) engine, spawns one job for intercompany eliminations, and as many non-controlling interest jobs as the number of remaining available record suites. For example, if there are a total of three record suites available, one is used by the elimination manager, one is used by the intercompany elimination spawned job, and the third is used for an NCI spawned job. If there are five record suites available, three can be used for non-controlling interest-spawned jobs.

During equitization processing, the system equitizes subsidiaries based on the ownership level sequence. Spawning of equitization jobs depends on the total number of subsidiaries in the ownership level divided by the number of record suites available. This strategy enables parallel processing for subsidiaries, reducing the amount of time required to process them all. The more record suites that are available, the faster processing occurs. For example, if there are a total of three record suites available during equitization processing, the system assigns one record suite to the parent equitization manager (GC_EQ_MGR) engine, spawning two (child) equitization jobs for each ownership level. When both jobs for the lowest ownership level are complete, the system spawns two more jobs for the next ownership level, and so on.

If you need to cancel processing for eliminations or equitization jobs, you should cancel the spawned jobs first (the child jobs), then the parent job. If you are using the delivered jobstreams for processing, you can identify parent jobs by the process name PF_JOBSTREAM. The process names for spawned jobs are:

GC_ICUELIMS for intercompany eliminations.
GC_NCI_ELIM for non-controlling interest eliminations.
GC_EQTZ for equitization.

ILOG and OLOG Maintenance for Reruns

During a rerun, the system adds the prior run's batch ID to GC_DELBATCH_TBL. The Delete Batch engine (GC_DELB) deletes the ILOG and OLOG data for the prior run batch. You should either run this as the last job in the jobstream when processing eliminations or equitization, or run it as a separate jobstream that you can schedule to run during off-peak hours—for example, sometime overnight. The delivered jobstream is GC_DELB.

Reconciliation for Ledger Preparation and Consolidation Processes

As part of consolidation processing, reconciliation occurs at several stages. The reconciliation programs include balance rules that check the records used during ledger preparation and consolidation processing.

For ledger preparation, the system uses a filter-based query that returns the count of the number of records in the source and target tables during calendar mapping, account mapping, and currency mapping. The number of records in the source and target should be equivalent.
For consolidation processing, the system uses a filter-based query that verifies that debits equal credits in the output journal, based on the balancing rule associated with the consolidation model.

This table describes the individual jobs that are used to reconcile specific aspects of ledger preparation or consolidation processing:

Job ID	Consolidation Phase	Description	Usage
GCRECNCAL	Ledger Preparation	Reconciliation for calendar mapping.	Counts the number of records in the source and target tables for each ledger business unit during the calendar mapping phase of ledger preparation processing. The counts should be the same. As illustrated in the diagram that follows this table, the reconciliation compares 1 and 2.
GCRECNCLED	Ledger Preparation	Reconciliation for ChartField mapping.	Counts the number of records in the source and target tables for each ledger business unit during the ChartField mapping phase of ledger preparation processing. The counts should be the same. As illustrated in the diagram that follows this table, the reconciliation compares 2 and 3.
GCRECNCUR	Ledger Preparation	Reconciliation for currency mapping.	Counts the number of records in the source and target tables for each ledger business unit during the currency mapping phase of ledger preparation processing. The counts should be the same. As illustrated in the diagram that follows this table, the reconciliation compares a and b for each ledger business unit that has a GC_SOURCE equal to 01 (the source staging ledger) and whose base currency field is not blank.
GCRECNELIM	Consolidation	Reconciliation for intercompany elimination processing.	Verifies that the output journal is balanced.
GCRECNEQTZ	Consolidation	Reconciliation for equitization processing.	Verifies that the output journal is balanced.
GCRECNNCI	Consolidation	Reconciliation for NCI processing (within intercompany elimination processing).	Verifies that the output journal is balanced.

Image: Ledger Preparation Reconciliation Points

This diagram illustrates the Ledger Preparation Reconciliation Points

These jobs are run as part of ledger preparation or consolidation processing. The IDs for the balance rules, filters, and constraints used by these jobs all start with GCRECN, and are in the SHARE SetID. For these jobs to work, you must not remove any rows from the delivered filter and constraint definitions. The delivered rules are intended primarily as examples; review them for applicability to your specific business requirements.

To set up the Consolidation Manager and Ledger Preparation Manager pages to view the status of the reconciliation jobs, use the Consolidation Processes page to add the job IDs to their related page, and then on the Status Details page, click the View Reconciliation Totals link to view the results.

Delivered Application Engines and Jobstreams

The Global Consolidation batch processes use several PeopleSoft application engine programs. This section provides a complete list of the engines used and the jobstream definitions that are provided with the delivered sample database in the SHARE SetID. This information is provided so that you can create your own jobstreams or modify the delivered ones to suit your implementation.

Delivered Application Engines

PeopleSoft Enterprise Performance Management applications use application engines to run each process. Engine metadata is delivered with the system; unless you are revising the application, you should not need to modify it. This metadata stores information about the various PeopleSoft application engine programs used within an engine. This table lists the delivered engines that are used by PeopleSoft Global Consolidations when processing consolidations by using the delivered jobstreams and their associated jobs:

Engine ID	Description	Usage
GC_CLOSMGR	Global Consolidations closing manager application engine.	Runs the closing process. Uses the GC_CLOSE_MGR application engine.
GC_DELB	Audit log cleanup engine.	Cleans up the ILOG and OLOG data for a prior run when you rerun any of the consolidation processes. Uses the GC_DELBATCH application engine. You should either run this as the last job in the jobstream when processing eliminations or equitization, or set it up as a separate jobstream that you can schedule to run during off-peak hours. See Understanding Consolidation Processing.
GC_ELIM	Spawned intercompany eliminations application engine.	Processes intercompany eliminations. Uses the GC_ICUELIMS application engine.
GC_ELIMMGR	Main elimination manager application engine. Spawns processing of the Intercompany Eliminations engine (GC_ELIM) and the NCI engine (GC_NCI).	Processes intercompany eliminations. Uses the GC_ELIM_MGR application engine.
GC_EQ_MGR	Main Equitization Manager application engine. Spawns processing of the equitization engine (GC_EQTZ).	Processes equitization. Uses the GC_EQTZ_MGR application engine.
GC_EQTZ	Spawned equitization application engine.	Processes equitization for each subsidiary entity. Uses the GC_EQTZ application engine.
GC_FILEIMP	File import application engine.	Processes file import. Uses the GC_FILE_IMP application engine.
GC_FLJRNL	Journal flow update application engine.	Processes journal flows. Updates the journal flow activity table based on the run criteria. Uses the GC_FLJRN_ENG application engine.
GC_FLOWFLT	Global Consolidations flow flattener application engine.	Creates a flattened table based on the flow group and the flow template attached to the model. Uses the GC_FLOW_FLAT application engine.
GC_FLSRC	Source flow update application engine.	Processes source flows. Updates the flow activity table based on the run criteria. Also calls the currency engine to perform translation of flow amounts. Uses the GC_FLSRC_ENG application engine.
GC_FX_MGR	Global Consolidations currency adjustment application engine	Processes currency adjustments. Uses the GC_FX_MGR application engine.
GC_JR_PUB	Journal publish application engine.	Publishes selected journals that result from consolidation processing. Uses the GC_JRNL_PUBL application engine. Note: This application engine publishes the journals only; you must set up application messaging to subscribe to the published journals. See Publishing Journals.
GC_JRNLEDT	Manual journal edit application engine.	Edits consolidation manual journals. Uses the GC_JRNLEDIT application engine.
GC_JRNLRCR	Consolidations create recurring journal application engine.	Creates recurring journals. Uses the GC_JRNL_RCR application engine.
GC_LEDVERF	GC ledger verification application engine.	Processes ledger verification rules. Uses the GC_LEDVERIFY application engine.
GC_MATCH	Matching report application engine.	Processes matching. Uses the GC_MATCH application engine.
GC_NCI	Spawned NCI application engine.	Processes NCI eliminations. Uses the GC_NCI_ELIM application engine.
GC_OWN_FLT	Ownership Inquiry Preparation engine.	Prepares a flattened ownership table prior to running the ownership inquiry. The flattened ownership table is populated with keys such as business unit, scenario, and as of date.
GC_PREP	Spawned ledger preparation application engine.	Processes ledger preparation. Uses the GC_PREP application engine.
GC_PREPMGR	Main ledger preparation process. Spawns processing of the ledger preparation engine (GC_PREP).	Processes ledger preparation. Uses the GC_PREP_MGR application engine.
GC_RECON	Reconciliation application engine.	Processes reconciliation rules defined for the ledger preparation and consolidation processes. Calls the PF_RECON application engine.
GC_VALID	Consolidation Validation application engine.	Validates consolidation rules and objects. A validation process that validates consolidation setups (elimination, non-controlling interest, equitization, ownership rules) and data preparation setups (ChartField, calendar, currency mapping). Uses the GC_VALIDATE application engine.
GCTREEFLAT	Tree flattener application engine.	Processes tree flattener. Uses the GC_TREE_FLAT application engine.
RECN	Reconciliation application engine.	PeopleSoft Enterprise Performance Management engine; processes reconciliation. Uses the PF_RECON application engine.
ALLOCATION	Allocation application engine.	PeopleSoft Enterprise Performance Management engine; processes allocations. Uses the PF_ALLOC_ENG application engine.
EDIT	PF Journal edit application engine.	PeopleSoft Enterprise Performance Management engine; processes journal edit. Uses the PF_EDIT application engine.
POST	PF Ledger post application engine.	PeopleSoft Enterprise Performance Management engine; processes ledger post. Uses the PF_POST application engine.
UNPOST	PF Ledger unpost application engine.	PeopleSoft Enterprise Performance Management engine; processes ledger unpost. Uses the PF_UNP application engine.
MERGE	Merge application engine.	PeopleSoft Enterprise Performance Management engine; merges temp tables to permanent tables. Uses the PF_MERGE application engine.

Delivered Jobstreams

PeopleSoft Global Consolidations uses jobstreams for processing. Jobstreams enable different users to run a series of application engines at the same time by using temporary tables. Instead of using fact tables in the Peoplesoft EPM database, temporary tables, using record suites, use only the relevant data from the main fact tables to run the application engines and process the data. This strategy enables the application engines in the jobstream to run faster (because the entire fact table is not being used) while keeping the fact tables open and accessible to other users so that they can run the same engines simultaneously. The record suites are assigned when the first application engine runs, then released when the last application engine is finished.

You associate each main application engine with a job ID on the Job Metadata page. You associate jobs with a jobstream on the Jobstream setup page. You must also define record suites for the jobstream on the Jobstream Record Suites page. A job must be unique across all jobstreams, so if you require additional jobstreams, you first need to create new jobs to use in each jobstream. This table lists each batch process, the delivered jobstream, and the engines and job IDs used in that jobstream:

Process	Delivered Jobstream ID	Application Engines Used (Engine ID)	Job IDs in Jobstream	Description
Closing	GC_CLOSMGR	GC_CLOSMGR MERGE	GC_CLOSMGR GC_MERGE	Global Consolidations closing process for year end closing and period roll forward.
Audit Log cleanup utility	GC_DELB	GC_DELB	GC_DELB	Cleans up ILOG and OLOG for prior run when you rerun eliminations or equitization.
Elimination	GC_ELIM	GC_ELIM	GC_ELIM	Processes intercompany eliminations. Uses the GC_ICUELIMS Application Engine program.
Elimination Manager	GC_ELIMMGR	GC_ELIMMGR MERGE	GC_ELIMMGR GC_ELIMMRG	Processes intercompany and non-controlling interest eliminations.
Equitization	GC_EQ_MGR	GC_EQ_MGR MERGE	GC_EQ_MGR GC_EQ_MRG	Processes equitization and NCI for current income.
Equitization	GC_EQTZ	GC_EQTZ	GC_EQTZ	Processes equitization.
GC file import	GC_FILEIMP	GC_FILEIMP	GC_FILEIMP	Import files.
Journal flow update	GC_FLJRNL	GC_FLJRNL MERGE	GC_FLJRNL GC_FLMERGE	Processes journal flow updates.
Flow flattener	GC_FLOWFLT	GC_FLOWFLT MERGE	GC_FLOWFLT GC_FLOWMRG	Creates a flattened table based on flow group and flow templates attached to the model.
Source flow update	GC_FLSRC	GC_FLSRC MERGE	GC_FLSRC GC_FLMERGE	Processes source flow updates.
Currency adjustment	GC_FX_MGR	GC_FX_MGR MERGE	GC_FX_MGR GC_MERGE	Processes currency adjustments.
Journal publish	GC_JR_PUB	GC_JR_PUB	GC_JR_PUB	Publishes journals.
Manual Journal Edit	GC_JRNLEDT	GC_JRNLEDT	GC_JRNLEDT	Processes manual journal edits.
Create Recurring Journals	GC_JRNLRCR	GC_JRNLRCR	GC_JRNLRCR	Processes recurring journal creation.
Ledger verification	GC_LEDVERF	GC_LEDVERF	GC_LEDVERF	Processes ledger verification.
Consolidation Match	GC_MATCH	GC_MATCH	GC_MATCH	Processes consolidation match report.
NCI Elimination	GC_NCI	GC_NCI	GC_NCI	Processes NCI eliminations.
Ownership Inquiry Preparation	GC_OWN_FLT	GC_OWN_FLT	GC_OWN_FLT	Moves data to flattened ownership table prior to running Ownership Inquiry.
Ledger Preparation	GC_PREP	GC_PREP	GC_PREP	Processes ledger preparation.
Ledger Preparation Manager	GC_PREPMGR	GC_PREPMGR MERGE	GC_PREPMGR GCPREPMRG	Processes ledger preparation.
Tree Flattener	GC_TREEFLT	GCTREEFLAT MERGE	GC_TREE GCTREEMRG	Processes tree flattener as a standalone job.
Validation	GC_VALID	GC_VALID	GC_VALID	Validates the consolidation setups (for example, elimination, non-controlling interest, equitization, ownership rules) and data preparation setups (for example, ChartField, calendar, and currency mapping).

Note: When running these jobs and jobstreams, do not select the As Of Dated Jobstream option on the run control page. This option is not supported for PeopleSoft Global Consolidations application engines. If you select this option, your results will be incorrect.