Search Results gcs_main_data_prep

Overview

GCS_DATA_PREP_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the Financials/consolidation domain. Its purpose, as stated in the package header, is to provide the "Package procedures for the Data Preparation Program." In practical terms, this package supports the Financial Consolidation Hub (FCH) / Global Consolidation System (GCS) by preparing source ledger and subledger data so that it can be consumed by the Consolidation Engine. The Data Preparation Program extracts, validates, and stages balances and transaction details from source entities, executes currency translation where required, applies proportional consolidation rules, and populates the tables the consolidation process reads for subsequent steps such as intercompany elimination and parent-level aggregation. The package is defined as AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user rather than its owner, which is relevant for security and for any direct invocation outside the standard concurrent program path.

Key Procedures and Functions

• GCS_MAIN_DATA_PREP — The primary entry point. According to the source header, it is "called via the SRS submission performed by the Consolidation Engine" and then dispatches to the appropriate routines to complete the full data preparation process. It accepts arguments that include the consolidation hierarchy identifier, entity identifier, target calendar period, execution mode (FULL or INCREMENTAL), the various entry identifiers used to distinguish STAT currency lines, other lines, and proportional consolidation lines, the consolidation relationship identifier, and the balance type code (ACTUAL or ADB). It also contains standard SRS error buffer and return code parameters.
• GCS_INCREMENTAL_DATA_PREP — Documented as being invoked through the SRS submission performed by the Consolidation Engine, this procedure performs the incremental variant of data preparation, processing only changes since the last load rather than the full data set. The source header lists the standard SRS error buffer and return code arguments, and it parallels the main procedure's argument structure.
• CREATE_PROCESS — Present in the package's documented interface but not detailed in the ETRM excerpt. Consistent with the naming conventions of consolidation programs, it is used to establish or register a data preparation process (for example, creating a run or process record) before the main preparation routines execute.

Note: the actual parameter lists of GCS_INCREMENTAL_DATA_PREP and CREATE_PROCESS are not reproduced in the excerpt; only GCS_MAIN_DATA_PREP's signature is documented above.

Tables Accessed

The package reads and writes through APPS synonyms. The most relevant objects include:

• GCS_DATA_SUB_DTLS, GCS_ENTRY_HEADERS_S, GCS_CONS_ENG_RUNS, and GCS_CONS_ENG_RUN_DTLS — the staging and run-tracking tables where prepared data and their processing status are persisted.
• GCS_CONS_RELATIONSHIPS — provides consolidation relationship definitions used to determine proportional versus full consolidation treatment.
• GCS_CAL_PERIOD_MAPS, GCS_CAL_PERIOD_MAPS_GT, and GCS_CAL_PERIOD_MAP_DTLS — calendar period mapping tables used to translate source periods into the target consolidation period.
• FEM_CAL_PERIODS_ATTR and FEM_CAL_PERIODS_B — Enterprise Planning and Management calendar period definitions.
• FEM_EXT_ACCT_TYPES_ATTR, FEM_LEDGERS_ATTR, FEM_LN_ITEMS_ATTR — FEM attribute and ledger structures supplying account type and line item metadata.
• GCS_ENTITIES_ATTR and GCS_ENTITY_CONS_ATTRS — entity and entity-consolidation attribute definitions used to select the correct entities and consolidation parameters for each run.

Usage Notes

GCS_DATA_PREP_PKG is not intended for direct interactive invocation. It is designed to be driven by the Consolidation Engine, which submits an SRS (Standard Request Submission) request that calls one of the data preparation procedures with the standard x_errbuf and x_retcode OUT parameters. The execution mode argument (FULL or INCREMENTAL) determines which entry point is used, with full mode running GCS_MAIN_DATA_PREP and incremental mode running GCS_INCREMENTAL_DATA_PREP. The package is referenced by two other packages within the APPS schema, confirming that it is part of a wider consolidation orchestration chain rather than a standalone utility. Because the package uses AUTHID CURRENT_USER, any custom code that invokes it must ensure the calling schema has the necessary object and execute privileges on the underlying GCS and FEM tables as well as on the package itself. Custom extensions should attach to the consolidation process through the documented entry procedures, preserving the argument contract (hierarchy, entity, period, execution mode, entry identifiers, relationship, balance type) rather than modifying the package body.