Вы находитесь на странице: 1из 377

QUALITY MANAGEMENT

SAP ECC-6.0

SANJAY KUMAR
QM-CONSULTANT
sanjayerp@gmail.com

1
Quality Management

Table of Contents
1.0 Quality Management - Basic Settings......................................................4
2.0 QM in Logistics..................................................................................17
3.0 Quality Planning.................................................................................46
4.0 Quality Inspection............................................................................136
5.0 Quality Certificates...........................................................................233
6.0 Quality Notifications..........................................................................264
7.0 Environment....................................................................................364

2
Quality Management in the R/3 System
The Quality Management component (QM) is part of the integrated R/3 System. Use the QM
component functions for the following quality management work:
 Quality planning
o Basic data for Quality Management
o Inspection planning
 Quality assurance
o Quality inspection
o Quality certificates
 Quality control
o Quality notifications
o QM information system
The QM component shares master data, in particular the material master, with other components.
It can be triggered from other components and can affect processes in other components.

The QM component is most effective when implemented with the following other components:
 Materials Management MM (Procurement, Inventory Management, Warehouse Management)
 Production Planning PP or PP-PI
 Sales and Distribution SD
 Plant Maintenance PM
 Controlling CO.

The following central components of the R/3 System are typically used with QM, to take full
advantage of its capabilities:
 Production Resources and Tools
 Engineering Change Management for Logistics Master Data
 Document Management and Optical Archive
 Classification
 Workflow
 Logistics Information System

Direct access by this transaction

QCC0 QM: Direct Access to IMG


QCC1 Direct Access to IMG: Notification
QCC2 IMG Direct Access: QM Quality Notification
QCC3 IMG Direct Access: QM Quality Inspection
QCC4 IMG Direct Access: QM Quality Planning
QCC5 IMG Direct Selection: QM Bus. Add-In
QCC_STABI Copy Stability Study Customizing
QCC_STABI_NK Copy Stability Study Number Ranges

3
1.0 Quality Management - Basic Settings

The section Basic Settings combines several work steps that you should take at the beginning of
the implementation project, before moving on to the function-related sections and their
implementation steps.
The settings you make here provide you with a head start in the implementation plan; you must
however alter the settings again during the project after working through subsequent sections.
First Steps
This section provides you with instructions for:
 Applying the Implementation Guide to your system
 Implementation procedures
 The important organizational steps and decisions

IMG Path: Implementation Guide for R/3 Customizing Quality Management.


Transaction Code QCC0

4
Setting up Clients

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 R/3 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.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Basic Settings  Setting up clients.
Transaction Code QCC0

There are the following transactions for copying basic settings:


 QCCC All standard settings
o With catalogs

5
o With standard texts
o Without number ranges
o Without sampling systems
o Without tolerance keys
o Without forms
 QCCF (forms QM_*)
 QCCK Catalog entries; examples
 QCCM Standard settings for quality notifications With notification-related catalogs
 QCCN (number ranges Q*) The application programs can only
 QCCP Standard settings for quality planning
 QCCS Sampling systems according to ISO 2859 and ISO 3951
 QCCT (standard texts QM_*)
 QCCU Standard settings for the QM environment
 QCCW Standard settings for quality inspections
 QCCY Tolerance keys according to ISO 0286
 QCCZ Standard settings for quality certificates
 QCE2 Edit Communication Support
 QCE3 Display Communication Support
 QCYF QM standard forms (general)
 QCYT QM standard texts (general)

Maintain Settings at Client Level

You can change several controlling functions.


These controls relate to different components in the QM component; for technical reasons they are
collated in a single table.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Basic Settings  Setting up clients.
Transaction Code QCC0

6
7
Replacement of Master Inspection Characteristics
If you set this indicator, you can replace old versions, which are in task lists and material specifications,
immediately with the new version when you create a new inspection characteristic version.
When the inspection characteristic is saved, the system creates a list in which it displays where the
characteristic is used. You can then replace specific old versions with the new version.

Replacement of Inspection Method


If you set this indicator, you can replace old versions that are in task lists with the new version when you
create a new inspection method version.
When you save the inspection method, the system creates a list, which shows where the inspection method is
used. You can then replace specific old versions for the inspection method with the new version.

Quality Score
Quality scores are used for the quantitative valuation of the quality of inspection lots.
The system allows quality scores ranging from 1 (extremely bad) to 100 (very good).
You may enter the upper limit for quality scores from within this given range.

Maintain Settings at Plant Level

8
You can change and supplement several central controlling functions at plant level:
These controlling functions relate to the planning and implementation of quality inspections; for
technical reasons they are collated in one table. The functions you want to use for quality
inspections determine which settings are relevant for your requirements.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Basic Settings  Setting at Plant Level.
Transaction Code QCC0

9
Requirements
To be able to make comprehensive settings for the functions you want to use, you must have
maintained the following master data and Customizing tables:
 Master data
 Usage decisions
 Sampling procedures
 Customizing tables
 Characteristic weighting
 Defect classes
 Field combination for inspection points
 Storage locations (coordinate with inventory management)

If you want to record quality costs, you need


 Controlling areas,
 Cost centers and
 Order types for appraisal and nonconformity costs.

10
Insp. Characteristics Are Maintained with History
If you set this indicator, all released versions for the inspection characteristics are stored. If you
access a released version using the function "Change inspection characteristic", the system creates
a new version.

Inspection Methods Are Maintained with History


If you set this indicator, all released versions of the inspection methods are stored. If you access a
released version using the function "Change inspection method", the system creates a new version.

11
To set “Number of
containers required”
for goods receipt”.

Recording of the No. of Containers for Inspection Lot


If you set this indicator, you can or must enter the number of lot containers in the inspection lot on
the item detail screen when you make an inventory posting.
In addition to the number of lot containers, you can also enter a unit of measure for the
containers. Set-The Physical-sample drawing by number of containers must be set.
Inspection Type for Available Stock in Quality Inspection
The system creates inspection lots using the inspection type entered here, if quality inspection
stock is available when a stock-relevant inspection type is activated. This applies to quality
inspection stock, which is not managed by inspection lots.
Order Type for QM Orders with Single Assignment to Insp. Lot
Order type for individual QM orders that are assigned to an inspection lot.
This order type is used for the creation of individual QM orders when an inspection lot is created.
The settlement rule assigned to these orders calls for a full settlement.
Order Type for Long-Running QM Orders
Order type for general long-running QM orders.
This order type is used during the creation of QM orders with the transaction "Creating and
assigning QM orders to materials".
The settlement rule assigned to these orders calls for a periodic settlement.

Sampling Method (Proposal)

12
The sampling procedure entered here is used for determining samples whenever sampling
procedures have not been assigned to characteristics. This does not apply, however, in the case of
inspections with inspection points.
Weighting of the Characteristic
A classification of inspection characteristics according to their importance. For example, you can
classify characteristics as critical, major, or minor.
The importance of a characteristic (or characteristic weight) and its controlling effects are defined
in the Customizing application.
Defect Class
Categorizes the possible defects into classes according to a defect valuation based on the results
caused by the defect.
Defects are usually assigned to one of three classes: critical defect, major defect, or minor defect.

Recording of Summarized Statistics


Means that the results recording will always be summarized if n = 1 (for example when inspecting
one unit or 1 ml).

13
Marginal Classes up to the Plausibility Limits
Means that for quantitative characteristics with classed-value recording the system creates the
marginal classes up to the plausibility limits of the characteristic.
For quantitative characteristics you can define plausibility limits in the inspection plan. If you do
not define the plausibility limits the system determines them on the basis of the plausibility factor
defined in the plant-level setting.
If this indicator is not set the marginal classes have no limits.

Factor (%) with Which the Plausibility Limit Is Calculated


If plausibility limits are not set for a quantitative characteristic in the plan, this factor (a
percentage) is used along with the tolerance limits to calculate the plausibility limits for results
recording.
The plausibility limits are calculated on the basis of the tolerance limits as follows:

Plausibility factor: 200%

Upper tolerance limit: 150


Upper plausibility limit: 300
Lower tolerance limit: 50
Lower plausibility limit: 25
Number of Additional Decimal Places for
Statistical Values
Indicates the number of additional decimal places used when summarized values are displayed in
the results recording; the mean and standard deviation, for example.
The number of additional decimal places is not used for calculations. Internal calculations are
always carried out with maximum precision.

Starting Value for the Assignment of Sample Numbers


For characteristics for which multiple samples are defined, the system determines the sample
number from the starting value, when creating the first partial sample for a characteristic within
results recording.
The sample number that is determined by the system for the new partial sample is only a default
and can be changed within results recording.

Key for Configuration of Recording Function


Configuration key that can control the process flow in results recording

14
You can use recording configuration to automate the process flow in results recording. Other
requirements need to be considered, depending on which indicators are set for the configuration
key.
The configuration key is defined in Customizing and stored in the QM plant settings. The indicator
for the configuration key can also be stored as a user parameter. The user parameter takes
precedence over the plant settings.
In the example, the following indicators are set for the configuration key:
 Skip characteristic overview
 Automatic close on entering
 Auto. goto object
 Auto. goto operation

Message Category if There Are Too Many Decimal Places


Message category that is displayed at results confirmation.
You can use the message category to change the procedure used when the number of planned
decimal places is exceeded in results confirmation.

Identification for the Inspection Point Field Combination


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.

Partial Lot Assignment in an Inspection during Production


You can use the entry in this list field to set the detailing levels for the assignment of manufactured
quantities.
1. Partial lots not defined - the manufactured partial quantities are assigned to inspection
points for which inspection results are also recorded.
2. Partial lot for each inspection point - the partial quantities, to which the inspection points
are assigned, are combined into partial lots.
3. Partial lot and batch for each inspection point - partial lots are combined into batches.
Procedure
You can define partial lot assignment in the task list header or refer to the default values at plant
level.
 If you define partial lot assignment in the task list header, this specification overrides the
default values at plant level.
 If there is no entry in the task list header, this means that the default value at plant level is
used.
 If no entry exists in the default values at plant level, this means that partial lots are not
defined.

Proposal for Inspection Point Valuation (Manual valuation)


Code for Inspection Point Valuation
This code is proposed automatically for valuating the inspection point, if no codes for the
acceptance or rejection have been given in the inspection point definition.
You can change these default valuations when you record results.

15
Controlling area,
Cost center: Scrap and
Cost center: Destroyed are
mandatory fields for Scrap
and Sample usage posting.

Storage Location for reserve


The storage location used for stock management of the sample that is kept in reserve after an
inspection. The storage location should not be indicated as relevant for MRP.

Waiting Time (Minutes) Since Insp. Lot Creation for Skip Lot
Before the system can make an automatic usage decision for inspection lots with skip status, the
delay time (in minutes) must have already expired since the lot was created.

Waiting Time in Hours and Minutes Since Insp. Lot Creation (Auto. UD)
The number of hours entered here must have expired after creation of the lot, before the system
makes an automatic usage decision for the corresponding inspection lot.

Batch Valuation Possible Without Specification


If you set this indicator, a link between the master inspection characteristics and the class
characteristics for the batch class must exist when an inspection lot is created, for batch valuation
to occur when the usage decision or inspection point valuation is made. A link within the material
specification is not required.

16
Selection Period for Inspection Lot Processing in Days
To calculate the starting date of the selection time period, the value you enter here is subtracted
from the current date.

2.0 QM in Logistics

17
This section describes Customizing activities that control quality management in the logistical
processes.
The material master record is the most important integration element for the application
components in Logistics.
The material master record (short form: material) contains the material status that influences
critical business processes in the logistical chain. The material status is present in the views of all
relevant components.
The specific view in Quality Management for the material is activated in Customizing for the
material type. The QM view contains controlling functions for QM in procurement, as well as the
control of inspection lot processing.
QM in Procurement
The QM component provides a number of controls you can use, depending on your requirements.
These QM controls apply in part to a specific:
 Material and plant
 Vendor
 Combination of material, vendor and plant
Accordingly, these controls are stored in part in the:
 Material master (material)
 Vendor master (vendor)
 Information record (info record) for a combination of material and vendor; (the combination
of material and vendor is referred to in the following section as the supply relationship).
Define Control Keys
You define the control keys for QM in procurement.
The control keys in the material master are defined at plant level.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
QM in procurement  Define Control Keys.
Transaction Code QCC0

18
Activities
1. Determine which material groups can have the same control settings.
2. Define the control keys for each material group.

19
Vendor Release Required for Regular Delivery
If you set this indicator, the supply relationship must be released before any procurement
activities can take place.

Block Invoice
If you set this indicator, the payment of the invoice is blocked with blocking reason I (I =
Inspection), if you want to prevent automatic payment of the invoice from a QM standpoint.
If this indicator is set, when the invoice is created, the system determines whether an inspection
lot exists and if necessary, sets blocking reason I.(FB01)
This occurs in the following instances:
 There is still no usage decision for the inspection lot.
 The inspection lot is rejected.

20
Certificate Required
If this indicator is set, a certificate must be submitted with the delivered goods.
With requests for quotations and purchase orders, the vendor is informed of the certificate
requirement and certificate type.

Block Is Inactive
If you set this indicator, you deactivate a block in the vendor master or in the quality info record
that has been set for quality reasons.

Notification Type when Blocking Function Is Active


In this list field, you define the type of message (information, warning, error) issued by the system
when the corresponding block is active. The block can either be set in the vendor master record, or
in the quality information record.

21
GR Control for Rejected Source Inspection Lot
Using this field you define how the system reacts when a goods receipt is posted, when the
indicator Source inspection instead of goods receipt inspection is set in the Q info record,
and the corresponding source inspection lot was refused. You choose, if
 A goods receipt is allowed despite the above
("Source inspection lot has no effect on the goods receipt")
 A new inspection lot is created at goods receipt
("Create new inspection lot")
 The goods receipt is not allowed
("Goods receipt not allowed")
First Batch in Source Inspection Lot: GR Control
Your entry in this list box controls the creation of a new inspection lot at goods receipt of a batch
material, if the batch in the goods receipt document is different from the batch given in the source
inspection lot.
If you decide to create an inspection lot, this occurs under the following preconditions:
 No batch was entered in the source inspection lot.
 A batch was entered in the source inspection lot that differs from the batch that was
entered in the goods receipt document.
 The vendor batch is contained in the source inspection lot, but it differs from the vendor
batch in the goods receipt document.
Define Keys for Certificate Processing

22
You define certificate types for quality certificates and the controlling functions linked to the
certificate type for QM in procurement.
The certificate type is stored in the material master at plant level.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
QM in procurement  Define Keys for Certificate processing.
Transaction Code QCC0

23
Certificate Type
Defines the content of a quality certificate.
The definition of certificate types applies to the following activities:
o Certificate processing in procurement
o Certificate creation
Use
 In procurement, you can use the certificate type to control a number of functions that have
been defined in Customizing. The certificate type is specified in the QM data of the material
for this purpose.
 For certificate creation, you can use the certificate type to control the statuses in the
certificate profile. The certificate type is specified in the certificate profile. The status profile
is assigned to the certificate type in Customizing.

24
Activities
1. Find out which controlling functions are linked to the certificate type and decide which of these
functions you require.
2. Define appropriate certificate types for the material groups that require certificates.
3. Define the controlling functions linked to the certificate type.
4. If you want to use the enhanced certificate processing, (which includes management of the
certificate receipt), you must maintain a number range for the receipt of the certificate.
5. You can also receive certificates by data transfer. For the required implementation step, see the
section Quality Certificates / Output Processing.

25
Certificate Required for Each Purchase Order Item
If you set this indicator, a certificate has to be received for every purchase order item.

Certificate Required for Each Delivery


If you set this indicator, the receipt of a certificate must be confirmed for each goods receipt. A
precondition for this is that the Certificate required for a purchase order item is set.

Explicit Inspection of GR Certificate Necessary


If you set this indicator, at goods receipt the system will generally perform as described in the field
"Control without certificate".
This means that even if you confirm the certificate receipt at goods receipt, and thereby set the
status "2 - Certificate received", the system will still perform as specified in the field "control
without certificate". See Control without certificate.
You can confirm that you have checked the content of the certificate in the certificate
transaction or when making the usage decision.

Control if Certificate Is Not Available


Type of control used by the system if the certificate required at goods receipt is not provided. The
deciding factor is whether or not an inspection lot is created at goods receipt.

26
Enhanced Certificate Processing Active
If you set this indicator, extended certificate processing is active for this certificate type. You can
then manage the inbox for quality certificates independent of the goods receipt.

Prevent Certificate Confirmation at GR


Defines that there is no opportunity to confirm the certificate receipt at goods receipt.
If you set this indicator together with the Enhanced certificate processing indicator, the
certificate receipt cannot be confirmed for this certificate type at goods receipt.  You must therefore
confirm receipt of the certificate independently of the goods receipt posting.

Reminder Deadline (Days)


Number of days after the goods receipt, after which a reminder can be generated, if the quality
certificate has not been received.

Escalation Deadline (days) After Sending Reminder


The number of days since goods receipt after which certificate receipt escalates.
The period should be greater than the reminder period.

27
28
Certificate Required for Each Purchase Order Item
If you set this indicator, a certificate has to be received for every purchase order item.

Certificate Required for Each Delivery


If you set this indicator, the receipt of a certificate must be confirmed for each goods receipt. A
precondition for this is that the Certificate required for a purchase order item is set.

Explicit Inspection of GR Certificate Necessary


If you set this indicator, at goods receipt the system will generally perform as described in the field
"Control without certificate".
You can confirm that you have checked the content of the certificate in the certificate transaction
or when making the usage decision.

Control if Certificate Is Not Available


Type of control used by the system if the certificate required at goods receipt is not provided. The
deciding factor is whether or not an inspection lot is created at goods receipt.

Enhanced Certificate Processing Active


If you set this indicator, extended certificate processing is active for this certificate type. You can
then manage the inbox for quality certificates independent of the goods receipt.

Prevent Certificate Confirmation at GR


Defines that there is no opportunity to confirm the certificate receipt at goods receipt.
If you set this indicator together with the Enhanced certificate processing indicator, the
certificate receipt cannot be confirmed for this certificate type at goods receipt.  You must therefore
confirm receipt of the certificate independently of the goods receipt posting.

Reminder Deadline (Days)


Number of days after the goods receipt, after which a reminder can be generated, if the quality
certificate has not been received.

Escalation Deadline (days) After Sending Reminder


The number of days since goods receipt after which certificate receipt escalates.
The period should be greater than the reminder period.

29
30
31
Internal (' ') or external ('X') number range flag
Indicator which determines whether the number range interval is external or
internal.

Define Delivery Block

