Professional Documents
Culture Documents
Client – 110
User – EYPP
Password - ******
In this step, you can change several controlling functions, which effect at client level. These controls relate to different
components in the QM component.
IMG Activity Path Quality Management Basic Setting Setting at Plant level
In this step, you can change and supplement several central-controlling functions at plant level:
Results recording
Summary recording for n=1 - Indicator activated
Limit marginal classes - Indicator activated
Additional decimal places - 1
Plausibility factor (%) - 200. 00
Samples: Start value - 1
Phys.-sample. Interval - 1
Recording configuration – Automatic Close
Message Cat. Decimal Places - No message issued
Inventory posting
Storage Location for Reserves: P001
Batch Valuation
Batch Valuation without Material Spec. – Indicator Marked
Screen Output:
3. Quality Planning
In this subsection, you define the Quality Management functions for materials procurement; you make the relevant
settings in Customizing and maintain the required master data.
The QM component provides a number of controls you can use, depending on your requirements. These QM controls
apply in part to a specific:
Explanation:
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).
3.2. Catalogs
Explanation:
You use catalogs to manage, uniformly define, and standardize information (for example, defect types, follow-up
actions, tasks or characteristic attributes) on a client-wide or plant-wide basis. The catalogs can help you to record and
subsequently evaluate qualitative data, and to describe problems.
Quality Management
Quality planning
Basic Data
IMG Activity Path Catalog Define Catalog Types
In this step, you define the terminology catalogs and catalog languages you will need in addition to those contained in
the standard system.
Screen Output:
3.4. Defect Class
Quality Management
Quality planning
Basic Data
IMG Activity Path Catalog Define Defect Classes
In this step, you define the defect classes that are used to valuate the defects qualitatively on the basis of the defect
consequences.
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
In this step, you maintain the catalogs you require for the inspection characteristics. The following catalogs are usually
delivered with the standard system:
For example:
Catalog 1: Characteristic attributes for qualitative characteristics. You must create selected sets at plant level for this catalog
Catalog 1:
Quality Management
Quality planning
Basic Data
IMG Activity Path
Catalog Edit catalog->Selected Sets
Transaction code QS51
Description of IMG Activity Edit Catalog-Selected Sets
Catalog 1:
Similarly for all Code Groups, Selected Sets have been maintained.
Catalog 3:
For Catalog 3, Code Group: UDMU, Following Selected Sets have been maintained:
Similarly for all Code Groups, Selected Sets have been maintained.
3.7. Inspection Characteristics
In this step, 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.
After you have specified in the control key whether or not the indicators will be predefined and whether the
characteristic is quantitative or qualitative, you must define various characteristic attributes. Refer to the F1-
documentation for information about the control indicators contained in the key.
Quality Management
Quality Planning
Basic Data
IMG Activity Path
Inspection Methods
Transaction code SPRO
Description of IMG Activity Inspection Methods
In this section, you maintain the master records for the inspection methods.
The inspection method describes how a characteristic is to be inspected. Inspection methods are defined at the plant
level. They are used either directly in the inspection plans/inspection characteristics or indirectly via the master
inspection characteristics.
Requirements:
If you want to classify the inspection methods, you must have set up the classification system.
Activities:
Refer to the instructions for organizing and maintaining the inspection characteristics and carry out these steps in a
similar fashion for the inspection methods.
3.9. Inspection Planning - Operation
In this step, 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.
Recommendation
Keep the predefined formula parameters
Activities
1. If necessary, determine which formula parameters are needed for a calculated characteristic and check whether
these parameters have already been preset in the table.
2. If a formula parameter does not yet exist, you must first define it and then decide:
a) Whether you can reference a field in the characteristics records, or
b) Whether the value of an input characteristic must be calculated with the help of a function module
3. The characteristic fields you can reference to calculate the values have been predefined comprehensively in the
system. Only in certain exceptions will you need to expand this selection of fields.
Screen Output:
3.10. Task List Usage
Quality Management
Quality planning Inspection
IMG Activity Path
planning GeneralAssign Task list type to Material
Transaction code Types
SPRO
Description of IMG Activity Assignment of Material Types
Screen Output:
4. Quality Planning
4.1. Inspection Lot Creation
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 have 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
Screen Output:
The following Inspection Types have been maintained:
4.2. Inspection Lot Origin
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
In addition, you must define which inspection type variants should exist for each origin. An example of an inspection
type variant is a model inspection with a separate inspection type and associated task list usage.
Sample types for sample management have been defined
Screen Output:
In this step, 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.
All the settings have been retained as per SAP default for the different inspection types. In general the screen below
shows the various indicators that can be maintained as default while maintaining quality management view in material
master.
Screen Output:
4.4. Inspection for Goods Movements
In this step, 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.
If you set this indicator for a movement type, no inspection lots are created for stock postings.
Screen Output:
4.5. Define Inventory posting
In this step you can adapt the inventory postings that are linked to the usage decision.
Standard Settings
Several movement types are delivered with the standard system for transfer posting the stocks managed in the
inspection lot.
Screen Output:
4.6. Result Recording
In this step, you determine which inspection characteristics are displayed for certain transactions (for example, for
results recording and for the usage decision).
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:
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).
The defects recording function is a supplementary feature of the Q-notification. It provides a quick and simple means of
recording the defects that are encountered during quality inspections. Once you have recorded the defect data, you
can process this data further in the form of quality notifications.
You can use the defects recording function to document the following defect criteria:
Defect type
Defect location
Defect cause
Activity
Defect Valuation
Screen Output:
5.2. Notification Processing
Define Priorities
In this step, you define the priorities for the quality notifications.
You can define different priority types and assign a priority type to each quality notification type. For each priority
type, you define:
Which priority (rank) warrants a quality notification
Which start date and finish date (based on the creation date) the notifications should have following four options
are available in QM priority type which are assigned to all QM Notification type.
1 Very High
2 High
3 Medium
4 Low
In this step, you define the response time monitoring functions for the quality notifications. For this purpose, you must
first define response profiles and service profiles. You must then assign the response profiles and service profiles to
the quality notification types.
In the response profile, you define a sequence of standard tasks (based on the priority of the notification) that can be
proposed in the quality notification and which must be carried out within a predefined period of time
In this step, 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.
You can control the structure of the action box in the following way:
To call the function, you can define an icon with descriptive quick info in addition to the identifier.
You use the sort number to define the order of the functions as they appear in the action box.
In addition to the notification type, you can enter a scenario. If you do this, the function only appears in the
action box if this scenario is assigned to the notification.
You define the transactions in which the function is to appear in the action box by choosing an activity type.
The usage defines whether the function is available at notification level or at task level.
You can control the execution of the function in the following way:
You can document the processing of the function using a task or activity.
Note: When you display the notification, the system only offers the functions that were defined with attribute
"No documentation". The assigned function module cannot make any changes to the notification.
You can enter a user-defined function module for each function. This module is processed when the function is
called. You can also program a dialog box to be used with this function module.
If you link a business operation to the function, it will only be triggered if the status of the operation in the
quality notification allows this.
(The system checks the user authorization for this operation.)
If the function is generated for a task, there are two statuses for this task, either released or completed.
Additionally, you can define a workflow task that is activated when the notification is saved. You can also enter
a function module that changes the workflow container when the notification is saved.
For each function, you can also define several dependent functions (dependent follow-up functions). These dependent
follow-up functions can be triggered from the action box, after the higher-level function has been executed. In this way
you can ensure the adherence to certain sequences during processing.
5.3. Defect Recording
In this section, you make the necessary preparations to use the defects recording function.
From a technical standpoint, the defects recording function provides a quick means of recording quality notification
items using entry lists; the recorded defects can be processed in the form of quality notifications.
A quality notification that is created while recording defects for an inspection lot receives the status 'Defect record';
when you make the usage decision for the inspection lot, it automatically receives the status 'Completed.' You can
delete the status 'Defect record' and still process the notification once the usage decision has been made, provided you
carry out one of the following steps:
Select the function 'Activate quality notification' while processing the inspection lot
Change the notification using a processing function
For this reason, you must first define the quality notification types that are suitable for defects recording. Defects are
confirmed during inspections and recorded for specific inspection lots. You must therefore assign a suitable quality
notification type to each inspection type for which defects are to be recorded.