Search Results hz_party_usg_assignment_pvt




Overview
Explore in AI Chat

Overview

HZ_PARTY_USG_ASSIGNMENT_PVT is an internal private API package body in the Oracle E-Business Suite Trading Community Architecture (TCA) schema APPS. It provides the implementation layer that manages the assignment of party usages to parties and party sites. A party usage describes the business role that a party plays — for example Customer, Supplier, or Employee — and Oracle EBS requires that these usages be explicitly assigned, validated, and maintained against the correct registry records. This package encapsulates the logic that binds a usage to a specific party or party site, enforces the rules that govern allowable combinations, and coordinates downstream effects such as the population of the Bulk Ordering Tool (BOT) tables.

The metadata classifies the object as an API of classification PVT, indicating that it is intended for internal consumption by other TCA packages rather than as a formally published public interface. It is documented as VALID in the ETRM repository and is referenced by eighteen other database objects, confirming its role as a shared dependency within the party management stack.

Key Procedures and Functions

The package body exposes eight documented procedures and functions:

  • ASSIGN_PARTY_USAGE — creates a usage assignment linking a party or party site to a defined party usage, applying the governing usage rules.
  • INACTIVATE_USG_ASSIGNMENT — deactivates an existing party usage assignment, typically by setting the end date rather than physically deleting the record.
  • UPDATE_USG_ASSIGNMENT — modifies attributes of an existing usage assignment.
  • REFRESH — rebuilds or synchronizes dependent data maintained outside the base assignment tables, including BOT-related population.
  • SET_CALLING_API — records the identity of the calling API for audit, diagnostics, and error-message context.
  • ALLOW_PARTY_MERGE — determines whether a party merge operation may proceed given its current usage assignments and associated rules.
  • FIND_DUPLICATES — identifies potentially duplicate party usages or assignments for review and resolution.
  • VALIDATE_SUPPLIER_NAME — validates a supplier name against TCA party naming and registration expectations.

Tables Accessed

The package reads and writes several core TCA tables through APPS synonyms. HZ_PARTY_USG_ASSIGNMENTS is the primary transactional table holding assignment rows. HZ_PARTY_USAGES_B stores the definition of each usage. HZ_PARTY_USAGE_RULES holds the rules governing which usages may be assigned and under what conditions. HZ_PARTIES supplies the party registry records. FND_LOOKUP_VALUES provides validation against seeded lookup codes, and PLITBLM is an Oracle-supplied integer table type used for PL/SQL collections. Supporting dependencies include the HZ_PARTY_USG_ASSIGNMENTS_PKG, HZ_POPULATE_BOT_PKG, and HZ_UTILITY_V2PUB packages, along with the FND_API, FND_MSG_PUB, and FND_LOG error-handling and logging infrastructure.

Usage Notes

HZ_PARTY_USG_ASSIGNMENT_PVT is not intended for direct invocation by customer code. It is called internally by the public party usage assignment package and by other TCA components — including customer and supplier registration and update flows — whenever usages must be created, changed, deactivated, or validated. It is also reached indirectly through the Bulk Ordering Tool population and the party merge path, where ALLOW_PARTY_MERGE safeguards data integrity. Because the package depends on FND_MSG_PUB and FND_LOG, callers are expected to initialize the standard API error and logging stacks. Developers extending TCA should use the public wrapper APIs rather than this private body, since its procedures and signature assumptions may change between releases, including between 12.1.1 and 12.2.2.