Search Results g_valid_level_high




Overview
Explore in AI Chat

Overview

HZ_PARTY_USG_ASSIGNMENT_PVT is an Oracle E-Business Suite private (PVT) PL/SQL package owned by the APPS schema. It is the internal implementation layer that governs the assignment of party usages to records in the TCA (Trading Community Architecture) registry. A "party usage" is the mechanism by which Oracle EBS classifies a party — for example, whether an organization or person is treated as a supplier, a customer, a prospect, or a contact. Because a single party record may carry multiple usages simultaneously, the assignment, update, and inactivation of those usage rows must be performed through a controlled API rather than by direct DML against the underlying tables.

The package was authored under an AUTHID CURRENT_USER declaration and carries an original header revision of 120.2 dated 2005, indicating it is a long-standing, stable component of the TCA foundation. It declares a strongly typed record structure, party_usg_assignment_rec_type, which mirrors the columns of the party usage assignment entity, including party identity, usage code, effective dating, owner table context, and twenty descriptive flexfield attributes. The package also publishes a set of validation-level constants (G_VALID_LEVEL_FULL, G_VALID_LEVEL_HIGH, G_VALID_LEVEL_THIRD_MEDIUM, G_VALID_LEVEL_MEDIUM, G_VALID_LEVEL_LOW, and G_VALID_LEVEL_NONE) that express graduated degrees of validation confidence, consistent with the fuzzy-matching model used by Oracle's data quality and duplicate-identification framework.

Key Procedures and Functions

The ETRM repository documents eight public procedures and functions within this package:

  • ASSIGN_PARTY_USAGE — Creates a new party usage assignment for a given party, applying the package's effective-dating and validation rules.
  • INACTIVATE_USG_ASSIGNMENT — Ends an existing usage assignment, typically by setting an effective end date rather than physically deleting the row.
  • UPDATE_USG_ASSIGNMENT — Modifies attributes of an existing usage assignment, preserving effective-date integrity.
  • REFRESH — Re-synchronizes or recalculates usage assignment data, generally invoked after bulk changes or dependent processing.
  • SET_CALLING_API — Records the identity of the calling API so that created_by_module and audit context can be attributed correctly. This is a standard convention in TCA private APIs.
  • ALLOW_PARTY_MERGE — Evaluates whether the usage assignments attached to a party permit that party to be merged into another.
  • FIND_DUPLICATES — Identifies parties whose usage and attribute data suggests potential duplication, supporting the customer and supplier de-duplication processes.
  • VALIDATE_SUPPLIER_NAME — Validates a supplier name against party usage rules and existing party records. This is the procedure most commonly associated with the search term the user entered, and it is the entry point that custom code typically probes when automating supplier registration or validation.

Tables Accessed

The package operates against the following tables, accessed through APPS synonyms: HZ_PARTIES (the master party registry, read to confirm party identity and merge eligibility), HZ_PARTY_USAGES_B (the usage definition table that supplies valid usage codes), HZ_PARTY_USAGE_RULES (which constrains which usages may be assigned in a given context), HZ_PARTY_USG_ASSIGNMENTS (the primary transaction table into which assignments are inserted, updated, and inactivated), FND_LOOKUP_VALUES (for flexfield and reference validation), and PLITBLM (the standard PL/SQL index-by table used for message stack handling).

Usage Notes

As a private API, this package is not intended for direct invocation by customer code; Oracle supports it only through the public wrapper HZ_PARTY_USG_ASSIGNMENT_V2PUB or equivalent. It is referenced by eighteen other packages, indicating that much of the TCA supplier and customer lifecycle depends on it. Typical invocation paths include the Suppliers and Customers forms, the Supplier Registration and Duplicate Identification concurrent programs, and TCA batch import flows. When customizing, callers should always invoke SET_CALLING_API before the assignment procedures so that audit columns remain meaningful, and should respect the effective-date semantics rather than deleting assignment rows directly.