Search Results validate_party_site_use

Overview

HZ_REGISTRY_VALIDATE_V2PUB is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is classified as a PUB (public) API and functions as the central validation layer for the Oracle Trading Community Architecture (TCA) Registry. The package does not create or persist registry data itself; instead, it exposes a comprehensive set of validation routines that the HZ_*_V2PUB public APIs invoke before committing party, location, contact, and relationship records to the database.

Because the package is documented as both referencing and being referenced by nearly every major TCA public API — including HZ_PARTY_V2PUB, HZ_PARTY_INFO_V2PUB, HZ_PERSON_INFO_V2PUB, HZ_ORGANIZATION_INFO_V2PUB, HZ_LOCATION_V2PUB, HZ_PARTY_SITE_V2PUB, HZ_CONTACT_POINT_V2PUB, HZ_PARTY_CONTACT_V2PUB, HZ_RELATIONSHIP_V2PUB, HZ_RELATIONSHIP_TYPE_V2PUB, and HZ_MAP_PARTY_PUB — it acts as a shared, reusable conformance engine that ensures registry records satisfy TCA business rules before the create, update, or merge logic in the calling APIs proceeds. Users who search for "hz_party_v2pub" are in practice directed into this validation package, since HZ_PARTY_V2PUB depends upon it for all party-level checks.

Key Procedures and Functions

The ETRM metadata documents 29 public procedures and functions that span the full TCA registry domain. No parameter lists are documented, so only their purpose is described here.

• Party-level validators: VALIDATE_PARTY, VALIDATE_PERSON, VALIDATE_GROUP, and VALIDATE_ORGANIZATION validate the core party entity and its person or organization subtype attributes.
• Party site and site use: VALIDATE_PARTY_SITE and VALIDATE_PARTY_SITE_USE validate the association of a party to a location and the intended usage of that site.
• Organization contacts: VALIDATE_ORG_CONTACT and VALIDATE_ORG_CONTACT_ROLE validate contact assignments and their roles within an organization.
• Person attributes: VALIDATE_PERSON_LANGUAGE validates language proficiency data for a person party.
• Location: VALIDATE_LOCATION validates address and location records, including territory and reference data consistency.
• Relationships: VALIDATE_RELATIONSHIP_TYPE and VALIDATE_RELATIONSHIP validate relationship definitions and party-to-party relationship instances.
• Contact points: VALIDATE_CONTACT_POINT provides the generic entry point, with type-specific validators for EDI, EFT, Web, Phone, Telex, and Email contact points.
• Flexfield and non-support: VALIDATE_ORG_NONSUPPORT_COLUMN validates organization attributes that are not directly supported by the standard organization API.

Tables Accessed

Validation logic draws against a broad set of APPS synonyms. Core TCA tables include HZ_LOCATIONS, HZ_CONTACT_POINTS, HZ_CITIZENSHIP, HZ_CODE_ASSIGNMENTS, HZ_CREDIT_RATINGS, HZ_EDUCATION, HZ_EMPLOYMENT_HISTORY, HZ_FINANCIAL_NUMBERS, and HZ_FINANCIAL_REPORTS — used to verify referenced person, organization, and financial data. Foundation reference data is sourced from FND_CURRENCIES, FND_LANGUAGES, FND_LOOKUP_VALUES, FND_TERRITORIES, FND_OBJECTS, and FND_OBJECT_INSTANCE_SETS, ensuring values conform to seeded and configured lookups, valid currencies, languages, and territories.

Usage Notes

HZ_REGISTRY_VALIDATE_V2PUB is not normally called directly by end users. It is invoked implicitly by the TCA public APIs (HZ_PARTY_V2PUB and its related packages) during create, update, and merge operations, including calls originating from Oracle Forms, concurrent programs such as customer and supplier import, and custom integration code built on the V2PUB API family. The package is referenced by 12 other packages, confirming its role as a shared compliance gate. Custom developers extending TCA should attempt validations through the higher-level APIs rather than calling this package directly, since the public APIs orchestrate the correct sequence of validations. When errors occur, they are typically raised as standard API exceptions propagated back through the calling V2PUB package.