QM tables:

Important QM Tables

Area Table Description

Master Data QMAT Inspection type - material parameters
Master Data QMHU QM Link Between Inspection Lot and Handling Unit Item
Master Data QMTB Inspection method master record
Master Data QMTT Inspection Method Texts
Master Data QPAC Inspection catalog codes for selected sets
Master Data QPAM Inspection catalog selected sets
Master Data QPMK Inspection characteristic master
Master Data QPMT Master Inspection Characteristics Texts
Master Data QPMZ Assignment table - insp. methods/master insp. characteristic
Master Data TQ01D Authorization groups for QM master data
Master Data TQ01E Text authorization groups for QM master data
Master Data TQ21 Assignment of screens to screen groups
Master Data TQ25 QM:screen sequence for master and inspection characteristics

QM Master Data

Catalog QPCD Inspection catalog codes

Catalog QPCT Code texts
Catalog QPGR Inspection catalog code groups
Catalog QPGT Code group texts
Catalog TQ07 Follow-Up Action for Usage Decision of Inspection Lot
Catalog TQ07A QM: Function Modules for Follow-Up Action
Catalog TQ07T Language-dependent texts for Table TQ07
Catalog TQ15 Inspection catalog type index
Catalog TQ15T Language-dependent texts for table TQ15
Catalog TQ17 Defect classes
Catalog TQ17T Language-dependent texts for table TQ17
Catalog

Sample Determination QDEB Allwd. Relationships: Sampling Procedures/Dynamic Mod. Rules

Sample Determination QDEBT Allowed combinations of procedures/dynamic mod. rules: texts
Sample Determination QDPA Sampling scheme-instructions
Sample Determination QDPK Sampling scheme header
Sample Determination QDPKT Sampling scheme: texts
Sample Determination QDPP Sampling scheme item

1
Sample Determination QDQL Quality level
Sample Determination

Inspection Char TQ17A Weighting of Char

Inspection Char TQ11 Inspection Qualification
Inspection Char TQ29 Tolerance Keys
Inspection Char T006 Unit of measurement
Inspection Char

Dynamic Modification QDBM Valuation mode

Dynamic Modification QDBMT Valuation Mode: Texts
Dynamic Modification QDDR Dynamic modification rule (header)
Dynamic Modification QDDRT Dynamic modification rule: texts
Dynamic Modification QDEP Allowed inspection severities
Dynamic Modification QDEPT Allowed Inspection Severities: Texts
Dynamic Modification QDFB Function modules for the individual procedure categories
Dynamic Modification QDFBT Function Modules for Procedure: Texts
Dynamic Modification QDFM Function modules for valuation mode
Dynamic Modification QDFMT Function Modules for Valuation Mode: Texts
Dynamic Modification QDPS Inspection stages for a dynamic modification rule
Dynamic Modification QDPST Inspection Stages: Texts
Dynamic Modification QDSA Sampling type
Dynamic Modification QDSAT Sampling Type: Texts
Dynamic Modification QDSV Sampling procedure
Dynamic Modification QDSVT Sampling Procedure: Texts
Dynamic Modification TQ39B QM : Activates reference for dyn. modification level
Dynamic Modification

Graphics & SPC QASH Quality control chart

Graphics & SPC QAST Control chart track
Graphics & SPC QPSH Control chart types
Graphics & SPC QPSHT Texts for control chart types
Graphics & SPC QPSP SPC criterion
Graphics & SPC QPSPT Texts for SPC criteria
Graphics & SPC QPST Control chart track
Graphics & SPC QPSTT Texts for control chart tracks
Graphics & SPC

Specifications QMSP QM: material specification

Specifications

Inspection Plan PLKO Inspection plan Header

Inspection Plan MAPL Material Assignement

2
Inspection Plan PLPO Operation Details
Inspection Plan PLMK Inspection plan characteristics
Inspection Plan PLMW MAPL-Dependent Charac. Specifications (Inspection Plan)
Inspection Plan TQ03 QSS: Control for Screen Texts/TABLE NOT USED (Rel. 4.6)
Inspection Plan TQ29A Dependency tolerance key - nominal measurement
Inspection Plan TQ72 Type of share calculation
Inspection Plan TQ72T Texts for type of share calculation
Inspection Plan TQ75 QM formula parameters
Inspection Plan TQ75F Field names for QM formulas
Inspection Plan TQ75K Short text for Table TQ75F
Inspection Plan TQ75T Description of formula parameters

Inspection Plan

Qm in procurement QINF QM-info record for material and vendor

Qm in procurement TQ02 QM system definition
Qm in procurement TQ02A QM system assignment and QM system requirements
Qm in procurement TQ02B QM system
Qm in procurement TQ02T QM system description
Qm in procurement TQ02U Description QM system
Qm in procurement TQ04A Functions that can be blocked
Qm in procurement TQ04S QM block functions : texts
Qm in procurement TQ05 QM certificate categories for procurement
Qm in procurement TQ05T QM: text table for certificate types
Qm in procurement TQ08 Control of QM in procurement
Qm in procurement TQ08T QM: text for QM procurement keys
Qm in procurement TQ09 QM: agreement of QM document types
Qm in procurement TQ09T QM: agreement of QM document types
Qm in procurement TQ32A Inspection type to status assignment from status profile

Qm in procurement

QM in SD QVDM QM Info Record - QM Control in SD

QM in SD TQ32B Find insp.type for quality insp. for delivery note
QM in SD

Inspectio lot QALS Inspection lot record

Inspectio lot QALT Partial lot
Inspectio lot T156Q Movement Type: Material-Independent Control
Inspectio lot TQ30 Inspection types
Inspectio lot TQ30T Texts for inspection types

3
Inspectio lot TQ32 Assignment of inspection type to origin
Inspectio lot TQ32C Lot creation allowed values for the origin
Inspectio lot TQ32C _T Texts for lot creation indicator
Inspectio lot TQ33 Relevant fields for origin
Inspectio lot TQ34 Default values for inspection type
Inspectio lot

Inspection point QAPP Inspection point

Inspection point TQ79 Table with inspection point/user field combinations
Inspection point TQ79T Key words for inspeciton point user fields
Inspection point

Results Recording QAES Sample unit table

