Search Results validate_party_site_id

Overview

AS_TCA_PVT is a private (PVT) validation package in the Oracle E-Business Suite Applications product, part of the customer model foundation known as Trading Community Architecture (TCA). Its business function is to centralize and standardize entity validation for party-related records — verifying that a given party, party site, contact, or contact point actually exists within the TCA registry before dependent processing proceeds. The package header dates to May 2000, reflecting its role as long-standing foundational infrastructure within the Oracle Applications schema (APPS).

Because it is classified as a private API, AS_TCA_PVT is not part of Oracle's public, supported integration surface. It sits beneath the public TCA APIs and is intended for internal consumption by other Oracle Applications packages. Its validation logic exists to protect data integrity across modules that record or reference TCA entities.

Key Procedures and Functions

Four documented procedures form the package interface. Each returns the standard concurrent-style API outcome parameters: a return status, a message count, and a message data string.

• VALIDATE_PARTY_ID — Confirms that a supplied party identifier corresponds to a valid record in the HZ_PARTY table. This is the entry point most directly associated with the user search term "validate_party_id," invoked to ensure a party reference is genuine before it is used or stored.
• VALIDATE_PARTY_SITE_ID — Validates a party site identifier, confirming that the site belongs to the registry in HZ_PARTY_SITES and, implicitly, that it associates with the supplied party.
• VALIDATE_CONTACT_POINT_ID — Validates a contact point identifier, checking that it exists in HZ_CONTACT_POINTS and relates to the given party and organization contact.
• VALIDATE_CONTACT_ID — Validates an organization contact identifier against HZ_ORG_CONTACTS for the supplied party.

Each procedure accepts an initialization flag (p_init_msg_list) defaulting to FND_API.G_FALSE, consistent with the Oracle Applications API message-handling convention.

Tables Accessed

The package reads the core TCA registry tables to perform its existence checks:

• HZ_PARTY — the master party table; queried by VALIDATE_PARTY_ID to confirm party existence.
• HZ_PARTY_SITES — the party site registry; queried by VALIDATE_PARTY_SITE_ID.
• HZ_CONTACT_POINTS — the contact point registry; queried by VALIDATE_CONTACT_POINT_ID.
• HZ_ORG_CONTACTS — the organization contact registry; queried by VALIDATE_CONTACT_ID.

These tables are accessed through APPS synonyms. Validation is read-only in nature; the package does not write to these tables, it only confirms the presence of referenced rows.

Usage Notes

AS_TCA_PVT is a private package and is referenced by four other packages within Oracle EBS. It is typically invoked indirectly — for example by public TCA APIs and other internal validators — rather than called directly from forms or concurrent programs. Custom code should in general call the supported public TCA APIs rather than referencing this PVT package, since private APIs may change without notice. Within 12.1.1 and 12.2.2, its validation procedures provide the existence-check behavior that callers expect when confirming party, site, contact, and contact point identity before committing related records.