Results for “measure_type_code”

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

Overview

GCS_DATA_SUB_DTLS is a Financial Consolidation Hub (GCS) table within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store tracking information on pristine data loads made to FEM_BALANCES, the balances table used by the Enterprise Performance Foundation / Financial Consolidation Hub consolidation engine. The table records the parameters, timing, and status of each data-load event so that the consolidation process can trace which source data was loaded, under which rule set, and with what outcome.

Within the ETRM documentation this object is flagged as obsolete for the GCS product line, and the referenced implementation shows it as "Not implemented in this database." Customers on 12.1.1 or 12.2.2 should therefore treat it as a legacy artifact whose presence depends on whether the Financial Consolidation Hub data-load subsystem was ever provisioned in their instance.

The heuristic Data Vault classification mined from the foreign-key structure is satellite-leaning. This is a modeling suggestion only: the table carries a single-column primary key (LOAD_ID) and a dense set of descriptive and status attributes, which is characteristic of a satellite attached to a load hub or link, rather than an independent hub or an associative link.

Key Information Stored

The physical schema documents 27 columns. The most operationally significant are the load identifiers and the consolidation context fields:

• LOAD_ID — surrogate primary key, enforced by GCS_DATA_SUB_DTLS_PK and also by unique index GCS_DATA_SUB_DTLS_U1. This is the business-key candidate for the load event itself.
• LOAD_NAME — human-readable label for the load run.
• ENTITY_ID, CAL_PERIOD_ID, CURRENCY_CODE, BALANCE_TYPE_CODE — the consolidation dimension context (entity, calendar period, currency, and balance type) against which the load was applied.
• LOAD_METHOD_CODE, CURRENCY_TYPE_CODE, AMOUNT_TYPE_CODE, MEASURE_TYPE_CODE — classification codes describing how the data was sourced and interpreted.
• RULE_SET_ID, VALIDATION_RULE_SET_ID, BALANCES_RULE_ID — the lexical mapping and validation rule sets applied to the load.
• ASSOCIATED_REQUEST_ID — the concurrent request that executed the load, linking the row back to the concurrent manager.
• START_TIME, END_TIME, STATUS_CODE — execution timing and outcome.
• LOCKED_FLAG, MOST_RECENT_FLAG — concurrency and versioning markers indicating whether the load is currently held and whether it is the latest run.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — standard EBS audit and optimistic-locking columns.

Common Use Cases and Queries

The primary use case is load reconciliation: confirming that a pristine data load completed against FEM_BALANCES, identifying the rule set applied, and diagnosing failures. A typical query retrieves recent successful loads for an entity and period:

• SELECT LOAD_ID, LOAD_NAME, ENTITY_ID, CAL_PERIOD_ID, STATUS_CODE, START_TIME, END_TIME FROM GCS_DATA_SUB_DTLS WHERE ENTITY_ID = :entity AND CAL_PERIOD_ID = :period AND STATUS_CODE = 'SUCCESS' ORDER BY START_TIME DESC;
• Correlate a load with its concurrent request: SELECT d.LOAD_ID, d.LOAD_NAME, r.REQUEST_ID, r.PHASE_CODE, r.STATUS_CODE FROM GCS_DATA_SUB_DTLS d JOIN FND_CONCURRENT_REQUESTS r ON r.REQUEST_ID = d.ASSOCIATED_REQUEST_ID WHERE d.LOAD_ID = :load_id;
• Find the most recent load per entity using MOST_RECENT_FLAG, and identify locked loads via LOCKED_FLAG for troubleshooting concurrency.
• Join to GCS_LEX_MAP_RULE_SETS on RULE_SET_ID or VALIDATION_RULE_SET_ID to report which mapping and validation rules governed each load.

These patterns support audit reporting, multi-period consolidation variance analysis, and root-cause investigation of consolidation discrepancies.

Related Objects

• GCS_CONS_IMPACT_ANALYSES.LOAD_ID → GCS_DATA_SUB_DTLS.LOAD_ID — impact-analysis records that depend on this load tracking entry.
• GCS_LEX_MAP_RULE_SETS — referenced twice, via RULE_SET_ID and VALIDATION_RULE_SET_ID.
• FND_CONCURRENT_REQUESTS — referenced via ASSOCIATED_REQUEST_ID for execution status.
• FND_CURRENCIES — referenced via CURRENCY_CODE for currency validation.
• FEM_BALANCES — the target balances table the tracking rows describe, though no direct FK is documented.