Search Results validate_quantity_picked

Overview

APPS.CSP_PICKLIST_LINES_PVT is a private PL/SQL package within the Oracle E-Business Suite (EBS) that supports the picklist line functionality of the Channel Sales Portal / Field Service picklist subsystem. Picklists drive warehouse and field operations by grouping the inventory items that must be collected, staged, and issued to fulfill demand documents. The private ("PVT") API designation indicates that the package is intended for internal consumption by the application's own forms and validation layers rather than as a public integration interface. Documented metadata confirms validity in both EBS 12.1.1 and 12.2.2 under the APPS schema.

Key Procedures and Functions

The package exposes fourteen documented procedures and functions covering the full lifecycle of picklist lines and their supporting validations:

• CREATE_PICKLIST_LINES, UPDATE_PICKLIST_LINES, DELETE_PICKLIST_LINES — core DML operations that insert, modify, and remove picklist line records.
• VALIDATE_PICKLIST_LINES — a batch validation entry point for a set of picklist lines.
• VALIDATE_PICKLIST_LINE_REC — record-level validation, likely intended to validate a single line record structure before persistence.
• Key identifier validations: VALIDATE_PICKLIST_LINE_ID, VALIDATE_PICKLIST_LINE_NUMBER, VALIDATE_PICKLIST_HEADER_ID, and VALIDATE_LINE_ID confirm that the identifiers supplied by callers reference valid, existing records and establish the correct parent-child relationship between a picklist header and its lines.
• Attribute validations: VALIDATE_INVENTORY_ITEM_ID, VALIDATE_UOM_CODE, VALIDATE_REVISION, VALIDATE_QUANTITY_PICKED, and VALIDATE_TRANSACTION_TEMP_ID enforce domain integrity on the substantive attributes of a line — the item being picked, the unit of measure, the item revision, the quantity actually picked, and the temporary transaction identifier used during pick confirmation processing.

No parameter lists are reproduced here because they are not part of the documented metadata; callers should obtain formal signatures from the ETRM or from the package specification in a development environment.

Tables Accessed

The documented ETRM metadata lists no explicit table references for this package; the references section of the content excerpt records only dependencies on the PL/SQL infrastructure packages APPS.FND_API and SYS.STANDARD. Based on the package's purpose and the nature of its validations, it operates on the picklist lines and picklist header tables owned by the CSP schema (for example, the picklist lines entity implied by the package name and the header entity validated by VALIDATE_PICKLIST_HEADER_ID), together with inventory item and UOM reference data used by the validation routines. Consult the live source in the APPS schema to confirm the exact table list before relying on it in a design document.

Usage Notes

Two documented dependencies identify how this package is consumed. It is referenced by the form CSP_PC_FORM_PICKLINES, which is the primary user interface for maintaining picklist lines; the form calls the create, update, delete, and validation routines as the user enters and saves line data. It is also referenced by itself, reflecting internal calls between the validation helpers and the public DML procedures. These dependencies place the package squarely inside the CSP picklist form's server-side processing.

Because the API classification is PVT, the package should not be called directly from custom integrations or external interfaces. Custom code that needs to create or maintain picklist lines should use the supported public interfaces of the CSP modules or invoke the underlying DML through approved extension points. When troubleshooting form-level picklist behavior, the validation routines are the first place to inspect, since they produce the field-level errors surfaced on the CSP_PC_FORM_PICKLINES form. Any use of this package in a custom program carries upgrade risk, as private APIs are not covered by Oracle's public API stability guarantees.