Results for “gcs_entry_headers”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GCS_ENTRY_HEADERS is the consolidation entry header table within the Oracle E-Business Suite Financial Consolidation Hub (GCS) module, identified in the ETRM metadata as obsolete. It stores the header-level definition and control attributes for consolidation entries—records that drive elimination, reclassification, and aggregation logic during the consolidation of legal entities into a consolidated reporting hierarchy. Each row represents a single named entry that is applied against a consolidation hierarchy for a defined calendar period range.

The table is owned by the GCS schema and, in the documented 12.1.1 physical schema, contains 27 columns. The table is not implemented in every database instance, consistent with the deprecated status of the Financial Consolidation Hub product. Its primary key is GCS_ENTRY_HEADERS_PK, defined on the ENTRY_ID column, with a supporting unique index GCS_ENTRY_HEADERS_U1 also on ENTRY_ID.

From a Data Vault modeling perspective, ETRM's heuristic classification places GCS_ENTRY_HEADERS as hub-leaning. Under that suggestion, ENTRY_ID functions as the hub business key, while descriptive and status attributes such as ENTRY_NAME, DISABLED_FLAG, and APPROVAL_STATUS_CODE would populate an associated satellite. The self-referencing foreign key on ASSOC_ENTRY_ID indicates a recursive relationship between entry headers, which a Data Vault model would typically capture as a link or a same-hub relationship.

Key Information Stored

The most significant columns are:

• ENTRY_ID — the surrogate primary key (GCS_ENTRY_HEADERS_PK) and the sole documented business-key candidate, carried by the unique index GCS_ENTRY_HEADERS_U1. It is the column referenced by all downstream foreign keys.
• ENTRY_NAME — the user-visible identifier for the consolidation entry.
• HIERARCHY_ID — foreign key to GCS_HIERARCHIES_B, scoping the entry to a consolidation hierarchy.
• ENTITY_ID — the legal entity to which the entry applies.
• CURRENCY_CODE and BALANCE_TYPE_CODE — the currency and balance type (for example, actual or translated) under which the entry operates.
• START_CAL_PERIOD_ID and END_CAL_PERIOD_ID — the effective calendar period range for the entry.
• ENTRY_TYPE_CODE — classifies the entry type within the consolidation engine.
• RULE_ID — foreign key to GCS_ELIM_RULES_B, linking the entry to a governing elimination rule.
• ASSOC_ENTRY_ID — self-referencing foreign key to GCS_ENTRY_HEADERS, associating one entry with another.
• PROCESSED_RUN_NAME and PROCESS_CODE — identify the consolidation run that consumed the entry and the processing context.
• APPROVAL_STATUS_CODE and WORKFLOW_KEY — approval state and workflow linkage for entry review.
• DISABLED_FLAG, SUSPENSE_EXCEEDED_FLAG, and PERIOD_INIT_ENTRY_FLAG — status flags controlling entry eligibility and exception handling.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical reporting scenarios include listing active entries for a hierarchy and period, auditing disabled or unapproved entries, and reconciling entries consumed by a specific consolidation run. A sample query joining the hierarchy table is:

• SELECT h.entry_id, h.entry_name, h.entity_id, h.approval_status_code FROM gcs_entry_headers h WHERE h.hierarchy_id = :p_hierarchy_id AND h.disabled_flag = 'N';
• SELECT h.entry_id, h.entry_name, r.rule_name FROM gcs_entry_headers h, gcs_elim_rules_b r WHERE h.rule_id = r.rule_id;
• SELECT h.entry_id, h.assoc_entry_id, h.processed_run_name FROM gcs_entry_headers h WHERE h.assoc_entry_id IS NOT NULL;

Because ENTRY_ID is the primary key and is indexed uniquely, joins from dependent tables to GCS_ENTRY_HEADERS are efficient single-row lookups. Period-range queries using START_CAL_PERIOD_ID and END_CAL_PERIOD_ID support effective-dating reports, and APPROVAL_STATUS_CODE combined with WORKFLOW_KEY supports workflow dashboards.

Related Objects

The most significant related objects, based on documented foreign key relationships, are:

• GCS_HIERARCHIES_B — referenced by GCS_ENTRY_HEADERS.HIERARCHY_ID; defines the consolidation hierarchy owning the entry.
• GCS_ELIM_RULES_B — referenced by GCS_ENTRY_HEADERS.RULE_ID; supplies the elimination rule applied to the entry.
• GCS_ENTRY_HEADERS (self) — referenced by GCS_ENTRY_HEADERS.ASSOC_ENTRY_ID, modeling paired or derived entries.
• GCS_CONS_ENG_RUN_DTLS — references this table through ENTRY_ID, STAT_ENTRY_ID, PRE_PROP_ENTRY_ID, and PRE_PROP_STAT_ENTRY_ID; records consolidation engine run detail and entry processing outcomes.
• GCS_CONS_IMPACT_ANALYSES — references this table through ENTRY_ID, STAT_ENTRY_ID, ORIGINAL_ENTRY_ID, and PRE_PROP_ENTRY_ID; stores impact analysis results tied to entry processing.

These dependencies confirm that GCS_ENTRY_HEADERS acts as a central parent object for consolidation run processing and impact analysis records, and that its references to hierarchies and elimination rules anchor entry behavior to consolidation setup data.