Search Results qa_skiplot_process_rules_pk1

Overview

The QA_SKIPLOT_PROCESS_PLAN_RULES table resides in the QA schema of Oracle E-Business Suite (validated in both 12.1.1 and 12.2.2) and belongs to the Quality Management module. It stores the individual skipping parameters that govern how skip lot inspection is applied within a skip lot process plan. Skip lot inspection is a sampling methodology in which a defined number of lots are received and accepted before inspection is relaxed or skipped entirely, and this table holds the granular rules — expressed as sequences, frequencies, round counts, and time spans — that determine that behavior.

From a Data Vault modeling perspective, the metadata suggests a satellite-leaning classification. The table carries its own surrogate primary key (PROCESS_PLAN_RULE_ID) alongside a foreign key to a parent plan, and its columns describe attributes of a rule rather than independent business entities or associations between multiple hubs. Modelers designing an analytical or vault-style layer should therefore treat QA_SKIPLOT_PROCESS_PLAN_RULES as descriptive, dependent context hanging off the process plan, rather than as a hub or link.

Key Information Stored

The documented physical schema contains twelve columns. The most significant are listed below.

• PROCESS_PLAN_RULE_ID — The surrogate primary key, enforced by QA_SKIPLOT_PROCESS_RULES_PK1, uniquely identifying each rule row. It is also the sole documented unique index candidate (QA_SKIPLOT_PROCESS_RULES_U1), making it the business-key pointer for this structure.
• PROCESS_PLAN_ID — The foreign key to QA_SKIPLOT_PROCESS_PLANS, linking each rule to its parent skip lot process plan.
• RULE_SEQ — The sequence in which rules are evaluated or applied within the plan.
• FREQUENCY_NUM and FREQUENCY_DENOM — The numerator and denominator defining the skip frequency, i.e. the ratio of lots to be skipped relative to lots inspected.
• ROUNDS — The number of rounds or cycles over which the rule applies before the plan advances.
• DAYS_SPAN — The time window, in days, governing the validity or application period of the rule.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN provide standard EBS who/when auditing for each rule row.

Common Use Cases and Queries

Quality analysts and implementation teams query this table to understand, audit, and report on skip lot configurations. Typical questions include which plans skip the highest proportion of lots, how frequently a supplier's inspection is relaxed, and whether rule sequences contain gaps or overlaps.

A representative join against the parent plan looks as follows:

• SELECT r.PROCESS_PLAN_RULE_ID, r.PROCESS_PLAN_ID, r.RULE_SEQ, r.FREQUENCY_NUM, r.FREQUENCY_DENOM, r.ROUNDS, r.DAYS_SPAN FROM QA.QA_SKIPLOT_PROCESS_PLAN_RULES r WHERE r.PROCESS_PLAN_ID = :plan_id ORDER BY r.RULE_SEQ;

Reporting use cases include summarizing skip ratios by plan, identifying plans with unusually long DAYS_SPAN values, and reconciling rule configurations against inspection outcomes. Because the table is small and rule-oriented, it is frequently joined to its parent for full context in quality dashboards.

Related Objects

The documented foreign key establishes the primary relationship between this table and its parent. Additional objects below are significant contextual dependencies in the quality skip lot model.

• QA_SKIPLOT_PROCESS_PLANS — The parent plan header; the FK column PROCESS_PLAN_RULES.PROCESS_PLAN_ID references QA_SKIPLOT_PROCESS_PLANS, forming the core join.
• QA_SKIPLOT_PROCESS_RESULTS — Stores skip lot processing outcomes evaluated against the plans and rules defined here.
• QA_PLANS and QA_PLAN_INSPECTIONS — Define inspection plans and their scheduled inspections, which the skip lot rules influence.
• QA_RESULTS — Captures inspection results consumed by skip lot logic to determine whether inspection may be relaxed.
• PO_HEADERS_ALL / PO_LINES_ALL — Receiving transactions that trigger skip lot evaluation under purchasing.
• QA_SKIPLOT_PROCESS_PLAN_RULES_V or concurrent programs — Supporting views and concurrent processes that read these rules during skip lot execution.