Search Results gl_xfr_ccid_mappings




Overview
Explore in AI Chat

Overview

GL_XFR_CCID_MAPPINGS is a General Ledger (GL) table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the account-level translation rules used by the ledger mapping (cross-ledger transfer) feature. Where GL_XFR_LEDGER_MAPPINGS defines which source ledger maps to which target ledger, GL_XFR_CCID_MAPPINGS defines, for each accounting period, the precise conversion of a source account combination into its corresponding target account combination. It is the operational detail table of the ledger mapping framework: without a matching row, a source code combination has no destination account for the given period.

Granularity is one row per ledger mapping, per period, per source account, keyed by LEDGER_MAPPING_ID, PERIOD_NAME, and FROM_CCID. The metadata's heuristic Data Vault classification is link, suggesting the table is best modeled as a relationship object connecting the ledger mapping definition, the source code combination, and the target code combination, with period as a descriptive attribute rather than a hub or satellite.

Key Information Stored

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

  • LEDGER_MAPPING_ID — identifies the parent ledger mapping defined in GL_XFR_LEDGER_MAPPINGS; part of the primary key and the join path to the mapping header.
  • PERIOD_NAME — the accounting period for which the mapping is effective, enabling period-specific account translation. Part of the primary key.
  • FROM_CCID — the source code combination ID (surrogate reference to GL_CODE_COMBINATIONS) being translated. Part of the primary key.
  • TO_CCID — the destination code combination ID that the source account maps to for that period.
  • CREATION_DATE, CREATED_BY — audit stamp recording when and by whom the mapping row was created.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — audit stamp recording the most recent modification and the session that performed it.

The surrogate primary key is GL_XFR_CCID_MAPPINGS_PK (LEDGER_MAPPING_ID, PERIOD_NAME, FROM_CCID). The unique index GL_XFR_CCID_MAPPINGS_U1 (LEDGER_MAPPING_ID, FROM_CCID, PERIOD_NAME) is a business-key candidate covering the same logical attributes, enforcing that a source account maps to at most one target account within a given mapping and period.

Common Use Cases and Queries

Typical usage involves reviewing, auditing, or diagnosing ledger mapping results. A common pattern resolves the source and target accounts to their displayable account strings:

SELECT m.period_name, fcc.concatenated_segments from_account, tcc.concatenated_segments to_account
FROM gl_xfr_ccid_mappings m
JOIN gl_code_combinations_kfv fcc ON fcc.code_combination_id = m.from_ccid
JOIN gl_code_combinations_kfv tcc ON tcc.code_combination_id = m.to_ccid
WHERE m.ledger_mapping_id = :mapping_id
AND m.period_name = :period_name;

  • Mapping validation — confirming that every source account used in a period has a defined TO_CCID before running a translation.
  • Gap analysis — identifying source accounts present in balances but absent from this table for a given mapping and period.
  • Period comparison — detecting accounts whose mapping changed from one period to the next.
  • Audit reporting — using CREATED_BY, CREATION_DATE, and LAST_UPDATE_DATE to track who altered a mapping and when, supporting change-control and compliance review.

Related Objects

The FK metadata documents three reference relationships that anchor this table to its surrounding objects:

  • GL_XFR_LEDGER_MAPPINGS — joined on LEDGER_MAPPING_ID; the header table that defines the source-to-target ledger mapping to which each CCID mapping row belongs.
  • GL_CODE_COMBINATIONS — joined on FROM_CCID; supplies the source account combination attributes.
  • GL_CODE_COMBINATIONS — joined on TO_CCID; supplies the destination account combination attributes. The two FK paths make GL_CODE_COMBINATIONS the most frequently joined object.
  • GL_CODE_COMBINATIONS_KFV (and other key-flex views) — used in reporting to render concatenated segment strings instead of numeric CCIDs.
  • GL_LEDGERS — reached through GL_XFR_LEDGER_MAPPINGS to resolve source and target ledger names for reporting context.

Because translation and revaluation processes consume these mappings, the table is read at period close; rows should be inserted or updated deliberately, as a missing or incorrect mapping directly affects the resulting transferred balances.