Results for “validate_contact_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AS_TCA_PVT is a private API package body in the APPS schema that forms part of the Oracle Trade Management / Advanced Pricing (AS) product family, specifically the TCA (Trading Community Architecture) integration layer. Its role is to provide internal validation services for the core TCA entities — parties, party sites, contact points, and contacts — used throughout the AS modules. The "PVT" classification indicates this is a private implementation package, meaning it is intended for internal consumption by other AS or TCA packages rather than as a public, externally callable API. The package body is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2, confirming it remains an active, supported component across these releases.

Key Procedures and Functions

The package exposes four documented procedures and functions, each responsible for validating a distinct TCA entity identifier before it is used in downstream processing:

• VALIDATE_PARTY_ID — Confirms that a supplied party identifier corresponds to a valid, active party record. This is the foundational validation, since sites, contacts, and contact points all ultimately belong to a parent party.
• VALIDATE_PARTY_SITE_ID — Verifies that a given party site identifier is valid and correctly associated with its parent party. This guards against orphaned or inconsistent location references.
• VALIDATE_CONTACT_POINT_ID — Checks the validity of a contact point, which represents a specific communication channel (such as phone or email) attached to a party or site.
• VALIDATE_CONTACT_ID — Validates a contact identifier, ensuring the referenced contact record exists and is usable in the calling context.

Because this is a private package, these routines typically perform lightweight existence and status checks and return a success or failure indication to the calling program rather than raising user-facing errors directly.

Tables Accessed

The package reads from several TCA interface views rather than base tables directly, reflecting Oracle's preference for encapsulating the underlying data model. The documented dependencies include AS_PARTY_ADDRESSES_V, AS_PARTY_CUSTOMERS_V, AS_PARTY_ORG_CONTACTS_V, AS_PARTY_PHONES_V, and JTF_PARTY_PHONES_V. Each view supports a specific validation path: address and customer views back the party and party site validations, while the organization contacts and phones views support contact and contact point validation. No write operations to these objects are documented; AS_TCA_PVT is a read-only validation utility. It also depends on the standard FND_API, FND_GLOBAL, FND_MESSAGE, and FND_MSG_PUB packages for logging, context retrieval, and message plumbing.

Usage Notes

AS_TCA_PVT is not referenced by any database object according to the dependency metadata, but the documented package data states it is referenced by four other packages. This apparent discrepancy reflects the fact that dependency reporting focuses on stored schema objects while the package is invoked at runtime by sibling PL/SQL packages. In practice, AS_TCA_PVT is called internally by other AS packages whenever a TCA identifier must be validated before processing — for example, during trade management setup, customer assignment, or contact synchronization. It is not intended for direct invocation from Oracle Forms or concurrent programs, and custom code should avoid calling it because private APIs are subject to change without notice across releases and patches. Developers requiring equivalent validation should use the public TCA APIs (such as the HZ_PARTY_V2PUB package family) rather than this private implementation.