Results Recording QAKL Results table for value classes
Results Recording QAMR Characteristic results during inspection processing
Results Recording QAMV Characteristic specifications for inspection processing
Results Recording QASE Results table for the sample unit
Results Recording QASR Sample results for inspection characteristics
Results Recording QASV Sample specifications for inspection processing
Results Recording TQ12 Ind. external numbering for test units in results recording
Results Recording TQ12T Texts for the ind. for ext. numbering of units to be insp.
Results Recording TQ70 Control table for results recording
Results Recording TQ70C Function codes for navigation from the char.overview screen
Results Recording TQ70E Screen-based processing tables
Results Recording TQ70F Navigation during results recording
Results Recording TQ70S Characteristic overview screen for results recording
Results Recording TQ73 Origin of results data
Results Recording TQ73T Texts for origin of results data
Results Recording TQ74 Recording configuration
Results Recording TQ74T Recording configuration
Results Recording TQ76 Processing status of inspection characteristics
Results Recording TQ76T Texts for the processing status of insp. characteristics
Results Recording TQ77 Attributes for the Inspection Characteristic
Results Recording TQ77T Text Tables for Attributes
Results Recording TQ78 Status-dependent processing table for insp. characteristics
Results Recording TQ78T Texts for the status-specific proc. table for insp. char.
Results Recording

Defects recording TQ84 Confirmation profile

Defects recording TQ84T Text table for confirmation profile
Defects recording TQ86 Report category for defects recording
Defects recording TQ86A Assignment report category for work center

4
Defects recording TQ86T Text table for report category
Defects recording V_T35 2B_F Generated table for view V_T352B_F
Defects recording

Usage decision QAMB QM: Link Between Inspection Lot and Material Document
Usage decision QAVE Inspection processing: Usage decision
Usage decision TQ06 Procedure for Calculating the Quality Score
Usage decision TQ06T Language-specific texts for Table TQ06
Usage decision TQ07M QM: Inventory postings with usage decision
Usage decision

Sample Mgmt QPRN Sample drawing of phys. samples

Sample Mgmt QPRS Master record for phys. samples
Sample Mgmt QPRVK Sample-drawing procedure
Sample Mgmt QPRVK T Header for sample drawing procedure texts
Sample Mgmt QPRVP Sample-drawing items
Sample Mgmt QPRVP T Items for sample drawing procedure texts
Sample Mgmt TQ40 Definition of sample types
Sample Mgmt TQ40T Text table for sample type
Sample Mgmt TQ41 Storage locations for physical samples
Sample Mgmt TQ41T Texts for storage locations
Sample Mgmt TQ42 Physical sample containers
Sample Mgmt TQ42T Texts for phys. sample containers
Sample Mgmt

QMIS S068 Vendor statistics

QMIS S069 Material statistics
QMIS S097 QM notifications: Matl anal.
QMIS S098 QM notification: Vendor anal.
QMIS S099 QM notifications: Cust. anal.
QMIS S100 Problems: Material analysis
QMIS S102 Problems: Vendor analysis
QMIS S103 Problems: Customer analysis
QMIS S104 Customer statistics
QMIS S161 Inspection results: General
QMIS S162 Quantitative insp. results
QMIS S163 Quant. Insp. Result: Vendor
QMIS S164 Quant. Insp. Result: Vendor
QMIS S165 Inspection result: gen. custs
QMIS S166 Insp. Results: Quant. Customer
QMIS TQ55 Assign inspection lot origin for update group
QMIS TQ56 Definition of quality score classes

5
QMIS TQ56T Text table for the definition of quality score classes
QMIS TQ57 Assignment of quality score key to info structure
QMIS

Quality Certificates QCPR QM quality certificates in procurement

Quality Certificates I000 Conditions for certificate profile
Quality Certificates KONDI Conditions: Data part for certificates
Quality Certificates QCVK Certificate profile header
Quality Certificates QCVM Certificate profile characteristic level
Quality Certificates QCVMT Certificate profile characteristic level: texts
Quality Certificates QCVV Certificate Profile: List of Preliminary Products
Quality Certificates TQ61 Result value origin for certificates
Quality Certificates TQ61T Origin of result values for certificates: texts
Quality Certificates TQ62 Output strategy for skip characteristics
Quality Certificates TQ62T Output strategy for skip characteristics: texts
Quality Certificates TQ63 Origin of insp. specs for certificates (function modules)
Quality Certificates TQ63T Origin of inspection specifications for certificates: texts
Quality Certificates TQ64 Origin of characteristic short text for certificates
Quality Certificates TQ64T Origin of characteristic short text for certificates: texts
Quality Certificates TQ65 Certificates: Combinations allowed for origins, specs/values
Quality Certificates TQ67 Certificate-Relevant Output Types
Quality Certificates

Quality Notification QMEL Notification header

Quality Notification QMFE Item
Quality Notification QMSM Task
Quality Notification QMMA Activities
Quality Notification T352C Catalog types for each catalog profile
Quality Notification TQ81 Notification Scenario
Quality Notification TQ81V Usage of parts
Quality Notification TQ81V_T Texts for usage of parts
Quality Notification TQ81_T Texts for Notification Scenarios
Quality Notification TQ82 Change of Notification Type
Quality Notification TQ83 Partner Functions for Codes
Quality Notification TQ85 Function table for follow-up functions
Quality Notification TQ85R Rules for Follow-Up Functions
Quality Notification TQ85_T Action box text table
Quality Notification TQ8CO Assignment of reference orders to notification type
Quality Notification

Other Objects MARA Material Number

Other Objects T001W Plant

6
Other Objects LFA1 Vendor
Other Objects KNA1 Customer
Other Objects AUFK Order Number
Other Objects SAFK Run Schedule Header Number
Other Objects MCH1 Batch Number
Other Objects MCHA Batch Record
Other Objects EKKO Purchasing Document Header
Other Objects EKPO Purchasing document Item
Other Objects EKET Delivery Schedule
Other Objects VBUK Delivery Header
Other Objects VBUP Delivery Item
Other Objects CSKS Cost Center
Other Objects EQUI Equipment Number

Using formula for MIC

I have a scenario where I have 3 master inspection characteristics. Characteristic 70 'Before',

Characteristic 80 'After', Characteritic 90 'Difference'. What I would like to know is how to use
the formula functionality to calculate the difference between 70 'Before' and 80 'After' and record
this in Characteristic 90 'Difference' . These are quantitative characteristics with single results
recording (50 samples).

In control indicator of characteristic 90 choose option Calc. charac. in formula tab. As soon as
you do this, system will ask for the formula, you just enter there A00080 - A00070 or any other
calculation formula required by you.

