Results for “xle_fp_ou_ledger_v”

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

Overview

XLE_FP_OU_LEDGER_V is an APPS-owned database view in Oracle E-Business Suite Release 12.1.1 and 12.2.2, delivered under the XLE — Legal Entity Configurator product. The view exposes a denormalized, report-ready projection that links operating units to their associated ledgers and the legal entities configured on those ledgers. Its name reflects this purpose: "FP" refers to the Financials/legal-entity profile context, "OU" to operating unit, and "LEDGER" to the General Ledger ledger assignment. In practice, the view answers the recurring question, "For a given operating unit or ledger, which legal entity is assigned, and what are its registration and address attributes?" It is therefore consumed primarily by reporting, diagnostics, and integration logic that must resolve legal-entity context without traversing the raw configuration tables manually.

Underlying Base Objects

The view is defined over eight referenced objects, all exposed as APPS synonyms in the documented metadata: GL_LEDGERS, GL_LEDGER_CONFIGURATIONS, GL_LEDGER_CONFIG_DETAILS, GL_LEDGER_RELATIONSHIPS, HR_LOCATIONS_ALL, HR_ORGANIZATION_INFORMATION, XLE_ENTITY_PROFILES, and XLE_REGISTRATIONS. The driving relationship originates in GL_LEDGER_RELATIONSHIPS, filtered to Application ID 101 (General Ledger), and restricts rows to secondary ledgers with a non-'NONE' relationship, primary ledgers with a 'NONE' relationship, and ALC (accounting ledger configuration) ledgers whose relationship type is 'JOURNAL' or 'SUBLEDGER'. The primary ledger is joined through GL_LEDGER_CONFIGURATIONS and, with an outer join, GL_LEDGER_CONFIG_DETAILS at OBJECT_TYPE_CODE = 'LEGAL_ENTITY'. The legal entity is resolved through XLE_ENTITY_PROFILES, then linked to XLE_REGISTRATIONS on SOURCE_ID where SOURCE_TABLE = 'XLE_ENTITY_PROFILES' and IDENTIFYING_FLAG = 'Y'. Address data is attached via HR_LOCATIONS_ALL, and the operating unit is derived by self-joining HR_ORGANIZATION_INFORMATION on organization ID, matching ORG_INFORMATION3 to the target ledger ID and constraining the context to 'CLASS' and 'OPERATING UNIT'.

Key Columns

• OPERATING_UNIT_ID — Organization ID of the operating unit associated with the target ledger.
• LEDGER_ID, LEDGER_NAME, LEDGER_SHORT_NAME — Identifier and descriptive attributes of the target ledger.
• LEGAL_ENTITY_ID, LEGAL_ENTITY_NAME — The legal entity assigned to the primary ledger configuration.
• LEGAL_ENTITY_IDENTIFIER — The entity's configured unique identifier.
• ACTIVITY_CODE, SUB_ACTIVITY_CODE, TYPE_OF_COMPANY — Classification attributes of the legal entity profile.
• LE_EFFECTIVE_FROM, LE_EFFECTIVE_TO — Validity window of the legal entity record.
• REGISTRATION_NUMBER — Identifying registration number from XLE_REGISTRATIONS.
• ADDRESS_LINE_1/2/3, REGION_1/2/3, TOWN_OR_CITY, POSTAL_CODE, COUNTRY — Registered address attributes sourced from HR_LOCATIONS_ALL.

Common Use Cases and Queries

Typical uses include validating legal-entity assignment by operating unit, reconciling ledger-to-entity mappings before period close, and driving downstream integrations that require entity and registration context. A representative query retrieves entity detail for a specific operating unit:

SELECT operating_unit_id, ledger_name, legal_entity_name, legal_entity_identifier, registration_number FROM apps.xle_fp_ou_ledger_v WHERE operating_unit_id = :p_org_id;

To enumerate all operating units mapped to a ledger:

SELECT operating_unit_id, ledger_id, ledger_short_name FROM apps.xle_fp_ou_ledger_v WHERE ledger_id = :p_ledger_id ORDER BY operating_unit_id;

Because the view joins configuration and HR tables with outer joins in places, consumers should treat results as the currently valid configuration snapshot and apply effective-date logic where historical accuracy is required.