Search Results check_cnt_point_items

Overview

AMS_CNT_POINT_PVT_W is a private PL/SQL package in the Oracle E-Business Suite 12.1.1 and 12.2.2 codebase, owned by the APPS schema and located within the Oracle Marketing (AMS) product family. Its name follows the standard EBS convention for a private API wrapper: the _PVT suffix indicates that the underlying business logic is not exposed for direct customer invocation, while the _W suffix denotes the "wrapper" variant of the package. The package operates with AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the calling schema rather than the definer, a common design in multi-org and HTML/Forms interoperability layers.

The functional domain is contact points — the channels, addresses, phone numbers, and electronic touchpoints associated with parties, contacts, and organizations in the Trade Management and Marketing data model. AMS_CNT_POINT_PVT_W therefore serves as a procedural gateway through which contact point records are validated, created, and maintained by higher-level public APIs, concurrent processes, or the Contact Point user interface.

Key Procedures and Functions

The ETRM metadata documents seven procedures in the package. The two Rosetta procedures, ROSETTA_TABLE_COPY_IN_P3 and ROSETTA_TABLE_COPY_OUT_P3, are array-conversion utilities. They translate between the PL/SQL record type ams_cnt_point_pvt.cnt_point_tbl_type and the set of loosely typed JTF_NUMBER_TABLE, JTF_DATE_TABLE, and JTF_VARCHAR2_TABLE_n collections used by the JTT/HTML layer. This mechanism, historically called "Rosetta" after the translation stone, allows a PL/SQL API to be called from web-based (JSP/HTML) clients that can only marshal scalar arrays across the boundary.

• CHECK_CNT_POINT_ITEMS — the procedure most directly relevant to the user's search term; it performs a validation or existence check over the set of contact point items, typically used to confirm that referenced items are valid before an insert or update proceeds.
• CREATE_CNT_POINT — inserts a new contact point record after validation.
• UPDATE_CNT_POINT — modifies an existing contact point record.
• VALIDATE_CNT_POINT — applies business-rule validation to a single contact point, returning or raising an error when the data violates model constraints.
• VALIDATE_CNT_POINT_REC — the record-level counterpart, validating an entire contact point record structure rather than individual fields.

Tables Accessed

The only documented table reference is PLITBLM, an APPS synonym. PLITBLM is a standard EBS PL/SQL interlanguage or "PL/SQL interface table" structure used to pass values between the Forms/Java layer and PL/SQL, consistent with the package's array-translation design. The bulk of the contact point data manipulation is delegated to the underlying private package AMS_CNT_POINT_PVT, whose record type is declared in this wrapper; the persistent tables (for example the contact point and contact point item tables in the AMS schema) are therefore handled within that inner package rather than directly here.

Usage Notes

Because AMS_CNT_POINT_PVT_W is classified as OTHER and referenced by zero other documented packages, it should be treated as an internal implementation artifact. It is invoked indirectly through the public contact point APIs or the Contact Point form, and through the JTT/HTML client layer via the Rosetta copy routines. Developers should not call ams_cnt_point_pvt_w directly; instead the public AMS contact point API should be used to preserve supportability across 12.1.1 and 12.2.2. CHECK_CNT_POINT_ITEMS is useful diagnostically when tracing why a contact point assignment fails validation, but it is not a supported entry point.