Results for “gl_ledg_map”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GL_LEDG_MAP is a table owned by the GMF schema (Process Manufacturing Financials) in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is ledger mapping: it associates a General Ledger ledger with an operating company and organization context so that transactional and costing data originating in Process Manufacturing can be translated to the correct accounting ledger. The table is registered as VALID in ETRM and contains twelve documented columns.

Under the heuristic Data Vault classification mined from its foreign key structure, GL_LEDG_MAP is best modeled as a link table. It resolves several independent business entities — a ledger, an operating company (policy), and an organization — into a single mapping relationship. Its own surrogate primary key (LEDG_MAP_ID) is subordinate to the combination of business keys it joins, which is the hallmark of a link construct rather than a hub or satellite.

Key Information Stored

The table is anchored by the surrogate primary key defined in GL_LEDG_MAP_PK, which consists of the single column LEDG_MAP_ID. This is a system-generated identifier with no business meaning and should not be exposed to end users in reporting.

The business-key candidate is defined by the unique index GL_LEDG_MAP_U1 over CO_CODE and ORGN_CODE. This means a given operating company and organization combination may map to only one ledger at a time — the pair is the natural key for the mapping.

• LEDGER_CODE — the General Ledger ledger to which the company/organization combination is mapped; foreign key to GL_LDGR_MST.
• CO_CODE — the operating company (policy) code; foreign key to GL_PLCY_MST and part of the unique business key.
• ORGN_CODE — the organization code; foreign key to both SY_ORGN_MST and SY_ORGN_MST_B and the second component of the unique business key.
• TRANS_CNT — a transaction/usage counter maintained for the mapping record.
• TEXT_CODE — a short textual qualifier or code attached to the mapping row.
• DELETE_MARK — the standard Oracle soft-delete flag; rows are logically removed rather than physically purged.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard Oracle WHO audit columns recording insert and update attribution.

Common Use Cases and Queries

Typical scenarios include validating that every active operating company and organization combination resolves to a ledger before posting Process Manufacturing transactions, and reporting which ledger a given plant or organization feeds. Because DELETE_MARK governs visibility, queries should filter on it unless historical rows are explicitly required.

• Resolve the ledger for a company/organization pair: SELECT LEDGER_CODE FROM GMF.GL_LEDG_MAP WHERE CO_CODE = :co AND ORGN_CODE = :orgn AND NVL(DELETE_MARK,0) = 0;
• List all mappings for a ledger: SELECT CO_CODE, ORGN_CODE FROM GMF.GL_LEDG_MAP WHERE LEDGER_CODE = :ledger AND NVL(DELETE_MARK,0) = 0;
• Detect orphans by joining to GL_LDGR_MST, GL_PLCY_MST, and SY_ORGN_MST to confirm each foreign key resolves to a valid parent row.
• Audit mappings created or changed in a period using CREATION_DATE and LAST_UPDATE_DATE.

Related Objects

• GL_LDGR_MST — parent ledger master; joined on GL_LEDG_MAP.LEDGER_CODE = GL_LDGR_MST.LEDGER_CODE.
• GL_PLCY_MST — operating company policy master; joined on GL_LEDG_MAP.CO_CODE = GL_PLCY_MST.CO_CODE.
• SY_ORGN_MST — organization master; joined on GL_LEDG_MAP.ORGN_CODE = SY_ORGN_MST.ORGN_CODE.
• SY_ORGN_MST_B — organization master (base/alternate); joined on GL_LEDG_MAP.ORGN_CODE = SY_ORGN_MST_B.ORGN_CODE.

These four parents form the complete documented foreign key footprint of GL_LEDG_MAP and constitute the join path required for any mapping validation or reporting query.