Search Results skiplot_control

Overview

QA_SKIPLOT_UTILITY is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that implements the core engine for skip lot inspection in Oracle Quality. Skip lot inspection allows an organization to reduce the frequency of incoming or in-process inspection for a supplier or item once a defined history of acceptable lots has been established. The package evaluates skip lot plans, tracks acceptance and rejection statistics across inspection rounds, and determines whether a given lot may bypass inspection.

The package supports two inspection contexts, distinguished by internal constants: receiving inspection (RCV) and work in process inspection (WIP). It also defines two skip lot rule evaluation modes, ADJACENT_DATE_CHECK and DATE_SPAN_CHECK, which govern how elapsed time and lot sequence affect skip lot eligibility. The header declares AUTHID CURRENT_USER, meaning the package executes with the privileges of the invoking user rather than the definer.

The user search term "skiplot_setup" corresponds directly to the SKIPLOT_SETUP function, which is one of three availability-check functions exposed by this package and is central to determining whether skip lot criteria have been configured for an organization.

Key Procedures and Functions

• CHECK_SKIPLOT_AVAILABILITY — Determines whether skip lot functionality is available for a given transaction type and inventory organization. Per the source comments, it calls SKIPLOT_CONTROL, QA_INSTALLATION, and SKIPLOT_SETUP to arrive at its result.
• SKIPLOT_CONTROL — Returns whether skip lot control is enabled at the inventory organization level.
• SKIPLOT_SETUP — Returns whether skip lot criteria have been defined for the specified organization and transaction context.
• GET_PROCESS_PLAN_ID — Retrieves the process plan identifier associated with a skip lot evaluation.
• CHECK_RULE_FREQUENCY — Evaluates whether the current lot satisfies the frequency requirement defined by the active skip lot rule.
• FETCH_PLAN_STATE — Retrieves the current state record for a skip lot plan, including round, frequency, and acceptance counters.
• INIT_PLAN_STATE / INIT_PLAN_STATES — Initialize plan state records for a single plan or a set of plans prior to evaluation.
• RESET_LAST_RECEIPT_DATE / RESET_PLAN_STATES — Reset receipt dates and plan state data, typically at the start of a new cycle or after plan reconfiguration.
• INSP_ROUND_FINISHED / INSP_RULE_FINISHED — Indicate whether an inspection round or an inspection rule has completed.
• GET_NEXT_INSP_RULE — Returns the next rule to be applied within the skip lot process.
• MORE_ROUNDS — Signals whether additional inspection rounds remain.
• ENOUGH_LOT_ACCEPTED — Determines whether sufficient lots have been accepted to qualify for reduced inspection.
• DATE_REASONABLE — Validates date logic for time-based (adjacent date or date span) skip lot checks.
• UPDATE_INSP_STAGE / UPDATE_PLAN_STATE — Persist updated inspection stage and plan state information.
• LAUNCH_WORKFLOW — Initiates the Oracle Workflow process associated with skip lot processing.
• UPDATE_STATE_HISTORY — Records state transitions into the skip lot state history table.

Tables Accessed

MTL_PARAMETERS supplies organization-level defaults, and MTL_SYSTEM_ITEMS context is implied through organization validation. QA_PLANS and QA_CHARS define inspection plans and the characteristics evaluated. QA_SKIPLOT_ASSOCIATION links skip lot definitions to plans or items, while QA_SKIPLOT_PROCESSES, QA_SKIPLOT_PROCESS_PLANS, and QA_SKIPLOT_PROCESS_PLAN_RULES store the process, plan, and rule configuration that drives evaluation. Runtime state is held in QA_SKIPLOT_PLAN_STATES and history in QA_SKIPLOT_STATE_HISTORY. Transactional results are captured in QA_SKIPLOT_LOG and QA_SKIPLOT_RCV_RESULTS, with sequences QA_SKIPLOT_LOG_ID_S and QA_SKIPLOT_LOT_ID_S providing identifiers. DUAL is used for trivial single-row queries.

Usage Notes

QA_SKIPLOT_UTILITY is not typically invoked directly by end users. It is called by Oracle Quality forms and by the skip lot processing logic executed during receiving and WIP transactions, and it is referenced by six other packages in the EBS schema. The CHECK_SKIPLOT_AVAILABILITY function is the standard entry point for external callers that need to confirm skip lot eligibility before processing a lot. Customizations that extend skip lot behavior should call the same documented functions rather than modifying the package, since it is an Oracle-owned object subject to patching.