Results for “primary_ledger_code”

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

Overview

The GMF_LEGAL_ENTITIES view in the APPS schema is a reporting construct in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, delivered as part of the Process Manufacturing Financials (GMF) product family. Its purpose is to present a simplified, denormalized picture of each legal entity defined in the E-Business Tax and Ledger architecture, joined to its assigned primary ledger. The view is designated as an internal view, meaning Oracle does not formally document it as a public interface; nevertheless it is widely referenced in GMF-related reporting, extensions, and integration routines where downstream logic needs a single-row representation combining legal entity identity with primary ledger attributes.

The view is significant because EBS stores legal entity definitions and ledger assignments across several normalized tables, requiring a multi-way join to resolve the primary ledger associated with a given legal entity. GMF_LEGAL_ENTITIES encapsulates that join, exposing the legal entity identifier and name alongside the primary ledger identifier, name, short name, functional (base) currency, and chart of accounts identifier. This consolidation makes it convenient for reporting layers, concurrent programs, and custom extensions in Process Manufacturing to retrieve the ledger context of a legal entity without re-creating the underlying configuration joins.

Underlying Base Objects

The view is defined over three synonym-referenced base objects:

• XLE_ENTITY_PROFILES (alias LE) — the legal entity registry, supplying LEGAL_ENTITY_ID and NAME.
• GL_LEDGERS (alias LG) — the ledger definition table, supplying ledger identifier, name, short name, currency, chart of accounts, configuration identifier, completion flag, and ledger category.
• GL_LEDGER_CONFIG_DETAILS (alias CFGDET) — the ledger configuration detail table, which maps configuration identifiers to specific objects such as legal entities. This table provides the linkage between a ledger and its owning legal entity.

The join logic relies on CFGDET.CONFIGURATION_ID = LG.CONFIGURATION_ID, with outer-join predicates (OBJECT_TYPE_CODE(+) = 'LEGAL_ENTITY' and OBJECT_ID(+) = LE.LEGAL_ENTITY_ID) mapping the legal entity to the ledger configuration. The view restricts rows to ledgers where NVL(LG.COMPLETE_FLAG,'Y') = 'Y' and LG.LEDGER_CATEGORY_CODE = 'PRIMARY', ensuring only complete primary ledgers are returned.

Key Columns

• LEGAL_ENTITY_ID — primary identifier of the legal entity from XLE_ENTITY_PROFILES.
• LEGAL_ENTITY_NAME — descriptive name of the legal entity.
• PRIMARY_LEDGER_ID — ledger identifier of the entity's primary ledger (LG.LEDGER_ID).
• PRIMARY_LEDGER_NAME — descriptive name of the primary ledger.
• PRIMARY_LEDGER_CODE — short name of the primary ledger (LG.SHORT_NAME); this is the column most commonly referenced by users searching for the ledger short code, often described informally as primary_ledger_code.
• BASE_CURRENCY_CODE — functional currency of the primary ledger.
• CHART_OF_ACCOUNTS_ID — chart of accounts assigned to the primary ledger.

Common Use Cases and Queries

Typical usages include resolving the primary ledger for a legal entity during GMF accounting or reporting, driving multi-org-aware extracts, and validating ledger assignments in configuration audits. A representative query retrieving the primary ledger code for a legal entity is shown below.

• SELECT legal_entity_id, legal_entity_name, primary_ledger_id, primary_ledger_code, base_currency_code FROM apps.gmf_legal_entities WHERE legal_entity_id = :p_legal_entity_id;
• SELECT legal_entity_name, primary_ledger_code FROM apps.gmf_legal_entities ORDER BY legal_entity_name;
• SELECT primary_ledger_id, chart_of_accounts_id FROM apps.gmf_legal_entities WHERE primary_ledger_code = :p_ledger_code;

Because the object is an internal view, consumers should treat its column set and definition as potentially subject to change across releases and validate compatibility before embedding it in production customizations in either 12.1.1 or 12.2.2.