Search Results assign_party_usage




Overview

HZ_PARTY_USG_ASSIGNMENT_PUB is the public application programming interface package for creating and maintaining party usage assignments within Oracle E-Business Suite Release 12.1.1 and 12.2.2. Party usages classify a party record according to the business roles it plays — for example Customer, Supplier, Employee, or Prospect — and the assignment of these usages governs which downstream functionality, such as order entry, receivables, or procurement, recognizes the party as eligible.

The package body is a thin public wrapper over the private implementation package HZ_PARTY_USG_ASSIGNMENT_PVT. Each public procedure registers the calling API and delegates to the corresponding private procedure, passing an initialized message list flag. This layered design keeps error handling, message stack management, and validation logic inside the private layer while exposing a stable, documented calling interface to external consumers. The source header identifies the body revision as 120.0, and the modification history records that the package was created on 01/05/2005 by Jianying Huang.

Key Procedures and Functions

Three public procedures are documented for this package:

  • ASSIGN_PARTY_USAGE — Creates a party usage assignment. It accepts a party usage assignment record and, as documented for the API, an initialization flag for the message stack, and it returns a standard FND_API return status along with message count and message data outputs. The public procedure delegates to the private implementation with a validation level of G_VALID_LEVEL_FULL, so the full business validation rules for a new assignment are enforced.
  • INACTIVATE_USG_ASSIGNMENT — Deactivates an existing party usage assignment, logically ending the association rather than deleting it, thereby preserving the historical record of the party's prior usages and protecting referential integrity with dependent transactions that were created while the usage was active.
  • UPDATE_USG_ASSIGNMENT — Modifies the attributes of an existing party usage assignment, such as its status or effective dates, through the same validated public interface.

All three procedures follow the Oracle Application Object Library API conventions: an input initialization flag, an assignment record, and the standard return status, message count, and message data outputs.

Tables Accessed

The ETRM metadata does not enumerate the tables referenced through APPS synonyms at the package-body level. In practice the package operates against the party usage assignment entity — the HZ_PARTY_USAGES and HZ_PARTY_USG_ASSIGNMENTS tables — reading and writing assignment records through the private layer rather than issuing SQL directly in the public body. Because all table access is performed inside HZ_PARTY_USG_ASSIGNMENT_PVT, the public package presents a narrow, version-stable contract even if the underlying schema objects change.

Usage Notes

HZ_PARTY_USG_ASSIGNMENT_PUB is the supported entry point for any code that needs to assign, update, or inactivate party usages, and is referenced by four other packages within the E-Business Suite. It is typically invoked from party maintenance and customer or supplier setup forms, from concurrent programs that bulk-create or bulk-retire usages, and from custom PL/SQL that must register a party in a business role. Callers should always check x_return_status against FND_API.G_RET_STS_SUCCESS, G_RET_STS_ERROR, and G_RET_STS_UNEXP_ERROR, and inspect the message stack when a failure is returned. Direct DML against the underlying HZ tables is unsupported; because the public procedures always invoke the full validation level, all documented business rules are preserved. The package is identified in ETRM as owned by APPS and classified as a PUB API.