Search Results list_items

Overview

PA_DIST_LIST_ITEMS is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that defines the list of recipients authorized to access a particular distribution list object. Each row associates a recipient — which may be an application role, a project team member, or a literal e-mail address — with a parent distribution list, and optionally scopes that recipient's access further through an access level and a menu reference. The table therefore acts as the access-control detail for distribution lists used in project collaboration, notification, and document-sharing flows.

From a dimensional modeling perspective, the FK structure is satellite-leaning: the table carries descriptive recipient and access attributes that are functionally dependent on a parent distribution list key rather than introducing new business entities of its own. It is best treated as a dependent satellite hanging off the distribution list hub, with MENU_ID as a secondary reference into the FND_MENUS lookup.

Key Information Stored

The documented physical schema contains 13 columns. The most significant are:

• LIST_ITEM_ID — surrogate primary key, enforced by unique index PA_DIST_LIST_ITEM_U1.
• LIST_ID — foreign key to the parent distribution list header; the anchor of the satellite relationship.
• RECIPIENT_TYPE and RECIPIENT_ID — together with LIST_ID they form the second unique business key (PA_DIST_LIST_ITEM_U2), identifying the recipient and its nature (role, team member, and so on).
• ACCESS_LEVEL — the privilege granted to the recipient for the referenced object.
• MENU_ID — foreign key to FND_MENUS, allowing recipient access to be tied to a menu definition.
• EMAIL — literal e-mail address used when the recipient is not an EBS user or role.
• RECORD_VERSION_NUMBER — optimistic locking / concurrency control column.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO-column audit trail.

The two unique indexes clearly separate the artificial primary key (LIST_ITEM_ID) from the natural business key (LIST_ID, RECIPIENT_TYPE, RECIPIENT_ID).

Common Use Cases and Queries

Typical scenarios include reporting on who can access a given distribution list, resolving recipients for notification or workflow mail-outs, and auditing access changes over time.

• Recipients of a specific list: SELECT RECIPIENT_TYPE, RECIPIENT_ID, EMAIL, ACCESS_LEVEL FROM PA.PA_DIST_LIST_ITEMS WHERE LIST_ID = :list_id;
• All distinct recipients across lists: SELECT DISTINCT RECIPIENT_TYPE, RECIPIENT_ID FROM PA.PA_DIST_LIST_ITEMS;
• Recipients scoped by menu: join to FND_MENUS on MENU_ID to resolve menu names.
• Recently modified access rows: filter on LAST_UPDATE_DATE between a date range for change audits.
• E-mail-only recipients: WHERE EMAIL IS NOT NULL AND RECIPIENT_ID IS NULL (for external distribution).

Related Objects

The following objects are most significant in relation to PA_DIST_LIST_ITEMS:

• FND_MENUS — referenced via MENU_ID; the only documented foreign key.
• PA_DIST_LISTS (parent header implied by LIST_ID) — the distribution list each item belongs to.
• PA_PROJECT_TEAM_MEMBERS — source of RECIPIENT_ID when the recipient is a team member.
• FND_USER and FND_ROLES — resolve role-based RECIPIENT_ID values.
• PA_PARTY_* / PER_ALL_PEOPLE_F — resolve personnel recipients and e-mail addresses.
• PA_DIST_LIST_ITEMS public APIs / PL/SQL packages in the PA schema that maintain recipient rows programmatically.

Joins typically flow from LIST_ITEM_ID (PK) outward to FND_MENUS via MENU_ID, and from LIST_ID upward to the distribution list header.