Results for “set_ledger”

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

Overview

GL_MC_INFO is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema. It is a multi-currency (MC) and multiple reporting currency (MRC) information utility package used by the General Ledger application. Its core business function is to resolve and expose metadata about ledgers, secondary ledgers, reporting sets of books, and their associated legal entities and balancing segment values, so that other General Ledger processes can translate or report accounting data across currencies and ledger relationships.

The package abstracts the complexity of determining the relationship between a primary ledger (or primary set of books) and its associated secondary or reporting ledgers. In Release 12, this logic is centralized through ledger relationship configuration, and GL_MC_INFO provides the query layer that returns the correct ledger identifiers, currencies, and legal entity context. It is a read-oriented utility package rather than a transactional API. Its status is VALID, and the documented API classification is OTHER, indicating it is not a public, customer-facing API but an internal General Ledger dependency.

Key Procedures and Functions

The package exposes 39 documented procedures and functions, of which the following are representative:

• GET_LEDGER_CURRENCY — Returns the currency associated with a given ledger, used to determine the functional currency for translation and reporting.
• GET_ALC_LEDGER_TYPE, GET_ALC_LEDGER_ID, GET_ALC_ASSOCIATED_LEDGERS — Resolve Accounting Local Currency (ALC) ledger information and the ledgers associated with an ALC configuration.
• GET_SOB_TYPE, GET_LEDGER_CATEGORY — Return the set of books type and ledger category, distinguishing primary, secondary, and reporting ledgers.
• GET_SOURCE_LEDGER_ID, GET_PRIMARY_SET_OF_BOOKS_ID, GET_PRIMARY_LEDGER_ID, GET_REPORTING_SET_OF_BOOKS_ID — Identify the originating or primary ledger from a related ledger context.
• INIT_LEDGER_LE_BSV_GT — Populates the global temporary structures that hold ledger, legal entity, and balancing segment value associations for the session.
• GET_LE_LEDGERS, GET_LEGAL_ENTITIES, GET_BAL_SEG_VALUES — Return the ledgers, legal entities, and balancing segment values configured for a ledger relationship.
• SET_LEDGER, SET_ORG_ID, SET_RSOB — Establish the current ledger, operating unit, and reporting set of books context for subsequent queries.
• MRC_INSTALLED, ALC_ENABLED, MRC_ENABLED — Installation and feature-enablement flags indicating whether MRC or ALC functionality is active.

Tables Accessed

GL_MC_INFO reads configuration and reference data rather than posting accounting entries. It accesses GL_LEDGERS, GL_LEDGER_RELATIONSHIPS, GL_LEDGER_CONFIG_DETAILS, GL_LEDGER_LE_V, GL_LEDGER_LE_BSV_GT, GL_LEDGER_BSV_GT, GL_LEDGER_NORM_SEG_VALS, GL_LEDGER_RSHIPS_V, GL_SECONDARY_LEDGER_RSHIPS_V, and GL_ALC_LEDGER_RSHIPS_V to resolve ledger hierarchies, relationships, and balancing segment assignments. FND_CURRENCIES supplies currency definitions. XLE_ENTITY_PROFILES provides legal entity information. FND_FLEX_VALUE_SETS, FND_FLEX_VALUES_VL, and FND_FLEX_VALIDATION_TABLES supply key flexfield value and validation metadata. FA_MC_BOOK_CONTROLS supports the multi-currency relationship to Assets books. FND_PRODUCT_GROUPS and FND_MESSAGE provide installation and message lookup support. DBMS_APPLICATION_INFO, DBMS_SQL, DUAL, PLITBLM, DBMS_STANDARD, and STANDARD are used for session context, dynamic SQL, and standard PL/SQL runtime support.

Usage Notes

GL_MC_INFO is invoked internally by General Ledger forms, concurrent programs, and other packages that must determine ledger relationships during multi-currency processing. It is referenced by 31 other packages, and it is not referenced by any database object directly, confirming its role as a supporting utility rather than a database-triggered or view-bound object. Typical invocations occur when a General Ledger form needs to display or validate reporting ledger data, or when a concurrent program must resolve the correct secondary ledger for translation and reporting. Because it exposes session context routines such as SET_LEDGER, SET_ORG_ID, and SET_RSOB, callers generally establish context before querying. Custom code should use it with caution, as it is an internal package and its behavior is tied to the configuration of ledger relationships, ALC, and MRC.