Search Results validate_location

Overview

HZ_DYN_VALIDATION is a public PL/SQL package in the Oracle E-Business Suite Trading Community Architecture (TCA), owned by the APPS schema and declared with AUTHID CURRENT_USER. Its source header (ARHDVSS.pls, version 115.2) dates to 2002, reflecting its role as a long-standing validation utility within the Oracle Receivables / Oracle Customers (HZ) module. The package provides a dynamic, profile-driven validation layer for the records manipulated by the TCA public APIs, most notably the hz_party_v2pub, hz_relationship_v2pub, hz_party_contact_v2pub, hz_party_site_v2pub, hz_location_v2pub, and hz_contact_point_v2pub packages.

The central design concept is that validation behavior is not hard-coded per API call; instead, each procedure accepts an x_validation_profile parameter that selects a configured validation rule set. The package emits four named exceptions — invalid_profile_option, invalid_validation_procedure, null_profile_value, and execution_error — indicating that profile misconfiguration and rule execution failures are first-class error conditions that calling code must handle. The optional x_temp_id parameter allows validation to be associated with a temporary (in-flight) identifier, supporting validation of records before they are committed to the base TCA tables.

Key Procedures and Functions

The package exposes seven documented procedures, each aligned to a TCA entity type:

• VALIDATE_ORGANIZATION — validates an organization record supplied through the hz_party_v2pub organization record type against the selected validation profile.
• VALIDATE_GROUP — validates a group record (hz_party_v2pub.group_rec_type), typically used for group-level party constructs.
• VALIDATE_RELATIONSHIP — validates a relationship record (hz_relationship_v2pub.relationship_rec_type) between parties.
• VALIDATE_ORG_CONTACT — the procedure returned by the user’s search term "validate_org_contact". It validates an organization contact record (hz_party_contact_v2pub.org_contact_rec_type), covering the contact details associated with an organization party.
• VALIDATE_PARTY_SITE — validates a party site record (hz_party_site_v2pub.party_site_rec_type).
• VALIDATE_LOCATION — validates a location record (hz_location_v2pub.location_rec_type).
• VALIDATE_CONTACT_POINT — validates a contact point together with its type-specific companions: EDI, EFT, e-mail, phone, telex, and web record types, plus the base contact point record.

Tables Accessed

The package references a family of validation staging tables via APPS synonyms, consistent with its dynamic-rule architecture. These include HZ_PARTY_VAL_GT and HZ_PARTY_VAL_GT_S, HZ_GROUP_VAL_GT and HZ_GROUP_VAL_GT_S, HZ_RELATIONSHIP_VAL_GT, HZ_ORG_CONTACT_VAL_GT, HZ_PARTY_SITE_VAL_GT and HZ_PARTY_SITE_VAL_GT_S, HZ_LOCATION_VAL_GT and HZ_LOCATION_VAL_GT_S, and HZ_CONTACT_POINT_VAL_GT and HZ_CONTACT_POINT_VAL_GT_S. Two additional tables appear: HZ_CONTACT_VAL_GT_S and HZ_ORG_PROFILE_VAL_GT / HZ_ORG_PROFILE_VAL_GT_S. The _GT suffix denotes global temporary tables used to stage the record being validated and its rule results within a session; the _S variants hold shadow or rule-set definitions. HZ_ORG_PROFILE_VAL_GT is associated with organization profile validation.

Usage Notes

HZ_DYN_VALIDATION is invoked behind the scenes by the TCA public APIs and by forms and concurrent programs that perform customer, contact, site, and location maintenance. The ETRM metadata records that it is referenced by one other package, confirming it is a subordinate utility rather than a top-level entry point. Custom integrations that call hz_party_v2pub or hz_party_contact_v2pub directly — for example, through interfaces or web services — will implicitly exercise these procedures, so the configured validation profile must supply a valid rule set or the caller will receive one of the package’s declared exceptions. This behavior is identical across EBS 12.1.1 and 12.2.2.