Search Results hz_relationship_type_v2pub_jw

Overview

The APPS.HZ_RELATIONSHIP_TYPE_V2PUB_JW package is a PL/SQL API belonging to the Oracle Trading Community Architecture (TCA) and Registry (HZ) schema, which forms the foundation of customer, party, and relationship data management across Oracle E-Business Suite. In EBS 12.1.1 and 12.2.2, this package serves as the public programmatic interface for creating and maintaining relationship type definitions. Relationship types classify the nature of the link between two parties (for example, "Employee Of," "Contact Of," or "Shareholder Of") and provide the structural metadata that governs how party relationships are authenticated, constrained, and secured throughout the TCA model.

The object is classified in the ETRM repository as an OTHER API and currently holds a VALID status in the APPS schema. It is a generated wrapper-style package (denoted by the _JW suffix), which conventionally indicates a Java Web Services–oriented or Java-wrapped interface layer used to expose the underlying TCA relationship type business logic to external integration channels. Its dependencies are limited to the SYS.STANDARD package, reflecting that it relies on core PL/SQL runtime services rather than a broad set of subordinate TCA packages.

Key Procedures and Functions

The package exposes two documented public subprograms:

• CREATE_RELATIONSHIP_TYPE_1 — Creates a new relationship type record. This entry point is used to define a fresh classification of party-to-party linkage, establishing the role/reverse-role pairing and associated directional semantics that TCA uses when constructing relationship records between entities. It is the primary insertion API for extending the relationship type reference set.
• UPDATE_RELATIONSHIP_TYPE_2 — Modifies an existing relationship type definition. Successive numbered suffixes (the trailing _1, _2) reflect Oracle's versioning convention, where newer variants are introduced to support additional or altered business requirements while preserving backward compatibility. This routine is used to amend attributes of an already-defined relationship type without creating a duplicate.

No parameter signatures are documented in the retrieved metadata; consumption of these routines should therefore always be validated against the current package specification in the target instance before coding.

Tables Accessed

The ETRM excerpt for this package lists no directly referenced tables via APPS synonyms. This is consistent with the _JW wrapper pattern, in which the actual DML against the underlying TCA relationship type base tables (such as those held within the HZ_RELATIONSHIP_TYPE family) is delegated to the non-wrapped counterpart package that this object shadows. As documented, HZ_RELATIONSHIP_TYPE_V2PUB_JW references no external packages and is referenced by zero other packages, confirming it sits at a leaf position in the TCA dependency graph and acts purely as an exposed entry surface.

Usage Notes

This package is typically invoked through integration layers rather than directly by end users. Common invocation paths include:

• Java or SOA-based integrations that call the wrapped API to propagate relationship type definitions from external master data systems into TCA.
• Custom concurrent programs or PL/SQL scripts that need to seed or adjust relationship type metadata during implementation or data migration activities.
• Targeted corrective scripts during patching or configuration of the party relationship model.

Because the package carries an OTHER classification and exposes only creation and update operations, it is not intended for the high-volume transactional party relationship assignments handled by the standard V2PUB party relationship APIs. Developers should treat it as a maintenance interface for the relationship type reference data itself. As with all TCA public APIs, direct table manipulation should be avoided in favor of these supported entry points to preserve data integrity and upgrade safety across 12.1.1 and 12.2.2.