Search Results hz_party_usg_assignments




Overview

The HZ_PARTY_USG_ASSIGNMENTS table is a core component of the Oracle E-Business Suite Trading Community Architecture (TCA) and is owned by the AR (Receivables) schema. It stores the association between a party record and one or more party usages, effectively defining the functional roles that a given party plays within the enterprise. Party usages distinguish whether a party functions as a customer, supplier, employee, or other business role, and this table records those associations together with their validity periods and status. Without usage assignments, a party record exists in the registry but is not enabled for any specific business function.

In Oracle EBS 12.1.1 and 12.2.2, the table carries a status of VALID and comprises 42 documented columns. Based on FK structure, the heuristic Data Vault classification for this object is a link, since it resolves a many-to-many relationship between parties and party usages. From a dimensional modeling perspective, it is best treated as an associative entity rather than a hub or satellite.

Key Information Stored

The table is anchored by a surrogate primary key and references two parent business entities:

The table also includes a standard TCA descriptive flexfield block (ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE20), audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN), concurrency control via OBJECT_VERSION_NUMBER, and concurrent-program traceability columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_LOGIN_ID) plus CREATED_BY_MODULE and APPLICATION_ID.

Common Use Cases and Queries

Typical scenarios include determining whether a party is enabled as a customer or supplier, reconciling active usages against date ranges, and reporting on inactive assignments. A representative query joining the party and usage parents:

  • SELECT a.party_usg_assignment_id, a.party_id, a.party_usage_code, a.status_flag
  • FROM hz_party_usg_assignments a, hz_parties p
  • WHERE a.party_id = p.party_id AND a.status_flag = 'A';

Effective-dating filters use SYSDATE BETWEEN effective_start_date AND NVL(effective_end_date, SYSDATE). Descriptive flexfield reporting can extract the ATTRIBUTE columns when custom usage classifications are configured.

Related Objects

  • HZ_PARTIES — joined on PARTY_ID; the master party registry.
  • HZ_PARTY_USAGES_B — joined on PARTY_USAGE_CODE; defines the available usage definitions.
  • HZ_PARTY_USAGES_TL — translation table supplying usage descriptions.
  • HZ_CUST_ACCOUNTS and HZ_SUPPLIERS — downstream operational entities populated once usage assignment is granted.
  • HZ_PARTY_SITES and HZ_LOCATIONS — commonly resolved alongside usage assignments for address reporting.

In summary, HZ_PARTY_USG_ASSIGNMENTS is the pivotal link table that activates party records for functional business roles across the TCA model.