Search Results xle_firstparty_information_v




Overview
Explore in AI Chat

Overview

The XLE_FIRSTPARTY_INFORMATION_V view is a reporting and integration object owned by the APPS schema within the Oracle E-Business Suite Legal Entity Configurator (XLE) module. It consolidates first-party (legal entity) identification, registration, and address information into a single denormalized structure for a given legal entity and its information context. In ETRM releases 12.1.1 and 12.2.2, this view presents registered legal entity details without requiring consumers to join multiple XLE and HR tables directly.

The view derives its data primarily from the legal entity profile records, enriched with descriptive flexfield lookups and registration data. It exposes both the raw flexfield context (LE_INFORMATION_CONTEXT) and resolved descriptive values such as ACTIVITY_CATEGORY and ACTIVITY_DESCRIPTION, which are computed via correlated subqueries against FND_DESCR_FLEX_COLUMN_USAGES, FND_FLEX_VALUE_SETS, and AR_LOOKUPS.

Underlying Base Objects

The documented base objects referenced by this view are:

  • XLE_ENTITY_PROFILES (SYNONYM) — the primary source of legal entity profile data (LEGAL_ENTITY_ID, NAME, PARTY_ID, ACTIVITY_CODE, EFFECTIVE dates, and DFF attributes).
  • XLE_REGISTRATIONS (SYNONYM) — supplies registration number, registration effective dates, and location linkage.
  • XLE_JURISDICTIONS_B (SYNONYM) — provides legislative category codes for the associated jurisdiction.
  • HR_LOCATIONS_ALL (SYNONYM) — delivers address information and address style (ADDRESS_LINE_1 through _3, TOWN_OR_CITY, REGION_1 through _3, and related fields).
  • FND_DESCR_FLEX_COLUMN_USAGES (SYNONYM) and FND_FLEX_VALUE_SETS (SYNONYM) — resolve the value set name for the ACTIVITY_CODE flexfield segment within the XLE_LE_INFO_DEV descriptive flexfield.
  • AR_LOOKUPS (VIEW) — maps the ACTIVITY_CODE lookup code to its meaning for the resolved value set.

The view is therefore a composite of legal entity, registration, jurisdiction, address, and flexfield-metadata sources joined by legal entity and context.

Key Columns

  • LEGAL_ENTITY_ID — unique identifier of the legal entity.
  • LE_INFORMATION_CONTEXT — the descriptive flexfield context code defining the legal entity information segment.
  • NAME, PARTY_ID, LEGAL_ENTITY_IDENTIFIER — entity name, associated trading partner party, and the legal entity identifier.
  • ACTIVITY_CODE / ACTIVITY_CATEGORY / ACTIVITY_DESCRIPTION — the activity code, its resolved value set name, and its human-readable meaning.
  • TYPE_OF_COMPANY, SUB_ACTIVITY_CODE — classification attributes of the entity.
  • LE_EFFECTIVE_FROM / LE_EFFECTIVE_TO — the effective date range of the legal entity profile record.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — descriptive flexfield attribute columns for entity-level extensions.
  • REGISTRATION_NUMBER, LEGISLATIVE_CAT_CODE, and registration EFFECTIVE_FROM/EFFECTIVE_TO — registration identity and jurisdiction classification.
  • LOCATION_ID, ADDRESS_STYLE, ADDRESS_LINE_1..3, TOWN_OR_CITY, REGION_1..3 — the registered address details.

Common Use Cases and Queries

This view is commonly used for legal entity reporting, registration compliance extracts, and integrations requiring a flat first-party record. A typical query selects entities by activity or jurisdiction:

  • Listing all legal entities with their activity description and registration number.
  • Extracting address and jurisdiction information for statutory filing or treasury integrations.
  • Filtering by LE_INFORMATION_CONTEXT to isolate entities provisioned under a specific flexfield context.
  • Driving downstream reconciliation between XLE entity setup and third-party interfaces.

Sample SQL:

SELECT legal_entity_id, name, activity_category, activity_description, registration_number, legislative_cat_code, town_or_city
FROM apps.xle_firstparty_information_v
WHERE le_information_context = :p_context
ORDER BY name;

Because the view resolves value set names and lookup meanings at runtime, it is best used for read-only reporting rather than high-volume transactional processing.