Results for “as_lists_v”

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

Overview

AS_LISTS_V is a Sales Foundation (AS) reporting and inquiry view that consolidates header-level attributes of customer and contact list definitions stored in Oracle E-Business Suite. In the Oracle EBS 12.1.1 and 12.2.2 data models, lists are used by Oracle Sales, TeleSales, and Marketing to group parties, contacts, and prospects for targeted campaigns, territory assignments, and call-list generation. The view flattens the parent list record together with supporting lookups and person names so that forms, concurrent programs, and ad hoc reports can retrieve a complete, human-readable list definition without writing multi-table joins.

The view is documented as not implemented in the base database delivered by ETRM, which indicates it is supplied as a seeded object that is activated only when the relevant AS product features are licensed and installed. Its primary consumers are the list management and list assignment screens and the associated reporting components that display list ownership, priority, and enablement status.

Underlying Base Objects

AS_LISTS_V is defined over six referenced objects:

• AS_LISTS L — the driving base table holding list header records (name, type, ownership, enablement, DFF attributes).
• AS_LIST_RULES RULE1 — joined on LIST_RULE_ID to supply the list's primary rule name.
• AS_LIST_RULES RULE2 — joined on LIST_PRIORITY_ID to supply the priority rule name.
• AS_LOOKUPS ASLKP1 — supplies the meaning of the list TYPE via LOOKUP_TYPE = 'LIST_TYPE'.
• PER_EMPLOYEES_CURRENT_X PER1 — resolves the owner person's first and last name.
• PER_EMPLOYEES_CURRENT_X PER2 — resolves the assignee person's first and last name.

All joins to the lookups, rules, and person views are outer joins, so a list row is returned even when its type is not defined in AS_LOOKUPS or when rule or person references are null.

Key Columns

• LIST_ID, NAME, TYPE, TYPE_MEANING — the list identifier, its display name, the coded type, and the decoded meaning.
• LIST_RULE_ID / RULE_NAME and LIST_PRIORITY_ID / PRIORITY_NAME — the rule and priority rule governing list membership and ordering.
• ENABLED_FLAG, PUBLIC_FLAG, LIST_ONLINE_FLAG, LIST_ONLINE — status indicators; LIST_ONLINE is a derived DECODE that renders '*' when the list is online.
• OWNER_PERSON_ID / OWNER_FIRST_NAME / OWNER_LAST_NAME and ASSIGN_PERSON_ID — list ownership and assignment.
• LIST_SOURCE and ATTRIBUTE_CATEGORY through ATTRIBUTE15 — origin and descriptive flexfield context.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view supports list inventory reports, ownership audits, and rule-to-list cross-reference queries.

• List all enabled public lists: SELECT LIST_ID, NAME, TYPE_MEANING FROM AS_LISTS_V WHERE ENABLED_FLAG='Y' AND PUBLIC_FLAG='Y';
• List ownership report: SELECT LIST_ID, NAME, OWNER_FIRST_NAME, OWNER_LAST_NAME FROM AS_LISTS_V ORDER BY OWNER_LAST_NAME;
• Rules usage: SELECT LIST_ID, NAME, RULE_NAME, PRIORITY_NAME FROM AS_LISTS_V WHERE RULE_NAME IS NOT NULL;

As the view performs no aggregation, filtering, or security predicate of its own, callers should still apply operating unit and security context through the calling form or report logic. Because AS_LISTS_V references PER_EMPLOYEES_CURRENT_X, its results reflect only current employee-person records, so historical owners no longer in that view will not be resolved.