Results for “as_list_entries_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AS_LIST_ENTRIES_V is a Sales Foundation (AS) view in Oracle E-Business Suite 12.1.1 and 12.2.2 that exposes the individual entries belonging to a list. In the ETRM data model, a "list" is a container used primarily by the Sales and TeleSales modules to hold sets of customers, addresses, contacts, phones, leads, persons, and related entities. This view presents those list members together with the descriptive attributes required to render them in an application UI or a report.

The view is read-only by design. Because it is defined over the base list table via a ROWID-based select (LIST.ROWID ROW_ID), it is a non-key-preserving, non-updatable view. All inserts, updates, and deletes that populate it are performed against the underlying table by the Sales Foundation APIs, not through the view. The view is marked "Not implemented in this database" in the ETRM excerpt, meaning the row was not physically present in the source database used for documentation and its object owner and dependency list were not captured. Its behavior can therefore be inferred only from the embedded view text, which is fully documented.

Underlying Base Objects

The documented metadata lists no referenced base objects, and the DBA-level dependency information was not captured for this version. The view text does, however, resolve to two clear external references beyond the primary list table (aliased LIST):

• LOOK1 — a lookup source joined to return LOOK1.MEANING as the TITLE column, resolving LIST.TITLE_CODE.
• JOBS — a job-definition source joined to return JOBS.MEANING, resolving LIST.JOB_TITLE_CODE.

These are the only joins visible in the view text; all other columns are projected straight from the base list entry table. Absent a documented physical object list, the view should be treated as an AS-owned convenience layer whose underlying table is the primary list-entry table — likely AS_LIST_ENTRIES or its equivalent.

Key Columns

The view exposes several groups of columns relevant to Sales Foundation processing:

• Identity and ownership: ROW_ID, LIST_ENTRY_ID, LIST_ID, and LIST_SOURCE identify the entry, its parent list, and the origin of that list.
• Audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE support change tracking and concurrent-program lineage.
• Entity foreign keys: CUSTOMER_ID, ADDRESS_ID, CONTACT_ID, PHONE_ID, LEAD_ID, PERSON_ID, PERSON_USER_ID, LETTER_ID, EVENT_ID, PICKING_HEADER_ID, and BATCH_ID allow a single list to span multiple object types.
• Transfer control: TRANSFER_FLAG and TRANSFER_STATUS — the columns most relevant to the transfer_flag search term — govern whether an entry has been transferred to its target destination and the state of that transfer.
• Presentation and denormalized data: COMPANY_NAME, address lines, CITY, STATE, PROVINCE, POSTAL_CODE, COUNTRY_CODE, FIRST_NAME, LAST_NAME, TITLE (lookup meaning), JOB_TITLE, EMAIL_ADDRESS, and PHONE_NUMBER support direct display without joins.
• Flexible attributes: ATTRIBUTE_CATEGORY plus ATTRIBUTE1 through ATTRIBUTE25.

Common Use Cases and Queries

The most frequent use of this view is verifying which list entries are pending, in progress, or complete with respect to transfer, and reporting on list membership by entity type.

SELECT LIST_ID,
       LIST_ENTRY_ID,
       TRANSFER_FLAG,
       TRANSFER_STATUS,
       CREATION_DATE
FROM   APPS.AS_LIST_ENTRIES_V
WHERE  TRANSFER_FLAG = 'Y'
  AND  TRANSFER_STATUS = 'PENDING'
ORDER BY CREATION_DATE DESC;

Because the view is not key-preserving, it can be queried but not modified. To inspect the parties and addresses on a list, use:

SELECT LIST_ENTRY_ID, COMPANY_NAME, FIRST_NAME, LAST_NAME, CITY, TITLE, JOB_TITLE
FROM   APPS.AS_LIST_ENTRIES_V
WHERE  LIST_ID = :list_id
ORDER BY LAST_NAME, FIRST_NAME;

Always apply WHERE predicates and confirm that the base object exists in the target environment before relying on the view, since the ETRM excerpt flags it as not implemented in the documented database.