Search Results arc_incl_object_from




Overview

The AMS_LIST_SELECT_ACTIONS table is a core data object within the Oracle E-Business Suite Marketing (AMS) module, specifically for releases 12.1.1 and 12.2.2. It functions as a configuration and execution log for the list generation process. Its primary role is to store the definitions of the various source objects—such as Discoverer workbooks, target segments, and existing marketing lists—that are selected to populate the entries of a new or updated marketing list. This table essentially holds the "selection rules" or actions that determine which contacts or entities are included in a list, enabling complex, multi-source list compilation within the application.

Key Information Stored

The table's structure is designed to link a list header to its source selection criteria. The critical columns include the primary identifier, LIST_SELECT_ACTION_ID, and the foreign key LIST_HEADER_ID, which ties the action to a specific list in AMS_LIST_HEADERS_ALL. The INCL_OBJECT_NAME and INCL_OBJECT_ID columns identify the specific source object (e.g., a workbook or another list) used for selection. The ARC_INCL_OBJECT_FROM column acts as a lookup type, indicating the source object's entity type or origin. The ORDER_NUMBER column sequences multiple selection actions, allowing for ordered, multi-step list generation. The ACTION_USED_BY_ID column links to objects like models or scores that may have initiated the list action.

Common Use Cases and Queries

A primary use case is auditing and troubleshooting list generation. For instance, to understand all source components used to build a specific marketing list, a query would join AMS_LIST_SELECT_ACTIONS to AMS_LIST_HEADERS_ALL. Another common scenario is reporting on list composition sources across campaigns. A sample query to retrieve selection details for a list might be:

  • SELECT alsa.LIST_HEADER_ID, alh.LIST_NAME, alsa.INCL_OBJECT_NAME, alsa.ARC_INCL_OBJECT_FROM, alsa.ORDER_NUMBER FROM AMS.AMS_LIST_SELECT_ACTIONS alsa, AMS.AMS_LIST_HEADERS_ALL alh WHERE alsa.LIST_HEADER_ID = alh.LIST_HEADER_ID AND alh.LIST_HEADER_ID = :p_list_id ORDER BY alsa.ORDER_NUMBER;

Technical support or data fix scripts may also query this table to identify lists built from a specific, problematic source object by filtering on INCL_OBJECT_ID and ARC_INCL_OBJECT_FROM.

Related Objects

AMS_LIST_SELECT_ACTIONS has extensive foreign key relationships, centralizing its role in list management. Its primary parent is AMS_LIST_HEADERS_ALL (via LIST_HEADER_ID). It references numerous source object tables through the INCL_OBJECT_ID column, including:

Furthermore, it links via ACTION_USED_BY_ID to predictive modeling objects:

These relationships document that list selection actions can be driven by both manual configuration and automated analytical processes within the Marketing module.

  • Table: AMS_LIST_SELECT_ACTIONS 12.2.2

    owner:AMS,  object_type:TABLE,  fnd_design_data:AMS.AMS_LIST_SELECT_ACTIONS,  object_name:AMS_LIST_SELECT_ACTIONS,  status:VALID,  product: AMS - Marketingdescription: This table stores the set of discoverer workbook, target segments and existing lists which are used to generate the set of list entries. ,  implementation_dba_data: AMS.AMS_LIST_SELECT_ACTIONS

  • Table: AMS_LIST_SELECT_ACTIONS 12.1.1

    owner:AMS,  object_type:TABLE,  fnd_design_data:AMS.AMS_LIST_SELECT_ACTIONS,  object_name:AMS_LIST_SELECT_ACTIONS,  status:VALID,  product: AMS - Marketingdescription: This table stores the set of discoverer workbook, target segments and existing lists which are used to generate the set of list entries. ,  implementation_dba_data: AMS.AMS_LIST_SELECT_ACTIONS