Search Results lock_cnt_point

Overview

APPS.AMS_CNT_POINT_PVT is a private PL/SQL package within the Oracle E-Business Suite (EBS) Oracle Marketing (AMS) module, classified under the API classification "PVT" (private). It serves as the internal implementation layer for managing contact points associated with marketing activities and campaigns. Contact points represent the specific channels, addresses, or contact mechanisms (such as email addresses, phone numbers, or web URLs) through which a marketing activity reaches its target audience.

As a private package, AMS_CNT_POINT_PVT does not expose a public API surface for direct external invocation; instead, it provides the underlying Create, Update, Delete, and validation logic that the corresponding public wrapper package, AMS_CNT_POINT_PVT_W, delegates to. This separation between the private implementation (PVT) and the public wrapper (_PVT_W) is a standard design pattern in Oracle EBS APIs, enabling controlled access while encapsulating business logic. The package is documented as VALID in the APPS schema and is classified as an API Private package type in ETRM 12.2.2. It depends on FND_API, the standard Oracle Applications foundation API library, which provides common utilities such as message handling, transaction control, and error stack management.

Key Procedures and Functions

The package exposes seven documented procedures and functions that collectively implement the lifecycle management of contact point records:

• CREATE_CNT_POINT — Creates a new contact point record, establishing a channel of contact associated with a marketing activity.
• UPDATE_CNT_POINT — Modifies an existing contact point record, allowing changes to the contact point attributes.
• DELETE_CNT_POINT — Removes a contact point record from the system.
• LOCK_CNT_POINT — Acquires a lock on a contact point record, typically used to prevent concurrent modifications during transactional processing.
• VALIDATE_CNT_POINT — Performs validation logic on a contact point record, checking for required fields and business rule compliance before or during DML operations.
• CHECK_CNT_POINT_ITEMS — Verifies the existence or state of related contact point items, supporting referential integrity checks.
• VALIDATE_CNT_POINT_REC — Validates a complete contact point record structure, likely operating on a record type parameter for batch or set-based validation.

These procedures follow the standard EBS API convention of accepting a standardized parameter interface (p_api_version, p_init_msg_list, x_return_status, x_msg_count, x_msg_data) typical of PVT-layer APIs, though exact parameter lists are not documented in the ETRM metadata.

Tables Accessed

The package accesses the following tables through APPS synonyms:

• AMS_ACT_CONTACT_POINTS — The primary table storing contact point records for marketing activities. The CREATE, UPDATE, and DELETE procedures perform DML against this table.
• AMS_ACT_CONTACT_POINTS_S — The corresponding date-tracked (soft delete / audit) table for AMS_ACT_CONTACT_POINTS, supporting Oracle Marketing's record history and auditing requirements.
• DUAL — Used for single-row selection operations, typically for validation lookups or sequence-related queries.

The presence of the _S table indicates that contact point records participate in the Oracle Marketing date-tracking framework.

Usage Notes

AMS_CNT_POINT_PVT is referenced by the public wrapper package AMS_CNT_POINT_PVT_W, which is the entry point for external callers. It is also referenced by AMS_COLLAB_ASSOC_PVT (collaboration association logic) and OZF_COPY_OFFER_PVT (offer copy functionality), indicating that contact point management is invoked during offer duplication and collaborative marketing operations, not solely through direct contact point maintenance. Typical invocation occurs through the Oracle Marketing application forms, concurrent programs, or custom PL/SQL code that calls the corresponding public wrapper APIs rather than the private package directly.