MIC 90 must have these settings:

- Active Record Measure Value control indicator.

- Select the radio button: Calculated characteristic.

In the inspection plan (MIC level):

- Select the MIC 90, go to "Quan Data", Enter the formula C00080 - C00070.

Also, you have this options (Prefix) to use with formulas:

A0 Measured value for single unit

B0 Arith. mean of measur. values for sample
B1 No. of valid measured values for sample
B2 Share of defective units for sample
B3 No. of defects observed in sample
B4 No. of defective units in sample
7
B8 Variance of valid meas. values in sample
B9 Minimum valid meas. value in sample
BA Maximum valid meas. value in sample
C0 Arith. mean of measured values for char.
C1 No. of valid measured values for char.
C2 Share of defective units in char.
C3 No. of defects observed in char.
C4 No. of defective units for char.
C5 Upper limit of tolerance range
C6 Lower limit of tolerance range
C7 Target value of characteristic
C8 Variance of valid meas. values for char.
C9 Minimum valid meas. value for char.
CA Maximum valid meas. value for char.
D0 Function module test

Source inspection :

A source inspection is a quality inspection in which Buyer required the quality check before the material
received. So that he performed the quality inspection at the vendor’s Location.

8
To setup source inspection, you should define inspection type (01 and 0101) in material master QM
View. (MM01)

When requesting source inspection, include the following information:

a) Purchase order number

b) Item number
c) Part number
d) Quantity of parts to be inspected
e) Date source inspection is required
f) Types of inspection required
- In Process
- Final
- Interim
- First Article Inspection (FAI)
g) Contact name and phone number

Go to transaction QI07 and give the material code, vendor, plant and opening period. When you execute
the transaction you would find open purchase orders for the given input data. Select the Purchase Order
you wish to perform Source Inspection and choose Create Inspection Lot. These inspection lot triggers
for inspection type 0101. Against this inspection Lot perform result recording QE01 & QA11.

When finally you received Goods at your premises, then inspection lot will triggered automatically (01)
and perform result recording QE01 & QA11

Transaction QI07 is used for source Inspection process. Source inspection is the activity to carry out
inspection before making GR (Means Inspecting material at external site before it reaches Plant).

Now, How it works?

1. Cretae P.O for the material. For source Inspection, first Inspection lot will be created for P.O. Once P.O
is created it gets upadted in Source Worklist So called QI07.

2. In QI07 initial screen , select Delivery date & req opening period & execute , system list all the P.O list
awaiting for Inspection within Delivery date.
3.Select req line items and click Inspection lot tab in top screen, system gives message on lot created on
save.
4. Once u save , lot will get created automatically in QA32 screen. Message QA150 is on missing Infor
records.

Can Any buddy put some light on how to use 0101 Inspection type in Purchase cycle

9
you can try creating a quality info record with status management.
Choose the status profile QM_P_001.
In this way you will have automatically several step in the supply relationship:

Supply relationship started

Model
Pilot series
Series
Requalific. model requested

At the beginning your record info has status Supply relationship started. After that, with your first goods
receipt you will have an inspectionm lot with inspection type 0101 to reach model status.
After usage decision with acceptance of this inspection lot, you will automatically reach model status.
With the next goods receipt you will have an inspection lot with inspection type 01.
After usage decision with acceptance of this inspection lot, you will automatically reach pilot series
status.
With the next goods receipt you will have an inspection lot with inspection type 01.
After usage decision with acceptance of this inspection lot, you will automatically reach series status.
After that every goods receipt will be with inspection type 01 in series status.
To see this status profile in customizing you can go under Qualit Mnagement > QM in Logistics > QM in
procurement > Define Status of Supply Relationships.

In this way you can define several stages in the procurement process for the material-supplier via Q
record info: you can attach inspection type 0101 to a status of status profile (in Q record info) and define
for it an inspection plan different form the "Series" inspection plan.
In this way, when you receive the first sample from your supplier you have an inspection lot with
inspection type 0101 and an appropriate inspection plan. Moreover, if you defined in customizing, after
the acceptance of the first inspection lot (type 0101) you will reach a status with inspection type 01 and
the "Series" inspection plan.

Material master set up:

10
11
Quality info record:

12
13
Inspection plan (4 plans –for source inspection usage is 501)

Group1:

Operation:

14
Create PO:

Standard PO created under the number 4500017369

Trigger source inspection manually:QI07

15
And save to create inspection lot

16
QE51N : Worklists:

Select lot for result recording:

Enter results:

Take usage discision: QA32

17
Perform GR for PO:

Here posting is in inspection stock since for 0101 we have selected post to inspection stock .We manually
change this to

Unrestricted stock. To post to unrestricted by default ,for 0101 deselect post to inspection stock in
material master.

Material document 4900008056 posted

18
Note:

Status Profile Assigned to Quality Info Record

Use

The supply relationship can run through a sequence of statuses that you define in a status profile.
The sequence of statuses for the supply relationship is updated whenever inspection lots are
accepted in the usage decision.

Dependencies

If you assign a status profile that has a mandatory sequence of statuses to a vendor relationship,
the system creates inspection lots for origin 01 with an inspection type appropriate to the status
of the vendor relationship. You can set this inspection type.

The status profile can also contain further statuses that are not part of the mandatory sequence.

Note

19
Note the additional explanations in the Implemementation Guide, if you want to use this function.

Inspection Type for Insp. Lot Origin (Source Inspection) in q-info record

Inspection type for the source inspection

Use

If you enter an inspection type for inspection lot origin 01 in this field, you can create an
inspection lot for the source inspection within the lead time before the (scheduled) delivery date.

Dependencies

The inspection type must be active in the inspection setup (Quality Management view) of the
material master.

If a status profile is stored in the quality info record for the supply relationship, a goods receipt
inspection takes place instead of a source inspection.

3.If 01 and 0101 is there in material master with post to inspection stock selected for 01 and deselected
for 0101

0101 is assigned in q-infor record ,then stock in PO and at GR IS Q-relevant and posted to quality by
default ,which may be changed at PO/GR level.

Now we remove the check box at Q-inforecord as follows:

20
The status becomes initial :supply relationship executed as per status profile below:

21
Also set QM Procurement is active in material master :

So at GR sytem will ask for certificate .

22
Now create PO:

23
Standard PO created under the number 4500017372 With stock type post to quality
inspection

