Search Results csp_pick_serial_lots_pub




Overview
Explore in AI Chat

Overview

APPS.CSP_PICK_SERIAL_LOTS_PUB is a public PL/SQL API package in Oracle EBS that manages the association between picklist lines and the serial numbers and lot numbers consumed during pick confirmation. It belongs to the CSP (Costing, and specifically the picking/shipping serial and lot capture) module and exposes a set of published, AUTHID CURRENT_USER procedures intended for external invocation from forms, concurrent programs, and custom code. The package header (version 120.1) declares the record type psl_Rec_Type and the associated table type psl_Tbl_Type, both of which model the CSP_PICK_SERIAL_LOTS entity. The record carries ROW_ID, PICKLIST_SERIAL_LOT_ID, the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN), PICKLIST_LINE_ID, ORGANIZATION_ID, INVENTORY_ITEM_ID, QUANTITY, LOT_NUMBER, and SERIAL_NUMBER. Default attribute initialization uses the FND_API.G_MISS_* sentinels, and the package exposes the standard global defaults G_MISS_psl_REC and G_MISS_psl_TBL together with G_DEFAULT_NUM_REC_FETCH (initialised to 30). This design follows the Oracle Application Object Library (AOL) API conventions, signalling full compatibility with the standard EBS error-handling and message-stack patterns.

Key Procedures and Functions

  • CREATE_PICK_SERIAL_LOTS — Inserts new pick serial/lot assignment records. Typical use is during pick confirmation, when a user or process records the specific serial numbers or lot numbers that satisfy a picklist line.
  • UPDATE_PICK_SERIAL_LOTS — Modifies existing pick serial/lot assignments, for example correcting a quantity or changing an assigned serial number after the initial confirmation.
  • DELETE_PICK_SERIAL_LOTS — Removes pick serial/lot assignment records. The user search term "delete_pick_serial_lots" maps directly to this procedure. It is the entry point used to undo or reverse a previously created pick serial/lot relationship, and is subject to the package's standard validation and error reporting.
  • GET_PICK_SERIAL_LOTS — Retrieves pick serial/lot assignment information. It supports the record and table structures defined in the package header and is suitable for querying existing assignments without modifying data. The G_DEFAULT_NUM_REC_FETCH constant controls the default fetch batch size (30).

Tables Accessed

The package operates on the CSP_PICK_SERIAL_LOTS table (accessed through its APPS synonym), which stores one row per picklist line/serial/lot combination. The columns mirror the psl_Rec_Type record: the primary key PICKLIST_SERIAL_LOT_ID, the foreign key PICKLIST_LINE_ID linking to the picklist line, ORGANIZATION_ID and INVENTORY_ITEM_ID identifying the item context, QUANTITY, LOT_NUMBER, SERIAL_NUMBER, and the WHO audit columns. The create, update, and delete procedures write to this table, while GET_PICK_SERIAL_LOTS reads from it. Because the metadata does not enumerate additional referenced tables via APPS synonyms, callers should assume the package also relies on standard EBS validation lookups (for example item and organization validation) as part of its internal processing.

Usage Notes

CSP_PICK_SERIAL_LOTS_PUB is a published API and is referenced by one other package within the EBS codebase, indicating it is called both directly from the shipping/picking UI and via dependent program units. The delete_pick_serial_lots procedure is normally invoked when a pick confirmation is reversed, a picklist line is cancelled, or data must be corrected. Invocations should follow the standard EBS API pattern: initialise the error handler, pass the record or table structures defined in the header, provide the standard p_init_msg_list, x_return_status, and x_msg_count/x_msg_data parameters, and inspect the returned status before committing. Because the package is declared AUTHID CURRENT_USER, it executes with the caller's privileges, and custom code should connect as APPS or use the appropriate synonym grants. Direct DML against the underlying table should be avoided; all inserts, updates, and deletes should be routed through this API to preserve validation and audit integrity. Note that the header dates from 2006 (120.1) and is marked "noship"; in both 12.1.1 and 12.2.2 the public interface remains the four documented procedures.