Search Results gl_coa_mappings_pk

Overview

GL_COA_MAPPINGS is a General Ledger table in the Oracle E-Business Suite (documented here for 12.1.1 and 12.2.2) that stores chart of accounts mapping definitions. A chart of accounts mapping defines a translation rule between two charts of accounts: a source (From) chart of accounts and a target (To) chart of accounts. These definitions are the foundation for consolidation, where subsidiary ledger balances expressed in one chart of accounts must be re-expressed against the parent chart of accounts before they can be combined, translated, and reported.

Each row in GL_COA_MAPPINGS is a header-level definition. The segment-level rules that actually determine how a source segment value translates into a target segment value are not held here; they are held in the child segment mapping tables that point back to this table through COA_MAPPING_ID. The mapping header therefore acts as the identity and lifecycle anchor for the entire mapping rule set, carrying the from/to chart assignments, the mapping name, and effective dating.

The supplied ETRM metadata classifies this object heuristically as standalone, with no inbound or outbound foreign keys at the header level other than the references from child tables. Under a Data Vault modeling suggestion this would be treated as a hub-like reference entity: a durable, uniquely identified business object (the mapping definition) to which descriptive attributes (name, description, security flag, effective dates) attach as satellite-like context. It is not a transactional link, since it does not itself record an accounting event.

Key Information Stored

The documented physical schema for 12.2.2 contains 13 columns. The most significant are:

• COA_MAPPING_ID — the surrogate primary key, enforced by the unique index GL_COA_MAPPINGS_PK. It is the value propagated into every child table.
• NAME — the user-facing mapping name. This is a business-key candidate, enforced by the unique index GL_COA_MAPPINGS_U1 (COA_MAPPING_ID) and GL_COA_MAPPINGS_U2 (NAME). Note the metadata lists COA_MAPPING_ID under both the PK and U1; in practice NAME is the meaningful alternate key.
• FROM_COA_ID — identifies the source chart of accounts being mapped from.
• TO_COA_ID — identifies the target chart of accounts being mapped to. Together, FROM_COA_ID and TO_COA_ID define the direction and scope of the mapping.
• DESCRIPTION — free-text explanation of the mapping's purpose.
• SECURITY_FLAG — controls whether the mapping definition is treated as secured for access purposes.
• START_DATE_ACTIVE and END_DATE_ACTIVE — the effective dating window for the mapping, enabling multiple mappings between the same pair of charts to exist across different periods without collision.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS audit columns recording who created and last changed the row and when.

Common Use Cases and Queries

The primary reporting use case is identifying which mapping to run for a given consolidation. A typical pattern joins the mapping header to the consolidation definition to confirm the mapping assigned to a parent:

• List active mappings: SELECT coa_mapping_id, name, from_coa_id, to_coa_id FROM gl_coa_mappings WHERE SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);
• Resolve the mapping in use by a consolidation: join GL_CONSOLIDATION.COA_MAPPING_ID to GL_COA_MAPPINGS.COA_MAPPING_ID.
• Audit changes to mapping definitions using LAST_UPDATED_BY / LAST_UPDATE_DATE to support period-close controls.
• Validate completeness by checking that every mapping header has child rows in GL_CONS_SEGMENT_MAP; a header with no segment rules indicates an incomplete mapping.

Related Objects

The following documented objects depend on GL_COA_MAPPINGS through COA_MAPPING_ID:

• GL_CONS_SEGMENT_MAP — references GL_COA_MAPPINGS.COA_MAPPING_ID; holds the segment-value-level translation rules.
• GL_CONS_FLEXFIELD_MAP — references GL_COA_MAPPINGS.COA_MAPPING_ID; holds key flexfield mapping rules.
• GL_CONSOLIDATION — references GL_COA_MAPPINGS.COA_MAPPING_ID; the consolidation definition that consumes the mapping.

These three child tables, joined on COA_MAPPING_ID, form the complete mapping construct. Mapping definitions are typically created and maintained through the Oracle General Ledger Consolidation responsibility rather than by direct DML, since the mapping must remain internally consistent across the header and its child segment and flexfield rules.