you can try creating a quality info record with status management.
Choose the status profile QM_P_001.
In this way you will have automatically several step in the supply relationship:

Supply relationship started

Model
Pilot series
Series
Requalific. model requested

At the beginning your record info has status Supply relationship started.

Next you have to perform GR for PO as present status supply relationship started will not
allow creating lot for source inspection in QI07

After that, with your first goods receipt you will have an inspectionm lot with
inspection type 0101 to reach model status.

Perform MIGO to generate a lot with inspection type 0101 .

24
The generated inspection lot :

25
After RR and UD and post to unrestricted the status changes to Model status in info record:

After usage decision with acceptance of this inspection lot, you will automatically reach
model status.

26
 With the next goods receipt you will have an inspection lot with inspection type 01.
After usage decision with acceptance of this inspection lot, you will automatically
reach pilot series status.

We perform another GR for the PO and after RR and UD of the new lot created the status of Q-
info record is as follows:

Here for the material 60-100F the relevant inspection lot is created from quality plan having
usage 5 ,usual for lot origin 01.

27
The status in Q-info record is updated as follows.

With the next goods receipt you will have an inspection lot with inspection type 01.
After usage decision with acceptance of this inspection lot, you will automatically
reach series status.

Here the inspection lot is created with lot origin 01 .The specifications are selected from
Quality plan as follows:

28
I,e after the first GR ,for all subsequent GRs the quality plan selected is for usage 5 :

The status of quality info record changes to series

29
 After that every goods receipt will be with inspection type 01 in series status.
Note:

Can we have inspection type 01(GR insp for PO) & 0101 (Source Inspection) activated at the same time in
the
Material master record for a material.Have you come across such a scenario.What will be the implication
if
both the inspection types are activated.

1) Source Inspection(SI): Well, you need to understand the concept and use of Source Inspection. The
inspection lots created using this are not stock relevant as the material is not inward thru GR at the point
when these lots are triggered. Hence the UD will not have a stock posting tab and if you want a stock
posting tab then it becomes normal inspection (01). Hope you understand the difference, also after
results record & UD if you decide not to have a inspection lot triggered @ GR then you need to update it
in the Q-Info record. The settings for this scenario are already given below.

2) Inspection type (01,0101) can be activated @ the same time.In addition to this you can have a
preferred indicator set for the inspection type you want to be selected when you perform goods receipt.
This check box is available in the inspection type set up in the Material master. If you do not check the
preferred inspection type then the variant 01 for lot origins 01 is given preference.

If you want an inspection type 0101 to be triggered @ SI then you need to define this in the Q-Info
record.

Conclusion :

Different constellations and behavior

Material master (60- Quality info record(60- plan Result

100F) 100F/1000)

01-post to inspection Source inspection Usage 501-Model 1.PO created under the
stock checked/active 0101 number 4500017374

0101-predefined type Source inspection –No 3.Inspection lot by QI07

and post to inspection GR Checked for PO and RR/UD with
stock unchecked/active
30
Qm procurement no stock relevance
active ,control
key,certificate type Status profile - 2.No inspection lot at GR
QM_P_001 and stock posted to
unrestricted.

01-post to inspection Source inspection Usage -501/5 The status profile is

stock checked/active 0101 activated and status
change occurs with
0101- post to inspection Source inspection –No inspection lot processing
stock unchecked/active GR Checked at GR at all status of
Qm procurement Status profile - SCM cycle as
active ,control QM_P_001 demonstrated above.
key,certificate type

01-post to inspection Source inspection

stock checked/active 0101

0101- post to inspection Source inspection –No

stock unchecked/active GR Checked

Qm procurement Status profile -

active ,control QM_P_001
key,certificate type

2.Inspection at GR with Dynamic modification Criteria:

Set up:

Material master : H4-LAMPE

31
 This means a certificate needs to be entered at GR

If a material is activated for QM in procurement, the system initiates the following check whenever
purchasing functions are carried out (for example, when a request for a quotation is made or if a
purchase order is created):whether the vendor's verified QM system, according to vendor master
record or quality info-record (for a combination of vendor/material) meets the requirements for QM
systems as specified in the material masterIn carrying out the check, the system relies on the
defined assignments for target QM systems and actual QM systems in the Customizing application.If
the check is unsuccessful, a warning message is issued when a request for quotation is initiated and

32
Inspection plan:

33
The dynamic modification rule is as follows:

* Maximum Skip Duration

Use

This field is used in the following ways:

To determine the current inspection stage at sample determination

When the quality level is updated

The system first checks the number of skips and then the skip duration.

Inspection lot creation

At sample determination for a lot, if the number of allowed skips has not yet been reached, but
the maximum skip duration has been reached or exceeded, the next stage in the sequence for
accepted lots is taken as the current stage for the inspection lot. If this stage is another skip, then

34
the next stage in the sequence for a rejected lot is taken as the current inspection stage. This
means that the current inspection lot is due for inspection as a result of the maximum skip
duration, although the quality level contains a skip as the next inspection stage.

Update of the quality level

The quality level is updated either at lot creation or when the usage decision is made. The update
occurs independently of sample determination for an inspection lot (even if dynamic
modification takes place at lot creation) and always occurs after the current inspection stage has
been determined for the inspection lot. If the maximum skip duration has been reached or
exceeded, when the quality level is updated, the system calculates the next inspection stage for
the quality level of an accepted lot based on the same algorithm. This means that the following
stage in the sequence for accepted lots is used as the next inspection stage. If this stage is a skip,
the following stage in the sequence for a rejected lot is taken as the inspection stage for the
quality level. Since this stage usually specifies an inspection, the next inspection lot is to be
inspected.

Procedure

You have two options, irrespective of whether dynamic modification occurs at lot creation or
when the usage decision is made:

Option 1

If you want to control the stage change at the skip stage, both by the number of skips and by the
maximum skip duration and create for both criteria a stage change, define your dynamic
modfication rule in the usual way (as described in example 1). Define an additional inspection
(provided that dynamic modification takes place at lot creation).

Option 2

If you only want to interrupt the skip stage with a one-time inspection controlled by the
maximum skip duration, you can assign an additional skip in the dynamic
modification rule. This means that if the lot is accepted, the inspection stage always
changes from one skip to another. At each stage change, if the maximum skip duration
has been exceeded for an inspection lot, a one-time inspection of this lot takes place.

Examples

Example 1

