The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Oracle Fusion Cloud Quality Management can inspect a sample of a work-order operation’s quantity during an inline WIP inspection, but only for non-serialized work. Serial-tracked operations still require each serial to be inspected at that operation. Before a sampling plan goes live, a planner has to choose a sampling method (fixed count, percentage, or ANSI/ASQC Z1.4 acceptance sampling), confirm that the inspection plan matches the operation, and set the rejection rule and characteristic limits to match the factory’s own quality policy. Oracle’s documentation does not recommend a sample size, so the numbers in your plan are a business decision you need to justify.
Where WIP sampling applies
Oracle describes the capability this way: the Work In Process Sampling feature in Quality Inspection Management “provides the ability to select representative sample(s) out of a discrete or process manufacturing work order operation quantity to determine the quality of non-serialized work in process (WIP)” (Oracle, How You Manage Inspections).
In practical terms, the feature is supported in these conditions:
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minute- The inspection is an inline inspection performed during an operation transaction on a work order.
- The operation is not serial-tracked. Oracle states that support for WIP sampling at inline inspections covers non-serial-tracked operations (Oracle, How You Manage Inspections).
- A matching inspection plan exists for the inline inspection (Oracle, Inline Inspections).
The serial-tracking boundary
This is the first limit a planner must check. Sampling is designed for WIP that is treated as non-serialized. On a serial-tracked operation, each serial must be inspected at that operation, and a sample cannot stand in for those individual units. Oracle’s documentation makes this distinction explicit for WIP sampling (Oracle, How You Manage Inspections).
#1 Best Overall
Before designing a plan, confirm two things for every operation in scope: whether the item is serial-controlled, and whether the operation is set up as serial-tracked. If either answer is yes, the sampling plan does not apply to that operation, and the inspection design has to be built around per-serial inspection instead.
Selection method versus acceptance rule
Most confusion about WIP sampling comes from treating two separate decisions as one. Each sampling plan answers two different questions:
- Selection method: how many units are drawn from the operation quantity for inspection. Oracle offers fixed count, percentage, and ANSI/ASQC Z1.4 sampling for this purpose.
- Acceptance rule: how many failed samples lead to rejection of the inspection quantity. The rule depends on the method. Under fixed count and percentage sampling, a single failure rejects the whole inspection quantity. Under AQL sampling, the rejection number from the applicable AQL table decides.
A planner can change the sample size without changing the rejection logic, and the reverse is also true. Keep the two decisions separate when you document the plan.
The three sampling approaches
Oracle documents three approaches for inspection levels: ANSI/ASQC Z1.4 acceptance sampling, fixed count, and percentage sampling (Oracle, Inspection Levels). The table below compares them on the points that matter when you set up a plan.
Rank #3
- These driver's vehicle inspection report (DVIR) books comply with DOT regulations 49 CFR 396.11 and 396.13.
- Our DVIR inspection book contains a vehicle inspection checklist that comprehensively lists specific tractor/truck and trailer parts to help simplify the inspection process. This allows drivers to quickly mark any needed repairs.
- DVIR books include essential DOT regulations which are printed on the inside cover to remind drivers of the DOT-required procedures they must follow. And there are instructions for filling out a DVIR form to simplify the completion.
- This package comes with 10 books. Each book contains 35 sets of DVIR forms, in duplicate. In total, you will receive 350 forms. Compact 8.5" x 5.5" size facilitates easy handling and record-keeping.
- Our inspection report books are made of carbonless, premium paper that withstands daily use. Whether you manage a single vehicle or a large commercial fleet, our DVIR book is an essential tool for ensuring the safety and compliance of your operations.
| Method | What Oracle documents | How sample count behaves | Rejection rule | Planning implication |
|---|---|---|---|---|
| Fixed count | The planner specifies a fixed number of samples (Oracle, Inspection Levels). | Stays the same regardless of the operation’s completed quantity, so the inspected share changes as the quantity changes. | One failing representative sample rejects the entire inspection quantity. | Predictable inspection effort per transaction. A large lot receives a smaller share of inspection than a small one. |
| Percentage | The planner specifies a percentage of the total quantity to inspect (Oracle, Inspection Levels). | Scales with the quantity. Rounding behavior is not stated in Oracle’s overview. | One failing representative sample rejects the entire inspection quantity. | Inspection effort rises with lot size. Check how fractional samples are handled in your release before relying on exact counts. |
| ANSI/ASQC Z1.4 (AQL) | Acceptance sampling based on acceptable quality limits. Sample size and acceptance and rejection numbers are associated with the sampling plan (Oracle, QA_INSPECTION_LEVELS_B). | Rejection occurs when the number of failed samples meets or exceeds the rejection number from the applicable AQL table (Oracle, Inspection Levels). | Allows a defined number of failures before the lot is rejected. The sample size and rejection number come from the standard’s tables, not from a free choice. |
Fixed count sampling
Fixed count suits operations where the team wants the same inspection workload on every transaction. The weakness is that a large operation quantity gets a smaller inspected share than a small one, so the detection power of the plan shifts with lot size. If lot sizes vary widely, record the inspected share for each typical size so the consequences are visible.
Percentage sampling
Percentage sampling ties inspection effort to quantity. It is easier to explain to operators because the rule is a single ratio. Because the rule is still one-failure rejection, a large lot with a high percentage carries a larger inspection burden with the same strictness per sample.
ANSI/ASQC Z1.4 acceptance sampling
AQL sampling is the only method in this set that allows some failed samples without rejecting the inspection quantity. The standard’s tables link the lot size, the inspection level, and the acceptable quality limit to a sample size and an acceptance and rejection number. Oracle labels the standard ANSI/ASQC Z1.4, the name used in its documentation, and the same standard is commonly referenced today as ANSI/ASQ Z1.4. Confirm the edition your quality team works from, because table values should come from that edition. Oracle’s documentation identifies the standard as a sampling option but does not reproduce the tables.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchHow sample quantities are calculated
An inline inspection requires a matching inspection plan. When the inspection level includes a sample quantity and a unit of measure, Oracle uses those values to calculate the quantity per sample and the total sample quantity (Oracle, Inline Inspections). That means the sample quantity is defined once at the inspection level, and the transaction-level figures follow from it.
The sources describe which inputs are used but do not publish a worked formula for every method. Before go-live, run a test transaction on a representative operation and confirm that the quantity per sample, the total sample quantity, and the unit of measure match your intent.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Characteristics, limits and action rules
A WIP inspection plan applies at work-order execution and contains inspection elements, specifications, and criteria. Characteristics can carry target values and limits. A result outside those limits can create a quality issue, and what happens next depends on the configured action rule (Oracle, Inspection Plans).
This is separate from the sampling method. Sampling decides which units are checked. Characteristic limits and action rules decide whether a checked unit’s measurement is a problem. A plan can have a correct sampling method and still produce the wrong outcome if the limits are too loose or the action rule does not escalate the way your policy requires. The method and limits should be set from your process capability and quality policy, not copied from another site.
Decisions to make before production
The following decisions are general quality-planning considerations. Oracle’s documentation does not prescribe them, and none of them implies a recommended sample size.
- Confirm the serial boundary. List each operation in scope and record whether it is serial-tracked. Remove any serial-tracked operation from the sampling design.
- Choose the selection method. Use fixed count when a constant inspection workload matters most, percentage when effort should follow lot size, and AQL when your quality standard defines acceptable failure levels.
- Set the sample quantity and unit of measure at the inspection level, then check the calculated quantity per sample and total sample quantity on a test transaction.
- Define the acceptance rule. For fixed count and percentage, accept that one failure rejects the inspection quantity. For AQL, document the rejection number taken from the table you use.
- Set characteristic targets and limits from your process data and specification, and record which action rule fires when a result is out of limit.
- Document the rationale. Record the defect consequences, the process risk, the lot size range, and any customer or regulatory requirement that drove each choice. Those records are what auditors and quality reviewers will ask for.
- Confirm the release. Oracle’s cited pages come from its 25C, 26A, and 26B documentation. Feature behavior can change in later quarterly updates, so check the help for your tenant’s release before finalizing settings.
What the documentation does not settle
Oracle’s WIP sampling documentation defines how the feature works and which fields drive the calculation. It does not give a recommended sample size, an outcome rate, or a preferred method for every factory. Those choices belong to the quality team, and the plan should be defensible on its own terms.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
