Search Results gcs_entity_cctr_orgs

Overview

GCS_ENTITY_CCTR_ORGS is a table within the GCS (Financial Consolidation Hub) product family in Oracle E-Business Suite. Its documented description identifies it as a "Summary of all GCS entity organizations," meaning it records the association between a consolidation entity and the company cost center organization used in consolidation processing. The ETRM metadata explicitly marks the product as obsolete and states that the object is "Not implemented in this database," so in a running 12.1.1 or 12.2.2 instance this table may not exist, may exist only as a legacy artifact, or may be present solely in a partially upgraded schema. Consultants encountering the name during impact analysis, upgrade assessment, or customization review should treat it as a deprecated consolidation object rather than an active transaction table.

The heuristic Data Vault classification mined from the foreign-key structure is standalone. In modeling terms, this suggests a link-style or association structure rather than a pure hub or satellite: the object exists to relate two identifying keys rather than to carry richly versioned descriptive attributes. The absence of downstream dependents in the mined FK structure reinforces that interpretation.

Key Information Stored

The table is documented with eight physical columns owned by the GCS schema. Of these, the most significant are:

• ENTITY_ID — the consolidation entity identifier; part of the composite primary key and the primary driver of the entity-to-organization mapping.
• COMPANY_COST_CENTER_ORG_ID — the organization identifier representing the company cost center; the second component of the composite primary key.
• OBJECT_VERSION_NUMBER — the optimistic locking column standard in EBS tables, used to detect concurrent updates.
• CREATION_DATE / CREATED_BY — audit columns recording when and by whom the row was inserted.
• LAST_UPDATE_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN — audit columns recording the most recent modification, the updating user, and the login context.

Two unique indexes are documented. GCS_ENTITY_CCTR_ORGS_PK is the primary key on the composite of ENTITY_ID and COMPANY_COST_CENTER_ORG_ID, and GCS_ENTITY_CCTR_ORGS_U1 carries an identical column list and is therefore documented as a business-key candidate for the same pair. Users searching for "gcs_entity_cctr_orgs_pk" are almost certainly looking for this composite primary key constraint definition. Note that no surrogate single-column key is documented; ENTITY_ID is not independently unique.

Common Use Cases and Queries

Because the table represents the entity-to-cost-center organization relationship, its principal use is determining which cost center organization is bound to a given consolidation entity, or conversely, enumerating all entities assigned to a particular organization. A representative query follows:

• SELECT entity_id, company_cost_center_org_id FROM gcs_entity_cctr_orgs WHERE entity_id = :entity_id; — retrieves organizations for a consolidation entity.
• SELECT entity_id FROM gcs_entity_cctr_orgs WHERE company_cost_center_org_id = :org_id; — reverse lookup for organizational reporting.
• SELECT * FROM gcs_entity_cctr_orgs WHERE last_update_date >= :since_date; — change-audit style extract.

Typical reporting scenarios include reconciliation extracts validating that every consolidation entity has at least one assigned organization, and migration scripts confirming that legacy mappings were carried forward. Given the obsolete status, any query should be preceded by a data dictionary check such as SELECT table_name FROM all_tables WHERE table_name = 'GCS_ENTITY_CCTR_ORGS'; to confirm existence before execution, and defensive coding should handle ORA-00942 gracefully.

Related Objects

The mined relationship data classifies the object as standalone, with no documented foreign keys to other tables in the ETRM repository. Consequently, related objects are inferred from the shared GCS consolidation domain rather than from enforced constraints:

• GCS entity master tables keyed by ENTITY_ID, which this table references logically rather than through a documented FK.
• GCS consolidation mapping and hierarchy tables that consume the entity-to-organization relationship during consolidation runs.
• HR organization tables that supply COMPANY_COST_CENTER_ORG_ID, since the column carries the standard _ORG_ID suffix.
• GCS concurrent programs and consolidation engine packages that read these mappings at runtime.

Any integration point should be validated against the target instance, because the documented state is "not implemented," and references to this object may simply be stale metadata retained from earlier ETRM documentation sets.