32
You define the keys to block supply relationships.
Depending on whether the block applies to all materials or only certain materials for a vendor, the
blocking key is contained in the vendor master or in the quality information record for a
material/vendor combination.
The key allows you to block the following business transactions:
 Request for quotation
 Selection during source determination
 Purchase order
 Goods receipt

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
QM in procurement  Define Delivery Block.
Transaction Code QCC0

Activities
1. Together with the purchasing and inventory management departments, determine which
blocking options are used in your company and how the system and the persons responsible will
respond, in the event of a block.
2. Replace the blocking keys in the standard system with the keys that are needed in your
company.

33
3. Set the system message type according to the arrangements made with the purchasing and
materials management departments.

Blocking Function for Quotation Request


If you set this indicator, a request for quotation relating to the corresponding material or vendor is
not allowed.
Blocked for Source Determination
If you set this indicator, the vendor is blocked for the source determination procedure.
Purchase Order Blocking Function
If you set this indicator, a purchase order for the relevant material or vendor is blocked.
Goods Receipt Is Blocked
If you set this indicator, the goods receipt is blocked for a vendor or for the combination of a
material and vendor.

Define Document Types

34
You define the document types for the exchange of quality documents with vendors.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
QM in procurement  Define Document Type.
Transaction Code QCC0

35
Standard Settings
Two document types have been defined in the standard system for QM in Procurement:
Q01 - quality assurance agreement with vendors (QAA)
(Stored in the info record for the material and vendor supply relationship)
Q02 - technical delivery terms (TDT)
(Stored in the material master)

36
Define QM Systems

You define models for the verification of quality management systems (QM system for a vendor).

Activities
1. Determine the requirements that exist for vendor QM systems in your company. Note that such
requirements may stem from the requirements of your customers.
Define the target QM systems in the table.
2. Determine which actual QM systems your vendors use. If you want to valuate these systems,
define a valuation profile.
Define the actual QM systems and their valuation.
3. Assign the target QM system to the actual QM system whose requirements it fulfills. You must
do this in the following steps:
o Make all obvious assignments. For example, the QM system that conforms to ISO/TS
16949:2009 also conforms to the requirements of ISO 9001:2008.
o In those cases where you first have to check the specifications of the QM systems and the
certification requirements, supplement the assignment list as necessary.

37
Certified QM System - Skip
Causes the lot to be skipped on the basis of the certificate status. If you set this indicator, no
inspection lot is created even though there is an active inspection type in the inspection setup for
the material.
 If you enter a certified QM system in the vendor master record, the skip lot applies to all the
materials supplied by the vendor.
 If you enter a certified QM system in the info record for controlling QM in Procurement, the
skip lot only applies to one particular combination of material, vendor and plant.
A certified QM system that has been entered in the vendor master record can be made ineffective
in the QM info record for a particular material and plant using the inspection control identifier.

38
Target QM System for Vendor
This key and the associated description enable you, as a customer in a supply relationship, to
define the requirements of QM systems for your materials.

39
Define Status of Supply Relationships

You define status profiles for the supply relationships and assign an inspection type to the statuses
in the profile.
In the status profile, you can specify that the delivery of a material from a vendor must pass
through a number of statuses, for example:
 Model series
 Preliminary series
 Regular delivery
You can assign different inspection types (with corresponding task list usages) to a status. The
system then selects the appropriate inspection types and inspection plans based on the status of
the supply relationship.

40
41
Activities
1. Determine whether the supply relationships must pass through certain statuses and if this is the
case, maintain the corresponding status profiles for the object type QINF.
For a detailed description of the general status management function,
refer to the chapter Basic Settings and Environment, Central Functions, status profile.
2. If necessary, assign an inspection type (which indirectly assigns a task list usage) to the
statuses in the profiles.
3. Store the status profiles in the quality info records (QM control in procurement) for the relevant
materials, vendors and plants, and set the current statuses for the supply relationships.

42
43
44
QM in Production

The settings described in the subsection 'Quality Planning' / 'Basic Data' also apply to the quality
planning activities in production; otherwise, no other special settings are necessary.
The settings described in the sections 'Quality Inspection' and 'Quality Notification' also apply to
the quality management activities in production. In particular, refer to section inspection for a
production order.
The inspection planning function for routings, rate routings and master recipes allows you to define
inspection points and their corresponding partial quantities.
You can assign partial lots to the quantities of materials associated with certain inspection points
(in a ratio of n: 1). you can then make usage decisions for the partial lots and trigger automatic
follow-up actions with each usage decision. If you manage your material stocks in batches, you
can assign the partial lots to batches (in a ratio of n: 1).
If you carry out inspections during production on the basis of inspection points, you can not only
record the inspection results for an inspection lot, but you can also confirm the actual values for
the production order. Make sure you consider the following settings for this purpose: The control
key for the operation (confirmation) the settings for order type and order confirmation.
Depending on the production type and the desired functions, there are several settings that affect
the production planning functions themselves. For details, refer to the Implementation Guides for
Production and for production planning in the Process Industry.
Determine whether you want to intervene in the release of the production process with the help of
the MM/PP status. Coordinate your activities with the production department and take an active
part in defining the status.

QM in Sales and Distribution

To control quality management in Sales and Distribution, the QM component contains an info
record for the supply relationship, (that is for the object type’s customer or for the object types
customer, sales organization and material).
 You can use the info record to:
Define whether inspection lots should be created for a delivery and how the inspection is to
be integrated in the delivery process.
You make the settings required for this in the section Quality Inspection, Inspection Lot
Processing, Inspection Lot Creation Inspections in SD.
 Store documents that are to be managed by the general document
management functions. For more information, refer to the section Environment, Central
Functions, Define document types. See the Cross-Application Functions; section Document
Management System for more information on document management settings.
You can set a status in the Sales and Distribution data for the material that you can use to control
the release of the Sales & Distribution functions. You set the material status independently of the
plant, dependent on the sales organization and distribution channel. The status takes effect from a
specified date. The material status from the SD view supplements the material status from the
MM/PP view that you use to control the release of materials management and production functions.
See also the sections QM in Procurement and QM in Production.
You can add quality certificates to the delivery. There is a separate Implementation Guide for this
in the section Quality Certificates.

45
3.0 Quality Planning

This section describes the Customizing settings for quality planning.


In the Inspection Characteristic section, you can find additional conceptual information on
Customizing and how to maintain inspection characteristic master records that can be applied to
other master data types.
In the Inspection Planning section, you can find additional conceptual information on
procedures.
In the Samples and SPC section, you can find specific conceptual information on the planning of
samples and statistical process control with the help of control charts.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Planning  Basic Data.
Transaction Code QCC4

46
Basic Data

You use this section to customize and maintain specific master data, called basic data, since it can
be a reusable building block in various higher-level objects (for example, in inspection plans). This
data includes:
 Catalogs
Catalogs are used for the following functions:
o Values of qualitative characteristics
o Defect characteristics (such as defect type, defect cause, ...)
o Usage decisions (for inspection lots, partial lots, inspection points)
o Catalog profiles for quality notifications
 Master inspection characteristics and inspection methods
 Sampling procedures, sampling schemes, dynamic modification rules and sample-drawing
procedures

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Planning  Basic Data.
Transaction Code QCC4

47
Define Defect Classes

You define the defect classes that are used to valuate the defects qualitatively on the basis of the
defect consequences.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Planning  Basic Data.
Transaction Code QCC4

These defect classes are used in the following places or for the following purposes:
 In the selected sets for catalog 1 (characteristic attributes)
 In catalog 9 (defect types)
 For the valuation of characteristic inspection results

For each defect class, you can specify:


 A quality score
 Whether a characteristic attribute in catalog 1 with this defect class can be valuated as
acceptable
 Whether the following can be activated:
o Workflow event
o Quality notification

48
Quality Score
Standard statistical value for valuating the quality of an inspection lot.
The procedure for determining the quality score (quality score procedure) is defined in
Customizing and assigned to the material or inspection object using the inspection type.

Defect Class Allowed for Valuation 'A'


If you set this indicator, when maintaining the code for a selected set of catalog type1 (characteristic
attributes) you can also enter the defect class, even though you entered the valuation "A" (accepted).
If you do not set this indicator, you can only enter the defect class, if you enter the valuation "R" (rejected)
for the code.

Triggering Workflow when Generating Defect Record


If you set this indicator, and the quality notification in which the defects data is recorded is not active, the
Workflow event "defects Created" is triggered when a defect record is generated in results recording for an
inspection lot.

Activation of Q-Notification While Generating Defect Record


If you set this indicator, the quality notification (already existing) is immediately activated, when the defect
data record is created. This means, that the quality notification receives the status "Outstanding notification"
(OSNO).

49
50
51
Define Catalog Types

You define the terminology catalogs and catalog languages you need, in addition to those
contained in the standard system.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Planning  Basic Data  Catalog  Define Catalog Type.
Transaction Code QCC4

Catalog
Main category by which code groups and codes are classified according to their contents (e.g.
characteristic attributes, defect types, usage decisions).
Maintain the master records for the catalogs you previously defined, in the following sequence:
a) Code group, code (at client level)
b) Selected set (at plant level)
The following catalogs have additional functions:
o 1 Characteristic attributes
o 2 Tasks
o 3 Usage decisions
o 9 Defect types
 You can only use catalogs 1 and 3 in conjunction with selected sets.
A valuation of the codes in the selected sets is obligatory.
 Selected sets are defined at plant level in the user language.
 For catalog 2, or for other catalogs that are used as task catalogs in quality notifications,
you can define follow-up actions at code level in the code groups.
 For catalog 3, you can define follow-up actions at code level in the selected sets.

52
Catalog 1: Characteristic attributes
You need this special catalog to record inspection results; in it you define the value range for
qualitative inspection characteristics.

53
Catalog 2: Tasks
You need this special catalog for the quality notifications. You can define automatic follow-up
actions for tasks.

54
Catalog 3: Usage decisions
You need this special catalog for inspection lot completion. You can only access the usage
decisions using selected sets. You must maintain the following additional control fields for each
code contained in a selected set:
 Valuation of the inspection lot
 Quality score
 Follow-up action

55
56
Catalog 9: Defect types
You use this special catalog to record defects in quality notifications. In this catalog, you must
define a defect class for each code contained in a code group.

57
Edit Catalogs

You maintain the catalogs you require for the inspection characteristics. The following catalogs are
usually delivered with the standard system:
 Catalog 1: Characteristic attributes for qualitative characteristics
you must create selected sets at plant level for this catalog.
 Catalog 9: Defect types

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Planning  Basic Data  Catalog  Edit Catalog.
Transaction Code QCC4

58
Inspection Characteristic, Inspection Method

You use this section to customize and maintain inspection characteristics and inspection methods.
Master inspection characteristics and inspection methods are defined at plant level.
Master inspection characteristics can reference inspection methods and catalogs.
You want to reference
 Inspection methods and catalogs from the master inspection characteristics, you must
have previously maintained the corresponding master records.
 If you want to classify the master inspection characteristics or inspection methods you must
have maintained the Classification System.
Prerequisites
If you want to reference
 Inspection methods and catalogs from the master inspection characteristics, you must
have previously maintained the corresponding master records.
 If you want to classify the master inspection characteristics or inspection methods you must
have maintained the Classification System.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path: Quality Planning  Basic Data  Inspection Characteristics,
Inspection Method.
Transaction Code QCC4

59
Define Default Values for Control Indicators

You define control keys for the attributes of inspection characteristics.


The control key is used to propose or predefine the control indicators for the master inspection
characteristics and inspection plan characteristics.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path: Quality Planning  Basic Data  Inspection Characteristics,
Inspection Method  Default values for Control Indicators.
Transaction Code QCC4

Quantitative Characteristic
If you set this indicator, it causes the characteristic to be treated as a quantitative characteristic.

Default Control Indicators Cannot Be Changed


Set this indicator to specify that the control indicators that were defined for the inspection
characteristic using a control key cannot be changed.

Activities
1. Determine which control indicators or characteristic attributes exist and which are important to
you.
2. Determine which basic types of characteristics are commonly used in your company and how
they can be displayed using these control indicators.
3. Define mnemonic short texts for these basic types.
4. Maintain the table for the control key default values.
5. Test the effect of the control keys when you record results.

60
Define Characteristic Weighting

You define the characteristic weights.


You can define weight classes for the characteristics according to any desired criteria. For each
weight class, you can specify a weight factor that determines whether a skip will be allowed for a
characteristic belonging to this particular weight class.
In certain procedures, characteristic weights are used to calculate the quality score.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path: Quality Planning  Basic Data  Inspection Characteristics,
Inspection Method  Define Characteristics Weighting.
Transaction Code QCC4

Activities
1. Define the desired characteristic weights and their attributes.
2. Define a default value for the characteristic weight in the menu option Settings at plant level.

61
Weighting Factor for Evaluations
Determines the proportion the individual valuation criteria contribute to the calculation of the
quality score.

No Skip Allowed
If you set this indicator, no skip (skip lot) can take place.
If you set this indicator, when calculating samples the system chooses the next inspection stage
contained in the dynamic modification rule that is not a skip, instead of the skip stage that has
been predefined by the quality level.

62
63
64
Define Estimation Procedure for Fraction of Defects

You can define your own processes to estimate the fraction of defects using the characteristic
inspection results. There are the following fraction estimates:
 Nonconforming units (with regard to a characteristic and in the inspection lot)
 Characteristic values outside of the tolerance range
The keys for the procedure are defined in the inspection characteristic.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path: Quality Planning  Basic Data  Inspection Characteristics, Inspection
Method  Define Estimation Procedure for Fraction of Defects.
Transaction Code QCC4

Standard settings
In the standard system, fraction estimates have been maintained for the following distributions:
 Binomial distribution
 Poisson distribution
 Normal distribution

65
66
Recording the Number of Defects
If you set this indicator, you can enter the number of nonconforming units and the number of
defects during results recording
If you do not set this indicator, you can enter the number of nonconforming units during results
recording.

67
Measured Values Must Be Recorded
If you set this indicator, measured values for this quantitative characteristic have to be inspected
and confirmed.

68
Define Number Range

You maintain the number ranges for inspection characteristics and inspection methods.
You must define independent number ranges for each plant.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path: Quality Planning  Basic Data  Inspection Characteristics, Inspection
Method  Define Number Range.
Transaction Code QCC4

69
Standard Settings
The following number ranges are available for inspection characteristics and inspection methods:
 01 for internal number assignment
 02 for external number assignment
No other number ranges are allowed for purely numeric names of inspection characteristics and
inspection methods; you can only define the number interval.
The system checks the names of alphanumeric inspection characteristics and inspection methods to
make sure they are explicit.

70
71
Internal (' ') or external ('X') number range flag
Indicator which determines whether the number range interval is external or internal.
The SAP system issues the numbers for internal number range intervals automatically. This number
is between the from-number and the to-number. The last number issued is logged in the current
number level.
You need to enter a number for external number issue. The number you enter needs to be between
the from-number and the to-number.

Activities
For each plant, define the ranges for the externally and internally assigned numbers.

72
Sample, SPC

This subsection describes how to implement sampling procedures, sampling schemes,


dynamic modification rules, sample-drawing procedures and control charts.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Planning  Basic Data  Sample, SPC.
Transaction Code QCC4

73
Define Sample Determination

You maintain:
 Sampling types
 Rules for determining the sampling instruction
The sampling type defines the basic conditions for determining the sample size for each inspection
characteristic. A distinction is made between certain basic forms, such as:
 100% inspection
 Fixed sample
 Percentage sample
 Sample according to the sampling scheme
To define or adapt the rules for determining samples, integrate the function module responsible for
determining the sampling plan in your system. These rules form part of the function that supports
the sampling type and are therefore dependent on the same parameters as this sampling type.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Planning  Basic Data  Defined Sample Determination.
Transaction Code QCC4

74
Activities
Determine whether you need sampling types and sampling rules in addition to those contained in
the standard system.
1. Maintain the additional sampling types.
2. Maintain the additional rules for determining samples. Ensure that the necessary function
modules are programmed.

75
Sampling Type Cannot Be Used
If you set this indicator, the corresponding sampling type cannot be assigned to a sampling
procedure.

76
77
78
Define Inspection Severities

You define the inspection severities that can be used for dynamic modification.
Internationally used standards (for example, ISO 2859) define several inspection severities; for
example, normal, reduced and tightened. In addition, these standards also propose several skip
stages that do not have inspection severities assigned to them.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Planning  Basic Data  Defined Inspection Severities.
Transaction Code QCC4

Use in “DMR with


sampling procedure”

Activities
Define the desired inspection severities.

79
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.
The decisions are stored in the catalog for characteristic attributes.
 A decision based on a sampling plan for discrete characteristics (attributive inspection) with
the following options:
o Number of defects
o 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:
o Complying with the distribution limits of the characteristic values (s-method)
o 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:
o Attribute inspection, for discrete characteristics (in accordance with ISO 2859)
o 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:
o Worst case principle
o Last case principle
o 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

80
Implementation Guide for R/3 Customizing  Quality Management 
IMG Path:
Quality Planning  Basic Data  Defined Valuation Mode.
Transaction Code QCC4

81
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.
o Substitute the function modules
o Program your own function modules.
o Enter the valuation rules in the relevant valuation modes.

82
Valuation Mode Cannot Be Used
If you set this indicator, the corresponding valuation mode is not assigned to a sampling
procedure.

83
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.

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
 A5 Inspection of equipment or functional locations

84
85
Statistical Process Control

You make the necessary preparations to use control charts.


In the Customizing application for control charts, you define:
 Which charts will be available
o How results recording will be controlled for these charts
 Which function modules will be used to process the control charts
o How parameters will be used in these functions
 How the charts will be assigned to the processes (SPC criteria)

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Planning  Basic Data  Sample, SPC Statistical Process Control.
Transaction Code QCC4

86
Define SPC Criteria

You define the criteria that will be used to summarize and assign the inspection results for control
charts to the processes.
The SPC criteria determine whether the system will maintain separate or collective control charts
for different orders, work centers, materials, manufacturers or customers.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path: Quality Planning  Basic Data  Sample, SPC  Statistical Process Control
 Define SPC Criteria.
Transaction Code QCC4

Requirements
You have defined the inspection types, inspection lot origins and task list usages for which
control charts are to be used.

Activities
1. Determine which inspection types require control charts.

87
2. Determine which combinations of criteria are needed to collect the results for the inspection
characteristics.
3. If you need certain combinations of criteria that are not contained in the standard system, have
a qualified person create the corresponding function modules and store them in the table.

Use functional module for control


chart QRKS_INSPECTION_LOT

Key for task list usage


Key to control in which type of task list you can use: operating resources (for example, work
centers or production resources/tools).

Control Chart Assignment in Each Inspection Lot


No change of control chart within an inspection lot.
If you set this indicator, the same control chart is assigned to all partial lots for an inspection
characteristic within an inspection lot.

