Inspection Points

Inspection point is a wonderful tool which can be used to carry out inspection
on the basis of several factors i.e Time frame, Quantity based, Sample
Management, Calibration, or any other factor called as a POINT. In simple
words, Inspection points can be applied to any scenario where multiple results
are captured for a common inspection lot.
SAP has defined different Inspection points in standard itself and given
additional provision to define our own process. I have tried to put my best
efforts to write this document to identify the basic settings required to be done,
relevant master data and execution of Inspection points in an inspection lot.
Since there are already system defined identifiers available, I’m going to adopt
a customized approach for Inspection points.
Process: I have taken a scenario where business needs to record multiple

results for a single inspection lot on the basis of Lab name, Shift name and
Sample sequence. There are ten laboratories, which are analyzing samples
round the clock shift wise. It’s like recording the individual result per
sample/lab/shift.
Configuration settings: QCC0> Quality Planning> Inspection planning>

General> Define Identifier for Inspection points.
I have defined an Inspection point Z06 with reference of Shift, Laboratory and
Sample detail.
1. In the following snap shot, Keywords are defined against respective User
fields with Field Active. You need to provide a number into that to activate the
respective User field. This also need to be consider that any Two fields each
for Char type and Num type can be defined and one each for date and time in
respective formats as indicated clearly below.
So whenever I go to record my result, I need to provide details in the

sequence of Shift>Lab>Sample
2. Next step is to define the Valuation. Go the next tab ‘Valuation’ and assign
the usage decision selected set along with Acceptance and Rejection criteria.
Following snap shot indicates the UD selected set Z01 defined in Plant 1100
along with A (Accepted) and R (Rejected) codes as per valuation. This
valuation is basically done once you go to save the result for each Inspection
point (Explained in later part of this document).
3. Next step is to Assign this inspection point into the header of Inspection
plan.
Above settings are well enough to use the Inspection points. There could
Sampling scenario also be in the picture where SP would need to be created
wrt Inspection points. If it is not into use, then no need to create one.
Execution of Inspection points.
One GR is being everyday for the PO number 3500001413. System will create
three inspection lots in three days (as shown below) and multiple analysis
would be done daily and respective results would be recorded for each
inspection lot using Inspection points.
When user go to record the result against first inspection lot 10000121027,
system will pop up a screen asking the Shift, Lab and Sample details. Refer
following snapshot where input for Shift, Lab and sample is provided. This
indicates the first sample analyzed in Lab 1 during Shift A.
Following snapshot reflects the multiple results against the same inspection
lot, or different sample analysis carried out in same shift and laboratory using
different point.
Similarly, there could be different combinations. Following is another case of

multiple inspection points for a different inspection lot number.
This way, several combination can be made and result recording can be done
following different points. If user provides the same combination, system will
show the screen with already filled results.
As soon as you enter the result, system will ask for the valuation before saving
them. It will give its own valuation (based on your predefined settings) but you
can always change the valuation. Valuation against each inspection point is
visible in the UD screen of the respective inspection lot.
Refer following snapshot,
Please note that if there is any class characteristic linking done, transfer of
inspection results would take place on the basis of latest valuation.
At last, it is always fair to close the inspection lot which can be done by
completing UD and releasing the stock out of QI.
Multiple results against a single inspection lot are stored in table QASR. This
can be used directly or to generate any customized report to download the
data.
I hope this document will come handy for all those who need step by step
procedure to implement inspection points and those as well who haven’t
worked on IP for long time.
Any feedback pertaining a correction, update or in general is highly
appreciable to strengthen this document.

Inspection Points

Uploaded by

Copyright:

Available Formats

Inspection Points

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Inspection Points

Uploaded by

Copyright:

Available Formats

Inspection point is a wonderful tool which can be used to carry out inspection

Process: I have taken a scenario where business needs to record multiple

Configuration settings: QCC0> Quality Planning> Inspection planning>

So whenever I go to record my result, I need to provide details in the

Similarly, there could be different combinations. Following is another case of

You might also like