Search Results picklist_status_name

Overview

APPS.CSP_PICKLIST_HEADERS_V is a supplementary Oracle EBS view registered against the CSP (Warehouse Management / picklist) product family. In ETRM it is catalogued as View Type "A supplementary view used to simplify forms coding," which is the defining characteristic of this object: it exists primarily to support the Oracle Forms-based picklist confirmation and maintenance screens rather than to serve as a general-purpose reporting interface. Oracle's own documentation includes the explicit warning that the view should not be queried or altered directly for data modification, and that its definition may change substantially in subsequent minor or major releases, since it is not part of the published, frozen integration surface.

The view presents one row per picklist header within an inventory organization, together with the standard WHO audit columns, descriptive flexfield (DFF) segments, and the identifying attributes of the picklist. A notable feature is that it is not a purely table-derived projection: its documented base objects include a package and a lookup view, which means some column values are resolved at runtime rather than read directly from the underlying headers table. For a user searching on the term "picklist_status_name," this is the key point — the view is known to surface a decoded, user-facing status name alongside the raw internal status code, so a query against this view can return a readable status string without the caller having to join to FND_LOOKUPS manually.

Underlying Base Objects

The documented base objects for CSP_PICKLIST_HEADERS_V are:

• CSP_PICKLIST_HEADERS (referenced as a SYNONYM) — the primary driving table. It supplies the picklist header identifier, organization, picklist number, status code, creation and confirmation dates, the WHO columns, and the ATTRIBUTE1 through ATTRIBUTE15 DFF segments.
• FND_GLOBAL (PACKAGE) — used to resolve environment/session context, most commonly the organization identifier via FND_GLOBAL.ORG_ID, which binds the view to the current inventory organization.
• FND_LOOKUPS (VIEW) — used to decode the stored picklist status code into its display name. This is the source of the status description that appears in the "picklist_status_name" style column.

The dependency on FND_GLOBAL and FND_LOOKUPS is why the view is described as supplementary rather than a thin wrapper: results are partially session-dependent and partially lookup-dependent. Reports that assume a stable, self-contained dataset should therefore treat the view with caution and prefer the base table plus an explicit lookup join if a fixed contract is required.

Key Columns

The column list begins with ROW_ID (ROWID), a row identifier, and PICKLIST_HEADER_ID (NUMBER), the primary key of the picklist header. Standard WHO columns follow: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.

Operational columns include:

• ORGANIZATION_ID — inventory organization the picklist belongs to.
• PICKLIST_NUMBER — VARCHAR2(30), the externally visible picklist number.
• PICKLIST_STATUS — VARCHAR2(30), the internal status code stored on the header record.
• DATE_CREATED and DATE_CONFIRMED — the picklist creation timestamp and the timestamp at which the picklist was confirmed.
• ATTRIBUTE_CATEGORY — the DFF structure defining column, VARCHAR2(30).
• ATTRIBUTE1 through ATTRIBUTE15 — VARCHAR2(240) descriptive flexfield segment columns.

The status decoding derived from FND_LOOKUPS is the column most relevant to a "picklist_status_name" search: it converts PICKLIST_STATUS into the meaningful label displayed to users. Because lookup meanings can be customized per installation, the displayed name should be treated as configuration-dependent.

Common Use Cases and Queries

Typical usage centres on operational reporting: listing open or confirmed picklists for an organization, reconciling picklist numbers against shipping or order data, and extracting DFF attributes for downstream integration. Note that because the view is not Oracle-recommended for direct query, production interfaces should generally read CSP_PICKLIST_HEADERS and join FND_LOOKUPS explicitly.

A representative query:

• SELECT picklist_header_id, organization_id, picklist_number, picklist_status, date_created, date_confirmed FROM apps.csp_picklist_headers_v WHERE organization_id = :org_id AND date_created >= :from_date ORDER BY picklist_number;

For a decoded status view in the base-table form: SELECT h.picklist_number, fl.meaning AS picklist_status_name, h.date_created FROM csp_picklist_headers h, fnd_lookups fl WHERE fl.lookup_type = 'PICKLIST_STATUS' AND fl.lookup_code = h.picklist_status AND h.organization_id = :org_id;

Restrict the query to a single organization via FND_GLOBAL.ORG_ID or an explicit bind to avoid cross-organization results, and treat attribute columns as site-specific extensions that require validation before use in integrations.