Control Chart Assignment for Each Inspection Point


Control chart can be changed within an inspection lot.

88
Define Control Chart Type

You define the control chart types.


For each control chart type, you define the requirements based on the control indicators and
sampling procedures used in the inspection characteristic.

In a second step, define the control chart tracks. For each track, determine which control variable
is used and how the warning limits or action limits are calculated.

The following control chart types are supported:


 mean value chart with tolerances (acceptance chart)
 mean value chart without tolerances (Shewhart chart)
 standard deviation chart
The following control chart types are available in the Quality Management component for inspection
characteristics:
 Mean value chart with tolerances (acceptance chart).
 Mean value chart without tolerances (Shewhart chart).
 Standard deviation chart (Shewhart chart).
 Moving mean-value chart.
 Range (Shewhart chart).
 Exponential weighted moving average (EWMA chart).
 Original value and moving range chart for sample size n = 1
 Charts for qualitative characteristics.
o NP-chart for the number of nonconforming units.
o P-chart for the fraction of nonconforming units.
o C-chart for the number of defects.
o U-chart for the number of defects for each sample unit.

In statistical process control, one or more control variables of the observed characteristic are
selected and determined by taking samples from the process at set time intervals if possible. These
statistics are entered in the chart in chronological order. The most important control variables are:
 Mean value X-bar
 Standard deviation s
 Median value
 Range
 Original value of a sample
 Number of nonconforming units
 Number of defects

89
Implementation Guide for R/3 Customizing  Quality Management 
IMG Path: Quality Planning  Basic Data  Sample, SPC  Statistical Process
Control  Define Control Chart.
Transaction Code QCC4

Activities
1. Determine which types of control charts will be used in your company.
2. For purposes of retrieving data, define appropriate control indicators for the control chart type.
This control must be compatible with the control for the inspection characteristics and the
sampling procedure being used.
3. Define the function modules and parameters according to which the system will calculate the
warning limits and action limits. Also plan the initial run.

90
Mean Value Acceptance Chart
General Control Chart Settings

Reference Axis of a Control Chart


The reference axis (x-axis) in a quality control chart determines how the samples are sorted in the
control chart and the how the reference axis is labelled.

Setting parameters for the reference axis


This parameter defines how the x-axis of the control chart is displayed. The following four options
are available:
1. Object number (inspection lot, sample, inspection point)
2. Creation time (of data record)
3. Time of last change (to data record)
4. Inspection time

91
The entries for reference axes with a time reference are not equidistant but refer to the
actual time intervals.

Track Settings
A one-digit number is used to differentiate between the tracks of a control chart type. In theory,
therefore, up to nine tracks can be defined for each chart.

Track Settings
The track is assigned a function module. The information for selecting or defining the control
variable and the algorithms for calculating the control limits are programmed in this module.

Two control variables of a characteristic are often run in parallel as two tracks on a control chart
(for example, the mean value and the standard deviation).

The following modules are implemented in the standard system:


MEAN VALUE ACCEPTANCE
MEAN VALUE SHEWHART

92
STD DEVIATION SHEWHART
RANG SHEWHART

Use functional module for Mean


value acceptance for X-Bar chart
(Mean value chart with tolerance)
QRKT_MEAN_VALUE_ACCEPTANCE

Statistical Parameter
in a Control chart

Check change
control limits

Parameter for Control Charts


The function modules have six possible parameters that can be set in the details screen for the
track. In this way, you can influence the statistical levels when the control limits are calculated.
The way in which the parameters are used can vary from module to module.
The action limits of an X- Shewhart chart can be calculated in such a way that 99% or 99.73%
(3σ- Rule) of the mean values are within the limits, if the process is not in control.

Statistical Parameter in a Control Chart (Optional)


Serves as a number value for setting a quality control chart.
By setting these parameters, you can adapt the control charts to meet the requirements of your
company, industry, or country. The type of control chart and track determine how the system uses
these parameters.
If you do not require the warning limits, reset parameters 2 and 3 to the initial value 0.

93
Uncheck
change control
limits

Display Specification Limits in Control Chart Track


Determines whether the tolerance for the inspection characteristic is displayed in the control chart
track.
Using this indicator, you can specify whether or not the lower specification limit, target value, and
upper specification limit for the inspection characteristic are displayed in the control chart track.
You can also enter a value for this indicator that allows you to display or hide this information as
required.

Control Limits Can Be Changed Manually


Setting that determines whether you can enter and change the control limits manually.
The system can calculate the action limits, warning limits, and center line for a control chart track
according to the algorithms assigned in Customizing. If you set this indicator, you can also enter
and change these limits manually.

94
SAP
statistical
graphics

Note: Acceptance Chart for X-Bar (Mean value chart with tolerance)
Control Indicator
 Tolerance limit (Mandatory)
 Sampling procedure
 SPC characteristics
 Single result
 Classed recording
 Defects recording
 Required characteristic
 Record measured values
Sampling Procedure
 Sampling Type
You must choose fixed sample.
 Valuation Mode

95
Valuation Mode, ‘Mean value within tolerance range’.

Shewhart Chart for X-Bar

Uncheck
Single result

Note:
The tolerance or single results are not required for an X-Shewhart chart for example. These
indicators, therefore, are not set in the requirements profile. This control chart, however, can also
be used for characteristics with a tolerance range limited on one side or on both sides or with
single values.

96
97
Use functional module for
Shewhart Chart for X-Bar
(Mean value chart with tolerance)
QRKT_MEAN_VALUE_SHEWHART_2

Check change
control limits

Display Specification Limits in Control Chart Track


Determines whether the tolerance for the inspection characteristic is displayed in the control chart
track.
Using this indicator, you can specify whether or not the lower specification limit, target value, and
upper specification limit for the inspection characteristic are displayed in the control chart track.
You can also enter a value for this indicator that allows you to display or hide this information as
required.

Control Limits Can Be Changed Manually


Setting that determines whether you can enter and change the control limits manually.
The system can calculate the action limits, warning limits, and center line for a control chart track
according to the algorithms assigned in Customizing. If you set this indicator, you can also enter
and change these limits manually.

98
Uncheck
change control
limits

Note: Shewhart Chart for X-Bar (Mean value chart without tolerance)
Control Indicator
 Tolerance limit (optional)
 Sampling procedure
 SPC characteristics
 Summarize recording
 Classed recording
 Defects recording
 Required characteristic
 Record measured values
Sampling Procedure
 Sampling Type
You must choose fixed sample.
 Valuation Mode

99
Valuation mode ‘SPC inspection’.
For Tolerance limit in MIC select
Valuation Mode, ‘Mean value within tolerance range’ always

Modal Display of Graphics


Indicates whether the SAP business graphics function (displayed in a modal dialog box) or graphics
based on OCX components are to be used.

You can use the test call function to check whether the modification was successful.

100
Define Number Range

You define the number ranges for the control charts.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path: Quality Planning  Basic Data  Sample, SPC  Statistical Process Control
 Define Number Range.
Transaction Code QCC4

101
Activities
Check to make sure an adequate number interval has been set.

102
Inspection Planning

You implement the functions for inspection planning using the R/3 QM component.
Although these implementation steps are described for the inspection plan (task list type Q), they
also apply to inspection planning activities for other task list types.
The inspection plan uses a variety of other master data in the form of building blocks. The
Implementation Guide contains separate chapters that describe how to maintain this data:
 Basic data in the chapter Quality planning
 Work centers and test equipment in the Implementation Guide for Production

General

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Planning  Inspection Planning  General.
Transaction Code QCC4

103
Assign Task List Types to Material Types

You specify which material types can be inspected using inspection plans .

Implementation Guide for R/3 Customizing  Quality Management  Quality


IMG Path:
Planning  Inspection Planning  Assign Task List Type to Material Type.
Transaction Code QCC4

104
Task List Type
Key which classifies task lists according to their functionality.
The following task list types are available:
 Q ( inspection plan ) for general inspections
 N (PP- routing ) for production
 M (PP- rate routing ) for simple production processes
 2 ( master recipe ) for processes
 E ( equipment task list ) for calibration inspections
 T (task list for functional location)
 A ( general maintenance task list ) for general plant maintenance
If necessary, define your own task list usages.
Material Type
Key that assigns the material to a group of materials such as raw materials, operating supplies or
trading goods.
The material type defines certain attributes of the material and has important control functions.
Activities
1. Check the settings of the material types in the menu item "Material master/ Define
attributes of material types.”
2. Determine which material types should be inspected with task list type Q (inspection plan).
3. Maintain the assignment table.

Define Task List Usages


In this step, you define your task list usages.
Within a task list group, you can create different task list types with different usages. For example,
you can distinguish among the following usages: model inspections, goods receipt inspections,
inspections for goods returned from a customer, product audits and goods issue inspections. With
the task list usage, the system can find an appropriate task list for a certain inspection type.
For each task list usage, you also define appropriate dynamic modification criteria to update the
quality level. The dynamic modification criteria defined in the task list usage only serve as default
values for the dynamic modification criteria in the task list.

105
Implementation Guide for R/3 Customizing  Quality Management 
IMG Path:
Quality Planning  Inspection Planning  Define Task List Usage.
Transaction Code QCC4

Task list usage


Key specifying the areas in which the task list can be used (for example, in production or plant
maintenance).
Do not confuse the task list usage with the usage of a PRT or a work center. In these cases, the
usage describes the task list types in which the PRT or work center can be used.

Dynamic Modification Criterion


Dynamic modification criteria are required if inspection scopes need to be dynamically changed.
Dynamic modification criteria for a goods receipt inspection are for example, material and vendor.
The quality level is updated for these dynamic modification criteria after each goods receipt
inspection. The inspection scope is then dynamically adapted, based on the quality level.
Activities
1. Define the usages for which you intend to use your own inspection plans, and for which your
own criteria should be suggested for updating the quality level. Define the usages on the basis of
the inspection types that are commonly used in your company.
2. For each task area, define the appropriate criteria that will be used to update the quality level.
3. Maintain your task list usages.
Define Task List Status

You define the Status that is used in the logistical task lists (inspection plan, reference operation
set, routing)
The status controls the following functions in the QM application component:
 Release for use
o Of reference operation sets in inspection plans
o Of inspection plans in inspection lots

106
 Release for standard cost estimate
(The standard cost estimate currently does not apply to inspection plans.)
 Consistency check

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Planning  Inspection Planning  Define Task List Status.
Transaction Code QCC4

Released
Indicator which specifies whether a reference operation set is released for usage in routings and
plans.
Costing
Indicator which specifies that the task list is released for costing.
Consistency check prior to posting
Indicator you use to specify that a consistency check is automatically carried out before a task list with this
status is saved.

Define Planner Group

You define the inspection planner groups.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Planning  Inspection Planning  Define Planner Group.
Transaction Code QCC4

107
Responsible planner group/department
Key which identifies the planner group responsible for maintaining the task list.

Activities
1. Find out how the inspection planners are grouped in the plants within your company.
2. Maintain the planner groups for each plant in the table.

Define Overview Variants

You can create your own object overviews for an inspection plan.
For each overview that you create, you also create an overview variant. For this overview variant,
you must specify:
 Which objects are to be displayed in the overview (for example, operations or
characteristics)
 Which fields are to be displayed for each object.

108
Implementation Guide for R/3 Customizing  Quality Management 
IMG Path:
Quality Planning  Inspection Planning  Define Overview Variants.
Transaction Code QCC4

Standard Settings
The standard system contains an overview variant.

109
Activities
To create your own overviews, proceed as follows:
1. Create overview variants
This section describes how to create overview variants.
2. Define objects
This section describes how you can define the objects that are to be included in the
overview.
3. Define fields
This section describes how to select fields and define the layout for the overview.
4. You can transport your settings by selecting Table view Transport.

Maintain Profiles for Default Values

110
You can maintain profiles for the default values in inspection plans.
The default values stored in the material master or work center master have priority over the
values in the profile.
Profiles with default values are available for the following levels:
 inspection plan in general
o inspection plan header
o operation
 inspection characteristic

Implementation Guide for R/3 Customizing  Quality Management  Quality


IMG Path:
Planning  Inspection Planning  Maintain Profiles for Default values.
Transaction Code QCC4

111
Activities
1. Identify the fields in the inspection plan for which you can (and should) store default values in
profiles.
2. If necessary, define several different profiles and specify when these profiles should be used.
Define the nomenclature for a mnemonic profile short text.
3. Maintain the default values for the general management of inspection plans.
4. Maintain the default values for the management of inspection characteristics.

112
113
Define Field Selection

114
You adapt the field selection in task lists. For more information, see section Environment/ Tools/
System Modification / Adapt Field Selection.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Planning  Inspection Planning  Define Field Selection.
Transaction Code QCC4

115
116
Define Text Widths

117
You define the line length of the long texts in the inspection plans.
The long texts for the following objects are affected by this table setting:
 plan header
 sequence
 operation
 sub-operation
 production resources and tools assignment

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Planning  Inspection Planning  Define Text Widths.
Transaction Code QCC4

The length of the short text is always 40 characters. If you define a line length for the long text
that is greater than 40 characters, the associated short text will display only the first 40 characters
of the first long text line.

Maintain Parameters for Task List Type

118
You assign number ranges to the task list types.
You can also activate the following options for each task list type:
 Creation of change documents
 For the material, task list group and sales document: the last value maintained is displayed
as a default value
 Deletion of task lists and operations (but only with special authorization)
(Controlled by the authorization object Q_ROUT)

Standard Settings
In the delivery system, the parameters for the inspection plans (type Q) and reference operation
sets (type S) have already been set up in a meaningful way.

Maintain Number Ranges for Inspection Plans

119
You maintain the number ranges for the task list groups associated with the following task list
types:
 Inspection plans
 Reference operation sets
Number allocation can take place internally and externally.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Planning  Inspection Planning  Maintain Number Range.
Transaction Code QCC4

120
Check number
ranges used

121
Standard Settings
Number ranges have already been predefined in the standard system.
Activities
Maintain the number ranges for the external and internal number assignment.

Define Identifier for Inspection Points

122
You define inspection points in this step. This involves defining the following:
 Identification of inspection points
 Default values for Valuating the inspection points
 Function modules for generating the inspection points
You can use this identification technique in several application areas. The standard system,
therefore, provides the following inspection point types
 Freely defined inspection points to identify partial lots in production
You need this inspection point type; for example, if you create inspection lots for a
production order and want to carry out several inspections for each operation during the
production process.
 Inspection points to identify samples
You need this inspection point type if you want to manage samples and record inspection
results for physical samples
 Inspection points to identify maintenance objects
you need this inspection point type if you want to carry out calibration inspections and
record the results of test equipment inspections or inspections of functional
locations.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path: Quality Planning  Inspection Planning  General  Define Identifier for
Inspection Point.
Transaction Code QCC4

Identification for the Inspection Point Field Combination


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.
QB1 Equipment
QB2 Functional location
QB3 Physical sample
QBK Production

123
Inspection points during the production process
The identifiers for the inspection points are defined in the task list header and are valid for all
operations. If you do not define an inspection point identifier in the task list header, the system
uses a general identifier, which is stored in the settings at plant level.

124
Select ‘X’ to make
this field optional

Field Active
An identification field is only active if you have made an entry in this field.
Fields with numeric entries are required fields. The numbering sequence that you define for these
fields uniquely identify an inspection point.
The inspection point type determines whether required fields are called up for identification. These
fields cannot be changed.

Last Inspected Sample is Valid


If you set this indicator, the results for the last inspected inspection point are valid.
All characteristic results for previous inspection points are automatically set to invalid. Only the
results for the last inspection point are considered for summarization at summarized characteristic
level.
You can display the summarized characteristic result using the transaction Display results for an
operation.
For example, you should set this indicator if samples should be drawn (and inspection points
created) until the target value is reached.

125
Default for valuating inspection point (Automatic Valuation)

Selected Set for Inspection Point Valuation


Selected set from the usage decision catalog (catalog type 3) that is used for valuating inspection points.
Code Group for Inspection Point Valuation (Accepted)
Code group for the code which is suggested automatically for valuating the inspection point. You can,
however, modify valuation of the suggestion and choose a different code.
Code Group for Inspection Point Valuation (Rejected)
Code group for the code which is suggested automatically for valuating the inspection point. You can,
however, modify valuation of the suggestion and choose a different code.

126
QAPP_CUST_IP_CREATE
Use functional module
inspection for Production

QAPP_CUST_IP_PROPOSA
L

Change the necessary function modules (SE37)


Automatic creation of insp. Points
QAPP_CUST_IP_CREATE - Automatic Creation of Inspection Points and Partial Lots
Default for user fields in results recording
QAPP_CUST_IP_PROPOSAL - Default for Inspection Point Identification in Results Recording
Verification of user fields in results recording
QAPP_CUST_IP_CHECK - Checking the Entered Inspection Point Identification
List of values for user fields in results recording
QAPP_CUST_IP_F4 - F4-Help for the Inspection Point Fields

Operation

127
This subsection describes the settings for inspection operations.
You can maintain master records for three object types that are subordinate to an operation:
 Work center
 Production resources and tools (PRT)
 Inspection characteristic
The settings for these three object types are not included in this section, but are described in
separate sections of the Implementation Guide.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path: Quality Planning  Inspection Planning  Operation  Define Control Keys
for Inspection Operations.
Transaction Code QCC4

Define Control Keys for Inspection Operations

128
You define the control keys for the inspection operations.
Using the operation control key, you can influence the planning and processing of an inspection
operation in several ways. The following indicators are relevant to inspection plans:
 Characteristics
o Inspection characteristics exist.
 Printing
o Shop papers are printed for the operation.
 Scheduling
o The operation is scheduled.
 Costing
o The operation is taken into consideration for costing purposes.
 Processing of confirmations
o The operation is confirmed.
o The operation is confirmed as a milestone.
 External processing
o The operation is processed externally (outside of your own company).
Note: no goods receipt inspection is carried out for the externally processed item upon
its return.

Activities
1. Make sure you know which functions for the inspection operations are influenced by the control
key.
2. Find out which control keys are needed and coordinate these requirements with all affected
departments.
3. Maintain the table of operation control keys (if necessary, coordinate this with the other
modules).

129
Inspection characteristics for operation required
This indicator specifies that inspection characteristics are to be maintained for the following objects
if specified in the control key you selected. Operations in Quality Management (QM) and Production
Planning (PP)

130
Print
This indicator specifies that the following objects are taken into account when printing shop papers,
such as time tickets or confirmation slips, if specified by the control key you selected. Operations
and sub-operations in Quality Management (QM), Plant Maintenance (PM) and Production Planning
(PP)

131
Cost
This indicator specifies that the following objects are included in costing if they possess the
selected control key. In the areas Quality Management (QM), Plant Maintenance (PM), and
Production Planning (PP): operations and sub operations.

