Search Results calculate_quant_result

Overview

QA_SKIPLOT_RES_ENGINE is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that implements the skip-lot inspection results engine within Oracle Quality. Skip-lot inspection is the practice of inspecting only a percentage of received lots from suppliers who have demonstrated consistently acceptable quality, rather than inspecting every receipt. The package evaluates incoming receipt and inspection data, determines whether a lot qualifies for skip-lot processing, and records the outcome so that Quality can reduce inspection frequency without compromising supplier quality controls.

The package is classified as OTHER in the ETRM metadata, indicating that it is an internal engine rather than a published open interface. Its status is VALID in both Oracle EBS 12.1.1 and 12.2.2. The package depends on QA_SKIPLOT_LOT_PLANS and the SYS.STANDARD package, and it is referenced directly by QA_INSPECTION_PKG, which is the primary caller invoked during inspection processing. The engine is therefore a supporting component of the Quality inspection flow rather than a standalone entry point.

Key Procedures and Functions

The package exposes eleven documented procedures and functions. Their purposes are as follows:

• PROCESS_SKIPLOT_RESULT — Core routine that evaluates incoming skip-lot data and processes the resulting skip-lot decision.
• MSCA_PROCESS_SKIPLOT_RESULT — Variant of the result processing logic intended for the Mobile Supply Chain Applications (MSCA) execution path.
• UPDATE_LOT_PLANS — Maintains the skip-lot lot plan records that govern which items and suppliers are eligible for skip-lot inspection.
• UPDATE_SKIPLOT_RESULT — Writes or updates the recorded outcome of a skip-lot evaluation.
• UPDATE_PLAN_STATE — Updates the state of the skip-lot plan, reflecting progression through its inspection cycle.
• GET_SKIPLOT_FLAG — Returns the current skip-lot flag, allowing callers to determine whether skip-lot logic applies to a given context.
• SET_SKIPLOT_FLAG — Sets the skip-lot flag to control subsequent processing behavior.
• LAUNCH_SHIPMENT_ACTION — Initiates a shipment-related action when skip-lot evaluation requires follow-up at the receipt or shipment level.
• CALCULATE_QUANT_RESULT — Computes quantitative inspection results associated with the skip-lot decision.
• GET_ASL_STATUS — Retrieves the Approved Supplier List status, which is a key input to skip-lot eligibility decisions.

Tables Accessed

The package reads and writes a wide set of Quality, receiving, and supplier tables through APPS synonyms:

• QA_SKIPLOT_LOT_PLANS and QA_SKIPLOT_ASSOCIATION — Define skip-lot plans and their associations to items, suppliers, and organizations.
• QA_SKIPLOT_RCV_RESULTS and QA_RESULTS — Store skip-lot evaluation outcomes and inspection results.
• RCV_SUPPLY, RCV_TRANSACTIONS, and RCV_TRANSACTIONS_INTERFACE — Provide receipt data and support downstream receipt actions.
• PO_APPROVED_SUPPLIER_LIST and PO_ASL_STATUSES — Supply ASL status used by GET_ASL_STATUS for eligibility determination.
• MTL_SYSTEM_ITEMS_B and MTL_SECONDARY_INVENTORIES — Supply item and locator context.
• QA_INSP_PLANS_TEMP, QA_PLAN_CHARS, QA_INSP_COLLECTIONS_TEMP, and QA_INSP_COLLECTIONS_DTL_TEMP — Carry inspection plan, characteristic, and collection data through the evaluation.

Usage Notes

QA_SKIPLOT_RES_ENGINE is not intended for direct invocation by end users. It is called by QA_INSPECTION_PKG during inspection processing and is also reachable from MSCA-related flows via MSCA_PROCESS_SKIPLOT_RESULT. Typical invocation occurs when a receipt is inspected: the engine reads ASL status and lot plan configuration, determines skip-lot eligibility, records the result, and may launch shipment actions. Custom code should not call the package directly unless it replicates the full QA_INSPECTION_PKG calling sequence, because the engine assumes established plan state and inspection context. Because the package manipulates QA_SKIPLOT_LOT_PLANS and QA_RESULTS, any extension should respect existing validation and concurrency handling rather than bypassing QA_INSPECTION_PKG.