Search Results validate_picklist_number

Overview

APPS.CSP_PICKLIST_HEADER_PVT is a private PL/SQL API package within the Oracle E-Business Suite Order Management (OM) / Shipping Execution (WSH) module family. It encapsulates the core business logic for manipulating picklist headers — the records that identify a group of ordered items selected for picking within a warehouse. The package is declared with AUTHID CURRENT_USER, meaning that it executes with the privileges of the calling schema rather than the definer, an important consideration for security and privilege propagation in the EBS environment.

The package provides a self-contained transactional interface for creating, updating, deleting, and validating picklist header records. Its private (PVT) classification indicates that it is intended for internal consumption by other Oracle application code — typically public wrapper packages, concurrent programs, or shipping forms — rather than being invoked directly by customer extensions. A companion public package, such as CSP_PICKLIST_HEADER_PUB, typically fronts this private layer to expose a stable, documented interface.

The package header carries a historical revision marker ($Header: cspvtphs.pls 115.8 2003/05/02), confirming that the code base traces back to the pre-11i era and has been maintained across the 12.1.x and 12.2.x release families.

Key Procedures and Functions

The package exposes eleven documented subprograms, all centered on the lifecycle of a picklist header: identification, null-ID or invalid-reference validation, picklist number uniqueness, picklist status values, and date consistency. The major groups are:

• CREATE_PICKLIST_HEADER — Inserts a new picklist header record using the attribute values supplied by the caller (typically via the PICK_HEADER_REC_TYPE record).
• UPDATE_PICKLIST_HEADER — Modifies an existing picklist header, generally used to advance the picklist status or stamp confirmation information.
• DELETE_PICKLIST_HEADER — Removes a picklist header, subject to the application's referential and status constraints.
• VALIDATE_PICKLIST_HEADER_ID — Confirms that the supplied picklist_header_id is non-null and corresponds to an existing row; this is the routine most often referenced by callers who encounter the search term "validate_picklist_header_id."
• VALIDATE_ORGANIZATION_ID — Verifies that the operating unit / inventory organization is valid and accessible to the calling session.
• VALIDATE_PICKLIST_NUMBER — Ensures the picklist number is present and conforms to the expected format and uniqueness rules.
• VALIDATE_PICKLIST_STATUS — Checks that the status code is a recognized value in the picklist status lookup.
• VALIDATE_DATE_CREATED and VALIDATE_DATE_CONFIRMED — Enforce temporal consistency between the creation and confirmation dates.
• VALIDATE_PICK_HEADER_REC — Performs record-level validation across all fields of PICK_HEADER_REC_TYPE before DML is attempted.
• VALIDATE_PICKLIST_HEADER — The master validation routine that orchestrates the individual field checks.

Each procedure typically raises the standard FND_API exceptions (e.g., FND_API.G_EXC_ERROR) and returns a Boolean or error-message table depending on the declared signature.

Tables Accessed

The package operates against the CSP_PICKLIST_HEADERS entity (exposed through an APPS synonym), with the corresponding primary key column PICKLIST_HEADER_ID. Each column referenced in the PICK_HEADER_REC_TYPE record — including ORGANIZATION_ID, PICKLIST_NUMBER, PICKLIST_STATUS, DATE_CREATED, DATE_CONFIRMED, and the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) plus fifteen ATTRIBUTE / ATTRIBUTE_CATEGORY descriptive flexfield columns — maps one-to-one to columns in that underlying table. Validation procedures issue SELECT statements against the same table (and likely the picking organization / inventory organization views) to confirm that referenced IDs exist before any INSERT, UPDATE, or DELETE is committed.

Usage Notes

CSP_PICKLIST_HEADER_PVT is normally invoked indirectly: by the Shipping Transactions forms, by picklist confirmation concurrent programs, or by the public CSP_PICKLIST_HEADER_PUB wrapper. Only one other package in the ETRM metadata references it directly. Developers writing custom code should call the public wrapper rather than this private package, since the PVT layer's signatures are not guaranteed stable across patches. When troubleshooting "validate_picklist_header_id" errors, confirm that the ID passed has been populated by the shipping engine and that the record has not been purged or archived.