Search Results xle_legalauth_v




Overview
Explore in AI Chat

Overview

XLE_LEGALAUTH_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite Legal Entity Configurator (XLE) product. It exposes a consolidated, query-friendly projection of legal authorities: organizations that have been designated as recognized legal or regulatory bodies (for example, a securities commission, registrar of companies, or tax authority) within Oracle's Trading Community Architecture (TCA) model and are subsequently used by Legal Entity Configurator when registering legal entities and their jurisdictional registrations. The view does not store data; it derives its results at runtime by joining TCA party, party site, location, organization profile, and code assignment records.

Because the search term associated with this object is "hz_code_assignments", the principal purpose of this view for integrators and report developers is to resolve the classification mechanism used by TCA. Legal authority status in TCA is not a dedicated column or entity. Instead it is expressed as a row in HZ_CODE_ASSIGNMENTS with CLASS_CATEGORY = 'BUSINESS_FUNCTION' and CLASS_CODE = 'LEGAL_AUTHORITY'. XLE_LEGALAUTH_V encapsulates that logic, so a developer can query legal authorities without reconstructing the classification join manually or risking an incorrect predicate. In EBS 12.1.1 and 12.2.2 the object remains a standard, valid APPS view.

Underlying Base Objects

Per the documented ETRM metadata, XLE_LEGALAUTH_V is defined over five synonyms, each resolving to a TCA base table:

  • HZ_CODE_ASSIGNMENTS — referenced twice, once (HCA) to identify the BUSINESS_FUNCTION classification of LEGAL_AUTHORITY, and once (HCA2) as an outer-joined source of the LEGISLATIVE_CATEGORY classification.
  • HZ_PARTIES — supplies the party identifier and restricts results to PARTY_TYPE = 'ORGANIZATION'.
  • HZ_ORGANIZATION_PROFILES — provides the organization name, surfaced as the authority name.
  • HZ_PARTY_SITES — supplies the active party site (STATUS = 'A') linked to the party.
  • HZ_LOCATIONS — supplies the formatted address of the party site.

The join path is party-driven: HP.PARTY_ID links to the code assignment owner record, the organization profile, and the party site, which in turn links to the location. The legislative category assignment is joined with the Oracle outer-join operator (+) to HP.PARTY_ID, making that classification optional.

Key Columns

  • LEGALAUTH_ID — the HZ_PARTIES.PARTY_ID of the legal authority organization; the primary identifier exposed by the view.
  • AUTHORITY_NAME — the organization name from HZ_ORGANIZATION_PROFILES.
  • PARTY_ID — the same underlying party identifier, exposed under its native name for joining to other TCA objects.
  • PARTY_SITE_ID — the active party site identifier for the authority.
  • ADDRESS_STYLE, ADDRESS1–ADDRESS4, CITY, STATE, POSTAL_CODE, COUNTRY — address attributes from HZ_LOCATIONS.
  • LEGISLATIVE_CATEGORY_CODE — the CLASS_CODE of the optional LEGISLATIVE_CATEGORY code assignment, indicating the type of legislative body where recorded.

Common Use Cases and Queries

Typical uses include populating legal authority lists of values in custom pages, validating registrations in legal entity interfaces, and producing jurisdiction reports. A simple lookup follows:

  • SELECT legalauth_id, authority_name, city, country FROM xle_legalauth_v ORDER BY authority_name;
  • SELECT legalauth_id, authority_name, legislative_category_code FROM xle_legalauth_v WHERE country = 'US';
  • SELECT v.authority_name, v.legalauth_id FROM xle_legalauth_v v WHERE v.legalauth_id = :p_party_id;

Because the view resolves the HZ_CODE_ASSIGNMENTS classification, it should be preferred over ad hoc joins when filtering for legal authorities in TCA. Note that the outer join on LEGISLATIVE_CATEGORY can return null values, so application logic should treat that column as optional.