Dynamic modification rule

Stage 1: Initial inspection stage/Inspect
Accepted (OK) Rejected (Not OK)
Number of inspections: 1 Number of rejections: 1
New inspection stage : 2 New inspection stage: 1
35
Stage 2: Skip
Accepted (OK) Rejected (Not OK)
Number of skips : 10 Number of rejections: 1
Max. skip duration : 30 days New inspection stages: 1
New inspection stage : 1

Example 2

Dynamic modification rule

Stage 1: Initial inspection stage/Inspect
Accepted (OK) Rejected (Not OK)
Number of inspections: 1 Number of rejections: 1
New inspection stage: 2 New inspection stage : 1

Stage 2: Skip
Accepted (OK) Rejected (Not OK)
Number of skips : 32600 Number of rejections : 1
max. skip duration : 30 Tage New inspection stages : 1
New inspection stages : 3

Stage 3: Skip
Accepted (OK) Rejected (Not OK)
Number of skips : 32600 Number of rejections: 1
max. skip duration : 30 Tage New inspection stage: 1

Quality plan : operations and MIC:

36
Check another task list: Material T-BQ100

37
Task list usage 5-GR (for PO)

The dynamic modification rule:

Operations:

MIC s:

MIC name Control indicator Catalog/selected Sampling Effect on RR

set procedure

8-101 Summation recording No 100%-0, No of non

sampling procedure, fixed catalog/selected conforming
Qualitative, attributive
scope set in MIC,But units to be
reference char selected set inspection non enterd,if 0
conforming units
assigned in plan * then valuation
Determination is accept
rule 20
100% inspection

9-101 Target,upper,lower,Classed
recording, No of class
reference char 6,class midpoint 70,class
Quantitative width0.20(upper-
lower)/class no

38
 Selected set

For 9-101

For

39
Now create a PO for the material: QTY 100 pcs

40
GR for 100 QTY:

Material doc posted and inspection lot generated:

Now inspection lot processing:

QA32:

Results recording:

OP1:

41
Op2:

Note:

Char 1:

Enter selected set for MIC While creating and maintain classed recording indicator:

42
For characteristics 2:

In the inspection plan you can define the number of value classes, class width and class midpoint for a
quantitative characteristic with inspection results recording in classes. The system determines the upper
and lower class limits for each value class on the basis of these specifications: and also class recording
indicator in MIC:

43
Class Width

Difference between the upper limit and the lower limit of a class.The class width is stored in this
field, if the characteristic is treated as a quantitative characteristic whose values are managed
with classes. The width of the classes is given in the same unit as the target value and the
tolerances.All classes except for the marginal classes have the same width. For additional
information about marginal classes, refer to the documentation about the number of classes.

In this field you can enter EITHER a value or an *. If you enter an *, the system calculates the
class width as follows:
class width = tolerance range / number of classes.You must enter both limit values (the upper and
the lower) as well as the number of classes, so that the system can carry out the calculation
automatically.

For automatic close of result recording:settins at plant level:

Op3:

44
Take UD:

Post Qty Proposal::

45
Note on recording:

QM configurations:

46
1.Basic Settings:

a.Set up Client:

In this IMG activity, you provide the clients in the test system with the standard settings available in the
QM component. You can then use these basic settings to maintain the master data required for your
business transactions and to test the functions in the QM component.

This function is particularly useful, if you:

Have other SAP application components active in a client and you want to implement the QM functions
retrospectively.

Want to update or add to the system settings in the current client after changing a release.

Requirements

You have set up the client according to the general instructions.

Activities

If you did not set up the client as an exact copy of client 000, you can use the transactions listed below to
copy the basic data and default settings for the QM component in client 000 of the standard system to
other clients.

Caution:

No cancellations are possible for these transactions!

Entries that already exist in the target client are not overwritten.

The automatic import protection in the target client is adhered to.

If the automatic correction recording is active, the system draws up a transport request in the target
client that contains all copied entries (you can process category 'Copy Transport' in transaction SE01).

The system only executes the transaction if you have the authorization to create transport requests in
the current client and the transport system is set up correctly in this client.

To copy this data into subsequent target systems or target clients, you only need to transport the request
with its copied data entries.

Caution It is important to note that existing data can be deleted and/or changed when you execute a
transport into another system (not the same as transports that originate in client 000). Therefore, you
should never transport this request into a production system.

47
The following transactions can be used copying basic settings:

QCCC All standard settings

With catalogs

With standard texts

Without number ranges

Without sampling systems

Without tolerance keys

Without forms

QCCP Standard settings for quality planning

QCCW Standard settings for quality inspections

QCCZ Standard settings for quality certificates

QCCM Standard settings for quality notifications With notification-related catalogs

QCCU Standard settings for the QM environment

QCCK Catalog entries; examples

QCCT (standard texts QM_*)

You must copy the standard texts used in the forms into the current client, since there is no automatic
default to client 000 for these texts. There is, however, a default defined for the language in table T002C
in the client.

QCCF (forms QM_*)

You do not need to copy forms into the current client, since the system automatically defaults to client
000, if the required form does not exist in the current client.

QCCS Sampling systems according to ISO 2859 and ISO 3951

QCCY Tolerance keys according to ISO 0286

QCCN (number ranges Q*)

The application programs can only be run, if the number ranges are available in the current client.
The number ranges in the standard system are set up in such a way that you can copy them for most
applications, using transaction QCCN without having to change them. However, if you automatically copy
number ranges from client 000 using transaction QCCN, this leads to inconsistencies, if number ranges
already exist in the current client that overlap with those in the standard system. This is also why the
copying of number ranges is not included in transaction QCCC. Therefore, you must first check whether
48
non-standard number ranges have been set up in the current client and if this is the case, you must
manually maintain the number ranges for:

Inspection characteristics and Inspection methods

Control charts

Inspection plans and reference operation sets

Inspection lots

Physical samples and physical-sample drawing

Condition records for certificate profile determination

Characteristic confirmation numbers

Quality notifications

You must pay particular attention both when grouping notification types and assigning these groups to
the number ranges manually and when copying from the standard client. See text reference and SAP
Note number 52390 in the notes database.

Technical note: to improve the response times, the standard system is set up so that it stores a certain
number interval when numbers are allocated internally. The numbers contained in the buffer are lost
when the application program is terminated. You can define the scope of the number range buffers using
transaction SNRO.

Further notes