External processing
This key indicates whether the following objects can or must be externally processed if so specified
in the control key you selected. Operations and sub-operations in Quality Management (QM), Plant
Maintenance (PM) and Production Planning (PP)

132
Completion confirmation
This key specifies whether an object is to be confirmed if it has the control key you selected.
You can specify that milestone confirmations are carried out for an object in PP (Production
Planning and Control) and PP-PI (Production Planning for Process Industries).

An order has a final confirmation status once all operations, activities and phases specified for
confirmation have been completely confirmed.

133
Define User Fields

You can define your own fields for the detail screen of an operation, in addition to those that are
already present in the standard system.
The inspection plan contains a group of fields at the operation level that can be defined by the
user. You activate these fields by entering a key word ID in the detail screen for the operation.
You use the key word ID to identify a group of fields.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Planning  Inspection Planning  Operation  Define User Field.
Transaction Code QCC4

You define such groups of fields by:


 defining key word ID's
 selecting key words for each key word ID from a predefined selection of key words
representing different data types
 assigning a name and a meaning to each of these keywords

134
135
Work Center

You maintain the settings that can be copied from the work center into the operation.
You can assign a work center to operations. This allows you to use a wide range of data from the
work center master record in the operation. This data can either be referenced, or used as default
values. The data can be used for:
 Scheduling
 Capacity planning
 Costing
Linking subsystems to process operations and record results
To use the controlling functions of the work center assignment, you must maintain the work center
master data. You can find information on the relevant settings in the Production, Basic Data, and
Work center section.
The data from the work center can be used in the operation in two ways:
 As default values
the system proposes the values when you maintain the operations; the inspection planner
can change these values.
 As reference values
the system always retrieves the current values from the work center and uses them in the
operation; the inspection planner cannot change these values. The person responsible for
the work center, however, can change these values centrally in the work center.

Maintain Standard Text Keys

You maintain the text keys and standard texts for the description of inspection operations.
In the inspection operations, you can specify standard text keys that reference standard texts.
These texts are then displayed as operation texts. Only the long text for the standard text key is
displayed and not the 40-character short text for the text key.

Define Qualifications

You can define the qualifications that are required for certain inspection operations.
Do not confuse the qualifications at the operation level with the inspector qualifications at the
characteristic level.
You must define the qualifications at the operation level for each plant

Inspection Characteristic

You maintain the controls at the characteristic level of the inspection plan.
You can store basic data relating to the inspection characteristic in the system in the form of
master inspection characteristics. You can find the relevant settings in the section Quality Planning,
Basic Data, Inspection Characteristic.
You only require the other settings at characteristic level, if you want to record results based on
inspection characteristics. For these settings, see section Quality Inspection / Results Recording.

136
4.0 Quality Inspection

This section deals with the implementation of quality inspection procedures.


R/3 QM supports diverse variants for quality inspections. The basic variants among these control
options can work alongside one another and are:
 Basic inspection lot processing; partial functions:
o Inspection lot creation, inspection lot processing, sample calculation
o Defects recording for inspection lot
o Inspection lot completion, usage decision with quality score, follow-up actions, data
update in QM information system
 Inspection lot processing with inspection plan; supplementary functions:
o Inspection plan selection
o Sample calculation with lot-based dynamic modification based on usage decision
o Printing of shop papers (inspection instruction, sample-drawing instruction, physical-
sample labels)
o Defects recording for inspection operation and inspection characteristic
 Inspection lot processing with results recording; full functionality:
o Recording characteristic results
o Transfer of inspection results to batch valuation
o Sample calculation with dynamic modification based on characteristic valuation
 Inspection with inspection points and the following additional functions:
o Freely-defined inspection points for an operation
o Recording characteristic results and defects for an inspection point
o Creation of partial lots and batches, based on the results for inspection points
A standardized interface supports the processing of the inspection operations in subsystems.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Inspection  Inspection Lot Creation.
Transaction Code QCC3

137
Inspection Lot Creation

You define the controls for inspection lot creation.

Automatic Inspection Lot Creation


If you activate the corresponding inspection type in the inspection setup for the material, the
system creates inspection lots for the following inspection lot origins:
 Inventory Postings
o 01 Goods receipt for purchase order
o 04 Goods receipt from production
o 05 Miscellaneous goods movement
o 08 Stock transfer (for example, from unrestricted-use stock to inspection stock)
o 09 recurring inspection
 Production
o 03 Production order
o 03 Process order
o 13 Repetitive manufacturing
 Deadline Monitoring of batches
o 09 For the date of the recurring inspection
o 09 For the shelf life expiration date
 Deliveries
o 10 Deliveries to customer with sales order
o 11 Deliveries to customer without sales order
o 12 Other deliveries
 Sample Management
o 15 Inspection lots for physical samples
For the system to create inspection lots, you can (or in some cases) must specify the
inspection type in the order type for the following inspection lot origins:
 Plant Maintenance (for example, with calibration inspection).
o 14 Maintenance orders
In this case the inspection type is only determined using the order type.

Manual Inspection Lot Creation


You can currently only create inspection lots manually for the following inspection lot origins:
o 07 Vendor audit
o 89 Miscellaneous

138
Maintain Inspection Types

You maintain the inspection types and the controls associated with the inspection type.
Using the online documentation, first familiarize yourself with the meaning of the individual fields in
this table!

Requirements
Depending on the functions and control options you want to use, you must make sure the following
conditions are met before you can maintain the table:
 Catalog 3 for usage decisions and the associated selected sets has been created at the
plant level.
 Status profiles for inspection lots have been defined.
 Order types for appraisal costs have been defined.
 Quality notification types have been defined.
 Task list usages have been defined.
 Control keys for inspection operations have been defined.
 Sample types for sample management have been defined.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Inspection  Inspection Lot Creation Maintain Inspection Type.
Transaction Code QCC3

Activities
1. Define the eight-character keys and the short texts for each inspection type that you want to use.
Note that you are only allowed to use each inspection type for one inspection lot origin.

139
2. Determine which control fields are relevant for each inspection type.
Define the contents of the controlling fields for each inspection type. If necessary, you must make sure the
conditions mentioned above have been met.

Inspection lot processing  Assignment of a status profile


 Proposal of a QM order type for the inspection type
 Proposal of a selected set for the usage decision
Print control  Specifying when inspection instruction will be printed
 Specifying when sample-drawing instruction will be printed
Results recording  Specifying the default recording view
 Specifying which notification type will be created for activated
defects
 Specifying how many notifications will be created for each
inspection lot
Inspection planning  Specifying the task list usage (for example, for goods receipt,
production, and so on)
Type of Inspection Indicator What You Should Know
With material specification  Insp. with mat. spec You must enter the operation data
 Insp. by charac. for the material specification
(operation number and control key)
and you must enter the number
range for the inspection
characteristics at client level.
With task list  Insp. with task list
 Insp. by charac.
With material specification  Insp. with mat. spec Inspection specifications for master
and task list  Insp. with task list inspection characteristics that occur
 Insp. by charac. in the task list and in the material

140
specification are taken from the
material specification.

141
Selected Set for Usage Decision
If you enter a selected set, the system only allows you to make usage decisions that are included
in the selected set for the inspection type.
You can use the indicator Selected set in same plant to limit the selection to the plant to which
the inspection lot belongs.

Selected Set Must Be Available in Plant


If you set this indicator, you can only use usage decisions from selected sets that are in the same
plant as the inspection lot.
Using the UD-selected set field, you can limit the pool of usage decisions to a single selected set.

142
143
An inspection stock already exists in the R/3 System for the material for example, because the
QM component was installed after the inventory management system in the MM component). In
this case, you have the following options:
a) Removing inspection stock before an inspection type is activated
First make sure that the quantity of goods in inspection stock is reduced to zero; that is, complete
the current inspection and post the inspected quantity to unrestricted-use (or blocked) stock.
b) Activate the required inspection types in the inspection setup for the material. You can
now create and process inspection lots for the quantities of materials to be inspected.
c) Managing inspection stock with the help of inspection lots
Take the following steps:
 Define an additional inspection type for the inspection lot origin 08 stock transfers
(inspection type 0800 in the standard system).
 Define default values for this inspection type.
 Enter this inspection type in the settings at plant level

144
Selected Set Must Be Available in Plant
If you set this indicator, you can only use usage decisions from selected sets that are in the same
plant as the inspection lot.

145
146
147
Maintain Inspection Lot Origins and Assign Inspection Types

In the "Origin" step, you define the inspection lot origin-dependent controls.
The inspection lot origins are predefined in the system.
You cannot define your own inspection lot origins. However, for each available inspection lot origin,
you must define the following parameters:
 Number range
 Available dynamic modification criteria
 Task list type
 Inspection plan status

Implementation Guide for R/3 Customizing Quality Management 


IMG Path:
Quality Inspection  Inspection Lot Creation  Maintain Inspection Type.
Transaction Code QCC3

148
Original Number Dynamic Task List Type Inspection plan Inspection Lot origin
Range Modification status Text
Criteria

Maintain inspection lot origins and assign inspection types


You can define the following control parameters for each inspection type:
 Number range (user-defined or system-generated inspection lot number)
 Dynamic modification criteria
 Task list type that will be selected when the system assigns an inspection specification to
the inspection lot
 Task list status that will be selected when the system assigns a task list to the inspection lot

Standard Settings
The inspection lot origins are predefined by SAP.

149
Activities
1. For each inspection lot origin used in your company, define:
a) Which inspection lot number range is to be used.
If you want to define new number ranges, refer to the corresponding step Maintain Number
Ranges.
b) Which dynamic modification criteria can be used.
Define the maximum number of dynamic modification criteria that can be combined for each
inspection lot origin.
Note:
If you use dynamic modification without a task list, the quality level for the dynamic modification
criteria is managed in the inspection lot origin.
If you inspect with a task list, the intersection of the dynamic modification criteria in the task list
and in the inspection lot origin is used for the quality level. You can define default values for the
dynamic modification criteria in the task list using the control parameter task list usage.
c) Which status the inspection plan must have.
The status "Released" (proposed in the standard system) is generally used.

150
2. Maintain the properties for the inspection lot origins in the control table. Look for appropriate
number ranges, dynamic modification keys and a task list status.
3. Maintain the inspection type variants for each inspection lot origin.
Make sure that a variant '01' (zero one) is available for each inspection lot origin!

Maintain Number Ranges

You determine the number ranges for the inspection lots. These number ranges are stored in the
inspection lot origin; they apply to the entire client.
The system only allocates the inspection lot numbers internally, based on the defined number
range. Therefore, it is not advisable to define an external number range.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Inspection  Inspection Lot Creation  Maintain Number Range.
Transaction Code QCC3

151
Standard Settings
An individual number range is defined for each inspection lot origin.

152
Define Default Values for Inspection Type

You define default values for a material's inspection setup.


You can define different inspection lot processing sequences for individual materials or material
groups by changing the default values for the inspection types in the material master.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path: Quality Inspection  Inspection Lot Creation  Define Default Values for
Inspection Type.
Transaction Code QCC3

Activities
1. Determine which control parameters are relevant for the individual inspection types and which of
these parameters can be predefined uniformly for each inspection type.
2. Define the default values for each inspection type.
Store only those default values that you will always use when you maintain the material master.

153
3. Maintain the table of default values.
4. Although some controls cannot be predefined uniformly in the system by means of default
values for an inspection type for all materials, they could still be defined uniformly for
comprehensive material groups. For such material groups, define the profiles using organizational
measures and make sure the inspection planners use these profiles.

Control of Inspection Lot Creation (Lot Summary)


You can make the following settings:
 ' ' An inspection lot for each material document item (No lot summary)
An inspection lot is created for each item in the goods receipt document.
Material (Single)  Multiple Batch (Single GR)  Multiple Inspection lot.
 'X' An inspection lot for each purchase order item/order item
This setting is limited for use with the inspection lot origins 01 and 04.
An inspection lot is only created during the first goods receipt for each PO item or
production order.
Material (Single)  Single P.O. (Multiple GR & same batch)  Single Inspection lot.
 '1' An inspection lot for each material document and material
If you set this indicator, the system creates only one inspection lot for a material document (in a
goods receipt transaction) for each material. This setting is useful, if several purchase orders or
partial deliveries are processed for the same material in a goods receipt transaction.

154
Material (Single)  Different P.O. (Single GR)  Single Inspection lot.
 '2' An inspection lot for each material and batch
If you set this indicator, the system creates only one inspection lot for each material and batch.
This setting is only advisable for materials with a batch management requirement.

Control of Inspection Lot Creation (Lot Summary)


You can make the following settings:
 ' ' An inspection lot for each material document item (No lot summary)
An inspection lot is created for each item in the goods receipt document.
 'X' An inspection lot for each purchase order item/order item
This setting is limited for use with the inspection lot origins 01 and 04.
An inspection lot is only created during the first goods receipt for each PO item or production order.

155
156
You can make the following settings:
An inspection lot is only created during the first goods receipt for each PO item or production order.
 'Y' An inspection lot for an early goods receipt inspection
this setting is only relevant for inspection lot origin 04.
An inspection lot with inspection lot origin 04 is created when a production or process order
is released. You can use this inspection lot to inspect goods receipts of the finished
quantities and then manage them after goods receipt posting in the inspection lot stock.

157
158
159
160
161
162
Inspection for Goods Movements

You control the creation of inspections for goods movements or other inventory postings.
For the system to be able to create an inspection lot for a goods movement, the appropriate
inspection lot origin must be entered in the update view for the movement type.
You can deactivate the creation of inspection lots in an additional view.

Implementation Guide for R/3 Customizing  Quality Management  Quality


IMG Path:
Inspection  Inspection Lot Creation  Inspection for Goods Movement.
Transaction Code QCC3

163
164
165
Movement Type for QM Inspection Processing Not Active
If you set this indicator for a movement type, no inspection lots are created for stock
postings.
Inspections for Goods Movements
The systems can create inspection lots automatically for the goods movements listed below.
Inspection Type Movement Type
Inspection for a goods receipt With PO-101
Without PO-501
Goods receive from production-101
Inspection for a goods issue Goods issue to production-261(order),
-201(Cost centre).

166
Delivery to customer with sales order-601
Delivery to customer without sales order-602
Inspection for a stock transfer Plant to plant-301,303 & 305
Store to store-311, 315, Mat to Mat-309,
Inspection for a return delivery 651 & 655
A transfer of goods from inspection stock to 321
unrestricted-use stock
Reverse a stock posting for an inspection lot 102 (Goods receipt for a purchase order into
warehouse - reversal).
Posting materials to goods-receipt blocked 103
stock
Inspection for Deadline Monitoring of Batches

You plan the creation of inspection lots by monitoring the deadlines of materials whose stocks are
managed in batches.
The monitoring of deadlines involves two activities:
 Changing the batch status when the following deadlines are reached:
o Shell life expiration date
o Date of the next recurring inspection

 Creating an inspection lot before the date of the next recurring inspection expires and
posting the materials to inspection stock
To create inspection lots automatically, the system starts a job that triggers the monitoring of
deadlines at certain intervals:
o On a one-time basis
o At predefined intervals
Activities
1. Plan the jobs to create the inspection lots.
o Define report variants for triggering the inspections with the help of the deadline monitoring
function.
o For each plant and material, define the intervals in which the deadlines are to be monitored.

167
Inspection of Manufacturing Order

In this step, you define the inspections during production.


You or the system can create inspection lots for the following methods of production:
 Production orders
Inspection lot origin 03 <- task list type N (routing)
Inspection lot origin 03 <- task list type M (rate routing)
 Process orders
Inspection lot origin 03 <- task list type 2 (master recipe)
 Repetitive manufacturing
Inspection lot origin 13 <- the task list type can be set using the production version of the
material.

Implementation Guide for R/3 Customizing  Quality Management  Quality


IMG Path:
Inspection  Inspection Lot Creation  Inspection for Goods Movement.
Transaction Code QCC3

168
169
Requirements
When you maintain the corresponding task list type, you must provide for inspection characteristics
and use corresponding control keys for the operations.
In task lists, you can define results recording based on inspection points. For more information on
the necessary settings, see the sections on Quality Planning, Inspection Planning, and Inspection
Points.
Standard settings
If you enter a task list type or task list status, when maintaining inspection lot origins 03 and 13,
this has no effect, since the system does not take these entries into account when selecting task
lists for production orders, process orders, and production versions.
Activities
1. For inspection lots in production, the system selects the preferred inspection type or
inspection type with variant 01 for the corresponding inspection lot origin, unless you specify
another inspection type in the settings for the order type.
Determine whether you need different inspection types in production that are dependent on the
order type. If necessary, define variants for these inspection types and predefine them for the
order type at plant level. Note that the table is a part of the Production area.

170
Inspection for External Processing

171
You can make settings to inspect goods receipts from an external process, or subcontract (external
process with material to be provided).
Requirements
 Control keys for production operations allow for an external process.
 There is an inspection type assigned to the inspection lot origin 01 for the affected
operations.
 This inspection type is active in the material master for the finished product.
Activities
1. Identify the types of external processes for which goods receipt inspections are required.
2. Define suitable inspection types and task list usages
3. Maintain these inspection types in the material master records for finished products and
in their corresponding task list operations.
4. If required, create inspection plans with suitable task list usages.

Inspection at Shipping

172
You define the delivery types in the Sales and Distribution (SD) component, for which inspections
are to be triggered in the QM component. To do this:
 You assign one of the following inspection lot origins to the delivery type predefined in the
SD component:
o 10 for delivery to customer with sales order
o 11 for delivery to customer without sales order
o 12 for other deliveries (without customer reference)
 Assign an inspection type to the combination inspection lot origin/ delivery category
(called usage indicator in the SD component).
Requirements
 The delivery types and usage indicators are maintained in the SD component.
 The inspection lot origins and inspection types are maintained in the QM component.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Inspection  Inspection Lot Creation  Inspection Shipping.
Transaction Code QCC3

173
Delivery Type
A classification that distinguishes between different types of delivery.
The delivery type determines how the system processes a delivery.
For example, depending on the delivery type, the system determines which screens to present and
which data to request from the user.
Activities
1. Determine which delivery types are defined in the SD module. Determine whether quality
inspections are to be triggered for these delivery types.
2. If inspections are to be triggered:
o Assign suitable inspection lot origins to these delivery types.

Note: You can only enter the inspection lot origins 10, 11 or 12. This also applies to inspections for
return deliveries; the inspection lot origin 06 cannot be used for these.
o Assign suitable delivery types and inspection types to these inspection lot origins

