Search Results gcs_data_sub_dtls




Overview
Explore in AI Chat

Overview

The GCS_DATA_SUB_DTLS table is a core data object within the Oracle E-Business Suite Financial Consolidation Hub (GCS) module. Its primary function is to serve as a detailed audit and tracking log for "pristine" data loads into the central balances table, FEM_BALANCES. A pristine load refers to the initial submission of financial data from a source system before any consolidation or transformation rules are applied. This table is critical for maintaining data lineage, enabling impact analysis, and troubleshooting the data submission process. It is important to note that the GCS module is marked as obsolete in the provided metadata for EBS 12.1.1 and 12.2.2, indicating its functionality may be superseded by other applications like Oracle Financial Consolidation and Close Cloud in contemporary implementations.

Key Information Stored

The table's structure is designed to capture metadata about each data submission. The primary key, LOAD_ID, uniquely identifies each submission instance. Other significant columns, as indicated by the foreign key relationships, include RULE_SET_ID and VALIDATION_RULE_SET_ID, which link to the GCS_LEX_MAP_RULE_SETS table to record the mapping and validation rule sets applied during the load. The ASSOCIATED_REQUEST_ID column references FND_CONCURRENT_REQUESTS, providing a direct link to the EBS concurrent manager job that executed the load process. The CURRENCY_CODE column, linked to FND_CURRENCIES, denotes the transaction currency of the submitted data. While the specific column for BALANCES_RULE_ID is noted, its target foreign table is unspecified in the provided metadata.

Common Use Cases and Queries

This table is primarily used for administrative reporting and audit trails within the consolidation process. Common scenarios include tracing the origin of balances in FEM_BALANCES back to a specific load job, analyzing submission history for a particular entity or period, and investigating failed data loads by examining the associated request details. A typical query would join GCS_DATA_SUB_DTLS with FND_CONCURRENT_REQUESTS to get the status and parameters of a load, or with GCS_CONS_IMPACT_ANALYSES to review the consolidation impact of a specific data submission.

Sample Query Pattern:
SELECT d.LOAD_ID, d.CURRENCY_CODE, r.request_date, r.phase_code, r.status_code
FROM GCS_DATA_SUB_DTLS d,
FND_CONCURRENT_REQUESTS r
WHERE d.ASSOCIATED_REQUEST_ID = r.request_id
AND r.actual_completion_date > SYSDATE - 30
ORDER BY r.request_date DESC;

Related Objects

The GCS_DATA_SUB_DTLS table maintains integral relationships with several other EBS objects, as documented in the provided metadata.

  • Referenced Foreign Keys (This table references):
    • FND_CURRENCIES: Via GCS_DATA_SUB_DTLS.CURRENCY_CODE.
    • GCS_LEX_MAP_RULE_SETS: Via GCS_DATA_SUB_DTLS.RULE_SET_ID and GCS_DATA_SUB_DTLS.VALIDATION_RULE_SET_ID.
    • FND_CONCURRENT_REQUESTS: Via GCS_DATA_SUB_DTLS.ASSOCIATED_REQUEST_ID.
  • Referencing Foreign Key (Another table references this):
    • GCS_CONS_IMPACT_ANALYSES: The column GCS_CONS_IMPACT_ANALYSES.LOAD_ID references GCS_DATA_SUB_DTLS.LOAD_ID, linking impact analysis results to a specific data submission.
  • Primary Target: The table's core purpose is to track loads into FEM_BALANCES, establishing a critical data flow relationship, though this is not enforced as a formal foreign key.