Results for “as_lists_all”

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

Overview

AS_LISTS_ALL is a Sales Foundation (AS) table owned by the OSM schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It defines market and campaign lists used to segment trading partners, customers, or prospects for targeted selling and marketing activity. In practice, a list is a named collection of parties that qualifies for a specific marketing initiative, campaign, or market assignment, and downstream Sales and Trade Management processes (list assignment, list rules, and territory or market handling) reference the list to determine which parties are included.

The table carries the standard EBS 11 columns of who-audit and program context (for example, LIST_ID, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE) alongside its functional columns. Its heuristic Data Vault classification, as mined from the foreign-key structure, is standalone. This should be read as a modeling suggestion only: AS_LISTS_ALL behaves as a standalone hub-like entity for the list business key, without documented dependent links or satellites within the ETRM model. Where a warehouse model is required, treat AS_LISTS_ALL as the list dimension/hub and derive any satellite attributes from the same physical table.

Key Information Stored

The surrogate primary key is LIST_ID, enforced by the AS_LISTS_PK constraint. Two unique indexes provide business-key candidates: AS_LISTS_U1 on LIST_ID (the single-column uniqueness guarantee) and AS_LISTS_U2 on the composite of NAME, OWNER_PERSON_ID, and ORG_ID, which asserts that a list name is unique for a given owner within a given operating unit. The most important functional columns include:

• LIST_ID — surrogate primary key; the internal identifier used by all referencing objects.
• NAME — the user-facing list name; part of the composite business key AS_LISTS_U2.
• TYPE — classifies the list (for example, market versus campaign), driving how the list is consumed.
• OWNER_PERSON_ID — the person who owns the list; part of AS_LISTS_U2.
• ASSIGN_PERSON_ID — the person to whom list membership or follow-up is assigned.
• ORG_ID — the operating unit (multi-org) that owns the list; part of AS_LISTS_U2.
• ENABLED_FLAG — indicates whether the list is active and eligible for use.
• PUBLIC_FLAG — controls whether the list is shared publicly or restricted.
• LIST_SOURCE — identifies how the list was created or sourced.
• LIST_ONLINE_FLAG — indicates whether the list is available for online use.
• LIST_RULE_ID and LIST_PRIORITY_ID — reference the rule and priority definitions that govern list evaluation and ordering.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) columns for customer-specific extensions.

Common Use Cases and Queries

Typical scenarios include: displaying active lists to a sales representative, selecting lists for assignment processing, reporting on list ownership and coverage by operating unit, and auditing changes to list definitions. A basic lookup by business key follows:

• SELECT list_id, name, type, enabled_flag FROM as_lists_all WHERE name = :name AND owner_person_id = :owner AND org_id = :org_id;
• SELECT list_id, name, type FROM as_lists_all WHERE org_id = :org_id AND enabled_flag = 'Y' ORDER BY name;
• SELECT list_id, name, owner_person_id, assign_person_id FROM as_lists_all WHERE type = :list_type AND public_flag = 'Y';

For reporting, join AS_LISTS_ALL to its member/assignment tables to produce counts of parties per list, and apply ORG_ID as a mandatory predicate when running under multi-org security. Since the table contains a date-tracked audit trail but is not date-effective at the row level, change history is normally obtained from audit or DFF history rather than from the base table alone.

Related Objects

The PK/LIST_ID relationship data indicates the following significant dependencies:

• AS_LIST_RULES / list rule objects — referenced via LIST_RULE_ID; define the criteria that populate the list.
• AS_LIST_PRIORITIES — referenced via LIST_PRIORITY_ID; order list evaluation.
• AS_LIST_MEMBERS (or equivalent list membership table) — joins on LIST_ID to resolve the parties belonging to each list.
• AS_LIST_ASSIGNMENTS — joins on LIST_ID and ASSIGN_PERSON_ID to route list work.
• PER_PERSONS (or PER_ALL_PEOPLE_F) — joins OWNER_PERSON_ID and ASSIGN_PERSON_ID to person records.
• HR_OPERATING_UNITS / ORG_ORGANIZATION_DEFINITIONS — joins ORG_ID for operating-unit context.
• FND_FLEX_VALUES / FND_DESCR_FLEX_COL_USAGE — supports the ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 flexfield columns.
• AS_LISTS_VL / AS_LISTS_AL — if defined, the translated and audit views over the base table.

All PL/SQL that manipulates these lists accesses AS_LISTS_ALL through the AS_LIST public APIs and the tables above, so direct DML on AS_LISTS_ALL should be avoided in favor of supported list APIs.