Results for “as_assigned_list_entries_v”

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

Overview

The AS_ASSIGNED_LIST_ENTRIES_V view is a Sales Foundation (AS) reporting and integration object within Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the entries assigned to marketing and sales lists, joining each list entry to its parent list definition so that consumers can retrieve both the assignment-level attributes and the descriptive attributes of the owning list in a single query. The view is a denormalized read layer intended for operational reporting, list cleansing, telemarketing, campaign execution, and outbound data extracts. Because it presents list membership data with customer, contact, address, and phone detail already joined, it is commonly used as the source for list-entry exports, direct-mail file generation, and integration feeds to external marketing automation platforms.

The ETRM documentation describes the view as the "Assigned list entries view" under the AS – Sales Foundation product. It is listed as not implemented in the reference database, meaning the object exists in the released AS schema but may not be present or populated in every environment, depending on installed modules and patch level.

Underlying Base Objects

ETRM does not document referenced base objects for this view. The embedded view text clearly shows the principal base tables: AS_LIST_ENTRIES (aliased LE), which stores the individual assigned list entries, and AS_LISTS (aliased AL), which stores the list header containing NAME, PUBLIC_FLAG, ENABLED_FLAG, and TYPE. A third alias, LU, supplies a ROWID used as ROW_ID, consistent with a union or lookup construct over list usage. Additional joins resolve descriptive lookups: a territory table (TERR1) supplies TERRITORY_SHORT_NAME as COUNTRY, and flex/lookup values (LOOK1–LOOK4) resolve job title, department, and language meanings.

Key Columns

• LIST_ENTRY_ID, LIST_ID, LIST_NAME — the entry identifier and its owning list. PUBLIC_FLAG, ENABLED_FLAG, and LIST_TYPE describe list accessibility and category.
• CUSTOMER_ID, ADDRESS_ID, CONTACT_ID, PHONE_ID, LEAD_ID, LETTER_ID, EVENT_ID, PICKING_HEADER_ID, BATCH_ID — foreign keys identifying the assigned entity or source activity.
• COMPANY_NAME, ADDRESS1–ADDRESS4, CITY, STATE, PROVINCE, , COUNTRY_CODE, COUNTRY — mailing address attributes, with USE_PVT_MAILING_ADDRESS indicating whether a private mailing address applies.
• FIRST_NAME, LAST_NAME, TITLE_CODE, JOB_TITLE_CODE, JOB_TITLE, JOB_TITLE_MEANING, MAIL_STOP, EMAIL_ADDRESS, PHONE_TYPE_CODE, AREA_CODE, PHONE_NUMBER, FULL_NUMBER, EXTENSION, CONTACT_SUFFIX — contact and telephony detail.
• MARKED_FLAG, TRANSFER_FLAG, TRANSFER_STATUS — assignment state used by list management and transfer processing.
• NUM_OF_EMPLOYEES, PARENT_CUSTOMER_ID, PARENT_COMPANY_NAME, POTENTIAL_REVENUE_CURR_FY, POTENTIAL_REVENUE_NEXT_FY, FISCAL_YEAREND_MONTH, ANALYSIS_FY, MISSION_STATEMENT, TAX_REFERENCE, NET_WORTH, YEAR_ESTABLISHED — firmographic and financial profiling fields.
• DEPARTMENT_CODE, DEPARTMENT_MEANING, DEPARTMENT, RANK, MANAGED_BY, MANAGER_FIRST_NAME, MANAGER_LAST_NAME — organizational attributes.
• NATIVE_LANGUAGE, OTHER_LANGUAGE_1, OTHER_LANGUAGE_2 and their _MEANING columns — language and localization attributes.
• CUSTOMER_ORIG_SYSTEM_REFERENCE, ADDRESS_ORIG_SYSTEM_REFERENCE, CONTACT_ORIG_SYSTEM_REFERENCE — cross-system keys for integration.

Common Use Cases and Queries

The view supports list membership reporting, deduplication, list transfer extraction, and direct-marketing output. A typical query retrieves all enabled entries for a named list:

• SELECT list_entry_id, list_name, customer_id, last_name, company_name, email_address FROM as_assigned_list_entries_v WHERE list_id = :p_list_id AND marked_flag = 'Y';
• Exporting contact detail for mailing: SELECT last_name, first_name, company_name, address1, city, state, postal_code, country FROM as_assigned_list_entries_v WHERE list_id = :p_list_id AND enabled_flag = 'Y';
• Identifying originated records: SELECT customer_orig_system_reference, address_orig_system_reference FROM as_assigned_list_entries_v WHERE list_type = 'CUSTOMER';

The user search term user_defined5 does not appear in the documented view text, which exposes no user-defined (DDF) attribute columns. Where descriptor flexibility is required, the DFF context columns reside on the underlying AS_LIST_ENTRIES table rather than this view; consumers needing user_defined5 must query the base table or a DFF-specific view directly.