174
Delivery Category
The delivery category corresponds to the use in Sales and Distribution (SD).
From a QM perspective, it describes a special class of a delivery requested by a customer. It allows
QM to carry out a special form of quality inspection.
Examples of delivery types are:
 Model delivery
 Preliminary series delivery
 Regular delivery
 Substitute delivery

Define Inspections in Plant Maintenance

175
You make the settings for plant maintenance inspections, for example, for calibration inspections of
test equipment.
Apart from defining suitable inspection types for the inspection lot origin 14, the only thing you
have to ensure from a QM standpoint is that for identifying the equipment a suitable user field
combination exists for the inspection point type equipment. This is required, for example, if
you want to carry out calibration inspections on test equipment.
You can find all other settings for the maintenance of equipment in the Implementation Guide for
Plant Maintenance.
Implementation Guide for R/3 Customizing  Quality Management 
IMG Path: Quality Inspection  Inspection Lot Creation  Define Inspection in Plant
Maintenance.
Transaction Code QCC3

Activity
1. Inspection type
2. Default values for inspection type
these default values provide valid standard values for inspection types of inspection lot origin 14.
3. Inspection lot origin 14 and assignment of the inspection types for inspection lot origin 14.
Note: A number range must be maintained for the inspection lot origin 14.
4. User field combinations for inspection types of the Plant Maintenance objects equipment and
functional location.
5. Order types for maintenance orders.
6. Assigning the inspection types to the order types
7. Follow-up actions for the usage decision that are used to update the equipment data.

176
Inspection Lot Completion

You determine system functions which are related to the usage decision:
The inspection lot completion includes:
 Inspection Completion
you can complete the inspection temporarily or definitively (short-term completion or final
completion) even without having entered a usage decision. Entry of a usage decision,
however, causes the inspection lot to be completed. If long term characteristics are still
open in this case, completion only applies to the short-term inspection.
 Usage Decision
the usage decisions are defined in catalog 3.
 Quality Valuation
a quality score must be defined as well as the usage decision for the inspection lot.
 Updating the Quality Level
Provided that a dynamic modification rule is entered in the inspection setup for the
material or in the task list. Since in dynamic modification based on characteristics the
quality level is only run for characteristics that have been completed at the usage decision,
the system does not write a quality level for long-term characteristics.
 Updating the QM Information System
Provided that an update group for the QM information system was assigned to the
inspection lot origin and that this update group is active
 Transfer of Inspection Results to the Batch Specification
Provided that the inspection characteristics are linked to characteristics of the batch
class or that the transfer of the inspection decision to batch is arranged for
corresponding characteristics of the batch class.
 Follow-Up Actions
you can specify a follow-up action for the usage decision that can consist of a chain of
automatically triggered function modules.

The system automatically performs certain actions that are related to the origin of the inspection
lot and you do not need to define these individually as follow-up actions.
o Stock that was posted from inspection lots in goods movements to inspection stock
can be posted out of inspection stock to unrestricted -use when the usage decision is
made.
You can post out of inspection stock at any time, irrespective of whether the
inspection is completed, with the help of the usage decision transactions.
o The update of the vendor evaluation in inspection lots from goods receipts for
purchase orders or from related shop floor complaints takes place when a new
vendor evaluation is made.

177
Implementation Guide for R/3 Customizing  Quality Management 
IMG Path:
Quality Inspection  Inspection Lot Completion.
Transaction Code QCC3

178
Maintain Catalogs for Usage Decisions

You maintain catalog 3, which is provided for making usage decisions.


Requirements
Before you can maintain the selected sets for the usage decision, you must implement the
following steps in this section:
 Define Quality Score Procedure
 Define Follow-Up Actions
 Define Inventory Postings

Activities
1. Check whether catalog type 3 exists in the table.
Copy and keep the standard settings.
2. In catalog 3, enter the code groups and codes for the UD.
3. Maintain the selected sets from catalog 3 at plant level.
Automatic Proposal for Stock Postings
For usage decision codes in inspection catalog type 3, you can predefine automatic proposals for
stock postings. You do this by maintaining the selected set codes as follows:
 Specify a stock posting proposal for a code
For example, for the usage decision code to accept an inspection lot, you can set the stock
proposal indicator so the system will automatically post the stock to unrestricted use stock.
 Set the indicator for background processing
If you set this indicator for a code, the system posts the stock automatically. If you do not
set this indicator, you must confirm the stock proposal manually.
 Set the batch status
You can specify that the system change or retain the current batch status with the usage
decision (for example, no change to batch status, change batch status to “unrestricted,” or
change batch status “restricted”).

179
Define Quality Score Procedure

You define the procedures for determining the quality score.


The quality score procedure is defined in the inspection setup for the material master at plant level.
You can define a default value for this procedure in the inspection type.
Requirements
 The following specification limits have been defined in the Settings at Client Level.
o Highest quality score
o Lowest quality score
o Lower limit for good quality
 If you want to use quality score procedures that access the weighted shares of defects for
the characteristics, you must maintain the characteristic weights.
 If you want to use quality score procedures that access the quality score of the
characteristics, you must maintain the defect classes.
 If you want to use quality score procedures, in which the system calculates the share of
scrap, you must:
o Check whether procedures for estimating the scrap share have been defined in
Customizing
o Assign suitable procedures for estimating the scrap share to the characteristics in the
task list
o Identify inspection characteristics as relevant for scrap in their control indicators

Implementation Guide for R/3 Customizing  Quality Management  Quality


IMG Path:
Inspection  Inspection Lot Completion  Define Quality Score Procedure.
Transaction Code QCC3

180
“Weighted from quality scrape for chars”
And “For usage decision code”
Use in UD code

Standard Settings
A number of commonly used procedures for determining the quality score are implemented in the
standard system:
 Quality score from the usage decision
 Quality score from the share of defects in the lot
 Quality score from the shares of defects for the characteristics
o From the maximum share of defects
o From the weighted average share of defects
 Quality score from the quality score of the characteristics
o From the minimum (worst) quality score
o From the weighted average quality score
Activities
1. Determine which procedures for calculating the quality score should be used. You can make a
distinction on the basis of the:
 Plant
 Inspection type
2. Modify the table of quality score procedures according to your needs. If the procedures
contained in the standard system are not sufficient, you must create additional procedures using
function modules (SE37).

181
3. Define the quality score procedures in the Default Values for the Inspection Type or in the
inspection setup for the material.
Plan Automatic Usage Decision

You plan the process for the automatic usage decision (UD) for inspection lots.
You can enable the automatic UD for each inspection type in the material master. The system
then makes the usage decision automatically if all characteristics that must be inspected have been
accepted and if no defects or quality notifications were recorded. (You do not have to inspect
optional characteristics and characteristics that are in a skip stage.)
Before making the usage decision, however, the system waits until a specified amount of time has
elapsed from the date the inspection lot was created. During this time period, you can still
intervene in the automatic process.
Planning the times when the automatic UD is to be carried out:
 On a one-time basis
 Periodically

Implementation Guide for R/3 Customizing  Quality Management  Quality


IMG Path:
Inspection  Inspection Lot Completion Plan Automatic Usage Decision.
Transaction Code QCC3

182
The intervention periods in the standard system are set to a value greater than 24 hours;
the automatic usage decision function is not active.

Activities
1. Identify the plants, inspection types and materials for which the automatic usage decision will be
used. Specify this in the inspection setup for the material.
2. Define the intervention periods for individual plants so that you can intervene in the
automatic
o Skip
o Usage decision
3. Define the intervals, in which the automatic usage decision is to be made in the individual plants
and arrange the intervention periods.
4. Enter the periods or intervals, after which the automatic usage decision is to be made.
5. If you create inspection lots for production orders, you must also specify a cycle according to
which the automatic UD is to be made for these lots, once the production orders have been
completed.

183
Define the periods or intervals for this purpose.

Define Follow-Up Actions

You define follow-up actions for the usage decisions.


Several processing variations are possible for follow-up actions:
a) A manual trigger of activities to be carried out manually.
b) A manual trigger of activities to be processed by the system.
c) An automatic trigger of activities to be carried out manually Workflow link.
d) 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
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.
Implementation Guide for R/3 Customizing  Quality Management 
IMG Path:
Quality Inspection  Inspection Lot Completion Define Follow-Up Action.
Transaction Code QCC3

184
Use in UD code
for Partial lot
in Production

Use in UD code
for schedule IL

185
Requirements
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.

Standard Settings
The standard system also contains several executable examples of function modules for follow-up
actions:
 Sending a mail to a distribution list with information about the usage decision and quality
score.
 Sending a mail to a distribution list with information about the usage decision, quality score
and stock posting.
In the standard system, the distribution list only contains the name of the user who made the
usage decision.
 Updating the equipment data in a calibration inspection (inspection lot origin 14).

Selecting Follow-Up Actions


In the characteristic overview screen, the area for the usage decision also contains a field in which
you can enter a follow-up action. Use the possible entries help for the field to select a follow-up
action. The follow-up actions that have been defined in Customizing for the standard system
include the following:
 MAIL
Send a standard mail when the usage decision is made.
 MAIL2
Send a mail with the usage decision data when the usage decision is made.
 MAIL3
Send mail with the usage decision data and a long text when the usage decision is made.
 MANUAL
Execute follow-up action manually (no function).

186
Activities
1. Determine which follow-up actions for usage decisions are needed in your company. Be sure to
consider all inspection types, plants and usage decisions.
2. For the automatic follow-up actions, specify:
o The series of function modules to be used and the update form for each of these
function modules.
o The business transactions for the follow-up actions (if the activities carried out by the
function module are linked to the status management function for the inspection lot).
3. Maintain the table of follow-up actions. You must do this before you can maintain selected sets
in the usage decision catalog.
4. Create the necessary function modules (SE37).

Define Inventory Postings

187
You can adapt the inventory postings that are linked to the usage decision.

Implementation Guide for R/3 Customizing  Quality Management  Quality


IMG Path:
Inspection  Inspection Lot Completion Define Inventory Postings.
Transaction Code QCC3

Set 103 movement


type

Posting Proposal in Usage Decision


You can define a proposal for the inventory posting at the usage decision in this field.
If you enter a proposal for the inventory posting in this field and set the indicator "Quantity window
in the background", an inventory posting is automatically made for this stock in the background
when the usage decision is made for the lot.
Recommendation
Keep the standard settings!
Standard Settings
Several movement types are delivered with the standard system for transfer posting the stocks
managed in the inspection lot.
The table has the delivery class G. The following name range is reserved for the user:
 Inspection lot origin 01, 04, 05, 08, 09
Activities
Check if you need to change the table entries and adapt the table if required.
You may need to make changes if:
 You do not want to allow certain movement types.
 You want to replace the movement types contained in the standard system with your own
modified movement types 9*.
 You want to supplement the quantity postings planned in the standard system with other
quantity postings.

Transfer Inspection Decision to Batch


188
You create the preconditions that cause the usage decisions for inspection lots to be automatically
transferred to the batch valuation.
When the usage decision is made, the system copies the following data from the inspection point
into the batch valuation:
 Usage decision
 Quality score

Requirements
The following class characteristics must exist in the current client and must be assigned to the
batch class of the corresponding material:
 LOBM_UDCODE (usage decision)
 LOBM_QSCORE (quality score)

Activities
Determine whether you want to use the automatic transfer function for the usage decision to the
batch valuation and if this is the case, proceed as follows:
1. Copy the class characteristics for the usage decision and the quality score, using the functions
available in the current client.
2. Maintain a batch class in the Classification System and assign the characteristics mentioned
above.
3. Assign this batch class to all relevant materials.

Status Management

189
This subsection describes how to use the general status management function for inspection lots.
For a detailed description of the general status management function, refer to the chapter
Environment  Central Functions  Status Management.

Define Status Profile

You can use the general status management function for inspection lots to:
 incorporate your own conditions in the inspection lot processing activities (this occurs with
the help of the inspection type)
 define your own business transactions as follow-up actions
 define your own selection profiles for the selection of inspection lots
 to automatically create workflows as a result of certain inspection lot statuses; for additional
information, refer to the section Environment  Central functions  Workflow

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Inspection  Status Management  Define Status Profile.
Transaction Code QCC3/BS02

Prevent Stock Posting – if UD is not done


190
Activities
1. Check whether additional user statuses are required for certain inspection types.
2. Define the corresponding status profiles.
3. Assign the status profiles to these inspection types.
Check whether the process variants (with/without inspection plan/characteristic results) defined in
the default values for the inspection type are suitable for the object types that are assigned to
these status profiles.

Step-1 Create User Profile QMUDSP01.


The above User status profile is created, by copying SAP Standard Status profile QM_L_003.

191
Step 2: Create two User statuses namely (1) NSPO & (2) QFIN.

192
Step 3: Define the Transaction control of each status.

193
Double click the First status “NSPO”, we get the “Change Status Profile: Transaction Control”
Screen.

NSPO Status has only one Business Transaction


1. Start inventory posting before Usage Decision with “Forbidden” & “Set” settings.
The Radio buttons of “Forbidden” & “Set” columns are activated.

Go back to the initial screen & double click the second status “QFIN”

194
QFIN status has three Business Transactions.
1. The Radio Button of “Allowed” column is activated in the Business Transaction – Inventory
Posting required.

2. The Radio Button of “Allowed” & “Set” columns are activated in the Business Transaction –
Make Usage Decision.

3. The Radio Button of “Allowed” & “Set” columns are activated in the Business Transaction –
Start Inventory Posting after Usage Decision.

Define Appraisal Cost Recording

195
You make settings that allow you to settle the appraisal costs.
You can skip this step if you only want to record appraisal costs for inspection lots that were
created on the basis of production orders, or maintenance orders. In this case, you confirm and
settle the costs using the production order or maintenance order.

Implementation Guide for R/3 Customizing  Quality Management  Quality


IMG Path:
Inspection  Status Management  Define Appraisal Cost Recording.
Transaction Code QCC3

To be able to record appraisal costs, you must perform the following steps:
1. In Controlling, you must
a) Define activity types for inspection activities
b) Assign these activity types to cost centers
c) Define an activity price for each activity type
d) Enter the cost center in the work centers
e) Define order types for QM orders
f) Define settlement rules for the QM order types.
Note: The controlling data (activity type, cost center) are only valid for certain periods of time
(such as fiscal year).

196
2. In Customizing, you must define control keys for operations and activate the following
functions in them:
a) Costing
b) Confirmation
3. You must define these control keys in the inspection operations of the task lists.
4. You must predefine the activity types in the work centers and in the inspection operations
of the task lists
5. You must create QM orders in one of the following ways:
a) Collective generation and transfer to the inspection setup data for the material.
In this case, the order type is either copied from the inspection type or from the settings
at plant level. These types of QM orders are automatically copied into the inspection lot
b) Individual generation for the inspection lot
In this case, the order type is either copied from the inspection type or from the settings at
plant level.
Once these prerequisites have been created, you can record inspection activities for the inspection
lot when you record results or make the usage decision.

197
198
199
200
Influence of QM Results Recording on Confirmation
Controls the system message that appears when you confirm an order, if QM inspection results
must be recorded for an operation but no results are available yet.

201
202
Final/Partial Confirmation
Specifies what sort of confirmation is to be automatically proposed.

Propose activities
Specifies that the activity which according to planning has yet to be confirmed, is proposed for
confirmation by the system.

Deviation (in %) permitted for work in confirmation


If the confirmation exceeds the acceptable deviation, the system automatically issues a warning.

Deviation (in %) permitted for work in confirmation


If the confirmation exceeds the acceptable deviation, the system automatically issues a warning.

203
Sample Management

You make the settings for managing physical samples.


You must also consider the following work steps in other sections of the Implementation Guide,
depending on which functions you want to use in sample management:
 If you want the system to generate physical-sample records for inspection lots, you first
must define a physical-sample type for the corresponding inspection type
 If sample-drawing procedures are to take the lot container into account, you can
define the entry of a container for a goods receipt in the settings at plant level.
 You can predefine an appropriate
 Sampling procedure for managing samples in the settings at plant level.
If you want to record inspection results for physical samples, you must define a user field
combination for this inspection point type in Customizing for Inspection Planning. To do this,
use the function for identifying inspection points.

If the physical-sample drawing is to be authenticated by a digital signature, you must first define
a corresponding material authorization group.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Inspection  Sample Management.
Transaction Code QCC3

204
Define Physical-Sample Types

You define the physical-sample types for sample management.

Implementation Guide for R/3 Customizing  Quality Management  Quality


IMG Path:
Inspection  Sample Management  Define Physical-sample Types.
Transaction Code QCC3

205
Maintain Screen Control Key for Sample Types

You define the Screen Control Key for sample type.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path: Quality Inspection  Sample Management  Maintain Screen Control Key
for Sample Types.
Transaction Code QCC3

206
Define Physical-Sample Container

You define the physical-sample container for physical samples.

Implementation Guide for R/3 Customizing  Quality Management  Quality


IMG Path:
Inspection  Sample Management  Define Physical Sample Container.
Transaction Code QCC3

207
Storage Location for a Physical Sample
You define the storage locations for physical samples in Customizing for Sample Management.
Storing the physical sample after an inspection

Define Print Control, Forms, Print Programs

You set up the print control for the shop papers (print lists) to meet the needs of your company.

Implementation Guide for R/3 Customizing Quality Management 


IMG Path: Quality Inspection  Sample Management  Maintain Print Control, Forms,
Print Programs.
Transaction Code QCC3

208
Result Recording

You define certain aspects for recording and processing characteristic-related inspection results.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Inspection  Results Recording.
Transaction Code QCC3

209
Define Recording Configuration

You define various background functions for recording characteristic inspection results.

Define the required entry configuration, according to your requirements:


a) In the Settings at plant level and
b) As a parameter in the user master data
Activities
1. using the F1 field help, determine which background functions are possible when recording
characteristic inspection results.
2. Determine which background functions are required in your company, and maintain the
corresponding entries in the view.
3. Define the required entry configuration, according to your requirements:
o In the Settings at plant level and
o As a parameter in the user master data

Tip: You can also create the user parameters using the results recording transaction.
Note:
Do not confuse the Recording configuration dealt with in this step, with the Recording view.
You use the recording view to control the display of inspection characteristics on the overview
screens. You can choose between several predefined recording views and specify the recording
view you require in the inspection type or inspection operation. You can also set the recording view
as a user parameter.

210
211
212
Close when Choosing Continue
If this indicator is set when you record or change inspection results, the inspection characteristic or
partial sample will be closed automatically, provided that the following conditions have been met:
 The inspection scope indicator fixed scope or smaller scope is set in the inspection
characteristic.
 The target sample size has been reached.
 You have the authorization to valuate and close the characteristic or partial sample.
 You chose Continue after confirming the results for the characteristic or sample
Note
If you do not have authorization for the closing procedure, the characteristic or partial sample is
not valuated.

213
Define Origins of Results Data

