Results for “frequency_num”

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

Overview

QA_SKIPLOT_PLAN_STATE_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the Quality (QA) product family. It exposes the runtime state of skip lot sampling plans, consolidating information about the process, plan, active rule, and current sampling progress into a single denormalized structure. In skip lot inspection, a receiving or manufacturing organization inspects only a fraction of incoming lots once a supplier or process has demonstrated consistent quality; the Skip Lot plan tracks which lots are inspected, which are skipped, and how the current rule (reduced, normal, or tightened frequency) is applied. The view surfaces exactly this state: the currently applicable rule, the frequency counters, the current round, and the current lot indicator.

The view is read-only and is intended for inquiry, reporting, and integration rather than transactional processing. Quality analysts, sourcing personnel, and BI developers use it to monitor skip lot activity across processes and plans without joining the underlying QA_SKIPLOT_* tables manually. Because it joins five base objects and resolves the active rule via the rule sequence, it represents the authoritative, point-in-time snapshot of each skip lot process plan's progress.

Underlying Base Objects

The view is defined over five APPS synonyms, each resolving to a QA base table:

• QA_SKIPLOT_PLAN_STATES — the driving table (QSPS), holding the mutable state per process plan, including CURRENT_RULE, CURRENT_ROUND, CURRENT_LOT, and LOT_ACCEPTED.
• QA_SKIPLOT_PROCESSES — the skip lot process definition, supplying PROCESS_ID and PROCESS_CODE.
• QA_SKIPLOT_PROCESS_PLANS — the association between a process and a quality plan.
• QA_SKIPLOT_PROCESS_PLAN_RULES — the ordered rule set for each process plan, joined on QA_SKIPLOT_PLAN_STATES.CURRENT_RULE = RULE_SEQ to expose the active rule's frequency and rounds.
• QA_PLANS — the master quality plan, providing PLAN_NAME.

The joins link PROCESS_PLAN_ID across the state, plan, and rule tables, and resolve PLAN_ID to QA_PLANS. Consequently, one row is returned per process plan in its current state, enriched with process, plan, and active-rule attributes.

Key Columns

• PROCESS_PLAN_ID — primary identifier linking the state to its process plan; the principal join key for consumers.
• PROCESS_ID / PROCESS_CODE — the skip lot process and its user-facing code.
• PLAN_ID / PLAN_NAME — the quality plan that governs the inspection characteristics.
• CRITERIA_ID — identifies the skip lot criteria evaluated for this state.
• CURRENT_RULE — the rule sequence currently in effect, which determines whether sampling is at normal, reduced, or tightened frequency.
• FREQUENCY_NUM / FREQUENCY_DENOM — the numerator and denominator expressing the inspection frequency (for example, 1/5 indicates one lot inspected per five).
• TOTAL_ROUNDS / CURRENT_ROUND — the number of rounds defined for the active rule and the round presently underway.
• CURRENT_LOT — the sequence position of the lot being processed within the current round; this is the column most frequently searched by users tracking skip lot position.
• LOT_ACCEPTED — indicates whether the most recently evaluated lot was accepted, driving rule promotion or demotion.
• RULE_START_DATE — the date the current rule became effective.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical scenarios include monitoring which process plans have advanced to reduced frequency, auditing how many lots remain in the current round, and identifying plans whose current lot or rule state has changed recently for exception reporting.

To list current skip lot state with frequency information:

SELECT process_code,
       plan_name,
       current_rule,
       frequency_num || '/' || frequency_denom AS frequency,
       current_round,
       total_rounds,
       current_lot,
       lot_accepted,
       rule_start_date
FROM   apps.qa_skiplot_plan_state_v
ORDER  BY process_code;

To find plans currently inspecting a lot within a round:

SELECT process_plan_id,
       process_code,
       current_lot,
       current_round,
       lot_accepted
FROM   apps.qa_skiplot_plan_state_v
WHERE  current_lot IS NOT NULL;

To retrieve recently modified skip lot states for a given process:

SELECT process_code,
       plan_name,
       current_rule,
       current_round,
       current_lot,
       last_update_date,
       last_updated_by
FROM   apps.qa_skiplot_plan_state_v
WHERE  process_code = :process_code
ORDER  BY last_update_date DESC;

Because the view resolves the active rule through a join on CURRENT_RULE, callers should recognize that historical rule state is not preserved here; the view reflects only the current point-in-time configuration of each process plan.