Search Results ams_act_lists_s

Overview

APPS.AMS_ACT_LIST_PVT is the private implementation body of the Oracle Marketing (AMS) activity list API. In Oracle E-Business Suite 12.1.1 and 12.2.2 it encapsulates the business logic that creates, validates, updates, locks, and deletes activity lists — the campaign worklists that drive telemarketing and telesales execution. Activity lists are the operational interface between campaign planning in AMS and the day-to-day tasks performed by marketing and sales users. The package body exposes the implementation behind the public specification AMS_ACT_LIST_PVT, holding the milestone-oriented and target-group generation routines that are not intended for direct external invocation.

Because it is a PVT (private) package, the body is invoked principally by the public AMS activity-list API, by the AMS list-generation concurrent programs, and by generated Oracle Workflow event activity. Record status is VALID in the APPS schema, and the body carries a substantial dependency footprint across the AMS list, query, and workflow object families.

Key Procedures and Functions

The body contains 18 documented procedures and functions:

• CREATE_ACT_LIST — creates a new activity list header record.
• UPDATE_ACT_LIST — modifies an existing activity list.
• DELETE_ACT_LIST — removes an activity list.
• LOCK_ACT_LIST — applies locking semantics to prevent concurrent modification.
• VALIDATE_ACT_LIST and VALIDATE_ACT_LIST_REC — perform validation of an activity list and of a single list record.
• CHECK_ACT_LIST_ITEMS — verifies the constituent items of an activity list.
• GENERATE_TARGET_GROUP_LIST and GENERATE_TARGET_GROUP_LIST_OLD — generate the target group (list) membership from the associated query and rules; the _OLD variant preserves prior behavior.
• CREATE_TARGET_GROUP_LIST — creates the target group list structure used by the generation routines.
• INIT_ACT_LIST_REC and COMPLETE_ACT_LIST_REC — initialize and complete an activity list record within the generation flow.
• PROCESS_CELL — processes an individual cell within the list generation.
• COPY_TARGET_GROUP — duplicates an existing target group.
• INVOKE_TARGET_GROUP_LOCK — invokes locking on a target group.
• CONTROL_GROUP_GENERATION — orchestrates group generation control.
• CHECK_SUPP... — a supporting check routine recorded in truncated form in the metadata.

Tables Accessed

The package operates against the core AMS activity list tables plus their audit shadows. It reads and writes AMS_ACT_LISTS and AMS_ACT_LISTS_S, the principal activity list header and its audit table, and AMS_ACT_LIST_GROUPS. It also accesses AMS_ACT_LOGS along with AMS_ACT_LOGS_S and AMS_ACT_LOGS_TRANSACTION_ID_S to record list execution and transaction-level activity, and AMS_CAMPAIGN_SCHEDULES_B to relate lists to campaign scheduling.

List-generation logic touches AMS_LIST_CONT_RESTRICTIONS, AMS_LIST_ENTRIES (the generated membership rows), AMS_LIST_HEADERS_ALL, AMS_LIST_QUERIES_ALL and AMS_LIST_QUERIES_PARAM_S, together with the rule metadata in AMS_LIST_RULE_FIELDS and AMS_LIST_RULE_USAGES. These reads supply the query, restriction, and rule definitions from which target group membership is derived. Oracle Workflow integration is represented by references to WF_EVENT_T types.

Usage Notes

AMS_ACT_LIST_PVT is a private body and should not ordinarily be called directly by custom code; integrations should use the public AMS_ACT_LIST_PVT specification, which delegates to these routines. The package is invoked when marketing users create or maintain activity lists from the AMS forms, and when the list-generation and refresh concurrent programs produce target group membership for campaign execution.

Eight dependent packages reference it, and it in turn depends on utility and framework packages including FND_API, FND_GLOBAL, FND_MESSAGE, FND_MSG_PUB, JTF_PLSQL_API, WF_CORE, WF_EVENT, DBMS_SQL, and DBMS_RANDOM. The use of DBMS_SQL indicates dynamic query construction for list selection criteria, consistent with the configurable query framework the package supports. In 12.2.2 the dependency list against AMS_ACT_LISTS_S confirms that audit-trail maintenance is handled inline rather than by the naming conventions of the underlying table alone. This distinction is often relevant when users search the name "ams_act_lists_s", which corresponds to the audit table rather than to the package itself. Because the package body is marked VALID, no recompilation is required in a standard installation.