Search Results update_pack_serial_lots




Overview
Explore in AI Chat

Overview

CSP_PACK_SERIAL_LOTS_PUB is a public PL/SQL API package owned by the APPS schema in Oracle E-Business Suite. It belongs to the CSP (Channel/Spares Management, historically associated with the "Pack" functionality used in field service and depot repair flows) product family and is classified as a PUB (public) API, meaning its procedures are intended to be called by external programs, forms, and custom code rather than being restricted to internal package use.

The package provides the business function of managing the serial number and lot number assignments associated with pack list lines. In Oracle EBS, a pack list represents a shipment or packing document that groups inventory items for movement or delivery. Where those items are serial- or lot-controlled, the correspondence between each pack list line and its specific serial numbers or lot numbers must be recorded. CSP_PACK_SERIAL_LOTS_PUB exposes a controlled interface for creating, maintaining, retrieving, and removing that serial/lot association data. The package is declared AUTHID CURRENT_USER, so it executes with the privileges of the calling schema, relying on APPS synonyms over the underlying base tables. The header revision (115.4) dates the source to 2002, indicating a long-stable interface carried forward into EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The package publishes four documented procedures, corresponding to the four CRUD-style operations on pack list serial/lot records. Parameter lists are deliberately not reproduced here; the documented behavior of each is described below.

  • CREATE_PACK_SERIAL_LOTS — Inserts new serial number and lot number associations for one or more pack list lines. It accepts the new record attributes, applies API defaults and validation, and persists the rows to the pack list serial/lot table.
  • UPDATE_PACK_SERIAL_LOTS — Modifies existing pack list serial/lot records. This is the procedure targeted by the search term "update_pack_serial_lots" and is the standard supported entry point for changing quantity, lot number, serial number, or related attributes on an existing association.
  • DELETE_PACK_SERIAL_LOTS — Removes previously established serial/lot associations, typically when a pack list line is corrected, re-packed, or cancelled. Business rules governing deletability are enforced internally.
  • GET_PACK_SERIAL_LOTS — Retrieves pack list serial/lot records matching supplied selection criteria, returning the record set to the caller for display or downstream processing.

Tables Accessed

The underlying record structure, plsl_Rec_Type, maps directly to a single pack list serial/lot entity. Its attributes include ROW_ID, PACKLIST_SERIAL_LOT_ID, PACKLIST_LINE_ID, ORGANIZATION_ID, INVENTORY_ITEM_ID, QUANTITY, LOT_NUMBER, and SERIAL_NUMBER, together with the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN). These attributes confirm that the package reads and writes the pack list serial/lot table (via its APPS synonym) and references the parent pack list line, inventory organization, and inventory item identifiers. LOT_NUMBER and SERIAL_NUMBER are modelled as VARCHAR2(240), consistent with inventory-level lot and serial definitions. The API also relies on FND_API shared components for the G_MISS sentinel values used to indicate "attribute not supplied."

Usage Notes

CSP_PACK_SERIAL_LOTS_PUB is invoked whenever serial or lot detail must be attached to or changed on pack lists. Typical callers are the CSP pack list maintenance forms, which bind the update and delete procedures to user actions on pack list lines, and related server-side logic within the CSP modules. The package is also documented as being referenced by one other package, indicating internal reuse within the same product family. The presence of G_DEFAULT_NUM_REC_FETCH (30) further indicates that GET operations are designed for paged retrieval, with callers fetching result sets in batches of thirty records per call. Custom integrations and extensions should call these procedures rather than performing direct DML on the underlying table, since the API encapsulates validation, WHO column maintenance, and the required interaction with inventory item, organization, and pack list line data.