Update instead of Insert: If you want to overwrite the existing settings in the current client with the
standard settings from client 000, (instead of supplementing them) you can use the method mentioned
in the transactions above. These transactions process prepared command files with the help of
transaction SM29. To carry out an update instead of an insert, use the transaction SCC1 (in place of
SM29) or the report RSCLCCOP together with the command files stored in the transactions mentioned
above. The system, however, does not record this process in a transport request, as in transaction SM29.
You can display the copy's log with transaction SCC3 or report RSCCPROT.

Transport to Other Clients or Systems:

Customizing tables
All Customzing tables in the QM component have an automatic transport link.

Transporting master data of QM component

See SAP Note 61049 in notes database
We recommend that you maintain master data in the target system, instead of transporing it.

49
Transporting SAPscript objects
See SAP Note 3355 in notes database

B.Settings at clinet level:

Setting Up Clients

In this IMG activity, you provide the clients in the test system with the standard settings available in the
QM component. You can then use these basic settings to maintain the master data required for your
business transactions and to test the functions in the QM component.

This function is particularly useful, if you:

Have other SAP application components active in a client and you want to implement the QM functions
retrospectively.

50
Want to update or add to the system settings in the current client after changing a release.

Requirements

You have set up the client according to the general instructions.

Activities

If you did not set up the client as an exact copy of client 000, you can use the transactions listed below to
copy the basic data and default settings for the QM component in client 000 of the standard system to
other clients.

Caution:

No cancellations are possible for these transactions!

Entries that already exist in the target client are not overwritten.

The automatic import protection in the target client is adhered to.

If the automatic correction recording is active, the system draws up a transport request in the target
client that contains all copied entries (you can process category 'Copy Transport' in transaction SE01).

The system only executes the transaction if you have the authorization to create transport requests in
the current client and the transport system is set up correctly in this client.

To copy this data into subsequent target systems or target clients, you only need to transport the request
with its copied data entries.

Caution It is important to note that existing data can be deleted and/or changed when you execute a
transport into another system (not the same as transports that originate in client 000). Therefore, you
should never transport this request into a production system.

The following transactions can be used copying basic settings:

QCCC All standard settings

With catalogs

With standard texts

Without number ranges

Without sampling systems

Without tolerance keys

Without forms

51
QCCP Standard settings for quality planning

QCCW Standard settings for quality inspections

QCCZ Standard settings for quality certificates

QCCM Standard settings for quality notifications With notification-related catalogs

QCCU Standard settings for the QM environment

QCCK Catalog entries; examples

QCCT (standard texts QM_*)

You must copy the standard texts used in the forms into the current client, since there is no automatic
default to client 000 for these texts. There is, however, a default defined for the language in table T002C
in the client.

QCCF (forms QM_*)

You do not need to copy forms into the current client, since the system automatically defaults to client
000, if the required form does not exist in the current client.

QCCS Sampling systems according to ISO 2859 and ISO 3951

QCCY Tolerance keys according to ISO 0286

QCCN (number ranges Q*)

The application programs can only be run, if the number ranges are available in the current client.
The number ranges in the standard system are set up in such a way that you can copy them for most
applications, using transaction QCCN without having to change them. However, if you automatically copy
number ranges from client 000 using transaction QCCN, this leads to inconsistencies, if number ranges
already exist in the current client that overlap with those in the standard system. This is also why the
copying of number ranges is not included in transaction QCCC. Therefore, you must first check whether
non-standard number ranges have been set up in the current client and if this is the case, you must
manually maintain the number ranges for:

Inspection characteristics and Inspection methods

Control charts

Inspection plans and reference operation sets

Inspection lots

Physical samples and physical-sample drawing

Condition records for certificate profile determination

52
Characteristic confirmation numbers

Quality notifications

You must pay particular attention both when grouping notification types and assigning these groups to
the number ranges manually and when copying from the standard client. See text reference and SAP
Note number 52390 in the notes database.

Technical note: to improve the response times, the standard system is set up so that it stores a certain
number interval when numbers are allocated internally. The numbers contained in the buffer are lost
when the application program is terminated. You can define the scope of the number range buffers using
transaction SNRO.

Further notes

Update instead of Insert: If you want to overwrite the existing settings in the current client with the
standard settings from client 000, (instead of supplementing them) you can use the method mentioned
in the transactions above. These transactions process prepared command files with the help of
transaction SM29. To carry out an update instead of an insert, use the transaction SCC1 (in place of
SM29) or the report RSCLCCOP together with the command files stored in the transactions mentioned
above. The system, however, does not record this process in a transport request, as in transaction SM29.
You can display the copy's log with transaction SCC3 or report RSCCPROT.

Transport to Other Clients or Systems:

Customizing tables
All Customzing tables in the QM component have an automatic transport link.

Transporting master data of QM component

See SAP Note 61049 in notes database
We recommend that you maintain master data in the target system, instead of transporing it.

Transporting SAPscript objects

See SAP Note 3355 in notes database

53
QM-Result recording config

Settings for data transfer in lot and RR(Copying of inspection results)

Origin of results data:

Define parameters for calculated char:

54
55
56
Maintain field name definition as follows:

57
58
Calibration inspection:

Set up:

1. Inspection point- QM-Quality planning-Inspection planning-general-Define identifier for inspection

point

Standard; Equipment 300, F/L—310

Here in valuation we maintain default for acceptance and rejection-plant specific .For this we create
selected set (For Usage decision –Catalog 03 and code group 14) for plant with code group and code and
assign for acceptance and rejection. Unless this is assigned here the UD codes will not appear for UD:

59
2. We have following MIC S:

1. Scurrent –standard current-Numerical –Sample procedure assigned PM-incomplete copy model—

op0010

2. Dcurrent –standard current-Numerical –Sample procedure assigned PM- incomplete copy model—
op0020

3. %Error—Percentage error –Calculated characteristics –Formula assigned during MIC inclusion in task
list-

(C00010-c00020)/c00010*100

4. Recording of results is controlled by setting the indicator:

a. Summation recording-only one value to be entered during RR

b. Individual recording—all individual values to be entered for the sample size

C.Classed recording—value to be entered: Midpoint,, no of class and class width while assigning MIC in
plan or task list while assigning MIC:

D.No characteristics recording

E.Defects recording:

MIC :

60
While assigning MIC to plan or task list:

Follow up action for UD:

Settings for UD and automatic status change for equipment –NPRT and order-TECO following UD