You can define inspection result origins for inspection characteristics.


The user can specify a results origin during results recording, as long as the inspection
characteristic has the status "in process". The results origin entry is a source of information only.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Inspection  Results Recording  Define Origins of Results Data.
Transaction Code QCC3

Recorded results do not just come from an inspection. They can also come from:
 Technical data
 Quality certificates
 Batch specifications
Determine whether results origins must be defined and recorded for inspection characteristics, and
maintain the table if required.

214
Supplement Attributes of Inspection Characteristic Results

You can change the attributes of the inspection characteristic results. You can:
 Change the descriptions of the existing attributes
 Add your own attributes

Implementation Guide for R/3 Customizing  Quality Management  Quality


IMG Path:
Inspection  Results Recording.  Inspection Characteristic Results.
Transaction Code QCC3

215
Define Parameters for Calculated Characteristic.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path: Quality Inspection  Results Recording  Define Parameters for Calculated
Characteristic.
Transaction Code QCC3

216
Note:- Change the necessary function modules (SE37) - QEFC_FORMULA_CALC_EXAMPLE.

217
218
Define Parameters for Input Processing.

Implementation Guide for R/3 Customizing  Quality Management  Quality


IMG Path:
Inspection  Results Recording  Define Parameters for Input Processing.
Transaction Code QCC3

219
Enter Identifier for Units to be inspected

You define the control indicators in the inspection plan header that affect the recording of
information for the units to be inspected. These indicators determine whether:
 The entry of identifiers (for example, serial numbers) for the units to be inspected is:
o Not required
o Optional
o Mandatory
o The identifiers must be unique
 The identifiers must be unique
Irrespective of these indicators, you can also specify the inspection of single units using serial
numbers (in the inspection setup for material for each inspection type), if you define a serial
number profile in the plant data.  In this case, the recording of serial numbers has priority over
the control indicator settings in the inspection plan.

Implementation Guide for R/3 Customizing  Quality Management  Quality


IMG Path:
Inspection  Results Recording  Enter Identifier for Unit to be Inspected.
Transaction Code QCC3

Activities
1. Determine whether and how the identifiers for units to be inspected are recorded in your
company.
2. You can delete unnecessary table entries and adapt the remaining keys and short texts as
necessary.
Note: Do not delete the entry contained in the standard system <blank> with short text <blank>!
This entry is used to improve the ergonomics of the interface, if the function is not used.

220
No External Numbering of Units to Be Inspected
Means that during results recording external numbers (e.g., serial numbers) cannot be assigned to
individual test units.

External Numbering of Units to Be Inspected is Optional


Means that during results recording external numbers (e.g., serial numbers) can be assigned to
individual test units.

External Numbering of Units to Be Inspected is required


Means that during results recording external numbers (e.g., serial numbers) have to be assigned to
individual test units.

221
Define Filter for Inspection Characteristics

You determine which inspection characteristics are displayed for certain transactions (for example,
for results recording and for the usage decision).
This depends on:
 The control indicators for the inspection characteristic
o Optional characteristic
o Required characteristic
 The recording status of the inspection characteristic
o In the skip
o In process
o Valuated
o Closed
o Fixed
o Blocked
o Transferred to a subsystem for processing
 The valuation of the inspection characteristic
Characteristics for partial samples can also be selected.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path: Quality Inspection  Results Recording  Define Filter for Inspection
Characteristics.
Transaction Code QCC3

Activities
1. Determine whether all of the transactions in the table (for example, for results recording - QE0x
- and for the usage decision - QA1x -) are used in your company and whether the characteristic
filters required in your company differ from the standard setting.
2. If necessary, modify these characteristic filters.

222
Recommendation
Do not change the standard settings. Do not delete any entries!

223
Define Number Ranges for Characteristic Confirmation

You define the number range interval for the completion confirmation numbers of the inspection
characteristics.
The completion confirmation numbers are assigned automatically by the system (internal number
assignment). You can modify the number interval and the current number level.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path: Quality Inspection  Results Recording  Define Number ranges for
Characteristic Confirmation.
Transaction Code QCC3

Standard Settings
In the standard system, the eight-digit number interval is used to the fullest extent.

Recommendation
Do not change the default setting.

224
Make Settings for Copy of Inspection Results

You use this IMG activity to make settings for the copy inspection results function that are
absolutely necessary if you wish to use this function.
The settings are relevant to the inspection type and the plant of the inspection lot into which the
results are to be copied.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Inspection  Make settings for copy inspection results.
Transaction Code QCC3

Inspection Type Plant Control in Inspection lot Control in RR


01 1210 3 Manual & Automatic 2Automatic Data Transfer When accessing
Results Recording
0101 1210 3 Manual & Automatic 2Automatic Data Transfer When accessing
Results Recording

225
Uncheck Log

Check Log

Inspection Plant Close Origin TL Data Origin Selection Mapping Delay Log
Type RR Days
01 1210 Make No setting Previous 300 100 0 No Tick
Tick inspection mark
mark point
0101 1210 Make Previous Previous 300 200 0 Make
Tick inspection inspection Tick
mark point point mark

Note: In the inspection plan for each MIC to which you want to copy, you have maintained in
General Data  Origin Result data  04 previous inspection points.

To activate EA-PLM business function using Transaction SFW5 .

Go to T-code SE80 Enter the Function group, QEEM and Goto the GUI Status E110, if the status is
inactive, please press Activate (Ctrl + F3).
Check BADI QEC_RESULT_COPY, QEC_SELECTION and QEC_MAPPING are implemented (SE18).

226
Dynamic Modification

In a sequence of inspection lots, dynamic modification controls the inspection scope with regard to
inspection characteristics and sample sizes, so that a predefined quality goal is achieved in the
majority of cases. To reach this goal, the system determines the inspection stages after each usage
decision for the subsequent lot of a material, by using dynamic modification rule defined in the
task list. The system then updates the quality level. This update can take place at various
dynamic modification levels.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Inspection  Dynamic Modification.
Transaction Code QCC3

227
Define Reference Dynamic Modification Level

You specify the initial inspection stage for when you are creating a new quality level. The system
can either take the initial inspection stage from the dynamic modification rule, or can suggest an
inspection stage from one of the reference dynamic modification levels as the initial inspection
stage.
Implementation Guide for R/3 Customizing  Quality Management 
IMG Path: Quality Inspection  Dynamic Modification Define Reference Dynamic
Modification Level.
Transaction Code QCC3

Activate Dynamic Modification Level Reference


If you set this indicator, you activate the reference dynamic modification level
Requirements
You perform inspections using sampling procedures and a dynamic modification rule.
Standard settings
The dynamic modification levels are already logically linked.
Recommendation
Keep the standard settings for the reference dynamic modification levels.
Activities

228
Check whether you need to deviate from the standard settings, and if required make different
settings.
Quality Control

This section describes the procedure for defining settings for quality control using the QM
component.
Evaluations of the following transaction data form an integral part of quality control:
 Original datasets, for example for inspection lots and Q-notifications
 Compressed data in the QM information system.
Note
Take note of the connection to the step Archiving in the section Basic Settings and Environment 
Central Functions

Quality Management Information System

You can make settings for data processing in the Logistics Information System (LIS). These
settings are part of the LIS settings. You can find additional information in the Implementation
Guide section on the Logistics Information System Logistics Data Warehouse.
More details are in the sections
 Update Control
 Data basis, Tools Set Up
The QM component provides the LIS with data from quality inspections and quality notifications.
 Quality Inspection
See section Quality Inspection / Information System for the relevant settings.
 Quality Notification
See section Quality Notification / Information System for the relevant settings.

229
Define Update for Each Origin

You define the summarization and updating of the inspection lot data by specifying an update
group for each inspection lot origin.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Inspection  Information System  Define Update for Each Origin.
Transaction Code QCC3

230
Standard settings
Suitable update groups have already been defined in the standard system for all possible inspection
lot origins.

Actions
1. Determine whether the assignments of update groups to the inspection lot origins predefined by
SAP meet your requirements.
2. If necessary, modify the table according to your requirements.

231
Divide Quality Scores into Classes

In this step:
 You define the classification of quality scores for inspection lots into a maximum of five
classes.
 You assign these classifications to the information structures that have been defined in
the LIS for update purposes.

Implementation Guide for R/3 Customizing  Quality Management  Quality


IMG Path:
Inspection  Information System  Divide Quality Score into classes.
Transaction Code QCC3

232
233
Standard settings
Both uniform and exponentially weighted classifications are predefined in the standard system. The
uniform classification is proposed as the default.

Activities
1. Coordinate the classifications for the quality scores on a company-wide basis and maintain the
class limits in the table.
2. Assign the required classification to each information structure.

234
235
Activate Workflow Template

You activate the workflow template that is to run in inspection processing.


For more information, see the section Environment / Central Functions / Activate Workflow.

Subsystems

You can link CAQ subsystems to the R/3 System, in order to implement solutions for special tasks.
Depending on what types of general conditions need to be fulfilled, different procedures are
available:

236
5.0 Quality Certificates
The section 'Quality Certificates' is a part of the Implementation Guide for the QM (Quality
Management) component.
Quality certificates (or certificates as they are commonly called) apply to certain materials; they
can be created for different objects in the R/3 System:
 In the QM (Quality Management) component for the inspection lot
 In the MM (Materials Management) component for a Batch
 In the SD (Sales and Distribution) component for a delivery
The integration of the certificates in the SD component means that the settings in QM to a great
extent overlap with the settings in the SD component. Since you have to coordinate some of the
settings in the QM module with those in the SD module, access certain tables in the SD component
and have appropriate skills in this area, it may be advisable to have an SD expert make these
settings.

Important: The function for creating certificates is not active in the standard system! To activate
the function, you must:
 Maintain an output determination procedure.
 Assign this output determination procedure to the relevant delivery item categories.

You can design the certificate layouts with considerable flexibility and thereby fulfill a variety of
requirements; from simple quality certificates (without reference to quality characteristics) to
certificates of specification (with reference to general values of quality characteristics) and
inspection certificates (with references to values of quality characteristics, which are determined for
a specific batch). You can combine the elements of these basic certificate types in any combination
and you can design the certificate forms freely, allowing you to satisfy all requirements in terms of
form and content.

You can tailor the layout and content of the certificates to the needs of the partner for whom the
corresponding delivery item is intended.
Finally, you can also flexibly define the printing and dispatch parameters for the certificates.

Recommendation
Before you make any changes to the default settings, test the function for creating certificates
using the settings and sample data contained in the standard system. Follow the instructions
described below:
1. Make sure the following conditions have been fulfilled:
o Create a certificate profile; in the profile, assign the sample form QM_CERT_01
(contained in the standard system) to the profile.
o Create a material and make sure all of the data that is required by the certificate is
available for the material (for example, the characteristic results).
o Set the print control parameters.
2. Release the certificate profile and assign it to the material.
3. Define the output dispatch:
o Define an explicit certificate recipient ('goods receipt' function). Use the output type 'LQCA'
and set the dispatch time to '3.'
4. Create a delivery for the material.
o Create a customer order in the SD component (type 'TA').
o Create a delivery with an item for the material in question.

237
o Post the goods issue.
5. Check the delivery item to see if the system created an output.
6. Trigger the certificate dispatch for this delivery item and check whether a print job was created
for the required certificate.
Certificate Profile

You make the settings for the certificate profiles. You are also required to create the necessary
certificate profiles (master data).
A certificate profile specifies:
 What information is to be contained in the certificate:
o Default values
o Inspection results
o Texts
 The origin of the data in the certificate:
o Master inspection characteristics from task lists
o Batch characteristics from material specifications
o How the data is be displayed
Make sure the profiles are compatible with the certificate types.

Requirements
If you want to access quality characteristics in the certificates, you must have previously
maintained these characteristics as one of the following:
 As characteristics in the classification system
 As master inspection characteristics

Standard Settings
Client 0 in the standard system contains at least one example of a layout set. This layout set uses
four standard texts.
 The sample layout set is stored under the generic name QM_QCERT*.
 The standard texts are stored under the generic name QM_QCERT*.
Be sure to note the remarks about the MAIN window in the layout set that has been provided as an
example (select text elements!).
To be able to use the example, you must copy the corresponding standard texts to the current
client.
Activities
1. Design the layout for your certificates.
2. Complete the SAP script layout sets and standard texts used for this purpose. Use the example
contained in the standard as a basis.
o Create layout sets.
o Create standard texts.
o Create profiles.

238
Implementation Guide for R/3 Customizing  Quality Management 
IMG Path:
Quality Certificates  Certificate Profile.
Transaction Code QCC2

Define Status Profile for Certificate Profiles

You can define your own status profiles for certificate profiles. These are then assigned to the
certificate type.

Activities
1. Check whether user statuses are required for certificate profiles.
2. Define the corresponding status profiles.
Further Notes
For more information, please refer to the chapter Environment, Central functions, General Status
Administration, Status Profile

239
Define Certificate Types
You define the certificate types.
You only define the keys and short texts for the certificate types. When you define the certificate
profiles, you must make sure the certificates conform to the standard type in both form and
content.
You can assign a status profile to each certificate type.
Recommendation
 Note that the table of certificate types is used both in procurement and Sales & Distribution.
 Define the certificate types according to the applicable standards.

Activities
Determine which certificate types are required in your company for procurement and
sales/distribution and define these certificate types in the table.
Further Notes
Refer to the chapter 'Environment' for information on the general status management function and
the status profile
Maintain Form
You maintain the SAP script forms for the certificate profiles.
Requirements
To process forms, you need to have experience in SAP script.
Standard Settings
The standard system provides the universally applicable QM_QCERT_01 form.
Recommendation
Use this form as it is, or use it as a copy model for your requirements.
Activities

240
Determine whether you need your own forms for quality certificates and ensure that these are
created to accepted standards.
Also determine whether you need your own function module for data retrieval, or whether you
need to adapt the output program.
Define Data Origin
You define data origins for certificates.
If you are using certificate types which contain value information for inspection characteristics or
class characteristics, the values can have the following origin:
 Default values for characteristics
o From master inspection characteristics
o From batch specifications
 Results for characteristics
o From result records for the inspection lot or partial lot
o From batches
You can define sources for language-specific characteristic short texts irrespective of the origin of
the value specifications:
 Characteristics from a certificate profile
If no text is found here, the system accesses further master records:
o Master inspection characteristics
o Class characteristics
If the results are loaded from inspection lots or partial lots, you must specify strategies for the skip
procedure when maintaining the certificate profiles.
If the results for inspection points or samples were loaded, the mean values and original
values for the last inspection point or last sample (or for all inspection points or samples in an
inspection lot) can be included in the certificate.
You can define keys for all of the listed data origins in the system and assign function modules for
data retrieval to these keys.

In certain circumstances you need to include differing materials in certificates, for example, if the
same material is sold in different forms, but the properties of the material remain the same.
To avoid incorrect assignments of data origins, you define allowed combinations of data origins for
characteristic specifications and characteristic values. You can also define that specifications and
values must come from the same source.
Standard Settings
The system already contains predefined keys and function modules for the data origins.
Proposals are also implemented in case of a skip.
Recommendation
Use the data origins set in the system. Consult an expert if you want to implement your own data
origins.
Do not change the function modules implemented in the standard system. Create your own
function modules, if necessary. Use the available function modules as copy models, for the
interfaces in particular.
Activities
You can use the online documentation for the table fields and function modules to determine from
where the system retrieves the characteristic data in the standard system. It is only necessary to
define your own origins and function modules if this manner of retrieval is not acceptable. In doing
so, consider the following origins:
1. Origin of the default values.
2. Origin of the short texts.
3. Origin of the result values.
4. Alternative strategy in case of a skip.

241
5. Allowed combinations of default origins and characteristic values.
The report RQCFTQ65 determines the usual combinations using the characteristic data in the
existing certificate profiles and makes entries in the table.

242
243
244
245
246
247
248
Profile Determination

You determine how the certificate profiles are found.


The certificate profile determination function uses condition functions from the Sales and
Distribution module.
The source element is the so-called plan. Usually, a plan can contain several lines with condition
types that are processed in sequence. Processing can be subject to conditions.
Every line uses a certain condition type that in turn refers to an access sequence. The access
sequence determines the sequence in which the condition records are accessed from the condition
tables.
The user can define the keys for condition tables by selecting one or more fields from a field
catalog.
The system searches for the certificate profile that matches this key when a certificate is created. If
it does not find a reference under this key, it searches further keys in accordance with the access
sequence.
The condition technique used here for profile determination is also used for output determination
where it is implemented to an even greater extent.
Implementation Guide for R/3 Customizing  Quality Management 
IMG Path:
Quality Certificates  Profile Determination.
Transaction Code QCC2

249
Define Access Sequence for Profile Determination

You maintain the access sequence that is used to find the certificate profile.
The system searches for the certificate profile sequentially using the condition records contained in
the access sequence.

250
Standard Settings
The system contains an access sequence QCA1 as an example. This access sequence ranges from
special to general and contains the condition tables:
 Material + customer + partner function
 Material
 Material group

Activities
Define a suitable sequence of conditions for your application in the access sequence QCA1 or define
your own access sequence.

Further notes
Note that this setting is applies to all clients!

251
Define Condition Type for Profile Determination

252
You maintain the condition type to determine the certificate profiles.

Standard Settings
The current release has only one predefined condition type.
Activities
Check whether condition type QCA1 exists in the system and whether it contains the access
sequence QCA1 (or an access sequence you have defined yourself).

Output Determination

253
You define the settings for output determination; that is, you determine how the certificate
recipient is found and assigned. The certificate recipient here means: partner function (for
example, sold-to party or goods recipient) and shipping type (for example, fax, immediate
shipping, language English).
The technical concept of the output determination function is identical to that used for profile
determination. However, the options contained in the concept are used to a greater extent for
output determination.
The output determination concept is described in detail in the Implementation Guide for the Sales
and Distribution module. Refer to the chapter Basic Functions, Messages with the subchapter
Output Determination and the section Message Default for Condition Technique.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Certificates  Output Determination.
Transaction Code QCC2

Define Access Sequences for Output Determination

254
You determine the access sequences for output determination.
The procedure is identical to the one used to define the access sequences for profile
determination.

Standard settings
The system contains an example of an access sequence that progresses from special to general
access with the condition records
 Sales organization + distribution channel + division + customer
 Sales organization + customer

Activities
Set the access sequences that are suitable for you application.

Define Condition Types for Output Determination

255
You define condition types for the output determination.
The condition types correspond to the output types contained in an output determination
procedure.

Standard settings
The following condition types are set up in the standard system:
 LQCA (for quality certificates intended for the ship-to party)
 LQCB (for quality certificates intended for the sold-to party)

Recommendation
Use the condition types that are available in the standard system. If your system has a link to the
archive, you can activate it by selecting a suitable archiving mode.

