Results for “por_favorite_list_headers”

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

Overview

The POR_FAVORITE_LIST_HEADERS table resides in the ICX schema and belongs to the Oracle iProcurement product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as the headers table for implementing favorite lists — user-defined groupings of frequently ordered catalog items, internal requisitions, or other purchasable entities rendered on the iProcurement shop page. Each row represents a single favorite list owned by a specific employee, capturing both the display name and the description shown to that user.

The ETRM record documents an object of type TABLE with status VALID, reflecting a stable, long-lived structure. The physical schema is documented with 27 columns. Heuristic Data Vault classification derived from the foreign-key structure designates this object as standalone; from a modeling perspective, it behaves most like a hub or master entity, since it defines the identity of a favorite list and is referenced by downstream detail tables rather than aggregating transactions from them. This classification is a modeling suggestion, not an Oracle-imposed constraint.

Key Information Stored

The table is keyed by the composite primary key POR_FAV_LIST_HEADERS_PK1, comprising FAVORITE_LIST_ID and EMPLOYEE_ID. A separate unique index, POR_FAVORITE_LIST_HEADERS_U1, covers EMPLOYEE_ID and FAVORITE_LIST_ID, confirming the same pair as the business-key candidate. The most consequential columns include:

• FAVORITE_LIST_ID — the list identifier; part of the primary key and the column users most often search on.
• EMPLOYEE_ID — the owning employee; the second half of the primary key, enforcing per-user ownership.
• FAVORITE_LIST_NAME — the user-visible label for the list.
• DESCRIPTION — free-text description of the list's purpose.
• PRIMARY_FLAG — indicates the default/preferred list for that employee.
• INACTIVE_DATE — soft-disable timestamp, allowing lists to be retired without deletion.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns maintained by the framework.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF (descriptive flexfield) columns for client-specific extensions.

Note that FAVORITE_LIST_ID is ambiguous between the surrogate key and business key; in practice it is the surrogate identifier, while the (EMPLOYEE_ID, FAVORITE_LIST_ID) pair forms the business key.

Common Use Cases and Queries

Typical reporting and support scenarios include listing all favorite lists for a user, identifying the default list, and auditing creation and modification activity. Because FAVORITE_LIST_ID is exposed and searched, a common retrieval is:

• Lists for an employee: SELECT favorite_list_id, favorite_list_name, primary_flag FROM icx.por_favorite_list_headers WHERE employee_id = :emp_id;
• Lookup by list ID: SELECT * FROM icx.por_favorite_list_headers WHERE favorite_list_id = :list_id;
• Default list resolution: filter on PRIMARY_FLAG = 'Y' for the employee.
• Active lists only: add AND inactive_date IS NULL to exclude retired lists.
• Audit reporting: group by created_by or order by last_update_date.

Related Objects

The documented relationship data classifies this object as standalone, so no enforced foreign keys are recorded within ETRM. The most significant logically related objects are:

• POR_FAVORITE_LIST_ITEMS — the detail (lines) table, joined on FAVORITE_LIST_ID.
• PER_ALL_PEOPLE_F — employee master, joined on EMPLOYEE_ID to resolve the owner.
• FND_USER — application user context for the employee.
• ICX_POR_... catalog tables — items referenced by favorite list detail rows.
• POR_REQUISITION_HEADERS_ALL — requisitions sourced from favorite-list selections.

These joins rest on FAVORITE_LIST_ID and EMPLOYEE_ID, the two defining columns of this object.