Results for “xle_le_from_registrations”

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

Overview

The APPS.XLE_LE_FROM_REGISTRATIONS view is a reporting and integration construct within the Oracle E-Business Suite Legal Entity Configurator (XLE) module. It resolves the relationship between operating units, ledgers, legal entities, and their statutory registrations, presenting a denormalized result set that joins ledger configuration data, legal entity profiles, registration records, jurisdictions, geographies, and organization classifications. The view is defined as a UNION of two branches: the first derives legal entity context through GL_LEDGER_CONFIGURATIONS and GL_LEDGER_CONFIG_DETAILS, while the second supplements the result set by resolving registrations from the tax registration tables (ZX_REGISTRATIONS and ZX_PARTY_TAX_PROFILE). Its principal role is to answer the question of which legal entity and registration applies to a given operating unit and ledger combination, a requirement common to subledger accounting, tax configuration, and intercompany reporting. The name reflects its purpose: it maps a legal entity *from* registration records back to the operating unit and ledger that consume them. Users who search for gl_ledger_configurations typically arrive here because that table is the pivot that links a primary ledger to its assigned legal entity, and this view exposes that linkage in a queryable form.

Underlying Base Objects

The view is built over a documented set of base objects, most of which are referenced through APPS synonyms. The ledger side draws on GL_LEDGERS, GL_LEDGER_RELATIONSHIPS, GL_LEDGER_CONFIGURATIONS, and GL_LEDGER_CONFIG_DETAILS. The legal entity and registration side draws on XLE_ENTITY_PROFILES, XLE_REGISTRATIONS, XLE_JURISDICTIONS_B, XLE_ETB_PROFILES, and the tax tables ZX_REGISTRATIONS, ZX_REGIMES_B, and ZX_PARTY_TAX_PROFILE. Supporting lookups and geography come from AR_LOOKUPS and HZ_GEOGRAPHIES, while operating unit identification is resolved through HR_ORGANIZATION_INFORMATION, which supplies both the CLASS and OPERATING UNIT INFORMATION contexts. The join logic anchors on GL_LEDGER_RELATIONSHIPS with APPLICATION_ID = 101 and a PRIMARY ledger category, then connects the primary ledger's CONFIGURATION_ID to GL_LEDGER_CONFIG_DETAILS filtered to OBJECT_TYPE_CODE = 'LEGAL_ENTITY'. This is precisely the configuration path that makes GL_LEDGER_CONFIGURATIONS central to the view.

Key Columns

• OPERATING_UNIT_ID — the organization identifier of the operating unit derived from HR_ORGANIZATION_INFORMATION.
• LEDGER_ID — the target ledger associated with the registration context.
• LEGAL_ENTITY_ID / LEGAL_ENTITY_NAME — the legal entity resolved through the ledger configuration detail or the establishment profile.
• REGISTRATION_ID / REGISTRATION_NUMBER — the statutory registration record and its government-issued number.
• LEGISLATIVE_CATEGORY_CODE / LEGISLATIVE_CATEGORY_MEANING — the legislative category of the jurisdiction, decoded from AR_LOOKUPS.
• COUNTRY_OF_REGISTRATION — the geography code of the registering jurisdiction.
• EFFECTIVE_FROM / EFFECTIVE_TO — the validity window of the registration.
• TRANSACTION_TAX_REGN_CONTEXT — a placeholder column returned as NULL in the first branch, reserved for tax registration context resolution.

Common Use Cases and Queries

Typical usage includes identifying the legal entity and registration applicable to an operating unit for a given ledger, validating that ledger configurations point to the correct legal entity, and driving tax or statutory reporting extracts. A representative query follows.

• List registrations by operating unit:

SELECT operating_unit_id, ledger_id, legal_entity_name, registration_number, legislative_category_code, country_of_registration FROM apps.xle_le_from_registrations WHERE operating_unit_id = :p_org_id AND SYSDATE BETWEEN effective_from AND NVL(effective_to, SYSDATE);

• Confirm legal entity assignment for a ledger:

SELECT DISTINCT ledger_id, legal_entity_id, legal_entity_name FROM apps.xle_le_from_registrations WHERE ledger_id = :p_ledger_id;

Because the view joins multiple configuration and tax tables, queries should be filtered by operating unit or ledger to avoid full scans, and effective date ranges should be applied to return only currently valid registrations.