Understanding the PeopleSoft Global Consolidations Architecture
This section discusses:
PeopleSoft EPM Warehouse components.
Ledger record objects.
Metadata.
Ledger data loading steps.
Note: The information in these topics assume that you are familiar with PeopleSoft Application Designer and PeopleSoft Enterprise Performance Management (EPM) Warehouse metadata.
PeopleSoft EPM Warehouse Components
One of the first procedures that you need to complete when implementing Global Consolidations is loading the supporting subsidiary ledger data that is to be consolidated into PeopleSoft EPM. The main components of the PeopleSoft EPM warehouse architecture are:
Operational Warehouse Staging (OWS).
The OWS area mirrors the data in your transactional system; it is used for staging data.
Operational Warehouse Enriched (OWE).
The OWE area stores the data that is used within the various PeopleSoft analytic applications, including Global Consolidations.
Multidimensional Warehouse (MDW).
MDW tables are subject-oriented sets of denormalized tables that are used for multidimensional analysis and in certified reporting solutions to produce reports.
Loading Data into the Warehouse Tables
You can use Extract, Transform, and Load (ETL) jobs to load source subsidiary ledger data into the operational warehouse (OW). The data is first loaded to the OWS tables, and then to the OWE tables. For detailed information about the PeopleSoft Enterprise Performance Management architecture and use of these tools, please refer to the PeopleSoft Enterprise Performance Management Fundamentals 9.1 Documentaion.
You can also import subsidiary ledger data from spreadsheets to the OWE Spreadsheet/Manual Entry Ledger table (GC_LEDMANL_F00). This table also stores data that is manually entered through the Manual Ledger Data Entry component. These methods of data import load data directly from an external ledger system and directly into the OWE.
Ledger Record Objects
PeopleSoft Global Consolidations is delivered with the ledger record objects that you will need for consolidation processing. You can also use PeopleSoft Application Designer to create or modify these ledger record objects, as long as they contain the minimum set of fields that Global Consolidations requires. This table defines those record objects and how they are used.
|
Ledger Record |
Description |
|---|---|
|
Spreadsheet/Manual Entry Ledger |
This record contains the subsidiary ledger data that you import from a spreadsheet or enter manually into the OWE. |
|
Subsidiary Source Ledger |
This record contains the subsidiary ledger data that you ETL into the OWS, then move into the OWE using another set of ETL jobs. There can be multiple subsidiary source ledgers per consolidation ledger. |
|
Source Staging Ledger (SLED) |
This record is a copy of your subsidiary source ledger record, with several additional fields that are required by Global Consolidations. Any online pages that navigate to the source data use this ledger record object. You will typically have one source staging ledger record for each source subsidiary ledger that you plan to process through Ledger Preparation. The source staging ledger is used as the source for Data Mapper rules, which map ChartField values to the consolidation ledger. |
|
Mapped Ledger (MLED) |
This record stores the ledger data after the ledger preparation process maps the subsidiary ledger data to the common consolidation structure. You will typically have one mapped ledger record for each consolidation ledger record. The mapped ledger is used as the target for Data Mapper rules. |
|
Consolidation Ledger (CLED) |
This record stores the ledger data at the completion of ledger preparation processing. The system uses this record as input into the various consolidation processes. You will typically have one consolidation ledger record for each different ledger structure that you plan to consolidate. A single consolidation ledger can be shared between multiple consolidation models, because the consolidation ledger record includes the scenario field as a key. |
Metadata
Anytime you add or revise a record for use with Global Consolidations, you must create or update its associated metadata. You create the records by using PeopleSoft Application Designer, then define the EPM metadata by using several PeopleSoft EPM pages. You use record metadata to define any new records that you create. If you make changes to a record, such as adding a field, you must change its data map to reflect the changes that you made in PeopleSoft Application Designer. You must also recompile its associated record metadata, table map, data map, filters, constraints, and data mapper rules.
Note: When you define record metadata for any records that will be used for Global Consolidations, you must set the Owner/Source field to Global Consolidation.