Search Results validate_picklist_line_id

Overview

The APPS.CSP_PICK_SERIAL_LOTS_PVT package is a private (PVT) PL/SQL API belonging to the Oracle EBS discrete manufacturing and order fulfillment stack. It provides the programmatic foundation for managing the association between picklist lines and the specific serial numbers and lot numbers that satisfy them. In warehouses that enforce lot and serial control, a picklist line is not complete until the exact inventory instances have been identified. This package exists to record, validate, and maintain those instance-level allocations.

The package is declared with AUTHID CURRENT_USER, indicating that it executes with the privileges of the invoking schema rather than the definer, and its header originates from a 2006 source revision (cspvtsls.pls 120.1). It is classified as a private API, meaning it is not intended as a public integration surface; instead it is consumed internally by higher-level picking and shipping logic. The documented metadata indicates that two other packages reference it, confirming its role as a supporting layer beneath the pick-confirm and pick-release flows. The source excerpt defines a psl_Rec_Type record and a psl_Tbl_Type PL/SQL table, both defaulting every attribute to the FND_API.G_MISS_* sentinel values, which is the standard Oracle API convention for distinguishing "not supplied" from an explicit null.

Key Procedures and Functions

The package exposes twelve documented procedures, comprising a full CRUD and validation set over the pick serial/lot record structure.

• CREATE_PICK_SERIAL_LOTS — Inserts new picklist serial/lot association records for a given picklist line.
• UPDATE_PICK_SERIAL_LOTS — Modifies existing association records, typically to adjust quantity or corrected lot/serial values.
• DELETE_PICK_SERIAL_LOTS — Removes association records when a pick is backed out or reallocated.
• VALIDATE_PL_SERIAL_LOT_ID — Confirms the primary key of an existing association record is valid and present.
• VALIDATE_PICKLIST_LINE_ID — Confirms that a supplied picklist line identifier references a legitimate picklist line. This is the routine most commonly reached when resolving a search for validate_picklist_line_id, and it acts as a prerequisite check before any create or update operation.
• VALIDATE_ORGANIZATION_ID — Verifies the inventory organization context for the transaction.
• VALIDATE_INVENTORY_ITEM_ID — Verifies that the item being picked is a valid inventory item.
• VALIDATE_QUANTITY — Checks that the quantity assigned to the serial/lot record is positive and consistent with the line.
• VALIDATE_LOT_NUMBER — Confirms the supplied lot number exists and is valid for the item and organization.
• VALIDATE_SERIAL_NUMBER — Confirms the supplied serial number exists and is valid for the item and organization.
• VALIDATE_PSL_REC — Performs record-level validation across the assembled psl_Rec_Type structure.
• VALIDATE_PICK_SERIAL_LOTS — Orchestrates the full validation sequence in the correct order.

Tables Accessed

The documented metadata lists only DBMS_SQL and DUAL as referenced objects via APPS synonyms. DUAL is used for scalar checks such as sequence and existence probes. DBMS_SQL indicates that at least one routine builds and executes dynamic SQL, most likely for the flexible validation queries performed against the underlying picklist serial/lot table and inventory tables. Because the validation routines are designed to confirm picklist line, organization, item, lot, and serial integrity, the package will in practice read the base picklist serial/lot entity table and the inventory lots and serials tables, though these are not enumerated in the supplied metadata excerpt.

Usage Notes

Because this is a private API, it should not be called directly from custom extensions where a public alternative exists. Invocation occurs principally from the Oracle picking and shipping forms during pick confirmation, where the form collects lot and serial details against a picklist line and delegates persistence to CREATE_PICK_SERIAL_LOTS and UPDATE_PICK_SERIAL_LOTS. Concurrent programs that release or confirm picks may also call the validation routines prior to processing.

When calling any routine, the standard Oracle API convention applies: initialize the record with G_MISS_psl_REC, populate only the attributes being changed, and rely on the VALIDATE_* procedures to enforce business rules before committing. VALIDATE_PICKLIST_LINE_ID in particular should be treated as the entry gate — without a valid picklist line, none of the subordinate lot or serial validation can succeed.