61
QM-Quality inspection-inspection lot completion-define follow up actions

Use

In this step, you define follow-up actions for the usage decisions.

Several processing variations are possible for follow-up actions:

A manual trigger of activities to be carried out manually.

A manual trigger of activities to be processed by the system.

An automatic trigger of activities to be carried out manually -> Workflow link.

An automatic trigger of activities to be processed by the system -> (subject of this step).

The automatically triggered, system-supported follow-up actions are particularly important. You can
define a series of follow-up actions the system will carry out in sequence.

For each follow-up action, you must define the level on which the follow-up action will take effect. The
system carries out automatic follow-up actions when a usage decision has been made for:

An inspection lot

A partial lot in production

Operation completion in results recording

You can also specify the business transaction that is to be linked to this follow-up action and how the
update is to be processed.

62
 Levels at which follow up actions are to activated

Requirements

1.You should have maintained the catalog for the usage decision to such an extent that you only need to
enter the name of the follow-up action in the selected set codes, once you complete this step.

Maintaining the Usage Decision Catalog

The follow-up actions are defined for a code in a selected set of catalog 3 (usage decision). The catalog
does not differentiate between the levels (inspection lot, operation completion, or partial lot), at which
the follow-up action is defined. However, the usage decision transaction checks whether the follow-up
action is valid for the relevant usage decision level, when you choose a usage decision code or change a
follow-up action. To prevent an invalid usage decision code from being chosen, we recommend that you
define the level of the usage decisions or their related follow-up actions when maintaining catalog 3 by
either defining your own code for each level, or creating a separate selected set for each level. If you do
not want to trigger a follow-up action from the usage decision, leave the follow-up function field in the
selected set blank.

Maintain catalog 3-UD catalog:

63
Code group and code:

Follow-up action chains

Quality Management allows you to implement automatic follow-up actions in the form of function
modules. If a follow-up action consists of a series of individual activities, these partial activities must be
numbered in the sequence to be carried out and each activity must be linked to a separate function
module.

Links to operations

If you want to assign an operation from the general status management function to a follow-up action,
the operation must be supported for the inspection lot's object type and it must be compatible with the
status profile assigned to the inspection type. Also refer to the step Define status profile. The F4 help for
the operation field shows you which operations are available for use.
Operations play an important role in managing the statuses of inspection lots. For more information on
this subject, refer to Status Management.

64
To help you select an appropriate operation for a follow-up action, you can display the definitions of
operations that support follow-up actions for usage decisions (you cannot, however, change these
definitions). To do this, proceed as follows:

Display the list of operations. Call up the operations for inspection lots by entering QM*; then select the
desired operation.

Select the function Where-used list (not Follow-up action). In this view you see:

That the operation applies to the object type insp. lot, ...

Which inspection lot statuses this operation sets and deletes

Which other statuses influence this operation

Edit selected set and assign follow up action to selected set code:

65
Create a sampling procedure PM:

If we choose manual valuation then the valuation after result recording is done when we accept the
proposal in the dialog box.

Enter a sample size:

66
Here the valuation mode chosen means that after result recording the valuation will take place according
char attribute-ok or not ok

For this we have to create a code group and codes for catalog type 1 –charactersitics attribute as follows:

67
When you create selected set for UD for catalog type 3 –UD you enter a valuation code –accepted or
rejected.In sample procedure

The valuation is according to characteristic attribute.

Valuation by Code

Use

If you set this indicator, you define the valuation mode using a valuation according to a code.

For a sampling procedure with this valuation mode, valuation occurs using a code that is
assigned a valuation (selected set).

The valuation mode is configured as :

QM-Quality planning –basic data-sample,spc-define valuation mode.

68
The valuation rule is defined as :

To valuate the inspection characteristic or the (partial) sample, the following information is required:

Selected set of the code

Code group of the code

Selected set code

69
This information is transferred to the function module by means of the appropriate fields in the
valuation structure.

Note on valuation :

Define Valuation Mode

In this step, you can:

Define how a decision is made to accept or reject inspection characteristics (valuation mode). These
decisions are used in the sampling procedure.

Integrate your own function modules that allow you to make the decision whether to accept or reject
inspection characteristics.

You must decide which one of the basic forms you want to use. These forms are as follows:

Manual decision
This is required for attributive characteristics (that is, characteristics for which no values are recorded).
These are characteristics you simply accept or reject. This type of decision is also used in all other cases,
where an automatic valuation is not possible or allowed.

Code valuation: a decision on the basis of qualitative attributes.(ONLY FOR QUALITATIVE

CHARACTERSITICS)
The decisions are stored in the catalog for characteristic attributes.(catalog type 1)

Selected set for catalog 1 in plant KSBA:

This selected set is to be assigned to sampling procedure ,but the sampling procedure only supports
summarized recording

A decision based on a sampling plan for discrete characteristics (attributive inspection) with the
following options:

Number of defects
70
Number of nonconforming units

This decision can also be used in conjunction with tolerance specifications for the measured values of
quantitative characteristics.

A decision based on a sampling plan for quantitative characteristics (variable inspection) with the
following options:

Complying with the distribution limits of the characteristic values (s-method)

Complying with the mean value limits of characteristic values (checking the tolerance specifications)
This is a special application of the s-method, where k = 0.

A decision based on a control chart.

You can assign suitable, different valuation rules to these basic forms and thereby define different
valuation modes, such as:

Simple valuation

Manual valuation

Code valuation. This valuation is based on the attributes of qualitative characteristics

Valuation based on the number of defects

Valuation based on the number of nonconforming units

Valuation for the mean value of quantitative characteristics, based on the tolerance specifications

Valuation modes for procedures using sampling schemes:

Valuation according to sampling plan for:

Attribute inspection, for discrete characteristics (in accordance with ISO 2859)

Variable inspection, for continuous characteristics (in accordance with ISO 3951)

The system supports a single-sided and double-sided s-method.

Valuation based on the limits of a control chart

Valuation modes for procedures using independent multiple samples:

Valuation according to the:

Worst case principle

Last case principle

71
Best case principle

The valuation modes for procedures with independent multiple samples are suitable for the valuation of
characteristics in:

Inspections during production with inspection points

Inspection of partial lots

Inspection of physical samples

Inspection of maintenance objects

Standard settings

In the standard system, the table of valuation rules is designed so that all commonly used valuation
modes are supported at characteristic level.

