Search Results gcs_formula_statements_pkg

Overview

GCS_FORMULA_STATEMENTS_PKG is an APPS-owned PL/SQL package in Oracle E-Business Suite that supports the Oracle Governance, Risk, and Compliance (GRC) / Global Consolidation System (GCS) product family. Its documented API classification is OTHER, indicating it is not a primary public business API but rather a supporting data-maintenance package. The package serves as the programmatic interface for managing records in the GCS_FORMULA_STATEMENTS entity, which stores consolidation formula statement definitions used by the GCS consolidation engine to derive and report consolidated financial data across legal entities and ledgers. The package encapsulates the insert, update, load, and translation logic required to keep this configuration data consistent, insulating callers from the underlying table structure. It is marked VALID and depends only on SYS.STANDARD, meaning it is a self-contained utility with no cross-package dependencies within the APPS schema. It is not referenced by any other documented package, confirming its role as a leaf-level data access module rather than a shared library.

Key Procedures and Functions

The ETRM metadata documents four procedures or functions in this package:

• INSERT_ROW — Creates a new row in the GCS_FORMULA_STATEMENTS table. It is used when a new formula statement definition must be introduced into the consolidation configuration, handling the assignment of the primary key and any mandatory columns.
• UPDATE_ROW — Modifies an existing formula statement record. It applies changes to the attributes of a previously defined statement while preserving referential integrity with dependent consolidation data.
• LOAD_ROW — Performs a conditional load operation, typically combining insert-or-update behavior. This is the standard vehicle used by data-loading routines and seed-data migration utilities to populate GCS_FORMULA_STATEMENTS idempotently, ensuring a record is present and current regardless of whether it already exists.
• TRANSLATE_ROW — Populates or maintains translated (multilingual) values for the formula statement record. This supports Oracle EBS's multi-language architecture, allowing user-facing statement text to be stored per language.

No parameter signatures are documented, so callers should inspect the package specification for the exact argument lists before invoking these routines.

Tables Accessed

The package references two tables through APPS synonyms:

• GCS_FORMULA_STATEMENTS — The primary base table holding consolidation formula statement definitions. All four procedures operate against this table: INSERT_ROW and UPDATE_ROW perform DML, LOAD_ROW conditionally inserts or updates, and TRANSLATE_ROW maintains translated columns.
• DUAL — The standard Oracle single-row pseudo-table, used for scalar evaluations and simple SQL expressions within PL/SQL logic.

Usage Notes

Because the package is classified as OTHER and is not referenced by any other APPS package, it is typically invoked directly rather than through a higher-level API stack. The most common invocation contexts are:

• Oracle Forms — GRC/GCS setup forms that maintain formula statement definitions call these procedures to persist user changes, usually from POST-INSERT, POST-UPDATE, and POST-QUERY triggers or via the block's ON-INSERT / ON-UPDATE handlers.
• Concurrent programs and data migration scripts — LOAD_ROW and TRANSLATE_ROW are the natural entry points for batch loading or upgrading formula statement configuration during implementation, patching, or environment refresh.
• Custom extensions — Developers extending consolidation behavior may call these procedures to keep the formula statement table synchronized with external configuration sources.

Practitioners should treat this package as internal to the GCS consolidation configuration layer. Direct DML against GCS_FORMULA_STATEMENTS is discouraged in favor of these packaged procedures, which preserve the expected validation and translation semantics across both EBS 12.1.1 and 12.2.2 environments. As with all APPS packages containing row-level DML, callers should issue a commit or rollback appropriate to their transaction boundary, since the package itself does not manage transaction control.