Results for “qa_skiplot_process_rules_u1”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

QA.QA_SKIPLOT_PROCESS_PLAN_RULES is a transaction data table in the Oracle E-Business Suite Quality (QA) schema that stores the individual rule lines belonging to a Skip Lot Process Plan. A skip lot process plan defines how incoming or in-process inspections may be periodically skipped once a supplier or item has demonstrated consistent quality. Each row in this table represents one rule entry within such a plan, determining the sequence in which the rule applies, the frequency at which lots are skipped versus inspected, and the thresholds that govern when frequency changes occur or when the plan is abandoned. In EBS 12.1.1 and 12.2.2 the table resides in the APPS_TS_TX_DATA tablespace, is owned by QA, and is registered under FND Design Data as QA.QA_SKIPLOT_PROCESS_PLAN_RULES with a VALID status.

From a dimensional modeling perspective, the mined foreign key structure suggests a satellite-leaning classification: the table hangs off a parent process plan and carries descriptive, time-stamped attribute rows rather than serving as a standalone hub or a many-to-many link. Treating it as a satellite of QA_SKIPLOT_PROCESS_PLANS aligns with the observed dependency, where PROCESS_PLAN_ID points back to the parent plan.

Key Information Stored

The physical schema documents twelve columns. The surrogate primary key is PROCESS_PLAN_RULE_ID, a NUMBER column that uniquely identifies each rule line. A separate unique index, QA_SKIPLOT_PROCESS_RULES_U1, also covers PROCESS_PLAN_RULE_ID, making it the documented business-key candidate for unique identification.

• PROCESS_PLAN_RULE_ID — primary key; unique identifier for the rule row.
• PROCESS_PLAN_ID — foreign key to the parent Skip Lot Process Plan; ties the rule to its owning plan.
• RULE_SEQ — sequence number that orders rules within a plan.
• FREQUENCY_NUM — numerator of the skipping frequency (for example, skip 1 of every N).
• FREQUENCY_DENOM — denominator of the skipping frequency, forming the ratio with FREQUENCY_NUM.
• ROUNDS — number of rounds that must pass before the frequency is reduced.
• DAYS_SPAN — number of days spanned before the rule is aborted.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns tracking creation and modification.

Common Use Cases and Queries

Typical uses include reviewing the skipping logic configured for a given process plan, auditing frequency changes over time, and reporting on inspection reduction strategies. Because the table is satellite-leaning, queries generally join it to its parent plan.

To retrieve all rules for a plan in order:

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

To join rules with their owning plan:

SELECT r.PROCESS_PLAN_RULE_ID, r.RULE_SEQ, r.FREQUENCY_NUM,
       r.FREQUENCY_DENOM, p.*
FROM   QA.QA_SKIPLOT_PROCESS_PLAN_RULES r,
       QA.QA_SKIPLOT_PROCESS_PLANS p
WHERE  r.PROCESS_PLAN_ID = p.PROCESS_PLAN_ID;

Reporting scenarios include identifying plans with aggressive skip ratios, plans whose DAYS_SPAN thresholds have elapsed, and frequency reduction schedules based on ROUNDS.

Related Objects

The FK/PK relationship data identifies the following significant dependency:

• QA.QA_SKIPLOT_PROCESS_PLANS — parent entity; joined on PROCESS_PLAN_ID = PROCESS_PLAN_ID.
• QA_SKIPLOT_PROCESS_RULES_U1 — unique index on PROCESS_PLAN_RULE_ID (business-key candidate).
• QA_SKIPLOT_PROCESS_RULES_N1 — non-unique index on PROCESS_PLAN_ID supporting parent lookups.
• APPS synonym QA_SKIPLOT_PROCESS_PLAN_RULES — application-layer alias referenced by forms and concurrent programs.

These objects collectively support skip lot rule configuration, maintenance, and reporting within Oracle Quality.