Search Results acctg_environment_code

Overview

GL_LEDGER_LE_V is an APPS-owned database view within the Oracle E-Business Suite General Ledger (GL) module. It provides a consolidated, reporting-friendly projection of ledger configuration data joined with legal entity, registration, and location information. The view is particularly relevant to environments that use the Ledger and Subledger Accounting architecture introduced in Release 12, where a primary ledger can be associated with one or more secondary ledgers as well as Accounting Legal Entity configurations. Rather than forcing report authors and integrators to reconstruct the relationship between ledgers, ledger configurations, configuration details, and legal entities, GL_LEDGER_LE_V exposes this data in a single flattened result set.

The view combines ledger attributes (such as ledger name, short name, category code, currency, chart of accounts, period set, and accounting method) with legal entity attributes (object identifier, legal entity name, and registration location details). This makes it suitable for cross-referencing ledgers to their assigned legal entities and for examining ledger relationship structures, including primary, secondary, and ALC ledger categories.

Underlying Base Objects

GL_LEDGER_LE_V is defined over seven documented base objects, all referenced through APPS synonyms:

• GL_LEDGERS — supplies the core ledger attributes (LEDGER_ID, NAME, SHORT_NAME, LEDGER_CATEGORY_CODE, CURRENCY_CODE, CHART_OF_ACCOUNTS_ID, PERIOD_SET_NAME, ACCOUNTED_PERIOD_TYPE, SLA accounting method, and balancing segment options).
• GL_LEDGER_CONFIGURATIONS — provides the configuration identifier and accounting environment code.
• GL_LEDGER_CONFIG_DETAILS — used in two roles: the primary ledger detail (aliased PRIMDET) and the legal entity detail (aliased CFGDET), the latter joined with an outer join.
• GL_LEDGER_RELATIONSHIPS — supplies the primary ledger relationship, target ledger id, target ledger category code, and relationship enabled flag.
• XLE_ENTITY_PROFILES — provides the legal entity identifier and name, joined via an outer join to the legal entity configuration detail.
• XLE_REGISTRATIONS — supplies the identifying registration record for the legal entity, again outer-joined.
• HR_LOCATIONS_ALL_TL — provides the location code and description for the legal entity registration location, outer-joined and filtered by the user's session language.

The joins enforce a specific relationship set: the view restricts results to ledgers whose relationship type and target category satisfy primary, secondary, or ALC conditions, and only where the ledger is marked complete.

Key Columns

• LEDGER_ID, LEDGER_NAME, LEDGER_SHORT_NAME — identity of the target ledger.
• LEGAL_ENTITY_ID, LEGAL_ENTITY_NAME — the legal entity assigned to the ledger configuration.
• LOCATION_ID, LOCATION_CODE, LOCATION_DESCRIPTION — the legal entity's registration location from HR_LOCATIONS_ALL_TL.
• LEDGER_CATEGORY_CODE, CURRENCY_CODE, CHART_OF_ACCOUNTS_ID, PERIOD_SET_NAME, ACCOUNTED_PERIOD_TYPE — standard ledger setup attributes.
• SLA_ACCOUNTING_METHOD_CODE, SLA_ACCOUNTING_METHOD_TYPE — the subledger accounting method.
• BAL_SEG_VALUE_OPTION_CODE, BAL_SEG_COLUMN_NAME, BAL_SEG_VALUE_SET_ID — balancing segment configuration.
• ACCTG_ENVIRONMENT_CODE, CONFIGURATION_ID — configuration context.
• PRIMARY_LEDGER_ID, RELATIONSHIP_ENABLED_FLAG — relationship to the primary ledger.

Common Use Cases and Queries

Typical uses include identifying the legal entity associated with each ledger, reporting on secondary and ALC ledger assignments, and validating multi-ledger configurations prior to period close or consolidation.

Sample query listing ledgers with their legal entities:

• SELECT ledger_id, ledger_name, legal_entity_name, ledger_category_code, currency_code FROM apps.gl_ledger_le_v;

Sample query filtering to secondary ledgers linked to a given primary ledger:

• SELECT ledger_id, ledger_name, primary_ledger_id, legal_entity_name FROM apps.gl_ledger_le_v WHERE ledger_category_code = 'SECONDARY' AND relationship_enabled_flag = 'Y';

Because legal entity and location columns are populated through outer joins, values may be null for ledgers lacking an assigned legal entity or registration.