Search Results hz_party_usage_assignments

Overview

HZ_PARTY_BO_PVT is a private PL/SQL package body in the Oracle E-Business Suite Trading Community Architecture (TCA) / Receivables (AR) module. Its name reflects its role as the "Business Object" (BO) private layer for the HZ_PARTIES entity and its dependent sub-entities. The package encapsulates the internal logic required to construct, populate, and persist TCA party business objects. In EBS 12.1.1 and 12.2.2, the TCA data model treats a party (person or organization) as an aggregate of related records: relationships, classifications, certifications, financial profiles, and party usage assignments. HZ_PARTY_BO_PVT provides the reusable private routines that orchestrate creation and update of these aggregate structures, including business object versioning, business object tracking, and Business Event System (BES) callouts. It is an internal ("PVT") API, meaning Oracle does not support direct customer invocation; it is consumed by public party APIs and other TCA packages.

Key Procedures and Functions

The ETRM metadata documents 19 procedures and functions that fall into logical groups:

• Party preferences and relationships: SAVE_PARTY_PREFERENCES, CREATE_RELATIONSHIPS, CREATE_RELATIONSHIP_OBJ, UPDATE_RELATIONSHIP_OBJ, SAVE_RELATIONSHIP_OBJ, SAVE_RELATIONSHIPS, and GET_RELATIONSHIP_OBJ handle party-to-party relationship structures — creating the object form, persisting it, and retrieving it for update.
• Classifications: CREATE_CLASSIFICATIONS and SAVE_CLASSIFICATIONS build and persist party classification codes and their associated attributes.
• Certifications: CREATE_CERTIFICATIONS and SAVE_CERTIFICATIONS manage certifications asserted against a party, typically for supplier or compliance purposes.
• Financial profiles: CREATE_FINANCIAL_PROFILES and SAVE_FINANCIAL_PROFILES handle financial profile data used in credit and risk assessment.
• Party usage assignments: CREATE_PARTY_USAGE_ASSGMNT and SAVE_PARTY_USAGE_ASSGMNT are the routines directly relevant to the search term "hz_party_usage_assignments." They construct and persist usage assignments that determine how a party may participate in a particular application or business context.
• Infrastructure: CALL_BES invokes Business Event System callouts; IS_RAISING_CREATE_EVENT and IS_RAISING_UPDATE_EVENT determine whether create or update events must be fired; RETURN_ALL_MESSAGES surfaces the accumulated error/warning message stack to the caller.

Private helper routines declared in the specification excerpt — log, add_cust_tracking, set_hz_parties_bo_ver, assign_certification_rec, and assign_financial_prof_rec — support these public operations by writing audit rows, managing BO_VERSION_NUMBER on HZ_PARTIES, and mapping object attributes into PL/SQL record types.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

• HZ_PARTIES: the master party record; updated to maintain BO_VERSION_NUMBER.
• HZ_RELATIONSHIPS: stores party relationship rows created or updated by the relationship procedures.
• HZ_BUS_OBJ_DEFINITIONS: defines which business objects exist for party processing.
• HZ_BUS_OBJ_TRACKING: records business object tracking entries, including the add_cust_tracking output.
• HZ_ORIG_SYS_REFERENCES: captures original system reference mappings, important for data migration and multi-source feeds.
• WF_PARAMETER_LIST_T and PLITBLM: Workflow parameter list and PL/SQL index-by table types used for Business Event System payloads.

Usage Notes

HZ_PARTY_BO_PVT is not intended for direct customer invocation. It is referenced by 13 other packages and is typically invoked indirectly through public TCA party APIs, party maintenance forms in the EBS HTML/JSP UI, and concurrent programs that load or synchronize party data. The Business Object Event System integration (CALL_BES, IS_RAISING_CREATE_EVENT, IS_RAISING_UPDATE_EVENT) means operations here may trigger subscriptions in the Workflow Business Event System, so custom event subscriptions should account for these callouts. Because BO_VERSION_NUMBER is maintained on HZ_PARTIES, any custom code that modifies party records directly must synchronize with this version counter to avoid concurrency or optimistic locking issues. For 12.1.1 and 12.2.2, the package has remained stable in documented behavior; customers should rely on the supported public HZ_PARTY_* APIs rather than calling this private body directly.