Search Results gcs_entry_headers_s

Overview

The APPS.GCS_ENTRY_PKG package body is a core component of the Oracle E-Business Suite (EBS) Financial Consolidation Hub (FCH), also delivered under the Global Consolidation System (GCS) module. In Oracle EBS 12.1.1 and 12.2.2, this package encapsulates the business logic responsible for creating, importing, validating, and maintaining consolidation entry headers and their associated entry lines. Consolidation entries represent the adjusting, eliminating, and reclassification journal entries that a parent entity applies to subsidiary balances during a consolidation run.

The package acts as a server-side API layer that shields callers — Oracle Forms, concurrent programs, and workflow-enabled processes — from the underlying data model. It abstracts the multi-table relationships required to persist an entry header, its descriptive flexfields, its lines, and the audit columns maintained through the GCS_ENTRY_HEADERS_S sequence. The package status is VALID in the ETRM repository, confirming it is a supported, compiled object in the APPS schema.

Key Procedures and Functions

The ETRM metadata documents six public program units:

• UPLOAD_ENTRY_HEADERS — Drives the bulk import of consolidation entry headers from an external or staged source, iterating validated rows into the transactional tables.
• MANUAL_ENTRIES_IMPORT — Supports the import of manually entered consolidation adjustments, applying the same validation and derivation rules as the interactive entry path.
• CREATE_ENTRY_HEADER — The primary creation routine, responsible for generating a new entry header record including currency, calendar period, entity, and category context.
• INSERT_ENTRY_HEADER — Performs the low-level insert into GCS_ENTRY_HEADERS, coordinating the GCS_ENTRY_HEADERS_S sequence to obtain the surrogate key.
• DELETE_ENTRY — Removes an entry header and, in the process, its dependent entry lines, preserving referential integrity.
• RAISE_DISABLE_EVENT — Publishes a Workflow business event, allowing downstream listeners to react to the disablement or invalidation of an entry.

Because the documented signature detail is limited, parameter lists are intentionally not reproduced here; integrators should consult the object's source in the APPS schema for exact argument definitions.

Tables Accessed

The package reads and writes the core GCS consolidation tables and a set of FEM (Financial Enterprise Management) reference attributes:

• GCS_ENTRY_HEADERS and GCS_ENTRY_HEADERS_S — the header store and its surrogate key sequence.
• GCS_ENTRY_LINES — the detail lines of each consolidation entry.
• GCS_CATEGORIES_B, GCS_HIERARCHIES_B, GCS_HIER_GRP_MEMBERS — provide the category and hierarchy context for validation of each entry.
• GCS_ELIM_RULES_VL and GCS_CONS_ENG_RUN_DTLS — elimination rule and consolidation run context.
• FEM_CAL_PERIODS_ATTR, FEM_ENTITIES_VL, FEM_EXT_ACCT_TYPES_ATTR, FEM_LN_ITEMS_ATTR — reference attributes resolving period, entity, account type and line item semantics.
• FND_CURRENCIES, FND_GLOBAL, FND_PROFILE, FND_API, FND_MESSAGE, FND_LOG, FND_FILE — standard EBS infrastructure for currency validation, session context, profile options, error messaging, logging, and file handling.
• FND_REQUEST, WF_EVENT, WF_PARAMETER_LIST_T — concurrent request submission and workflow event raising.

Usage Notes

GCS_ENTRY_PKG is typically invoked from the Consolidation Entry forms within Financial Consolidation Hub, from concurrent programs that import manual or uploaded entries, and from custom PL/SQL integrations that programmatically generate consolidation adjustments. The package honours the FND_API error-handling convention, returning status and message through the standard API output parameters, and it raises Workflow events so that approval and downstream processes (notably GCS_ADJ_APPROVAL_WF_PKG) can subscribe to entry lifecycle changes. Because the metadata notes the package is not referenced by any database object but is referenced by seven other packages, it should be regarded as a leaf-level business logic layer consumed by peer GCS packages rather than by database-level triggers or constraints. Developers customizing FCH should invoke these routines through the documented entry points rather than inserting directly into GCS_ENTRY_HEADERS, ensuring sequence allocation, validation, and workflow notification remain intact.