Search Results gl_coa_mappings_u1

Overview

GL.GL_COA_MAPPINGS is a General Ledger reference table that stores chart of accounts mappings defined through the Chart of Accounts Mappings form in Oracle E-Business Suite. A chart of accounts mapping defines a reusable relationship between a source ("from") chart of accounts and a target ("to") chart of accounts, allowing account balances and journal detail to be translated between different key flexfield structures. This capability is central to consolidation processing, where a parent operating unit must translate the balances of subsidiary ledgers that use divergent chart of accounts structures into a single reporting chart of accounts.

The table resides in the GL schema, is registered under FND Design Data as SQLGL.GL_COA_MAPPINGS, and its data segment is stored in the APPS_TS_TX_DATA tablespace. Each row holds the mapping name, its source and target chart of accounts identifiers, descriptive text, and effective dating attributes. A single mapping row fans out into detailed mapping rules held in GL_CONS_FLEXFIELD_MAP and GL_CONS_SEGMENT_MAP, establishing a one-to-many relationship between the mapping header and its segment-level translation rules.

From a Data Vault modeling perspective, the mined metadata classifies this object as standalone. In practice it behaves as a hub-like reference entity: GL_COA_MAPPINGS_PK on COA_MAPPING_ID provides the durable surrogate key, while the descriptive and effective-dating columns (NAME, DESCRIPTION, START_DATE_ACTIVE, END_DATE_ACTIVE, SECURITY_FLAG) function as satellite-style attributes that could be separated in a formal Data Vault design.

Key Information Stored

The table contains thirteen documented columns. The most significant are:

• COA_MAPPING_ID — NUMBER(15); the surrogate primary key (GL_COA_MAPPINGS_PK) and the defining column for the mapping. Also the target of all foreign keys pointing into this table.
• FROM_COA_ID — NUMBER(15); the source key flexfield structure defining column, identifying the chart of accounts being mapped from.
• TO_COA_ID — NUMBER(15); the target key flexfield structure defining column, identifying the chart of accounts being mapped to.
• NAME — VARCHAR2(33); the chart of accounts mapping name. Enforced by the unique index GL_COA_MAPPINGS_U2, making it the principal business-key candidate.
• SECURITY_FLAG — indicates whether definition access set security applies to the mapping.
• DESCRIPTION — VARCHAR2(240); free-text description of the mapping's purpose.
• START_DATE_ACTIVE and END_DATE_ACTIVE — effective dating bounds that determine the period during which the mapping is considered active.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — standard WHO audit columns recording creation and last-modification context.

Two unique indexes are documented: GL_COA_MAPPINGS_U1 enforces uniqueness on COA_MAPPING_ID, and GL_COA_MAPPINGS_U2 enforces uniqueness on NAME. Both reside in the APPS_TS_TX_IDX tablespace.

Common Use Cases and Queries

Typical usage centers on identifying which mappings exist between specific chart of accounts structures, validating effective-dated mappings before running consolidation, and reporting the mapping rules attached to each header. Column projection against the documented query text is straightforward:

• Listing all active mappings: SELECT COA_MAPPING_ID, NAME, FROM_COA_ID, TO_COA_ID FROM GL.GL_COA_MAPPINGS WHERE SYSDATE BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE);
• Resolving a mapping by business key using the U2 index: SELECT * FROM GL.GL_COA_MAPPINGS WHERE NAME = :mapping_name;
• Finding mappings between two structures: SELECT COA_MAPPING_ID, NAME FROM GL.GL_COA_MAPPINGS WHERE FROM_COA_ID = :from_id AND TO_COA_ID = :to_id;
• Joining header to detail rules for audit reporting: SELECT m.NAME, f.* FROM GL.GL_COA_MAPPINGS m, GL.GL_CONS_FLEXFIELD_MAP f WHERE m.COA_MAPPING_ID = f.COA_MAPPING_ID;

These patterns support consolidation setup verification, migration validation between environments, and reconciliation of chart of accounts translation logic across ledgers.

Related Objects

The following objects reference or depend on GL_COA_MAPPINGS through the documented foreign keys:

• GL.GL_CONS_FLEXFIELD_MAP — references COA_MAPPING_ID; holds the flexfield-level mapping detail for each header row.
• GL.GL_CONS_SEGMENT_MAP — references COA_MAPPING_ID; stores segment-level (value-level) translation rules belonging to a mapping.
• GL.GL_CONSOLIDATION — references COA_MAPPING_ID; the consolidation definition that consumes the mapping when translating subsidiary balances.

Together these objects form the consolidation mapping hierarchy: the header row in GL_COA_MAPPINGS governs effective dating and security, while GL_CONS_FLEXFIELD_MAP and GL_CONS_SEGMENT_MAP supply the structural detail that GL_CONSOLIDATION applies during balance translation.