Results for “line_item_id”

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

Overview

The GCS_INTERCO_MEMBERS table belongs to the GCS product family, Financial Consolidation Hub, and is documented in Oracle E-Business Suite 12.1.1 and 12.2.2 as an obsolete object. Its documented purpose is to store intercompany line item elimination sets, which define the combinations of consolidation rule, line item group, and line item identifier that participate in intercompany elimination processing during financial consolidation. In a functioning consolidation implementation, this table would act as the configuration bridge between a consolidation rule and the individual line items that the rule eliminates when intercompany balances and transactions are offset prior to producing consolidated financial statements.

The ETRM metadata records this object as "Not implemented in this database," and classifies it as an obsolete component of the Financial Consolidation Hub. Under the heuristic Data Vault classification mined from its foreign key structure, the table is identified as standalone. From a modeling perspective, this suggests the object behaves as an independent entity or reference structure rather than as a conventional hub, link, or satellite within a Data Vault design. Its composite primary key of RULE_ID, LINE_ITEM_GROUP, and LINE_ITEM_ID functions more like a configuration association or membership set than a transactional fact. Because the object is obsolete, this classification is best treated as a historical modeling observation rather than guidance for new development.

Key Information Stored

The documented physical schema for 12.1.1 lists the GCS owner and nine columns. The most significant columns are the three that make up the primary key and unique business-key candidate:

• RULE_ID — Identifies the consolidation or elimination rule to which the member line items belong. It is the leading column of the GCS_INTERCO_MEMBERS_PK primary key and of the GCS_INTERCO_MEMBERS_U1 unique index.
• LINE_ITEM_GROUP — Groups related line items within the elimination set, allowing a rule to process multiple related accounts or line items as a single logical unit. It is the second component of both the primary key and the unique index.
• LINE_ITEM_ID — Identifies the specific line item that is a member of the elimination set. It completes the composite primary key and unique index.

The remaining documented columns are standard Oracle EBS transactional and concurrency columns: OBJECT_VERSION_NUMBER, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. The presence of these audit columns indicates that the table was designed to be maintained through normal EBS form and API processing with row-level locking. Because RULE_ID, LINE_ITEM_GROUP, and LINE_ITEM_ID together constitute both the primary key and the only documented unique index, there is no separate surrogate key column; the business key and the primary key are identical, which is typical of pure intersection or membership tables in the EBS data model.

Common Use Cases and Queries

Because the table is documented as obsolete and not implemented, there are no supported runtime use cases in current releases. Historical reporting and migration analysis remain the primary practical scenarios. A typical query enumerates the line items associated with a given elimination rule, for example selecting RULE_ID, LINE_ITEM_GROUP, and LINE_ITEM_ID from GCS_INTERCO_MEMBERS where RULE_ID equals a supplied value, optionally ordered by LINE_ITEM_GROUP and LINE_ITEM_ID. Analysts migrating configuration from an older Financial Consolidation Hub environment might join this table to rule and line item reference tables to reconstruct elimination definitions. Data lineage and audit queries can use CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY to determine when a membership set was established or last changed. Any such query should be validated against the target database first, since the ETRM documentation explicitly states the object is not implemented.

Related Objects

The metadata does not document explicit foreign key targets, and the object is classified as standalone. In the broader Financial Consolidation Hub schema, the columns imply relationships to the following objects, which should be confirmed against the actual database before reliance:

• GCS_INTERCO_RULES (or the corresponding elimination rule definition table) — joined on RULE_ID to resolve rule attributes for each membership set.
• GCS_LINE_ITEMS (or the corresponding line item definition table) — joined on LINE_ITEM_ID to resolve line item names and attributes.
• GCS_LINE_ITEM_GROUPS (or equivalent grouping table) — joined on LINE_ITEM_GROUP to resolve group definitions.
• GCS_INTERCO_BALANCES or intercompany balance tables — used alongside this configuration during elimination processing.
• GCS_CONSOLIDATION_RULES — parent consolidation logic that references elimination rules and their member sets.

These relationships are inferred from column naming conventions consistent with the GCS schema. Organizations should treat the table as obsolete, avoid building new dependencies on it, and reference Oracle's current replacement functionality for intercompany elimination configuration in supported releases.