Search Results qa_inspection

Overview

QA_INSPECTION_PKG is an APPS-owned PL/SQL package in Oracle E-Business Suite that supports the Quality inspection process, particularly for skip lot and sampling inspection plans. It is declared with AUTHID CURRENT_USER, meaning its SQL executes with the privileges of the invoking user rather than the package owner. The package provides supporting logic for dispatching shipment actions based on the inspection control type (skip lot, sampling, or regular inspection), populating temporary working tables consumed by downstream inspection logic, and exposing utility functions that determine the inspection mode or the QA configuration state.

The header source reveals the package was created at revision 120.0.12000000.1 (2007), indicating it is a long-standing component of the ETRM/Quality schema that has been carried forward into the 12.1.1 and 12.2.2 releases. The user's search term, launch_shipment_action, corresponds to the package's LAUNCH_SHIPMENT_ACTION procedure, which is the dispatch entry point for shipment-action launching.

Key Procedures and Functions

The package exposes seven documented program units:

• INIT_COLLECTION — Procedure that initializes the temporary tables QA_INSP_COLLECTIONS_TEMP and QA_INSP_PLANS_TEMP for a given collection id and plan id. It accepts parameters identifying the collection, the lot size, the collection plan, and the unit of measure. These temporary tables are used by both the skip lot and sampling processes.
• LAUNCH_SHIPMENT_ACTION — Procedure that dispatches action-launching logic based on the sampling and skiplot flags. Per the header comment, it does nothing for a regular inspection; it is meaningful only when the collection is under sampling or skip lot control. It accepts a PO processor mode, a group id, and an employee id.
• IS_REGULAR_INSP — Function returning fnd_api.g_false if the collection is under either skip lot or sampling control, and fnd_api.g_true otherwise (i.e., a regular inspection).
• IS_SAMPLING_INSP — Function returning fnd_api.g_true if the collection is under sampling control, fnd_api.g_false otherwise.
• IS_SKIPLOT_INSP — Function returning fnd_api.g_true if the collection is under skip lot control, fnd_api.g_false otherwise.
• QA_INSTALLATION — Function returning whether the Quality (QA) module is installed.
• QA_INSPECTION — Function returning whether the QA_PO_INSPECTION profile option is set to Quality.

Tables Accessed

Three tables are referenced through APPS synonyms:

• QA_INSP_COLLECTIONS_TEMP — temporary holding table for inspection collection data, populated by INIT_COLLECTION.
• QA_INSP_PLANS_TEMP — temporary holding table for inspection plan data, populated by INIT_COLLECTION.
• QA_RESULTS — the results table against which inspection mode and control (sampling, skip lot, regular) are evaluated by the IS_* functions.

Usage Notes

QA_INSPECTION_PKG is referenced by three other packages, indicating it operates as a shared utility within the QA/PO inspection flow rather than as an end-user-facing API. LAUNCH_SHIPMENT_ACTION is typically invoked during receiving or shipment processing when inspection actions must be dispatched for collections governed by sampling or skip lot plans; because it is a no-op for regular inspections, callers generally guard its invocation using IS_REGULAR_INSP. The IS_SAMPLING_INSP and IS_SKIPLOT_INSP functions allow callers to branch logic according to the applicable control type, while QA_INSTALLATION and QA_INSPECTION support configuration checks before inspection processing is attempted. Custom extensions integrating with the QA inspection flow should call these routines rather than replicating control-type logic directly against QA_RESULTS.