Search Results ams_list_tmp_entries




Overview
Explore in AI Chat

Overview

AMS_LIST_TMP_ENTRIES is a staging table owned by the AMS (Marketing) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to be temporarily populated during the list generation process, prior to the records being inserted into the permanent List Entry table (AMS_LIST_ENTRIES). In effect, it functions as a transient work area where the list-building engine assembles candidate rows — sourced from customer, prospect, and other marketing sources — applies selection criteria, ranking, and cell assignment, and then flushes the qualified set into the final list structure. Because the contents are transient by design, data retention in this table is normally short-lived and tied to the lifecycle of a single list generation run.

From a Data Vault modeling perspective, the supplied metadata classifies this object heuristically as a standalone structure, meaning no parent/child hub-link relationship is implied. In practice, however, its columns reference both AMS_LIST_SELECT_ACTIONS and FND_SECURITY_GROUPS, so it behaves as a link-like staging element connecting a list header to the action and security context that produced each entry.

Key Information Stored

The documented schema contains 15 columns. The most significant for understanding and querying the table are:

No surrogate primary key column is explicitly documented in the excerpt; the natural candidate key is the combination of LIST_HEADER_ID, LIST_ENTRY_SOURCE_ID, LIST_ENTRY_SOURCE_TYPE, and CELL_CODE.

Common Use Cases and Queries

Typical uses center on diagnosing list generation runs, verifying selection action behavior, and auditing cell/rank assignment.

  • Counting staged rows per list: SELECT list_header_id, COUNT(*) FROM ams.ams_list_tmp_entries GROUP BY list_header_id;
  • Reviewing rank distribution: SELECT cell_code, rank, COUNT(*) FROM ams.ams_list_tmp_entries WHERE list_header_id = :id GROUP BY cell_code, rank;
  • Reconciling staged versus persisted entries by comparing against AMS_LIST_ENTRIES.
  • Identifying which selection action produced rows via join to AMS_LIST_SELECT_ACTIONS on LIST_SELECT_ACTION_ID.
  • Diagnosing why a source record failed to reach the final list by inspecting SAVE_ROW_FLAG.

Related Objects

  • AMS_LIST_ENTRIES — The permanent List Entry table into which staged rows are inserted.
  • AMS_LIST_HEADERS — Parent list definition referenced via LIST_HEADER_ID.
  • AMS_LIST_SELECT_ACTIONS — Referenced via LIST_SELECT_ACTION_ID.
  • FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID.
  • AMS_LIST_SELECT_CRITERIA and related AMS list configuration tables that drive the generation process.