Results for “legal_construct_id”

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

Overview

XLE_TAX_ASSOCIATIONS is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the XLE – Legal Entity Configurator product. It presents the tax-calculation associations defined between legal constructs (such as establishments represented by XLE_ETB_PROFILES) and the entities they relate to, including inventory organizations, operating units, and HR locations. The view is read-only and its status is VALID in both 12.1.1 and 12.2.2.

The view is a denormalized presentation layer: it joins association metadata (association, object, and subject types) to the underlying entity records so that a single row exposes the association type, the associated entity, the legal construct, the owning legal party, and the effective dating of the relationship. Because the view filters on ASSOC_TYPES.CONTEXT = 'TAX_CALCULATION', it is scoped specifically to tax-calculation associations and should not be used to report other association contexts. This makes it suitable for reporting, data extraction, and integration scenarios where legal-entity tax associations must be reconciled or exported.

Underlying Base Objects

The documented base objects referenced by the view are:

• XLE_ASSOCIATIONS (SYNONYM) – the core association records linking an object to a subject with effective dates.
• XLE_ASSOCIATION_TYPES (SYNONYM) – defines the association type and the object/subject type pairing, including the context.
• XLE_ASSOC_OBJECT_TYPES (SYNONYM) – joined twice (as ASSOC_OBJ and ASSOC_SUBJ) to resolve the object-side entity type and the subject-side legal construct type.
• XLE_ETB_PROFILES (SYNONYM) – the establishment (legal construct) record providing party and name details.
• HR_ALL_ORGANIZATION_UNITS (SYNONYM) – supplies organization names for inventory-organization and operating-unit entities.
• HR_LOCATIONS_ALL (SYNONYM) – supplies the location code used when the associated entity is an HR location (the hr_loc reference matching the user's search).

The view is defined with the classic XLE pattern of joining object types to association types on object_type_id and subject_type_id, then joining association types to associations on association_type_id. The HR organization and HR location joins are both outer joins (HR_LOC.LOCATION_ID(+) = ASSOC.OBJECT_ID and ORG.ORGANIZATION_ID(+) = ASSOC.OBJECT_ID), and the establishment join is an inner join on XEP.ESTABLISHMENT_ID = ASSOC.SUBJECT_ID.

Key Columns

• CONTEXT – association context; restricted to TAX_CALCULATION.
• ENTITY_TYPE and LEGAL_CONSTRUCT – resolved object-type and subject-type names.
• ASSOCIATION_TYPE_ID, ASSOCIATION_ID, ENTITY_ID, LEGAL_CONSTRUCT_ID – primary and foreign key identifiers.
• ENTITY_NAME – a DECODE that returns the organization name for INVENTORY_ORGANIZATION and OPERATING_UNIT entities, otherwise the HR location code.
• LEGAL_PARTY_ID and LEGAL_CONSTRUCT_NAME – party identifier and establishment name.
• LEGAL_PARENT_ID – parent of the legal construct in the establishment hierarchy.
• EFFECTIVE_FROM and EFFECTIVE_TO – validity window of the association.

Common Use Cases and Queries

Typical uses include auditing which establishments are associated with which organizations or HR locations for tax calculation, and extracting currently effective associations.

SELECT legal_construct_name,
       entity_type,
       entity_name,
       effective_from,
       effective_to
FROM   xle_tax_associations
WHERE  TRUNC(SYSDATE) BETWEEN effective_from AND NVL(effective_to, TRUNC(SYSDATE));

To list associations by HR location specifically, filter on the location-derived entity name:

SELECT legal_construct_name, entity_name
FROM   xle_tax_associations
WHERE  entity_type = 'HR_LOCATION';

Because the view already restricts context to TAX_CALCULATION and resolves names, it eliminates the need to re-implement the multi-table joins in custom reports. When querying, avoid joining back to XLE_ASSOCIATIONS unless additional attributes are required, and always apply effective-date predicates to obtain the correct point-in-time association.