The tables have the delivery class G. The following name range is reserved for the user:

Valuation mode 9*, A*, ... Z*

Valuation mode 9*, A*, ... Z*

SAP Recommendation

Use the valuation modes contained in the standard system.

Do not delete any of the valuation modes contained in the standard system; instead, you can lock the
entries you do not need.

Do not delete any of the valuation rules contained in the standard system and under no circumstances
delete valuation rules A1, A2, A3, A4, A5, since these were used for programming.

You only need to maintain your own valuation rules in special cases.

Activities

1. Determine whether additional or other valuation modes are used in your company. If necessary, you
must also define and program appropriate valuation rules for these valuation modes.

2. Determine whether you need additional or other valuation rules. Define these rules only if required.

a) Substitute the function modules

b) Program your own function modules.

c) Enter the valuation rules in the relevant valuation modes.

Additional Information
72
Valuation Levels

The valuation of an inspection characteristic is usually made up of several steps that take place at the
following levels:

Valuation of original values or value classes

In summarized results recording original values or value classes are not valuated.

Valuation of samples
If the system does not allow for multiple samples, there is no valuation at sample level

Valuation of a characteristic

The valuation rules mentioned above are active at characteristic or sample level. At original value, or
value class level, the valuation rules that are dependent on the control key for the characteristic are fixed
automatically by the system:

Manual valuation

Code valuation for qualitative characteristics with characteristic attributes

Valuation based on tolerance specifications for quantitative characteristics

Definition of Valuation Rules

The valuation rule is usually defined in the valuation mode and is included in this way in the sampling
procedure.
There are two valuation rules for inspecting independent multiple samples; one for characteristic-based
decisions for individual samples and one for characteristic-based decisions for all samples. The valuation
rule that links the decisions relating to the individual samples to a collective decision for the
characteristic is stored directly in the sampling procedure, together with the valuation mode for the
samples.

For inspections with partial lots and inspections with inspection points, for example, inspections during
production, inspection of physical samples or inspection of maintenance objects (equipment or
functional locations), two valuation rules are also required. In these cases, the combining valuation rule
is not stored in the sampling procedure, but taken directly from this table.
If you want to change the collective valuation, you must substitute or change the function module
contained in the following valuation rules:

A1 Manual valuation

A2 Inspection with partial lots

A3 Inspection with inspection points

A4 Inspection of physical samples

73
A5 Inspection of equipment or functional locations

Create a task list with inspection point 300 and above MICs

Inspection point in quality plan/Task list header:

Create an order of order type PM06 and enter reference object(Must for inspection lot generation ) and
also enter other equipments for calibration in the object list. assign the task list group 81 to order by
direct entry..This sequence of data entry is important before release

to assign all equipments to object lists.

74
Release and save the order:

The inspection lot generated is 140000004290

QE71 Result recording: shows all equipments in list

75
Entering values for standard current in detail screen :

Entering values for defective current in detail screen:

76
After calculation for the results:

77
Following things are observed:

1. Valuation proposal comes in dialog box-accept/reject after all 5 entries for the three characteristics
when mean of 5 have been

Calculated. This is due to the manual valuation mode in sampling procedure

2. Default proposal is accept; Needs to be corrected.

3. Calculated value for error is based on mean value of standard and defective in all cases and is always
30.Needs to be corrected.

This is corrected by entering the formula as (A00010-A00020)/A00010*100 for the calculated

characteristics in task list.

Another inspection lot ,created with the task list has now been processed as shown, where % error has
been calculated against individual values of other characteristics and hence 5 different values are
returned.

The parameter A0-Individual value –is stored in QASE Table –Field MESSWERT—measured value

78
The table QASE is updated as follows:

79
Now we maintain target, upper and lower limit in individual MIC:

Now for another lot 140000004292 the automatic valuation occurs with auto close after RR for
characteristics and with individual percentage error calculated.

80
On overall valuation as rejection ,the status of equipment is set NPRT

Now take UD:

AND Create a defect and activate notification.

81
A defect notification 10002063 is created by activating it and

82
Automatic close after save due to setting in plant level:

83
Settings for lot origin 14:

In case of defect the defect notification is created based on notification type entered here:

Note:Identification for the Inspection Point Field Combination

Use

84
To identify inspection points, you can define a combination of fields in Customizing. In such a field
combination, user-defined fields as well as fields fixed by the inspection point type are defined with
individual key words and an individual sequence.

There are inspection point types for equipment, functional locations, physical samples, and production.
These inspection point types can be assigned individually in the user specifications if required. The
following parameter IDs correspond to the following inspection point types:
Parameter ID Inspection point type
QB1 Equipment
QB2 Functional location
QB3 Physical sample
QBK Production

Examples

Wire basket/shift
A wire basket number uniquely identifies for all operations a production quantity for which inspection
results should be recorded. For results recording, the shift should also be entered as additional
information.
At the operation level, an inspection interval is predefined for every 50 units.
You can show this by the following inspection point identifier:

Predefined field dependent on inspection point type (' ')

Field active Key word

User fields Field active Key word

Text Length 18

Text Length 10

No. Length 10 1 Wire basket

No. Length 3 X Shift

Date

Time

By marking the "Field active" column, you can make a field an optional field.
In order that an inspection point can be uniquely identified, the system only considers fields with an
entry between 1 and 6 in the "Field active" column.

85
Vessel/Date/Time
In the process industry, liquids are produced in vessels. This operation can take several days. A sample is
taken on an hourly basis (a time-based inspection interval, interval = 1 hour).
This can be be shown by the following inspection point identifier:

Predefined field dependent on inspection type (' ')

Field active Key word

User fields Field active Key word

Text Length 18

Text Length 10

No. Length 10

No. Length 3 1 Vessel

Date 2 Date

Time 3 Time

Test equipment
Test equipment is monitored in calibration inspections. Choose inspection point type 1 (inspection point
for equipment). The equipment number 1 must be entered as an identifier. Since the equipment is test
equipment, use 'test equipment' as the key word.

This can be be shown by the following inspection point identifier:

Predefined field dependent on inspection type ('1')

Field active Key word

Equipment 1 Test equipment

User fields Field active Key word

Text Length 18

Text Length 10

No. Length 10

No. Length 3

Date

Time

86
Note

Even if the test equipment type allows for certain fields, you can define additional user fields.

If you enter a value for the field combination in the task list header, this value is copied to the inspection
lots.

87