Activities
Check the details of the condition types. In doing so, be sure to refer to the field documentation.

Further notes
With respect to the partner function, also refer to the step Define partner for each output.

256
Define Exclusion Conditions

257
You can define exclusion conditions that prevent certain condition types in the output determination procedure
from being accessed.

Example
You want to prevent the same addressee from receiving several versions of a certificate if the sold-
to party and goods recipient are identical.
Activities
1. Determine whether conditions can occur, under which certain condition types are not to be
carried out.
2. Formulate these conditions in ABAP/4 FORM routines.
3. Store these routines in the table and assign them the Shipping V2 application.

Further notes
The conditions can also be used in the access sequences.
You can define your own conditions. Technical instructions for doing so can be found in the
Implementation Guide for the Sales and Distribution module in the chapter System Modification,
subchapter Routines, section Conditions.

Output Determination Procedure

258
You edit the output determination procedures for creating certificates.
The output determination procedure contains one or more condition types, that is, it can trigger
one or more individual outputs (certificates).

Edit Output Determination Procedure

259
You define the output determination procedure.
The output determination procedure contains all condition types, that is, all messages which are in
turn processed in accordance with certain conditions. Messages are implemented at different levels
of the delivery. Certificates are messages for the delivery item. If the schema contains two
condition types, for example, two certificates can be issued.
The output determination procedure can link the condition types contained in it to conditions which
prevent further processing.

260
Standard settings
The determination procedure V20001 contained in the standard system contains all of the
messages for the delivery item. It refers to the condition types LQCA and LQCB. If this procedure
or the entries contained in it are not contained in the current client, then you must copy the
determination procedure V20001 and the corresponding control with condition types LQCA and
LQCB from client 000.

Recommendation
Keep the schema V20001 contained in the standard system.

Activities
1. Check whether you want to maintain the condition types predefined in the standard system.
2. Check the conditions linked to the condition types.

Read the long texts for the conditions.

Define Partner for Each Output

261
You determine the partners for each output.
You determine the output medium and the functions of the partners who should receive the output
for each output type.

Implementation Guide for R/3 Customizing  Quality Management  Quality


IMG Path:
Certificates  Profile Determination Define Partner for Each Output.
Transaction Code QCC2

262
263
Requirements
The partner functions are defined.
The following partner functions are predefined for quality certificates:
 goods recipient
 sold-to party
 Q1 quality certificate recipient at the goods recipient
 Q2 quality certificate recipient at the sold-to party

Activities
1. Check the partner functions contained in the system. These may have to be adapted.
2. Allocate the appropriate partner functions to the condition types (individual messages).

Further notes
Partner functions are also required for other applications, for example, quality notifications. For
detailed notes on maintaining partner functions, please refer to the Implementation Guide for the
Sales and Distribution module in the chapter Basic Functions, subchapter Partner Determination,
and section Partner Functions.

264
Process Output

You make the necessary settings to create the certificates. This includes making the preparations
to print the certificates and dispatch the outputs.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Certificates  Process Output.
Transaction Code QCC2

265
Set Print Parameters

You set the output parameters.


Standard Settings
In the standard system, there are entries for the condition types LQCA, LQCB.

Activities
1. Determine which output locations are possible for each condition type.
2. Maintain the output parameters for each condition type and position

Assign Print Program to Output Type/Medium

You assign the processing programs to the output types (condition types) and the media used.

266
Standard Settings
The message processing program RQCAAP00 is implemented in the standard system for both
condition types LQCA and LQCB.
Activities
1. Determine the output media (printer, fax) on which the certificates are to be issued.
2. If the processing program RQCAAP00 does not fulfill all of the requirements, create your own
processing programs and assign them to the output types in the table.

267
Define Output Types with Certificate *

You define with which output types and transmission mediums certificates can be issued.
You only need to maintain these settings, if you want to create certificates for delivery items in the
Internet.

Output Processing from Internet


Indicator for processing output from the Internet.
Set the indicator if you want to process output from the Internet for this output type and the
specified transmission medium.

Storage Display from Internet


Identification for the display of stored output from the Internet.
Set the indicator if you want to display output for this output type and the specified
transmission medium in the Internet from the storage system.
Example
If your business partners want to access certificates for output type LQCA from the archive using
the Internet, enter output type LQCA and dispatch type 1 (print output) in the table, and set the
indicator "Archive".

268
6.0 Quality Notifications

This chapter contains instructions on how to use the quality notifications and functions for defects
recording.
In the course of processing problems and initiating corrective actions, the quality notification
supports you in a number of tasks. These tasks include:
 Documenting the nature of the problem
 Diagnosing the defects
 Defining and implementing tasks
 Recording costs
 Managing the statuses of notifications and tasks
 Communicating with the parties who are involved with the problem
 Evaluating the notification data
While you can use the quality notifications independently of the other functions in the QM
application component you can also create quality notifications using these other functions (for
example, when you record defects for an inspection lot).

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Notification  Overview of Notification Type.
Transaction Code QCC1  Notification, QCC2  Q-Notification

269
Overview of Notification Type

This step gives you an overview of:


 The notification types that is available in the system.
All notification types for all notification categories and notification origins are listed.
 The settings of a particular notification type
you can display all assignments of notification parameters for
one notification type.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Notification  Overview of Notification Type.
Transaction Code QCC2

Activities
When implementing notifications, first work through the sections Notification Creation and
Notification Processing. These provide an ideal basis for using this function.

270
Notification Creation

You define the notification types and their basic functions.

Notification type
 Quality notifications:
o Customer complaints
o Complaints against the vendor
o Internal problems

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Notification  Notification Type  Define Notification Type.
Transaction Code QCC2

271
272
Early Number Assignment
Indicator that causes the notification to be assigned a number when the create function is first
called, and not just when it is saved.

273
Define Number Ranges

You define number ranges for the notifications. You must specify a number range for each
notification type. You can also assign several quality notification types to a single number range (a
group).

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Notification  Notification Type  Define Number Range.
Transaction Code QCC2

Activities
1. Define which notification types or groups of notification types can be distinguished on the basis
of the number ranges. If appropriate, you can give the groups titles.
2. Reserve the number ranges for the notifications and assign the corresponding notification types
to these number ranges.

274
275
276
277
278
279
280
Define Screen Templates

You structure the screen templates you want to use for quality notifications.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Notification  Notification Type  Define Screen Templates.
Transaction Code QCC2

281
Screen Areas.

You can assign the groups of information contained in the quality notifications to various tab pages
and screen areas to give a flexible structure to the screen templates. You perform the following
tasks in separate screen areas.

282
Customer complaints

283
284
Screen templates

10TAB01 040 Reference documents


Header Details 035 Contact Person
031 Subject and long text
005 Reference object
10TAB02 010 Processing
Processing 045 Organization data
10TAB03 Cause 018 Cause (Root cause analysis)
10TAB10/13 Item Defective item
10TAB11/14 Task Corrective action & preventive action
10TAB12/15 Activities Activities

285
Notification: Tab Header
The text entered here is used as a label for the tab page.

Function Icon
Icons that are display the function on the screen.

Tab in Notification Processing Active


If the indicator is set, the tab strip control is active.
If the indicator is not set, the tab strip control is inactive and the tab strips are hidden.

Notification: Screen Area


The tab page is composed of a maximum of five screen blocks. You can determine which
information is located in which position. You can select the available screen blocks from the list of
possible entries.

Note:
Tab pages 10\TAB are at header level and tab pages 20\TAB at item level in the Q-notification.

286
Complaints against the vendor

Screen templates

10TAB01 040 Reference documents


Header Details 035 Contact Person
031 Subject and long text
005 Reference object
10TAB02 010 Processing
Processing 045 Organizational data
10TAB03 Cause 018 Cause (Root cause analysis)
10TAB10/13 Item Defective item
10TAB11/14 Task Corrective action & preventive action
10TAB12/15 Activities Activities

287
288
289
Internal problems

290
291
Screen templates

10TAB01 040 Reference documents


Header Details 035 Contact Person
031 Subject and long text
005 Reference object
10TAB02 010 Processing
Processing 080 QM Order
10TAB10 Item Defective item
20TAB01 Item overview Item overview
20TAB02 Item cause cause
20TAB03 Item tasks Corrective tasks
20TAB03 Item activities Corrective activities

292
293
294
Initial Screen

You can cause the system to offer additional recording screens when you access the quality
notification by assigning the corresponding function modules and initial screens to the
notification types. The system contains examples of this.

295
Long Text

You can control the formatting of the long text on the notification screen. If required, the system
can
 Automatically insert log lines
 Prevent changes to text

296
Log Line for Long Text Change
If you set this indicator, a log line will be added to any long text that you change when processing
the notifications. In this manner, the history of long text changes can be traced.

No Changes to Existing Long Text


If you set this indicator, changes to an existing long text cannot be made while processing the
notifications. However, the long text can be supplemented.

297
Allowed Change of Notification Type

You define the changes to the notification type that are allowed.
This step only deals with the changes to the notification types that are made when you create or
change notifications using the simplified transactions (IQS21 or IQS22).

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path: Quality Notification  Notification Type  Define Allowed Change of
Notification Type.
Transaction Code QCC2

298
You have created a notification of type "General notification" and want to change this into a
notification of type "Quality notification" to record defect data in the notification items.

Notification Content

You use catalogs and catalog profiles to define the range of values for the qualitative
information contained in the notification. You then assign catalogs and catalog profiles to the
notification type.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Notification  Notification Content.
Transaction Code QCC2

299
Maintain Catalogs

You define the contents of the notifications while also taking the next step into consideration
(defining the catalog profiles). This means that you must:
 Define which elements (for example, catalog entries, short text, and long text) of the
notifications will be used and which information these elements will contain
 Organize and maintain the catalogs that are used for the notifications and the defects
recording function
Example
Depending on the scope of your catalog profile, you may need catalogs for:
 Problem descriptions (coding) at the notification header level
o Defect criteria at the notification item level
o Defect type
o Defect location
o Defect cause
 Tasks and activities
You can define tasks and activities on two levels in the notification:
o Notification header (immediate tasks, immediate activities)
o Notification item (tasks, activities)
Important: in the notifications, you can only use code groups at the plant level (and not selected
sets). As an alternative, you can limit the selection of available catalogs with the help of the
catalog profile.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Notification  Notification Content  Maintain Catalogs.
Transaction Code QCC2

300
301
Define Catalog Profile

You define the catalog profiles for notifications.


Definition
A combination of code groups from several catalogs that have been grouped together as allowed
values for notification processing or defects recording.
The catalog profile is defined and assigned to the notification type. You can also assign a catalog
profile to a:
 Material in the material master
 Report type in defects recording
A catalog profile assigned to a material master or report type has priority over a catalog profile
assigned to a notification type.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Notification  Notification Content  Define Catalogs Profile.
Transaction Code QCC2

302
303
Use
The catalog profile has two primary functions for notification processing:
 It controls which code groups you can access from the individual catalogs, to record defects,
tasks, and activities in a quality notification.
 You can store a default class in the catalog profile under which a defect item can be
classified in the R/3 System’s Classification System.
You can use the catalog profile, for example, to restrict the selection of codes to specific types of
defects or damage, based on the notification type.

304
Activities
1. Define the required code groups for each catalog in the catalog profile.
a) You should agree with all other catalog users how to best define the eight character
mnemonic keys for the code groups. Make a note of the generics of the keys. For example, you can
specify that separate code groups be created for each notification type and that the first two
characters correspond to the notification type.
b) Define the maintenance of the code groups. You can maintain the codes in retrospect.
c) Determine whether you want to classify the notification items. If necessary, create the
classes in the classification system and assign them to the catalog profile. The class characteristics
should be defined and maintained at the same time.
Class type 15 is provided for classifying notification items.
If required you can record class characteristic values in a dialog box when you process classified
notification items.

305
Activities
1. If you want to use the defects recording function, determine:
o Whether you want to valuate defects
o Whether a unit of measurement should be predefined in the catalog profile for this
purpose. The unit of measurement must have been defined previously. Refer to the
step Units of measurement in the chapter Basic Settings and Environment.

306
Catalogs and Catalog Profiles for Notification Type
307
1. Define the information that is to be entered for the notification item and choose the most
appropriate catalog.
2. Define the catalog profile for the notification type, if this did not already take place when the
notification type was created.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path: Quality Notification  Notification Content  Catalogs and Catalogs Profiles
for Notification Type.
Transaction Code QCC2

Activities
1. Define the information that is to be entered for the notification item and choose the most
appropriate catalog.
2. Define the catalog profile for the notification type, if this did not already take place when the
notification type was created.
3. Activate the Classification of the notification items, if you want to use class characteristics to
store additional information for the notification item.

308
Example
Depending on the scope of your catalog profile, you may need catalogs for:
 Problem descriptions (coding) at the notification header level
 Defect criteria at the notification item level
o Defect type
o Defect location
o Defect cause
 Tasks and activities
You can define tasks and activities on two levels in the notification:
o Notification header (immediate tasks, immediate activities)
o Notification item (tasks, activities)
Important: in the notifications, you can only use code groups at the plant level (and not selected
sets). As an alternative, you can limit the selection of available catalogs with the help of the
catalog profile.

309
Partner

You define the partners who are involved in the notifications.


Depending on the notification type, different partners may be involved in a notification. These
partners can play various roles.
When you define the partner functions, proceed as follows:
 Define partner determination procedures that contain the relevant partner functions.
Define the appropriate partner type for each partner function.
Assign the partner determination procedure to the notification type.
The possible partner types are predefined in the system.
 For each partner type, define the fields displayed in the partner lists.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Notification  Partners.
Transaction Code QCC2

310
Define Partner Determination Procedures

You define the partners for processing notifications.


Several partners are usually involved in processing a notification - internal and external partners.
The types of partners and their functions can be different for each notification type.

Certain partners have been predefined in the system; for example, the following partners apply to
notifications:
 Customer (customer number)
 Vendor (vendor number)
 Person (personnel number)
 System user (SAP user)
 Organizational unit

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Notification  Define Partner Determination Procedures.
Transaction Code QCC2

311
Activities
1. Define the partner functions and the partner determination procedures.
o Define the partner functions.
If required, assign multilingual keys to the partner functions
o Define the partner determination procedure and determine which functions are
contained in each procedure.
2. Assign a partner determination procedure to each notification type.
3. Specify the appropriate partner function in the notification header for each notification type.

312
Define the partner functions and the partner determination procedures.

Function Determination

One business partner can be assigned other business partners using function determination.

Partner Determination Procedure


A grouping of partner functions. The procedure specifies which partner functions are allowed for
a particular business transaction (for example, for processing a sales order) and which of those
partner functions are mandatory.

Partner type
Partners can be:
 Internal partners (for example, internal employees or partners in the HR Human Resources
system)
 External partners (for example, customers, vendors, or manufacturers)

313
Partner function
The various partner types can be subdivided into partner functions. The partner function defines
the rights, responsibilities and tasks of each partner during the processing of a business
transaction.

Notification Type Partner Functions for Partner Functions for Tasks


Notification Header
Customer complaint (Q1)  Sold-to party User responsible
 Contact person
 Implementing department
 Coordinator
Complaint against vendor  Vendor User responsible
(Q2)  Manufacturer
 Implementing department
 Coordinator
Internal problem report  Author User responsible
(Q3)  Implementing department
 Coordinator

314
Define the partner functions.

Define the partner determination procedure and determine which functions are contained in each
procedure.

Author:
The Author is the person who will create the Internal Problem Notification. This will be for example
the Shift Operator or the Quality Inspector in the Laboratory.

Coordinator:
The Coordinator is the overall person responsible for the notification. He must track the notification
and make sure that all Tasks in the notification are carried out successfully.

User Responsible:
The User Responsible is any person required to carry out correction tasks and corrective actions.

315
Assign a partner determination procedure to each notification type.

316
Specify the appropriate partner function in the notification header for each notification type.

