How-toSAP S/4HANA and ECCQuality Management (QM) / Physical Samples

SAP QM Sample-Drawing Procedure: Setup and Use (QPV1)

Question
sap qm sample drawing procedure

Also searched as

  • sap qpv1 sample drawing procedure
  • sap physical sample drawing
  • sample-drawing procedure inspection plan sap

Short answer

A sample-drawing procedure defines how physical samples are taken for an inspection: how many, in which containers, and what they are used for. Create it with QPV1, then reference it from the inspection plan (or material and inspection setup), so that when a lot is created the system generates the physical sample records, which you can also create manually with QPR1.

Applies to: SAP ECC 6.0 and SAP S/4HANA on-premise with QM physical sample management

Set up a sample-drawing procedure

  1. 1Run QPV1 (Create Sample-Drawing Procedure). Enter the plant and a procedure name.
  2. 2Give a description and the sampling scope: the sample quantity or number of samples to be drawn.
  3. 3Define the sample unit and the container or packaging used for the physical sample.
  4. 4Set the sample type and the storage or usage information if your process requires it.
  5. 5Save. QPV2 changes and QPV3 displays the procedure.
  6. 6Assign the procedure in the inspection plan so that lots created from the plan use it.
  7. 7Create an inspection lot, check the physical sample records it generates, and print the sample labels if used.

What physical sample management does

Physical sample management records the actual samples taken during inspection: who took them, where they are stored, which lot and characteristic they relate to. This is the evidence trail needed for retained samples, laboratory testing and returns.

The sample-drawing procedure is the master data that describes how to take the sample. It is not the same as the sampling procedure (QDV1), which defines how many units to inspect statistically. Both are often used together.

Without the procedure, physical samples can still be created manually, but there is no standard definition to apply automatically.

Linking to plans and lots

Assign the procedure in the inspection plan so the lot picks it up when generated. At lot creation, the system proposes physical sample records for the lot, based on the procedure and the sample quantity.

At results recording, inspectors can refer to the samples and record results against them. In laboratory flows, samples are passed to a lab and the results flow back.

Where the same product has different sampling needs per plant or customer, create separate procedures and keep naming consistent.

QPV1   Create sample-drawing procedure
QPV2   Change sample-drawing procedure
QPV3   Display sample-drawing procedure
QPR1   Create physical sample drawing
QDV1   Create sampling procedure (different object)

Troubleshooting

If no physical samples appear in a new lot, check that the procedure is assigned in the plan used for the lot, that the plan is the one selected for the lot, and that the inspection type allows physical samples.

If quantities look wrong, check the sample size in the procedure against the sampling scheme of the lot. The two are independent, so a mismatch is possible.

Make sure users have authorization for physical sample transactions. Missing authorization often looks like a missing function rather than a clear error.

Try it here, free

SAP QM Sample Size Calculator by Lot Size and Sampling Procedure

Open full tool

Compare the sample size from an AQL table, a percentage rule and a fixed sample for any lot size, and estimate the inspection time.

Common pitfalls

  • !Confusing the sampling procedure (QDV1) with the sample-drawing procedure (QPV1).
  • !Assigning the procedure to a plan that is not the one selected for the lot.
  • !Defining a sample size that conflicts with the sampling scheme.
  • !Not setting up the storage or labeling needed to find the physical samples later.
  • !Forgetting authorizations for physical sample transactions.

How an ERP-grounded AI assistant handles this

Physical sample questions are usually traceability questions: where is the retained sample from lot X, and which plan told the operator to take it. A grounded assistant can follow the lot to the sample records, the plan and the procedure in one answer. Netray can host it on your own servers so quality and traceability data stay inside your network.

Frequently asked questions

What is a sample-drawing procedure in SAP QM?

It is master data that defines how physical samples are taken for an inspection, including quantity and containers. It is used with physical sample management to create sample records for a lot.

What is the difference between QPV1 and QDV1?

QPV1 creates a sample-drawing procedure for physical samples. QDV1 creates a sampling procedure, which defines the statistical inspection sample size. They solve different problems.

How are physical samples created?

Automatically when the inspection lot is created, if the plan has a sample-drawing procedure, or manually with QPR1. They are then tracked against the lot.

Do I need physical sample management for all inspections?

No. It is optional and mostly used where retained samples, laboratory testing or sample traceability are required. For simple in-line inspection it adds effort without value.

Related

How-to

How to Create an Inspection Method in SAP QM (QS31)

An inspection method describes how a characteristic is to be inspected, for example with a micrometer or a visual check, and holds the instructions. Create it with QS31 for a plant, set the status and version, write the text, and assign it to a master inspection characteristic (QS21) or directly in an inspection plan characteristic.

Error fix

SAP QM: Inspection Lot Not Created at Goods Receipt

An inspection lot is created only when QM is active for the plant, the material has an active inspection type for the goods movement, and the material carries a QM control key. Check the Quality Management view in MM02, confirm inspection type 01 (purchase order) or 04 (production order) is active, then check QM activation in the plant and the goods movement used.

How-to

How to Create a Selected Set in SAP QM (QS51)

A selected set is a subset of codes taken from one or more catalog code groups, so users only see the relevant choices. Create it with QS51 for a catalog type and plant, add the codes, save, and then assign it to a master inspection characteristic (QS21), the usage decision, or defect recording.

Error fix

SAP M7 021: Deficit of SL Stock Quantity

M7 021 fires during a goods issue, delivery, or confirmation when SAP checks the unrestricted-use (SL) stock for the exact plant, storage location and batch combination and finds less than what you are trying to post out. Fix the entry (batch, storage location, quantity) first; only enable negative stock or downgrade the message to a warning if the business genuinely needs to post ahead of a receipt.

Error fix

SAP IDoc Status 51: Application Document Not Posted

Status 51 tells you the IDoc reached the application layer and failed to post, but the status text itself is not the error - the real cause sits in the status record's long text or the linked application log. Fix the underlying data or configuration, then reprocess the IDoc through BD87 rather than editing the status.

Error fix

SAP Short Dump TIME_OUT: Maximum Runtime Exceeded

A TIME_OUT runtime error means a dialog (or RFC) work process ran longer than the maximum allowed runtime, controlled by profile parameter rdisp/max_wprun_time (600 seconds by default). The fix is almost always to move the long-running work to background processing or tune the underlying program, not to raise the timeout.

AI for ERP

AI for SAP Quality Management: Notifications, 8D, and CAPA Without the Manual Drafting

AI grounded on SAP QM data that triages notifications, drafts 8D and CAPA reports, and summarizes inspection trends, deployed on-prem for full traceability.

Stuck on SAP S/4HANA and ECC?

Talk to engineers who work inside SAP S/4HANA and ECC every week, and who build private AI that answers these questions from your own ERP data.