Search Results in_instance_sets




Overview
Explore in AI Chat

Overview

HZ_RELATIONSHIP_TYPE_V2PUB is a public (PUB-classified) PL/SQL package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Oracle Trading Community Architecture (TCA) / Customer Relationship Management family of public APIs and serves as the supported programmatic interface for creating and maintaining relationship type definitions within the TCA Registry. Relationship types are the configurable classifications (for example, "Employee Of", "Contact Of", or "Parent Of") that govern how parties such as persons and organizations may be linked to one another. By exposing these operations through a versioned public API rather than direct DML, the package enforces TCA business rules, validation logic, and the FND_API error-handling conventions. The package is registered in ETRM as VALID and depends directly on FND_API and the SYS.STANDARD package.

Key Procedures and Functions

The documented API surface of HZ_RELATIONSHIP_TYPE_V2PUB comprises three entry points:

  • CREATE_RELATIONSHIP_TYPE — Creates a new relationship type definition in the TCA Registry, applying the standard public-API validation, defaulting, and error-stack handling provided by FND_API. It returns the generated identifier for the newly created relationship type.
  • UPDATE_RELATIONSHIP_TYPE — Modifies the attributes of an existing relationship type definition identified by its primary key. Only the mutable attributes of the relationship type are changed; the procedure preserves the API's optimistic-locking and validation behavior.
  • IN_INSTANCE_SETS — Determines whether a specified object is a member of one or more instance sets. This function underpins the TCA object/instance-set model used for extensibility and is referenced internally by other TCA public APIs.

As with other V2PUB packages, these procedures follow the Oracle Applications public-API standard: callers receive a return status and must inspect the FND_MSG_PUB message stack for diagnostic detail rather than relying on unhandled exceptions.

Tables Accessed

The package operates against the following tables through APPS synonyms:

  • HZ_RELATIONSHIP_TYPES — The primary table holding relationship type definitions. It is inserted into by CREATE_RELATIONSHIP_TYPE and updated by UPDATE_RELATIONSHIP_TYPE.
  • HZ_PARTIES — The TCA party registry. It is consulted to validate that relationship type definitions are consistent with the parties they will classify.
  • FND_OBJECTS — The Applications Object Library definition table, used to resolve the object metadata that relationship types and instance-set membership are associated with.
  • FND_OBJECT_INSTANCE_SETS — The mapping table between objects and their instance sets, queried by IN_INSTANCE_SETS to evaluate membership.

Usage Notes

HZ_RELATIONSHIP_TYPE_V2PUB is intended for use by Oracle application forms, concurrent programs, and customer-written extensions that must manage relationship types through a supported interface. It is referenced by five other packages, including HZ_REGISTRY_VALIDATE_V2PUB, HZ_HIERARCHY_V2PUB, HZ_COPY_REL_PVT, HZ_GEOGRAPHY_STRUCTURE_PUB, and its own Java wrapper HZ_RELATIONSHIP_TYPE_V2PUB_JW. The link to HZ_REGISTRY_VALIDATE_V2PUB is particularly relevant: registry validation logic relies on this package to confirm that relationship type definitions are valid before party relationships are committed. Because these are public APIs, they should be called with the standard FND_API initialization of the message stack, and the return status and message stack should always be checked to detect validation failures. Direct DML against the underlying tables is not supported and can bypass the integrity rules enforced here.