Results for “ledger_code”

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

Overview

GL_LDGR_MST is a Process Manufacturing Financials (GMF) master table that stores General Ledger ledger definitions used by Oracle EBS Process Manufacturing applications. It resides in the GMF schema and is documented as VALID under ETRM 12.2.2, with an equivalent footprint in 12.1.1 deployments. The table functions as the master reference for ledgers that Process Manufacturing subledger and costing components consume, particularly for distribution accounting, policy assignment, and subledger-level posting configuration.

The table is owned by GMF and contains ten documented columns. Its primary key is GL_LDGR_MST_PK, defined on the LEDGER_CODE column. From a Data Vault modeling perspective, the mined FK structure suggests a hub-leaning classification: GL_LDGR_MST behaves as a business-key hub, holding the durable identity of each ledger (LEDGER_CODE) with descriptive attributes attached. Downstream tables reference this hub through their own LEDGER_CODE or PRIMARY_LEDGER_CODE foreign keys, which is characteristic of a hub with multiple dependent links and satellites rather than a transactional link table itself.

Key Information Stored

The most significant columns in GL_LDGR_MST are:

• LEDGER_CODE — The business key and sole column of the primary key GL_LDGR_MST_PK. It uniquely identifies each ledger record and is the column referenced by every documented foreign key from dependent tables.
• LEDGER_DESC — The descriptive name or short text associated with the ledger, used for display and reporting.
• TEXT_CODE — A code column typically used for additional classification or lookup-driven text association.
• TRANS_CNT — A transaction counter, commonly used in GMF master tables for concurrency control, sequencing, or tracking of transactional activity against the record.
• DELETE_MARK — The standard Oracle EBS logical delete flag; rows with this indicator set are treated as inactive without physical deletion.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — The standard WHO columns capturing audit and user context for insert and update activity.

No surrogate sequence-based identifier is documented beyond LEDGER_CODE; the primary key is therefore a natural or business key rather than a generated surrogate. GL_LDGR_MST_PK is the only documented unique index and is the business-key candidate for this table.

Common Use Cases and Queries

Typical use cases include validating ledger setup before Process Manufacturing costing or distribution transactions are posted, resolving ledger codes to descriptions in reporting, and joining ledger master data to policy, mapping, and subledger configuration tables. A representative lookup follows:

• SELECT LEDGER_CODE, LEDGER_DESC FROM GMF.GL_LDGR_MST WHERE DELETE_MARK = 0;
• SELECT m.LEDGER_CODE, m.LEDGER_DESC, p.PRIMARY_LEDGER_CODE FROM GMF.GL_LDGR_MST m, GMF.GL_PLCY_MST p WHERE m.LEDGER_CODE = p.PRIMARY_LEDGER_CODE;
• SELECT d.LEDGER_CODE, COUNT(*) FROM GMF.PO_DIST_DTL d GROUP BY d.LEDGER_CODE; — to review distribution activity by ledger.

Reporting extracts frequently denormalize LEDGER_DESC onto transaction-level reports, and reconciliation scripts compare GL_LDGR_MST entries against GL_LEDG_MAP and GL_SUBR_LED to detect orphaned or unmapped ledger references.

Related Objects

Six documented foreign keys reference GL_LDGR_MST, establishing it as a referenced parent object:

• GL_LEDG_MAP.LEDGER_CODE — Ledger mapping records linking GMF ledgers to GL ledger configuration.
• GL_PLCY_LGR.LEDGER_CODE — Ledger-level accounting policy associations.
• GL_PLCY_MST.PRIMARY_LEDGER_CODE — The master policy table's primary ledger assignment.
• GL_SUBR_LED.LEDGER_CODE — Subledger-to-ledger assignment records.
• GL_SUBR_TST.LEDGER_CODE — Subledger test configuration referencing ledgers.
• PO_DIST_DTL.LEDGER_CODE — Purchase order distribution detail lines carrying ledger references.

These relationships confirm that GL_LDGR_MST sits upstream of policy, mapping, subledger, and purchasing distribution data, making it a foundational hub for Process Manufacturing financial integration with Oracle General Ledger.