Search Results org_contact_rec_type

Overview

HZ_PARTY_CONTACT_V2PUB is a public PL/SQL package in the Oracle Trading Community Architecture (TCA) product (product code HZ), owned by the APPS schema. It exposes the create and update APIs for organizational contacts and contact roles, providing the supported programmatic interface for registering and maintaining contact information associated with a party. The package is classified as a PUBLIC API (API classification: PUB), meaning its procedures are intended for direct invocation by external and customer code, and its signature is preserved across releases per Oracle's API lifecycle policy. The package header carries $Header ARH2PCSS.pls 120.9, and its documentation reference is the Party Contact APIs chapter of the Oracle Trading Community Architecture Technical Implementation Guide (120hztig.pdf). Its documented business entity is HZ_CONTACT, with a display name of "Party Contact."

Key Procedures and Functions

The ETRM 12.2.2 metadata documents six public procedures and functions:

• CREATE_ORG_CONTACT — Creates a new organizational contact record, populating the HZ_ORG_CONTACTS entity and any associated contact number data.
• UPDATE_ORG_CONTACT — Updates an existing organizational contact, using primary key and object version number semantics typical of TCA V2 public APIs.
• CREATE_ORG_CONTACT_ROLE — Creates a contact role assignment linking a contact to a role type within a party relationship context.
• UPDATE_ORG_CONTACT_ROLE — Updates an existing contact role record.
• GET_ORG_CONTACT_REC — Returns a populated record structure for an existing organizational contact, providing a template for callers preparing create or update calls.
• GET_ORG_CONTACT_ROLE_REC — Returns a populated record structure for an existing contact role.

The user's search term, org_contact_rec_type, refers to the PL/SQL record type declared in this package that defines the attribute payload passed to the contact procedures. It includes fields such as org_contact_id, comments, contact_number, department_code, department, title, job_title, decision_maker_flag, job_title_code, reference_use_flag, rank, party_site_id, orig_system_reference, orig_system, attribute_category, and attribute1 through attribute24, along with created_by_module, application_id, and an embedded party_rel_rec of type HZ_RELATIONSHIP_V2PUB.relationship_rec_type. A companion type, org_contact_role_rec_type, carries contact role attributes such as org_contact_role_id and role_type.

Tables Accessed

The package operates against the following tables, accessed through APPS synonyms:

• HZ_ORG_CONTACTS — Primary store for organizational contact rows created or modified by the contact procedures.
• HZ_CONTACT_NUMBERS_S — Sequence source used to generate unique contact number identifiers.
• HZ_ORG_CONTACT_ROLES — Stores contact role assignments managed by the create and update role procedures.
• HZ_PARTIES — Parent party record against which contacts are anchored.
• HZ_PERSON_PROFILES — Person profile data linked to contacts where applicable.
• HZ_RELATIONSHIPS and HZ_RELATIONSHIP_TYPES — Support the embedded party_rel_rec and the relationship context of a contact role.
• DUAL — Used for lightweight PL/SQL evaluations and sequence/version lookups.

Usage Notes

HZ_PARTY_CONTACT_V2PUB is typically invoked from Oracle Forms-based TCA maintenance screens (for example, the Party and Contact forms), from concurrent programs that bulk-load or migrate contact data, and from custom PL/SQL integrations that must create contacts through supported APIs rather than direct DML. The ETRM metadata records that this package is referenced by 40 other packages, confirming its role as a foundational dependency within TCA. Callers should always obtain a record template through GET_ORG_CONTACT_REC or GET_ORG_CONTACT_ROLE_REC, populate the relevant fields, and pass the populated record to the create or update procedure, rather than constructing records manually. Because the API is public and versioned (V2), its signature is stable within releases 12.1.1 and 12.2.2, and it should be preferred over direct table manipulation to preserve data integrity and TCA internal bookkeeping.