Search Results validate_act_list_rec

Overview

AMS_ACT_LIST_PVT_W is the public wrapper package for the Oracle Marketing (AMS) Activity List private API, AMS_ACT_LIST_PVT. Activity Lists are the containers that group marketing activities (campaigns, events, and related deliverables) into a manageable, ordered collection for planning and execution purposes. This wrapper package exposes the underlying private API to external callers, including Oracle Forms-based user interfaces, concurrent programs, and custom PL/SQL integrations, while preserving the AUTHID CURRENT_USER invocation model and the standard Oracle EBS API conventions (API version number, initialization flag, commit flag, validation level, and the standard OUT parameters x_return_status, x_msg_count, and x_msg_data).

The package is classified as OTHER in the ETRM metadata and its header bears the identifier $Header: amswalss.pls 120.1 2005/06/27. The same functionality is available in both 12.1.1 and 12.2.2, since this object belongs to the long-standing Oracle Marketing foundation layer rather than to any release-specific technology stack. It is important to note the wrapper does not itself contain business validation logic; it delegates to AMS_ACT_LIST_PVT and provides the Rosetta table conversion utilities required to bridge PL/SQL collection types across the OTA/AMS call boundary.

Key Procedures and Functions

• ROSETTA_TABLE_COPY_IN_P1 / ROSETTA_TABLE_COPY_OUT_P1 — Conversion helpers that move data between the ams_act_list_pvt.child_type record/collection structure and the JTF_VARCHAR2_TABLE_100 collection type. The IN variant populates the internal AMS structure from the JTF table, while the OUT variant performs the reverse mapping.
• ROSETTA_TABLE_COPY_IN_P4 / ROSETTA_TABLE_COPY_OUT_P4 — Broader conversion helpers mapping the ams_act_list_pvt.act_list_tbl_type structure against thirteen parallel JTF collections (JTF_NUMBER_TABLE, JTF_DATE_TABLE, and JTF_VARCHAR2_TABLE_100). These support the multi-attribute activity list record used by create/update operations.
• CREATE_ACT_LIST — Creates a new activity list record, returning the generated x_act_list_header_id along with the standard API status out parameters.
• UPDATE_ACT_LIST — Modifies an existing activity list header.
• VALIDATE_ACT_LIST — Performs record-level validation against the activity list entity, invoked prior to insert or update.
• CHECK_ACT_LIST_ITEMS — Validates the line-level items associated with an activity list.
• VALIDATE_ACT_LIST_REC — The specific entry point surfaced by the search term "validate_act_list_rec." It validates a single activity list record (the private rec structure) and is the routine most commonly referenced by callers needing pre-save validation of one record rather than an entire entity.
• INIT_ACT_LIST_REC — Initializes an activity list record structure with default values prior to population.
• COMPLETE_ACT_LIST_REC — Finalizes an activity list record, typically after validation and before persistence, ensuring all derived attributes are populated.

Tables Accessed

The ETRM metadata documents a single referenced table via APPS synonym: PLITBLM. This is the PL/SQL inter-language table-map view used by Oracle EBS APIs as the source for Rosetta-style bulk collection conversion. It does not carry business data; it supports the table-driven copy routines. Actual activity list persistence is performed by the underlying AMS_ACT_LIST_PVT package against the AMS activity list base tables (such as AMS_ACT_LISTS and AMS_ACT_LIST_ITEMS), which are not individually enumerated in the wrapper metadata.

Usage Notes

AMS_ACT_LIST_PVT_W is invoked from the Oracle Marketing Activity List (AMS) Forms, from concurrent programs that perform bulk activity list creation or maintenance, and from custom PL/SQL code that must create, update, or validate activity lists using the supported public API rather than direct DML. Callers should follow the standard EBS API pattern: call INIT_ACT_LIST_REC, populate the record, invoke VALIDATE_ACT_LIST_REC, then CREATE_ACT_LIST or UPDATE_ACT_LIST, passing fnd_api.g_miss_* or default sentinel values where attributes are unchanged. The metadata records zero inbound package references, confirming it is an integration-surface object rather than an internally chained dependency.