317
318
Partner Function for Implementation (Department)
Abbreviation that identifies the partner function for the implementing partner (this means the
department responsible in the partner overview for the notification, maintenance order, or service
order.
Notification Type with Approval Procedure
Set this indicator, if the notification is to be subject to an approval procedure.
Do not set this indicator if the notification is not to be subject to an approval procedure.

319
Notification Processing

You define a number of controls that will be needed to process notifications.


This includes:
 Additional controls that pertain to the notification type; for example:
o Priority of the notification
o Response monitoring
o Print control
 Miscellaneous controls

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Notification  Notification Processing.
Transaction Code QCC2

320
Additional Notification Functions

You define additional functions that you can call up when processing notifications.
SAP delivers some examples of these functions with the standard system; users can also add their
own functions.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path: Quality Notification  Notification Processing.  Additional Notification
functions
Transaction Code QCC2

321
Define Action Box

You define additional functions (activities) that can be performed during the processing of a
notification. You define these functions using a key and an identifier and they are assigned to a
notification type. The follow-up functions appear in a separate screen section (action box) in the
header, when you process notifications.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path: Quality Notification  Notification Processing.  Additional Notification
functions  Define Action Box.
Transaction Code QCC2

322
Activities
1. Determine which recurring functions you can define, dependent on the notification type.
2. Define these functions. Perform any programming necessary for the function modules you
require. Proceed as follows:
o Define the key and identifier for the function
o Assign a function to the notification type
o Define the controls for the function
o Enter a function module with the required flow logic (optional)
o Define icons and text
o Enter code group and code for the task or activity from the catalog that is assigned to the
notification type, if the function is to be documented as a task or activity.
You must enter a status for the task that is to be included in the notification.
3. Determine if tasks are to be supplemented by the workflow and define the workflow tasks if
required. If the assigned function module has a container for the Workflow task, the container must
also have an entry.
4. Determine whether the functions are to be triggered in a particular sequence and if so, define
the dependent follow-up functions.

323
Action Box
You define the functions, with which you can generate tasks or activities (known as
supplementary actions) for a notification. These functions should be defined using a key and a
label. They are assigned to a notification type, and are available at header level when processing
notifications. When the function is called up, the system copies the task or activity defined into the
notification.

324
The standard system contains some example functions as ideas and models for your own definition.
You can find the relevant function modules using the following generic keys:
 QM06_FA* Function modules for activities
 QM06_CO* Function modules for changes to the workflow container

Dependent follow-up function


(The follow-up function is dependent one another follow-up function)
As simple functions that can be performed repeatedly and that are independent of other follow-up
functions.
Only performed once
(It is only to be performed once, or several times)
These follow-up functions are then dependent on other follow-up functions being executed first and
if required, may only be performed once.

325
The standard system contains some example functions as ideas and models for your own definition.
You can find the relevant function modules using the following generic keys:
 QM06_FM* Function modules for tasks
 QM06_CO* Function modules for changes to the workflow container

326
The standard system contains some example functions as ideas and models for your own definition.
You can find the relevant function modules using the following generic keys:
 QM06_FM* Function modules for tasks
 QM06_CO* Function modules for changes to the workflow container

327
The standard system contains some example functions as ideas and models for your own definition.
You can find the relevant function modules using the following generic keys:
 QM06_FM* Function modules for tasks
 QM06_CO* Function modules for changes to the workflow container

328
Dependent follow-up functions

329
330
Vendor Complaints – Quality Notification Action box and follow-up actions for tasks
 Stock transfer postings
 Quality inspections
 Return deliveries
 Debits or credit memo requests
 Send mail

331
Define Follow-Up Actions for Tasks

You can define follow-up actions for tasks.


You can define a series of follow-up actions that the system will carry out sequentially.
For each follow-up action, you must define:
 The level at which the follow-up action will be effective.
(Only the task level is relevant.)
You can also define:
 How the update will be processed.
 When the follow-up action will be triggered; that is, with which business transaction will the
follow-up action be carried out
(The system will check whether the user has authorization for this transaction.)

332
Activities
1. Determine which follow-up actions for tasks are needed in your company and which should be
automated.
2. For automatic follow-up actions, define:
o The series of function modules and their update form
o The business transactions for the follow-up actions (provided the function module is to be
linked to the status management function for the task)
3. Maintain the table of follow-up actions.
4. Create the corresponding function modules.

333
Print Control

You define the print control for the notification shop papers. In particular, you specify:
 The type and format of the shop papers
 Where the shop papers are to be printed
 The archiving mode (provided an archiving link is active)

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Notification  Notification Processing.  Print Control.
Transaction Code QCC2 and Printer Setting-CQ85

334
Define Shop Papers, Forms, Print Programs

You specify:
 Which shop papers will be printed and archived
 The form in which these shop papers will be printed and archived
 Which shop papers will be printed for which notification types

Implementation Guide for R/3 Customizing  Quality Management  Quality


IMG Path:
Notification  Notification Processing.  Print Control  Define Shop Papers.
Transaction Code QCC2

335
Activities
1. Determine which shop papers are needed for the notifications.
o Determine whether you need shop papers other than the ones already provided in the
standard system.
o If necessary, have a qualified person create the ABAP reports and SAP script layout sets for
these shop papers.
o Define these shop papers in the table.
2. For each document type (notification type), specify which shop papers are available for printout
and whether these shop papers should be displayed with a selection indicator.

Notes:
 The user can change the selection indicator manually when printing the shop papers.
 The document type and the shop paper can be selected generically.

336
337
Define Printer

You set the parameters for the print control.


The print control allows you to individually define the output devices and print parameters for each
user and shop paper.
Using a table-controlled printer rerouting, you can also define special printers and print parameters
for the individual shop papers, based on the contents of certain fields.

Activities
1. Define a printer and the corresponding print parameters for the individual users and shop
papers. Note that generic entries are possible.
2. Determine whether the printout of individual shop papers should be rerouted based on the
contents of certain objects and fields.
o Define these objects and fields. Use the objects and fields proposed by SAP and activate
them for the printer rerouting, as necessary.

338
o For each active printer rerouting, define the appropriate contents of the controlling fields
and the special print parameters. The entries for the controlling fields can be generic.

339
340
Status Management

This section describes how to use the general status management function for notifications.
For a detailed description of the general status management function, refer to the section
Environment  Central Functions  Status Management.

Status Profile
You define the status management function for the notifications.
Notifications use the general status management function for SAP objects. A brief explanation of
this concept is provided at the end of this text. For a detailed description of the status management
function and related technical information, refer to the chapter "Basic Settings and Environment" in
the section Status Profile.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Notification  Notification Processing.  Status Management.
Transaction Code QCC2

341
Define Status Profiles

You can define selection profiles for notifications. You can use these selection profiles to find the
notifications on the basis of their statuses.
Refer to the chapter Environment, Central Functions, Status Management,  and Selection
Profile for detailed information about selection profiles.

342
343
Activities
1. Determine whether additional user statuses are required for certain notification types.
2. Define the status profiles for the notifications. For each notification type, you can define
appropriate status profiles for the following object types:
o Notification header
o Task
3. Choose the appropriate status profiles for each notification type.

344
Define Costing Parameters
345
You define a number of parameters for the order type that the system uses to create a QM order.

1. First read the instructions in the section Environment  Central Functions  QM Order Types.
Make sure the required order types are available and the settings for the costing parameters have
been made.
2. For each notification type and plant, assign the following parameters:
a) Order type for the QM order
(The system only proposes order types from order category 06.)
b) Business area (if required)
c) Settlement rule proposal for the QM order
You can select the following objects for the settlement rule:
o Order number (for example, CO order)
o Cost center
o Sales order
Check the settlement of the nonconformity costs by processing a quality notification and recording
costs for the notification.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Notification  Notification Processing. Define Costing Parameters.
Transaction Code QCC2

346
Activities
1. First read the instructions in the section Environment  Central Functions  QM Order Types.
Make sure the required order types are available and the settings for the costing parameters have
been made.
2. For each notification type and plant, assign the following parameters:
o Order type for the QM order
(The system only proposes order types from order category 06.)
o Business area (if required)
o Settlement rule proposal for the QM order
You can select the following objects for the settlement rule:
 Order number (for example, CO order)
 Cost center
 Sales order
1. Check the settlement of the nonconformity costs by processing a quality notification and
recording costs for the notification.

Costing Parameters for QM Orders

347
348
Account Assignment for QM Orders
349
350
The following QM order parameters are defined:
 Quality notification type*
 Plant number*
 Order type (QN01 for nonconformity costs)
 Business area (optional)
 Account assignment (cost object for debiting the costs; for example, cost center, sales
order)
The parameters marked with an asterisk above must be maintained in Customizing for Notification
Processing. If the remaining parameters are not defined in Customizing, you can enter them in a
dialog box when you create a QM order for a quality notification.

Create Special Settlement Rule for QM Order


You set this indicator, if you want to maintain details of the settlement rule in a dialog box, when
you create a QM order.

351
Defects Recording

You make the necessary preparations to use the defects recording function.
You can use the defects recording function to document the following defect criteria:
 Defect type
 Defect location
 Defect cause
 Activity
 Defect valuation

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Notification  Defect Recording.
Transaction Code QCC2

352
353
Define Defect Valuation for Catalog Profile

Defect Valuation
You can valuate the recorded defects quantitatively by assigning a unit of measure (unit for defect
valuation) to the catalog profile. You can specify the number of decimal places to be maintained for
this unit of measure. You can define a separate defect valuation unit for each existing catalog
profile.

Quantitative Defect Valuation


Quantitative weighting of a defect.
You define the criterion for the defect valuation within your own organization.
For example, you can valuate and give a weighting to the defects quantitatively on the basis of
damage potential or nonconformity costs.

354
Define Notification Type for Inspection Type

355
Activities
1. Check the notification types that will be used for defects recording.
o Identify the notification types that will be used for defects recording
o Check the catalogs and catalog profiles as well as their assignment to the notification type.
o Check the screen settings for these notification types.
2. If you want to use a defect valuation, you can assign units of measurement to the appropriate
catalog profiles.
3. Assign an appropriate notification type to all inspection types with which you intend to record
defects.

356
Define Confirmation Profile

You define confirmation profiles for defects recording.


In the confirmation profile, you specify which fields are to appear on the screens when you record
defects and whether the user must enter data in these fields. The confirmation profile essentially
mirrors the various recording forms used by the inspectors in the work centers.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Notification  Defect Recording  Define Confirmation Profile.
Transaction Code QCC2

Activities
1. Determine which report categories are required in your company and what information should
be contained in the defect records that will be created on the basis of these report categories.
(The fields in the confirmation profile must be compatible with the catalog profile).
2. Define the corresponding confirmation profiles.

357
358
Recommendation
Define the confirmation profiles after you have defined the report categories. It may be advisable
to define a separate confirmation profile for each report category.

Required Entry
In the confirmation profile for defects recording, you can control how the individual objects are
confirmed. You define the control for each object, by setting one of the following three indicators:
 optional entry
 required entry
 no entry
Dependencies
For example, if the 'Cause' is defined as a required entry in the confirmation profile, the system
requires you to enter a cause when you confirm a defect item.
When defect records are created automatically on a subsystem, the required entry is ignored.
No Serial Numbers Active
If you set this indicator, the serial number maintenance function for defects recording for the
confirmation profile is not active.
You can thus deactivate the function for assigning a defect to a serial number for those report
categories in which the confirmation profile is used.

359
Define Report Type

You define the report types for defects recording.


In the report type, you link a to a catalog profile. In doing this, you define the content of the
defect report in terms of format and range of available values.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Notification  Defect Recording  Define Report Type.
Transaction Code QCC2

360
Define Defect Report Type

361
Check quality
notification type.

Copy Catalog Profile from Quality Notification Type.


If the indicator is set, the catalog profile will be copied from the quality notification type when the program is
run.
Copy Catalog Profile from Material Master.
If the indicator is set, the catalog profile is copied from the material master when the program is run.
If a maintenance notification is created at defects recording, this indicator is not evaluated.

Dependencies
If the indicator for the catalog profile is also set in the quality notification type (QN Type) and the
system does not find an entry for the catalog profile in the material master, the system copies the
catalog profile from the quality notification type.

If none of the indicators are set, the system uses the catalog profile that is assigned to the report
type.

362
Automatic determination of report category

When you are recording defects, the system searches for the appropriate report category in the
following manner and sequence:
1. Report category for the work center
You can assign a report category to one or more work centers. When you specify the work
center, you can make generic entries. When you record defects for an operation or
characteristic, the system automatically selects the most suitable report category.
2. Report category for the user
If the system cannot automatically find the report category when the user is ready to record
defects, he must specify a report category. To simply the procedure, you can store the
report category in a user master. Use the user parameter 'QFE' for this purpose and assign
the appropriate report category to it as a value.

363
Subsystem Indicator
If you set this indicator for a combination of work center and report category, the system uses this report
category to automatically create defect records, if a subsystem is linked to the work center for purposes of
valuating the characteristics.

364
Information System

You define:
 The update of information from quality notifications to the QM information system
 The creation of key figures relating to the frequency of quality notifications
The data is displayed when processing quality notifications and can come from:
 Original documents
 The QM information system

Define Update in QM Information System

You define the function for updating the quality notifications in the QM Information System by
defining an appropriate update group for each quality notification type.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Notification  Define update in QM Information System.
Transaction Code QCC2

365
Activate Reference to Related Notifications

You specify for each notification whether a reference should be made to existing Q-notifications for
the same material, customer, vendor and manufacturer and if so, how this is to be done.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Notification .Activate Reference to Related Notification.
Transaction Code QCC2

Activities
Decide whether you require key figures to be displayed for the frequency of the notification when
the notifications are processed. If necessary, maintain suitable criteria for data compression, the
data source, and the screen display control for each notification type.

Number of Days
The system takes all quality notifications into consideration that were created in this time period. If
you do not specify a time period, the system automatically selects the last 60 days.

366
Define Nonconformity Costs for Vendor Evaluation

You define an estimated amount for any work performed that relates to the nonconformity of goods
(nonconformity costs, costs incurred as a consequence of defects), as a result of a quality
notification.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Quality Notification  Define Nonconformity Cost for Vendor Evaluation.
Transaction Code QCC2

367
Process Return Delivery to Vendor

You make the settings required to process returns that arise from complaints against a vendor.
Several partial processes for returns are triggered from a quality notification. These include:
 Stock transfer postings
 Quality inspections
 Return deliveries
 Debits or credit memo requests
At the goods receipt inspection or at the subsequent storage and processing of goods, defects can
be identified that can be traced back to the vendor or manufacturer. As a first step, you create a
quality notification that documents the problem and forms the basis for the appropriate corrective
tasks. To prevent the damaged goods from being used, the department responsible can post the
stock available in the warehouse from unrestricted-use stock to blocked stock or to inspection
stock. (Stock types)
Note: If the Warehouse Management (WM) component is installed and the inspection lot (or goods
receipt document in the case of a skip), can be determined, the system uses this data to find all
the individual quantities and goods movements and helps you to collect all defective quantities in
one storage location.
You have several options for further processing. If necessary, the partial quantity that can still be
used can be sorted and the defective partial quantity sent for rework or scrapped. The defective
quantity can also be returned to the vendor with a request for a replacement quantity.
If you decide to return the goods, you can do so either with or without reference to the original
purchase order or goods receipt. If you reference the original document, the system reduces the
delivered quantity contained in the original purchase order. If you do not use a reference, the
system creates a separate return delivery purchase order, which then forms the basis for the actual
return delivery.
In both scenarios a delivery is created, the accompanying papers (such as delivery note, complaint
against a vendor with defect data, 8D report) are printed, the goods issue is posted and the vendor
is sent an invoice. The return delivery purchase order and credit memo request or debit display
reference the quality notification from which they were triggered. You can trace the document flow
in the notification.

368
Process Customer Repair Order

You make the required settings to process returns and repairs of materials that have to be
processed as a result of customer repair orders.
The following procedures are taken into account:
 Basic procedure: Repair order and service order
This procedure forms the basis for the following complementary variants:
 Variant 1: With quality notification (or service notification)
 Variant 2: With quality notification (or service notification) and quality inspection
 Variant 3: With quality inspection
The text for this step deals with the basic procedure and the individual variants separately.

Recommendation
Use the recommendation for implementing the IMG (hypertext link to the IMG structure in place of
displaying the IMG text in the SAPscript editor using the display function).

Repair Order and Service Order


Requirements
The starting point for processing is a repair order from the customer. The repair order is an SD
sales document which references a serviceable material and, depending on the order type, a
service product.
A service order is generated from the customer order. The order type for this must fulfill the
following criteria:
 It must be marked as a service order.
 It must be marked for refurbishment processing
 It must not be marked as revenue-relevant

Vendor Evaluation

The vendor evaluation belongs primarily to the purchasing area. Its functions and the relevant
Customizing can therefore be found in the SAP purchasing component.
The QM component contributes to the calculation of the criterion "Quality".
Quality as a Criterion in the Vendor Evaluation
The main criterion quality contains the automatically valuated sub criteria - goods receipt, audit
and complaints.
Goods Receipt (GR)
The goods receipt score is calculated from the quality score (QSc) for the inspection lots, according
to the following formula:
QSc = (S1 + S2) / (n1 + n2)
S1 = Sum of quality scores for the inspection lots
n1 = Number of inspection lots
n2 = Number of deliveries for materials with a quality information record, for which no inspection
lots exist.
S2 = n2 * QScmax
you can break down the GR score for the vendor according to the material and the inspection type.
Audit:
The audit score is either the average quality score for the audits or is made up of the quality scores
for the most recent audits. You can also enter an audit score manually.

369
Complaints:
The complaints score is calculated from the number of complaints against the vendor, according to
the following formula:
QSc = QScmin + (QScmax - QScmin) * (1 - (N * K) / (F * U))
QSc = QScmin if  (N * K) > (F * U)

Activities
Refer to the following sections of the IMG for the required Customizing work steps:
Materials Management/Purchasing
 Vendor Evaluation
o Weighting Key
o Criteria
o Purchasing Organization Data
 Quality Management/Basic Settings/ Settings at Client Level/
Quality Score Areas
 Quality Management/Quality Inspection/Inspection Lot Completion/
Quality Score Procedure
 Quality Management/Quality Inspection/Inspection Lot Creation/
Inspection Lot Origin 07
Vendor Audit
 Quality Management/Quality Notification/Information System /
Nonconformity Costs

370
7.0 Environment

Environment
In the section 'Environment' of the QM Implementation Guide:
 You make central settings that cannot or should not be assigned to any particular section.
 Central Customizing functions are described that are used in several areas of the QM
component.
 You have access to general Customizing tools.

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Environment  Centrals Functions  Maintain QM Order type
Transaction Code QCC0/KOT2

371
Maintain QM Order Types

In this step, you make the settings for the order categories and order types that are used for the
following functions in the QM component:
 Print control for the shop papers relating to the quality inspection
o Sample-drawing instruction
o Inspection instruction

 Recording of quality costs


o Appraisal costs
o Nonconformity costs

372
Requirements

The following order types for printing shop papers must be maintained for order category 50
(inspection lot):
 QM01 Sample-drawing instruction
 QM02 Inspection instruction
The following order types must be maintained for order category 06 (quality costs):
 QL01 Appraisal costs accumulated and settled for several materials or inspection lots
 QL02 Appraisal costs associated with a single inspection lot
 QN01 Nonconformity costs
You must have maintained default values for these order types
You must have imported evaluations (reports) for these order types from the standard client 000
into the current client and generated them in the current client (report group 7K0O for the QM and
PM components).

Standard settings
These requirements have been met in the standard system.

Recommendation
Coordinate your activities with your controlling area and ask their advice with regard to
determining, recording, settling and analysing quality costs.

Activities
1. Determine whether the following order categories and order types have been maintained in the
system:
a) Order category 50 (inspection lot) with order types:
o QM01 Printing the sample-drawing instruction
o QM02 Printing the inspection instruction
b) Order category 06 (quality costs) with the order types:
o QL01 Collective settlement of appraisal costs, (periodic)
o QL02 Individual settlement of appraisal costs
o QN01 Nonconformity costs
2. Determine whether the relevant settings for these order types have been maintained in the
system
a) For each plant, define the costing variants that are used in all default values for order types
relating to quality costs.
b) Define two order types for appraisal costs in the
settings at plant level; one for individual settlement of costs and one for the periodic
collective settlement of costs. (See section Basic Settings and Environment / Settings).
c) For each plant, define the default values for the following order types relating to quality
costs:
o Appraisal costs (in the Quality Inspection / Inspection Lot Processing section).
o Nonconformity costs (in the Quality Notification / Notification Processing section).
d) Check whether suitable order types have been maintained in the Print control for inspection
documents (in the Quality Inspection / Inspection Lot Processing section).
3. Determine whether further order types are necessary, for example:
o To differentiate between appraisals costs depending on inspection lot origin or inspection
type
o To differentiate between nonconformity costs depending on notification type.

373
Maintain the relevant table entries if necessary.

374
375
Organize Archiving

Implementation Guide for R/3 Customizing  Quality Management 


IMG Path:
Environment  Centrals Functions  Organize Archiving
Transaction Code QCC0

Completed notifications are automatically archived and deleted from the database after a specific
time interval has expired. This time interval is set in Customizing for Quality Management
Therefore, make sure all processing steps have been concluded for a notification before you
complete the notification.

376
Activate Workflow - OOCU

Activate Business Functions - SFW5

377

Вам также может понравиться