Search Results xle_le_info_dev

Overview

APPS.XLE_FIRSTPARTY_INFORMATION_V is a reporting view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that exposes consolidated "first party" legal entity information for the Legal Entity Configurator (XLE) module. It presents a denormalized, query-friendly projection of legal entity profiles joined to their registration details, jurisdictions, and primary address information — including descriptive flexfield (DFF) attribute columns — so that downstream reports, integrations, and extracts do not need to replicate the multi-table join logic themselves.

The view is of particular interest to developers working with the XLE_LE_INFO_DEV descriptive flexfield, because the view's Activity_Category and Activity_description columns are derived dynamically from the DFF context defined under descriptive flexfield name XLE_LE_INFO_DEV for application_id 204 (Legal Entity Configurator). In effect, the view surfaces the flexfield value set and its associated lookup meaning alongside the entity record.

Underlying Base Objects

The view is defined over the following documented base objects:

• XLE_ENTITY_PROFILES (synonym) — the primary driver table (aliased lep), supplying legal entity identity, context, party, activity, and DFF attribute columns.
• XLE_REGISTRATIONS (synonym) — aliased reg, supplying registration number, effective dates, and location.
• XLE_JURISDICTIONS_B (synonym) — aliased jur, supplying the legislative category code.
• HR_LOCATIONS_ALL (synonym) — aliased hrl, supplying the formatted address (style, address lines, city, region, postal code, country).
• FND_DESCR_FLEX_COLUMN_USAGES (synonym) and FND_FLEX_VALUE_SETS (synonym) — used in scalar subqueries to resolve the value set name associated with the ACTIVITY_CODE segment of the XLE_LE_INFO_DEV flexfield context.
• AR_LOOKUPS (view) — used to resolve lookup meanings for the activity code against the resolved value set name.

The joins link each legal entity to its registrations and jurisdictions, then to the address held against the registration's location, producing one row per registration context.

Key Columns

• legal_entity_id, party_id, legal_entity_identifier — core entity identifiers.
• le_information_context — the DFF context code that drives the Activity_Category and Activity_description subqueries.
• activity_code, sub_activity_code, type_of_company — classification of the legal entity's business activity.
• Activity_Category — the flex value set name resolved from FND_DESCR_FLEX_COLUMN_USAGES for the ACTIVITY_CODE column.
• Activity_description — the AR_LOOKUPS meaning for the activity code within that value set.
• le_effective_from / le_effective_to — legal entity effectivity dates.
• ATTRIBUTE1 … ATTRIBUTE20, ATTRIBUTE_CATEGORY — the entity profile's DFF attribute values.
• registration_number, legislative_cat_code, effective_from, effective_to, location_id — registration and jurisdiction detail.
• ADDRESS_STYLE, address_line_1..3, town_or_city, region_1..3, postal_code, country — primary address of the registration location.

Common Use Cases and Queries

The view is typically used for legal entity reporting, first-party master data extracts, and validating DFF configuration for the XLE_LE_INFO_DEV flexfield. A representative query:

• SELECT legal_entity_id, name, activity_code, Activity_Category, Activity_description, registration_number, legislative_cat_code, town_or_city, country FROM APPS.XLE_FIRSTPARTY_INFORMATION_V WHERE le_information_context = :p_context ORDER BY name;

To diagnose flexfield resolution for a given context:

• SELECT DISTINCT le_information_context, Activity_Category FROM APPS.XLE_FIRSTPARTY_INFORMATION_V WHERE Activity_Category IS NOT NULL;

Because Activity_Category and Activity_description are resolved via correlated subqueries against FND_DESCR_FLEX_COLUMN_USAGES and AR_LOOKUPS, queries filtering on those columns may perform slowly; restricting by legal_entity_id or le_information_context first is recommended.