Search Results csi_extend_attrib_pool




Overview
Explore in AI Chat

Overview

APPS.XDP_PARAMETER_POOL_VL is a validation-language (VL) style database view in the Oracle E-Business Suite APPS schema. Its internal name suggests a generic parameter pool, but its defining SQL reveals a narrow, specific purpose: it exposes rows from the CSI_LOOKUPS lookup table where the lookup type equals CSI_EXTEND_ATTRIB_POOL. The view therefore presents the set of valid extension attribute pool codes used by Oracle Enterprise Asset Management (eAM) and related CSI (Customer Service/Installed Base) functionality.

The view is a classic "lookup view" pattern. It projects a subset of columns from a flex-field style lookup table and nulls out a number of unused positions to conform to a standard 17-column lookup-view signature used by Oracle Forms and OA Framework LOV (list of values) components. This makes the view usable as a key flexfield or descriptive flexfield validation source without exposing the full CSI_LOOKUPS structure.

In reporting and integration contexts, XDP_PARAMETER_POOL_VL is typically used to populate an LOV or to resolve the display meaning of a stored extension attribute pool code. Because it is a view, it cannot be updated directly through standard DML; changes are made to the underlying CSI_LOOKUPS table.

Underlying Base Objects

The view is defined over a single documented base object: CSI_LOOKUPS (VIEW). CSI_LOOKUPS is the lookup repository for the CSI product family. Although CSI_LOOKUPS itself is documented as a view, it behaves as the effective base source for XDP_PARAMETER_POOL_VL, and the joined condition binds the two objects tightly.

The relationship is one-to-many at the table level: CSI_LOOKUPS contains many lookup types, while XDP_PARAMETER_POOL_VL filters to exactly one type, 'CSI_EXTEND_ATTRIB_POOL'. Every row returned by the view corresponds to one row of CSI_LOOKUPS with that lookup type. No join, union, or aggregation is applied; the view is a simple filtered projection.

Key Columns

  • ROW_ID — the ROWID of the underlying CSI_LOOKUPS row; used internally for row identification and Forms/ADF navigation.
  • LOOKUP_CODE — the coded value of the extension attribute pool; this is the value stored in referencing tables.
  • MEANING — the user-facing description of the pool code, displayed in LOVs and reports.
  • ENABLED_FLAG — indicates whether the lookup is currently active; queries generally filter to 'Y'.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — define the date range during which the pool code is valid.
  • NULL placeholders — numerous unused columns that exist only to satisfy the standard lookup view column layout.

Common Use Cases and Queries

The most common use is populating a validation list of available extension attribute pools, often filtered by enabled flag and effective dates:

SELECT lookup_code, meaning
FROM   apps.xdp_parameter_pool_vl
WHERE  enabled_flag = 'Y'
AND    TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE)
                          AND NVL(end_date_active, SYSDATE);

A second scenario resolves the meaning for a stored code, typically joined to an extension attribute table:

SELECT p.lookup_code, p.meaning
FROM   apps.xdp_parameter_pool_vl p
WHERE  p.lookup_code = :pool_code;

Because the view is defined on CSI_LOOKUPS, administrators maintain the pool values by inserting, updating, or disabling rows in CSI_LOOKUPS where LOOKUP_TYPE = 'CSI_EXTEND_ATTRIB_POOL'. Reports and integrations should treat the view as read-only reference data, and should always honor ENABLED_FLAG and the active-date columns to avoid presenting retired pool codes.