Search Results gcs_entry_headers_pk

Overview

The GCS_ENTRY_HEADERS table is a core data object within the Oracle E-Business Suite module GCS - Financial Consolidation Hub, which is documented as obsolete in the provided metadata for releases 12.1.1 and 12.2.2. This table serves as the primary header record for consolidation journal entries. It functions as the master control point for manual, system-generated, or imported adjustment entries made during the financial consolidation process. The table's primary role is to store high-level metadata about each entry, such as its status, type, and associated consolidation context, which is then linked to detailed line items in related tables. The metadata explicitly states it is "Not implemented in this database," indicating it may not be present in a standard installation or may be a legacy artifact.

Key Information Stored

While the provided excerpt does not list specific columns beyond key identifiers, the primary and foreign key relationships define the critical data points stored. The central column is ENTRY_ID, which is the unique primary key (GCS_ENTRY_HEADERS_PK) for every consolidation entry. Other essential foreign key columns establish the entry's operational context: HIERARCHY_ID links to the consolidation hierarchy (GCS_HIERARCHIES_B), RULE_ID associates the entry with a specific elimination rule (GCS_ELIM_RULES_B), and ASSOC_ENTRY_ID enables a self-referential relationship, likely for linking related entries such as a reversal or a statistical entry to its primary counterpart. Additional attributes typically found in such header tables would include entry status, creation date, last update date, description, consolidation entity, period, and entry type (e.g., manual adjustment, elimination, reclassification).

Common Use Cases and Queries

This table is central to querying and reporting on the history and status of consolidation adjustments. Common operational scenarios include auditing all manual entries for a specific period, tracing the lineage of an elimination entry back to its source rule, or identifying all entries associated with a particular consolidation run. A typical query would join GCS_ENTRY_HEADERS to its detail lines (commonly a table like GCS_ENTRY_LINES, inferred but not listed) and related master data. For example, to find all active adjustment entries for a hierarchy, one might use a pattern such as: SELECT geh.ENTRY_ID, geh.DESCRIPTION, geh.STATUS, geh.HIERARCHY_ID FROM GCS_ENTRY_HEADERS geh WHERE geh.HIERARCHY_ID = :p_hier_id AND geh.PERIOD_NAME = :p_period;. Another critical use case is impact analysis, where entries are traced through various stages of processing, as evidenced by the multiple foreign key references from the GCS_CONS_IMPACT_ANALYSES table.

Related Objects

The table maintains extensive relationships within the Consolidation Hub schema, as documented by the foreign key metadata.

• Referenced by GCS_ENTRY_HEADERS (Self): Column ASSOC_ENTRY_ID references ENTRY_ID, creating a hierarchical or associative link between entries.
• References Outward:
  • GCS_HIERARCHIES_B via HIERARCHY_ID
  • GCS_ELIM_RULES_B via RULE_ID
• Referenced by Other Tables:
  • GCS_CONS_ENG_RUN_DTLS: Links consolidation engine run details to specific entries via PRE_PROP_ENTRY_ID, PRE_PROP_STAT_ENTRY_ID, ENTRY_ID, and STAT_ENTRY_ID.
  • GCS_CONS_IMPACT_ANALYSES: Tracks the impact of consolidation processes on entries using STAT_ENTRY_ID, ENTRY_ID, ORIGINAL_ENTRY_ID, and PRE_PROP_ENTRY_ID.

These relationships underscore the table's role as a central nexus for tracking the flow and state of data through the consolidation engine and related analytical processes.