Results for “list_priority_id”

16 results




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

Overview

AS_LISTS is an Oracle E-Business Suite (EBS) view owned by the APPS schema and associated with the AS – Sales Foundation product. It exposes list definitions used within Oracle Sales and related modules, and is documented as a multi-org construct, meaning records are filtered by the operating unit (ORG_ID) in which the user session is active. In EBS 12.1.1 and 12.2.2, the object carries a status of VALID in the ETRM repository.

Its principal reporting and integration role is to present only the list rows visible to the current organization by translating the multi-org security stored on the underlying table. Report writers, concurrent programs, and integrations query AS_LISTS rather than the base table so that organization-level security is applied consistently without writing the ORG_ID predicate manually. The view is read-only with respect to application data and is generally consumed through Oracle Reports, BI Publisher, OAF pages, and custom SQL.

Underlying Base Objects

The documented definition references a single base object: the synonym AS_LISTS_ALL, which resolves to the multi-org table holding every list row across all organizations. The view text selects all business and descriptive columns from AS_LISTS_ALL and appends a WHERE clause that restricts rows by organization.

The organization predicate is derived from USERENV('CLIENT_INFO'), from which the first ten characters are interpreted as the current ORG_ID. When the first character is blank, the decode returns NULL, and NVL substitutes -99, causing the comparison to match rows with a NULL ORG_ID (shared or global rows) alongside the active organization. This mechanism is the standard EBS multi-org view pattern and explains why AS_LISTS can return both organization-specific and cross-organization list records.

Key Columns

Common Use Cases and Queries

Typical scenarios include validating which lists are visible to the current operating unit, identifying public versus private lists, and auditing list ownership. The PUBLIC_FLAG column is frequently used to separate globally shared lists from user-specific ones, while ENABLED_FLAG filters inactive definitions.

Query active public lists:

SELECT list_id, name, type, public_flag, org_id
FROM   apps.as_lists
WHERE  enabled_flag = 'Y'
AND    public_flag  = 'Y';

Query lists by owner with organization context:

SELECT l.list_id, l.name, l.owner_person_id, l.org_id
FROM   apps.as_lists l
WHERE  l.owner_person_id = :p_person_id;

Query with a forced organization context for reporting across a specific operating unit:

SELECT list_id, name, public_flag
FROM   apps.as_lists
WHERE  org_id = :p_org_id
OR     org_id IS NULL;

Because the view applies organization security automatically, the explicit ORG_ID predicate is generally unnecessary when CLIENT_INFO is already initialized. When running outside the standard EBS session context, initialization via FND_GLOBAL.INITIALIZE ensures the CLIENT_INFO value is set so that AS_LISTS returns the correct organization-scoped rows.