Search Results gcs_lex_map_derivations




Overview
Explore in AI Chat

Overview

The GCS_LEX_MAP_DERIVATIONS table is a core repository object within Oracle E-Business Suite's Financial Consolidation Hub (GCS) module, specifically for versions 12.1.1 and 12.2.2. It serves as the master definition table for transformation rule set derivations. In the context of the consolidation process, a derivation defines the logic for populating a target consolidation ledger column based on source data and specified business rules. This table is central to the configuration of the data transformation engine, which standardizes and maps disparate source system data into a unified format suitable for corporate-level financial consolidation and reporting.

Key Information Stored

While the full column list is not detailed in the provided metadata, the foreign key relationships explicitly identify the critical columns that define a derivation's behavior and relationships. The primary key, DERIVATION_ID, uniquely identifies each derivation rule. The RULE_ID column links the derivation to its parent rule definition in the GCS_LEX_MAP_RULES table. The derivation's logic type is indicated by references to either a lookup operation (via LOOKUP_TABLE_ID and LOOKUP_RESULT_COLUMN_ID pointing to GCS_LEX_MAP_STRUCTS and GCS_LEX_MAP_COLUMNS, respectively) or a custom PL/SQL function (via FUNCTION_NAME pointing to GCS_LEX_MAP_PLSQL_FUNCS). This structure allows derivations to be either table-driven or procedurally defined.

Common Use Cases and Queries

This table is primarily accessed during the design and troubleshooting of consolidation transformation rules. Implementation consultants use it to audit and validate the configured derivation logic. A common reporting need is to list all derivations associated with a specific transformation rule set to understand the complete data mapping flow. For troubleshooting data transformation errors, administrators may query derivations to identify the source of incorrect target values, examining the linked lookup tables or functions. A typical diagnostic query would join GCS_LEX_MAP_DERIVATIONS with GCS_LEX_MAP_RULES and the relevant lookup or function tables to present a human-readable mapping definition.

Related Objects

The GCS_LEX_MAP_DERIVATIONS table exists within a tightly integrated schema. Its documented relationships are as follows:

  • Parent References (Foreign Keys): This table references:
    • GCS_LEX_MAP_RULES via RULE_ID
    • GCS_LEX_MAP_STRUCTS via LOOKUP_TABLE_ID
    • GCS_LEX_MAP_COLUMNS via LOOKUP_RESULT_COLUMN_ID
    • GCS_LEX_MAP_PLSQL_FUNCS via FUNCTION_NAME
  • Child References (Referenced by): This table is referenced as a parent by:

These relationships form a hierarchical data model where a Rule contains multiple Derivations, each of which can have associated Conditions and Details, and each Derivation sources its logic from either a Lookup Structure/Column or a PL/SQL Function.