711
PLM412 Quality Planning and Inspection mySAP ERP Coporate Services Date Training Center Instructors Education Website Participant Handbook Course Version: 2006 Q2 Course Duration: 5 Day(s) Material Number: 50079954 An SAP course - use it to learn, reference it for work

Plm412 en Col62 Fv Part a4

  • Upload
    mjel

  • View
    1.881

  • Download
    121

Embed Size (px)

Citation preview

Page 1: Plm412 en Col62 Fv Part a4

PLM412Quality Planning and Inspection

mySAP ERP Coporate Services

Date

Training Center

Instructors

Education Website

Participant HandbookCourse Version: 2006 Q2Course Duration: 5 Day(s)Material Number: 50079954

An SAP course - use it to learn, reference it for work

Page 2: Plm412 en Col62 Fv Part a4

Copyright

Copyright © 2006 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may be changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Trademarks

� Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® areregistered trademarks of Microsoft Corporation.

� IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®,S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.

� ORACLE® is a registered trademark of ORACLE Corporation.� INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered

trademarks of Informix Software Incorporated.� UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.� Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®,

VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarksof Citrix Systems, Inc.

� HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, WorldWide Web Consortium, Massachusetts Institute of Technology.

� JAVA® is a registered trademark of Sun Microsystems, Inc.� JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for

technology invented and implemented by Netscape.� SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP

EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.comare trademarks or registered trademarks of SAP AG in Germany and in several other countriesall over the world. All other products mentioned are trademarks or registered trademarks oftheir respective companies.

Disclaimer

THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLYDISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDINGWITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE,INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTSCONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT,INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANYKIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOSTPROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDEDSOFTWARE COMPONENTS.

g200611290852

Page 3: Plm412 en Col62 Fv Part a4

About This HandbookThis handbook is intended to complement the instructor-led presentation of thiscourse, and serve as a source of reference. It is not suitable for self-study.

Typographic ConventionsAmerican English is the standard used in this handbook. The followingtypographic conventions are also used.

Type Style Description

Example text Words or characters that appear on the screen. Theseinclude field names, screen titles, pushbuttons as wellas menu names, paths, and options.

Also used for cross-references to other documentationboth internal (in this documentation) and external (inother locations, such as SAPNet).

Example text Emphasized words or phrases in body text, titles ofgraphics, and tables

EXAMPLE TEXT Names of elements in the system. These includereport names, program names, transaction codes, tablenames, and individual key words of a programminglanguage, when surrounded by body text, for exampleSELECT and INCLUDE.

Example text Screen output. This includes file and directory namesand their paths, messages, names of variables andparameters, and passages of the source text of aprogram.

Example text Exact user entry. These are words and characters thatyou enter in the system exactly as they appear in thedocumentation.

<Example text> Variable user entry. Pointed brackets indicate that youreplace these words and characters with appropriateentries.

2006/Q2 © 2006 SAP AG. All rights reserved. iii

Page 4: Plm412 en Col62 Fv Part a4

About This Handbook PLM412

Icons in Body TextThe following icons are used in this handbook.

Icon Meaning

For more information, tips, or background

Note or further explanation of previous point

Exception or caution

Procedures

Indicates that the item is displayed in the instructor'spresentation.

iv © 2006 SAP AG. All rights reserved. 2006/Q2

Page 5: Plm412 en Col62 Fv Part a4

ContentsCourse Overview ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Course Goals .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixCourse Objectives ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Unit 1: QM Processes in the Logistics Processes ... ... . . . . . . . . . . . 1Positioning of Quality Management .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2Inspection Process Flow in Quality Management - Overview... . .7Problem Processing with Quality Notifications - Overview .... . . 17

Unit 2: Basic Data in Quality Management..... . . . . . . . . . . . . . . . . . . . . 27Material Master and Inspection Settings... . . . . . . . . . . . . . . . . . . . . . . . . 29Sample Determination.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Dynamic Modification... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Inspection Setup - Mass Maintenance .. . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Master inspection characteristic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Input Processing for Measured Values.. . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Code Groups and Codes .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102Selected sets and catalog profile . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Inspection method ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126Distributing QM Basic Data .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132Material Specification... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136

Unit 3: Inspection Planning..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161The Inspection Plan .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163Test Equipment.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171Inspection Characteristics in the Inspection Plan.. . . . . . . . . . . . . . .183Reference Operation Set and Product Structure .. . . . . . . . . . . . . . .202Engineering Workbench... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220Engineering change management.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233Task List - Material Specification.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .238Flexible Inspection Specifications .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242Multiple Specifications - Overview .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248

Unit 4: Results Recording ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271Recording and Valuating Inspection Results . .. . . . . . . . . . . . . . . . . . .272

Unit 5: Defects Recording ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315Defects Recording in Inspection Processing ... . . . . . . . . . . . . . . . . . .316

2006/Q2 © 2006 SAP AG. All rights reserved. v

Page 6: Plm412 en Col62 Fv Part a4

Contents PLM412

Unit 6: Usage Decision ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335Inspection Completion with the Usage Decision.. . . . . . . . . . . . . . . .336

Unit 7: Definition and Structure of Notifications ..... . . . . . . . . . . . 357Definition and Structure of Notifications... . . . . . . . . . . . . . . . . . . . . . . . .358

Unit 8: Quality Notifications in Logistics..... . . . . . . . . . . . . . . . . . . . . . 375Quality Notifications at Goods Receipt .. . . . . . . . . . . . . . . . . . . . . . . . . . .376Quality Inspection and Defect Notification at Goods Receipt . .389Customer Complaints .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .403

Unit 9: Quality Notifications in Production ..... . . . . . . . . . . . . . . . . . . 423Quality Notification During Production .. . . . . . . . . . . . . . . . . . . . . . . . . . .424Quality Inspections and Defect Notifications DuringProduction... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .436

Unit 10: General Functions of Quality Notifications ..... . . . . . . . 455Customizing Settings for Notifications... . . . . . . . . . . . . . . . . . . . . . . . . . .456Status Management for Notifications.. . . . . . . . . . . . . . . . . . . . . . . . . . . . .484Other General Functions for Notifications ... . . . . . . . . . . . . . . . . . . . . .495

Unit 11: Quality-related Costs and QM Orders ..... . . . . . . . . . . . . . . 515QM order ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .516

Unit 12: SAP Business Workflow in QM - Overview ..... . . . . . . . 543SAP Business Workflow in QM - Overview... . . . . . . . . . . . . . . . . . . . .544

Unit 13: Evaluations..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557Evaluations Based on Original Documents.. . . . . . . . . . . . . . . . . . . . . .558Standard analyses ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .577

Unit 14: Enterprise Portals � Optional Unit .... . . . . . . . . . . . . . . . . . . . 603Motivation for Portals ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .604SAP's Product Strategy .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .610SAP NetWeaver... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .615Introducing SAP NetWeaver Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .625

vi © 2006 SAP AG. All rights reserved. 2006/Q2

Page 7: Plm412 en Col62 Fv Part a4

PLM412 Contents

Appendix 1: Vendor Evaluation ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633

Appendix 2: Technical Details .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639

Appendix 3: Business Case ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655

Appendix 4: Additional Information ..... . . . . . . . . . . . . . . . . . . . . . . . . 657

Glossary..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695

Index ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697

2006/Q2 © 2006 SAP AG. All rights reserved. vii

Page 8: Plm412 en Col62 Fv Part a4

Contents PLM412

viii © 2006 SAP AG. All rights reserved. 2006/Q2

Page 9: Plm412 en Col62 Fv Part a4

Course OverviewThis course covers the processing of QM-specific basic data and provides detailsabout inspection planning and how to carry out an inspection. You will learn howbasic data is used in different task lists and see the effect of the basic data onthe inspection process.

In addition, this course describes the possible uses of quality notifications and thedifferent evaluation and reporting possibilities in quality management.

The SAP Quality Management applications are part of the mySAP ERP (EnterpriseResource Planning) and mySAP PLM (Product Lifecycle Management) solutions.

The information in this course refers to the SAP ERP Central Component 6.0software component.

Target AudienceThis course is intended for the following audiences:

� Members of the project team� People in the department

Course PrerequisitesRequired Knowledge

� Basic knowledge of quality management� PLM400 (Quality Management)

Course GoalsThis course will prepare you to:

� Find out about the structure and usage of basic data in Quality Management.� Describe the process of an inspection.� Understand the structure, design, and possible uses of quality notifications.� Use evaluations in Quality Management.

Course ObjectivesAfter completing this course, you will be able to:

� Use the QM master data to plan and carry out inspections� Use quality notifications in logistics processes.

2006/Q2 © 2006 SAP AG. All rights reserved. ix

Page 10: Plm412 en Col62 Fv Part a4

Course Overview PLM412

� Use the different evaluation possibilities in Quality Management.

SAP Software Component InformationThe information in this course pertains to the following SAP Software Componentsand releases:

� ECC

x © 2006 SAP AG. All rights reserved. 2006/Q2

Page 11: Plm412 en Col62 Fv Part a4

Unit 1QM Processes in the Logistics

Processes

Unit OverviewThis chapter deals with the general positioning of Quality Management. Thegeneral QM processes in the logistics processes are considered using simpleexamples. The important objects inspection lot and quality notification areconsidered.

Unit ObjectivesAfter completing this unit, you will be able to:

� Describe the integration of QM in the logistical processes.� Explain the most important areas of QM.� Outline the different factors in the logistics supply chain that trigger

inspection lot creation� Identify the key steps for processing an inspection lot� Describe the possible uses of quality notification� Describe problem processing.� Use a customer complaint to illustrate what a quality notification describes,

on what data this quality notification is based, and what options are providedby the link to the Workflow.

Unit ContentsLesson: Positioning of Quality Management ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2Lesson: Inspection Process Flow in Quality Management - Overview ... . .7

Exercise 1: Inspection Lot - Overview .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Lesson: Problem Processing with Quality Notifications - Overview... . . . . 17

2006/Q2 © 2006 SAP AG. All rights reserved. 1

Page 12: Plm412 en Col62 Fv Part a4

Unit 1: QM Processes in the Logistics Processes PLM412

Lesson: Positioning of Quality Management

Lesson OverviewThis lesson deals with the general positioning of Quality Management in theprocesses of a company.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Describe the integration of QM in the logistical processes.� Explain the most important areas of QM.

Business Example� Industrial companies use quality inspections of products at various stages in

the logistics supply chain.� They need to maintain inspection specifications to record inspection results

and they can perform evaluations using this data.

Positioning of QM

Figure 1: Positioning of Quality Management

Quality planningMaster data for inspection planning, material specifications

Quality inspectionInspection lots, inspection results, and defects recordingUsage decisions and follow-up actions

2 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 13: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Positioning of Quality Management

Quality certificateCertificate receipt, certificate issue, certificate transfer

Quality notificationsInternal/external problem solving

Quality controlSPC and control chartsQM information system, key figures

Test equipment managementTest equipment monitoring

Stability studyStability study planning and execution

QM Processes in the Logistics Supply Chain

Figure 2: QM Processes in the Logistics Supply Chain

QM processes can be triggered by different events.

Standard processes (for example, inspections during production, goods receiptinspections) are planned in advance and are triggered regularly.

Event-controlled processes occur spontaneously (such as defects in production,damaged goods at goods receipt). The problems that arise can be recorded andprocessed in a quality notification.

In addition, you can monitor critical values using the information system andif necessary, trigger tasks via the Workflow. The data collected in planned andevent-controlled processes (such as, the number of complaints) is evaluated inthe information system.

2006/Q2 © 2006 SAP AG. All rights reserved. 3

Page 14: Plm412 en Col62 Fv Part a4

Unit 1: QM Processes in the Logistics Processes PLM412

Figure 3: Planned Processes

An inspection can be triggered at different stages in the logistics supply chain.This leads to the creation of an inspection lot.

Triggers can include:

� Goods movements (goods receipt, stock transfer, goods issue)� Orders (production orders, maintenance orders, delivery)� Deadline monitoring (batch monitoring)� Source inspections

The inspection lot forms the basis for inspection processing. It contains allthe data for the inspection (such as material, order, inspection specifications,inspection lot size, quantity to be inspected or, if required, QM order).

You record inspection results for this inspection lot.

The usage decision specifies whether the goods are accepted or rejected, based onthe results of the inspection.

4 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 15: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Positioning of Quality Management

Figure 4: Event-Controlled Processes

In addition to the standard processes, there are event-controlled processes in thelogistics supply chain, which are triggered when problems occur.

You record, analyze, and document these problems in quality notifications andforward them to the departments responsible for further processing.

You can define follow-up actions that help resolve problems quickly.

2006/Q2 © 2006 SAP AG. All rights reserved. 5

Page 16: Plm412 en Col62 Fv Part a4

Unit 1: QM Processes in the Logistics Processes PLM412

Lesson Summary

You should now be able to:� Describe the integration of QM in the logistical processes.� Explain the most important areas of QM.

6 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 17: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection Process Flow in Quality Management - Overview

Lesson: Inspection Process Flow in Quality Management- Overview

Lesson OverviewIn this lesson, you will learn about the inspection process flow and its mostimportant steps. The focus of this process flow is the inspection lot.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Outline the different factors in the logistics supply chain that triggerinspection lot creation

� Identify the key steps for processing an inspection lot

Business ExampleThe inspection lot represents the request to a plant to perform a quality inspectionon a certain quantity of a material.

For example, inspection lots can be created because of goods movements ordeliveries to customers. They can also be created with manufacturing orders andproduction versions to check materials during production.

Inspection lots can contain several operations. An operation defines which activityis to be performed at a work center.

Each operation can contain several inspection characteristics. An inspectioncharacteristic describes what is to be inspected.

2006/Q2 © 2006 SAP AG. All rights reserved. 7

Page 18: Plm412 en Col62 Fv Part a4

Unit 1: QM Processes in the Logistics Processes PLM412

QM Inspection Process

Figure 5: QM Inspection Process

Figure 6: Inspection Lot: General

8 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 19: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection Process Flow in Quality Management - Overview

Different events cause an inspection lot to be created, for example:

� Goods receipt� Production order� Calibration order� Goods movements

You can also manually create an inspection lot.

The inspection lot contains the inspection specifications. The specifications are aprerequisite for the inspection.

Figure 7: QM Inspection Process

An inspection lot is assigned to a material or to a maintenance order.

The first step in the inspection lot life cycle is the sample determination. Thesecond step consists of results or defects recording. The usage decision completesthe inspection lot.

The inspection status is updated in the inspection lot.

All inspection data (results, defects, usage decision) is recorded for the inspectionlot.

Different evaluations can be made based on the inspection lot data record.

2006/Q2 © 2006 SAP AG. All rights reserved. 9

Page 20: Plm412 en Col62 Fv Part a4

Unit 1: QM Processes in the Logistics Processes PLM412

Inspection Lot Data Record

Figure 8: Inspection Lot Data Record

The inspection lot data record contains the data relevant to you for the currentquality inspection. This data includes:

� The specified inspection lot quantity, sample size, and stock-relevant quantity� Information regarding inspection lot creation ( for example, origin, vendor,

order number, purchase order number, delivery number)� Specifications regarding the execution of the inspection (inspection

according to plan, inspection according to material specification)

The shop papers (inspection instructions, sample-drawing procedures) for theexecution of the inspection are created using the specifications from the inspectionlot data record.

10 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 21: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection Process Flow in Quality Management - Overview

Figure 9: Inspection Lot Search

The inspection lot can also be found using a selection profile that you maintain inCustomizing.

An �originating document� is one of the following:

� Purchasing document� Material document� Order� Delivery

2006/Q2 © 2006 SAP AG. All rights reserved. 11

Page 22: Plm412 en Col62 Fv Part a4

Unit 1: QM Processes in the Logistics Processes PLM412

Figure 10: Inspection lot instructions

You can set the automatic printout of the sample-drawing instruction and theinspection instruction with reference to the inspection type in Customizing.

The sample-drawing instruction contains the necessary information for taking thesample quantity or one or more physical samples.

The inspection instruction describes the nature of the inspection and how to carryit out.

You can print these documents for each inspection operation (work center).

12 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 23: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection Process Flow in Quality Management - Overview

Exercise 1: Inspection Lot - Overview

Exercise ObjectivesAfter completing this exercise, you will be able to:� Find an inspection lot data record using the search help.� Display all master data that is relevant for the inspection.

Business ExampleInspection lot data records are normally created automatically in the logisticssupply chain. An inspection lot is created because of a certain event, for example,a goods receipt. Using an inspection lot data record, you will learn about the datarelevant for the quality inspection and the integration of QM in other applicationcomponents.

Task: Display an inspection lotThe inspection lot is the central document in the planned inspection processing.The inspection lot can be created automatically or manually.

1. The goods receipt was posted for a purchase order and an inspection lot wasautomatically created. You want to display the data relevant for inspectionbefore processing the inspection lot further.

Limit the value range when searching for the inspection lot and search forthe inspection lots for material T-BQ1##. �##� is your group number.

Make a note of the following data from the inspection lot:Inspection lot number: _____________________Inspection type: _____________________System status: _____________________Vendor: _____________________Material document: _____________________Inspection lot quantity: _____________________Sample size: _____________________

2006/Q2 © 2006 SAP AG. All rights reserved. 13

Page 24: Plm412 en Col62 Fv Part a4

Unit 1: QM Processes in the Logistics Processes PLM412

Solution 1: Inspection Lot - OverviewTask: Display an inspection lotThe inspection lot is the central document in the planned inspection processing.The inspection lot can be created automatically or manually.

1. The goods receipt was posted for a purchase order and an inspection lot wasautomatically created. You want to display the data relevant for inspectionbefore processing the inspection lot further.

Limit the value range when searching for the inspection lot and search forthe inspection lots for material T-BQ1##. �##� is your group number.

Make a note of the following data from the inspection lot:Inspection lot number: _____________________Inspection type: _____________________System status: _____________________Vendor: _____________________

Continued on next page

14 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 25: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection Process Flow in Quality Management - Overview

Material document: _____________________Inspection lot quantity: _____________________Sample size: _____________________

a) Logistics→ Quality Management→ Quality Inspection→ InspectionLot→ Processing→ Display (QA03)

For inspection lot selection, enter material T-BQ1## on the Materialtab page of the F4 help, and choose Continue. All inspection lots thatcorrespond to the selection criteria are displayed in the list. Transferthe inspection lot number by double-clicking it. Choose Enter. TheDisplay Inspection Lot screen appears. You can see the followingvalues on this screen:

Field name or data type ValuesInspection lot number: ........Inspection type: 01System status: REL CALC SPRQ QLCHVendor: 1000Material document: ........

Insp. lot quantitiesInspection lot quantity: 1000 PCSample size: 1000 PC

2006/Q2 © 2006 SAP AG. All rights reserved. 15

Page 26: Plm412 en Col62 Fv Part a4

Unit 1: QM Processes in the Logistics Processes PLM412

Lesson Summary

You should now be able to:� Outline the different factors in the logistics supply chain that trigger

inspection lot creation� Identify the key steps for processing an inspection lot

16 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 27: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Problem Processing with Quality Notifications - Overview

Lesson: Problem Processing with Quality Notifications- Overview

Lesson OverviewIn this lesson you will get a general overview of problem processing using qualitynotifications.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Describe the possible uses of quality notification� Describe problem processing.� Use a customer complaint to illustrate what a quality notification describes,

on what data this quality notification is based, and what options are providedby the link to the Workflow.

Business ExampleThe procedure for processing problems plays an important part in the businessprocesses of a company. It is important to process different types of problemsefficiently.

Problems that occur can be caused by external or internal events.

Examples of these events are:

� Customer complaint� Complaint against a vendor� Internal company problems (for example, defective materials in production)

2006/Q2 © 2006 SAP AG. All rights reserved. 17

Page 28: Plm412 en Col62 Fv Part a4

Unit 1: QM Processes in the Logistics Processes PLM412

Uses of quality notifications

Figure 11: Uses of quality notifications

There are many uses for quality notifications.

Different business processes can be separated if you use various types of qualitynotifications.

Figure 12: Continuous Process Improvement

18 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 29: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Problem Processing with Quality Notifications - Overview

The quality notification system:

� Enables a problem to be solved more efficiently, especially if more than oneperson in the company is involved in solving it.

� Supports continuous improvement of quality by checking the effectivenessof any solutions that are identified.

Procedure for problem solving

Figure 13: Procedure for Problem Processing

There are two ways of processing a quality notification:

� You can use the immediate tasks and activities that provide short-term helpuntil an exact diagnosis is made.

� You can use the defect analysis that involves the investigation of thecause, and the introduction of the necessary corrective tasks and activities(long-term).

2006/Q2 © 2006 SAP AG. All rights reserved. 19

Page 30: Plm412 en Col62 Fv Part a4

Unit 1: QM Processes in the Logistics Processes PLM412

Figure 14: Case Study: Customer Complaint

� A customer complaint can be recorded in the following ways:

� You create a notification with reference to an SD document (salesorder, delivery) for example. In this instance, additional informationsuch as material number and customer is transferred directly to thequality notification.

� You enter a general description of the problem and save the notification.� The �quality assurance� department is notified using the SAP Business

Workflow.

20 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 31: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Problem Processing with Quality Notifications - Overview

Lesson Summary

You should now be able to:� Describe the possible uses of quality notification� Describe problem processing.� Use a customer complaint to illustrate what a quality notification describes,

on what data this quality notification is based, and what options are providedby the link to the Workflow.

2006/Q2 © 2006 SAP AG. All rights reserved. 21

Page 32: Plm412 en Col62 Fv Part a4

Unit Summary PLM412

Unit SummaryYou should now be able to:� Describe the integration of QM in the logistical processes.� Explain the most important areas of QM.� Outline the different factors in the logistics supply chain that trigger

inspection lot creation� Identify the key steps for processing an inspection lot� Describe the possible uses of quality notification� Describe problem processing.� Use a customer complaint to illustrate what a quality notification describes,

on what data this quality notification is based, and what options are providedby the link to the Workflow.

22 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 33: Plm412 en Col62 Fv Part a4

PLM412 Test Your Knowledge

Test Your Knowledge

1. When implementing QM, only the business processes in a company mustbe examined.Determine whether this statement is true or false.□ True□ False

2. Test equipment monitoring is part of test equipment management.Determine whether this statement is true or false.□ True□ False

3. QM is integrated in the processes of the logistics supply chain.Determine whether this statement is true or false.□ True□ False

4. Inspection results recording must always be carried out for each inspectionlot.Determine whether this statement is true or false.□ True□ False

5. Inspection lots can always only be created with reference to a logisticalprocess (for example, goods movement, order release).Determine whether this statement is true or false.□ True□ False

6. Does the inspection lot data record contain the following information?Choose the correct answer(s).□ A Lot size and sample size□ B Vendor or customer□ C Assigned inspection specifications (for example, task list)□ D Material documents that are related to the inspection lot

2006/Q2 © 2006 SAP AG. All rights reserved. 23

Page 34: Plm412 en Col62 Fv Part a4

Test Your Knowledge PLM412

7. The same type of notification is used for all notifications with reference toproduction.Determine whether this statement is true or false.□ True□ False

8. Several defect items can be included in one notification.Determine whether this statement is true or false.□ True□ False

9. The notifications can be used for various processes in the logistical chain.Determine whether this statement is true or false.□ True□ False

24 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 35: Plm412 en Col62 Fv Part a4

PLM412 Test Your Knowledge

Answers

1. When implementing QM, only the business processes in a company mustbe examined.

Answer: False

In addition to the business processes, standards requirements must also betaken into consideration for implementation.

2. Test equipment monitoring is part of test equipment management.

Answer: True

Test equipment management uses functions from Quality Managementand Plant Maintenance. The management of measuring devices is a PlantMaintenance task, calibration inspections are executed using transactionsfrom Quality Management.

3. QM is integrated in the processes of the logistics supply chain.

Answer: True

Due to the integration of QM with the logistics supply chain, inspections canbe triggered automatically.

4. Inspection results recording must always be carried out for each inspectionlot.

Answer: False

Depending on the setting in the inspection type, results recording and/ordefects recording can take place for an inspection lot. You can also workwith defects recording only.

5. Inspection lots can always only be created with reference to a logisticalprocess (for example, goods movement, order release).

Answer: False

You can also create manual inspection lots for particular inspection lotorigins, if required. In addition, you can use inspection lot origin 89 formanual inspection lots.

2006/Q2 © 2006 SAP AG. All rights reserved. 25

Page 36: Plm412 en Col62 Fv Part a4

Test Your Knowledge PLM412

6. Does the inspection lot data record contain the following information?

Answer: A, B, C, D

You can display relevant reference documents for an inspection lot, data frominspection planning, and inspection results via the inspection lot data record.

7. The same type of notification is used for all notifications with reference toproduction.

Answer: False

Depending on the application, different notification types can be used forinternal problem notifications. You can define your own notification types inCustomizing and assign the notification origin.

8. Several defect items can be included in one notification.

Answer: True

You can include several defect items in each notification. For each defectitem, defect causes, tasks, and activities can be created.

9. The notifications can be used for various processes in the logistical chain.

Answer: True

Through their integration in the processes of the logistical chain, thenotifications can be used, for example, for procurement operations, in goodsreceipt and goods withdrawal, or in production.

26 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 37: Plm412 en Col62 Fv Part a4

Unit 2Basic Data in Quality Management

Unit OverviewQM-specific master data is required in inspection planning so that thecorresponding information can be stored in the system. This unit gives you adetailed introduction to the basic data that is available. At the end of the unit,material-dependent inspection requirements are created in the system using thisbasic data. Material-dependent inspection requirements form the basis for therest of the inspection process.

Unit ObjectivesAfter completing this unit, you will be able to:

� Describe the inspection settings in the material master.� Explain Customizing for the inspection settings.� Explain the master data for sample determination.� Describe the tasks of the sampling procedure.� Describe the structure of the modification rule.� Explain how to use dynamic modification.� Describe the mass maintenance options for the inspection setup.� Use mass maintenance for an inspection setup that is already active.� Describe the structure of master inspection characteristics.� Explain the options for using master inspection characteristics.� Explain the functions of input processing for measured values.� Describe how these functions can be used.� Describe the structure of coding.� Describe how the different catalog types can be used.� Describe the structure of a selected set.� Explain how selected sets can be used in inspection planning.� Describe the possible uses of inspection methods.� Explain inspection planning using inspection methods.� Distribute certain QM basic data to other systems.� Describe the different distribution processes.

2006/Q2 © 2006 SAP AG. All rights reserved. 27

Page 38: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

� Explain the structure of the material specification.� Describe the possible uses of the material specification.

Unit ContentsLesson: Material Master and Inspection Settings .. . . . . . . . . . . . . . . . . . . . . . . . . . 29Lesson: Sample Determination .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Exercise 2: Sample Determination .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Lesson: Dynamic Modification ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Exercise 3: Dynamic Modification Rule.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Lesson: Inspection Setup - Mass Maintenance... . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Exercise 4: Inspection Setup - Mass Maintenance .. . . . . . . . . . . . . . . . . . . . 67Lesson: Master inspection characteristic .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Exercise 5: Master Inspection Characteristics.. . . . . . . . . . . . . . . . . . . . . . . . . . 83Lesson: Input Processing for Measured Values .. . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Lesson: Code Groups and Codes .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102

Exercise 6: Catalogs, Code Groups, and Codes.. . . . . . . . . . . . . . . . . . . . . .107Lesson: Selected sets and catalog profile . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112

Exercise 7: Selected Sets and Codes of Selected Sets.. . . . . . . . . . . . . .119Lesson: Inspection method .. .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126Lesson: Distributing QM Basic Data .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132Lesson: Material Specification ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136

Exercise 8: Material Specification ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139

28 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 39: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Material Master and Inspection Settings

Lesson: Material Master and Inspection Settings

Lesson OverviewThe settings in the material master have an important effect on processes inquality management. The fundamental settings that determine if a material mustbe inspected, and for which logistical processes, are stored here.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Describe the inspection settings in the material master.� Explain Customizing for the inspection settings.

Business ExampleAccording to the settings in the material master, automatic inspection lots aregenerated in logistical processes. The inspection settings are defined duringquality planning, in consultation with the relevant departments.

Material Master and Quality Management View

Figure 15: Master Data: Business Scenario

During inspection planning, you access different master data. This acts as modularreusable building blocks when planning quality inspections.

2006/Q2 © 2006 SAP AG. All rights reserved. 29

Page 40: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Figure 16: Material Master: Quality Management View

QM-specific data is maintained at plant level.

You can also maintain General Data in other views (for example, Purchasing).

The procurement data in the Quality Management view affects purchasing.

You use the inspection setup to define if and where the material is to be inspected.

30 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 41: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Material Master and Inspection Settings

Inspection Settings

Figure 17: Inspection Setup

For each inspection type you can also define the following:

� Processing of results recording� Sample determination and dynamic modification� QM order for inspection lot� Quality score calculation

Inspection with task list means:

� You inspect the inspection characteristics that are specified in an inspectionplan, routing, or master recipe.

Insp with spec. means:

� You inspect the inspection characteristics as defined in the materialspecification.

2006/Q2 © 2006 SAP AG. All rights reserved. 31

Page 42: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Inspection by configuration means:

� You can include customer-specific specifications for inspectioncharacteristics in the inspection: Configurations from the customer orproduction order are taken into consideration during inspection lot creationand the specifications from the task list or material specification areadapted accordingly. The prerequisite is that a link exists between the classcharacteristic and the master inspection characteristic.

Figure 18: Customizing for Inspection Lot Origin

You define the relationship between the inspection type and the inspection lotorigin in Customizing. The inspection lot origin is predefined in the system andit determines the origin of the inspection lot. The actual inspection process isdefined using the inspection type. You can create your own inspection types inCustomizing.

You can link several inspection types to each inspection lot origin.

� For example, inspection lot origin 01 (goods receipt) can have the followinginspection types assigned to it:

� 01 Inspection at goods receipt for purchase order� 0101 Receiving inspection for model series� 0102 Receiving inspection for preliminary series� 0130 Receiving inspection for GR from external processing

Default values for the inspection type can be set in Customizing and adapted inthe Inspection Setup for the material.

32 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 43: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Material Master and Inspection Settings

Lesson Summary

You should now be able to:� Describe the inspection settings in the material master.� Explain Customizing for the inspection settings.

2006/Q2 © 2006 SAP AG. All rights reserved. 33

Page 44: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Lesson: Sample Determination

Lesson OverviewSample determination is an obligatory step in the QM inspection process. Inaccordance with standard requirements, there are different options for calculatingthe sample size. These options are described in detail in this lesson.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Explain the master data for sample determination.� Describe the tasks of the sampling procedure.

Business ExampleDifferent specifications for sample determination are required for the differentinspection processes. These are created using sampling procedures and samplingschemes.

Sample Determination

Figure 19: QM Inspection Process: Sample Determination

Sample determination is an obligatory step in inspection lot processing.

Dynamic modification can influence sample determination.

34 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 45: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Sample Determination

Figure 20: Material Master - Sample Determination

In the inspection setup of the QM view of the material master, sampledetermination can be defined in the following ways:

� Manually� Percentage� With reference to a sampling procedure

If a planned inspection has inspection characteristics assigned to it, then theassignment of the sampling procedure takes place at inspection characteristic leveland not in the inspection setup in the QM view of the material master.

2006/Q2 © 2006 SAP AG. All rights reserved. 35

Page 46: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Sampling Procedure

Figure 21: Creating a Sampling Procedure

The sample size is determined using the sampling procedure.

The valuation mode in the sampling procedure determines the valuation of thesample, for example, whether it is attributive, variable, manual.

You can plan checks with inspection points along with task lists (for example,inspection plan, routing,master recipe). You can only use sampling procedures forwhich the �Freely-defined inspection points� indicator is set.

Depending on the sampling type or the valuation mode, further entries can ormust be made on the special conditions screen (for example, sampling scheme,control chart type, additional data, sample).

Hint: If the indicator �No stage change� is set in the sampling procedure,the characteristic (for characteristic-based dynamic modification) or lot(for lot-based dynamic modification) always stops at the initial stageof the dynamic modification rule.

36 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 47: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Sample Determination

Figure 22: Sampling Procedure

The following sample types can be defined in the sampling procedure:

� Sample percentage� Fixed sample� With reference to a sampling scheme

Figure 23: Summary: Sample Type Valuation Mode

The sampling type and the valuation mode define which parameters are used todetermine the sample.

2006/Q2 © 2006 SAP AG. All rights reserved. 37

Page 48: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

The valuation �Variable inspection s-method� can occur either single-sided ordouble-sided.

Sampling Scheme

Figure 24: Creating a Sampling Scheme

In the sampling scheme, you can define different sampling tables with samplingplans. In the individual sampling tables, you can define corresponding samplingplans for each lot size interval, for example, n-c or n-c/d, n-k.

The sampling scheme is assigned to the corresponding sampling procedure.

The standard system contains complete sampling schemes according to

� DIN ISO 2859-1 for attributive inspection� DIN ISO 3951 for variable inspections

For more information about samples in the SAP System, see Customizing in:Quality Management→ Quality Planning→ Basic Data→ Sample, SPC

38 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 49: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Sample Determination

Figure 25: Example: Determining the Sample Size

If the unit of measurement for the inspection lot does not consist of single units(for example, the unit of measurement liter or kg), then the lot size is determinedby dividing the lot quantity by the sample quantity.

The lot size determined in example 2 is 4000. As a result, the sample size of50 is used. (In the example, this can be used for a lot size greater than 1,000 orsmaller than or equal to 10,000.)

If the maximum possible lot size is exceeded, the sample size for the maximumpossible lot size is used.

2006/Q2 © 2006 SAP AG. All rights reserved. 39

Page 50: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

40 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 51: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Sample Determination

Exercise 2: Sample Determination

Exercise ObjectivesAfter completing this exercise, you will be able to:� Create sampling procedures and sampling schemes.

Business ExampleIn your company, you want to determine the sample quantity that is proposedfor the inspection using a suitable sampling procedure. You need a samplingprocedure with the corresponding valuation mode for the different inspectiontypes (attributive inspection, variable inspection). For certain inspections, youwant to work with a fixed sample or a sample percentage.

Task: Basic data for the sample determinationThe sampling procedure and the sampling schemes are part of the basic data forthe sample determination.

1. Creating a sampling procedure with a fixed sample.

Create a sampling procedure with the description SP01-## and a suitableshort text. Use a fixed sample with the sample size n = 5 and a valuationmode that allows the sample to be created automatically using thenonconforming units.

The sampling procedure is not to be used with inspection points. A stagechange is possible. You do not need a control chart.

Hint: Use the Sample button to define the fixed sample size n andthe acceptance number c.

Hint: Use the acceptance number c = 0 if nonconforming unitslead to a rejection.

2. Create a sampling procedure with a sample percentage - optional exercise

Create another sampling procedure with the description SP02-## and asuitable short text. Use the sample percentage as 5% and a valuation modewithout valuation parameters.

The sampling procedure is not used with inspection points. A stage changeis possible.

3. Create a sampling scheme - optional exercise

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 41

Page 52: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

You want to determine the sample size depending on the inspection lotquantity. To do this, create a sampling scheme with the description S## foran attributive inspection. The first sampling table should be used without theAQL value for the inspections with the inspection severity Normal. Entera sample size of your choice, an acceptance number (c1), and a rejectionnumber (d1) for the following intervals.

Hint: Note that for automatic valuation during a single samplinginspection, the difference between the acceptance and rejectionnumber must be exactly 1.

Lot size (to) Sample size c1 d1100

1 00010 000

Over 10,000

Hint: You should use a very large number, such as 10,000,000,000,as the last entry for the lot size. This is the maximum possible lotsize that you can use.

Create a second sampling table (also without an AQL value) for an inspectionwith the inspection severity Reduced. Enter a sample size of your choice, anacceptance number, and a rejection number for the following intervals.

Lot size (to) Sample size c1 d1100

1 00010 000

Over 10,000

Hint: When you create the second sampling table, set the indicatorWith copy model so that the data from the first sampling table canbe copied. Then, you only have to change the sample size and theacceptance and rejection number.

4. Creating a sampling procedure with a sampling schemeContinued on next page

42 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 53: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Sample Determination

Create another sampling procedure with the description SP03-## for anattributive inspection according to the number of nonconforming units. Usethe sampling scheme 212 or your sampling scheme S##.

The sampling procedure is not to be used with inspection points. A stagechange is possible.

Use the inspection severity Normal inspection and the AQL value 1.0. Thesampling procedure must not be added to the allowed relationships. If youuse the sampling scheme S##, an AQL value is not required.

2006/Q2 © 2006 SAP AG. All rights reserved. 43

Page 54: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Solution 2: Sample DeterminationTask: Basic data for the sample determinationThe sampling procedure and the sampling schemes are part of the basic data forthe sample determination.

1. Creating a sampling procedure with a fixed sample.

Create a sampling procedure with the description SP01-## and a suitableshort text. Use a fixed sample with the sample size n = 5 and a valuationmode that allows the sample to be created automatically using thenonconforming units.

The sampling procedure is not to be used with inspection points. A stagechange is possible. You do not need a control chart.

Hint: Use the Sample button to define the fixed sample size n andthe acceptance number c.

Hint: Use the acceptance number c = 0 if nonconforming unitslead to a rejection.

a) Logistics→ Quality Management→ Quality Planning→ Basic Data→ Sample→ Sampling Procedure→ Create (QDV1)

Enter the description SP01-## in the field Sampling procedure. ##is your group number. By choosing the Return key, the pushbuttonSampling procedure, or Enter, the Assignment screen appears. On thisscreen, you can define the short text for the sampling procedure, as wellas the sampling type and valuation mode.

Field name or data type Valuessampling type Fixed samplevaluation mode Attributive inspection nonconf.

units

By choosing the F5 function key, the pushbutton Continue, or Enter,the Special Conditions screen appears. Since this exercise requires nofurther entries, you can skip directly to the next screen by choosingSample and entering the value 5 in the Sample size field and the value 0in the Acceptance number field.

Save your entries.

Continued on next page

44 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 55: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Sample Determination

2. Create a sampling procedure with a sample percentage - optional exercise

Create another sampling procedure with the description SP02-## and asuitable short text. Use the sample percentage as 5% and a valuation modewithout valuation parameters.

The sampling procedure is not used with inspection points. A stage changeis possible.

a) Logistics→ Quality Management→ Quality Planning→ Basic Data→ Sample→ Sampling Procedure→ Create (QDV1)

Enter the description SP02-## on the initial screen. On the assignmentscreen, enter a suitable short text for the sampling procedure, as well asthe sampling type and valuation mode.

Field name or data type Valuessampling type Sample percentagevaluation mode Without valuation params

By choosing the F5 function key, the pushbutton Continue, or Enter,the Special Conditions screen appears. Since this exercise requiresno further entries, you can skip to the next screen directly using thepushbutton Sample and enter the value 5 in the Sample percentage field.

Save your entries.

3. Create a sampling scheme - optional exercise

You want to determine the sample size depending on the inspection lotquantity. To do this, create a sampling scheme with the description S## foran attributive inspection. The first sampling table should be used without theAQL value for the inspections with the inspection severity Normal. Entera sample size of your choice, an acceptance number (c1), and a rejectionnumber (d1) for the following intervals.

Hint: Note that for automatic valuation during a single samplinginspection, the difference between the acceptance and rejectionnumber must be exactly 1.

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 45

Page 56: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Lot size (to) Sample size c1 d1100

1 00010 000

Over 10,000

Hint: You should use a very large number, such as 10,000,000,000,as the last entry for the lot size. This is the maximum possible lotsize that you can use.

Create a second sampling table (also without an AQL value) for an inspectionwith the inspection severity Reduced. Enter a sample size of your choice, anacceptance number, and a rejection number for the following intervals.

Lot size (to) Sample size c1 d1100

1 00010 000

Over 10,000

Hint: When you create the second sampling table, set the indicatorWith copy model so that the data from the first sampling table canbe copied. Then, you only have to change the sample size and theacceptance and rejection number.

a) Create a sampling scheme: Logistics→ Quality Management→Quality Planning→ Basic Data→ Sample→ Sampling Scheme→Create (QDP1)

On the initial screen, enter the description S## in the Sampling schemefield. ## is your group number. By choosing the Return key, thepushbutton Sampling scheme, or Enter, the Header Data screen appears.On this screen, you can define the short text for the sampling scheme, aswell as the valuation parameters and the assignment of sampling tables.

Continued on next page

46 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 57: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Sample Determination

Field name or data type ValuesValuation parameters Attributive insp.Sampling tables for Insp. severities

By choosing the F5 function key, the pushbutton Continue, or Enter,the dialog box for choosing inspection severities appears. Choose theinspection severity Normal inspection using the input help for your firstsampling table in the field New. Enter sampling plans in the view forcreating the sampling table. For example:

Lot size (to) Sample size c1 d1100 3 0 1

1 000 5 1 210 000 8 2 3

Over 10,000 10 5 6

Create an additional sampling table for the inspection severity Reducedinspection. To do this, choose the pushbutton Other table and selectthe corresponding inspection severity using the input help. If you wantto copy entries from the first table, you must set the indicator Withcopy model. You can now define the sampling plan for the Reducedinspection. For example:

Lot size (to) Sample size c1 d1100 2 0 1

1 000 4 0 1

10 000 6 1 2Over 10,000 8 4 5

Save your entries.

4. Creating a sampling procedure with a sampling scheme

Create another sampling procedure with the description SP03-## for anattributive inspection according to the number of nonconforming units. Usethe sampling scheme 212 or your sampling scheme S##.

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 47

Page 58: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

The sampling procedure is not to be used with inspection points. A stagechange is possible.

Use the inspection severity Normal inspection and the AQL value 1.0. Thesampling procedure must not be added to the allowed relationships. If youuse the sampling scheme S##, an AQL value is not required.

a) Logistics→ Quality Management→ Quality Planning→ Basic Data→ Sample→ Sampling Procedure→ Create (QDV1)

Enter the description SP03-## in the field Sampling procedure. ##is your group number. By choosing the Return key, the pushbuttonSampling procedure, or Enter, the Assignment screen appears. On thisscreen, you can define the short text for the sampling procedure, as wellas the sampling type and valuation mode.

Field name or data type Valuessampling type Use sampling schemevaluation mode Attributive inspection nonconf.

units

By choosing the F5 function key, the pushbutton Continue, or Enter,the Special Conditions screen appears. In the Sampling scheme field,enter the value 212 or the sampling scheme S## that you created intask 3, Create a sampling scheme.

The sampling scheme 212 has different sampling tables for differentinspection severities. If you choose the pushbutton Additional data,the inspection severities are displayed, and you can choose a samplingtable using the input help. Use the sampling tables for the inspectionseverity Normal inspection and the AQL value 1.0.

The sampling scheme S## has 2 sampling tables for different inspectionseverities. If you choose the pushbutton Additional data, the inspectionseverities are displayed, and you can choose a sampling table usingthe input help.

Save your entries.

Hint: Answer the query regarding �allowed relationships�with NO.

48 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 59: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Sample Determination

Lesson Summary

You should now be able to:� Explain the master data for sample determination.� Describe the tasks of the sampling procedure.

2006/Q2 © 2006 SAP AG. All rights reserved. 49

Page 60: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Lesson: Dynamic Modification

Lesson OverviewIn conjunction with sample determination, dynamic modification also plays animportant role. Dynamic modification automatically reduces or increases the sizeof a sample according to the result of a previous inspection. The work involved inan inspection can then be reduced or increased, if required.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Describe the structure of the modification rule.� Explain how to use dynamic modification.

Business ExampleDynamic modification is used so that inspection costs can be reduced as a result ofhigh quality. Dynamic modification should be used to reduce the size of samplesand for inspection skip.

Dynamic Modification Rule

Figure 26: Creating a Dynamic Modification Rule

You should enter all inspection stages before you maintain the stage change.

50 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 61: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Dynamic Modification

When you maintain the stage change, you can specify, in addition to the number ofinspections, a maximum skip duration in days for inspection stages that cause aninspection lot to be skipped.

The system uses the reset period to calculate the reset date in the quality level andautomatically updates it when the quality level is updated or corrected. After thereset period has passed, the quality level returns to the initial inspection stage ofthe dynamic modification rule.

Figure 27: Dynamic Modification Rule

The dynamic modification rule defines the inspection stages and the conditionsfor an inspection stage change.

If you do not use a sampling scheme in a sampling procedure, you should not usethe inspection severities �Tightened�, �Normal�, or �Reduced� in the dynamicmodification rule.

In the dynamic modification history, you can display all inspection lots orinspection characteristics (if dynamic modification by characteristic) and theirrespective inspection stages as a list or graphic, independent of the dynamicmodification level (lot level, characteristic level, inspection type level).

2006/Q2 © 2006 SAP AG. All rights reserved. 51

Page 62: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Figure 28: Dynamic Modification Criteria

The quality level is the current stage of dynamic modification in relation to certaindynamic modification criteria.

You set dynamic modification criteria in Customizing for the inspection lot originor the task list usage. You select from the default dynamic modification criteriain the task list header.

Example:

� The dynamic modification criteria material, vendor, and manufacturer areused for goods receipt inspections. A quality level is updated at each goodsreceipt inspection with reference to these dynamic modification criteria.However, if the field Manufacturer has no entry in the inspection lot forexample,the system only updates the quality level for the material and vendor.

52 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 63: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Dynamic Modification

General Sample Determination

Figure 29: Allowed Relationships

The allowed relationships contain combinations of dynamic modification rules andsampling procedures with reference to a sampling scheme. Sampling procedureswithout a sampling scheme are not relevant for allowed relationships.

If you enter new entries for allowed relationships, the system checks whethercorresponding entries (sampling plans) are available in the relevant samplingscheme for all inspection severities in the dynamic modification rule and for anyavailable AQL value in the sampling procedure.

In a task list only combinations of dynamic modification rules and samplingprocedures with a sampling scheme are allowed that are defined as allowedrelationships in QM.

Figure 30: General Sample Determination

2006/Q2 © 2006 SAP AG. All rights reserved. 53

Page 64: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

54 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 65: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Dynamic Modification

Exercise 3: Dynamic Modification Rule

Exercise ObjectivesAfter completing this exercise, you will be able to:� Create dynamic modification rules.

Business ExampleYou reduce the inspection scope using suitable dynamic modification rules so thatyou can reduce the expense of inspections as a result of improved quality. Thesecan also allow for an inspection skip.

Task: Basic data for the dynamic modificationThe dynamic modification rules are part of the basic data for dynamicmodifications. The following tasks contain two examples for dynamicmodification rules.

1. Creating a dynamic modification rule without a sampling scheme

You reduce the inspection scope using suitable dynamic modification rules,so that you can reduce your appraisal costs as a result of improved quality.Define dynamic modification rule A## for dynamic modification when youmake the usage decision. A reset period is not needed for the quality level.

The initial inspection stage allows an inspection without a sampling scheme.The second inspection stage should allow for a skip. At the next inspectionstage, the inspection should be performed without a sampling scheme.

If no inspection lot is rejected after four inspections with the initial inspectionstage, five inspection lots should be skipped. Afterwards, an inspection iscarried out again. If this inspection is OK, five more lots can be skipped.

A rejection at any stage of the dynamic modification rule takes you back tothe beginning of the cycle. That means to the initial inspection stage.

This dynamic modification rule must not be added to the allowedrelationships.

Make a note of the individual inspection stages:

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 55

Page 66: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Stage Inspec-tionseverity

skip Initial inspectionstage

Short text

Make a note of the settings for the stage change:

OK Not OKInsp.stage No. of

inspec-tions

No. ofskips

Newinsp.stage

Rejections New insp.stage

2. Creating a dynamic modification rule with a sampling scheme

Define another dynamic modification rule B## for dynamic modificationwhen you make the usage decision. A reset period is not needed for thequality level.

The initial inspection stage allows an inspection with the inspection severityNormal. The inspection severity Reduced should be used in the secondinspection stage. The third stage of the dynamic modification rule should bea skip.

If no inspection lot was rejected after four inspections with the initialinspection stage, four more inspection lots should be inspected with theinspection severity Reduced. Then inspection lots should be skipped. Theinspection lots should not be skipped for more than 100 days. After thisperiod, four inspection lots should be inspected with the inspection severityReduced.

A rejection at any stage of the dynamic modification rule takes you back tothe beginning of the cycle. That means to the initial inspection stage.

Continued on next page

56 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 67: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Dynamic Modification

Add this dynamic modification rule to the allowed relationships with yoursampling procedure SP03-##.

Hint: The maximum number of skips is limited to 32,767 becauseof the nature of the database field. You must also enter the numberof skips when entering a maximum skip duration in days.

Make a note of the individual inspection stages:

Stage Inspec-tionseverity

skip Initial inspectionstage

Short text

Make a note of the settings for the stage change:

OK Not OKInsp.stage No. of

inspec-tions

No. ofskips

Max.skip

duration

Newinsp.stage

Rejections Newinsp.stage

2006/Q2 © 2006 SAP AG. All rights reserved. 57

Page 68: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Solution 3: Dynamic Modification RuleTask: Basic data for the dynamic modificationThe dynamic modification rules are part of the basic data for dynamicmodifications. The following tasks contain two examples for dynamicmodification rules.

1. Creating a dynamic modification rule without a sampling scheme

You reduce the inspection scope using suitable dynamic modification rules,so that you can reduce your appraisal costs as a result of improved quality.Define dynamic modification rule A## for dynamic modification when youmake the usage decision. A reset period is not needed for the quality level.

The initial inspection stage allows an inspection without a sampling scheme.The second inspection stage should allow for a skip. At the next inspectionstage, the inspection should be performed without a sampling scheme.

If no inspection lot is rejected after four inspections with the initial inspectionstage, five inspection lots should be skipped. Afterwards, an inspection iscarried out again. If this inspection is OK, five more lots can be skipped.

A rejection at any stage of the dynamic modification rule takes you back tothe beginning of the cycle. That means to the initial inspection stage.

This dynamic modification rule must not be added to the allowedrelationships.

Make a note of the individual inspection stages:

Stage Inspec-tionseverity

skip Initial inspectionstage

Short text

Make a note of the settings for the stage change:

Continued on next page

58 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 69: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Dynamic Modification

OK Not OKInsp.stage No. of

inspec-tions

No. ofskips

Newinsp.stage

Rejections New insp.stage

a) Logistics→ Quality Management→ Quality Planning→ Basic Data→ Sample→ Dynamic Modification Rule→ Create (QDR1)

Enter the description A## in the Modification rule field. ## is yourgroup number. By choosing the Return key, the pushbutton DynamicModification Rule, or Enter, the Header Data screen appears. On thisscreen, you can define a short text for the dynamic modification rule, aswell as the time of dynamic modification (at usage decision).

By choosing the F5 function key or the pushbutton Next screen, you cancall up the Inspection Stages screen for the dynamic modification rule.

Define individual inspection stages using the following table:

Stage In-spec-tionsever-ity

skip Initial inspectionstage

Short text

10 001 X Inspection start20 X Skip stage30 001 One-off inspection

To maintain the stage changes, you must select all inspection stages andswitch to the detail screens for the individual inspection stage changesusing the pushbutton Stage change.

Hint: You can select all stages of the dynamic modificationrule using the Select all pushbutton.

Define the individual inspection stages using the following table:

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 59

Page 70: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

OK Not OKInsp.stage No. of

inspec-tions

No. ofskips

Newinsp.stage

Rejections New insp.stage

10 4 20 1 10

20 5 30 1 1030 1 20 1 10

Save your entries.

Hint: Answer the query regarding �allowed relationships�with NO.

2. Creating a dynamic modification rule with a sampling scheme

Define another dynamic modification rule B## for dynamic modificationwhen you make the usage decision. A reset period is not needed for thequality level.

The initial inspection stage allows an inspection with the inspection severityNormal. The inspection severity Reduced should be used in the secondinspection stage. The third stage of the dynamic modification rule should bea skip.

If no inspection lot was rejected after four inspections with the initialinspection stage, four more inspection lots should be inspected with theinspection severity Reduced. Then inspection lots should be skipped. Theinspection lots should not be skipped for more than 100 days. After thisperiod, four inspection lots should be inspected with the inspection severityReduced.

A rejection at any stage of the dynamic modification rule takes you back tothe beginning of the cycle. That means to the initial inspection stage.

Add this dynamic modification rule to the allowed relationships with yoursampling procedure SP03-##.

Hint: The maximum number of skips is limited to 32,767 becauseof the nature of the database field. You must also enter the numberof skips when entering a maximum skip duration in days.

Make a note of the individual inspection stages:

Continued on next page

60 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 71: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Dynamic Modification

Stage Inspec-tionseverity

skip Initial inspectionstage

Short text

Make a note of the settings for the stage change:

OK Not OKInsp.stage No. of

inspec-tions

No. ofskips

Max.skip

duration

Newinsp.stage

Rejections Newinsp.stage

a) Logistics→ Quality Management→ Quality Planning→ Basic Data→ Sample→ Dynamic Modification Rule→ Create (QDR1)

Enter the description B## in the field Modification rule. ## is yourgroup number. By choosing the Return key, the pushbutton DynamicModification Rule, or Enter, the Header Data screen appears. On thisscreen, you can define a short text for the dynamic modification rule, aswell as the time of dynamic modification (at usage decision).

By choosing the F5 function key or the pushbutton Next screen, you cancall up the Inspection Stages screen for the dynamic modification rule.

Define individual inspection stages using the following table:

Stage In-spec-tionsever-ity

skip Initial inspectionstage

Short text

10 004 X Normal inspection20 002 Reduced

inspection30 X Skip stage

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 61

Page 72: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Select all inspection stages and define the individual stage changesusing the following table:

OK Not OKInsp.stage No. of

inspec-tions

No. ofskips

Max.skipdura-tion

Newinsp.stage

No. ofrejections

Newinsp.stage

10 4 20 1 10

20 4 30 1 1030 32 767 100 20 1 10

Save your entries.

Confirm the question Add dynamic modification rule to the allowedrelationships? with Yes.

The system displays the message that Dynamic modification ruleB## was created and then the view Allwd. Relationships: SamplingProcedures/Dynamic Mod. Rule appears. Assign sampling procedureSP03-## to dynamic modification rule B## using the pushbutton Newentries and enter a short text.

Save your entries.

Hint: You can also maintain allowed relationships at any timeby choosing:

Logistics→ Quality Management→ Quality Planning→Basic Data→ Sample→ Dynamic Modification Rule→Assign Sampling procedure (QDB1)

or:

Logistics→ Quality Management→ Quality Planning→Basic Data→ Sample→ Dynamic Modification Rule→Assign Dynamic Modification Rule (QDB1)

62 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 73: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Dynamic Modification

Lesson Summary

You should now be able to:� Describe the structure of the modification rule.� Explain how to use dynamic modification.

2006/Q2 © 2006 SAP AG. All rights reserved. 63

Page 74: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Lesson: Inspection Setup - Mass Maintenance

Lesson OverviewWhen QM is implemented, a large number of materials have to be prepared forthe inspection processes. In addition, it may also be necessary to change theinspection setup when using a large number of materials. Mass maintenance canbe used to accommodate these requirements.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Describe the mass maintenance options for the inspection setup.� Use mass maintenance for an inspection setup that is already active.

Business ExampleMaterials must have the correct inspection setup in the QM view of the materialmaster for a quality inspection at various points in the logistical processes. Tomaintain this inspection setup, a large number of materials are processed.

Inspection Setup - Mass Maintenance

Figure 31: Inspection Setup - Mass Maintenance

64 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 75: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection Setup - Mass Maintenance

The mass maintenance of the Inspection Setup (transaction QA08) makesprocessing easier:

� Mass activation or deactivation of inspection type.

� You can activate or deactivate a chosen inspection type generally orbased on the selection criteria plant, material,and material type.

� Activate despite inspection stock

When you set this indicator, inspection lots are automatically createdto avoid stock discrepancies between QM and MM, if you activatethe first stock-relevant inspection type. The inspection type is copiedfrom Customizing for this.

� Inspection setup individual processing

� You can display or edit the Inspection Setup directly for one or moreselected materials.

� Inspection setup mass processing

� You can change the Inspection Setup for a selected inspection typegenerally or based on the selection criteria.

� You can create change documents for each processing type. A changedocument provides information about which changes were made to a masterrecord, by whom, and when.

Figure 32: QM Master Data - Summary 1

You can maintain a relationship between a sampling procedure and a dynamicmodification rule for each inspection type in the QM view of the material master.

2006/Q2 © 2006 SAP AG. All rights reserved. 65

Page 76: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

66 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 77: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection Setup - Mass Maintenance

Exercise 4: Inspection Setup - MassMaintenance

Exercise ObjectivesAfter completing this exercise, you will be able to:� Change the inspection setup data in the QM view of the material master.� Create an inspection lot manually for defects recording.

Business ExampleMaterials must have the correct inspection setup in the QM view of the materialmaster for a quality inspection at various points of the logistics supply chain. Youmust edit a large number of materials to maintain this inspection setup data.

Task 1: Mass maintenance of the inspection setup inthe materialsChanging inspection setup data in the material master

1. For greater efficiency, you have decided to work only with defects recordingfor one inspection type. To do this, you must change the inspection setup forthe corresponding materials. You can use the transaction for maintaining theinspection setup to make these changes.

For materials T-BQ1## and T-BQ2##, the inspection setup should bechanged for inspection type 05 in plant 1000. These materials should beinspected without a material specification or inspection plan. An inspectionpercentage of 5% and the dynamic modification rule A## are used for thesample determination.

Hint: On the screen QM-specific data selection for material, choosethe pushbutton for multiple selection to select the two materials andthen enter the desired materials as single values.

Caution: Use multiple selection to ensure that you change only yourown materials and not the materials of the other course participants.

Make a note on the following overview of the inspection type settings thatare relevant for this exercise:

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 67

Page 78: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Description Indicator Description IndicatorInsp. with mat.spec.

100 % inspection

Insp. with task list Manual sampleAutomaticassignment

Skips allowed

Checkcharacteristics

Automatic UD

Entry EntryInspectionpercentage

Dyn. mod. rule

Task 2:Creating an inspection lot manually for defects recording

1. You want to create an inspection lot manually for a follow-up inspection atgoods receipt. The follow-up inspection occurs for material T-BQ1## inplant 500. The inspection lot origin is 05 (Miscellaneous goods movement)and the inspection type is also 05. The inspection lot quantity is 1000 pieces.

Also enter your group number in the Short text field.

Save the inspection lot.

Display the inspection lot and make a note of the following data:

Inspection lot number: ___________________________________System status: ___________________________________Sample size: ___________________________________Dynamic modificationrule:

___________________________________

Task 3:Maintaining Your List of Favorites � Optional Exercise

1. Since you often work with inspection lots, it is useful to enter the mostimportant transactions (for example, Display inspection lot) in your listof favorites.

You can do this in the following ways:

Continued on next page

68 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 79: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection Setup - Mass Maintenance

� Using �drag and drop�:

Move the required transaction to your list of favorites using the mouse.� Using the right mouse button:

Right-click the required transaction and choose Add to favorites.� Using the button in the toolbar:

Choosing the button in the toolbar copies the current entry.� Using the transaction code:

Make sure that you are in the initial menu. Choose Extras→ Settingsand choose the entry Display technical names.

Select the transaction and note the corresponding transaction code.Right-click the favorites folder to transfer the transaction to yourfavorites list.

Note that your favorites are displayed differently depending on the methodyou used.

If you want to rename your favorites, you can specify another name with aright mouse click (Change favorites).

2006/Q2 © 2006 SAP AG. All rights reserved. 69

Page 80: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Solution 4: Inspection Setup - MassMaintenanceTask 1: Mass maintenance of the inspection setup inthe materialsChanging inspection setup data in the material master

1. For greater efficiency, you have decided to work only with defects recordingfor one inspection type. To do this, you must change the inspection setup forthe corresponding materials. You can use the transaction for maintaining theinspection setup to make these changes.

For materials T-BQ1## and T-BQ2##, the inspection setup should bechanged for inspection type 05 in plant 1000. These materials should beinspected without a material specification or inspection plan. An inspectionpercentage of 5% and the dynamic modification rule A## are used for thesample determination.

Hint: On the screen QM-specific data selection for material, choosethe pushbutton for multiple selection to select the two materials andthen enter the desired materials as single values.

Caution: Use multiple selection to ensure that you change only yourown materials and not the materials of the other course participants.

Make a note on the following overview of the inspection type settings thatare relevant for this exercise:

Description Indicator Description IndicatorInsp. with mat.spec.

100 % inspection

Insp. with task list Manual sampleAutomaticassignment

Skips allowed

Checkcharacteristics

Automatic UD

Entry EntryInspectionpercentage

Dyn. mod. rule

Continued on next page

70 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 81: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection Setup - Mass Maintenance

a) Logistics→ Quality Management→ Quality Planning→ LogisticsMaster Data→ Material→ Inspection Setup (QA08)

The selection screen Mass Change of QM Inspection Setup Data inMaterials appears. Specify plant 1000 in the screen area QM-specificdata selection for material. You use the multiple selection pushbuttonthat is next to the material number field to select materials. Onthe Single vals tab page, enter the material numbers T-BQ1## andT-BQ2##. After leaving the multiple selection screen using thepushbutton Copy or the F8 function key, the selection screen for theinspection setup appears again. Choose the Mass processing tab pageand enter inspection type 05.

Execute the mass change using the F8 function key or the Executepushbutton.

The screen Parameters for Inspection Setup Data in Materials appears.In accordance with the specifications on the selection screen, you seethe Customizing settings for inspection type 05.

If you want to process inspection lots for this inspection type only withdefects recording, no entries should exist in the inspection setup thatreference specifications (for example, task list, specification). Enter thefollowing data for sample determination and dynamic modification:

Description Indicator Description IndicatorInsp. with mat.spec.

100 %inspection

Insp. with tasklist

Manual sample

Automaticassignment

Skips allowed X

Checkcharacteristics

Automatic UD

Entry EntryInspectionpercentage

5 % Dyn. mod. rule A##

After changing the entries and pressing Return, an overview screen ofmaterials that you can change appears. Select the materials and saveyour changes. In the status column, you can see that 2 materials wereedited.

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 71

Page 82: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Task 2:Creating an inspection lot manually for defects recording

1. You want to create an inspection lot manually for a follow-up inspection atgoods receipt. The follow-up inspection occurs for material T-BQ1## inplant 500. The inspection lot origin is 05 (Miscellaneous goods movement)and the inspection type is also 05. The inspection lot quantity is 1000 pieces.

Also enter your group number in the Short text field.

Save the inspection lot.

Display the inspection lot and make a note of the following data:

Inspection lot number: ___________________________________System status: ___________________________________Sample size: ___________________________________Dynamic modificationrule:

___________________________________

a) Logistics→ Quality Management→ Quality Inspection→ InspectionLot→ Processing→ Create (QA01)

Enter the following data on the initial screen:

Field name or data type ValuesMaterial T-BQ1##Plant 1000Inspection lot origin 05

You can access the detail data for the inspection lot by choosing Enter.

Field name or data type ValuesInsp. lot size 500Short text Group ##

Choose the Return key to release the data. Save your entries.

Display your manually created inspection lot:

Logistics→ Quality Management→ Quality Inspection→ InspectionLot→ Processing→ Display (QA03)

Continued on next page

72 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 83: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection Setup - Mass Maintenance

The number of the inspection lot that was last created is displayed in thefield Inspection lot. By choosing Enter, the screen Display inspectionlot appears. The following data is displayed on this screen:

Field name or data type ValuesInspection lot 50000000.......System status REL CALC QLCH

Insp. lot quantitiesSample size 25 PC

Insp. specificationsDyn. mod. rule A##

Task 3:Maintaining Your List of Favorites � Optional Exercise

1. Since you often work with inspection lots, it is useful to enter the mostimportant transactions (for example, Display inspection lot) in your listof favorites.

You can do this in the following ways:

� Using �drag and drop�:

Move the required transaction to your list of favorites using the mouse.� Using the right mouse button:

Right-click the required transaction and choose Add to favorites.� Using the button in the toolbar:

Choosing the button in the toolbar copies the current entry.� Using the transaction code:

Make sure that you are in the initial menu. Choose Extras→ Settingsand choose the entry Display technical names.

Select the transaction and note the corresponding transaction code.Right-click the favorites folder to transfer the transaction to yourfavorites list.

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 73

Page 84: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Note that your favorites are displayed differently depending on the methodyou used.

If you want to rename your favorites, you can specify another name with aright mouse click (Change favorites).

a) You can use one of the following ways to maintain favorites:

� Using �drag and drop�:

Move the required transaction to your list of favorites using themouse.

� Using the right mouse button:

Right-click the required transaction and choose Add to favorites.

� Using the button in the toolbar:

Choosing the button in the toolbar copies the current entry.

� Using the transaction code:

Make sure that you are in the initial menu. Choose Extras→Settings and choose the entry Display technical names.

Select the transaction and note the corresponding transactioncode. Right-click the favorites folder to transfer the transaction toyour favorites list.

74 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 85: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection Setup - Mass Maintenance

Lesson Summary

You should now be able to:� Describe the mass maintenance options for the inspection setup.� Use mass maintenance for an inspection setup that is already active.

2006/Q2 © 2006 SAP AG. All rights reserved. 75

Page 86: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Lesson: Master inspection characteristic

Lesson OverviewAn inspection characteristic describes what is to be inspected. If particularinspection specifications are required in many task lists, you can create a suitablemaster inspection characteristic and include this in different task lists. Masterinspection characteristics, therefore, help to simplify and standardize inspectionplanning.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Describe the structure of master inspection characteristics.� Explain the options for using master inspection characteristics.

Business ExampleTo ensure consistency and standardization in inspection planning, masterinspection characteristics are used. This is to enable you to process requiredchanges centrally.

Master Inspection Characteristic

Figure 33: Master Inspection Characteristics: General

76 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 87: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Master inspection characteristic

A master inspection characteristic is an inspection characteristic that has beendefined for frequent use in task lists or should be evaluated for all inspection plans.Master inspection characteristics help to improve and standardize inspectionplanning. Search and replace functions for master inspection characteristicsensure simplified processing.

As of mySAP ERP 2005 (ECC 6.0), as well as using the short text and search fieldto search, you can also use an extended search function for master inspectioncharacteristics. The master inspection characteristics are connected to the SAPsearch engine TREX. You can find the corresponding settings in Customizingunder SAP NetWeaver -> Application Server -> System administration -> SearchEngine Service.

Figure 34: master inspection characteristic

An inspection characteristic describes the inspection criteria.

The characteristic control contains, for example:

� Characteristic type (qualitative, quantitative)� Results confirmation type (for example, summarized, single result)� Characteristic processing type (required characteristic, optional

characteristic)

2006/Q2 © 2006 SAP AG. All rights reserved. 77

Page 88: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Figure 35: Creating a Master Inspection Characteristic

When you create a master inspection characteristic, the status Being created isproposed. To be able to use the master inspection characteristic, the status mustbe set to Released.

Incomplete copy model: The master inspection characteristic must not becompletely maintained at creation. The missing entries can be added in the tasklist.

Complete copy model: The master inspection characteristic must be completelymaintained at creation. When linking the master inspection characteristic to a tasklist or a material specification, you can change the characteristic specifications.

Reference characteristic: The master inspection characteristic must becompletely maintained at creation When linking the master inspectioncharacteristic to a task list or material specification, the characteristic is lockedand can be maintained and replaced centrally.

Complete copy models and reference characteristics can be used in the materialspecification and they can also be used as �additional characteristics� (unplannedcharacteristics) in the results recording.

Changes to master inspection characteristics can be carried out with and withouthistory. The necessary default values are defined in Customizing for each plant.

78 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 89: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Master inspection characteristic

Figure 36: Control Indicators for the Master Inspection Characteristic

You can use the control indicators in the master inspection characteristic todetermine the process flow of the characteristic inspection in detail.

You can define default values for the control indicators in Customizing: QualityManagement→ Quality Planning→ Basic Data→ Inspection Characteristics,Inspection Method→ Define Default Values for Control Indicators. Read therelevant documentation in Customizing if you are defining default values.

History Management

Figure 37: Validity of a Master Inspection Characteristic

Validity statuses of master inspection characteristics or inspection methods arepossible through the use of versions.

When you change a version, you can find the valid master inspection characteristicor the valid inspection method by specifying the key date.

2006/Q2 © 2006 SAP AG. All rights reserved. 79

Page 90: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Figure 38: History Management

In Customizing, history management for master inspection characteristics orinspection methods can be activated for each plant.

If the history management is active, the version counter is increased when thereleased master inspection characteristic or inspection method version is changed.

The following occurs if you change master inspection characteristics and/orinspection methods that are referenced in a task list, a material specification or acertificate profile:

� If you change this basic data with the history, the changed data is notautomatically updated in the task list, material specification or certificateprofile.

� If you change this basic data without the history, the changed data isimmediately automatically updated in the task list, material specificationand certificate profile.

80 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 91: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Master inspection characteristic

Figure 39: Effect of History Management on Master InspectionCharacteristics

When you create a new version (validity status), the procedure shown above isfollowed if the master inspection characteristic is used in task lists or materialspecifications.

When you change the validity status or version, the procedure shown above is alsofollowed if the master inspection characteristic/inspection method is used in tasklists or material specifications.

The process described above is always followed, if the master inspectioncharacteristic was changed with history or a new version of the inspection methodis created.

History management for master inspection characteristics or inspection methodsis set up in Customizing for the plant.

Replace master data for a new version is set up in Customizing for the client.

2006/Q2 © 2006 SAP AG. All rights reserved. 81

Page 92: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Figure 40: Tolerance Key

The standard system contains preset tolerance tables for drill-holes and shaftsaccording to DIN ISO 286-2.

The use of target-value-dependent tolerance keys can be preset in Customizingfor the tolerance key.

The unit of measurement, target value, accuracy, and upper and lower specificationlimits are defined for each tolerance key.

82 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 93: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Master inspection characteristic

Exercise 5: Master InspectionCharacteristics

Exercise ObjectivesAfter completing this exercise, you will be able to:� Create and edit master records for inspection characteristics.� Describe the most important control indicators for qualitative and

quantitative inspection characteristics

Business ExampleThe quality inspection is performed in your company using inspection plans. Youset the indicator Master inspection characteristics, so that you do not have tomanually create inspection characteristics in the individual inspection plans. Youcan create these master inspection characteristics as master records in the planningphase and then copy or reference them in one or more task lists.

Task 1: Create a qualitative master inspectioncharacteristicYou use qualitative and quantitative master inspection characteristics accordingto requirements and operational area. You create a qualitative master inspectioncharacteristic here to use later in inspection planning.

1. You need a qualitative master inspection characteristic for the inspectionof packaging materials. For plant 1000, create this master inspectioncharacteristic with the identifier MK01-## and the short text Packaging.Enter Group ## in the search field to find the master inspection characteristic.The characteristic should be referenced in task lists and materialspecifications.

A sampling procedure should be used to determine the respective inspectionscope. It is very important that the correct packaging material is always used.Therefore, this characteristic must always be inspected. Summarized resultsrecording should be used. If the characteristic is not accepted during theinspection, you may want to record additional information about the errorsthat occurred for this characteristic. To evaluate these recorded errors later, itis important that you use corresponding error codes when recording them.The number of units inspected during results recording must correspond tothe planned number of units to be inspected. Additional documentation isnot required during results confirmation. The characteristic should only beprinted on the inspection instruction, if no skip exists for the characteristic.

Make a note of the settings for the characteristic control indicators:

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 83

Page 94: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Type[ ] Char. attribute

Sample[ ] Sampling procedure [ ] Additive sample[ ] SPC characteristic [ ] Destructive insp.[ ] Record number of defs

Results confirmation( ) Summ. recording ( ) Required char.( ) Single result ( ) Optional char.( ) No charac. rec. ( ) After accept.( ) Classed recording ( ) After rejection[ ] Autom. def. recording

Insp. scope Doc. confirmation( ) Scope not fixed ( ) No documentation( ) Fixed scope ( ) Docu. if rejected( ) Smaller scope ( ) Doc. required( ) Larger scope

Miscellaneous[ ] Long-term inspection[ ] Scrap share/q-score[ ] Res. rec. change docs[ ] Test-equip. assign.

Print( ) Print( ) Do not print( ) Do not print at skip

Hint: The master inspection characteristic can only be used in tasklists and material specifications, if it has the status Released.

Continued on next page

84 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 95: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Master inspection characteristic

Task 2: Create a quantitative master inspectioncharacteristicYou use qualitative and quantitative master inspection characteristics accordingto requirements and operational area. You create a qualitative master inspectioncharacteristic here to use later in inspection planning.

1. You also use the master inspection characteristics to inspect the weight.Create a quantitative master inspection characteristic with the identifierMK02-## in plant 1000 and the short text Weight. Enter Group ## in thesearch field to find the master inspection characteristic. This characteristicshould be used in task lists and material specifications and if necessary, itshould be changed to suit the material. In this case, use the Complete copymodel.

A sampling procedure should be used to determine the respective inspectionscope. The weight of the goods must always be known. Therefore, thischaracteristic must always be inspected. You must confirm single resultsduring results recording. The number of units inspected during resultsrecording must correspond to the planned number of units to be inspected.If the characteristic is not accepted during the inspection, you may wantto record additional information for this characteristic. If you change therecorded inspection results later, you must create change documents. Youshould be able to assign test equipment in a task list (for example, inspectionplan, routing, ..). The characteristic should only be printed on the inspectioninstruction, if no skip exists for the characteristic.

The weight should be 1.0 kg. A deviation of 0.1 kg below and 0.1 kg abovethis value is allowed. You do not need a tolerance key.

Make a note of the settings for the characteristic control indicators:

Type[ ] Lower specif. limit [ [ ] Upper specif. limit[ ] Check target value

Sample[ ] Sampling procedure [ ] Additive sample[ ] SPC characteristic [ ] Destructive insp.

Results confirmation( ) Summ. recording ( ) Required char.( ) Single result ( ) Optional char.

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 85

Page 96: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Results confirmation( ) No charac. rec. ( ) After accept.( ) Classed recording ( ) After rejection[ ] Autom. def. recording

Insp. scope Doc. confirmation( ) Scope not fixed ( ) No documentation( ) Fixed scope ( ) Docu. if rejected( ) Smaller scope ( ) Doc. required( ) Larger scope

Miscellaneous[ ] Long-term inspection [ ] Record measured vals[ ] Scrap share/q-score[ ] Res. rec. change docs[ ] Test-equip. assign.

Print Formula( ) Print ( ) No formula( ) Do not print ( ) Calculated characteristic( ) Do not print at skip ( ) Input processing

86 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 97: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Master inspection characteristic

Solution 5: Master InspectionCharacteristicsTask 1: Create a qualitative master inspectioncharacteristicYou use qualitative and quantitative master inspection characteristics accordingto requirements and operational area. You create a qualitative master inspectioncharacteristic here to use later in inspection planning.

1. You need a qualitative master inspection characteristic for the inspectionof packaging materials. For plant 1000, create this master inspectioncharacteristic with the identifier MK01-## and the short text Packaging.Enter Group ## in the search field to find the master inspection characteristic.The characteristic should be referenced in task lists and materialspecifications.

A sampling procedure should be used to determine the respective inspectionscope. It is very important that the correct packaging material is always used.Therefore, this characteristic must always be inspected. Summarized resultsrecording should be used. If the characteristic is not accepted during theinspection, you may want to record additional information about the errorsthat occurred for this characteristic. To evaluate these recorded errors later, itis important that you use corresponding error codes when recording them.The number of units inspected during results recording must correspond tothe planned number of units to be inspected. Additional documentation isnot required during results confirmation. The characteristic should only beprinted on the inspection instruction, if no skip exists for the characteristic.

Make a note of the settings for the characteristic control indicators:

Type[ ] Char. attribute

Sample[ ] Sampling procedure [ ] Additive sample[ ] SPC characteristic [ ] Destructive insp.[ ] Record number of defs

Results confirmation( ) Summ. recording ( ) Required char.( ) Single result ( ) Optional char.

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 87

Page 98: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Results confirmation( ) No charac. rec. ( ) After accept.( ) Classed recording ( ) After rejection[ ] Autom. def. recording

Insp. scope Doc. confirmation( ) Scope not fixed ( ) No documentation( ) Fixed scope ( ) Docu. if rejected( ) Smaller scope ( ) Doc. required( ) Larger scope

Miscellaneous[ ] Long-term inspection[ ] Scrap share/q-score[ ] Res. rec. change docs[ ] Test-equip. assign.

Print( ) Print( ) Do not print( ) Do not print at skip

Hint: The master inspection characteristic can only be used in tasklists and material specifications, if it has the status Released.

a) SAP Menu→ Logistics→ Quality Management→ Quality Planning→ Basic Data→ Inspection Characteristic→ Create (QS21)

Enter the following data on the initial screen:

Field name or data type ValuesPlant 1000Master inspection characteristic Mk01-##Valid from Current date

Continued on next page

88 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 99: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Master inspection characteristic

You can display the general data for the master inspection characteristicby choosing the F5 function key, the pushbutton Master inspectioncharacteristic or Enter. You set the indicator for a qualitativecharacteristic on this screen. Additional data for the general data:

Field name or data type ValuesReleasedStatusReference characteristic

Short text PackagingSearch field Group ##

You can display the settings for the control indicator for a qualitativecharacteristic by choosing Enter or the Control indicator pushbutton.Set the indicators as follows:

Type[ ] Char. attribute

Sample[x] Sampling procedure [ ] Additive sample[ ] SPC characteristic [ ] Destructive insp.[ ] Record number of defs

Results confirmation(�) Summ. recording (�) Required charac.( ) Single result ( ) Optional char.( ) No charac. rec. ( ) After accept.( ) Classed recording ( ) After rejection[x] Autom. def. recording

Insp. scope Doc. confirmation( ) Scope not fixed (�) No documentation(�) Fixed scope ( ) Docu. if rejected( ) Smaller scope ( ) Doc. required( ) Larger scope

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 89

Page 100: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Miscellaneous[ ] Long-term inspection[ ] Scrap share/q-score[ ] Res. rec. change docs[ ] Test-equip. assign.

Print( ) Print( ) Do not print(�) Do not print at skip

Hint: When you have edited the first screen of controlindicators, the second screen appears when you choose theReturn key.

Hint: If errors are detected during the inspection, you shouldchoose the error codes manually. Therefore, you do not have toassign error codes to the master inspection characteristic.

Confirm your info messages by choosing ENTER.

After you have edited the control indicators, the general data for themaster inspection characteristic appears again.

Save your entries.

Task 2: Create a quantitative master inspectioncharacteristicYou use qualitative and quantitative master inspection characteristics accordingto requirements and operational area. You create a qualitative master inspectioncharacteristic here to use later in inspection planning.

1. You also use the master inspection characteristics to inspect the weight.Create a quantitative master inspection characteristic with the identifierMK02-## in plant 1000 and the short text Weight. Enter Group ## in thesearch field to find the master inspection characteristic. This characteristicshould be used in task lists and material specifications and if necessary, itshould be changed to suit the material. In this case, use the Complete copymodel.

Continued on next page

90 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 101: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Master inspection characteristic

A sampling procedure should be used to determine the respective inspectionscope. The weight of the goods must always be known. Therefore, thischaracteristic must always be inspected. You must confirm single resultsduring results recording. The number of units inspected during resultsrecording must correspond to the planned number of units to be inspected.If the characteristic is not accepted during the inspection, you may wantto record additional information for this characteristic. If you change therecorded inspection results later, you must create change documents. Youshould be able to assign test equipment in a task list (for example, inspectionplan, routing, ..). The characteristic should only be printed on the inspectioninstruction, if no skip exists for the characteristic.

The weight should be 1.0 kg. A deviation of 0.1 kg below and 0.1 kg abovethis value is allowed. You do not need a tolerance key.

Make a note of the settings for the characteristic control indicators:

Type[ ] Lower specif. limit [ [ ] Upper specif. limit[ ] Check target value

Sample[ ] Sampling procedure [ ] Additive sample[ ] SPC characteristic [ ] Destructive insp.

Results confirmation( ) Summ. recording ( ) Required char.( ) Single result ( ) Optional char.( ) No charac. rec. ( ) After accept.( ) Classed recording ( ) After rejection[ ] Autom. def. recording

Insp. scope Doc. confirmation( ) Scope not fixed ( ) No documentation( ) Fixed scope ( ) Docu. if rejected( ) Smaller scope ( ) Doc. required( ) Larger scope

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 91

Page 102: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Miscellaneous[ ] Long-term inspection [ ] Record measured vals[ ] Scrap share/q-score[ ] Res. rec. change docs[ ] Test-equip. assign.

Print Formula( ) Print ( ) No formula( ) Do not print ( ) Calculated characteristic( ) Do not print at skip ( ) Input processing

a) SAP Menu→ Logistics→ Quality Management→ Quality Planning→ Basic Data→ Inspection Characteristic→ Create (QS21)

Enter the following data on the initial screen:

Field name or data type ValuesPlant 1000Master inspection characteristic Mk02-##Valid from Current date

If you have to create several similar master inspection characteristics,you can create them With a copy model. In this case, the settings arecopied from an inspection characteristic and can be changed.

You can display the general data for the master inspection characteristicby choosing the F5 function key, the pushbutton Master inspectioncharacteristic or Enter. You set the indicator for a quantitativecharacteristic on this screen. Additional data for the general data:

Field name or data type ValuesReleasedStatusComplete copy model

Short text WeightSearch field Group ##

You can display the settings of the control indicators for a quantitativecharacteristic by choosing Enter or the Control indicator pushbutton.Set the control indicators as follows:

Continued on next page

92 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 103: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Master inspection characteristic

Type[x] Lower specif. limit [ [x] Upper specif. limit[x] Check target value

Sample[x] Sampling procedure [ ] Additive sample[ ] SPC characteristic [ ] Destructive insp.

Results confirmation( ) Summ. recording (�) Required charac.(�) Single result ( ) Optional char.( ) No charac. rec. ( ) After accept.( ) Classed recording ( ) After rejection[ ] Autom. def. recording

Insp. scope Doc. confirmation( ) Scope not fixed ( ) No documentation(�) Fixed scope (�) Docu. if rejected( ) Smaller scope ( ) Doc. required( ) Larger scope

Miscellaneous[ ] Long-term inspection [x] Record measured vals[ ] Scrap share/q-score[x] Res. rec. change docs[x] Assign test equipment

Print Formula( ) Print (�) No formula( ) Do not print ( ) Calculated characteristic(�) Do not print at skip ( ) Input processing

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 93

Page 104: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

After editing the control indicators, the tolerance key for thecharacteristic is displayed. You can enter 1 as the target value or youcan exit the screen using the Return key. The quantitative data for thecharacteristic then appears. On this screen, you define the number ofdecimal places, the unit of measurement (kg), if necessary the targetvalue (1), and both the lower specification limit (0.9) and the upperspecification limit (1.1) for the characteristic. Exit the screen.

Save your entries.

94 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 105: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Master inspection characteristic

Lesson Summary

You should now be able to:� Describe the structure of master inspection characteristics.� Explain the options for using master inspection characteristics.

2006/Q2 © 2006 SAP AG. All rights reserved. 95

Page 106: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Lesson: Input Processing for Measured Values

Lesson OverviewIn this lesson, you will learn about the functions and use of input processing formeasured values.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Explain the functions of input processing for measured values.� Describe how these functions can be used.

Business ExampleIn your company, there are particular requirements and stipulations for processingmeasured values. For example, particular measured values are to be rounded toa significant number of digits or a different value is to be calculated from themeasured value entered using a formula.

Input Processing for Measured Values

Figure 41: Input Processing for Measured Values

96 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 107: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Input Processing for Measured Values

Particular requirements for the determination and processing of measured valuesinclude:

� The measured value is to be changed after input (for example, it is to bemultiplied by a specific factor or rounded according to customer-specificrules).

� The measured value that has been entered (original value) is to be outputindependently of the decimal places defined in the plan or master inspectioncharacteristic. If, for example, two decimal places were planned in theinspection characteristic, but the measured value only has one decimal place,then only one decimal place will be output in results recording (outputlike input).

� The number of significant digits is not fixed. It is dependent on the actualmeasured size of the measured value. It must therefore be possible to controlthe rounding using a significance type that takes this dependency intoconsideration. A significance type can be defined as follows:

� Measured Value: 0<x<1, Significant Digits: 2, Example: 0.17253 isoutput as 0.17

� Measured Value: 0<x<10, Significant Digits: 2, Example: 1.173is output as 1.2

� Measured value: 10<x<12, Significant Digits: 2, Example: 11.173is output as 11

� The original value should be saved.� A direct conversion of the formula should be performed with user-defined

formulas. The required rounding is performed using a BAdI method in thisSAP solution.

Input Processing: Prerequisites

� In Customizing, the attribute of the BAdI parameter must be stored in theinput processing key.

� The control indicator for input processing must be set in the (master)inspection characteristic.

� The input processing key must be entered in the quantitative data of the(master) inspection characteristic.

� In the certificate profile for the characteristic, the value set for the number ofdecimal places should be 98 (so that the number of decimal places outputon the certificate corresponds to the number of decimal places from inputprocessing).

2006/Q2 © 2006 SAP AG. All rights reserved. 97

Page 108: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Customizing of BAdI parameters:

� You assign parameters to the BAdI methods in input processing fornon-classed measured values using a Customizing table (Customizing→Quality management→ Quality Inspection→ Results Recording→ DefineParameters for Input Processing). Here, you can define the three-digit keyfor input processing, a language-dependent short text for the key, and therequired parameters on the detail screen (a maximum of six).

� The filter values are cross-client values and therefore valid in the wholesystem.

� The names of the parameters are not fixed and can be edited in the table.This means that you can assign meaningful names.

Proposed values for control indicators:

� The indicator for input processing of non-classed measured valuesis considered in the control indicator default values (Customizing→Quality Management→ Quality Planning→ Basic Data→ InspectionCharacteristic, Inspection Method→ Define Default Values for ControlIndicators).

Figure 42: Input Processing: Customizing

98 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 109: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Input Processing for Measured Values

Figure 43: Input Processing: Control Indicator

At results recording, the BAdI (QM_INPUT_PROCEDURE) defined for theinspection characteristic is run and the input value is processed.

Input processing is intended for non-classed quantitative characteristics:

� Mean values� Single values

The method INPUT_PROCEDURE of the BAdI mentioned above can be used tochange the following fields:

� Input value� Attribute� Results data origin� Deviating decimal places

There is also the Original Value field, in which the value you entered is stored.

2006/Q2 © 2006 SAP AG. All rights reserved. 99

Page 110: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Figure 44: Input Processing: Quantitative Data

100 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 111: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Input Processing for Measured Values

Lesson Summary

You should now be able to:� Explain the functions of input processing for measured values.� Describe how these functions can be used.

2006/Q2 © 2006 SAP AG. All rights reserved. 101

Page 112: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Lesson: Code Groups and Codes

Lesson OverviewYou can use coding to specify how particular defects, defect causes, problems,and so on, are to be recorded and valuated. In this lesson, the options for usingcoding are described in detail.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Describe the structure of coding.� Describe how the different catalog types can be used.

Business ExampleTo record errors consistently, your company uses error codes. These are used inthe inspection processes and also in the analysis of defects. By structuring thecoding appropriately, a material-dependent assignment should be possible.

Catalogs and Coding

Figure 45: Using Catalogs

102 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 113: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Code Groups and Codes

You use catalogs to define, manage, and standardize information (for example,defect types, characteristic attributes, tasks) consistently for all clients or plants. Ifyou use catalogs, it is easier to record and evaluate qualitative data and describeobjects.

In a catalog, information is assigned a unique alphanumeric code and anexplanatory text.

Figure 46: Catalog Types

Catalogs are sorted into catalog types.

The catalog types 0 - 9 and A - O are defined by SAP; the catalog types P - Z canbe defined by the user.

2006/Q2 © 2006 SAP AG. All rights reserved. 103

Page 114: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Figure 47: Hierarchy of Catalogs, Example: Catalog Type 1 (CharacteristicAttributes)

Figure 48: Hierarchy of Catalogs, Example: Catalog Type 9 (Defect Types)

Catalog (1 character, alphanumeric)

� Summary of code groups according to contents (for example, characteristicattributes, defect type, defect cause etc).

104 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 115: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Code Groups and Codes

Code groups (max. of 8 characters, alphanumeric)

� Summary of codes according to contents (for example, surface attribute,color).

Codes (max. of 4 characters, alphanumeric)

� Description of a characteristic, defect, cause etc.

Hint: The codes contained in a code group are sorted alphanumerically.Therefore, use leading zeros if necessary when you define the codes.

The catalog type is maintained in Customizing.

The code groups and codes are maintained in one transaction.

The codes and the code groups can be maintained in several languages.

Choose Utilities→ Select languages to select the required languages. You canthen select Edit→ Translation to translate the corresponding entries.

Figure 49: Code Groups and Codes

Simplified processing by:

� Using table control technology� Changing/ adding code groups and codes to a catalog using one transaction� Switching from the selected code group directly to its corresponding code

You can enter individual code groups or all code groups for a catalog.

2006/Q2 © 2006 SAP AG. All rights reserved. 105

Page 116: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

You can translate entries into various languages. Choose Utilities→ SelectLanguages to select the required languages. You can then select Edit →Translation to translate the corresponding entries.

106 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 117: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Code Groups and Codes

Exercise 6: Catalogs, Code Groups, andCodes

Exercise ObjectivesAfter completing this exercise, you will be able to:� Edit code groups and codes within catalogs.

Business ExampleYou want to valuate certain qualitative inspection characteristics using thecharacteristic attribute. You define code groups and codes and create suitableselected sets for characteristic valuation, so that you can valuate characteristics inthe whole company according to the same specifications.

Task: Edit the catalogs for the characteristic attributeand the defect types.Creating code groups and codes

1. Only certain packaging materials can be used for packing goods. Therefore,you create code group CG01-## for the packaging materials with theappropriate codes. You should use these codes in the results recording forqualitative characteristics.

Which catalog type do you use for these code groups and codes?

Catalog type:________________________________

2. You should use defect codes to record defects in connection with the qualityinspection or the notification processing. Therefore, create code groupFE01-## for the possible lighting defects with the corresponding codes.

Assign an appropriate defect class to the respective defect codes. To selectthe defect class, use the F4 help for the Defect class field.

Which catalog type do you use for these code groups and codes?

Catalog type:________________________________

2006/Q2 © 2006 SAP AG. All rights reserved. 107

Page 118: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Solution 6: Catalogs, Code Groups, andCodesTask: Edit the catalogs for the characteristic attributeand the defect types.Creating code groups and codes

1. Only certain packaging materials can be used for packing goods. Therefore,you create code group CG01-## for the packaging materials with theappropriate codes. You should use these codes in the results recording forqualitative characteristics.

Which catalog type do you use for these code groups and codes?

Continued on next page

108 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 119: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Code Groups and Codes

Catalog type:________________________________

a) Logistics→ Quality Management→ Quality Planning→ Basic Data→ Catalog→ Code Group→ Edit (QS41)

Enter the following data on the initial screen for editing catalogs:

Field name or data type ValuesCatalog 1Code Group CG01-##

By choosing the Return key, the pushbutton Create/change, or Enter,the Change Code Group screen appears. Enter a description for yourcode group in the short text field, for example Packaging material forlamps. To use the code group, it must have the status Released.

Select the line with your code group CG01-##. In the dialog structure,double-click on Codes. The Change Codes view appears. On thisoverview screen, no codes have been entered yet for code groupCG01-##. Use function key F5 or the pushbutton New entries, andenter codes for the packaging materials. For example:

Code Short text for code1000 Paper2000 Plastic3000 Wood-wool4000 Rags5000 Miscellaneous6000 No packaging material

Save your code group and the corresponding codes.

Hint: The catalog profile allows you to group code groupsfrom different catalog types.

You can assign coding based on material, for example. Usethis feature when structuring coding to create contents of codegroups as required.

2. You should use defect codes to record defects in connection with the qualityinspection or the notification processing. Therefore, create code groupFE01-## for the possible lighting defects with the corresponding codes.

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 109

Page 120: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Assign an appropriate defect class to the respective defect codes. To selectthe defect class, use the F4 help for the Defect class field.

Which catalog type do you use for these code groups and codes?

Catalog type:________________________________

a) Logistics→ Quality Management→ Quality Planning→ Basic Data→ Catalog→ Code Group→ Edit (QS41)

Enter the following data on the initial screen for editing catalogs:

Field name or data type ValuesCatalog 9Code Group FE01-##

By choosing the Return key, the pushbutton Create/change, or Enter,the Change Code Group screen appears. Enter a description for yourcode group in the short text field, for example Lighting defect, GR##.To use the code group, it must have the status Released.

Select the line with your code group FE01-##. In the dialog structure,double-click Codes. The Change Codes view appears. No codes havebeen entered yet for code group FE01-## in this overview screen.Choose function key F5 or the pushbutton New entries and enter codesfor possible defects. For example:

Code Short text for code Defect class0100 Dirty Major defect B0110 Dirty glass Major defect B0120 Faulty connection Major defect B0200 Damaged connection Major defect A0300 Damaged glass Critical defect9999 Other defect Major defect A

Save your code group and the corresponding codes.

110 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 121: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Code Groups and Codes

Lesson Summary

You should now be able to:� Describe the structure of coding.� Describe how the different catalog types can be used.

2006/Q2 © 2006 SAP AG. All rights reserved. 111

Page 122: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Lesson: Selected sets and catalog profile

Lesson OverviewYou can use selected sets to group codes together in a catalog type. In this lesson,you will find out how to structure selected sets and how to use them in inspectionplanning.

The catalog profile allows you to group together the codes from different catalogtypes. This ensures that there is a suitable selection of codes (for example, defectcauses, defect locations, tasks) available for defects recording or notificationprocessing for example.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Describe the structure of a selected set.� Explain how selected sets can be used in inspection planning.

Business ExampleDuring results recording, a characteristic attribute is recorded (for example, coloror surface condition) for particular inspection characteristics. This coding isgrouped together in selected sets and valuated.

To process quality notifications efficiently, it is often advisable to categorize theproblem areas according to their contents. You can summarize the possible codesin a catalog profile. This allows you to process problems quickly and easily.

112 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 123: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Selected sets and catalog profile

Selected Sets and Codes of Selected Sets

Figure 50: Selected Sets

Codes from different code groups within the same catalog type can be groupedtogether in selected sets.

In Customizing for the catalog type, you can make a setting specifying whetherthe creation of selected sets is allowed.

Codes that are copied to a selected set are called codes of selected sets.

Only selected set codes of catalog type 1 (�characteristic attributes�) can be usedfor the valuation of a qualitative inspection characteristic in results recording.

2006/Q2 © 2006 SAP AG. All rights reserved. 113

Page 124: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Figure 51: Selected Sets and Codes of Selected Sets

When you maintain the complete selected set index, the system blocks other usersfrom accessing that particular catalog type.

Each code of selected sets of catalog type 1 must be valuated. If the valuation isRejected, you must specify a defect class.

The interface for selected sets and set codes is identical to the interface for codegroups and codes.

114 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 125: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Selected sets and catalog profile

Figure 52: Creating a Selected Set

When you copy a selected set or a set code to the selected set that you areprocessing, the valuation and defect class (if available) are also copied. You canchange the valuation and defect class.

When you have created a selected set, you can assign it to the inspectioncharacteristics.

Figure 53: Copy Function for Codes and Code groups

Comprehensive copy function for codes and code groups.

Copying of code groups with their corresponding codes. You can use the Copyas function to copy existing code groups, codes, selected sets, or set codes. Youcan use this function to create new code groups within a catalog, new selectedsets within a plant, new codes within a code group, and new set codes within aselected set.

2006/Q2 © 2006 SAP AG. All rights reserved. 115

Page 126: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

As of Release 4.6C, it is possible to edit catalogs (code groups, selected sets)in Customizing. Catalog tables - like all Customizing tables in QM - have anautomatic transport link.

As of Release 4.6C, it is possible to distribute code groups and the associatedcodes from one source system to one or more target systems using ALE. Thisdistribution can take place automatically in the background, or it can be triggeredusing transaction QL41.

You can also use SAP Note 61049 if you want to transport code groups and codesto all systems and clients.

The catalog profile

Figure 54: Catalog profile

The catalog profile contains a subset of code groups and codes from differentcatalog types.

You can use the catalog profile, for example, to plan which catalogs and codegroups are available to the user, based on the material, when results are recordedand notifications processed.

Hint: The catalog profile can only be defined at the level of the codegroup. You should try to ensure that code groups do not contain too manycodes. By limiting the number of codes, you ensure that you can latercreate suitable catalog profiles for your materials.

116 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 127: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Selected sets and catalog profile

Figure 55: Creating a Catalog Profile (1)

You can define one or more catalog profiles in Customizing for NotificationCreation (Notification Contents).

You can also define catalog profiles using the menu(SAP Menu→ Logistics→Quality Management→ Quality Notification→ Catalog→ Catalog Profile(OQN6)).

Figure 56: Creating a Catalog Profile (2)

You can make generic entries using �*�.

� Example:

Code group XY* in the catalog profile means that all code groups that beginwith XY can be chosen.

The masking symbol is the �+� symbol. The masking symbol stands for anysymbol.

2006/Q2 © 2006 SAP AG. All rights reserved. 117

Page 128: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Figure 57: Entry in a Catalog Profile

You can define a catalog profile for a material, a notification type and also fora report type.

The catalog profile specifies which code groups can be used for a certain material,notification type, or report type.

The notification type specifies the assignment of the catalog types to theappropriate object in the notification (for example, defect).

When processing notifications, you can manually change the catalog profile (thesystem usually proposes the catalog profile for the material; however, you can alsochoose the catalog profile for the notification type or an individual catalog profile).

118 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 129: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Selected sets and catalog profile

Exercise 7: Selected Sets and Codes ofSelected Sets

Exercise ObjectivesAfter completing this exercise, you will be able to:� Edit selected sets and codes of selected sets.

Business ExampleYou want to valuate certain qualitative inspection characteristics using thecharacteristic attribute. You define code groups and codes and create suitableselected sets for characteristic valuation, so that you can valuate characteristics inthe whole company according to the same specifications.

Task 1: Edit selected setsCreate selected sets and codes in selected sets for catalog type 1.

1. You can use selected sets to valuate qualitative characteristics. The selectedsets contain codes from code groups with a valuation. This means that itis defined in the selected set, whether a certain code is maintained for theacceptance or rejection of the characteristic.

Create selected set AW01-## in plant 1000. The selected set should be usedfor inspecting the packaging materials for lamps and should contain all codesfrom code group CG01-##. Also copy all codes from the Other valuationcode selected set to selected set AW01-##.

Task 2: Use selected sets for the inspectioncharacteristicsFor qualitative inspection characteristics, the codes from a selected set maybe relevant for results recording. If, in results recording, you want to recordthe characteristic attribute and not the nonconforming units, you must set theinspection characteristic accordingly.

1. You want to use the specifications from selected set AW01-##. to recordthe results for master inspection characteristic MK01-##. To do this, youmust change the control indicators for the master inspection characteristicMK01-##.

Which control indicator do you have to set?

Control indicators:

____________________________________________

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 119

Page 130: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

What other changes do you have to make?

____________________________________________

120 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 131: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Selected sets and catalog profile

Solution 7: Selected Sets and Codes ofSelected SetsTask 1: Edit selected setsCreate selected sets and codes in selected sets for catalog type 1.

1. You can use selected sets to valuate qualitative characteristics. The selectedsets contain codes from code groups with a valuation. This means that itis defined in the selected set, whether a certain code is maintained for theacceptance or rejection of the characteristic.

Create selected set AW01-## in plant 1000. The selected set should be usedfor inspecting the packaging materials for lamps and should contain all codesfrom code group CG01-##. Also copy all codes from the Other valuationcode selected set to selected set AW01-##.

a) Logistics→ Quality Management→ Quality Planning→ Basic Data→ Catalog→ Selected Set→ Edit (QS51)

Enter the following data on the initial screen for editing selected sets:

Field name or data type ValuesCatalog 1Plant 1000Selected set AW01-##

By choosing the Return key, the pushbutton Create/change, or Enter,the Change Selected Set screen appears. Enter a description for yourselected set in the short text field. To use the selected set, you must setthe status Released.

Select the line with your selected set AW01-##. In the dialog structure,double-click on Codes of selected sets. The Change Codes of SelectedSets view appears. On this overview screen, no codes have beenentered yet for selected set AW01-##. Choose the F5 function key orthe pushbutton New entries. On this screen, you can enter the requiredcode groups and codes with their valuation.

Copy your code group CG01-## to the selected set AW01-##. To dothis, place the cursor in the Code group field and on the applicationtoolbar choose Code groups. The initial screen for displaying the codegroup index appears. If you do not restrict the selection on this screen,the system displays all code groups and codes for catalog type 1 afteryou choose Index or F5.

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 121

Page 132: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Select the line containing code group CG01-## if you want to transferall codes from this code group. You can also select individual lines withthe required codes to transfer only those codes to the selected set.

Then press F6 or choose Copy. The code group and codes are onlysaved temporarily, and the screen for maintaining set codes appears.On this screen, you can use F4 to add the code group.

In the selected set, you can valuate the code using the input help. Ifyou valuate codes with Rejected, you must also specify a defect class.To do so, use the F4 help to select from the predefined defect classes.

Hint: You can also use F4 help to transfer other entries toyour selected set.

If you place the cursor in the Code Group field, you can use theF4 help to select the required codes from the different codegroups (catalog type 1) and transfer them.

If you place the cursor in the Code field, you can use the F4help to select one required codes and transfer it.

Copy the Other valuation code selected set to selected set AW01-##.To do so, place the cursor in the Code group field and on the applicationtoolbar choose Selected Sets. The initial screen for displaying theselected set index appears. Only enter plant 1000 on this selectionscreen. After you use the pushbutton Index or the F5 function key, allselected sets of catalog type 1 in plant 1000 are displayed.

Select the line with the Other valuation codes selected set if you wantto transfer all codes of the selected set. Select the row with one codefrom the selected set to transfer only certain codes of the selected set.

Then press F6 or choose Copy. The selected set is only savedtemporarily and the screen for maintaining set codes appears. On thisscreen, you can use F4 to add the selected set. The valuations of thecodes are copied and can be changed if required.

Save your entries.

Continued on next page

122 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 133: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Selected sets and catalog profile

Task 2: Use selected sets for the inspectioncharacteristicsFor qualitative inspection characteristics, the codes from a selected set maybe relevant for results recording. If, in results recording, you want to recordthe characteristic attribute and not the nonconforming units, you must set theinspection characteristic accordingly.

1. You want to use the specifications from selected set AW01-##. to recordthe results for master inspection characteristic MK01-##. To do this, youmust change the control indicators for the master inspection characteristicMK01-##.

Which control indicator do you have to set?

Control indicators:

____________________________________________

What other changes do you have to make?

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 123

Page 134: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

____________________________________________

a) Logistics→ Quality Management→ Quality Planning→ Basic Data→ Inspection Characteristic→ Change (QS23)

Enter the following data on the initial screen for changing the masterinspection characteristic version:

Field name or data type ValuesPlant 1000Master Inspection Characteristic MK01-##

By choosing the Return key, the pushbutton Master inspectioncharacteristic, or Enter, the view Change Master InspectionCharacteristic Version: General Data appears. Choose the pushbuttonControl indicators�, and set the indicator Charac. attribute� in theType� screen area. You use this indicator to specify that you referto codes for a selected set during results recording. After choosingthe Return key, the second screen of control indicators appears. Youleave this screen also by using the Return key. The screen Assignedinspection catalogs then appears automatically. You can enter theselected set AW01-## used for the valuation of the characteristicmanually in the field CGr/SSet or with a single click using the inputhelp from the displayed overview. Exit the Assigned inspectioncatalogs screen using the Return key and save your entries.

Hint: If defects are detected during the inspection, you shouldselect the defect codes manually. Therefore, you do not have toassign defect codes to the master inspection characteristic.

Confirm your info messages by choosing ENTER.

124 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 135: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Selected sets and catalog profile

Lesson Summary

You should now be able to:� Describe the structure of a selected set.� Explain how selected sets can be used in inspection planning.

2006/Q2 © 2006 SAP AG. All rights reserved. 125

Page 136: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Lesson: Inspection method

Lesson OverviewYou can describe the procedure and execution of an inspection in an inspectionmethod. In this lesson, you will learn about the structure and processing ofinspection methods.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Describe the possible uses of inspection methods.� Explain inspection planning using inspection methods.

Business ExampleParticular inspection characteristics are inspected according to differentprocedures. Inspection methods are used to take these specifications intoconsideration in inspection planning. It is also necessary to link documents withthe inspection methods.

Structure and Use of Inspection Methods

Figure 58: Inspection Method: General

An inspection method describes how the inspection is to be carried out for aninspection characteristic.

126 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 137: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection method

You can assign several inspection methods to a master inspection characteristic.When the master inspection characteristic is included in the task list, a particularinspection method is selected for the characteristic in the task list. There is a1:1 assignment between the master inspection characteristic and the inspectionmethod in the task list.

Only one inspection method can be assigned to a task list characteristic (aninspection characteristic that is created in the task list).

Figure 59: Creating an Inspection Method

When you create an inspection method, the status Being created is proposed. Tobe able to use the inspection method, the status must be set to Released.

As of mySAP ERP 2005 (ECC 6.0), as well as using the short text and search fieldto search, you can also use an extended search function for inspection methods.The inspection methods are connected to the SAP search engine TREX. Youcan find the corresponding settings in Customizing under SAP NetWeaver ->Application Server -> System administration -> Search Engine Service.

You can make changes to inspection methods with and without history. Thissetting is made in Customizing at plant level.

2006/Q2 © 2006 SAP AG. All rights reserved. 127

Page 138: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Figure 60: Inspection Method: Document Assignment

You can assign documents from the document management system (DMS) to aninspection method (for example, drawings or word documents). The assignment isperformed at the version level of the inspection method. Therefore, you can assigndifferent documents to the inspection method for various validity statuses.

When actively managing versions for the inspection method, you can changedocument assignments simultaneously.

You call up the document assignment and the assigned document in the inspectionmethod display simultaneously.

If you want to assign a document to a specific document type of an inspectionmethod, the document type must be assigned to the object QMTBDOC inCustomizing for document management (Quality Management→ Environment→ Central Functions→ Define Document Types).

It is possible to link to documents on the Web. To do this, the URL must be storedvia the Document Management System (DMS).

The URL is entered in the document master record on the Originals tab pageusing the Details pushbutton.

128 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 139: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection method

Figure 61: Assigning an Inspection Method to a Master InspectionCharacteristic

When you assign the inspection methods to the master inspection characteristics,only inspection methods with a validity date that corresponds to the masterinspection characteristic are proposed. This is valid for master inspectioncharacteristics that are not yet used in task lists.

Valid, released inspection methods from another plant can also be assigned to amaster inspection characteristic.

You can also assign the inspection method to task list characteristics.

2006/Q2 © 2006 SAP AG. All rights reserved. 129

Page 140: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Figure 62: Assigning Catalogs to a Master Inspection Characteristic

Direct assignment of catalogs is called method-independent assignment.

Indirect assignment of catalogs via inspection methods is calledmethod-dependent assignment.

Method-dependent assignment refers to the use of inspection characteristics intask lists. For material specifications, only method-dependent assignment is used.

Method-dependent assignment has priority over method-independent assignment.

130 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 141: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection method

Lesson Summary

You should now be able to:� Describe the possible uses of inspection methods.� Explain inspection planning using inspection methods.

2006/Q2 © 2006 SAP AG. All rights reserved. 131

Page 142: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Lesson: Distributing QM Basic Data

Lesson OverviewIn this lesson, you will be given a brief overview of the options for distributingQM basic data to different systems. You will learn which technical requirementsare necessary for distribution and how distribution can be carried out.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Distribute certain QM basic data to other systems.� Describe the different distribution processes.

Business ExampleA central system is used in QM for master data maintenance. If new master data iscreated, it is to be distributed automatically to different systems.

Distribution of QM Basic Data Using ALE

Figure 63: ALE Technology - Basic Concepts

ALE supports the configuration and running of distributed applications. It allowsthe controlled exchange of business messages between distributed applicationswith consistent data retention. The coupling between distributed applicationsystems can be either loose or narrow.

132 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 143: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Distributing QM Basic Data

The application integration is not achieved using a centralized database. Instead,the applications access a local database. Data retention is redundant. ALE ensuresthe distribution and synchronization of master, control, and transaction data usingasynchronous communications. ALE uses synchronous connections to read data.

The use of ALE offers a number of advantages:

� Distribution of application data between SAP systems� Customer-specific enhancements

Figure 64: Data Flow Between SAP Systems Using ALE

Technical ALE settings are usually made for multiple SAP system modules, notjust for the QM module. For more information about ALE distribution, see thegeneral documentation for ALE, particularly the ALE Implementation Guide.

Check that the general settings for the distribution of QM basic data have beenmade. These settings are required for both the initial distribution and the changedistribution.

For more information about ALE, see SAP Help Portal (http://help.sap.com) onIDOC interface/ALE.

2006/Q2 © 2006 SAP AG. All rights reserved. 133

Page 144: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Figure 65: Distributing QM Basic Data

From Release 4.6C, it is possible to distribute inspection methods, masterinspection characteristics, and code groups and the associated codes from onesource system to one or more target systems using ALE.

The following three objects can be distributed using a transaction. The newtransactions are:

� QL31 for inspection method distribution� QL21 for master inspection characteristic distribution� QL41 for code group distribution

Distribution of changes to master data can also be triggered automatically inthe background from the relevant change transactions if this function has beenactivated in Customizing (QM→ Basic Settings→ Maintain Settings at ClientLevel).

You can find further information in Customizing under QM→ Environment→Tools→ Distribute ALE Master Data.

You can use transaction QL11 to distribute material inspection settings.

134 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 145: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Distributing QM Basic Data

Lesson Summary

You should now be able to:� Distribute certain QM basic data to other systems.� Describe the different distribution processes.

2006/Q2 © 2006 SAP AG. All rights reserved. 135

Page 146: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Lesson: Material Specification

Lesson OverviewSimple inspection specifications for materials can also be represented in thesystem using a material specification. This is an easy way of fulfilling therequirement for inspection results recording.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Explain the structure of the material specification.� Describe the possible uses of the material specification.

Business ExampleFor particular materials, simple inspection specifications are to be implementedusing a material specification. For other materials, the material specification is tosupplement the specifications from an inspection plan.

Structure and Use of Material Specifications

Figure 66: Creating a Material Specification

From Release 4.5A, a time reference is available for the material specification.Changes can be planned for a specific date. The planned changes can be activatedmanually or using a job.

136 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 147: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Material Specification

You assign the required master inspection characteristics to the material in thematerial specification. In addition, you can plan a results data origin (for example,data from mobile results recording) for the characteristics. You can define aninternal characteristic ID for the quality data exchange in the material specificationor in the master inspection characteristic.

The maintenance interface for the material specification has been switched to tablecontrol. You can now view data in the table control that was previously onlyavailable on the detail screen.

The Undo reference function is also available for qualitative master inspectioncharacteristics that reference a selected set. In this way, another selected set canbe defined with reference to a material other than the one defined in the masterinspection characteristic.

Figure 67: Using a Material Specification

The default settings for the operation numbers for an inspection using a materialspecification are made in Customizing for each inspection type.

When the inspection lot is created, the material specification is copied to theinspection lot.

2006/Q2 © 2006 SAP AG. All rights reserved. 137

Page 148: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Figure 68: Master Data and Material Specification

The material specification can be used for a basic quality inspection with plannedinspection characteristics.

The material specification is integrated into the product structure (transactionCC04).

If you create a material specification, you use existing basic data from QM(for example, the sampling procedure, selected sets, code groups, and masterinspection characteristics).

The material specification is valid for all clients.

You cannot assign work centers or production resources/tools in the materialspecification.

Dynamic modification of the inspection scope is not possible when a materialspecification is used.

If you want to perform a quality inspection in various operations or use aproduction resource/tool, you must use a task list.

138 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 149: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Material Specification

Exercise 8: Material Specification

Exercise ObjectivesAfter completing this exercise, you will be able to:� Edit material specifications using QM master data� Use the material specification for a simple inspection.

Business ExampleIn your company, you want to change the inspection of certain materials with onlydefects recording to a planned inspection with inspection characteristics. You usethe material specification the first time the planned inspection is performed.

Task 1: Create a Material SpecificationFor simplified inspection processes, you can plan the inspection specificationsin the material specification.

1. Create a material specification for material T-BQ1##. Use both masterinspection characteristics MK01-## and MK02-## in plant 1000. Samplingprocedure SP01-## should be used for master inspection characteristicMK01-## during sample determination. Sampling procedure SP03-## shouldbe used for master inspection characteristic MK02-##.

Task 2: Change the inspection setup in the materialmasterThe current settings for the inspection type in the material master are always takeninto consideration at the inspection lot creation. To ensure that the inspectionspecifications from the material specification in the inspection lot are copied atthe next inspection lot creation in training course PLM412, you must change theinspection setup in the material master.

1. You must change the material master record for material T-BQ1##, so thatthe inspection specifications from the material specification can be usedfor the inspection. In the future, all inspection lots of inspection type 05should be created for this material with the specifications from the materialspecification. Make the necessary changes to the material master record.

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 139

Page 150: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Task 3: Create a manual inspection lotA manual inspection lot is required for a follow-on inspection in materialT-BQ1##.

1. Create the manual inspection lot. The inspection lot origin is 05(Miscellaneous goods movement) and the inspection type is 05. Theinspection lot quantity is 500 pieces.

For the description in the Short text field, also enter the text Group ##.

Save the inspection lot.

Display the inspection lot and make a note of the following data:Inspection lot number: __________________________________System status: __________________________________Sample size: __________________________________

Hint: You can also display the inspection lot using your list offavorites.

140 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 151: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Material Specification

Solution 8: Material SpecificationTask 1: Create a Material SpecificationFor simplified inspection processes, you can plan the inspection specificationsin the material specification.

1. Create a material specification for material T-BQ1##. Use both masterinspection characteristics MK01-## and MK02-## in plant 1000. Samplingprocedure SP01-## should be used for master inspection characteristicMK01-## during sample determination. Sampling procedure SP03-## shouldbe used for master inspection characteristic MK02-##.

a) Logistics→ Quality Management→ Quality Planning→ InspectionPlanning→ Material Specification→ Edit (QS61)

The initial screen for editing a material specification appears.

Field name or data type ValuesMaterial T-BQ1##

Choose the Return key, the Enter or Characteristics pushbutton, orthe F5 function key to open the Maintain Material Specification:Characteristic Assignment screen.

Field name or data type ValuesPlant 1000Master inspection characteristic MK01-##Master inspection characteristic MK02-##

Hint: You must specify the plant so that the correct masterinspection characteristic is found. The material specificationcan be used for the complete client.

You can either enter the identifier for the master inspectioncharacteristics directly in the field or use the input help todisplay a list of master inspection characteristics. If you usethe input help, you should limit the selection by entering plant1000 and group ##.

After you have entered the first master inspection characteristic, youcan open another line for a characteristic using the pushbutton NewCharacteristic and enter your second master inspection characteristic.

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 141

Page 152: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Field name or data type ValuesPlant 1000Master inspection characteristic MK02-##

Sample determination should be performed for both master inspectioncharacteristics in accordance with the control indicators using asampling procedure. The suitable sampling procedure is assigned to themaster inspection characteristic in the material specification.

To do this, select both lines in the characteristic assignment and choosethe Detail button in the application toolbar that is displayed below thecharacteristic assignments. The Values screen appears and you canenter the required data for your first master inspection characteristic.

Field name or data type ValuesSampling Procedure SP01-##Sample unit PC

You use the pushbutton Next page to access the Values screen for thesecond master inspection characteristic and enter the required data:

Field name or data type ValuesSampling Procedure SP03-##Sample unit PC

Choose the Return key. The screen for the characteristic assignment ofthe material specification appears again. Save your entries.

Hint: The master inspection characteristic MK01-## iscreated as a reference characteristic. As a result, you cannotmake changes to the selected set for the master inspectioncharacteristic in the Values screen. The master inspectioncharacteristic MK02-## is created as a complete copy model.For this master inspection characteristic, you can changethe quantitative data on the Values screen after you link thecharacteristic to the material specification.

Save the material specification.

Continued on next page

142 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 153: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Material Specification

Task 2: Change the inspection setup in the materialmasterThe current settings for the inspection type in the material master are always takeninto consideration at the inspection lot creation. To ensure that the inspectionspecifications from the material specification in the inspection lot are copied atthe next inspection lot creation in training course PLM412, you must change theinspection setup in the material master.

1. You must change the material master record for material T-BQ1##, so thatthe inspection specifications from the material specification can be usedfor the inspection. In the future, all inspection lots of inspection type 05should be created for this material with the specifications from the materialspecification. Make the necessary changes to the material master record.

a) Logistics→ Quality Management→ Quality Planning→ LogisticsMaster Data→ Material→ Change (MM02)

The screen Change Material (Initial Screen) appears. Enter materialT-BQ1## and continue by using the return key, Enter, or the pushbuttonSelect view(s).

Field name or data type ValuesMaterial T-BQ1##

Select the Quality Management view in the Select View(s) dialog boxand use the Return key or the pushbutton Organizational levels toexit this dialog box. Enter plant 1000 on the next screen and exit thescreen using the Return key.

The Quality Management view of the material master appears formaterial T-BQ1##. You must change the inspection setup for thematerial so that the inspection specifications from the materialspecification are used in the future. Choose the pushbutton Inspectionsetup. The screen appears on which you can see the available inspectiontypes for this material. Make the following changes to the detailedinformation for inspection type 05:

Field name or data type ValuesInsp. with spec. Set indicatorAuto. assignment Set indicatorInsp. by charac. Set indicatorInspection percentage Delete entry 5Dyn. mod. rule Delete A##

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 143

Page 154: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Exit the inspection setup by choosing the Return key, and save yourentries.

Task 3: Create a manual inspection lotA manual inspection lot is required for a follow-on inspection in materialT-BQ1##.

1. Create the manual inspection lot. The inspection lot origin is 05(Miscellaneous goods movement) and the inspection type is 05. Theinspection lot quantity is 500 pieces.

For the description in the Short text field, also enter the text Group ##.

Save the inspection lot.

Display the inspection lot and make a note of the following data:Inspection lot number: __________________________________System status: __________________________________Sample size: __________________________________

Hint: You can also display the inspection lot using your list offavorites.

a) Logistics→ Quality Management→ Quality Inspection→ InspectionLot→ Processing→ Create (QA01)

Enter the following data on the initial screen:

Field name or data type ValuesMaterial T-BQ1##Plant 1000Inspection lot origin 05

You can access the detail data for the inspection lot by choosing Enter.

Field name or data type ValuesInsp. lot quantity 500Short text Group ##

Choose the Return key to release the data. Save your entries.

Display your manually created inspection lot:

Continued on next page

144 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 155: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Material Specification

Logistics→ Quality Management→ Quality Inspection→ InspectionLot→ Processing→ Display (QA03)

The number of the inspection lot that was last created is displayed in thefield Inspection lot. By choosing Enter, the screen Display inspectionlot appears. The following data is displayed on this screen:

Field name or data type ValuesInspection lot 50000000 .......System status REL CALC

Insp. lot quantitiesSample size 50 PC

2006/Q2 © 2006 SAP AG. All rights reserved. 145

Page 156: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

Lesson Summary

You should now be able to:� Explain the structure of the material specification.� Describe the possible uses of the material specification.

146 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 157: Plm412 en Col62 Fv Part a4

PLM412 Unit Summary

Unit SummaryYou should now be able to:� Describe the inspection settings in the material master.� Explain Customizing for the inspection settings.� Explain the master data for sample determination.� Describe the tasks of the sampling procedure.� Describe the structure of the modification rule.� Explain how to use dynamic modification.� Describe the mass maintenance options for the inspection setup.� Use mass maintenance for an inspection setup that is already active.� Describe the structure of master inspection characteristics.� Explain the options for using master inspection characteristics.� Explain the functions of input processing for measured values.� Describe how these functions can be used.� Describe the structure of coding.� Describe how the different catalog types can be used.� Describe the structure of a selected set.� Explain how selected sets can be used in inspection planning.� Describe the possible uses of inspection methods.� Explain inspection planning using inspection methods.� Distribute certain QM basic data to other systems.� Describe the different distribution processes.� Explain the structure of the material specification.� Describe the possible uses of the material specification.

2006/Q2 © 2006 SAP AG. All rights reserved. 147

Page 158: Plm412 en Col62 Fv Part a4

Unit Summary PLM412

148 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 159: Plm412 en Col62 Fv Part a4

PLM412 Test Your Knowledge

Test Your Knowledge

1. Several inspection types can be active in materials.Determine whether this statement is true or false.□ True□ False

2. You can create your own inspection lot origins in Customizing.Determine whether this statement is true or false.□ True□ False

3. The Customizing settings for an inspection type cannot be changed in thematerial.Determine whether this statement is true or false.□ True□ False

4. Sample determination takes place according to the specifications in thesampling procedure.Determine whether this statement is true or false.□ True□ False

5. The sampling procedure can also ensure automatic valuation of theinspection characteristic.Determine whether this statement is true or false.□ True□ False

6. Using the sampling scheme, you can define a sample size that is dependenton the lot-size.Determine whether this statement is true or false.□ True□ False

2006/Q2 © 2006 SAP AG. All rights reserved. 149

Page 160: Plm412 en Col62 Fv Part a4

Test Your Knowledge PLM412

7. A dynamic modification rule can always only be used in conjunction witha sampling scheme.Determine whether this statement is true or false.□ True□ False

8. For each inspection stage, the specifications for the inspection stage changeare defined in the dynamic modification rule.Determine whether this statement is true or false.□ True□ False

9. Dynamic modification criteria can be defined in the task list header.Determine whether this statement is true or false.□ True□ False

10. The following changes can be made using mass maintenance for theinspection setup.Choose the correct answer(s).□ A Assignment and activation of a new inspection type in the

selected materials.□ B Deletion of an inspection type from the selected materials.□ C Mass change of an assigned inspection type.□ D Create QM view for the selected materials.

11. If inspection stock already exists for a material, a stock-relevant inspectiontype can be assigned and activated in the material.Determine whether this statement is true or false.□ True□ False

12. Change documents are created during mass maintenance of the inspectionsetup.Determine whether this statement is true or false.□ True□ False

150 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 161: Plm412 en Col62 Fv Part a4

PLM412 Test Your Knowledge

13. Master inspection characteristics can be referenced in task lists. Centralmaintenance is then possible.Determine whether this statement is true or false.□ True□ False

14. History management is not possible for master inspection characteristics.Determine whether this statement is true or false.□ True□ False

15. Master inspection characteristics that are created as an �incomplete copymodel� can only be used in task lists.Determine whether this statement is true or false.□ True□ False

16. Input processing for measured values is possible for all inspectioncharacteristics.Determine whether this statement is true or false.□ True□ False

17. Input processing for measured values cannot be used for a calculationaccording to a formula.Determine whether this statement is true or false.□ True□ False

18. The parameters for input processing are defined in Customizing.Determine whether this statement is true or false.□ True□ False

19. You can create your own code groups and codes within a catalog type.Determine whether this statement is true or false.□ True□ False

2006/Q2 © 2006 SAP AG. All rights reserved. 151

Page 162: Plm412 en Col62 Fv Part a4

Test Your Knowledge PLM412

20. Which of the following applies to code groups and codes?Choose the correct answer(s).□ A Distribution using ALE is possible.□ B Code groups and codes cannot be processed in Customizing.□ C The short text and long text can be created in several languages.□ D Code groups and codes can be copied across catalogs.

21. Coding is numeric only.Determine whether this statement is true or false.□ True□ False

22. Codes can be valuated in selected sets.Determine whether this statement is true or false.□ True□ False

23. Code groups and codes from one catalog type can be grouped together inselected sets.Determine whether this statement is true or false.□ True□ False

24. Codes from selected sets can be used for results recording.Determine whether this statement is true or false.□ True□ False

25. An inspection method can also be directly created in a task list.Determine whether this statement is true or false.□ True□ False

26. No code groups from catalogs can be assigned to an inspection method.Determine whether this statement is true or false.□ True□ False

152 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 163: Plm412 en Col62 Fv Part a4

PLM412 Test Your Knowledge

27. Documents can be assigned to an inspection method.Determine whether this statement is true or false.□ True□ False

28. The distribution of QM basic data can take place automatically according tothe distribution model.Determine whether this statement is true or false.□ True□ False

29. No inspection settings can be distributed.Determine whether this statement is true or false.□ True□ False

30. Using ALE, inspection plans can also be distributed in the standard system.Determine whether this statement is true or false.□ True□ False

31. Inspection characteristics can also be created in the material specification.Determine whether this statement is true or false.□ True□ False

32. The material specification is not integrated in the product structureDetermine whether this statement is true or false.□ True□ False

2006/Q2 © 2006 SAP AG. All rights reserved. 153

Page 164: Plm412 en Col62 Fv Part a4

Test Your Knowledge PLM412

Answers

1. Several inspection types can be active in materials.

Answer: True

An inspection can be required for a material, for example, at goods receiptand stock transfer. This is achieved by using two active inspection types.

2. You can create your own inspection lot origins in Customizing.

Answer: False

Inspection lot origins are predefined and cannot be changed. You can createyour own inspection type in Customizing and assign it to a predefinedinspection lot origin.

3. The Customizing settings for an inspection type cannot be changed in thematerial.

Answer: False

Default values are entered in Customizing for an inspection type. Thesedefault values can be changed in the inspection settings in the material.

4. Sample determination takes place according to the specifications in thesampling procedure.

Answer: True

The sampling procedure can be assigned in the inspection setup in thematerial or at the inspection characteristic.

5. The sampling procedure can also ensure automatic valuation of theinspection characteristic.

Answer: True

The valuation mode in the sampling procedure determines whether theinspection characteristic is valuated automatically or manually.

154 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 165: Plm412 en Col62 Fv Part a4

PLM412 Test Your Knowledge

6. Using the sampling scheme, you can define a sample size that is dependenton the lot-size.

Answer: True

A sampling scheme can contain several sampling tables in which the samplesize and the acceptance and rejection number are entered dependent on thelot size.

7. A dynamic modification rule can always only be used in conjunction witha sampling scheme.

Answer: False

A dynamic modification rule can also be used in conjunction with a samplingprocedure that does not contain a sampling scheme.

8. For each inspection stage, the specifications for the inspection stage changeare defined in the dynamic modification rule.

Answer: True

The specifications for the case �OK� and the case �Not OK� are stored foreach inspection stage. This also applies to the SKIP stage.

9. Dynamic modification criteria can be defined in the task list header.

Answer: True

Depending on the setting in the task list header, the update of the Q-leveltakes place, for example, with relation to the material or to the material /vendor.

10. The following changes can be made using mass maintenance for theinspection setup.

Answer: A, C

Mass maintenance for the inspection setup (transaction QA08) providesthe following options: activate inspection type, deactivate inspection type,individual processing, mass processing.

2006/Q2 © 2006 SAP AG. All rights reserved. 155

Page 166: Plm412 en Col62 Fv Part a4

Test Your Knowledge PLM412

11. If inspection stock already exists for a material, a stock-relevant inspectiontype can be assigned and activated in the material.

Answer: False

Assignment and activation is not possible via a material change (transactionMM02). It is, however, possible via mass maintenance of the inspectionsetup (transaction QA08).

12. Change documents are created during mass maintenance of the inspectionsetup.

Answer: True

If changes documents are not required, you can deactivate them using anindicator on the initial screen for mass maintenance.

13. Master inspection characteristics can be referenced in task lists. Centralmaintenance is then possible.

Answer: True

If you create master inspection characteristics as �reference characteristics�,you can reference them in task lists and, consequently, maintain themcentrally, if required.

14. History management is not possible for master inspection characteristics.

Answer: False

In Customizing, you can set up history management for master inspectioncharacteristics at plant level. If history management is active, a new versionis created when a released master inspection characteristic is changed.

15. Master inspection characteristics that are created as an �incomplete copymodel� can only be used in task lists.

Answer: True

If you also want to use master inspection characteristics in a materialspecification, you must create them as �reference characteristics� or as�incomplete copy models�.

156 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 167: Plm412 en Col62 Fv Part a4

PLM412 Test Your Knowledge

16. Input processing for measured values is possible for all inspectioncharacteristics.

Answer: False

Input processing for measured values can only be used for quantitativeinspection characteristics.

17. Input processing for measured values cannot be used for a calculationaccording to a formula.

Answer: False

By using input processing for measured values, the �original value� can alsobe used in a formula. In addition to the result (valuation of the formula), theoriginal value is also saved in results recording.

18. The parameters for input processing are defined in Customizing.

Answer: True

The corresponding specifications are stored in Customizing for resultsrecording.

19. You can create your own code groups and codes within a catalog type.

Answer: True

To structure the coding, similar codes and code groups can be groupedtogether.

20. Which of the following applies to code groups and codes?

Answer: A, C

Catalog processing can also be carried out in Customizing. You can onlycopy within one catalog type. Multilingual capability and distribution usingALE is possible.

21. Coding is numeric only.

Answer: False

Coding can be alphanumeric. There is a maximum of 8 characters for codegroups and a maximum of 4 characters for codes.

2006/Q2 © 2006 SAP AG. All rights reserved. 157

Page 168: Plm412 en Col62 Fv Part a4

Test Your Knowledge PLM412

22. Codes can be valuated in selected sets.

Answer: True

Valuation is obligatory for the codes in the selected sets for catalog type1 and catalog type 3.

23. Code groups and codes from one catalog type can be grouped together inselected sets.

Answer: True

If code groups from different catalog types have to be grouped together, acatalog profile can be used.

24. Codes from selected sets can be used for results recording.

Answer: True

The codes from the selected sets are used in results recording for qualitativeinspections characteristics with the control indicator �CharacteristicAttribute�.

25. An inspection method can also be directly created in a task list.

Answer: False

Inspection methods are always created as separate data records and thenlinked to a master inspection characteristic or assigned to a characteristicin the task list.

26. No code groups from catalogs can be assigned to an inspection method.

Answer: False

Code groups from catalogs can also be assigned using an inspection method.This is called method-dependent assignment. Method-dependent assignmenthas priority over method-independent assignment.

27. Documents can be assigned to an inspection method.

Answer: True

It is possible to assign documents that are stored using the documentmanagement system (DMS). The assigned documents can be displayed inresults recording.

158 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 169: Plm412 en Col62 Fv Part a4

PLM412 Test Your Knowledge

28. The distribution of QM basic data can take place automatically according tothe distribution model.

Answer: True

If you have created a distribution model in Customizing, automaticdistribution to the target systems can take place. Manual distribution is alsopossible using the corresponding transactions.

29. No inspection settings can be distributed.

Answer: False

Inspection settings in materials can be distributed. You can use transactionQL11 to do this.

30. Using ALE, inspection plans can also be distributed in the standard system.

Answer: False

It is currently not possible to distribute inspection plans in the standardsystem.

31. Inspection characteristics can also be created in the material specification.

Answer: False

In the material specification, only master inspection characteristics with theattribute �Reference characteristic� or �Complete copy model� can be used.

32. The material specification is not integrated in the product structure

Answer: False

In the product structure (transaction CC04), the material specification is alsodisplayed in addition to the task lists.

2006/Q2 © 2006 SAP AG. All rights reserved. 159

Page 170: Plm412 en Col62 Fv Part a4

Unit 2: Basic Data in Quality Management PLM412

160 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 171: Plm412 en Col62 Fv Part a4

Unit 3Inspection Planning

Unit OverviewIn this unit, you will learn about the structure of inspection plans. An exampleis used as a basis for a discussion on inspection plans and to show differentprocessing options. Change management and inspection planning in productionare also dealt with in this unit.

Unit ObjectivesAfter completing this unit, you will be able to:

� Explain the structure of an inspection plan.� Describe the assignment of QM basic data in the inspection plan.� Use test equipment in inspection planning.� Explain the prerequisites for regularly monitoring the test equipment used.� Describe the use of QM basic data at characteristic level in an inspection plan.� Create additional inspection characteristics in inspection plans.� Describe the structure and use of reference operation sets.� Explain the options for the product structure within inspection planning.� Describe the structure and use of the Engineering Workbench.� Use the Engineering Workbench for inspection planning.� Explain how engineering change management can be used in inspection

planning.� Describe the structure of the change master record.� Describe the options for using task lists and material specifications.� Describe the options for the flexible selection of specifications.� Describe the requirements for flexible inspection specifications.� describe the options for using multiple specifications.� use multiple specifications in inspection planning, in the inspection process

and at certificate creation.

2006/Q2 © 2006 SAP AG. All rights reserved. 161

Page 172: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Unit ContentsLesson: The Inspection Plan .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163Lesson: Test Equipment .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171

Exercise 9: Inspection Plan .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177Lesson: Inspection Characteristics in the Inspection Plan ... . . . . . . . . . . . . .183

Exercise 10: Inspection Characteristics in the Inspection Plan .. . . . .193Lesson: Reference Operation Set and Product Structure .. . . . . . . . . . . . . . . .202

Exercise 11: Material-task list assignment and reference operationset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211

Lesson: Engineering Workbench .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220Exercise 12: Engineering Workbench � Optional Exercise .. . . . . . . . . .227

Lesson: Engineering change management .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233Lesson: Task List - Material Specification ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .238Lesson: Flexible Inspection Specifications .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242Lesson: Multiple Specifications - Overview .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248

162 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 173: Plm412 en Col62 Fv Part a4

PLM412 Lesson: The Inspection Plan

Lesson: The Inspection Plan

Lesson OverviewInspection specifications are stored in inspections plans. You will learn aboutstructuring inspection plans and assigning QM basic data in the inspection plan.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Explain the structure of an inspection plan.� Describe the assignment of QM basic data in the inspection plan.

Business ExampleThe specifications for carrying out a quality inspection are stored in inspectionplans. By using QM basic data, identical specifications can be used in severalinspection plans.

QM Basic Data and Inspection Plan Structure

Figure 69: Inspection Plan - General

You use inspection plans to describe how a quality inspection should be processedfor one or more materials. You define in the inspection plan in which orderindividual inspection operations should be performed and which inspectioncharacteristics should be inspected using which inspection specifications.

2006/Q2 © 2006 SAP AG. All rights reserved. 163

Page 174: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

You can create inspection plans for different uses (for example, model inspection,preliminary series inspection, goods issue inspection).

The inspection plan in the Quality Management area is similar to the routing orrate routing in Production Planning. There are only slight differences betweenthese task list types with regard to planning.

Figure 70: QM Basic Data and Inspection Plan Structure

You assign QM specific basic data and other master data to the inspection plan:

� For example, QM specific basic data includes master inspectioncharacteristics, inspection methods, sampling procedures, code groups, andselected sets.

� Other master data includes, for example:

� Material master record (assignment required)� Vendor master record� Customer master record� Change master record

An inspection plan can contain several operations, which reflect the differentinspection stages for the product.

You can assign a work center and production resources/tools to each operation.

Each operation can contain several inspection characteristics.

164 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 175: Plm412 en Col62 Fv Part a4

PLM412 Lesson: The Inspection Plan

Figure 71: inspection plan header

In the inspection plan header, you define data that is valid for the whole inspectionplan.

The task list group is an alphanumeric identifier that is allocated by you or thesystem. You can combine similar inspection plans within a task list group.

An inspection plan is uniquely identified by the task list group and group counter.Within a task list group, each group counter represents exactly one inspectionplan with operations and characteristics.

In a task list group, people are combined who are responsible for processing theinspection plan.

The usage shows where the inspection plan is used, for example, at goods receiptor for a model inspection.

The system uses the material, usage code, plan status, and lot size to automaticallyselect the inspection plan.

If you use the inspection plan in connection with physical samples, you define thecorresponding sampling procedure in the inspection plan header.

2006/Q2 © 2006 SAP AG. All rights reserved. 165

Page 176: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Figure 72: Inspection Plan Operation

The operations describe the individual inspection steps in an inspection plan.

You use the control key to define how an operation is handled. For example,the data in the control key applies during the task list check, when printing shoppapers, and on the initial screen for results recording.

The work center defines where the inspection occurs. You can copy default valuesfrom the work center to the corresponding operation in the inspection plan.

The standard text key acts as a default for the operation description. It makes iteasier to enter data for frequently used descriptions.

You can assign production resources/tools (test equipment) at operation level.This is the test equipment that is needed for an inspection of characteristics withinan operation.

You can assign inspection characteristics to an operation. Hierarchically, theinspection characteristics are found below operation level.

166 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 177: Plm412 en Col62 Fv Part a4

PLM412 Lesson: The Inspection Plan

Work Center in the Inspection Plan

Figure 73: Main Functions of the Work Center

Work centers determine where an operation is to occur.

Work centers contain default values, which are copied to or referenced in theoperations when you create a task list.

Work centers contain costing data that enables you to carry out costing foroperations. As a basis for costing, you must assign the work center to a cost centerfor which activity types and prices are defined. The prerequisite is that you useControlling (mySAP Financials, Controlling). You need the work center data torecord and confirm inspection times for a QM order.

Work centers contain data that is needed for lead time scheduling and capacityplanning.

Hint: Capacity planning is not supported in QM.

The lead time scheduling can be represented in the task list as a diagram.

2006/Q2 © 2006 SAP AG. All rights reserved. 167

Page 178: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Figure 74: Work Center Where-Used List

Work centers are assigned to certain work center categories based on their function.

In the main, the field and screen selection for work centers is controlled by thework center category. In this way, you determine which data is maintained inthe master record for the work center.

Generally, certain work center categories are used for a specific task list usage(routing, network, etc.). However, a definite assignment does not exist.

You can set default values for each work center category and plant in Customizing.The screen sequence can also be set.

168 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 179: Plm412 en Col62 Fv Part a4

PLM412 Lesson: The Inspection Plan

Figure 75: Work Center Data

The work center contains several groups of data that can be defined on differentscreens.

The default values are copied to the task list. You can use the reference indicatorto define whether the default values can be changed in the task list.

In the work center, you can enter the printer that you want to use for theoperation-related output of the inspection instruction.

2006/Q2 © 2006 SAP AG. All rights reserved. 169

Page 180: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Lesson Summary

You should now be able to:� Explain the structure of an inspection plan.� Describe the assignment of QM basic data in the inspection plan.

170 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 181: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Test Equipment

Lesson: Test Equipment

Lesson OverviewTest equipment, such as required measuring devices, can also be planned duringinspection planning. In this lesson, you will learn about the different types oftest equipment that can be used here.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Use test equipment in inspection planning.� Explain the prerequisites for regularly monitoring the test equipment used.

Business ExampleThe required test equipment is taken into consideration during inspection planningand assigned in the inspection plans and routings. In addition, the requirementsare met for regularly inspecting the measuring devices used.

Test Equipment in Inspection Planning

Figure 76: Test Equipment Types in the SAP System

You assign test equipment (production resources/tools) in the task lists (forexample, the inspection plan, the task list, or the maintenance task list) using thefunction for production resources/tools.

2006/Q2 © 2006 SAP AG. All rights reserved. 171

Page 182: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

You can manage test equipment as:

� Materials

Production resources/tools that are maintained in the material master. Thesematerials are considered in materials management (for example, inventorymanagement, procurement).

� Documents

Production resources/tools that are maintained in the document managementsystem (for example, sketches, CAD drawings).

� Other production resource/tool master records

Production resources/tools that are managed as master data (for example,smaller tools). For this, a PRT master record is created that contains basicdata and location data among other things.

� Equipment

Production resources/tools that are maintained in the equipment master andfor which maintenance is specified (for example, gauges, high-quality tools).

Figure 77: Assignment of Production Resources/Tools

The assignment of production resources/tools occurs at operation level. You canassign several production resources/tools to an operation.

You define which of the assigned production resources/tools (test equipment) youuse for a specific inspection characteristic at characteristic level. The prerequisitefor assigning test equipment to a characteristic is that the corresponding controlindicator is set in the inspection characteristic. You can assign the test equipment

172 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 183: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Test Equipment

on the characteristic overview screen of the operation or on the characteristicsingle screen on the tab page General data. You use the F4 input help to displaythe assigned test equipment for selection at operation level.

The PRTs/test equipment are printed on the inspection instruction for thecorresponding characteristic.

The PRTs/ test equipment can be displayed in results recording.

Optional: Planning and Process Flow of CalibrationInspections

Figure 78: Calibration Inspection Planning

Test equipment is created as an equipment master record if it requires regularcalibration.

If you want to copy inspection results from the calibration inspection to ameasuring point for the equipment, a link is required between the QM masterinspection characteristic and the corresponding class characteristic.

You can link inspection characteristics in the form of QM master inspectioncharacteristics or task list characteristics to the maintenance task list. You mustuse master inspection characteristics, if you want to copy inspection results to ameasuring point for equipment.

The maintenance plan links the required master data (for example, equipmenttask list, general maintenance task list) and is used for scheduling the calibrationinspection.

You can also use maintenance strategies to define additional specifications for theprocess flow of the calibration.

2006/Q2 © 2006 SAP AG. All rights reserved. 173

Page 184: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Figure 79: Calibration Inspection Process Flow 1

The scheduling of the maintenance plan normally occurs automatically using abatch program. You can also schedule the maintenance plan manually at any time.

The result of scheduling is a maintenance order. An inspection lot is automaticallycreated for the calibration inspection when this maintenance order is released(inspection lot origin 14). The maintenance order can be created and released inone step.

The test equipment in the maintenance plan is copied to the inspection lot. Thebasis for the calibration inspection are the inspection characteristics defined in theequipment task list or in the general maintenance task list.

174 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 185: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Test Equipment

Figure 80: Calibration Inspection Process Flow 2

You display functional locations or equipment to be inspected in the resultsrecording worklist. You can choose, for example, the inspection lot origin,equipment numbers, or the master inspection characteristics to be inspected asthe selection criteria for the worklist.

Inspection results are recorded for each piece of equipment in the maintenanceplan.

Costs are recorded and capacity load utilization is traced using the maintenanceorder.

Changing the PRT status of the equipment occurs because of a follow-up actionfor the inspection lot usage decision.

If a link exists between a QM master inspection characteristic and a classcharacteristic, the summarized inspection result for the characteristic is copied tothe measurement document for the equipment measuring point.

Depending on the inspection result, you can change the cycle modification factorfor the usage decision as a follow-up action and, in this way, reduce or increase theinspection interval for the equipment.

2006/Q2 © 2006 SAP AG. All rights reserved. 175

Page 186: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

176 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 187: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Test Equipment

Exercise 9: Inspection Plan

Exercise ObjectivesAfter completing this exercise, you will be able to:� Create and edit inspection plans using QM master data and general master

data.� Use production resources/tools in inspection planning.

Business ExampleThe goods receipt inspection for materials is performed in your company using theinspection plan specifications. To do this, you create different inspection plansin the system. You use QM master data, as well as work centers and productionresources/tools for the first step.

Task: Create an inspection planYou need a new inspection plan for the goods receipt inspection of lamps.

1. Create a new task list group with the description Group## for the goodsreceipt inspection in plant 1000 for the materials lamps. Describe the firsttask list in this task list group with the short text GR inspection plan group##. The task list should be released and used for a lot size of up to 10,000 PC.

Create a first inspection operation in your inspection plan. In this inspectionoperation, the packaging of the lamps should be checked. This inspectionis always performed in work center QMWE1-##.

You need a specific production resource/tool (test equipment) for theinspections in this operation. Assign the equipment with the short textHigh-accuracy weighing machine, digital (T-W1##) to the operation.

During the packaging inspection, the packaging material used and the weightof the goods are checked. Use master inspection characteristics MK01-##and MK02-## for this inspection. For sample determination, use samplingprocedure SP01-## for master inspection characteristic MK01-##. Thesample for characteristic MK02-## is determined using sampling procedureFix50. You need the equipment Weighing machine, digital to inspect themaster inspection characteristic MK02-##.

For which master inspection characteristic can you still change the controlindicators?

Master inspection characteristic:

______________________________________________________

Why can you make these changes?Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 177

Page 188: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

______________________________________________________

Hint: A task list group was created in this first step of inspectionplanning. No material has yet been assigned to the inspection plan inthis task list group. Material is assigned to the task list in anotherexercise in training course PLM412.

178 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 189: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Test Equipment

Solution 9: Inspection PlanTask: Create an inspection planYou need a new inspection plan for the goods receipt inspection of lamps.

1. Create a new task list group with the description Group## for the goodsreceipt inspection in plant 1000 for the materials lamps. Describe the firsttask list in this task list group with the short text GR inspection plan group##. The task list should be released and used for a lot size of up to 10,000 PC.

Create a first inspection operation in your inspection plan. In this inspectionoperation, the packaging of the lamps should be checked. This inspectionis always performed in work center QMWE1-##.

You need a specific production resource/tool (test equipment) for theinspections in this operation. Assign the equipment with the short textHigh-accuracy weighing machine, digital (T-W1##) to the operation.

During the packaging inspection, the packaging material used and the weightof the goods are checked. Use master inspection characteristics MK01-##and MK02-## for this inspection. For sample determination, use samplingprocedure SP01-## for master inspection characteristic MK01-##. Thesample for characteristic MK02-## is determined using sampling procedureFix50. You need the equipment Weighing machine, digital to inspect themaster inspection characteristic MK02-##.

For which master inspection characteristic can you still change the controlindicators?

Master inspection characteristic:

______________________________________________________

Why can you make these changes?

______________________________________________________

Hint: A task list group was created in this first step of inspectionplanning. No material has yet been assigned to the inspection plan inthis task list group. Material is assigned to the task list in anotherexercise in training course PLM412.

a) Logistics→ Quality Management→ Quality Planning→ InspectionPlanning→ Inspection Plan→ Create (QP01)

The screen Create Inspection Plan: Initial Screen appears. Enter thefollowing data on this screen:

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 179

Page 190: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Field name or data type ValuesPlant 1000Group Group ##Key Date Today's date

You can access the header details of the inspection plan by choosingEnter or the icon Continue ( ). Enter the description GR inspectionplan group ## for your inspection plan in the short text field next to thefield Group counter. Enter the following additional data on the HeaderDetails screen for the inspection plan:

Field name or data type ValuesUse 5 (Goods receipt)Status 4 [Released (general)]To lot size 10,000 PC

Choose the pushbutton Operations. The operation overview of theinspection plan appears. In the first operation, enter the work centernumber QMWE1-## in the Work center field, and choose Return. Thecontrol keys for the operation and the operation description are copiedfrom the work center because of the settings in the work center.

Since you need a certain production resource/tool in this operation, youmust assign this at operation level.

To do so, select inspection operation 0010 and choose PRT. Thescreen Create Inspection Plan: New PRT Entries appears. Choose thePRT type Equipment by choosing the pushbutton Equipment. You canenter the required equipment in the upper part of the screen. Enter theequipment number T-W1## here, or use the input help and enterthe equipment description Weighing machine, digital or Weighingmachine* on the Equipment by short text tab page. After choosing theReturn key, the equipment number is displayed and can be copied tothe input field for the equipment assignment with a double-click. Exitthe dialog box using the Return key. The Create Inspection Plan: PRTOverview screen appears and you can see the assigned equipment inthe overview. Return to the operation overview for the inspection planusing the F3 function key.

Assign master inspection characteristics to operation 0010.

Select operation 0010 on the operation overview and chooseInspection characteristics. The characteristic overview appears.

Enter the characteristic description MK01-##in the Master inspectionContinued on next page

180 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 191: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Test Equipment

characteristic field and choose Return. The system creates a referenceto the master record for inspection characteristic MK01-## and thenswitches to the entry screen for the sampling procedure. Enter samplingprocedure SP01-## and choose Return. You exit the screen and returnto the characteristic overview. Enter the second master inspectioncharacteristic MK02-## in the Master inspection characteristic field.The system copies this master inspection characteristic to the inspectionplan and again switches to the entry screen for the sampling procedure.Use the sampling procedure Fix50 for this characteristic.

Since you want to use a certain piece of test equipment for inspectingcharacteristic MK02-##, you can assign the equipment assigned atoperation level to the characteristic. To do this, select characteristic 20in the characteristic overview and choose the pushbutton (Generaldata details). Use the input help in the Test equipment field to select thesuitable PRT from the production resources/tools assigned at operationlevel.

Save your entries.

Hint: For master inspection characteristic MK01-##, thecontrol indicator for Automatic Defects Recording was set forthe rejection of a characteristic. You can process the defectsrecording in the dialog with the user or in the background. Aprerequisite for the process in the background is that you assigna defect code for the inspection characteristic.

In this exercise for inspection planning, you must not assign adefect code for the characteristic. The consistency check thatyou carried out in the background before you saved the tasklist recognizes this �defect�.

However, do still save your inspection plan.

You can change the control indicators for characteristic MK02-##,because this characteristic has the attribute Complete copy model inthe master record and can therefore be copied to the inspection plan.You can then change the control indicators in the inspection plan. Incontrast, you cannot make changes to referenced characteristics (forexample, CH01-##)

2006/Q2 © 2006 SAP AG. All rights reserved. 181

Page 192: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Lesson Summary

You should now be able to:� Use test equipment in inspection planning.� Explain the prerequisites for regularly monitoring the test equipment used.

182 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 193: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection Characteristics in the Inspection Plan

Lesson: Inspection Characteristics in the InspectionPlan

Lesson OverviewThe most important QM basic data is used in inspection plans at characteristiclevel. The required inspection characteristics are stored here with thecorresponding specifications, such as tolerance or sample size.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Describe the use of QM basic data at characteristic level in an inspection plan.� Create additional inspection characteristics in inspection plans.

Business ExampleIn addition to master inspection characteristics, additional inspectioncharacteristics are also created in the task lists. These are partly used as dependentcharacteristics or calculated characteristics.

Inspection Characteristics in the Task List

Figure 81: Inspection characteristic

2006/Q2 © 2006 SAP AG. All rights reserved. 183

Page 194: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

You use inspection characteristics to describe what is to be inspected andaccording to which specifications the inspection is to be performed. The inspectioncharacteristics are subordinate to the operation. To standardize the process flow,you can reference or copy master inspection characteristics. You can also copyinspection characteristics from other inspection plans to the current inspectionoperation.

You can use (reference or copy) master inspection characteristics in the inspectionplan. Moreover, you can create inspection characteristics directly in the inspectionplan.

You can create and edit material-dependent, customer-dependent, andvendor-dependent characteristic specifications. These dependent characteristicspecifications take precedence over the characteristic specifications from theinspection characteristic.

You can use the inspection method to define how the inspection for an inspectioncharacteristic is executed. The inspection method must be available in the systemas a master record. It cannot be directly created in the inspection plan.

If the control indicator for the inspection characteristic plans a sampling procedure,assign this at characteristic level in the inspection plan.

On the characteristic overview screen for the inspection operation, you can viewthe QM-specific master data for each characteristic.

You can plan a results data origin for an inspection characteristic in the tasklist. You can use this function, for example, to determine whether an inspectioncharacteristic is to be inspected at goods receipt or whether the results are to becopied from the quality certificate.

You can use partial sample numbers to change the sample size for an inspection lot.The partial sample number is entered in the inspection characteristic in the task list.

184 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 195: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection Characteristics in the Inspection Plan

Figure 82: Usage of Master Inspection Characteristics

The master inspection characteristic is managed as a master record independent ofthe task list.

The master inspection characteristic must be created as a reference characteristicand released, if you want to reference it in a task list. When you reference a masterinspection characteristic, the system automatically chooses the current version ofthe master inspection characteristic. You can block a referenced master inspectioncharacteristic in a task list.

You can only display characteristic texts (short text, long text) in the task listsdependent on the logon language of the user for referenced master inspectioncharacteristics. Once you have unlocked the master inspection characteristic, thetexts are copied to the task list and subsequent changes to the master inspectioncharacteristic are not reflected in the task list.

If you use a master inspection characteristic with the indicator Complete copymodel in a task list, you can immediately adapt the data for the characteristicindividually in the task list (for examples, tolerances). The master inspectioncharacteristic acts as a copy model in this case. You can also copy masterinspection characteristics with the indicator Incomplete copy model to task lists.

The where-used list for master inspection characteristics shows in which task liststhe corresponding master inspection characteristics are used.

2006/Q2 © 2006 SAP AG. All rights reserved. 185

Page 196: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Figure 83: calculated characteristic

If you want to determine inspection results for a quantitative inspectioncharacteristic by calculating inspection results for other quantitative inspectioncharacteristics instead of inspecting the inspection characteristic itself, you can usecalculated characteristics. You define in the control indicator for the inspectioncharacteristic, whether it is a calculated characteristic.

You can only calculate inspection results for inspection characteristics withinan operation.

You define the formula for calculating the calculated characteristic in the task liston the detail screen for the quantitative data of the inspection characteristic. Youcan use mathematical standard functions and numerical values in the formula.

186 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 197: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection Characteristics in the Inspection Plan

Figure 84: Conditional Characteristics

The inspection of conditional characteristics (After acceptance, After rejection)depends on the results of the previous required characteristic within the sameoperation.

You define in the control indicators for the inspection characteristic which attributeapplies to a conditional characteristic.

Figure 85: Catalogs in the Inspection Plan

2006/Q2 © 2006 SAP AG. All rights reserved. 187

Page 198: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

You can assign code groups from various catalogs to the master inspectioncharacteristic. In addition, you can assign inspection methods to the masterinspection characteristic. You can also assign code groups from catalogs toassigned inspection methods.

If code groups are assigned to a master inspection characteristic using inspectionmethods, this is described as an assignment dependent on the method.

If you reference or copy master inspection characteristics in task lists,the method-independent catalog assignment takes precedence over themethod-independent assignment.

You can assign additional code groups from catalogs in the task list to copiedmaster inspection characteristics or inspection characteristics created in the tasklist.

Dynamic Modification in the Task ListYou use dynamic modification rules to vary the inspection scope. You can define adynamic modification rule in the:

� Task list at header level� Task list at characteristic level� Inspection setup of the material master at inspection type level

Figure 86: Dynamic modification in the inspection plan

In the task list header, you define at which level dynamic modification occurs andwhich dynamic modification criteria are used to update the quality level.

188 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 199: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection Characteristics in the Inspection Plan

If you define dynamic modification at lot level, the entry for the correspondingdynamic modification rule is made in the task list header. If you have definedcharacteristic-based dynamic modification and a dynamic modification rule in thetask list header, this is proposed at characteristic level and can be changed onthe characteristic overview screen or in the details for sample determination onthe characteristic detail screen.

Dynamic modification is possible at inspection type level when using task lists.You define the dynamic modification level in the task list header and the dynamicmodification rule in the inspection setup for the inspection type in the materialmaster. When you use the same task list for various inspection types, you canmaintain a quality level for each inspection type.

Dynamic modification is not possible with optional characteristics.

Figure 87: Dynamic Modification at Lot Creation

When you create an inspection lot, the sample is determined on the basis of thequality level.

If the indicator Dynamic modification at lot creation is set in the dynamicmodification rule, the quality level is immediately updated for the currentinspection lot after sample determination. The system automatically assigns thevaluation Accepted and, if necessary, makes a stage change when the lot is OKthat effects the next inspection lot.

When a characteristic is rejected in results recording, the quality level is updatedagain after the usage decision is made and in this case, for the not OK case.

The subsequent change in the quality level has no effect on inspection lots createdin the meantime.

2006/Q2 © 2006 SAP AG. All rights reserved. 189

Page 200: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Figure 88: dynamic modification at usage decision

If you set the indicator Dynamic modification at usage decision in the dynamicmodification rule, the system updates the quality level for the current inspectionlot when the usage decision is made.

When the usage decision is made, the system updates the quality level based ondynamic modification in the usage decision. At this point, the system evaluatesthe conditions for an inspection stage change based on the dynamic modificationrule and, depending on the results of the current inspection, it determines whetheror not the inspection stage change should occur.

Figure 89: QM Master Data - Characteristic Level

190 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 201: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection Characteristics in the Inspection Plan

You can assign several inspection characteristics to each inspection operation.At inspection characteristic level, you define what is to be inspected and whichQM-specific master data is to be used.

You can create where-used lists for specific master records and in this way,display an overview of where these master records are used in task lists, materialspecifications, inspection setup data, and certificate profiles.

� You can create a where-used list for the following QM-specific master data:

� Master Inspection Characteristics� Inspection Methods� code groups� Sampling Procedure� Dynamic modification rules� Test equipment (PRT)

In addition, you can create where-used lists for work centers and referenceoperation sets.

2006/Q2 © 2006 SAP AG. All rights reserved. 191

Page 202: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

192 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 203: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection Characteristics in the Inspection Plan

Exercise 10: Inspection Characteristics inthe Inspection Plan

Exercise ObjectivesAfter completing this exercise, you will be able to:� Enhance inspection plans and create inspection characteristics in an

inspection plan.� Use dynamic modification rules in inspection plans.

Business ExampleSince you want to improve the goods receipt inspection in your company forcertain materials, you enhance the existing inspection plans.

Moreover, you should change the inspection scope that is dependent on the currentquality of the goods. To do this, you use dynamic modification rules.

Task 1: Create an inspection characteristic in theinspection planYou want to enhance the inspection plan that you created in group Group##.

1. Add another inspection operation to your inspection plan in the task listgroup Group##. The inspections for this operation are always performedin work center QMWE2-##. The wattage of the lamps is measured in theinspection operation.

A quantitative inspection characteristic is needed for inspecting the wattage.Create this inspection characteristic with the short text Wattage in operation0020. On the whole, single results must be confirmed for this inspectioncharacteristic. The wattage of the lamps is generally between 20.00and 120.00 watts. Sample determination should occur using a samplingprocedure. The number of units inspected during results recording mustcorrespond to the planned number of units to be inspected. If this inspectioncharacteristic is rejected during results recording, the user should enter aninspection description in the system. The inspection characteristic shouldalways be printed on the inspection instruction.

Make a note of the control indicators for the inspection characteristic.

Type[ ] Lower specif. limit [ [ ] Upper specif. limit[ ] Check target value

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 193

Page 204: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Sample[ ] Sampling procedure [ ] Additive sample[ ] SPC characteristic [ ] Destructive insp.

Results confirmation( ) Summ. recording ( ) Required char.( ) Single result ( ) Optional char.( ) No charac. rec. ( ) After accept.( ) Classed recording ( ) After rejection[ ] Autom. def. recording

Insp. scope Doc. confirmation( ) Scope not fixed ( ) No documentation( ) Fixed scope ( ) Docu. if rejected( ) Smaller scope ( ) Doc. required( ) Larger scope

Miscellaneous[ ] Long-term inspection [ ] Record measured vals[ ] Scrap share/q-score[ ] Res. rec. change docs[ ] Test-equip. assign.

Print Formula( ) Print ( ) No formula( ) Do not print ( ) Calculated characteristic( ) Do not print at skip ( ) Input processing

Use sampling procedure SP03-## for this inspection characteristic.

Continued on next page

194 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 205: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection Characteristics in the Inspection Plan

Task 2: Dynamic modification in the inspection planDepending on the settings used in the inspection plan, you can use dynamicmodification.

1. If the delivered materials are always of a high quality and no defects arerecorded during the goods receipt inspection, the inspection scope can bereduced. Dynamic modification should always refer to the whole inspectionlot. Dynamic modification rule B## is used.

Where do you make the settings for dynamic modification in the inspectionplan?

__________________________________________________________

Which dynamic modification level should you choose?

__________________________________________________________

2006/Q2 © 2006 SAP AG. All rights reserved. 195

Page 206: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Solution 10: Inspection Characteristics inthe Inspection PlanTask 1: Create an inspection characteristic in theinspection planYou want to enhance the inspection plan that you created in group Group##.

1. Add another inspection operation to your inspection plan in the task listgroup Group##. The inspections for this operation are always performedin work center QMWE2-##. The wattage of the lamps is measured in theinspection operation.

A quantitative inspection characteristic is needed for inspecting the wattage.Create this inspection characteristic with the short text Wattage in operation0020. On the whole, single results must be confirmed for this inspectioncharacteristic. The wattage of the lamps is generally between 20.00and 120.00 watts. Sample determination should occur using a samplingprocedure. The number of units inspected during results recording mustcorrespond to the planned number of units to be inspected. If this inspectioncharacteristic is rejected during results recording, the user should enter aninspection description in the system. The inspection characteristic shouldalways be printed on the inspection instruction.

Make a note of the control indicators for the inspection characteristic.

Type[ ] Lower specif. limit [ [ ] Upper specif. limit[ ] Check target value

Sample[ ] Sampling procedure [ ] Additive sample[ ] SPC characteristic [ ] Destructive insp.

Results confirmation( ) Summ. recording ( ) Required char.( ) Single result ( ) Optional char.( ) No charac. rec. ( ) After accept.( ) Classed recording ( ) After rejection[ ] Autom. def. recording

Continued on next page

196 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 207: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection Characteristics in the Inspection Plan

Insp. scope Doc. confirmation( ) Scope not fixed ( ) No documentation( ) Fixed scope ( ) Docu. if rejected( ) Smaller scope ( ) Doc. required( ) Larger scope

Miscellaneous[ ] Long-term inspection [ ] Record measured vals[ ] Scrap share/q-score[ ] Res. rec. change docs[ ] Test-equip. assign.

Print Formula( ) Print ( ) No formula( ) Do not print ( ) Calculated characteristic( ) Do not print at skip ( ) Input processing

Use sampling procedure SP03-## for this inspection characteristic.

a) Logistics→ Quality Management→ Quality Planning→ InspectionPlanning→ Inspection Plan→ Change (QP02)

Enter the following data on the initial screen for changing inspectionplans:

Field name or data type ValuesPlant 1000Group Group ##

Choose the pushbutton Operations or the Return key. Theoperation overview for the inspection plan appears. Enter work centerQMWE2-## for the second operation and choose Return. The controlkey for the operation is copied from the specifications in the workcenter. Enter the operation description in the Description field (forexample, wattage).

Select operation 0020 to create the inspection characteristics and choosethe pushbutton Inspection characteristics. On the characteristicoverview, you can now create a new inspection characteristic. Set theQN indicator for a quantitative inspection characteristic and enter

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 197

Page 208: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Wattage as the short text for the inspection characteristic. Choosethe Return key. The screen for editing the control indicators of thecharacteristic appears. Set the indicators in the following way:

Type[x] Lower specif. limit [x] Upper specif. limit[ ] Check target value

Sample[x] Sampling procedure [ ] Additive sample[ ] SPC characteristic [ ] Destructive insp.

Results confirmation( ) Summ. recording (�) Required charac.(�) Single result ( ) Optional char.( ) No charac. rec. ( ) After accept.( ) Classed recording ( ) After rejection[ ] Autom. def. recording

Insp. scope Doc. confirmation( ) Scope not fixed ( ) No documentation(�) Fixed scope (�) Docu. if rejected( ) Smaller scope ( ) Doc. required( ) Larger scope

Miscellaneous[ ] Long-term inspection [x] Record measured vals[ ] Scrap share/q-score[ ] Res. rec. change docs[ ] Test-equip. assign.

Continued on next page

198 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 209: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection Characteristics in the Inspection Plan

Print Formula(�) Print (�) No formula( ) Do not print ( ) Calculated characteristic( ) Do not print at skip ( ) Input processing

After entering the control indicators, the quantitative characteristic dataappears if you choose the Return key. Since the wattage of the lamps isgenerally between 20.00 and 120.00 watts, enter the following values:

Field name or data type ValuesDecimal places 2Unit of measurement WLower limit 20,00Upperlimit 120,00

Exit the Quantitative Characteristic Data screen by choosingthe Return key. The Sample tab page appears for the inspectioncharacteristic. Enter the sampling procedure SP03-##.

Save your entries.

Task 2: Dynamic modification in the inspection planDepending on the settings used in the inspection plan, you can use dynamicmodification.

1. If the delivered materials are always of a high quality and no defects arerecorded during the goods receipt inspection, the inspection scope can bereduced. Dynamic modification should always refer to the whole inspectionlot. Dynamic modification rule B## is used.

Where do you make the settings for dynamic modification in the inspectionplan?

__________________________________________________________

Which dynamic modification level should you choose?

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 199

Page 210: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

__________________________________________________________

a) Logistics→ Quality Management→ Quality Planning→ InspectionPlanning→ Inspection Plan→ Change (QP02)

Enter the following data on the initial screen for changing inspectionplans:

Field name or data type ValuesPlant 1000Group Group ##

Choose the pushbutton Header or the F6 function key. The screenChange Inspection Plan: Header Details appears. In the headerdetails, you define the dynamic modification level in the screenarea Parameters for dynamic/inspection points. Choose Dynamicmodification at lot level in the field Dynamic modification level.

Enter the dynamic modification rule B## in the field Dyn. Mod. rule.

Save your entries.

200 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 211: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection Characteristics in the Inspection Plan

Lesson Summary

You should now be able to:� Describe the use of QM basic data at characteristic level in an inspection plan.� Create additional inspection characteristics in inspection plans.

2006/Q2 © 2006 SAP AG. All rights reserved. 201

Page 212: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Lesson: Reference Operation Set and Product Structure

Lesson OverviewIdentical inspection processes often occur in different inspection plans. These kindof specifications can also be included in a reference operation set. This referenceoperation set can then be referred to later in different inspection plans. Thisreduces the administrative work in inspection planning.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Describe the structure and use of reference operation sets.� Explain the options for the product structure within inspection planning.

Business ExampleTo reduce the number of inspection plans, the same inspection plan is used toinspect similar materials. This inspection plan contains material-dependenttolerance specifications, if required. The product structure provides you with anoverview of the relevant master data from inspection planning.

Dependent Characteristic Specifications in theInspection Plan

Figure 90: Reducing the Number of Inspection Plans

Similar materials can be inspected with the same inspection plan. These materialsmust be assigned to the inspection plan.

202 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 213: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Reference Operation Set and Product Structure

Specific inspection characteristic values are not allowed for referencedcharacteristics.

Figure 91: Dependent Characteristics in the Inspection Plan

You can maintain dependent characteristic specifications for the task list using thematerial-task list assignment of assigned materials. On the characteristic overview,there is an icon that shows whether dependent characteristic specifications exist.

You can define dependent characteristic specifications for quantitative andqualitative inspection characteristics with reference to:

� Material� Combination of material, vendor, and customer

If you have not defined dependent characteristic specifications, the system usesthe values defined for the inspection characteristic.

You cannot define dependent characteristic specifications for referenced masterinspection characteristics or inspection characteristics in reference operation sets.

2006/Q2 © 2006 SAP AG. All rights reserved. 203

Page 214: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Figure 92: Copy Characteristics

You can copy a characteristic from another operation in the task list or fromanother task list. The copied characteristics are added after the selectedcharacteristic to the current task list.

If you copy characteristics from another task list, the information is read fromthe database.

Figure 93: Copy Characteristic Values

204 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 215: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Reference Operation Set and Product Structure

When you copy characteristics within the same task list or from other task lists,the code groups and selected sets are copied to the current task list in addition tothe maintained quantitative data.

If you maintain dependent characteristic specifications, you can copy and thenchange available characteristic values for the task list characteristic.

Reference Operation Set and Product Structure

Figure 94: Reference Operation Set

The reference operation set has the same structure as the inspection plan. Itcan have several operations and each operation can contain several inspectioncharacteristics. You can assign work centers and production resources and tools(PRTs) to a reference operation set.

The reference operation set is not material-dependent.

You can use the reference operation set as a copy model when creating inspectionplans. The material reference is then created in the inspection plan header.

You can reference the reference operation set in inspection plans and routings. Inthis case, the material reference is also created using the header information fromthe inspection plan or routing.

2006/Q2 © 2006 SAP AG. All rights reserved. 205

Page 216: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Figure 95: product structure browser

The product structure browser displays information about your product data.This information is especially important for engineering and design as well asproduction. This graphical browser gives you an overview of product-definingdata by providing a structural display. You can navigate within a product structureand access all data that is relevant for your product.

As of Release 4.6C, some of the QMmaster data has been integrated in the ProductStructure Browser (transaction CC04). This applies to the following objects:

� Inspection plan� Material specification� Task list characteristic� Master inspection characteristic

You can use different filters to define which product-related data you want tobe displayed in the graphical overview. The product structure can be explodedfor all systems.

206 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 217: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Reference Operation Set and Product Structure

Figure 96: Product structure browser

From the graphical display of the product structure, you can go directly to theEngineering Workbench to perform further processing steps there.

You can display details related to the documents for a product in a separategraphical window within the product structure browser.

Figure 97: Displaying Task List Changes

2006/Q2 © 2006 SAP AG. All rights reserved. 207

Page 218: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Changes to inspection plans and reference operation sets are documented andcan therefore be traced.

� Depending on the selection criteria on the selection screen, you can displaythe task list changes (transaction QP60) or the related change documents(transaction QP61) in the inspection planning menu.

� You can also use transaction AUT10 (Evaluation of Audit Trail) to evaluatechanges to the inspection plans. You can access this function by choosingSAP Menu -> Cross-Application Components -> Engineering ChangeManagement -> Logging -> Evaluation of Audit Trail.

Figure 98: Inspection Plan: Management Functions

Selective printing of inspection plans

� You use the material from the material-task list assignment for theselective printing of an inspection plan. Only the dependent characteristicspecifications that are valid for the combination of material, vendor, andcustomer are printed.

Individual identifier for reference operation sets

� When you maintain inspection plans, the operations with reference to areference operation set with task list group and group counter are displayedin the operation overview.

Batch input for inspection plans

� You can use batch input to copy inspection plans with inspectioncharacteristics, as well as routings and reference operation sets. The datatransfer workbench in Customizing for inspection planning supports allstandard single steps in data transfer.

208 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 219: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Reference Operation Set and Product Structure

Authorizations

� You can protect QM fields at task list header and operation level using theauthorization check.

Figure 99: Data Transfer to the SAP System Using BAPIs

The initial data transfer possibilities of inspection plans, routings, and referenceoperation sets were improved in Release 4.6C. Three new BAPIs are available:

� For the creation of inspection plans (function module: BAPI_INSPEC-TIONPLAN_CREATE)

� For the creation of routings (function module: BAPI_ROUTING_CREATE)� For the creation of reference operation sets (function module:

BAPI_REFSETOFOPERATIONS_CREATE)

You can find general information about data transfer in the SAP Library underSAP ERP Central Component -> Cross-Application Components -> CA DataTransfer -> Data Transfer Workbench -> Data Transfer Objects in Applications-> QM - Quality Management: Data Transfer.

The BAPI explorer (transaction BAPI) gives you an overview of the BAPIs in aparticular application component.

The data transfer workbench (transaction SXDA) supports you in making aninitial data transfer and contains one report for the creation of test data in IDocformat from existing task lists. Read the documentation in QM Customizing underQuality Planning→ Inspection Planning→ General→ Copy Inspection Planfrom External System.

The documentation related to report RCPTRA01 contains a detailed descriptionof the procedure.

2006/Q2 © 2006 SAP AG. All rights reserved. 209

Page 220: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

210 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 221: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Reference Operation Set and Product Structure

Exercise 11: Material-task list assignmentand reference operation set

Exercise ObjectivesAfter completing this exercise, you will be able to:� Use reference operation sets in inspection planning.� Assign materials to an inspection plan and define dependent characteristic

specifications for these materials.

Business ExampleAt goods receipt, it is important that all materials are labeled and that the labelingis in the right place. You want to use these characteristics in all inspection plansfor goods receipt.

During a GR-inspection, all lamps are inspected with the same inspection plan. Inthis inspection plan, there must be corresponding specifications for the differentwattage of the lamps.

Task 1: To use the reference operation set ininspection planning.You can use reference operation sets to simplify the inspection planning.

1. You use a reference operation set to perform an inspection on the materiallabeling. This reference operation set is already available in the system andcan be used in your inspection plan for GR inspection group ##.

From the task list group Print, reference the reference operation set with thegroup counter in your inspection plan as operation 30.

Task 2: material-task list assignment in the inspectionplanSeveral materials can be inspected with one inspection plan. If required,material-dependent tolerance specifications can be defined for the inspectioncharacteristics.

1. The created inspection plan should now be used for the inspection ofmaterials T-BQ1## (lamp, 60 watts) and T-BQ2## (lamp, 80 watts). Assignthe materials to the inspection plan and for these materials, define dependentcharacteristic specifications for the inspection characteristic in operation20.

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 211

Page 222: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Task 3: To change the inspection setup in the materialmasterYou must change the inspection setup of inspection type 05 for these materials,so that the inspection specifications are copied automatically from the inspectionplan when inspecting the materials.

1. Change the inspection setup for your material T-BQ1##.

Task 4: Create a manual inspection lotAfter you change the inspection setup for inspection type 05, the inspectionspecifications will then be copied from the inspection plan for inspection lots.

1. Create a manual inspection lot for the follow-up inspection of materialT-BQ1##. The inspection lot origin is 05 (Miscellaneous goods movement)and the inspection type is 05. The inspection lot quantity is 50 pieces.

Also enter your group number in the Short text field.

Save the inspection lot.

Display the inspection lot and make a note of the following data:Inspection lotnumber:

__________________________________

Sample size: __________________________________

Hint: You can also display the inspection lot using your list offavorites.

Hint: General note:

In general, you can always create inspection plans that should onlybe used for onematerial. In this case, you can access the transactionfor creating the inspection plan by entering the combination of plantand material. In this case, the qualitative or quantitative data, whichyou enter in the task list for the inspection characteristics, are validonly for this one material.

212 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 223: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Reference Operation Set and Product Structure

Solution 11: Material-task list assignmentand reference operation setTask 1: To use the reference operation set ininspection planning.You can use reference operation sets to simplify the inspection planning.

1. You use a reference operation set to perform an inspection on the materiallabeling. This reference operation set is already available in the system andcan be used in your inspection plan for GR inspection group ##.

From the task list group Print, reference the reference operation set with thegroup counter in your inspection plan as operation 30.

a) Logistics→ Quality Management→ Quality Planning→ InspectionPlanning→ Inspection Plan→ Change (QP02)

Enter the following data on the initial screen for changing inspectionplans:

Field name or data type ValuesPlant 1000Group Group ##

Choose the pushbutton Operations or the Return key. The operationoverview of the inspection plan appears. Choose the pushbutton Ref(create reference) to display the screen for creating a reference. Enterthe following data on this screen:

Field name or data type ValuesOperation 30

Group referred to PrintGrp counter ref. to 1

Exit the screen by choosing ENTER. The operation overview of theinspection plan appears. Operation 30 is displayed in gray. This meansthat the operation is referenced from a reference operation set.

Save the changes you made to the inspection plan.

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 213

Page 224: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Task 2: material-task list assignment in the inspectionplanSeveral materials can be inspected with one inspection plan. If required,material-dependent tolerance specifications can be defined for the inspectioncharacteristics.

1. The created inspection plan should now be used for the inspection ofmaterials T-BQ1## (lamp, 60 watts) and T-BQ2## (lamp, 80 watts). Assignthe materials to the inspection plan and for these materials, define dependentcharacteristic specifications for the inspection characteristic in operation20.

a) Logistics→ Quality Management→ Quality Planning→ InspectionPlanning→ Inspection Plan→ Change (QP02)

Enter the following data on the initial screen for changing inspectionplans:

Field name or data type ValuesPlant 1000Group Group ##

Choose the pushbutton Header or the F6 function key. The screenChange Inspection Plan: Header Details appears.

Choose the pushbutton Material assignment. The assignment screenfor the material-task list assignment appears. On this screen, you assignmaterials to task lists within the task list group Group##.

Field name or data type Valuesgroup counter 1Plant 1000Material T-BQ1##Material T-BQ2##

Exit the assignment screen by choosing the Return key. You return tothe header details for the inspection plan.

The dependent characteristic specifications are defined in thecorresponding inspection characteristic. Choose the pushbuttonOperations. The operation overview of the inspection plan

appears. Select operation 20 and choose the pushbutton InspectionCharacteristics to go to the characteristic overview for operation 0020.In the characteristics overview, select characteristic 10 and choose the

Continued on next page

214 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 225: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Reference Operation Set and Product Structure

pushbutton Dependent Characteristic Specifications to define thematerial-dependent characteristic specifications. The screen ChangeInspection Plan: Dependent Characteristic Specifications appears.

Choose Add assignment ( ) to add materials from the material-tasklist assignment. Choose the first material from the assignment and addthe material. You can already enter the specification limits for thismaterial on the overview screen. However, after you add the material,you can also choose the pushbutton Quant. data to navigate to thedetail screen of the quantitative data. On this screen, you can adapt andcopy the quantitative data from the task list to the material-relatedcharacteristic specifications using the pushbutton Characteristicdata. In this case, specifications are copied for the decimal places andthe unit of measurement. Define the lower specification limit as 58 andthe upper specification limit as 62 for material T-BQ1##.

Define the specification limits for material T-BQ2## in the same way.For this material, the lower specification limit is 78 and the upperspecification limit is 82.

Save your entries.

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 215

Page 226: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Task 3: To change the inspection setup in the materialmasterYou must change the inspection setup of inspection type 05 for these materials,so that the inspection specifications are copied automatically from the inspectionplan when inspecting the materials.

1. Change the inspection setup for your material T-BQ1##.

a) Logistics→ Quality Management→ Quality Planning→ LogisticsMaster Data→ Material→ Change (MM02)

Field name or data type ValuesMaterial T-BQ1##

Select the Quality Management view in the Select View(s) dialog boxand use the Return key or the pushbutton Organizational levels toexit this dialog box. Enter plant 1000 on the next screen and exit thescreen using the Return key.

The Quality Management view of the material master appears formaterial T-BQ1##. You must change the inspection setup for thematerial so that the inspection specifications from the inspection planare used in the future. By choosing the pushbutton Insp. setup, theInspection Setup Data screen appears. Make the following changes tothe detailed information for inspection type 05:

Field name or data type ValuesInsp. with spec. Cancel indicatorInsp. with task list Set indicator

Exit the inspection setup by choosing the Return key, and save yourentries.

Task 4: Create a manual inspection lotAfter you change the inspection setup for inspection type 05, the inspectionspecifications will then be copied from the inspection plan for inspection lots.

1. Create a manual inspection lot for the follow-up inspection of materialT-BQ1##. The inspection lot origin is 05 (Miscellaneous goods movement)and the inspection type is 05. The inspection lot quantity is 50 pieces.

Also enter your group number in the Short text field.

Save the inspection lot.

Continued on next page

216 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 227: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Reference Operation Set and Product Structure

Display the inspection lot and make a note of the following data:Inspection lotnumber:

__________________________________

Sample size: __________________________________

Hint: You can also display the inspection lot using your list offavorites.

Hint: General note:

In general, you can always create inspection plans that should onlybe used for onematerial. In this case, you can access the transactionfor creating the inspection plan by entering the combination of plantand material. In this case, the qualitative or quantitative data, whichyou enter in the task list for the inspection characteristics, are validonly for this one material.

a) Logistics→ Quality Management→ Quality Inspection→ InspectionLot→ Processing→ Create (QA01)

Enter the following data on the initial screen:

Field name or data type ValuesMaterial T-BQ1##Plant 1000Inspection lot origin 05

You can access the detail data for the inspection lot by choosing Enter.

Field name or data type ValuesInsp. lot quantity 50Short text Group ##

Choose the Return key to release the data. Save your entries.

Hint: Note that two identical plans exist. Choose the plan thatyou have just created (Group: Group ##, GrC 1).

Display the inspection lot that you created manually:

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 217

Page 228: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Logistics→ Quality Management→ Quality Inspection→ InspectionLot→ Processing→ Display (QA03)

The number of the inspection lot that was last created is displayed in thefield Inspection lot. By choosing Enter, the screen Display inspectionlot appears. The following data is displayed on this screen:

Field name or data type ValuesInspection lot 50000000 .......

Insp. lot quantitiesSample size 13 PC

218 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 229: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Reference Operation Set and Product Structure

Lesson Summary

You should now be able to:� Describe the structure and use of reference operation sets.� Explain the options for the product structure within inspection planning.

2006/Q2 © 2006 SAP AG. All rights reserved. 219

Page 230: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Lesson: Engineering Workbench

Lesson OverviewYou use many task lists with inspection specifications. It should be possibleto process different task lists together using one transaction. In addition, therequirements for mass processing a large number of task lists must be met.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Describe the structure and use of the Engineering Workbench.� Use the Engineering Workbench for inspection planning.

Business ExampleInspection specifications are maintained centrally in inspection plans and routings.The Engineering Workbench is used for this so that graphical copying and massprocessing options are available.

Inspection Planning Using the Engineering Workbench

Figure 100: The Object-Oriented Approach

The Engineering Workbench is a new maintenance environment for productstructures, operations, and inspection operations, which goes beyond the classicapproach of maintenance for bills of material and task lists. The EngineeringWorkbench includes all object types that belong to the bill of material and task list.

220 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 231: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Engineering Workbench

You can combine the object types in question to suit the individual requirementsof a group of users. For these object types, you can use complex selection criteriato provide all the relevant objects for the user in a worklist.

Figure 101: Inspection Planning Using the Engineering Workbench

You define the object types that you want to edit in the Engineering Workbench ina work area. You define the focus and working environment for each work area,which you define in Customizing for inspection planning. The focus is the objecttype according to which you make selections. The object types that you also wantto edit create the working environment.

The task list header or operation can be a possible focus for a work area ininspection planning. If you want to set the task list header as the focus, alloperations for an inspection plan are loaded to the Workbench worklist. If youset the operation as the focus, only certain operations for an inspection plan areloaded to the worklist.

You enter selection criteria for task list headers, operations, productionresources/tools, or inspection characteristics on the selection screen depending onthe settings in the work area. If you have made a selection, a worklist is created inthe Engineering Workbench.

2006/Q2 © 2006 SAP AG. All rights reserved. 221

Page 232: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Figure 102: Inspection Plan - The "Engineering Workbench"

You can use the Engineering Workbench to display and edit the selected objectsflexibly and logically. These views allow you to display the known structures ofbills of material and task lists in the normal way, as well as with views that werenot previously available. In particular, you can create, copy, change, and deleteobjects.

You can use the Engineering Workbench to copy both bills of material and tasklist objects to the same worklist, and process them together (not separately aswas previously the case).

When editing a bill of material or task list with the classic transactions, the wholestructure is locked to other users. In contrast, the Engineering Workbench causesa targeted locking of sequences, operations, and BOM items so that other partsof the structure can still be edited by other users. This allows several users tosimultaneously process a structure.

222 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 233: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Engineering Workbench

Figure 103: Engineering Workbench: Overview of Task List Headers

Depending on the selection criteria, you can display an overview of all the tasklists in the worklist, which you can edit and display. Moreover, you can createnew task lists.

Depending on the setting in the work area, task lists that are in the worklist forthe Engineering Workbench are automatically blocked for other users. If differentusers often work in the same task list, it is better to automatically block theoperations and not the task list headers.

There are different processing options in the worklist:

� General settings for task list headers� QM-relevant settings for task list headers� Administrative data for task list headers� Details for task list header

To view the operation overview for the selected task list, choose Task lists→Operations.

2006/Q2 © 2006 SAP AG. All rights reserved. 223

Page 234: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Figure 104: Engineering Workbench: Overview of Operations

Depending on the setting in the work area, all operations that are in the worklistfor the Engineering Workbench are automatically blocked for other users.

You can use the tab page function to display the corresponding operation details.

On the overview screen, you can create new operations for the inspection plan asdefined in the context, or delete existing inspection operations.

In the operations overview, you can see which operations have inspectioncharacteristics or production resources and tools assigned to them.

You can switch to the production resources/tools overview and to the inspectioncharacteristics in an operation using the menu options. You can access thematerial-task list assignment in the same way.

224 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 235: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Engineering Workbench

Figure 105: Engineering Workbench: Overview of Characteristics

On the overview screen, you can create new characteristics for the operation asdefined in the context, or process existing inspection characteristics.

You can use the tab page function to make the corresponding detail settings for allcharacteristics in the chosen operation.

You process the inspection characteristics by specifying the key date or usingthe change number.

You can activate the browser for objects in the Engineering Workbench worklistusing the application toolbar. In this way, you can display an overview of task liststhat you can edit. By expanding the objects, you can switch to the task list headers,operations, inspection characteristics, production resources/tools etc.

Advantages of Using the Engineering Workbench

� Graphical interface� Uniform look and feel� Save interim results� Improved performance for �larger� task lists� Free navigation (menu or double-click)� Switch to QM master data display� Copy function using Drag&Drop with or without dependent objects� Comparison of task lists (several task lists simultaneously)� Selection variants can be used� Personalization: The system �remembers� the user settings� Control indicators for inspection characteristics integrated as tab

2006/Q2 © 2006 SAP AG. All rights reserved. 225

Page 236: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

You can use freely-defined selection criteria to create worklists for editing tasklists (for example, selection of task lists in which a specific dynamic modificationrule or sampling procedure is used).

You can edit individual operations from various task lists in your worklist withoutexiting the transaction.

You can define which task list objects you want to copy to your work area.

As a result of free navigation, you can, for example, navigate directly from theselection screen to the inspection characteristics or operations.

On the operation overview, you can see whether inspection characteristics orproduction resources/tools exist for an operation.

226 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 237: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Engineering Workbench

Exercise 12: Engineering Workbench �Optional Exercise

Exercise ObjectivesAfter completing this exercise, you will be able to:� Use the Engineering Workbench to change inspection plans and reference

operation sets.

Business ExampleYou use many inspection plans in your company for different reasons. You needindividual search criteria to maintain these inspection plans so that you can selectand edit certain plans. That is why you use the Engineering Workbench.

Task 1: Inspection Planning Using the EngineeringWorkbenchYou want to enhance an existing inspection plan. You want to create a newoperation with an inspection characteristic using the Engineering Workbench.

1. You want to create another inspection operation for material T-BQ3##(fluorescent lamps) during a goods issue inspection. In this inspectionoperation, you inspect at work center QMWA6-##, whether the technical datais printed on the glass of the fluorescent lamps. To do this, you use masterinspection characteristic MK04-00. Sample determination is performedusing sampling procedure SP03-##.

Hint: Define the working area in the Engineering Workbench, sothat the focus during selection is the inspection plan header.

Task 2: Mass Change Using the EngineeringWorkbenchReplacing the sampling procedure

1. You must replace sampling procedure Fix5-0 by sampling procedureSP03-## for master inspection characteristic MK02-## in all inspectionplans, because of changing from a fixed sample to a variable sample.

Hint: Define the working area in the Engineering Workbench, sothat the focus during selection is the inspection plan operations.

2006/Q2 © 2006 SAP AG. All rights reserved. 227

Page 238: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Solution 12: Engineering Workbench �Optional ExerciseTask 1: Inspection Planning Using the EngineeringWorkbenchYou want to enhance an existing inspection plan. You want to create a newoperation with an inspection characteristic using the Engineering Workbench.

1. You want to create another inspection operation for material T-BQ3##(fluorescent lamps) during a goods issue inspection. In this inspectionoperation, you inspect at work center QMWA6-##, whether the technical datais printed on the glass of the fluorescent lamps. To do this, you use masterinspection characteristic MK04-00. Sample determination is performedusing sampling procedure SP03-##.

Hint: Define the working area in the Engineering Workbench, sothat the focus during selection is the inspection plan header.

a) Logistics→ Quality Management→ Quality Planning→ InspectionPlanning→ Inspection Plan→ Workbench (CWBQM)

The dialog box for working area settings in the Engineering Workbenchappears. The working area defines which focus is used. This meansto which object type the selection criteria that you are recording refer.Define the working area so that the focus is in the inspection planheader. Exit the screen by choosing the Return key or the pushbuttonContinue.

The change to the task lists can occur with a key date or change number.Enter the current date as the key date in the Process using field.

For the selection criteria of task list headers, you can define theselection conditions on the different tab pages. Enter the following data:

Header tab page

Field name or data type ValuesMaterial T-BQ3##Task list type Inspection planUsage 6

Hint: You can use the pushbutton More selection criteria todefine additional selection conditions at any time.

Continued on next page

228 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 239: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Engineering Workbench

Choose the F8 function key or the pushbutton Load task lists. Theoverview of task list headers in the Engineering Workbench appears.

Hint: The system loads all task lists to the EngineeringWorkbench worklist, which meet the selection conditions. Youcan process all task lists with the corresponding operations andcharacteristics in the Workbench without having to load theindividual task lists again from the database.

Choose Task Lists→ Operations. The Operations Overview appears.Create the additional operation:

Field name or data type ValuesWork center QMWA6-##Operation short text Print of technical data

After you select the new operation, choose Task Lists→ InspectionCharacteristics. The overview of the inspection characteristics appears.

Hint: In the context block, you can always see which operationyou are processing in which task list.

Enter the master inspection characteristic MK04-00 in the fieldMaster inspection characteristic on the screen EWB: InspectionCharacteristics Overview. By choosing the Return key, the Sample tabpage appears on which you can enter the sampling procedure SP03-##.Exit this tab page by choosing the Return key.

Save your worklist and exit the Engineering Workbench.

Task 2: Mass Change Using the EngineeringWorkbenchReplacing the sampling procedure

1. You must replace sampling procedure Fix5-0 by sampling procedureSP03-## for master inspection characteristic MK02-## in all inspectionplans, because of changing from a fixed sample to a variable sample.

Hint: Define the working area in the Engineering Workbench, sothat the focus during selection is the inspection plan operations.

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 229

Page 240: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

a) Logistics→ Quality Management→ Quality Planning→ InspectionPlanning→ Inspection Plan→ Workbench (CWBQM)

The dialog box for working area settings in the Engineering Workbenchappears. Define the working area so that the focus is in the operation.Exit the screen by choosing the Return key or the pushbutton Continue.

Hint: If you always work in the same working area, you canalso define this as a standard working area.

Enter the current date as the key date for task list changes in theProcess using field.

For the selection criteria of operations, you can define the selectionconditions on the different tab pages. Enter the following data:

Operation tab page

Field name or data type ValuesTask list type Q

Inspection characteristic tab page

Field name or data type ValuesMaster inspection characteristic MK02-##Version 1Plant 1000Sampling procedure Fix5-0

When you have defined the selection criteria, choose Task Lists→Inspection Characteristics or the pushbutton Inspection Characteristicsin the application toolbar. The Inspection Characteristics Overviewappears. The system again loads all task lists to the EngineeringWorkbench worklist, which meet the selection conditions.

Hint: The selection focus in this case is the operation becauseof the setting in the working area. As a result, all characteristicsin the operation, which correspond to the selection conditions,are displayed in the worklist.

Continued on next page

230 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 241: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Engineering Workbench

If you only want to display the master inspection characteristicMK02-## in the inspection characteristics overview, you can set a filter.Select the column Master inspection characteristic in the inspectioncharacteristics overview and choose the pushbutton Filter. Definethe filter criteria for the master inspection characteristic. Enter themaster inspection characteristics MK02-## on the screen Filter insp.characs. Exit the screen by choosing ENTER. On the EWB: InspectionCharacteristics Overview only the master inspection characteristicMK02-## is now displayed.

On the Sample tab page, you can replace the sampling procedure Fix5-0by sampling procedure SP03-##.

Save your worklist and exit the Workbench.

2006/Q2 © 2006 SAP AG. All rights reserved. 231

Page 242: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Lesson Summary

You should now be able to:� Describe the structure and use of the Engineering Workbench.� Use the Engineering Workbench for inspection planning.

232 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 243: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Engineering change management

Lesson: Engineering change management

Lesson OverviewBy using engineering change management, changes in inspections plans can begiven a validity period. Depending on the specification, different objects, such asinspection plan and material master, are changed with one change number.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Explain how engineering change management can be used in inspectionplanning.

� Describe the structure of the change master record.

Business ExampleCertain changes to an inspection plan have to become valid as of a key date.Engineering change management is used for this in inspection planning.

Engineering Change Management in InspectionPlanning

Figure 106: Validity Statuses in the Inspection Plan - Change Number

2006/Q2 © 2006 SAP AG. All rights reserved. 233

Page 244: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

A task list change is made with or without a change number depending on thechange modes defined in the inspection plan header. If you do not want tooverwrite the old values for the task list, you must use the change number.

� If you work without a change number, the old values in the task list areoverwritten by new values. The change is valid on the valid-from date forthe task list object (for example, inspection characteristic or operation). Thekey date, which is used when changing task lists, is only used for selectingthe inspection plan that is to be changed. The change document shows allthe changes that have been made to the task list.

� The valid-from date for the change master record is the date that is usedwhen working with change numbers. A new data record is written to thedatabase with the new data (for example, changed specification limits).

Hint: Specifications are copied from the inspection plan to the inspectionlot. A subsequent change to the inspection plan does not effect inspectionlots to which the inspection plan is already assigned.

Hint: You can use the field selection in Customizing for inspectionplanning to specify that inspection plans can generally only be created orchanged using change numbers.

Figure 107: Structure of a Change Master Record

234 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 245: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Engineering change management

The change master record contains all information that is required for managingand controlling changes. This includes descriptive data (for example, reason forchange) and controlling data (for example, valid-from date, identifier for objecttypes).

� You can block individual object types using a corresponding indicator in thechange master record for changes with the relevant change number.

Change master records are identified by the change number. A change numbercan identify the following tasks in the change process:

� Simple change master record� Change master record with change hierarchy� engineering change request/order

In the change header, a short description of the change and the validity periodis maintained.

You use the object types to define which objects can be changed using the changemaster record.

Object management records enable changes to a certain object to be documented.

Figure 108: Object Types for the Change Master Record

You can change various change objects with reference to a change master record.Objects with the same attributes are assigned to one object type (for example,inspection plans, reference operation sets, routings, and so on, are assigned tothe object type �Task lists�).

2006/Q2 © 2006 SAP AG. All rights reserved. 235

Page 246: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Object-related management records are defined for some change objects. You canuse these object-related management records to access additional functions. Inthis way, these objects can contain, for example, an object-related valid-fromdate or run a specific status network.

You can use the object-related management record to control specific changes to acertain change object (for example, an inspection plan). You can create severalobject management records for a change master record.

Figure 109: Approval Procedure for the Inspection Lot

Integration of approval requirements from the process industry sector whenchanging master data.

You define a change rule and a change type in the inspection plan header to usethe approval procedure for the inspection plan.

You define an identifier for inspection lot approval in the material authorizationgroup (Customizing) to use the approval procedure in the inspection lot. To usethe authorization objects, the necessary authorizations must be assigned to thecorresponding user master records. The material authorization group is entered inthe material master under General data in the Quality Management view.

Single authorization is required for the inspection lot, if the task list requiresapproval but has not yet been approved. If the specifications from an approvedtask list are extended using a material specification, a single approval can also berequired for the inspection lot.

Approvals can be issued for inspection lots if you change the inspection lot statususing the corresponding functions. If the inspection lot has not yet been approved,you cannot record inspection results or make a usage decision.

236 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 247: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Engineering change management

Lesson Summary

You should now be able to:� Explain how engineering change management can be used in inspection

planning.� Describe the structure of the change master record.

2006/Q2 © 2006 SAP AG. All rights reserved. 237

Page 248: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Lesson: Task List - Material Specification

Lesson OverviewInspection specifications can be stored both in inspection plans/routings and in amaterial specification. These two options will be compared in this lesson.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Describe the options for using task lists and material specifications.

Business ExampleDetailed inspection specifications are stored in inspection plans or routings. Ifadditional material-dependent inspection specifications have to be stored for aparticular material, a material specification can be used.

Inspection with Task List and Material Specification

Figure 110: Comparison: Inspection Plan - Material Specification

The material specification valid at client level can replace or complete theinspection plan valid at plant level.

238 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 249: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Task List - Material Specification

You can perform a simplified quality inspection using the material specification. Ifyou only inspect according to the material specification, you cannot specify workcenters, set inspection methods, or use dynamic modification.

The master inspection characteristics used in the material specification mustbe fully maintained (reference characteristic or complete copy model) and cancontain specific inspection specifications for the material.

The use of the material specification is dependent on the inspection setup in theQuality Management view of the material master. The indicators Insp. with mat.spec. or Insp. with task list define according to which specifications the inspectionis performed.

Figure 111: Inspection with Task List and Material Specification

If you set the indicators Insp. with mat. spec. and Insp. with task list inthe inspection setup for the material master (Quality Management view),the information is linked. During inspection lot creation, master inspectioncharacteristics are copied from the task list and material specification to theinspection lot.

Inspection specifications for master inspection characteristics that occur in thetask list and the material specification are taken from the material specification.The specifications from the material specification take precedence over the tasklist specifications.

If additional master inspection characteristics are specified in the materialspecification, these are assigned to the last operation in the task list.

2006/Q2 © 2006 SAP AG. All rights reserved. 239

Page 250: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Figure 112: Inspection During Production - Master Data

It can be necessary to perform several single inspections in production for certainreasons or at certain intervals. By using QM in production, you can performinspections during production. The corresponding inspection characteristics areintegrated in the routings or master recipes.

By using inspection points, you can perform the following functions in aninspection during production:

� Perform inspections at regular intervals� Record and valuate results for each inspection point� Assign a quantity to each inspection point and summarize inspection points

for partial lots from a quality standpoint

� The inspection interval is determined by the specifications for theinspection point in the operation and the inspection frequency in thesampling procedure for the inspection characteristic.

You use partial lot assignment at header level of the task list to define whetheror how partial lots should be created, and whether the partial lots for batchesshould be summarized.

The indicator Last partial lot assignment means that an operation is marked as anOperation with stock-related partial lot assignment. Default values for quantitypostings for the order are only possible for an operation if this indicator is set. Theinspection point quantities from the last QM operation are proposed at the goodsreceipt posting for the order.

240 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 251: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Task List - Material Specification

Lesson Summary

You should now be able to:� Describe the options for using task lists and material specifications.

2006/Q2 © 2006 SAP AG. All rights reserved. 241

Page 252: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Lesson: Flexible Inspection Specifications

Lesson OverviewIn this lesson, you will learn about the options for the flexible selection ofinspection specifications. In addition to the effects on the planning phase, youwill also learn how this influences inspection lot creation and inspection resultsrecording.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Describe the options for the flexible selection of specifications.� Describe the requirements for flexible inspection specifications.

Business ExampleFlexible inspection specifications are to be used because inspections cannot befully planned in advance. The inspection specifications currently required are tobe selected from a super task list during inspection lot creation.

Planning and Using Flexible Inspection Specifications

Figure 113: Flexible Inspection Specifications: Procedure

242 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 253: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Flexible Inspection Specifications

This function is usually used in conjunction with the stability study solution. Itcan also be used for inspection lots in other processes if you implement a BAdI oruse customer functions.

Flexible inspection specifications can, for example, be used when inspectionscannot be fully planned in advance. This may be the case for:

� Inspections performed as a service� Inspections as the result of complaints� Inspections in stability studies

You can still perform these types of inspections if the inspection specifications canbe changed using flexible specification selection and changing at inspection lotcreation or in results recording.

The solution to the problem lies in the planning of inspection specifications in aso-called universal plan, which contains a wide scope of inspection specifications(characteristics, inspection methods, sampling procedures, and so on).

At inspection lot creation, the characteristics that are relevant to the currentinspection are selected in the universal plan. This is known as flexiblespecification selection.

At results recording, it is possible to change certain specifications, for exampleinspection method, tolerances, or characteristic attributes. This is known asflexible specification changing.

Figure 114: Flexible Inspection Specifications: Prerequisites (1)

2006/Q2 © 2006 SAP AG. All rights reserved. 243

Page 254: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

In our stability studies solution, flexible inspection specifications are onlyavailable for manual inspection lots with the inspection lot origin 16 (inspectionlot for initial test or manual inspection lot for storage condition).

Using the inspection setup in the material master record, you can plan a manualsample calculation for this inspection type. At lot creation, the system then checkswhether or not the relevant indicator is set. The flexible inspection specificationsfunction is only called if this indicator is set. This system behavior can berestricted to specific inspection lot origins.

Figure 115: Flexible Inspection Specifications: Prerequisites (2)

In accordance with the specification selection (selection of materialspecification/task list), the system displays a list of all characteristic specificationsthat have already been read at inspection lot creation.

In this list, you can select the characteristics that are relevant for the currentinspection. These characteristics are then copied into the inspection lot. However,the specifications listed on the next slide can still be changed.

The flexible inspection specifications function can also be used to changeinspection specifications in results recording. In this case, you can call thescreen in which the changes can be made using a pushbutton (customer functionQEEM0024, EXIT_SAPLQEEM_024 and EXIT_SAPLQEEM_028 ).

This list that appears displays all characteristics for which no results have beenrecorded, that have not been completed, and that are not in a skip.

244 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 255: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Flexible Inspection Specifications

Figure 116: Flexible Inspection Specifications: Changeable Specifications

The following specifications can only be changed at inspection lot creation:

� Operation short text� Sampling procedure� Control indicator (Required or optional characteristic)

The following specifications can be changed at inspection lot creation and inresults recording:

� Characteristic short text� All limit pairs (upper/lower tolerance, limit pairs 1 and 2, plausibility limits)� Target value� Decimal places� inspection method� Info fields related to the characteristic� Selected set

2006/Q2 © 2006 SAP AG. All rights reserved. 245

Page 256: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Figure 117: Flexible Inspection Specifications: Documentation

If not all of the characteristics were copied or if specifications were changed, thesystem status FLEX is set in the inspection lot.

If defects occur during the selection of characteristics or when changingspecifications, they are output in an defect log.

246 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 257: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Flexible Inspection Specifications

Lesson Summary

You should now be able to:� Describe the options for the flexible selection of specifications.� Describe the requirements for flexible inspection specifications.

2006/Q2 © 2006 SAP AG. All rights reserved. 247

Page 258: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Lesson: Multiple Specifications - Overview

Lesson OverviewDifferent inspection specifications are required for an inspection characteristicin quality management. These different specifications may include customerrequirements, requirements specified by pharmacopoeia or authorities,country-specific legal requirements, or internal requirements. These specificationsmay consist of different tolerances or characteristic attributes for example.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� describe the options for using multiple specifications.� use multiple specifications in inspection planning, in the inspection process

and at certificate creation.

Business ExampleDuring the planning of a material or a batch, additional information is oftenrequired about the suitability or authorization of goods (for example, due tocustomer-specific or country-specific requirements). This criteria is formed ininspection plans in the SAP system using multiple specifications depending ondifferent objects such as country, customer, pharmacopoeia and so on.

Inspection Planning and Inspection Process withMultiple Specifications

Figure 118: Multiple Specifications in the inspection process

248 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 259: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Multiple Specifications - Overview

Multiple specifications can be

� called and displayed for information purposes in the entire inspectionprocessing in quality management.

� used as a basis for the valuation of a material or a batch for results recordingand usage decision.

� included in the creation of quality certificates.

The aim of multiple specifications is to determine the suitability of a batch basedon special specifications. The overall valuation of the batch for each object tellsyou whether the batch can be delivered to a certain customer or whether it can beused in certain circumstances.

Using multiple specifications influences the entire inspection processing in qualitymanagement, from the inspection planning through to the certificate creation.

� Inspection PlanningCreating and processing multiple specifications

� inspection lot creationTransferring multiple specifications to the inspection lot

� Results RecordingDisplaying the object listDisplaying multiple specifications for each characteristicAutomatic valuation of multiple specifications

� Usage DecisionDisplaying the object listDisplaying the valuation of the multiple specificationOverall valuation of multiple specificationsBatch classification

� Certificate creationDetermining specifications for the object

2006/Q2 © 2006 SAP AG. All rights reserved. 249

Page 260: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Figure 119: Customizing for Multiple Specifications

You can use QM Customizing to activate the functions for multiple specifications.The multiple specifications are not active in the default settings.

Figure 120: Object Types and Objects for Multiple Specifications

The object types allowed for multiple specifications are defined in Customizing(transaction QCCO, Quality Management -> Quality Planning -> InspectionPlanning -> General -> Multiple Specifications). You can specify whether theobject type is pharmacopoeia, a country or a customer.

250 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 261: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Multiple Specifications - Overview

The object type controls the suitability of a batch for an object based on multiplespecifications. You must assign a control key to the object type and this keydetermines whether the batch classification should occur based on the customer,the country of the general object.

The following three object types are delivered in the standard system:

� Customer� Country� Pharmacopoeia

If you want to record the suitability of a batch for a multiple specification objectin the batch class, you must specify class characteristics in the table of the objecttypes. For each object type, you can enter a characteristic with the descriptionsuitable for and a characteristic not suitable for. The type of planned batchsearch determines whether you need a characteristic with a positive valuation or acharacteristic with a negative valuation:

� If you want to search using the question "Is the batch suitable for ...?", youneed characteristics with a positive valuation.

� If you want to search using the question "Is the batch unsuitable for ...?",you need characteristics with a negative valuation.

You can determine the suitability of a batch for a multiple specification object atthe usage decision. Based on the multiple specifications, the system determinesa default value for each object and the user can copy or change it. When yousave the usage decision, this value is passed on the the corresponding classcharacteristic for the batch class.

Figure 121: Inspection Planning for Multiple Specifications

2006/Q2 © 2006 SAP AG. All rights reserved. 251

Page 262: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

If you want to use multiple specifications, you must define them in an inspectionplan. You can use the function for dependent characteristic specifications todefine the multiple specifications. When you create or process an inspection plan,in addition to the standard objects material and customer, you can also assignother objects for multiple specifications to the task list and, based on these objects,you can define dependent inspection specifications. In addition to the standardinspection specifications, these specifications are also provided for informationpurposes in the inspection processing and they can be used for an object-relatedvaluation of the material or batch to be inspected.

Bear the following points in mind when you are planning multiple specifications:

� You can only record multiple specifications for task lists (task list type Q).� You can only create multiple specifications using the engineering workbench

(EWB).

Figure 122: Multiple Specifications in Task Lists

Enter the multiple specifications in the corresponding tab page depending onwhether the characteristic is quantitative or qualitative.

252 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 263: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Multiple Specifications - Overview

Figure 123: inspection lot creation

To ensure that the planned information for multiple specifications is available forfurther inspection processing, you must transfer it from the inspection plan to theinspection lot to be processed. If you select an inspection plan with multiplespecifications when creating an inspection lot, the following specifications areautomatically transferred from the inspection plan to the inspection lot:

� Standard inspection specifications (the specifications according to whichyou are checking)

� Multiple specifications (they are recorded for the inspection lot)

The multiple specifications are available for the valuation in results recording andfor the usage decision.

Note the following: You can use transactions QP03 and CWBQM to display theinspection specifications from the inspection lot. Only when you use transactionCWBQM are the multiple specifications displayed. Transaction QP03 displaysonly a restricted view. You can use user parameter Q_EWB_CALL to open theworkbench.

2006/Q2 © 2006 SAP AG. All rights reserved. 253

Page 264: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Figure 124: Results Recording

If you process an inspection lot with multiple specifications in the resultsrecording, all information for multiple specifications is available in various views.If you create and complete inspection results for the characteristics, the resultsare valuated as usual based on the standard inspection specifications. For eachinspection characteristic, an automatic valuation of the inspection results takesplace based on the multiple specifications. The same valuation rules apply forthis as for the valuation of the standard specifications. The results of thesevaluations are displayed in the results recording using symbols. Therefore, youcan determine whether the inspection results of the individual characteristics meetthe requirements of the objects for multiple specifications (such as pharmacopoeia,country, customer and so on).

You can display the information for multiple specifications in the followingfunctions and valuate them at characteristic level:

� Record inspection results for the operation� Results Recording Worklist� Record inspection results for the inspection point� Record inspection results for the sample

Select the Multiple specification tab page in the results recording. This displaysall objects for each characteristic. You can choose Change hierarchy displayto switch between the various views.

The valuation status of multiple specifications for characteristics that have alreadybeen completed are displayed as follows:

254 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 265: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Multiple Specifications - Overview

Icon MeaningGreen All multiple specifications for a

characteristic are fulfilledYellow At least one multiple specification for

a characteristic is not fulfilledRed No multiple specification for a

characteristic is fulfilledAlert A valuation could not be performedGray A valuation has not been performed yet

Figure 125: Usage Decision

If you process an inspection lot with multiple specifications in the usage decision,you can display the various objects of the multiple specifications and thecorresponding characteristic valuations, as is also the case in results recording.When you make the usage decision, you can also trigger an automatic or manualoverall valuation of the multiple specifications for the respective objects (such ascountry or pharmacopoeia) based on the recorded inspection results. The overallvaluation is proposed in the form of the suitability of the assigned material orbatch (for example, material is permitted for the country Germany), which youcan transfer or change. When you save the usage decision, the overall valuationfor each object can be transferred automatically to the batch classification.

2006/Q2 © 2006 SAP AG. All rights reserved. 255

Page 266: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

Figure 126: Multiple specifications and batch classification

The system can only transfer the overall valuations of the multiple specificationsto the batch classification if:

� Class characteristics were assigned to each object type in Customizing tospecify the suitability of the batch material (for example, class characteristicsSuitable for and Not Suitable for). Depending on the type of batch searchrequired, a single class characteristic may be sufficient for each object type(for example, search only for Suitable for).

� The class characteristics have been assigned to the batch class of the material.

256 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 267: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Multiple Specifications - Overview

Figure 127: Automatic certificate creation

The system can automatically create quality certificates or you can create themmanually in the delivery processing. When certificates are created, object-specificspecifications from multiple specifications may be output in the certificate. Thiscertifies that the delivered material or product complies with certain standards (forexample, requirements specified by pharmacopoeia or authorities, country-specificlegal requirements and so on).

When the system creates the certificate, it automatically determines the objectsof the multiple specifications that are suitable for the sales document. Certainsettings and assignments are required in Customizing and in the certificate profile.As a result of these settings, for each characteristic, the system searches for asuitable object for which multiple specifications were created.

During the automatic certificate creation, the system checks whether objects of themultiple specifications for the inspection lot can be found for the fields in the salesdocument (for example, material, customer or country). If the sales documentcontains a field value (for example, the field value Meier GmbH for the objectcustomer), for which there is a multiple specification in the inspection plan that isthe basis for the inspection, these specifications may be output in the certificate.The sequence of the search is as follows: 1. Customer, 2. Country. The shelf-lifespecifications are always output in the certificate. However, if there is no data inthe form of multiple specifications, the standard shelf-life specifications are outputin the certificate. If there are no standard shelf-life specifications, the system usesthe release specifications. If the system cannot determine a unique object from thesales document, it outputs the standard specifications in the certificate.

2006/Q2 © 2006 SAP AG. All rights reserved. 257

Page 268: Plm412 en Col62 Fv Part a4

Unit 3: Inspection Planning PLM412

In the standard certificate form QM_QCERT_01, valuations are output accordingto multiple specifications. Use this form as a template to adjust your own formsaccordingly.

258 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 269: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Multiple Specifications - Overview

Lesson Summary

You should now be able to:� describe the options for using multiple specifications.� use multiple specifications in inspection planning, in the inspection process

and at certificate creation.

Related Information

� You can find further information about the multiple specifications in theSAP Help Portal: http://help.sap.com.

2006/Q2 © 2006 SAP AG. All rights reserved. 259

Page 270: Plm412 en Col62 Fv Part a4

Unit Summary PLM412

Unit SummaryYou should now be able to:� Explain the structure of an inspection plan.� Describe the assignment of QM basic data in the inspection plan.� Use test equipment in inspection planning.� Explain the prerequisites for regularly monitoring the test equipment used.� Describe the use of QM basic data at characteristic level in an inspection plan.� Create additional inspection characteristics in inspection plans.� Describe the structure and use of reference operation sets.� Explain the options for the product structure within inspection planning.� Describe the structure and use of the Engineering Workbench.� Use the Engineering Workbench for inspection planning.� Explain how engineering change management can be used in inspection

planning.� Describe the structure of the change master record.� Describe the options for using task lists and material specifications.� Describe the options for the flexible selection of specifications.� Describe the requirements for flexible inspection specifications.� describe the options for using multiple specifications.� use multiple specifications in inspection planning, in the inspection process

and at certificate creation.

260 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 271: Plm412 en Col62 Fv Part a4

PLM412 Test Your Knowledge

Test Your Knowledge

1. The plan usage is stored in the inspection plan header.Determine whether this statement is true or false.□ True□ False

2. Materials, vendors, and customers can be assigned using the inspectionplan header.Determine whether this statement is true or false.□ True□ False

3. A work center can be assigned to the operation in the task list.Determine whether this statement is true or false.□ True□ False

4. Test equipment can be assigned directly to an inspection characteristic in aninspection plan.Determine whether this statement is true or false.□ True□ False

5. Documents can also be assigned as test equipment / productionresources/tools.Determine whether this statement is true or false.□ True□ False

6. The test equipment used can be inspected regularly.Determine whether this statement is true or false.□ True□ False

2006/Q2 © 2006 SAP AG. All rights reserved. 261

Page 272: Plm412 en Col62 Fv Part a4

Test Your Knowledge PLM412

7. Dependent characteristic specifications can also be entered for referencedmaster inspection characteristics.Determine whether this statement is true or false.□ True□ False

8. Dependent characteristics can be used in an operation.Determine whether this statement is true or false.□ True□ False

9. The control indicator for inspection characteristics can always be changedin the task list.Determine whether this statement is true or false.□ True□ False

10. Several materials can be inspected with one inspection plan.Determine whether this statement is true or false.□ True□ False

11. You can use a reference operation set as a copy model for creating newinspection plans.Determine whether this statement is true or false.□ True□ False

12. The operations from the inspection plan and the reference operation set aredisplayed in the product structure.Determine whether this statement is true or false.□ True□ False

13. The Engineering Workbench cannot be used to process reference operationsets.Determine whether this statement is true or false.□ True□ False

262 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 273: Plm412 en Col62 Fv Part a4

PLM412 Test Your Knowledge

14. Mass change is possible in the Engineering Workbench at both operationlevel and characteristic level.Determine whether this statement is true or false.□ True□ False

15. The work area is used to define which areas are offered as selection criteriaon entering the Workbench.Determine whether this statement is true or false.□ True□ False

16. Inspection characteristics are connected to engineering change managementas objects.Determine whether this statement is true or false.□ True□ False

17. By using engineering change management, different validity statuses canexist for an inspection plan.Determine whether this statement is true or false.□ True□ False

18. The change master record can be structured in such a way that changes canonly be made to inspection plans, but not to materials, with one changenumber.Determine whether this statement is true or false.□ True□ False

19. It is not possible to carry out an inspection according to specifications froman inspection plan and a material specification.Determine whether this statement is true or false.□ True□ False

2006/Q2 © 2006 SAP AG. All rights reserved. 263

Page 274: Plm412 en Col62 Fv Part a4

Test Your Knowledge PLM412

20. The material specification can supplement the specifications from theinspection plan.Determine whether this statement is true or false.□ True□ False

21. The specifications from the material specification are attached to the lastoperation in the inspection lot.Determine whether this statement is true or false.□ True□ False

22. Flexible inspection characteristics can be used at inspection lot creation.Determine whether this statement is true or false.□ True□ False

23. The use of flexible inspection specifications is linked to an authorization.Determine whether this statement is true or false.□ True□ False

24. The flexible inspection specifications function is not always available inthe standard system.Determine whether this statement is true or false.□ True□ False

25. You can include multiple specifications in all task lists.Determine whether this statement is true or false.□ True□ False

26. The multiple specifications can be used in the complete inspection process.Determine whether this statement is true or false.□ True□ False

264 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 275: Plm412 en Col62 Fv Part a4

PLM412 Test Your Knowledge

27. The multiple specifications can be displayed in the results recording andat the usage decision.Determine whether this statement is true or false.□ True□ False

2006/Q2 © 2006 SAP AG. All rights reserved. 265

Page 276: Plm412 en Col62 Fv Part a4

Test Your Knowledge PLM412

Answers

1. The plan usage is stored in the inspection plan header.

Answer: True

You can define a task list usage in Customizing, which is then assigned in theinspection plan header and in the inspection type.

2. Materials, vendors, and customers can be assigned using the inspectionplan header.

Answer: True

By assigning a material to a task list, a task list (task list group, tasklist group counter) can be used to check several materials. If required,material-dependent tolerance specifications (dependent characteristicspecifications) can be used.

3. A work center can be assigned to the operation in the task list.

Answer: True

The work center is required, among other things, for confirmations andconnecting to subsystems. Work center-related printing of the inspectioninstructions is also possible.

4. Test equipment can be assigned directly to an inspection characteristic in aninspection plan.

Answer: False

In the first step, test equipment is assigned to the operation in the task list asproduction resources/tools. Then, provided the control indicator �Assign testequipment� is set in the inspection characteristic, a reference can be madefrom the inspection characteristic to the test equipment of an operation.

5. Documents can also be assigned as test equipment / productionresources/tools.

Answer: True

Materials, documents, equipment, and other production resources/tools canbe used as test equipment / production resources/tools.

266 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 277: Plm412 en Col62 Fv Part a4

PLM412 Test Your Knowledge

6. The test equipment used can be inspected regularly.

Answer: True

Using test equipment management, the test equipment used can be inspectedat regular intervals. Inspection lots with inspection lot origin 14 are usedfor this.

7. Dependent characteristic specifications can also be entered for referencedmaster inspection characteristics.

Answer: False

Dependent characteristic specifications can only be used for unlocked masterinspection characteristics or for characteristics that were created in the tasklist.

8. Dependent characteristics can be used in an operation.

Answer: True

In the standard system, conditional (dependent) characteristics always referto the previous required characteristic within the same operation.

9. The control indicator for inspection characteristics can always be changedin the task list.

Answer: False

If a master inspection characteristic with the attribute �Referencecharacteristic� is included in the task list, the control indicators can only bechanged after the reference has been canceled (unlock).

10. Several materials can be inspected with one inspection plan.

Answer: True

Using material-task list assignment, you can assign several materials to onetask list. You can then use the same task list to inspect similar materials.

11. You can use a reference operation set as a copy model for creating newinspection plans.

Answer: True

In addition to an inspection plan, a reference operation can also be usedas a copy model.

2006/Q2 © 2006 SAP AG. All rights reserved. 267

Page 278: Plm412 en Col62 Fv Part a4

Test Your Knowledge PLM412

12. The operations from the inspection plan and the reference operation set aredisplayed in the product structure.

Answer: True

If a reference operation set is referenced in inspection plans, the operationsfrom the reference operation set are flagged in the product structure.

13. The Engineering Workbench cannot be used to process reference operationsets.

Answer: False

The Engineering Workbench can be used to process inspection plans, tasklists, and reference operation sets.

14. Mass change is possible in the Engineering Workbench at both operationlevel and characteristic level.

Answer: True

Using mass change, fields can be changed at characteristic, operation, andheader level.

15. The work area is used to define which areas are offered as selection criteriaon entering the Workbench.

Answer: True

The work areas for the Engineering Workbench are defined in Customizingand also contain specifications for the selection criteria. +

16. Inspection characteristics are connected to engineering change managementas objects.

Answer: False

No master inspection characteristics from QM are connected to engineeringchange management. The objects from the classification system areconnected to engineering change management.

268 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 279: Plm412 en Col62 Fv Part a4

PLM412 Test Your Knowledge

17. By using engineering change management, different validity statuses canexist for an inspection plan.

Answer: True

The change master record (change number) contains a valid-from date, fromwhich changes are valid. As a result of this, the same inspection plan canhave different validity statuses.

18. The change master record can be structured in such a way that changes canonly be made to inspection plans, but not to materials, with one changenumber.

Answer: True

When you create a change master record, you can define which objects canbe changed with the change number.

19. It is not possible to carry out an inspection according to specifications froman inspection plan and a material specification.

Answer: False

According to the inspection type setting in the material, both thespecifications from the inspection plan and from the material specificationare taken into consideration at inspection lot creation.

20. The material specification can supplement the specifications from theinspection plan.

Answer: True

The material specification is an inspection specification that is valid in allclients for the material. It can therefore supplement the specifications fromthe inspection plan.

21. The specifications from the material specification are attached to the lastoperation in the inspection lot.

Answer: True

If specifications from the material specification are also copied to theinspection lot, these are attached with special characteristic numbers to thelast operation in the inspection lot.

2006/Q2 © 2006 SAP AG. All rights reserved. 269

Page 280: Plm412 en Col62 Fv Part a4

Test Your Knowledge PLM412

22. Flexible inspection characteristics can be used at inspection lot creation.

Answer: True

The inspection specifications currently required can be selected from a�super task list� during inspection lot creation. The tolerance specificationscan be changed.

23. The use of flexible inspection specifications is linked to an authorization.

Answer: True

To define which user is allowed to use the flexible inspection specificationsfunction, an authorization can be used.

24. The flexible inspection specifications function is not always available inthe standard system.

Answer: False

Flexible inspection specifications are implemented using a BAdI.Filter-dependent implementations are required for this BAdI so that theinspection types function with the corresponding inspection lot origin canbe used.

25. You can include multiple specifications in all task lists.

Answer: False

The multiple specifications can only be included in the inspection plans(task list type Q).

26. The multiple specifications can be used in the complete inspection process.

Answer: True

Using multiple specifications influences the entire inspection processing inquality management, from the inspection planning, to the results recording,through to the certificate creation.

27. The multiple specifications can be displayed in the results recording andat the usage decision.

Answer: True

In the results recording and at the usage decision, you can use the tab pageto display multiple specifications for specifications and valuations for theobjects.

270 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 281: Plm412 en Col62 Fv Part a4

Unit 4Results Recording

Unit OverviewIn this unit, you learn how to record inspection results based on the specificationsfrom inspection planning. It also covers the different options and processes forresults recording.

Unit ObjectivesAfter completing this unit, you will be able to:

� Record results for inspection characteristics.� Explain the different valuation options for inspection results.� Describe the processes in results recording.

Unit ContentsLesson: Recording and Valuating Inspection Results.. . . . . . . . . . . . . . . . . . . . .272

Exercise 13: Results Recording Worklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .297Exercise 14: Process-Optimized Results Recording � OptionalExercise... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .301Exercise 15: Copy Inspection Results Function in InspectionProcessing... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .305

2006/Q2 © 2006 SAP AG. All rights reserved. 271

Page 282: Plm412 en Col62 Fv Part a4

Unit 4: Results Recording PLM412

Lesson: Recording and Valuating Inspection Results

Lesson OverviewIn accordance with the specifications from inspection planning, the inspectionresults are recorded in the system with relation to the inspection lot. The differentoptions for results recording and characteristic valuation are shown here.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Record results for inspection characteristics.� Explain the different valuation options for inspection results.� Describe the processes in results recording.

Business ExampleYou record and process inspection results for inspection characteristics in resultsrecording.

The recorded inspection results document the inspected properties of a product,enable evaluations, and are consequently important for quality control.

You can use process-optimized results recording to record inspection results for alloperations, inspection points, or inspection lots depending on your needs.

272 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 283: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Recording and Valuating Inspection Results

Inspection Results Recording: Access and ProcessFlow

Figure 128: QM Inspection Process: Results Recording

The following conditions must be met to record inspection results:

� Inspection characteristics have been created.� Inspection specifications have been assigned to the inspection lot

(for example, inspection characteristics from the task list or materialspecification).

� Sample determination has been performed.

The current processing status of an inspection lot is documented by the inspectionlot status.

Depending on the settings in the control indicator for the inspection characteristic,you must or can record inspection results for the characteristic.

The valuation for the inspection characteristic occurs automatically based onthe valuation mode defined in the sampling procedure. Manual valuation is alsopossible.

If certain prerequisites are fulfilled, the system can automatically close thecharacteristic.

2006/Q2 © 2006 SAP AG. All rights reserved. 273

Page 284: Plm412 en Col62 Fv Part a4

Unit 4: Results Recording PLM412

Figure 129: Results Recording: Access

The most efficient way to record results involves the worklist.

� You can select the inspection lots for processing according to suitable criteriausing the worklist. For example:

� Results recording for equipment/functional locations� Results Recording for Physical Samples� Results recording for master inspection characteristics

In addition, you can access results recording using one of the following singlefunctions:

� Inspection result for operation� Inspection result for inspection point� Inspection result for physical sample� Inspection result for sample� Inspection result for delivery in sales & distribution

Depending on which function you use to access results recording, you may need toenter additional data, such as, sample number, inspection point, or partial lot.

274 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 285: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Recording and Valuating Inspection Results

Figure 130: Results Recording: Worklist

Through the user settings, you can make individual settings for results recordingand thereby adapt the process to suit your requirements.

With a user-specific variant, you can set up the selection criteria as required(selection variant). In addition, you can define how the information is to beformatted in the tree (display variant or layout).

� You make the settings for the selection variant on the selection screen forthe worklist.

� You make the settings for the display variant on the entry screen usingthe Select layout icon.

The system only displays objects in the worklist (inspection lots, operations) forwhich you have processing authorization. The objects of the tree are displayeddifferently depending on the input requirements.

On the entry screen, you can easily navigate between the individual processingobjects. After inspection lot selection, you can automatically access the firstoperation with characteristics to be processed.

Using the integrated graphic display, you can call up a histogram, a run chart, or aquality control chart in the screen area below the entry area.

The characteristic valuations that are executed are immediately displayed in theoverview tree (worklist). In addition, the graphic display is updated.

You can use the user settings (the icon in the application toolbar) to influencethe worklist display in transaction QE51N. You can set the displayed objects (suchas, z.B. outstanding characteristics only) and also the type of display.

2006/Q2 © 2006 SAP AG. All rights reserved. 275

Page 286: Plm412 en Col62 Fv Part a4

Unit 4: Results Recording PLM412

Figure 131: Processing status

The processing status documents the current processing status of the inspectioncharacteristic or partial sample.

This processing status of the inspection characteristics is relevant for the inspectioncompletion with the usage decision. If there are still outstanding characteristics,the inspection completion (= inspection cancellation) must be confirmed whenthe usage decision is made. The inspection cancellation can only be made, ifyou have the appropriate authorization.

After the usage decision has been made, changes cannot be made to thecharacteristics.

Exception: Unprocessed long-term characteristics.

Figure 132: Results Recording: Views

276 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 287: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Recording and Valuating Inspection Results

Four main views are offered for the characteristic overview screen:

� General: For recording summarized values and single values� Summarized: For recording summarized values� Unit to be inspected: For recording single values for units to be inspected� Indicator: For displaying important indicators

You can predefine the view for the characteristic overview screen in resultsrecording:

� For each inspection type in Customizing� In the inspection plan at operation level� Directly in results recording with user settings

Figure 133: Results Recording by Unit to be Inspected

Results recording for units to be inspected is a possible recording view for thecharacteristic overview screen for the single values for a unit to be inspected. Onthis screen, you can in general only make entries in fields that are relevant forsingle value recording. The screen is hidden, if there are no characteristics withoriginal-value recording at operation level.

Results recording for units to be inspected is preset in the:

� Inspection type in Customizing� Task list at operation level� User settings

Step-by-step results recording for a unit to be inspected occurs for allcharacteristics. A unit to be inspected corresponds in this function to a singleunit or a serial number.

2006/Q2 © 2006 SAP AG. All rights reserved. 277

Page 288: Plm412 en Col62 Fv Part a4

Unit 4: Results Recording PLM412

Figure 134: Recording Configuration

You can use the recording configuration to automate the results recordingprocess. When recording inspection results, certain functions are performed in thebackground if specific prerequisites are met.

The recording configuration is defined in Customizing for results recording andspecified in the plant settings for QM. Moreover, you can save the attributes of therecording configuration as a user parameter. The user settings take precedenceover the plant setting.

You can use the user settings to define the recording configuration directly inresults recording.

defines

278 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 289: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Recording and Valuating Inspection Results

Figure 135: Results Recording: Process Flow

The results recording process occurs based on the recording configuration.

The process flow shown above, in which the characteristic overview screen is notdisplayed and inspection results are recorded directly on characteristic singlescreens, is, above all, directed at users who only occasionally record inspectionresults. As a rule, a person who regularly records inspection results prefers torecord results on the characteristic overview screen.

Characteristic Valuation

Figure 136: Characteristic Valuation (1)

2006/Q2 © 2006 SAP AG. All rights reserved. 279

Page 290: Plm412 en Col62 Fv Part a4

Unit 4: Results Recording PLM412

The valuation type is defined in the sampling procedure using the valuation mode.The valuation mode contains a valuation rule.

Various valuation rules are used for the valuation of inspection characteristics.These are dependent on the characteristic type and sampling procedure that areassigned to the inspection characteristics.

Characteristics must be manually valuated, if they have no sampling procedureassigned in the task list or material specification, or have a sampling procedurewith manual valuation.

You can assign a sampling procedure with code valuation to a qualitativecharacteristic with characteristic attributes and summarized recording in the tasklist or material specification. If you confirm the attribute for a characteristic,the system copies the valuation defined in the selected set as the characteristicvaluation.

Figure 137: Characteristic Valuation (2)

During characteristic valuation based on tolerance specifications, the characteristicis accepted if the mean value is within the tolerance range. The standard deviationis not important in this instance.

During a variable inspection for quantitative inspection characteristics, thevaluation occurs based on the s-method (ISO 3951). The s-method can be setfor a one-sided or two-sided tolerance range. The valuation for the inspectioncharacteristic occurs according to a n-k sampling plan using the mean value andstandard deviation for the measured values.

280 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 291: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Recording and Valuating Inspection Results

During an attributive inspection, the valuation for the inspection characteristicoccurs based on the number of nonconforming units or number of defectscorresponding to an n-c or n-c-d sampling plan.

Inspection characteristics can be valuated based on action limits for a control chart.

Further valuation procedures can be implemented using function modules.

Variants for Inspection Results Recording

Figure 138: Process-Optimized Results Recording

Process-optimized results recording enables flexible tabular characteristicprocessing. In this way, you can record inspection results exactly for the recordingprocess and work center.

The standard system contains the following recording options:

� Results recording for a master inspection characteristic for all inspection lotsand operations

� Results recording for inspection characteristics for all inspection lots andoperations

� Results recording for several inspection points (physical samples, equipment)in one inspection lot and operation

2006/Q2 © 2006 SAP AG. All rights reserved. 281

Page 292: Plm412 en Col62 Fv Part a4

Unit 4: Results Recording PLM412

Figure 139: Results Recording for Master Inspection Characteristic

You can process the results for one master inspection characteristic on one screen,in table form, and for all inspection lots. This function can be used, for example,when a characteristic is to be inspected for different materials/batches.

Figure 140: Results Recording for Several Inspection Lots

Recording screen for results recording for inspection characteristics for allinspection lots and operations.

282 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 293: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Recording and Valuating Inspection Results

Figure 141: Results Recording for Several Inspection Points

Recording screen for results recording for several inspection points within oneinspection lot and operation.

Figure 142: Results Recording for Several Physical Samples

Recording screen for results recording for several physical samples within oneinspection lot and operation.

2006/Q2 © 2006 SAP AG. All rights reserved. 283

Page 294: Plm412 en Col62 Fv Part a4

Unit 4: Results Recording PLM412

Figure 143: Unplanned Characteristics

After releasing an inspection lot for recording inspection results, you may alsohave to consider additional characteristics during results recording. You can createadditional inspection characteristics for the inspection lot within results recording.You can only use completely maintained master inspection characteristics(reference characteristic or complete copy model) as additional characteristics.

Specifications from the master inspection characteristic are copied to theunplanned characteristic. If the user is authorized to change master inspectioncharacteristics, they can make changes to the specifications that have been copied(for example, tolerances, target value).

It depends on the Sampling procedure control indicator in the master inspectioncharacteristic, whether a sampling procedure is assigned. If the indicator is notset, the sampling procedure is used that has been set in Customizing for QM atplant level. If no sampling procedure has been entered in Customizing, a 100%inspection is performed.

The characteristic number for the first unplanned characteristic is set in QMCustomizing at client level.

If the inspection plan and inspection lot have been approved, you cannot includeadditional unplanned characteristics.

284 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 295: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Recording and Valuating Inspection Results

Figure 144: Change Documents for Inspection Results

Change documents can be written for certain inspection characteristics todocument changes made to already recorded inspection results. The changedocuments contain data on the changed field, the time the change was made,or the person who made the change. In this way, all changes to an inspectioncharacteristic can be completely monitored.

Change documents are written for inspection characteristics, if:

� The control indicator for change documents during results recording is setin the characteristic

� Results recording has been completed and saved for the inspectioncharacteristic, and the inspection characteristic has been reset for processing

Change documents are created if changes are made in results recording for:

� Physical sample� Inspection point� Single value� Classed recording

2006/Q2 © 2006 SAP AG. All rights reserved. 285

Page 296: Plm412 en Col62 Fv Part a4

Unit 4: Results Recording PLM412

Copy Inspection Results Function

Figure 145: Business Background for Copy Inspection Results Function

The Copy Inspection Results function can support many business processes.

It is particularly useful for recurring inspections such as deadline monitoring ofbatches, calibration inspections (test equipment inspections), and stability checks.Some characteristics must only be checked once whereas others must be checkedevery time. For the sake of clarity, all inspection results must nevertheless beavailable in each inspection lot.

The Copy Inspection Results function is also used to transfer inspection resultsfrom inspection lots during inspection (inspection lot origin 03) in inspection lotsat goods receipt for the order to the warehouse (inspection lot origin 04). Youcan also transfer inspection results from one inspection point to another whenrecording results. The same applies for semi-finished products and raw materialsfrom finished batches from which you want to transfer some characteristic valuesto the inspection lot for the finished product.

You can also the Copy Inspection Results function to use inspection results frominspection during production as starting values for a stability study.

286 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 297: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Recording and Valuating Inspection Results

Figure 146: Copy Inspection Results Function: Selecting the Source Data

The first challenge in the process is to select the source inspection lot correctly.The Copy Inspection Results function always begins from a particular inspectionlot.

The data selection uses the inspection lot data to select process-related data in thesystem. You can define different rules for data selection. Data selection can beinitiated during inspection lot processing or during results recording.

2006/Q2 © 2006 SAP AG. All rights reserved. 287

Page 298: Plm412 en Col62 Fv Part a4

Unit 4: Results Recording PLM412

Figure 147: Copy Inspection Results Function: Characteristic Mapping

If an inspection lot is found as a data source, the correct results value must beassigned to the individual characteristics of the target inspection lot. You mayalso need to take inspection operations and inspection points into account for theassignment. When the data is transferred successfully to the target inspection lot,the results data origin is set to the planned value set in Customizing in Settings forthe Copy Inspection Results Function.

Key fields for characteristic mapping can depend on the process.

288 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 299: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Recording and Valuating Inspection Results

Figure 148: Selection and Mapping when Copying Inspection Results

Process-related selection and mapping were carried out using filter-dependentBusiness Add Ins (BAdIs). SAP provides different sample implementationsfor this purpose. BAdI technology enables customers to implement their ownselection and mapping procedures.

Features of the Copy Inspection Results function in inspection lot processing:

� When you create an inspection lot manually or automatically, you cantransfer values for the inspection characteristics to the inspection lotafter sample calculation. The Copy Inspection Results function is startedautomatically at the end of the sample calculation or you start it manuallywhen you change an inspection lot based on the setting in Customizing.

� Once the data is transferred, the inspection lot status is RREC.� If transfer following the sample calculation is not successful because the

system cannot find a source object, you can initiate the Copy InspectionResults function when you change the inspection lot.

Features of the Copy Inspection Results function in results recording:

� On the initial screen for results recording, you can copy data to thecharacteristics of the current operation or inspection point (but not to theentire inspection lot).

� You can start the Copy Inspection Results function manually from the menuat any time.

2006/Q2 © 2006 SAP AG. All rights reserved. 289

Page 300: Plm412 en Col62 Fv Part a4

Unit 4: Results Recording PLM412

A transfer log (application log), which can be displayed using the menu, is alwaysgenerated.

Other Options in Results Recording

Figure 149: Mobile Results Recording

From release 4.6C, quality management supports mobile results recording.

With mobile results recording you can record inspection results using a mobiledevice on site. This results data can later be transferred to the SAP System. In theSAP System, you determine which inspections are to be recorded using a mobiledevice in the worklist �Mobile Results Recording� (transaction [QEH1]). Afteryou have done this, there is an allocation at inspection operation level, determiningwhich inspector is to inspect with what device.

You can find information about this application on SAP Service Marketplacehttp://service.sap.com.

To perform mobile results recording, you first need to define �Mobile Devices� inCustomizing (QM→ Quality Inspection→ Subsystems→ Define Applicationsfor Mobile Recording).

290 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 301: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Recording and Valuating Inspection Results

Figure 150: Worklist for Mobile Results Recording

Mobile results recording occurs as follows:

� Creation of allocations: In the SAP system, certain inspection operationsare designated for mobile results recording by an inspector. This designationis based on allocations, which are created and monitored in a worklist(transaction QEH1) for this particular purpose.

� Transfer of inspection operations: Based on the allocations created, theinspection operations (including the inspection characteristic specifications)are transferred to the mobile recording device using BAPIs. The call isinitiated by the external recording facility.

� Mobile recording of results: The inspector uses the mobile recordingdevice to record the results.

� Confirming the Results Data to the SAP system: This transfer also occursusing BAPIs and is triggered by the external recording devices.

2006/Q2 © 2006 SAP AG. All rights reserved. 291

Page 302: Plm412 en Col62 Fv Part a4

Unit 4: Results Recording PLM412

Figure 151: Results Recording on the Internet

From Release 4.6C, it is possible to record results based on characteristics onthe Internet. The transaction for this service is QEW01 and it can be used fromexternal locations (Internet) and internally (Intranet).

A worklist appears, from which the user can choose an inspection lot, when thethe service is accessed. Results recording can be performed for all operations. Youcan record summarized results (measured values, mean values, attribute codes,number of defective units, number of defects), single values (single measuredvalues, number of defects), and comments for an inspection characteristic.

This service is useful for:

� Results recording at the vendor's (source inspection)� Internal results recording: Internally, the service can be used to record

results as normal.

The identification process in the SAP system is based on the alias. Therefore, eachSAP user must have an alias assigned to them (transaction SU01). A selectionvariant must also be created for each user in the SAP system. This can be doneusing transaction QEW01V. The selection variant is used to restricts a user'sworklist.

The following inspection lots cannot be selected: Inspection lots with inspectionpoint processing, inspection lots with partial lots, and inspection lots that require adigital signature.

292 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 303: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Recording and Valuating Inspection Results

Figure 152: Digital Signature

You can specify that a user must have a digital signature to be able to carry outcertain business transactions in the SAP system. The digital signature enablesyou to meet the security requirements stipulated in the Good ManufacturingPractices (GMP) with regard to the execution of these transactions. The digitalsignature ensures that a transaction can only be carried out by users with specialauthorization. The user identification is unique and cannot be forged. The name ofthe user is documented together with the signed transaction and the date and time,and cannot be manipulated afterwards.

The digital signature has been implemented for the following transactions in QM:

� Saving inspection results for an inspection lot� Recording and changing the usage decision for an inspection lot� Manual confirmation of a physical-sample drawing for an inspection lot

If you use digital signature during inspection results recording, the user nameis stored in the characteristic result. You use the QM material authorizationgroup to define which transactions in QM require a digital signature. TheQM material authorization group is defined in Customizing and is assignedin the Quality Management view of the material master.

The digital signature has been implemented in the SAP system using SecureStore and Forward (SSF). SSF allows you to link various security products thatuse different identification procedures. After three unsuccessful attempts, thetransaction is canceled.

2006/Q2 © 2006 SAP AG. All rights reserved. 293

Page 304: Plm412 en Col62 Fv Part a4

Unit 4: Results Recording PLM412

Figure 153: Printing Inspection Results

Inspection lot information can be read from the database using a report and printedin an inspection report for the inspection lot. You use the selection criteria forinspection lots to define whether results should be printed for certain inspectionlots. In the standard system, the SAPScript formula QM_INSP_RESULT is usedfor the inspection lot-based printing of results.

On the selection screen for results printing, you can define additional options forcontrolling the output. For example:

� Printing inspection descriptions for a characteristic� Long texts for the usage decision� Information for recorded defects� Data on the samples for the characteristic� Printing of single values or classed values

Hint: To print inspection results, use transaction QGA3.

The inspection list application toolbar (transaction QA32/QA33) containsa pushbutton for printing the inspection results.

Hint: You can use the QG_INSP_RESULT_PRINT BAdI to influence thedocument output when the results are printed. A sample implementationis provided for the BAdI. You can use transaction QCC5 to access theBAdIs for quality management.

294 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 305: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Recording and Valuating Inspection Results

Figure 154: Subsystem Interface (QM-IDI)

The QM system uses the QM-IDI Interface (�Inspection Data Interface in QualityManagement�) to access an open interface for external systems. This interfacewas designed for the exchange of quality data for inspection processing. QMprovides the external system with specifications for the quality inspection. Thequality inspection is then carried out using the external system and the results datais transferred back to the QM System.

The transfer of data between the subsystem and QM occurs simultaneously asdirect program-to-program communication. The subsystem initiates both therequest for the inspection specifications from QM and the confirmation of resultsdata.

SAP provides function modules for the transfer of inspection specifications andthe confirmation of inspection results. These function modules can be called upfrom �non-SAP systems� and run in the QM system.

For more information about QM-IDI, see the SAP Library under

SAP ERP Central Component→ Logistics→ Quality Management→ Interfaces.

2006/Q2 © 2006 SAP AG. All rights reserved. 295

Page 306: Plm412 en Col62 Fv Part a4

Unit 4: Results Recording PLM412

296 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 307: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Recording and Valuating Inspection Results

Exercise 13: Results Recording Worklist

Exercise ObjectivesAfter completing this exercise, you will be able to:� Record inspection results for a planned inspection using the results recording

worklist in the system.� Valuate recorded inspection results manually and close the inspection

characteristics.

Business ExampleYou are responsible for recording inspection results for certain materials in yourcompany. You use worklists for selecting inspection lots.

A manual valuation of inspection results is planned for some inspectioncharacteristics.

Task 1: Results recording worklistThe SAP system contains various transactions that you can use to recordinspection results. You can use transaction QE51N for �general� access to theresults recording. In the selection screen, you can choose �dynamic selections� toaccess the many selection options that are available.

1. Use the results recording worklist to select inspection lots for materialT-BQ1##.

How many inspection lots for inspection lot origin 05 are in your worklist?____________________________________________________________

Why are all the inspection lots for material T-BQ1## not displayed in thisworklist?

____________________________________________________________

Task 2: Results Recording for the Planned InspectionCharacteristicsYou can carry out the results recording for the individual inspection characteristicsof the inspection lots in accordance with the specifications in inspection planning.

1. Record inspection results for the single characteristics of the inspection lotsin your worklist. Do not make a usage decision for the inspection lots yet.

2006/Q2 © 2006 SAP AG. All rights reserved. 297

Page 308: Plm412 en Col62 Fv Part a4

Unit 4: Results Recording PLM412

Solution 13: Results Recording WorklistTask 1: Results recording worklistThe SAP system contains various transactions that you can use to recordinspection results. You can use transaction QE51N for �general� access to theresults recording. In the selection screen, you can choose �dynamic selections� toaccess the many selection options that are available.

1. Use the results recording worklist to select inspection lots for materialT-BQ1##.

How many inspection lots for inspection lot origin 05 are in your worklist?____________________________________________________________

Why are all the inspection lots for material T-BQ1## not displayed in thisworklist?

Continued on next page

298 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 309: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Recording and Valuating Inspection Results

____________________________________________________________

a) Logistics→ Quality Management→ Quality Inspection→ Worklist→ Results Recording (QE51N)

The selection screen for inspection lots in the results recording worklistappears. Use the Material tab page to select inspection lots.

Field name or data type ValuesPlant 1000Material T-BQ1##Inspection lot origin 05

Exit the selection screen by choosing the F8 function key or thepushbutton Execute.

The characteristic overview for results recording appears for theinspection lots you selected. Your current worklist is displayed on theleft side of the screen. On the right side of the screen, the characteristicoverview appears for the first inspection lot to be processed in yourworklist.

At least 2 inspection lots of inspection lot origin 05 should be inyour worklist. One inspection lot should contain the inspectionspecifications from the material specifications. The other inspection lotshould have specifications from the inspection plan.

This worklist contains only inspection lots for which you can recordinspection results. Inspection lots are not displayed in this worklist ifthey do not have planned characteristics and are therefore defined fordefects recording.

Task 2: Results Recording for the Planned InspectionCharacteristicsYou can carry out the results recording for the individual inspection characteristicsof the inspection lots in accordance with the specifications in inspection planning.

1. Record inspection results for the single characteristics of the inspection lotsin your worklist. Do not make a usage decision for the inspection lots yet.

a) Record the inspection results for the first inspection lot (withmaterial specification) on the characteristic overview screen. Onthe characteristic overview screen, you can record inspection resultsfor characteristics with summarized recording and with single-resultrecording.

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 299

Page 310: Plm412 en Col62 Fv Part a4

Unit 4: Results Recording PLM412

The first characteristic is defined for summarized results recording witha characteristic attribute. As a result, you can use the input help in thefield Result to select an attribute code from the planned characteristicattributes and to copy this code to the field with a double-click. Afterchoosing the Return key, the characteristic is valuated and closed basedon the settings in the characteristic control indicators and the recordingconfiguration. The characteristic is flagged as valuated and completedin the worklist on the left side of the screen.

The second characteristic is defined for single-results recording.According to the specifications, several items must be inspected. Afterentering the first result in the Result field and choosing the Return key,the first result is valuated and you can now enter the other 4 inspectionresults. Enter additional single results for the characteristic. After youhave recorded all the single results, the characteristic is automaticallycompleted again. The display in the worklist is automatically updated.

Save your entries.

Expand the second inspection lot in your worklist and double-click onthe first operation in the inspection lot. The characteristic overviewagain appears on the right side of the screen and you can recordinspection results in the same way as you did for the first inspection lot.

Hint: In results recording, you can use the pushbuttonTrigger to complete the inspection characteristic processingearly.

Hint: Provided that a usage decision has not been made forthe inspection lot, you can use the pushbutton to reset thecompleted inspection characteristics for processing.

Save your entries.

Do not make a usage decision for the inspection lots yet.

300 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 311: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Recording and Valuating Inspection Results

Exercise 14: Process-Optimized ResultsRecording � Optional Exercise

Exercise ObjectivesAfter completing this exercise, you will be able to:� Record results for a master inspection characteristic for all inspection lots

and operations.

Business ExampleCertain materials are often used in your company. In general, these materials havevery short lead times at quality control. You are responsible for the summarizedresults recording of certain inspection characteristics. You use tabular resultsrecording so that you do not have to process each inspection lot individually andcan record results for all inspection lots and operations.

Task:Results recording for master inspection characteristic

1. You are responsible for the results recording of certain inspectioncharacteristics at goods receipt.

Record inspection results for the master inspection characteristics MK03-00and MK04-00 for material T-BQ2##.

Use results recording for all inspection lots to do this.

2006/Q2 © 2006 SAP AG. All rights reserved. 301

Page 312: Plm412 en Col62 Fv Part a4

Unit 4: Results Recording PLM412

Solution 14: Process-Optimized ResultsRecording � Optional ExerciseTask:Results recording for master inspection characteristic

1. You are responsible for the results recording of certain inspectioncharacteristics at goods receipt.

Record inspection results for the master inspection characteristics MK03-00and MK04-00 for material T-BQ2##.

Continued on next page

302 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 313: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Recording and Valuating Inspection Results

Use results recording for all inspection lots to do this.

a) Logistics→ Quality Management→ Quality Inspection→ Worklist→Variants for Results Recording→ For All Inspection Lots (QE72)

The screen Selection: Tabular Results Recording for Inspection Lotsappears. Enter the following data on the selection screen:

Inspection lot selection:

Field name or data type ValuesPlant 1000Material T-BQ2##

Selection of characteristic:

Field name or data type ValuesMaster inspection characteristic MK03-00 to MK04-00

Choose the F8 function key. A worklist appears that contains inspectionlots that correspond to the selection criteria. Select all inspection lotsby choosing the F5 function key or the pushbutton Select all. Choosethe F8 function key or the pushbutton Change inspection results. Theresults recording screen for the selected inspection lots appears.

On the tabular overview, the inspection lot numbers and thecorresponding materials appear in the upper screen area. In the centerof the screen, the inspection characteristics and the correspondinginspection specifications are displayed. You can enter the summarizedinspection results for the inspection lots in the Result field.

Hint: Note that during tabular results recording, onlysummarized inspection results can be recorded. You can onlyrecord single values in the single screen for the characteristic.

After you have recorded inspection results, close results recording forthe characteristics by choosing the pushbutton Save.

Hint: You can also use tabular results recording to recordinspection results for several inspection points in an inspectionlot or for a specific master inspection characteristic. You canopen the initial screen for tabular results recording by choosingLogistics→ Quality Management→ Quality Inspection→Worklist→ Variants for Results Recording.

2006/Q2 © 2006 SAP AG. All rights reserved. 303

Page 314: Plm412 en Col62 Fv Part a4

Unit 4: Results Recording PLM412

304 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 315: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Recording and Valuating Inspection Results

Exercise 15: Copy Inspection ResultsFunction in Inspection Processing

Exercise ObjectivesAfter completing this exercise, you will be able to:� Use the copy inspection results function in inspection processing� Explain the times at which you can transfer data

Business ExampleYou can use the copy inspection results function in inspection lot processing andin results recording. You want to use this function in conjunction with recurringinspections of batches. In results recording, you want the system to propose theresults of the last inspection.

Task 1: Recurring inspections of batches for a materialThe batches for a material must be inspected at regular intervals. Inspection lotsof inspection lot origin 09 are used for this. These inspection lots are alwaysgenerated in time for the next inspection date using a periodic job.

1. In plant 1000, select all inspection lots for material TAQ5##. To do this, usethe inspection list in the selection transaction (QA33).

How many inspection lots are there for the material?_____________________

How many inspection lots for the material havealready been completed with the usage decision?___________________________________________________

2. Document the following data for the completed inspection lot:

Batch:_________________________________________________

Inspection characteristic short text:______________________________________

Inspection result:_____________________________________________

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 305

Page 316: Plm412 en Col62 Fv Part a4

Unit 4: Results Recording PLM412

Task 2: Copy Inspection Results Function inInspection ProcessingThe next recurring inspection for the material and batch from exercise 1, part 2 isdue. The corresponding inspection lot has already been created by a job.

Record inspection results for this inspection lot. To do this, use the resultsrecording worklist (transaction QE51N) and select all inspection lots for yourmaterial T-AQ5##.

1. How many inspection lots are in your worklist? _________

2. What do you notice about the inspection lot with the batch from exercise 1,part 2 when you go to results recording?

_______________________________________________________

_______________________________________________________

3. What is the processing status of the characteristic?

Status:_________ Short text: __________________________________

306 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 317: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Recording and Valuating Inspection Results

Solution 15: Copy Inspection ResultsFunction in Inspection ProcessingTask 1: Recurring inspections of batches for a materialThe batches for a material must be inspected at regular intervals. Inspection lotsof inspection lot origin 09 are used for this. These inspection lots are alwaysgenerated in time for the next inspection date using a periodic job.

1. In plant 1000, select all inspection lots for material TAQ5##. To do this, usethe inspection list in the selection transaction (QA33).

How many inspection lots are there for the material?_____________________

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 307

Page 318: Plm412 en Col62 Fv Part a4

Unit 4: Results Recording PLM412

How many inspection lots for the material havealready been completed with the usage decision?___________________________________________________

a) Overview of all inspection lots in recurring inspections for materialT-AQ5##:

Logistics→ Quality Management→ Quality Inspection→ Worklist→Inspection→ Display Data (QA33)

Enter the following data on the initial screen:

Field name or data type ValuesPlant 1000Inspection Lot Origin 09Material T-AQ5##

Exit the selection screen by pressing F8 or choosing Execute ( ).

Number of inspection lots for material T-AQ5##: at least 4 inspectionlots should be listed.

Sort your inspection lots according to the system status. To do so, selectthe System Status column in the inspection list and then click Sort inAscending Order ( ) or Sort in Descending Order ( ).

There is at least 1 inspection lot that has already been completed withthe usage decision (System Status UD, , and so on).

Hint: If necessary you can adjust the layout of the inspectionlist to include the batch, for example. To do this, use thepushbutton for changing the layout in the application toolbar,or use the key combination Ctrl + F9.

2. Document the following data for the completed inspection lot:

Batch:_________________________________________________

Inspection characteristic short text:______________________________________

Continued on next page

308 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 319: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Recording and Valuating Inspection Results

Inspection result:_____________________________________________

a) Data of the completed inspection lot:

Field name or data type ValuesBatch TAQ5##-3Short text for inspection characteristic DensityInspection Result 1,190

Task 2: Copy Inspection Results Function inInspection ProcessingThe next recurring inspection for the material and batch from exercise 1, part 2 isdue. The corresponding inspection lot has already been created by a job.

Record inspection results for this inspection lot. To do this, use the resultsrecording worklist (transaction QE51N) and select all inspection lots for yourmaterial T-AQ5##.

1. How many inspection lots are in your worklist? _________

a) Results recording worklist:

Logistics→ Quality Management→ Quality Inspection→ Worklist→ Results Recording (QE51N)

Field name or data type ValuesPlant 1000Inspection Lot Origin 09Material T-AQ5##

Exit the selection screen by pressing F8 or choosing Execute ( ).

At least 3 inspection lots should be in the worklist.

2. What do you notice about the inspection lot with the batch from exercise 1,part 2 when you go to results recording?

_______________________________________________________

_______________________________________________________

a) In results recording for the inspection lot with the batch TAQ5##-3, thevalue 1.190 is proposed as the result. This is due to data transfer fromthe preceding inspection lot when accessing results recording.

3. What is the processing status of the characteristic?

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 309

Page 320: Plm412 en Col62 Fv Part a4

Unit 4: Results Recording PLM412

Status:_________ Short text: __________________________________

a) The characteristic has the status 2 Processed.

310 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 321: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Recording and Valuating Inspection Results

Lesson Summary

You should now be able to:� Record results for inspection characteristics.� Explain the different valuation options for inspection results.� Describe the processes in results recording.

Related Information

2006/Q2 © 2006 SAP AG. All rights reserved. 311

Page 322: Plm412 en Col62 Fv Part a4

Unit Summary PLM412

Unit SummaryYou should now be able to:� Record results for inspection characteristics.� Explain the different valuation options for inspection results.� Describe the processes in results recording.

312 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 323: Plm412 en Col62 Fv Part a4

PLM412 Test Your Knowledge

Test Your Knowledge

1. In results recording, inspection characteristics are always automaticallyvaluated and completed.Determine whether this statement is true or false.□ True□ False

2. By using process-optimized results recording, you can record the inspectionresults for several samples on one recording screen.Determine whether this statement is true or false.□ True□ False

3. Results recording is possible over the Internet.Determine whether this statement is true or false.□ True□ False

2006/Q2 © 2006 SAP AG. All rights reserved. 313

Page 324: Plm412 en Col62 Fv Part a4

Test Your Knowledge PLM412

Answers

1. In results recording, inspection characteristics are always automaticallyvaluated and completed.

Answer: False

Depending on how the recording configuration is set up (plant- oruser-dependent), the completion of characteristics takes place automatically.

2. By using process-optimized results recording, you can record the inspectionresults for several samples on one recording screen.

Answer: True

Process-optimized results recording enables you to record inspection resultsfor several inspection lots, samples, or inspection points on one screen.

3. Results recording is possible over the Internet.

Answer: True

Using Internet service QEW01, you can carry out results recording over theInternet. Inspection lots are selected using a user-specific selection variant.

314 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 325: Plm412 en Col62 Fv Part a4

Unit 5Defects Recording

Unit OverviewIn addition to recording inspection results for the planned inspectioncharacteristics, you can also record unplanned defects that arise in the inspectionprocess. In this unit you learn about defects recording and how it is linked tothe inspection process.

Unit ObjectivesAfter completing this unit, you will be able to:

� Plan defects recording using a confirmation profile, catalog profile, andreport type.

� Record defects at inspection lot, operation, or characteristic level.� Activate a quality notification from the created defect record.

Unit ContentsLesson: Defects Recording in Inspection Processing.. . . . . . . . . . . . . . . . . . . . .316

Exercise 16: Defects Recording for Inspection Lots .. . . . . . . . . . . . . . . . . .327

2006/Q2 © 2006 SAP AG. All rights reserved. 315

Page 326: Plm412 en Col62 Fv Part a4

Unit 5: Defects Recording PLM412

Lesson: Defects Recording in Inspection Processing

Lesson OverviewIn addition to recording inspection results for planned inspection characteristics,defects recording is another way of describing the current condition of a productor a material. Defects recording can take place for each inspection lot.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Plan defects recording using a confirmation profile, catalog profile, andreport type.

� Record defects at inspection lot, operation, or characteristic level.� Activate a quality notification from the created defect record.

Business ExampleIf you process an inspection lot, you can record results for the inspection in theform of characteristic values or defects. A defect is any property of a material,product, or process, that does not meet the specifications for an inspectioncharacteristic. You record defects with predefined defect codes, which aremaintained in the inspection catalogs.

Whether defects recording is needed, depends on the manufactured product andproduction process. Defect records can act as an important source of informationfor quality control in many different areas of production. They improve qualityand optimize the process, while also reducing costs and increasing productivity.

With QM, you can record defects in the form of defect records. You can analyzedefects and determine their causes using defect records. In this way, you candefine the tasks that are needed to eliminate the cause of the problem and stop itfrom recurring. You can create defect records in the system in the following ways:

� The system can automatically create defect records within results recording.� You can manually create defect records using the defects recording function.

316 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 327: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Defects Recording in Inspection Processing

Defects Recording: Access and Process Flow

Figure 155: QM Inspection Process - Defects Recording

Defects recording occurs using defect codes. You can define these defect codes incatalog type 9. The criticality and consequences of the defect are important whendeciding to which defect class the defect is assigned.

Depending on the specifications in the confirmation profile, the system takesyou immediately to the detail screen for defects recording. In this screen, youcan enter additional data for the defect (for example, defect location, assembly,serial number).

If a defect record is created automatically or manually, it is initially inactive.The system stores this inactive defect record internally as a quality notificationwith the status:

� �Defects Recording�� �Notification outstanding�

Compl.

The system can automatically trigger a workflow task or activate a qualitynotification using defect classes.

2006/Q2 © 2006 SAP AG. All rights reserved. 317

Page 328: Plm412 en Col62 Fv Part a4

Unit 5: Defects Recording PLM412

Figure 156: Defects Recording: Access

You can create defect records manually for an inspection lot at any time. If youperform an inspection with a task list or material specification, you can also recorddefects for an operation or characteristic.

In addition to the direct entry screen for defects recording, you can also switchto defects recording from the results recording transactions or when you makethe usage decision.

The system can automatically create defect records within results recording, if thecharacteristic is rejected during valuation. To automatically create defect records,automatic defects recording must be active in the characteristic control indicatorsand the corresponding defect codes must be assigned.

318 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 329: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Defects Recording in Inspection Processing

Planning for Defects Recording

Figure 157: Catalog Profile

The catalog profile contains a subset of code groups and codes from differentcatalog types.

You can use the catalog profile, for example, to plan which catalogs and codegroups are available to the user, based on the material, when results are recordedand notifications processed.

Hint: The catalog profile can only be defined at the level of the codegroup. You should try to ensure that code groups do not contain too manycodes. By limiting the number of codes, you ensure that you can latercreate suitable catalog profiles for your materials.

2006/Q2 © 2006 SAP AG. All rights reserved. 319

Page 330: Plm412 en Col62 Fv Part a4

Unit 5: Defects Recording PLM412

Figure 158: Planning Defects Recording

The following play an important part in recording defects:

� Report type� Catalog Profile� Confirmation profile

The report type can be assigned to a work center. In this way, the form and thevalue set (code groups) can be designed based on the work center.

The report type is freely definable (for example, visual inspection, function check,summarized defect report, individual defect report).

If there is no work center available because the inspection is to take place withoutan inspection plan, you can specify the catalog profile on the initial screen ofresults recording.

The report type can be proposed using the user parameter QFE.

In the confirmation profile, you define the type of information that you can recordfor a defect (such as, defect type, defect cause, defect location, task and defectvaluation). You can also define whether an entry for a confirmation object (suchas defect location, defect cause) is obligatory, optional or not required.

The confirmation profile and the report type are defined in Customizing (QualityManagement→ Quality Notification→ Defects Recording).

320 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 331: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Defects Recording in Inspection Processing

Figure 159: Determining a Catalog Profile for Defects Recording

A catalog profile is defined in the report type. You use indicators in the report typeto control how the system accesses the catalog profile.

If you always want to use the catalog profile from the report type, do not set theindicators for the notification type or the material.

If you want to use the catalog profile for the material, you must set the materialindicator. If the material does not have a catalog profile assigned to it, the systemtakes the profile from the report type.

If the indicator for the notification type is set, the system uses the catalog profilethat has been assigned to this notification type.

If both indicators are set (notification type and material), the catalog profileis determined in exactly the same way as for a manual creation of a qualitynotification, (that is, the catalog profile assigned to the material, takes precedenceover the profile that has been assigned to the notification type).

2006/Q2 © 2006 SAP AG. All rights reserved. 321

Page 332: Plm412 en Col62 Fv Part a4

Unit 5: Defects Recording PLM412

Defects Recording and Results Recording

Figure 160: Defects Recording/Activating the Quality Notification

When you record a defect, the system creates a quality notification with the status�Defects recording� and �Outstanding notification�.

You can activate a quality notification manually with this status, or the system canactivate the notification automatically. If a quality notification is activated, thestatus of this notification changes to �Outstanding notification�.

You can switch to a notification processing screen directly from the resultsrecording function using a pushbutton. This allows you to access the notificationprocessing functions when you record defects and also to define tasks at thisstage. When you transfer to the notification processing screen, the notificationis activated automatically, if tasks or executable data have been entered (forexample, priority or person responsible for processing).

When you record defects, you can also enter long texts for these defects on theoverview screen next to the defect codes.

322 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 333: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Defects Recording in Inspection Processing

Figure 161: Flow Variants for Inspection Processing / Defects Recording

Depending on the application and planning, defects recording can be performedaccording to certain variants.

Variant 1 represents the simplest form of defects recording available. If required,defects are recorded manually for an existing inspection lot on the basis of defectcodes.

If task lists (inspection plan, routing, master recipe, ...) are in use, you can recorddefects for both the inspection lot and operations from the task list.

If you are recording inspection results by characteristic, you can, in addition to theinspection results, record characteristic defects. Defects recording in this variantis called up manually, either when recording inspection results, or by accessingdefects recording for the characteristic. Using this variant, it is possible for you tobe very precise when recording defects.

If the control indicator for the inspection characteristic allows for automaticdefects recording, the system automatically switches to the dialog for defectsrecording when a characteristic is rejected, or it generates a notification in thebackground containing the defect code planned for the inspection characteristic.

2006/Q2 © 2006 SAP AG. All rights reserved. 323

Page 334: Plm412 en Col62 Fv Part a4

Unit 5: Defects Recording PLM412

Figure 162: Results Recording and Defects Recording

If the control indicator for the inspection characteristic is set for defects recordingand .no defect code is assigned to this characteristic, a dialog box appears whenthe characteristic is rejected and you can enter the defect code in this dialog box.

If the inspection is carried out in a subsystem, defect records can only be generatedautomatically. Note: defect codes must be assigned to the characteristic!

As soon as there are defect data records available for an inspection lot, anadditional tab page appears containing the recorded defects when you are makingthe usage decision.

324 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 335: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Defects Recording in Inspection Processing

Figure 163: Code Selection when Entering Defects Recording

You can use the QFM user parameter to have the system construct multiple fieldselection at the same time as it constructs the defects overview screen when youaccess defects recording. As a result, you can record defects directly withoutcalling up the input help (F4) for the defect type. This speeds up defects recordingby providing multiple selection.

You can set the user parameter as a user setting on the initial screen for defectsrecording and in results recording.

2006/Q2 © 2006 SAP AG. All rights reserved. 325

Page 336: Plm412 en Col62 Fv Part a4

Unit 5: Defects Recording PLM412

326 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 337: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Defects Recording in Inspection Processing

Exercise 16: Defects Recording forInspection Lots

Exercise ObjectivesAfter completing this exercise, you will be able to:� Record defects for an inspection lot.� Record defects for operations and characteristics in an inspection lot.

Business ExampleYou do not use a planned inspection for some materials, but record defects ifnecessary.

Other materials are inspected using the specifications from the inspection plan.In this case, you record additional defects for an operation or characteristic in anoperation if required.

Task 1: Defects Recording for Inspection LotsDefects recording for inspection lots is a simple and quick option for documentingand evaluating deviations or defects in an inspection.

1. The first inspection lot that you created in PLM412 is defined only fordefects recording because you did not plan any inspection characteristics forthis inspection lot. Record defects for this inspection lot.

Also record a long text for a defect item.

Hint: Inspection lots, which are only defined for defects recording,have the system status ICNC (Insp. completion w/o confirm.). If youonly want to process such inspection lots, you can select them usinga selection profile in the system.

Task 2: Defects recording for an inspectioncharacteristicIn connection with a planned inspection, you can carry out defects recording foran inspection characteristic, for an inspection operation or for an inspection lot.

1. You determine during results recording that the socket for a lamp ismechanically damaged. You record this defect for your inspection lot,for which the inspection specifications are from the inspection plan. Yourecorded this defect while inspecting the wattage of the lamps.

2006/Q2 © 2006 SAP AG. All rights reserved. 327

Page 338: Plm412 en Col62 Fv Part a4

Unit 5: Defects Recording PLM412

Solution 16: Defects Recording forInspection LotsTask 1: Defects Recording for Inspection LotsDefects recording for inspection lots is a simple and quick option for documentingand evaluating deviations or defects in an inspection.

1. The first inspection lot that you created in PLM412 is defined only fordefects recording because you did not plan any inspection characteristics forthis inspection lot. Record defects for this inspection lot.

Also record a long text for a defect item.

Hint: Inspection lots, which are only defined for defects recording,have the system status ICNC (Insp. completion w/o confirm.). If youonly want to process such inspection lots, you can select them usinga selection profile in the system.

a) Logistics -> Quality Management -> Quality Inspection -> Worklist ->Inspection -> Change Data (QA32)

or

Logistics→ Quality Management→ Quality Inspection→ Defects→Record for Inspection Lot (QF11)

When working with QA32:

Enter the following data on the selection screen:

Field name or data type ValuesSel. profile PLM412Material T-BQ1##

After exiting the selection screen, an overview appears for inspectionlots that are only intended for defects recording. Select the linecontaining the inspection lot and choose the Create defect pushbutton inthe application toolbar. The Defects Recording: Initial Screen appears.The inspection lot number and the report type are defaulted and bychoosing Enter, you access the defects overview for the inspection lot.

Continued on next page

328 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 339: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Defects Recording in Inspection Processing

You use the input help to choose the codes for the defect type.

Hint: The codes for defect types are defined in code groupsfor catalog type 9 Defect types. You can use a catalog profileto define which code group from catalog type 9 should beused for a certain material.

In the item overview for defects recording, you can switch to theeditor for entering an additional long text by choosing the pushbuttonLT for each defect item. This long text is copied to the defect itemin the notification.

Hint: You can use the pushbutton Edit notification to switchdirectly from defects recording to notification processing.

When you enter the notification processing, you may have toenter a �mandatory partner�. As the coordinator, enter youruser PLM412-## here.

Hint: You can also access defects recording by choosingLogistics→ Quality Management→ Quality Inspection→Inspection Lot→ Editing→ Change (QA02).

You can enter the inspection lot number on this screen and bychoosing the pushbutton Record defects the item overview fordefects recording is displayed for the inspection lot.

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 329

Page 340: Plm412 en Col62 Fv Part a4

Unit 5: Defects Recording PLM412

Task 2: Defects recording for an inspectioncharacteristicIn connection with a planned inspection, you can carry out defects recording foran inspection characteristic, for an inspection operation or for an inspection lot.

1. You determine during results recording that the socket for a lamp ismechanically damaged. You record this defect for your inspection lot,for which the inspection specifications are from the inspection plan. Yourecorded this defect while inspecting the wattage of the lamps.

a) Logistics→ Quality Management→ Quality Inspection→ Worklist→ Results Recording (QE51N)

On the selection screen, enter material T-BQ1## on the Material tabpage and make the selection by choosing the pushbutton Execute orthe F8 function key.

Expand the inspection lot with an inspection plan in your worklist anddouble-click on the characteristic in the second operation. On the rightside of the screen, the detail screen for this characteristic appears. Youcan use the pushbutton Defect .... (defect for the characteristic)to access defects recording. The report type is copied from thespecifications to the work center and you can immediately begin toselect defect codes. Choose code 3 Socket mechanically damaged fromcode group F-300. Exit defects recording using the Return key.

Save your entries.

Hint: You can also access defects recording for an inspectioncharacteristic using: Logistics→ Quality Management→Quality Inspection→ Defects→ Record for Characteristic(QF31)

330 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 341: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Defects Recording in Inspection Processing

Lesson Summary

You should now be able to:� Plan defects recording using a confirmation profile, catalog profile, and

report type.� Record defects at inspection lot, operation, or characteristic level.� Activate a quality notification from the created defect record.

Related Information

2006/Q2 © 2006 SAP AG. All rights reserved. 331

Page 342: Plm412 en Col62 Fv Part a4

Unit Summary PLM412

Unit SummaryYou should now be able to:� Plan defects recording using a confirmation profile, catalog profile, and

report type.� Record defects at inspection lot, operation, or characteristic level.� Activate a quality notification from the created defect record.

332 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 343: Plm412 en Col62 Fv Part a4

PLM412 Test Your Knowledge

Test Your Knowledge

1. Defects recording with relation to an inspection lot is possible.Determine whether this statement is true or false.□ True□ False

2. If an inspection characteristic is rejected, automatic defects recording cantake place.Determine whether this statement is true or false.□ True□ False

3. A material-dependent selection of defect codes cannot be planned.Determine whether this statement is true or false.□ True□ False

2006/Q2 © 2006 SAP AG. All rights reserved. 333

Page 344: Plm412 en Col62 Fv Part a4

Test Your Knowledge PLM412

Answers

1. Defects recording with relation to an inspection lot is possible.

Answer: True

Defects recording via an inspection lot is possible as long as the inspectionlot has not been completed yet with the usage decision.

2. If an inspection characteristic is rejected, automatic defects recording cantake place.

Answer: True

If the control indicator �Automatic defects recording� is set in the inspectioncharacteristic and if codes were assigned to the inspection characteristic whenit was rejected, automatic defects recording can take place in the background.

3. A material-dependent selection of defect codes cannot be planned.

Answer: False

Material-dependent defect code groups can be assigned via the catalogprofile.

334 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 345: Plm412 en Col62 Fv Part a4

Unit 6Usage Decision

Unit OverviewAn inspection is completed with a usage decision. The planning of the usagedecision and the effects of the usage decision are covered in this unit.

Unit ObjectivesAfter completing this unit, you will be able to:

� Make a usage decision for an inspection lot and understand the individualfunctions and effects of a usage decision.

� Plan UD codes.

Unit ContentsLesson: Inspection Completion with the Usage Decision .. . . . . . . . . . . . . . . .336

Exercise 17: Manual Usage Decision.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .349

2006/Q2 © 2006 SAP AG. All rights reserved. 335

Page 346: Plm412 en Col62 Fv Part a4

Unit 6: Usage Decision PLM412

Lesson: Inspection Completion with the Usage Decision

Lesson OverviewInspection lot processing is completed when a usage decision is made. A usagedecision can trigger other processes, for example, a stock transfer posting or arelease. In this lesson, you will learn about planning a usage decision and also thedifferent options for inspection completion with a usage decision.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Make a usage decision for an inspection lot and understand the individualfunctions and effects of a usage decision.

� Plan UD codes.

Business ExampleAfter results recording and inspection completion, you must make a usage decisionfor the inspected goods.

You can use the usage decision to make stock postings for inspection lots, thathave been created because of goods movements (for example, to unrestricted-usestock, blocked stock, scrap).

If you make a usage decision for an inspection lot, the following occurautomatically:

� A quality score is determined for the inspection lot.� The quality level (inspection stages for the next inspection lot) is updated.� The Quality Management information system is updated with statistical data.� Automatic follow-up actions (optional) are triggered.

336 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 347: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection Completion with the Usage Decision

Completing an Inspection with the Usage Decision

Figure 164: QM Inspection Process - Usage Decision

The usage decision is made using a UD code.

Once the usage decision has been made, the quality score is determined based onthe settings for the inspection type in the material master (Quality Managementview, inspection setup).

You can define various follow-up actions.

2006/Q2 © 2006 SAP AG. All rights reserved. 337

Page 348: Plm412 en Col62 Fv Part a4

Unit 6: Usage Decision PLM412

Figure 165: Usage Decision: Access

You can access the usage decision:

� Using the worklist� From results recording� Manual

Inspection lots for which there are no rejected inspection characteristics or defectscan be completed with an automatic usage decision.

Figure 166: Usage Decision: General

An inspection is completed when the usage decision is made.

338 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 349: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection Completion with the Usage Decision

You can only make the usage decision for an inspection lot if all requiredcharacteristics and all processed optional characteristics have been completed. Ifthere are long-term characteristics open at inspection completion, the completionis accepted and the inspection is noted as a short-term inspection.

After inspection completion, you can only record results for long-termcharacteristics that have not been completed.

In the transaction �Record usage decision� (QA11) or �Change usage decision�(QA12), you can make quantity transfer postings from quality inspection stock.

When you make the usage decision, you define, on the basis of the inspectionresults, whether the goods are to be accepted or rejected. While you are makingthe usage decision, you can also:

� Record defects� Activate quality notifications� Confirm activities to QM orders

Figure 167: Usage Decision: Effects

In stock-relevant inspection lots, stock postings are triggered by the usage decision.

The quality score influences the quality criterion in the vendor evaluation (onlyfor inspection lots for inspection lot origin 01).

The inspection stage (determined using the dynamic modification rule) is updatedin the quality level.

2006/Q2 © 2006 SAP AG. All rights reserved. 339

Page 350: Plm412 en Col62 Fv Part a4

Unit 6: Usage Decision PLM412

Planning a Usage Decision

Figure 168: Usage Decision: Selected Set

Catalog type 3 is used for the usage decision. All codes for usage decisionsmust be created here.

In the selected sets for the catalog type 3, you can group together the codes yourequire from the different code groups.

Recommendation:

According to the type of inspection required (goods receipt, production, stocktransfer), you should create your own selected set for the usage decision and assignthis to the corresponding inspection type in Customizing.

340 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 351: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection Completion with the Usage Decision

Figure 169: Edit Selected Sets

You can assign a posting proposal to every UD code in the selected set. When youmake the usage decision, the lot quantity for the corresponding stock posting isproposed. This quantity can be changed.

If the indicator �Stock screen in background� is set for the code, the quantityposting proposed in the usage decision code is automatically made. You can onlyset this indicator after you have entered something in the field for the postingproposal.

You can assign a follow-up action (for example, send a mail, change a status, ...)to the to the UD code in the selected set.

Follow-up actions are defined in Customizing (Quality Management→ QualityInspection→ Inspection Lot Completion→ Define Follow-Up Actions). You candefine chains of follow-up actions that the system performs in order.

The stock postings at the usage decision can be dependent on authorizations.

2006/Q2 © 2006 SAP AG. All rights reserved. 341

Page 352: Plm412 en Col62 Fv Part a4

Unit 6: Usage Decision PLM412

Usage Decision for an Inspection Lot

Figure 170: Recording the Usage Decision

Depending on the inspection type, a selected set can be proposed for the usagedecision in Customizing.

Depending on the inspection lot, there are different tab pages available when youare making the usage decision:

� Defect: Overview of the defect codes recorded for the inspection lot.� Characteristics: Depending on the selection filter, either all characteristics

in the inspection lot or only the relevant (rejected or open) characteristicsare displayed.

� Inspection lot stock: Displays the stock relevant quantities (quantity to beposted, quantity already posted) for the inspection lot.

� Inspection points: Overview of the inspection points and the valuation ofthe inspection points.

� Physical samples: Planned and unplanned physical samples includingvaluations.

� Equipment: Overview of equipment used and valuations of equipment(incl. follow-up actions)

� Multiple specification:Valuation of the characteristics according to standardspecifications and multiple specifications.

� Operation completion:Overview of the operation completion for eachoperation of the inspection lot.

342 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 353: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection Completion with the Usage Decision

Figure 171: Make usage decision

Inspection lots without a usage decision are displayed in a worklist. In this way,they can be more easily processed.

You can create a worklist for inspection lots that have outstanding stockpostings. This includes all inspection lots where the lot quantity has not been fullyposted. The worklist only contains inspection lots that are stock relevant and forwhich, at minimum, a short-term inspection has been completed.

You can generate a list of inspection lots for which a collective usage decisionis to be made. The list that is created contains all inspection lots that fulfill thefollowing criteria:

� Characteristic processing has been completed� No usage decision has been made� No characteristics were rejected� No defects were recorded

You can also create lists for inspection lots without inspection completion andinspection lots without usage decisions.

2006/Q2 © 2006 SAP AG. All rights reserved. 343

Page 354: Plm412 en Col62 Fv Part a4

Unit 6: Usage Decision PLM412

Figure 172: Automatic Usage Decision

If the goods in an inspection lot have no defects, then the system can automaticallycomplete the inspection. However, certain criteria need to be fulfilled. When anautomatic usage decision is made, the following occurs:

� The inspection lot is completed� The usage decision is made� The stock is posted and the goods are released from inspection stock.

An automatic usage decision can only be made if the following criteria arefulfilled:

� No characteristic was rejected� All required characteristics were confirmed and completed� There are no defect records for the inspection lot� An automatic usage decision is provided for the material (depending on

the inspection type).� A job is scheduled for the automatic usage decision.

The processing time for skipped inspection lots is calculated by adding the jobinterval and delay time.

The time is calculated from lot creation.

344 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 355: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection Completion with the Usage Decision

Figure 173: Quality Score

The quality score is a statistic that describes the quality of the inspected lot. Youuse function modules to define the procedure for calculating the quality score.

In the material master, you can define a quality score procedure for each inspectiontype. The entry in this field is copied to the inspection lot record when theinspection lot is created.

Figure 174: Usage Decision: Stock Posting

If an inspection lot is stock-relevant, you can use the functions of the usagedecision to post the inspection lot stock. On the basis of your stock postings, thesystem makes the corresponding postings in Materials Management (inventorymanagement).

For materials that are managed in batches, there must be a batch number availableat stock posting.

2006/Q2 © 2006 SAP AG. All rights reserved. 345

Page 356: Plm412 en Col62 Fv Part a4

Unit 6: Usage Decision PLM412

During an inspection, inspection lot stock can also be completely posted fromgoods receipt blocked stock using the following postings:

� To unrestricted-use stock� Remains in blocked stock, therefore no goods movements; only complete

posting of the inspection lot stock� To the sample (This means, two postings are made internally. The first is a

transfer posting to unrestricted-use stock and the second is a posting of thisquantity from unrestricted-use stock to the sample.)

� Return delivery to vendors

The system takes the quantities of materials destroyed during a quality inspectioninto consideration automatically when you make the stock postings for aninspection lot.

Figure 175: Proposed Batch Status Change

For materials that are handled in batches, the batch status can be changed inaccordance with the UD code.

The setting of defaults for batch status management occurs in the selected set.

346 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 357: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection Completion with the Usage Decision

Figure 176: Alternative Units of Measure in the Usage Decision

In usage decision transactions, as standard you can specify quantities for stockpostings only in the base unit of measure of the material.

You can use the QEVA_ALT_QTY_INPUT Business Add-In to define input help(F4 help) for quantity fields on the stock screen (Inspection lot stock tab page)when making a usage decision. This allows you to enter quantities in units ofmeasure other than the base unit of measure.

You can use BAdI methods and an implementation to define a dialog box whereyou can specify the quantity value for another unit of measure. This value mustthen be converted to the base unit of measure within the implementation. Thismeans that in the context of usage decisions, quantities can only be transferred toinventory management in the base unit of measure.

If no alternative unit of measure is entered in the material, not input help appearsfor the quantity fields on the stock screen.

Operation CompletionAs of mySAP ERP 2005 (ECC6.0), based on the operation, you can record avaluation during the results recording and then trigger follow-up actions. Thisallows you to document the exact process of an inspection of an inspection lot.

You can valuate an operation completion in the object tree of the results recording(transaction QE51N) and you can recognize it by a separate tab page during theusage decision.

2006/Q2 © 2006 SAP AG. All rights reserved. 347

Page 358: Plm412 en Col62 Fv Part a4

Unit 6: Usage Decision PLM412

The function for the operation completion is set plant-specifically for eachinspection type in Customizing for quality management (Quality Inspection ->Results Recording -> Make Settings for Operation Completion).

Hint: The operation completion has only informative characters and doesnot influence the existing functions.

348 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 359: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection Completion with the Usage Decision

Exercise 17: Manual Usage Decision

Exercise ObjectivesAfter completing this exercise, you will be able to:� Complete the quality inspection with the usage decision.� Manually make the usage decision for the inspection lot.

Business ExampleThe quality inspection is completed when the usage decision is made. Youmake the usage decision manually for particularly important materials. All theinspection results and the defect types recorded are displayed again.

You use the quality level to display current information about the inspection scopefor the individual materials at any time.

Task 1: Usage Decision for an Inspection LotThe inspection lot processing is completed when the usage decision is made. Youcan make the usage decision manually or using a job.

1. You use an inspection list to display all the inspection lots that exist formaterial T-BQ1## in the system. Complete these inspection lots with theusage decision.

Which overview appears when you make the usage decision for theinspection lot, to which an inspection plan is assigned?

___________________________________________________________

You use the input help to choose a suitable UD code.

Task 2: Display the Quality Level:A quality level is updated in connection with the dynamic modification.Depending on the settings in the inspection type or the inspection plan, the qualitylevel is carried out based on the characteristic or on the lot.

1. Make a note of the quality levels for material T-BQ1##.

Why are there several quality levels for the material?

____________________________________________________________

2006/Q2 © 2006 SAP AG. All rights reserved. 349

Page 360: Plm412 en Col62 Fv Part a4

Unit 6: Usage Decision PLM412

Solution 17: Manual Usage DecisionTask 1: Usage Decision for an Inspection LotThe inspection lot processing is completed when the usage decision is made. Youcan make the usage decision manually or using a job.

1. You use an inspection list to display all the inspection lots that exist formaterial T-BQ1## in the system. Complete these inspection lots with theusage decision.

Which overview appears when you make the usage decision for theinspection lot, to which an inspection plan is assigned?

___________________________________________________________

You use the input help to choose a suitable UD code.

a) Logistics→ Quality Management→ Quality Inspection→ Worklist→Inspection→ Change Data (QA32) The inspection lot screen appears.Enter the following data for the selection:

Field name or data type ValuesPlant 1000Material T-BQ1##

List settings Select all inspection lots

Make the selection by choosing the F8 function key or the pushbuttonExecute. The worklist for inspection lots appears. In this worklist youcan choose from all the inspection lots for your material T-BQ1##.

Select the inspection lot with the largest inspection lot number(specifications from the inspection plan) and choose the pushbuttonUsage decision (UD).

Since you have recorded defects for this inspection lot, the system firstswitches to the tab page of the defect overview. All defects recorded forthe inspection lot are displayed on this screen and you can still recorddefects here before the usage decision is made. You can choose thepushbutton Defects� to switch to defects recording.

On the Characteristics tab page, you can see the characteristics relevantfor the usage decision. You can use the pushbutton Other charac. liston this tab page to display all characteristics from the inspection lot.You can use the pushbutton Display charac. data (magnifying glass) toswitch to the recorded inspection results for each characteristic.

Continued on next page

350 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 361: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection Completion with the Usage Decision

Make the usage decision for the inspection lot by using the input helpin the field UD code. Copy a suitable UD code from the selected set.

Save your entries.

Hint: The possible UD codes are created in catalog type 3Usage decision in code groups. The UD codes are valuatedin selected sets for catalog type 3 and, if necessary, follow-upactions are assigned.

You can define a UD selected set for each inspection type inCustomizing. The codes from this selected set are used whenthe usage decision is made.

Make the usage decision with a suitable UD code for your otherinspection lots and save your entries.

Task 2: Display the Quality Level:A quality level is updated in connection with the dynamic modification.Depending on the settings in the inspection type or the inspection plan, the qualitylevel is carried out based on the characteristic or on the lot.

1. Make a note of the quality levels for material T-BQ1##.

Why are there several quality levels for the material?

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 351

Page 362: Plm412 en Col62 Fv Part a4

Unit 6: Usage Decision PLM412

____________________________________________________________

a) Logistics→ Quality Management→ Quality Inspection→ InspectionLot→ Display (QA03)

Enter the following data on the initial screen for displaying the qualitylevel:

Field name or data type ValuesPlant 1000Material T-BQ1##

Choose the pushbutton Quality level, then choose Enter, or the Returnkey.

The overview screen of all quality levels for material T-BQ1## appears.On the overview screen, you can see all data for the quality levels. Youcan select a quality level with a double-click and display it in detail.You can use the pushbutton Dynamic modification history to switchfrom the detail display to the dynamic modification history.

A quality level is maintained both at inspection type level (from thefirst inspection lot to defects recording) and at inspection lot level(from inspection lot with inspection plan). Dynamic modification ruleA## is used for the inspection lot during defects recording. B## is usedfor the inspection lot with a task list.

352 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 363: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Inspection Completion with the Usage Decision

Lesson Summary

You should now be able to:� Make a usage decision for an inspection lot and understand the individual

functions and effects of a usage decision.� Plan UD codes.

Related Information

2006/Q2 © 2006 SAP AG. All rights reserved. 353

Page 364: Plm412 en Col62 Fv Part a4

Unit Summary PLM412

Unit SummaryYou should now be able to:� Make a usage decision for an inspection lot and understand the individual

functions and effects of a usage decision.� Plan UD codes.

354 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 365: Plm412 en Col62 Fv Part a4

PLM412 Test Your Knowledge

Test Your Knowledge

1. A usage decision can always be made automatically for an inspection lot.Determine whether this statement is true or false.□ True□ False

2. A stock transfer can also be carried out with the usage decision.Determine whether this statement is true or false.□ True□ False

3. When you make a usage decision manually, the most important informationfrom the inspection is displayed.Determine whether this statement is true or false.□ True□ False

2006/Q2 © 2006 SAP AG. All rights reserved. 355

Page 366: Plm412 en Col62 Fv Part a4

Test Your Knowledge PLM412

Answers

1. A usage decision can always be made automatically for an inspection lot.

Answer: False

A usage decision can only be made automatically for inspection lots whosecharacteristics are all OK and for which no defects have been recorded.

2. A stock transfer can also be carried out with the usage decision.

Answer: True

Depending on the planning in the select sets for catalog type 3, a stocktransfer (for example, inspection stock -> unrestricted-use stock) is alsocarried out when the usage decision is made.

3. When you make a usage decision manually, the most important informationfrom the inspection is displayed.

Answer: True

When you make a usage decision, rejected inspection characteristics andrecorded defects are displayed.

356 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 367: Plm412 en Col62 Fv Part a4

Unit 7Definition and Structure of

Notifications

Unit OverviewBased on the different notification systems, this unit introduces the basic termsand concepts related to notifications. The structure of the notification is explainedand information related to the notification header and notification items is alsoprovided.

Unit ObjectivesAfter completing this unit, you will be able to:

� Describe the notification systems in SAP system and the areas to whichthey belong.

� Describe the structure of a quality notification and how it can be used.� Describe how you can configure a quality notification.� Describe the data contained at different levels of the notification.� Describe the elements that are constituent parts of a quality notification

system.

Unit ContentsLesson: Definition and Structure of Notifications .. . . . . . . . . . . . . . . . . . . . . . . . . .358

Exercise 18: Definition and Structure of a Quality Notification ... . . . .369

2006/Q2 © 2006 SAP AG. All rights reserved. 357

Page 368: Plm412 en Col62 Fv Part a4

Unit 7: Definition and Structure of Notifications PLM412

Lesson: Definition and Structure of Notifications

Lesson OverviewThis lesson deals with the different notification systems and the relationships withnotification categories. In addition, it covers the structure of the notification andgives you information about the notification header and notification items.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Describe the notification systems in SAP system and the areas to whichthey belong.

� Describe the structure of a quality notification and how it can be used.� Describe how you can configure a quality notification.� Describe the data contained at different levels of the notification.� Describe the elements that are constituent parts of a quality notification

system.

Business ExampleThe problem processing procedure differs from company to company; this meansthat your requirements must be handled in a flexible way.

Figure 177: Definition and Structure: Business Scenario

358 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 369: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Definition and Structure of Notifications

The problem processing procedure differs from company to company; this meansthat your requirements must be handled in a flexible way.

The quality notifications in the SAP System are extremely flexible. When definingand configuring quality notifications, you can:

� Use the notification types that are delivered with the standard system.� Define your own notification types.� Configure the content and structure of the notification to your own

requirements.

Notification Categories and Associations

Figure 178: Notifications in the SAP System, Overview

Other components and supporting functions of the SAP System are integrated inthe quality notification system.

2006/Q2 © 2006 SAP AG. All rights reserved. 359

Page 370: Plm412 en Col62 Fv Part a4

Unit 7: Definition and Structure of Notifications PLM412

The SAP system differentiates between various notification systems:

� General notifications (notification category 05)� Quality notifications (notification category 02), operational area: Quality

management� Maintenance notifications (notification category 01), operational area:

Maintenance� Service notifications (notification category 03), operational area: Service

Processing� Claim notifications (notification category 04), operational area: Project

system

The following notification types are available in the SAP System:

� General notifications: General notification (G0), change notification (54)� Quality notifications: Customer-related defect (F1), vendor-related defect

(F2), material-related defect (F3), customer complaint (Q1), complaintagainst vendor (Q2), internal problem notification (Q3), general internalproblem notification (Z3)

� Maintenance notifications: PM order (M1), malfunction report (M2),activity report (M3), malfunction report from QM (MQ)

� Service notifications: Service notification (S1), activity report (S2), servicerequest (S3)

Figure 179: Notifications in the SAP System, Associations

360 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 371: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Definition and Structure of Notifications

Tasks and settings (overview):

� The notification category identifies notifications that are related to aparticular application component in the system. The notification categoryQ2, for example, is used for quality notifications in the Standard System.

� The notification origin defines the business context in which a notificationis used. The following notification origins are supported by SAP for qualitynotifications:

� Customer complaint (Q1)� Complaint against a vendor (Q2)� Internal problem notification (Q3)

� The notification type determines the origin, the content, and other propertiesof a notification. You can define your own notification types in Customizing.SAP provides sample notification types, for example Q1 and F1.

Figure 180: Quality Notifications in the Logistics Supply Chain

The uses for quality notifications cover the entire logistics supply chain.

Customer complaints from the sales area (notification types of notification originQ1)

� Managing and processing customer complaints and grievances

Customer complaints from the procurement area (notification types of notificationorigin Q2)

� Managing and processing complaints against a vendor

2006/Q2 © 2006 SAP AG. All rights reserved. 361

Page 372: Plm412 en Col62 Fv Part a4

Unit 7: Definition and Structure of Notifications PLM412

Internal problem notifications (notification types of notification origin Q3)

� Managing and processing problems from production� General internal problems

Quality Notification Structure

Figure 181: Structure of a Quality Notification

Quality notification(header):

What is the notification about?

Tasks (for the header): What must be done to take immediate remedialaction?

Actions (for the header): Which short-term activities were implemented?Partner: Which partners (internal and external) are affected?Notification items: Which defects have been identified?

Where or in which assemblies have these defectsoccurred?

Actions (for the item): What was done, to alleviate the problempermanently?

Tasks (for item): Which corrective tasks must be performed, toprevent the defect from occurring again?

Causes (for item): What are the causes of the defects?

362 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 373: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Definition and Structure of Notifications

Figure 182: Contents of a Quality Notification - General Data

Reference object:

� Material/plant/batch� Inspection lot� Purchasing document/material document� Production order/production version� Sales order/delivery� Device data/reference number� Copy model number� Vendor material/batch

Subject: Catalog and long text

Internal processing:

� Priority� Status� Deadlines

2006/Q2 © 2006 SAP AG. All rights reserved. 363

Page 374: Plm412 en Col62 Fv Part a4

Unit 7: Definition and Structure of Notifications PLM412

Figure 183: Contents of a Quality Notification - Partners

You can define your own partner functions in Customizing.

A partner type must be uniquely assigned to each partner function.

The partner type defines the master record (debtor, creditor, organizational unit,position, SAP user and personnel number) that underlies the partner function.

Partners are all the people/organizational units directly or indirectly affected by anotification.

Figure 184: Contents of a Quality Notification - Notification Item

364 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 375: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Definition and Structure of Notifications

The information contained in the catalog provides the best basis for the evaluationof defect data.

You can code a defect item according to defect type as well as defect location.

You have various options to describe a defect in detail, using the link to the centralSAP Classification System.

� The predefined class type for notification items is class type 015.

Figure 185: Contents of a Quality Notification - Cause

You can supplement each notification item with a detailed description of thedefect cause.

You can record several causes for each defect item.

2006/Q2 © 2006 SAP AG. All rights reserved. 365

Page 376: Plm412 en Col62 Fv Part a4

Unit 7: Definition and Structure of Notifications PLM412

Figure 186: Contents of a Quality Notification - Action

You can use the actions to document the steps that have already been taken tosolve the problem.

The elements above apply to actions in the header, as well as actions for individualitems in a quality notification.

Figure 187: Contents of a Quality Notification - Task

You can use tasks to initiate the activities to be performed.

366 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 377: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Definition and Structure of Notifications

It is important to assign a person responsible for processing (partner), and to createa link to the status management of the notification.

The elements above apply to tasks in the header, as well as tasks for individualitems in a quality notification.

Figure 188: Elements of the Quality Notification System

Status management: Link to central status management at notification headerlevel and task level (system status is predefined in the system; you can freelydefine user statuses in Customizing)

Document Management: Linking of documents to the quality notification

Services for Object Easy linking of documents, URLs and so on, to the qualitynotification

Action Box: Executing follow-up functions with a mouseclick

Action Log: Record of all changes that have been made in the quality notification

Classification system: Link to the SAP classification system to classify defectdata

ArchiveLink: Linking of original documents (such as complaint letters fromcustomers) to a quality notification; you can also archive outgoing documents

Workflow: Triggering Workflow using status at notification header and task level

Nonconformity costs: Recording nonconformity costs using QM orders

Evaluations/Controlling: Evaluations of notification data and nonconformitycosts

2006/Q2 © 2006 SAP AG. All rights reserved. 367

Page 378: Plm412 en Col62 Fv Part a4

Unit 7: Definition and Structure of Notifications PLM412

368 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 379: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Definition and Structure of Notifications

Exercise 18: Definition and Structure of aQuality Notification

Exercise ObjectivesAfter completing this exercise, you will be able to:� Search for, call up and process a quality notification in the system.� Document the defect analysis for a quality notification in the system.

Business ExampleYour company uses quality notifications to process complaints against vendors.

Task: Defects Recording Using the Quality NotificationIn addition to recording defects using the inspection lot, you can also recorddefects using the quality notification. You do not require any special settings inthe material master for this type of defects recording.

1. Defects were found in material T-AQ1## (## represents your group number).Since this material was supplied by vendor 1000, you recorded this problemin a quality notification.

Search for this notification in the system and record the defects that wereidentified in the defect analysis. Use the defect codes that have alreadybeen prepared in the system.

2006/Q2 © 2006 SAP AG. All rights reserved. 369

Page 380: Plm412 en Col62 Fv Part a4

Unit 7: Definition and Structure of Notifications PLM412

Solution 18: Definition and Structure of aQuality NotificationTask: Defects Recording Using the Quality NotificationIn addition to recording defects using the inspection lot, you can also recorddefects using the quality notification. You do not require any special settings inthe material master for this type of defects recording.

1. Defects were found in material T-AQ1## (## represents your group number).Since this material was supplied by vendor 1000, you recorded this problemin a quality notification.

Search for this notification in the system and record the defects that wereidentified in the defect analysis. Use the defect codes that have alreadybeen prepared in the system.

a) notification processing

Logistics→ Quality Management→ Quality Notification→ Change(QM02)

Use the field-related input help (F4), on the Extended Selection tabpage, to select the required notification. Enter the following data inthe selection screen:

Field name EntryMaterial: T-AQ1## (## is your group number)Vendor: 1000Purchasing organization: 1000

On the Items tab page, record the defects that have been identified.To do this, use the field-related input help for the defect location andthe defect type.

Save your notification.

370 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 381: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Definition and Structure of Notifications

Lesson Summary

You should now be able to:� Describe the notification systems in SAP system and the areas to which

they belong.� Describe the structure of a quality notification and how it can be used.� Describe how you can configure a quality notification.� Describe the data contained at different levels of the notification.� Describe the elements that are constituent parts of a quality notification

system.

2006/Q2 © 2006 SAP AG. All rights reserved. 371

Page 382: Plm412 en Col62 Fv Part a4

Unit Summary PLM412

Unit SummaryYou should now be able to:� Describe the notification systems in SAP system and the areas to which

they belong.� Describe the structure of a quality notification and how it can be used.� Describe how you can configure a quality notification.� Describe the data contained at different levels of the notification.� Describe the elements that are constituent parts of a quality notification

system.

372 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 383: Plm412 en Col62 Fv Part a4

PLM412 Test Your Knowledge

Test Your Knowledge

1. The notification type defines the business context in which a notificationis used.Determine whether this statement is true or false.□ True□ False

2. The status of an action defines whether this action is to be executed orcompleted.Determine whether this statement is true or false.□ True□ False

3. The following notification origins exist for the notification category 02(quality notifications):Choose the correct answer(s).□ A Q1, Customer complaint□ B Q2, Complaint against a vendor□ C Q3, Internal problem notification□ D G1, General notification

2006/Q2 © 2006 SAP AG. All rights reserved. 373

Page 384: Plm412 en Col62 Fv Part a4

Test Your Knowledge PLM412

Answers

1. The notification type defines the business context in which a notificationis used.

Answer: False

The notification type defines, amongst other things, the properties of anotification. The notification type can be defined in Customizing. Thenotification type is assigned to a notification origin. The notification origindefines the business context in which a notification is used.

2. The status of an action defines whether this action is to be executed orcompleted.

Answer: False

The actions in a notification do not have a status. A status is, for example,used for tasks for notifications or for items. Statuses define whether or not atask can be completed.

3. The following notification origins exist for the notification category 02(quality notifications):

Answer: A, B, C

The notification origin G1 is part of the notification category 05, generalnotification. Notifications in this notification category are neutral.

374 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 385: Plm412 en Col62 Fv Part a4

Unit 8Quality Notifications in Logistics

Unit OverviewThis unit covers the possible uses of the quality notification in procurement. Thenotification process is explained using the example of unexpected problems atgoods receipt. You also learn about the use of notifications in conjunction withthe quality inspection at goods receipt.

Quality notifications can also be used to record and process customer complaints.This unit covers the process flow of a customer complaint. An overview of returnsand repairs processing is also given.

Unit ObjectivesAfter completing this unit, you will be able to:

� Create a quality notification as a complaint against a vendor.� Complain when a faulty delivery is received.� carry out a defects recording using an inspection lot at goods receipt.� Use a quality notification to process the problem or defect.� Create a quality notification for a customer complaint.� Describe the procedure for returns and repairs processing, using quality

notifications.

Unit ContentsLesson: Quality Notifications at Goods Receipt .. . . . . . . . . . . . . . . . . . . . . . . . . . .376

Exercise 19: Problem Processing in Procurement - NotificationCreation... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .383

Lesson: Quality Inspection and Defect Notification at Goods Receipt.. .389Exercise 20: Goods Receipts and Complaints - Defects Recording.399

Lesson: Customer Complaints ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .403Exercise 21: Customer Complaint - Notification Creation.. . . . . . . . . . . .413

2006/Q2 © 2006 SAP AG. All rights reserved. 375

Page 386: Plm412 en Col62 Fv Part a4

Unit 8: Quality Notifications in Logistics PLM412

Lesson: Quality Notifications at Goods Receipt

Lesson OverviewUnplanned events that must be documented can arise when goods are received.Various tasks must be performed to solve the problems. This lesson gives adetailed description of notification processing at good receipt.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Create a quality notification as a complaint against a vendor.� Complain when a faulty delivery is received.

Business ExampleIn the procurement process in a company, problems and difficulties may arise thatneed to be documented and corrected. You can create quality notifications inthe SAP system for this.

Figure 189: Problem Processing in Procurement: Business Scenario

The procurement process in a company includes planned and unplanned events.

When you receive goods:

� You can discover that the delivery is incorrect.� You can identify and record defects in a planned goods receipt inspection.

In both cases, you create a quality notification to process a complaint or documentthe defects that have been identified.

376 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 387: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Quality Notifications at Goods Receipt

Complaint Concerning an Incorrect Delivery

Figure 190: Process 1: Complaint About Incorrect Delivery

At goods receipt, you discover that the vendor has delivered the wrong product.You can use a quality notification to document this event and to send a complaint.

Figure 191: Triggering a Quality Notification

You create a quality notification manually in the system.

If a vendor delivers the wrong goods, create a quality notification (notificationtype Q2) for notification origin Q2 (complaint against vendor).

The following quality notification types are available in the standard system forthe notification origin Q2:

� Complaint against the vendor (notification type Q2)� Vendor error (notification type F2)

2006/Q2 © 2006 SAP AG. All rights reserved. 377

Page 388: Plm412 en Col62 Fv Part a4

Unit 8: Quality Notifications in Logistics PLM412

Figure 192: Complaint Against Vendor with Reference Object

In Customizing for quality notifications(Quality Management -> QualityNotifications -> Notification Creation -> Notification Type -> Define ScreenTemplates), you can define the initial screen that you want to appear when youcreate a notification of this notification type.

You can copy specific data from preceding documents to the quality notificationvia the initial screen.

If necessary, you can change the assigned documents, for example, purchasingdocument or material document at a later stage.

378 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 389: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Quality Notifications at Goods Receipt

Figure 193: Transfer Posting of Goods

You can use the action box functions to process the wrong delivery.

For example, you can first perform a stock transfer posting. You use a functionin the action box to post goods that are the subject of a complaint fromunrestricted-use stock to blocked stock.

If a quality inspection is required, you can also make a transfer posting toinspection stock.

2006/Q2 © 2006 SAP AG. All rights reserved. 379

Page 390: Plm412 en Col62 Fv Part a4

Unit 8: Quality Notifications in Logistics PLM412

Figure 194: Create a Return Delivery

The next step is to use an action box function to create a return delivery.

You can create a return delivery with or without reference to an original purchasingdocument.

In addition, you can use a function in the action box to transfer directly to thedelivery (for example, to prepare delivery papers or process the goods issue).

Figure 195: Credit/Debit Memo

380 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 391: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Quality Notifications at Goods Receipt

You can debit the vendor with the cost of the returned goods.

Other follow-up functions that support complaints against the vendor are:

� Finding the vendor of the material and assigning him or her to the notification� Finding the purchasing document for the material and assigning it to the

notification� Transfer posting of material from blocked stock to unrestricted-use stock� Transfer posting of material from blocked stock to inspection stock� Creating a transfer order (if the Warehouse Management component is active)� Creating a return delivery� Transferring to the usage decision� Transferring to the function for changing the delivery

2006/Q2 © 2006 SAP AG. All rights reserved. 381

Page 392: Plm412 en Col62 Fv Part a4

Unit 8: Quality Notifications in Logistics PLM412

382 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 393: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Quality Notifications at Goods Receipt

Exercise 19: Problem Processing inProcurement - Notification Creation

Exercise ObjectivesAfter completing this exercise, you will be able to:� Create a complaint against a vendor in the system.

Business ExampleYou use quality notifications to process complaints concerning incorrect deliveriesfrom your vendors.

Task: Use the Quality Notification in ProcurementA problem occurs in procurement. This problem is documented in a qualitynotification. The required steps are initiated and carried out.

1. You ordered 50, 21� monitors (material: T-AQ2##) from your vendor 1000(C.E.B Berlin). When the monitors are delivered, you discover that they are17� monitors. You want to complain about the delivery. Create a qualitynotification for this problem with one defect item.

Which notification type do you use? ____________________

2. Create the notification with reference to the material document in the goodsreceipt.

Hint: Use the F4 help to select the corresponding material documenton the notification initial screen for the materialT-AQ2## and thevendor 1000 and copy the document number and the item fromthe material document.

What is the result?

___________________________________________

___________________________________________

___________________________________________

3. The contact person at your vendor�s address is Mrs. Erica Smith. Enter heraddress as the special address for the notification.

4. Enter your user as coordinator and then save the quality notification.

Make a note of the notification number:

______________________________________Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 383

Page 394: Plm412 en Col62 Fv Part a4

Unit 8: Quality Notifications in Logistics PLM412

5. Process the notification that you have just created. The goods are to bereturned to the vendor. Post the entire complaint quantity to blocked stockand then create a return delivery.

Make a note of the document number for the transfer posting to blockedstock:

______________________________________

Make a note of the return delivery number:

______________________________________

6. In addition, initiate an (immediate) task to activate a goods receipt inspectionfor the materials from this vendor. Enter your user as the processorresponsible.

384 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 395: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Quality Notifications at Goods Receipt

Solution 19: Problem Processing inProcurement - Notification CreationTask: Use the Quality Notification in ProcurementA problem occurs in procurement. This problem is documented in a qualitynotification. The required steps are initiated and carried out.

1. You ordered 50, 21� monitors (material: T-AQ2##) from your vendor 1000(C.E.B Berlin). When the monitors are delivered, you discover that they are17� monitors. You want to complain about the delivery. Create a qualitynotification for this problem with one defect item.

Which notification type do you use? ____________________

a) Logistics→ Quality Management→ Quality Notification→ Create(QM01)

Use the field-related input help (F4) to choose the notification type Q2(complaint against vendor) and confirm your entry.

2. Create the notification with reference to the material document in the goodsreceipt.

Hint: Use the F4 help to select the corresponding material documenton the notification initial screen for the materialT-AQ2## and thevendor 1000 and copy the document number and the item fromthe material document.

What is the result?

___________________________________________

___________________________________________

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 385

Page 396: Plm412 en Col62 Fv Part a4

Unit 8: Quality Notifications in Logistics PLM412

___________________________________________

a) In the dialog that appears, use the field-related input help for thematerial document to select the required material document byspecifying the material T-AQ2## (## is your group number) and thevendor 1000. Choose Execute to start the selection. Copy the requiredmaterial document by double clicking on the document number. Copythe item for the material document using the field-related input helpand confirm your entries.

The material, plant, purchasing organization, purchasing group,vendor and quantity are copied from the purchase order item tothe notification, as is the catalog profile.

Enter a subject for the notification. You can use the Subject screen areon the Subject tab page for this.

3. The contact person at your vendor�s address is Mrs. Erica Smith. Enter heraddress as the special address for the notification.

a) Choose the Contact Person tab page, then the Notification Address tabpage, and then choose the Notification Address pushbutton. Enter Mrs.Erica Smith as the contact person and confirm your entries.

4. Enter your user as coordinator and then save the quality notification.

Make a note of the notification number:

______________________________________

a) Enter your user in the Coordinator field and then save the qualitynotification.

Notification number: ______________________________________

5. Process the notification that you have just created. The goods are to bereturned to the vendor. Post the entire complaint quantity to blocked stockand then create a return delivery.

Make a note of the document number for the transfer posting to blockedstock:

______________________________________

Make a note of the return delivery number:

Continued on next page

386 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 397: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Quality Notifications at Goods Receipt

______________________________________

a) Choose Notification -> Change (QM02) and confirm the notificationnumber proposed by the system or enter the notification number youmade a note of earlier and confirm your entry.

In the action box, choose the follow-up function Transfer Post.Unrestricted -> Blocked, confirm the data that the system proposes forthe transfer posting, and save your notification.

Access your notification again, choose the Document flow pushbuttonand make a note of the document number for the transfer posting.

Document number for the transfer post-ing:____________________________

Access your notification again and use the action box to select thefollow-up function Create return delivery. Specify a reason forthe return delivery (select this using the input help). Confirm thedata proposed by the system for the return delivery and save yournotification.

Access your notification again, choose the Document flow pushbuttonand make a note of the document number for the return delivery.

Document number for the return delivery:_________________________

6. In addition, initiate an (immediate) task to activate a goods receipt inspectionfor the materials from this vendor. Enter your user as the processorresponsible.

a) Choose the Tasks tab page and use the field-related input help for thecode group to choose the code groupMONITOR1 Immediate task andthe code 2 - Activate goods receipt inspection. Confirm your entriesand save the notification.

2006/Q2 © 2006 SAP AG. All rights reserved. 387

Page 398: Plm412 en Col62 Fv Part a4

Unit 8: Quality Notifications in Logistics PLM412

Lesson Summary

You should now be able to:� Create a quality notification as a complaint against a vendor.� Complain when a faulty delivery is received.

388 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 399: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Quality Inspection and Defect Notification at Goods Receipt

Lesson: Quality Inspection and Defect Notification atGoods Receipt

Lesson OverviewDuring a goods receipt inspection, problems can arise that were not takeninto consideration during inspection planning. These unplanned problems canbe recorded with reference to a GR inspection lot and processed as a qualitynotification.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� carry out a defects recording using an inspection lot at goods receipt.� Use a quality notification to process the problem or defect.

Business ExampleThe procurement process in a company includes planned and unplanned events.

When you receive goods:

� You can discover that the delivery is incorrect.� You can identify and record defects in a planned goods receipt inspection.

In both cases, you create a quality notification to process a complaint or documentthe defects that have been identified.

2006/Q2 © 2006 SAP AG. All rights reserved. 389

Page 400: Plm412 en Col62 Fv Part a4

Unit 8: Quality Notifications in Logistics PLM412

Quality Inspection and Defect Notification at GoodsReceipt

Figure 196: Process 2: Quality Inspection with Defects Recording

In this scenario, a quality inspection is triggered for a goods receipt.

There are various types of quality inspection:

� Inspection without an inspection plan, manual defects recording and usagedecision

� Inspection with an inspection plan, manual defects recording and usagedecision

� Inspection with an inspection plan, results recording by characteristic,manual defects recording and usage decision

� Inspection with an inspection plan, results recording by characteristic,automatic and manual defects recording and usage decision

If defects are found during the goods receipt inspection, they can be processedfurther using quality notifications in the defects recording function.

390 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 401: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Quality Inspection and Defect Notification at Goods Receipt

Figure 197: Triggering a Quality Notification (Defects Recording)

You can record defects manually, or the system can record defects automatically.

When you record a defect, the system automatically creates a quality notificationwith the notification type that has been assigned to the inspection type inCustomizing:

� Customer complaint (notification type F1); for example, in a qualityinspection

� Complaint against the vendor (notification type F2); for example in a goodsreceipt inspection

� Internal problem notification (notification type F3); for example, in a goodsreceipt inspection from production

The inspection types and their process parameters can be assigned to the materialin the material master using the inspection setup in the QM view.

2006/Q2 © 2006 SAP AG. All rights reserved. 391

Page 402: Plm412 en Col62 Fv Part a4

Unit 8: Quality Notifications in Logistics PLM412

Figure 198: Planning Defects Recording

The following play an important part in recording defects:

� Report type� Catalog profile� confirmation profile

You can assign the report type to a work center. This enables the layout and thepossible entries for the coding (code groups) to be designed based on the workcenter.

The report type is freely definable (for example, visual inspection, function check,assembly, laboratory, summarized defect report, individual defect report, ...).

If there is no work center available because the inspection is to take place withoutan inspection plan, you can specify the catalog profile on the initial screen ofresults recording.

The report type can be proposed using the user parameter QFE.

In the confirmation profile, you define the type of information that you can recordfor a defect (such as, defect type, defect cause, defect location, task and defectvaluation). You can also define whether an entry for a confirmation object (suchas defect location, defect cause) is mandatory, optional or not required.

The confirmation profile and the report type are defined in Customizing (QualityManagement -> Quality Notification -> Defects Recording)

392 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 403: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Quality Inspection and Defect Notification at Goods Receipt

Figure 199: Determining a Catalog Profile for Defects Recording

A catalog profile is defined in the report type. You use indicators in the reporttype to control how the system accesses the catalog profile.

If you always want to use the catalog profile from the report type, do not set theindicators for the notification type or the material.

If you want to use the catalog profile for the material, you must set the materialindicator. If the material does not have a catalog profile assigned to it, the systemtakes the profile from the report type.

If the indicator for the notification type is set, the system uses the catalog profilethat has been assigned to this notification type.

If both indicators are set (notification type and material), the catalog profileis determined in exactly the same way as for a manual creation of a qualitynotification, (that is, the catalog profile assigned to the material, takes precedenceover the profile that has been assigned to the notification type).

2006/Q2 © 2006 SAP AG. All rights reserved. 393

Page 404: Plm412 en Col62 Fv Part a4

Unit 8: Quality Notifications in Logistics PLM412

Figure 200: Defects Recording/Activating the Quality Notification

When you record a defect, the system creates a quality notification with the status�Defects recording� and �Outstanding notification�.

You can activate a quality notification manually with this status, or the system canactivate the notification automatically. If a quality notification is activated, thestatus of this notification changes to �Outstanding notification�.

You can switch to a notification processing screen directly from the resultsrecording function using a pushbutton. This allows you to access the notificationprocessing functions when you record defects and also to define tasks at thisstage. When you transfer to the notification processing screen, the notificationis activated automatically, if tasks or executable data have been entered (forexample, priority or person responsible for processing).

When you record defects, you can also enter additional texts for these defects onthe overview screen next to the defect codes.

394 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 405: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Quality Inspection and Defect Notification at Goods Receipt

Buyer's Negotiation Sheet and Vendor Evaluation

Figure 201: Displaying Buyer's Negotiation Sheet

You can call the buyer's negotiation sheet directly, when editing or displayingnotifications of notification origin Q2. The buyer's negotiation sheet containsinformation:

� From the vendor evaluation� About the sales of the vendor� About existing purchase orders for the vendor

2006/Q2 © 2006 SAP AG. All rights reserved. 395

Page 406: Plm412 en Col62 Fv Part a4

Unit 8: Quality Notifications in Logistics PLM412

Figure 202: Requesting an 8D-Report

If, for example, a vendor from the automotive industry supplies you with defectivegoods, you can generate an 8D-report when processing a quality notification.

You can generate an 8D-report using a follow-up function in the action box andsend it to the vendor.

Figure 203: Vendor Evaluation

In materials management, you can use the vendor evaluation in the SAP System tochoose suitable vendors.

396 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 407: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Quality Inspection and Defect Notification at Goods Receipt

The vendor evaluation provides you with a summarized statistic that valuates thevendor according to main and subcriteria.

These criteria include:

� Price (price level and price history)� Quality (goods receipt inspections, complaints and system audits)� Delivery (on-time delivery performance, quantity reliability, shipping

instructions)� Service

Figure 204: Vendor Evaluation: Criteria

The total score represents the evaluation of a vendor. This score is the sum of thescores that the vendor receives for all the main criteria.

The scores for the main and subcriteria illustrate the performance of a vendor inmore detail than the total score.

The scores that the vendor receives for the individual criteria can be of varyingimportance for you. This is expressed by the weighting share.

2006/Q2 © 2006 SAP AG. All rights reserved. 397

Page 408: Plm412 en Col62 Fv Part a4

Unit 8: Quality Notifications in Logistics PLM412

Figure 205: Relevant Elements for Vendor Evaluation

Only closed notifications of notification origin Q2 and status �caused externally�are included in the grade determination for the subcriterion �complaint�.

398 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 409: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Quality Inspection and Defect Notification at Goods Receipt

Exercise 20: Goods Receipts andComplaints - Defects Recording

Exercise ObjectivesAfter completing this exercise, you will be able to:� Record defects for an inspection lot using the example of a goods receipt

inspection.

Business ExampleA goods receipt inspection is to be performed for certain materials. You havechosen inspection process variant defects recording for the inspection lot for thisgoods receipt inspection.

Task: Defects Recording Using the Inspection LotIf the relevant settings have been made in the material master, an inspection lot canbe created when the goods receipt is posted. You can carry out defects recordingat goods receipt with reference to the inspection lot.

1. Since you activated a goods receipt inspection for materials from vendor1000, the system creates an inspection lot the next time such goods arereceived.

Post the goods receipt for the material T-AQ1## you ordered.

Hint: A report type is used for defects recording. You can enter thisreport type when you access defects recording or you can preassignit using the user parameter QFE.

2. Use the worklist for inspections to select the inspection lot and recorddefects for the lot.

Make a note of the inspection lot number: ___________________

3. Search for the quality notification that was automatically created in thebackground by defects recording using the inspection lot. To do this, usethe worklist for the notifications and select the notifications for materialT-AQ1##.

Make a note of the notification number:___________________

2006/Q2 © 2006 SAP AG. All rights reserved. 399

Page 410: Plm412 en Col62 Fv Part a4

Unit 8: Quality Notifications in Logistics PLM412

Solution 20: Goods Receipts andComplaints - Defects RecordingTask: Defects Recording Using the Inspection LotIf the relevant settings have been made in the material master, an inspection lot canbe created when the goods receipt is posted. You can carry out defects recordingat goods receipt with reference to the inspection lot.

1. Since you activated a goods receipt inspection for materials from vendor1000, the system creates an inspection lot the next time such goods arereceived.

Post the goods receipt for the material T-AQ1## you ordered.

Hint: A report type is used for defects recording. You can enter thisreport type when you access defects recording or you can preassignit using the user parameter QFE.

a) Logistics→ Materials Management→ Inventory Management→Goods Movement→ Goods Movement (MIGO)

b) Use the field-related input help on the tab page Purchasing Documentsfor Materials to enter the material T-AQ1## (## is your group number)so that you can select the required purchasing document ( startsearch ) and then choose the Transfer pushbutton. The number ofthe purchasing document is transferred to the field. Confirm thistransfer using Enter.

Set the Item OK indicator and save your data.

2. Use the worklist for inspections to select the inspection lot and recorddefects for the lot.

Make a note of the inspection lot number: ___________________

a) Logistics -> Quality Management -> Quality Inspection -> Worklist ->Inspection -> Change Data (QA32)

b) Enter the material T-AQ1## as the selection criterion and chooseExecute.

Select the required inspection lot and choose the Create Defectpushbutton. Use the field-related input help to select the report type00000001 (summarized defect report) and confirm your entry.

Use the field-related input help for the code group to record defectcodes and then save your data.

Continued on next page

400 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 411: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Quality Inspection and Defect Notification at Goods Receipt

3. Search for the quality notification that was automatically created in thebackground by defects recording using the inspection lot. To do this, usethe worklist for the notifications and select the notifications for materialT-AQ1##.

Make a note of the notification number:___________________

a) Logistics→ Quality Management→ Quality Notification→ Worklist→ Notification→ Display Data (QM11)

b) Enter the material T-AQ1## as the selection criterion and chooseExecute.

Notification number: ______________________________________

Select the row with the notification number. In the application toolbar,use the Notification pushbutton to display the notification. You candisplay the defect entered using the inspection lot on the Item tab page.

2006/Q2 © 2006 SAP AG. All rights reserved. 401

Page 412: Plm412 en Col62 Fv Part a4

Unit 8: Quality Notifications in Logistics PLM412

Lesson Summary

You should now be able to:� carry out a defects recording using an inspection lot at goods receipt.� Use a quality notification to process the problem or defect.

402 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 413: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Customer Complaints

Lesson: Customer Complaints

Lesson OverviewThis lesson contains different methods for creating and processing customercomplaints using quality notifications. The lesson covers complaints processing,as well as the processes in returns and repairs processing.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Create a quality notification for a customer complaint.� Describe the procedure for returns and repairs processing, using quality

notifications.

Business ExampleQuick and reliable processing of customer problems is vital to maintain highcustomer satisfaction. Quality notifications give you many functions to aid theefficient processing of customer problems.

Figure 206: Customer Complaint: Business Scenario

In a modern company, it is important to process customer complaints efficientlyBy reacting quickly and effectively to problems, a company can greatly enhancetheir customer service image among their customers.

Quality notifications offer you a large number of functions for processingcustomer problems efficiently.

2006/Q2 © 2006 SAP AG. All rights reserved. 403

Page 414: Plm412 en Col62 Fv Part a4

Unit 8: Quality Notifications in Logistics PLM412

Customer Complaints

Figure 207: Customer Complaint

A customer complaint typically occurs during the sale or delivery of defectivegoods. Once customers have identified defects, they usually contact the vendor toreport their complaint.

As soon as the complaint has been entered by the company that delivered thegoods, the complaints processing procedure can begin. For example, the companycan initiate an immediate task that sends the customer a credit memo.

As the next step, the goods returned by the customer are subject to a detaileddefect analysis.

404 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 415: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Customer Complaints

Figure 208: Customer Complaint Using the Internet (1)

High quality, efficient customer service is important for both customers andvendors. Contact between the vendor and the customer must be made quickly,the customer must be able to report the problem without having to use elaboraterecording procedures, and the vendor should receive the notification as quickly aspossible.

Benefits for your customers:

� Your customers can enter the quality notification directly on your Webserver. They do not have to call or send a fax.

� Your customers can enter the data quickly and easily using the screen layoutthat you defined.

� Your customers can use a list of pre-defined defect codes to restrict theirproblem and they can also describe the problem using text.

� Your customers can check the status of the notification that they createdat all times.

Benefits for you:

� You can structure the screen layout so that it is easy and quick for customersto enter the data.

� You receive the notification online, that is, you receive it just after it hasbeen created.

� Because of the very small space of time between the creation and the receiptof the notification, you may be able to reproduce the problem immediately.

2006/Q2 © 2006 SAP AG. All rights reserved. 405

Page 416: Plm412 en Col62 Fv Part a4

Unit 8: Quality Notifications in Logistics PLM412

Figure 209: Customer Complaint Using the Internet (2)

If customers identify a defect in goods you have delivered, they want to reportthis immediately.

The contact person at the customer's premises can then create a quality notificationin the vendor system using the Internet. To so this, the contact person must havea corresponding authorization. The contact person selects the material that hewishes to complain about from a list that only contains materials that are deliveredby the particular vendor. The contact person subsequently describes the problemusing codes that he/she can select from a list and using a free text entry.

As soon as the notification has been sent, the SAP system assigns a qualitynotification number and passes this number on to the contact person at thecustomers.

The notification processor receives the customer complaint online (without asignificant time delay). It appears directly in his/her pool of new notifications andhe/she can react to this new notification immediately by analyzing the problem,making inquiries at the customers, or delivering a replacement.

The customer can check the status of the notification at any time on the Internet.

To record customer complaints using the Internet, the vendor must have anInternet Transaction Server (ITS).

406 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 417: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Customer Complaints

Figure 210: Creating a Customer Complaint with Reference Object

You create a customer complaint using a quality notification of origin Q1.

The following quality notification types are available in the standard system forthe notification origin Q1:

� Q1 Customer complaint� F1 Customer-related defect

In Customizing for quality notifications, you can specify the initial screen that youwant to appear when you create a notification of this notification type.

You can use the initial screen to supply the quality notification with predefinedsales-related data.

If necessary, you can alter the assigned documents retroactively (for example,sales order and delivery).

2006/Q2 © 2006 SAP AG. All rights reserved. 407

Page 418: Plm412 en Col62 Fv Part a4

Unit 8: Quality Notifications in Logistics PLM412

Figure 211: Displaying the Sales Summary

You can call the sales summary directly, when processing or displaying customercomplaints (notification origin Q1). The sales summary contains data aboutexisting notifications (for example, service notifications and quality notifications).

Returns and Repairs Processing

Figure 212: Returns and Repairs Processing (RMA)

408 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 419: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Customer Complaints

Quality management supports returns and repairs processing (RMA - returnmaterial authorization) using the following functions:

� Quality inspection� Quality notification

You use a customer complaint in conjunction with quality notifications to:

� Record a customer problem� Process returns that are related to a complaint

Figure 213: Processing a Quality Notification - RMA (1)

First, you create a quality notification for a customer complaint (for example,notification type Q1).

You enter notification data as required and if necessary, add a detailed descriptionof the problem.

If required, you can create immediate tasks in response to the customer's complaint(for example, sending a credit memo, or triggering a substitute delivery).

If customers want to return the faulty goods they have received, you can create arepair order in advance using the action box. In the repair order, you can enter areference to the current quality notification (notification number).

2006/Q2 © 2006 SAP AG. All rights reserved. 409

Page 420: Plm412 en Col62 Fv Part a4

Unit 8: Quality Notifications in Logistics PLM412

Figure 214: Entering the Returns - RMA (2)

Once the returned goods have been received at your company, the followingscenarios can occur:

� A quality inspection of the return delivery takes place. An inspection lot iscreated automatically at goods receipt. The following prerequisites mustbe fulfilled:

� There must be a repair order (sales order with repair item) for the return.� The inspection type that was assigned to inspection lot origin 05 (other

goods receipt) is active in the material master for the return.

� The returns are processed using a quality notification:

� The goods receipt is posted with reference to the repair order. You canfind the repair order using the notification number.

410 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 421: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Customer Complaints

Figure 215: Processing Returns - RMA (3)

You carry out a defect analysis on the returned goods and record the defectsidentified in the notification.

The results of this defect analysis enable you to decide which corrective tasks arerequired. You can use the action box in the notification to post a goods movementto the appropriate stock, for example, unrestricted-use stock (if no repair isrequired) blocked sales order stock (if a repair is required) or scrap.

You can use the action box to confirm the decision in the repair order. The systemsets the appropriate status in the repair order.

If a repair is required, the returns and repairs processing proceeds as follows:

� You can create a service order for the repair with the support of customerservice.

� The sales and distribution processes in SCM support the shipment of spareparts to customers.

2006/Q2 © 2006 SAP AG. All rights reserved. 411

Page 422: Plm412 en Col62 Fv Part a4

Unit 8: Quality Notifications in Logistics PLM412

412 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 423: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Customer Complaints

Exercise 21: Customer Complaint -Notification Creation

Exercise ObjectivesAfter completing this exercise, you will be able to:� Process a customer complaint using a quality notification.

Business ExampleThe customer complains about the delivered goods. You document this complaintusing a quality notification.

Task: Document a Customer Complaint Using aQuality Notification.You can create the customer complaints with reference to outbound deliveries orsales orders. If these documents are unknown, you can also create the complaintwith reference to the delivered material.

1. Customer 1033 (Karsson High Tech) wants to complain about a PC with thematerial number T-AQ3## (Desktop PC6/54), plant 1200.

Create a quality notification for this problem.

Notif. type: _______________________

2. Copy Mr. David Taylor as a contact person for the customer. If he has notyet been created, add his name as the customer contact person.

3. You tried to call the customer back. The customer however, could notbe reached. Document this transaction by entering an activity for thenotification.

4. You are responsible for processing this customer complaint further.Therefore, enter your user as the coordinator for this notification.

Then save the notification and make a note of the notification number.

______________________________________

2006/Q2 © 2006 SAP AG. All rights reserved. 413

Page 424: Plm412 en Col62 Fv Part a4

Unit 8: Quality Notifications in Logistics PLM412

Solution 21: Customer Complaint -Notification CreationTask: Document a Customer Complaint Using aQuality Notification.You can create the customer complaints with reference to outbound deliveries orsales orders. If these documents are unknown, you can also create the complaintwith reference to the delivered material.

1. Customer 1033 (Karsson High Tech) wants to complain about a PC with thematerial number T-AQ3## (Desktop PC6/54), plant 1200.

Create a quality notification for this problem.

Notif. type: _______________________

a) Logistics→ Quality Management→ Quality Notification→ Create(QM01)

Use the field-related input help (F4 help) to select the requirednotification type Q1 (Customer Complaint) and confirm your entry.

On the screen that appears, enter the following data and confirm yourentries.

Material: T-AQ3##Plant: 1200Customer: 1033

2. Copy Mr. David Taylor as a contact person for the customer. If he has notyet been created, add his name as the customer contact person.

a) In the tab page Reference Objects, choose the tab page Contact PartnerAddress and use the input help to select Mr. David Taylor as the contactpartner 1033 . If he has not yet been created, choose the pushbuttonCreate contact partner, enter the data for David Taylor and save

your entries.

Continued on next page

414 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 425: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Customer Complaints

3. You tried to call the customer back. The customer however, could notbe reached. Document this transaction by entering an activity for thenotification.

a) In the action box, choose the follow-up function Document TelephoneCall.

Use the field-related input help for the field Calls For to choose DavidTaylor and set the radio button Not Reached to document that you triedunsuccessfully to reach the customer by telephone.

Confirm your entries.

Choose the tab page Immediate Activities to check whether thetelephone call has been documented as an activity.

4. You are responsible for processing this customer complaint further.Therefore, enter your user as the coordinator for this notification.

Then save the notification and make a note of the notification number.

______________________________________

a) Enter your user (PLM412##) as coordinator on the tab page InternalProcessing.

Save the quality notification.

2006/Q2 © 2006 SAP AG. All rights reserved. 415

Page 426: Plm412 en Col62 Fv Part a4

Unit 8: Quality Notifications in Logistics PLM412

Lesson Summary

You should now be able to:� Create a quality notification for a customer complaint.� Describe the procedure for returns and repairs processing, using quality

notifications.

416 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 427: Plm412 en Col62 Fv Part a4

PLM412 Unit Summary

Unit SummaryYou should now be able to:� Create a quality notification as a complaint against a vendor.� Complain when a faulty delivery is received.� carry out a defects recording using an inspection lot at goods receipt.� Use a quality notification to process the problem or defect.� Create a quality notification for a customer complaint.� Describe the procedure for returns and repairs processing, using quality

notifications.

2006/Q2 © 2006 SAP AG. All rights reserved. 417

Page 428: Plm412 en Col62 Fv Part a4

Unit Summary PLM412

418 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 429: Plm412 en Col62 Fv Part a4

PLM412 Test Your Knowledge

Test Your Knowledge

1. When creating a notification, you cannot copy any data from �precedingdocuments�.Determine whether this statement is true or false.□ True□ False

2. You can carry out transfer postings using the action box.Determine whether this statement is true or false.□ True□ False

3. Documents can be assigned while processing a notification.Determine whether this statement is true or false.□ True□ False

4. The report type plays a significant role in the planning of defects recording.Which of the following statements about the report type are correct?Choose the correct answer(s).□ A The report type can be assigned to a work center.□ B The report type cannot be user-specific.□ C A report type must always be available at defects recording.□ D The report type consists of a confirmation profile and a catalog

profile.

5. For defects recording in relation to a goods receipt inspection, the defectnotification must be created manually.Determine whether this statement is true or false.□ True□ False

6. You can switch directly to notification processing from the defects recordingtransaction.Determine whether this statement is true or false.□ True□ False

2006/Q2 © 2006 SAP AG. All rights reserved. 419

Page 430: Plm412 en Col62 Fv Part a4

Test Your Knowledge PLM412

7. A customer complaint can be recorded using the Internet.Determine whether this statement is true or false.□ True□ False

8. Depending on the initial screen of the notification type, you can copy thefollowing data to the notification header when creating a customer complaint:Choose the correct answer(s).□ A Customer□ B Production order□ C Delivery□ D Customer material no.

9. You can access a sales summary from a customer complaint.Determine whether this statement is true or false.□ True□ False

420 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 431: Plm412 en Col62 Fv Part a4

PLM412 Test Your Knowledge

Answers

1. When creating a notification, you cannot copy any data from �precedingdocuments�.

Answer: False

An initial screen for the notification type can be set in Customizing. Onthe initial screen you can, for example, enter data related to the purchasingdocument or the material document. Data can be copied to the notificationfrom the relevant documents.

2. You can carry out transfer postings using the action box.

Answer: True

The action box is set up for each notification type in Customizing.The follow-up functions allow, for example, a transfer posting fromunrestricted-use stock to blocked stock.

3. Documents can be assigned while processing a notification.

Answer: True

If required, documents (for example, purchasing document or materialdocument) can also be assigned at a later stage or the assignment can bechanged.

4. The report type plays a significant role in the planning of defects recording.Which of the following statements about the report type are correct?

Answer: A, C, D

When recording defects with reference to an inspection lot, the report type(defect report type) is used. You can enter this report type when you areaccessing defects recording. The report type can be user-specific or it can beassigned to a work center.

5. For defects recording in relation to a goods receipt inspection, the defectnotification must be created manually.

Answer: False

If defects are recorded with reference to an inspection lot, a defect notificationis automatically created in the system with the corresponding defect items.

2006/Q2 © 2006 SAP AG. All rights reserved. 421

Page 432: Plm412 en Col62 Fv Part a4

Test Your Knowledge PLM412

6. You can switch directly to notification processing from the defects recordingtransaction.

Answer: True

Depending on the settings in the defect class, the defect notification canbe activated immediately. You can also switch from defects recording tonotification processing to, for example, define tasks for elimination of thedefect.

7. A customer complaint can be recorded using the Internet.

Answer: True

The Internet service QMW1 allows notification creation on the Internet. AnITS must be available so that this service can be used.

8. Depending on the initial screen of the notification type, you can copy thefollowing data to the notification header when creating a customer complaint:

Answer: A, C, D

The initial screens are defined in Customizing for the notification type.Depending on the initial screen you select, the corresponding data can beentered and copied to the notification header.

9. You can access a sales summary from a customer complaint.

Answer: False

When you are processing or displaying the customer complaint, you canaccess the sales summary directly. The sales summary contains informationabout existing notifications from this customer.

422 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 433: Plm412 en Col62 Fv Part a4

Unit 9Quality Notifications in Production

Unit OverviewThis unit deals with the use of quality notifications to document and processproblems within a company. You learn about the creation and processing ofnotifications, and order confirmations. The use of notifications in combinationwith a quality inspection in production is also explained.

Unit ObjectivesAfter completing this unit, you will be able to:

� Create quality notifications in the system for general internal problems.� Create and process quality notifications with order confirmation.� Record defects for a quality inspection in production.� Process the quality notifications used to record the defects.

Unit ContentsLesson: Quality Notification During Production ... . . . . . . . . . . . . . . . . . . . . . . . . . .424

Exercise 22: Internal Problem Notifications - Notification Creation ..431Lesson: Quality Inspections and Defect Notifications During Production 436

Exercise 23: Internal Problem Notification - Automatic DefectsRecording.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .441Exercise 24: Internal Problem Notification - General Internal ProblemNotification - Optional Execersise ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .447

2006/Q2 © 2006 SAP AG. All rights reserved. 423

Page 434: Plm412 en Col62 Fv Part a4

Unit 9: Quality Notifications in Production PLM412

Lesson: Quality Notification During Production

Lesson OverviewIn production, unexpected difficulties and problems can arise. Different peopleand departments must be involved in the problem-solving process. This lessoncovers notification processing in production.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Create quality notifications in the system for general internal problems.� Create and process quality notifications with order confirmation.

Business ExampleProblems arising in production must be documented. Therefore, a qualitynotification is created with reference to the relevant production order or salesorder. The causes of the problem and the solutions are documented in this qualitynotification. Different people and departments can be involved in the process.

Figure 216: Internal Problem Notifications: Business Scenario

The prevention of defects is an important factor in the production processes ofyour company. By using quality notifications, you can document and analyzevendor-related or production-related defects and can create tasks to preventnonconformities from occurring in the future. This enables a continuous andlasting quality improvement in your products.

424 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 435: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Quality Notification During Production

Problems During the Production Process

Figure 217: Problems During the Production Process

If problems occur during any stage of the production process, you can create aquality notification manually.

The notification originQ3 is used to process internal problem notifications.

You can use different notification types to create and process internal problems forthe notification origin Q3. Examples are:

� Notification type Q3: Internal problem notification in production� Notification type F3: Defect notification for a material� Notification type Z3: General internal problem notifications (notifications

for the janitor, notifications reporting hardware problems)

Figure 218: Creating an Internal Problem Notification with Reference Object

2006/Q2 © 2006 SAP AG. All rights reserved. 425

Page 436: Plm412 en Col62 Fv Part a4

Unit 9: Quality Notifications in Production PLM412

In Customizing for quality notifications, you can define the initial screen that youwant to appear when you create a notification of this notification type.

You can use the initial screen to supply the quality notification with predefinedproblem-related data.

Figure 219: Creating a Notification for Order Confirmation

If you want to create a quality notification for a production order, you can do thisfrom the confirmation of the production order transaction. This function is onlypossible for production orders and when you are usingconfirmation transactionCO11N .

If notifications already exist for this production order (for example, notificationsrelated to defects recording), then you can make changes to these notifications.

If you are creating a new quality notification, you can freely define the notificationtype.

426 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 437: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Quality Notification During Production

Figure 220: Creation of Complaints Against the Vendor from an ExistingNotification

If, during notification processing, you discover that a defect can be traced back tothe vendor, you can create a complaint against the vendor (notification origin Q2)using the action box in the internal problem notification (notification origin Q3).

You can transfer data from the internal problem notification to the externalnotification (for example, notification type Q2).

Figure 221: Request to Deviate from Specification

2006/Q2 © 2006 SAP AG. All rights reserved. 427

Page 438: Plm412 en Col62 Fv Part a4

Unit 9: Quality Notifications in Production PLM412

If problems occur during a sales order-related production, an external partner canbe notified. You can use the notification action box (internal problem notification)to send an e-mail to the partner that describes the process of requesting permissionto deviate from a specification in more detail.

In this e-mail, the partner is asked to process the request in the Workflow inboxand the inbox can be opened using a link.

The partner can then approve or reject the request for permission to deviate fromthe specification and record a comment.

The comment and the decision are added to the original notification as long text.

Both the partner and the notification processor receive a confirmation e-mail.

Classification of the Defect Item

Figure 222: Classification: Definition of Terms

You can use the Classification System to classify a defect item that has beenentered in a quality notification (that is using coding to describe the item in detail).

When you classify a defect item:

� You go from the quality notification to the classification system� You valuate the characteristic directly on the item detail screen

Class: A class describes a group of objects that have properties in commonor are similar.

Object: An object is a unit that can be classified (for example, material, vendor,notification item, etc.)

428 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 439: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Quality Notification During Production

Characteristic: A characteristic describes the properties of an object (such aslength, weight, basic material).

Characteristic value: Attribute of a characteristic (such as 10 cm, 15 kg, upto 2 tons, copper).

Figure 223: Searching in the Classification System

You can use the Classification System to search for specific defects (or defectitems). You can go directly to the notification display or the notification processingfrom the search results screen.

You can go to the classification system by choosingSAP Menu ->Cross-Application Components -> Classification System. You can usetransactionCL30N to search for objects in classes.

You can use Customizing for the classification systemCross-ApplicationComponents -> Classification System -> Classes (Maintain object types and classtypes) to determine which additional functions should be possible after you havesearched in the classification system.

2006/Q2 © 2006 SAP AG. All rights reserved. 429

Page 440: Plm412 en Col62 Fv Part a4

Unit 9: Quality Notifications in Production PLM412

430 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 441: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Quality Notification During Production

Exercise 22: Internal ProblemNotifications- Notification Creation

Exercise ObjectivesAfter completing this exercise, you will be able to:� Document internal problems with quality notifications.

Business ExampleIf problems occur with a production order, you can record them in a qualitynotification and forward them to be resolved.

Task: Enter Problems That Occur During theProductionIf problems occur during the production, enter them using an internal problemnotification. Document the reasons for the problem and the tasks

1. When the PC T-AQ3## in plant 1200 (desktop PC model 6) is beingmanufactured, you identify that the hard drives (component DPC9003 (20.5GB SCSI hard drive) are defective.

Create a quality notification with reference to the production order for thematerial and describe the subject and the problems that have been identified.

Notification type: _______________________

Hint: On the notification initial screen, use the field-related inputhelp for the production order, tab page Production orders usingInfosystemto select the relevant production order for the T-AQ3##material and the 1200 production plant.

2. Enter your user as the coordinator for the notification.

3. Document the defects that occurred (defective hard drive) as an items in thenotification and execute the defect analysis. When describing the defectlocation, refer to the corresponding component from the structure list.Determine the cause of the defect and create a corresponding corrective task.Enter your user as the processor responsible for this corrective task.

Make a note of the notification number:

______________________________________

4. Make a confirmation for the production order.

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 431

Page 442: Plm412 en Col62 Fv Part a4

Unit 9: Quality Notifications in Production PLM412

Follow the menu path Logistics→ Production→ Shop Floor Control→Confirmation→ Enter→ For Operation→ Time Ticket (CO11N)

Create a quality notification for the order confirmation directly.

Make a note of the notification number:

______________________________________

432 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 443: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Quality Notification During Production

Solution 22: Internal Problem Notifications- Notification CreationTask: Enter Problems That Occur During theProductionIf problems occur during the production, enter them using an internal problemnotification. Document the reasons for the problem and the tasks

1. When the PC T-AQ3## in plant 1200 (desktop PC model 6) is beingmanufactured, you identify that the hard drives (component DPC9003 (20.5GB SCSI hard drive) are defective.

Create a quality notification with reference to the production order for thematerial and describe the subject and the problems that have been identified.

Notification type: _______________________

Hint: On the notification initial screen, use the field-related inputhelp for the production order, tab page Production orders usingInfosystemto select the relevant production order for the T-AQ3##material and the 1200 production plant.

a) Logistics→ Quality Management→ Quality Notification→ Create(QM01)

b) Use the field-related input help to select the notification type Q3 andconfirm your entry.

Use the input help for the production order on the Production ordersusing Infosystem tab page, to select the required production order usingthe 1200 production plant and the T-AQ3## material and chooseExecute. Double-click the order number to transfer the specifications,and then save your entries.

In the tab page Subject enter a description of the problem.

2. Enter your user as the coordinator for the notification.

a) Choose the tab page Partner and enter your user in the fieldCoordinator.

3. Document the defects that occurred (defective hard drive) as an items in thenotification and execute the defect analysis. When describing the defectlocation, refer to the corresponding component from the structure list.Determine the cause of the defect and create a corresponding corrective task.Enter your user as the processor responsible for this corrective task.

Make a note of the notification number:

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 433

Page 444: Plm412 en Col62 Fv Part a4

Unit 9: Quality Notifications in Production PLM412

______________________________________

a) Choose the tab page Items. Use the field-related input help for thefield Defect Type and for the field Defect Location, to characterize thecategory of the defect and the defect location.

Select the item entered and choose the pushbutton Detail View.

Choose the Structure List pushbutton and select theDPC9003assembly for the defect location description.

Choose the Select pushbutton to leave the dialog box.

Then choose the pushbutton Copy to leave the dialog box and go to theDetail view for item dialog box.

Select the item again and choose the Causes tab page. Choose a cause.

Choose the tab page Item Tasks. Use the field-related input help for thetask to enter a suitable corrective task.

Enter your user name as responsible processor for the task and savethe notification.

4. Make a confirmation for the production order.

Follow the menu path Logistics→ Production→ Shop Floor Control→Confirmation→ Enter→ For Operation→ Time Ticket (CO11N)

Create a quality notification for the order confirmation directly.

Make a note of the notification number:

______________________________________

a) Logistics→ Production→ Shop Floor Control→ Confirmation→Enter→ For Operation→ Time Ticket (CO11N)

Use the input help for the production order on the Production ordersusing the info system tab page, to select the required production orderusing the plant1200 and the material T-AQ3## and choose Execute.Double-click the order number to transfer the specifications, and thensave your entries.

If required, you can choose the Quality Inspection pushbutton toexpand the quality management screen area.

Choose the Create Notification pushbutton and create anothernotification in accordance with the criteria listed above. Choose thegreen arrow button (F3) to get back to your time ticket and save yourdata.

434 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 445: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Quality Notification During Production

Lesson Summary

You should now be able to:� Create quality notifications in the system for general internal problems.� Create and process quality notifications with order confirmation.

2006/Q2 © 2006 SAP AG. All rights reserved. 435

Page 446: Plm412 en Col62 Fv Part a4

Unit 9: Quality Notifications in Production PLM412

Lesson: Quality Inspections and Defect NotificationsDuring Production

Lesson OverviewThis lesson gives you a detailed insight into the processes involved in recordingproblems in relation to planned inspections within production. As well asthe different possibilities for recording problems, the lesson also explains thesubsequent process steps.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Record defects for a quality inspection in production.� Process the quality notifications used to record the defects.

Business ExampleThe prevention of defects is an important factor in the production processes ofyour company. By using quality notifications, you can document and analyzevendor-related or production-related defects and can create tasks to preventnonconformities from occurring in the future. This enables a continuous andlasting quality improvement in your products.

Defects Recording in Production

Figure 224: Quality Inspection During Production

436 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 447: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Quality Inspections and Defect Notifications During Production

If defects are identified in an inspection during production (an inspection lot existsfor the order), a quality notification can be created using the defects recordingfunction.

Figure 225: Defects Recording in Production

If the control indicator for the inspection characteristic is set for defects recording,and no defect code is assigned to this characteristic, a dialog box appears when thecharacteristic is rejected, in which you can enter the defect code.

If the inspection is carried out in a subsystem, defect records can only be generatedautomatically. Note: defect codes must be assigned to the characteristic!

2006/Q2 © 2006 SAP AG. All rights reserved. 437

Page 448: Plm412 en Col62 Fv Part a4

Unit 9: Quality Notifications in Production PLM412

Figure 226: Quality Notification Status �Defects Recording�

Quality notifications that are created in the defects recording transaction can beidentified by their status �Defects recording�.

All quality notifications for an inspection lot that have the status �Defectsrecording� are completed when the usage decision is made.

It is possible to monitor defects after the usage decision has been made. To dothis, you must activate the quality notification before the usage decision orsubsequently put the notification in process again.

Figure 227: Activating a Quality Notification

438 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 449: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Quality Inspections and Defect Notifications During Production

You can activate a quality notification with the status �Defects recording�. Thisfunction is available in the defects recording, results recording and usage decisiontransactions.

If a defect record is generated with a defect class, for which the �Activatequality notification� indicator is set in Customizing, the quality notification isautomatically activated.

A quality notification with the status �Defects recording� is activated if one ofthe following occurred:

� A priority was entered� A notification text was entered� A code was entered for the subject� A partner responsible for processing was assigned� One or more tasks were defined

2006/Q2 © 2006 SAP AG. All rights reserved. 439

Page 450: Plm412 en Col62 Fv Part a4

Unit 9: Quality Notifications in Production PLM412

440 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 451: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Quality Inspections and Defect Notifications During Production

Exercise 23: Internal Problem Notification- Automatic Defects Recording

Exercise ObjectivesAfter completing this exercise, you will be able to:� Generate defect data records automatically for critical characteristics in

results recording� Explain the prerequisites necessary for this in the inspection plan.

Business ExampleYou define a defect code for important characteristics in inspection planning. Thisdefect code is automatically stored in a quality notification in results recordingwhen the characteristic is rejected.

Task: Settings in Inspection Planning for AutomaticDefects RecordingDisplay the settings in the inspection plan

1. Display the inspection plan for material T-AQ3## (desktop PC, model 6).This plan is in plant 1200 (Dresden) and has been created in task list groupPLM410##.

For which characteristics is an automatic defects recording provided incase of a rejection?

Which defect codes are used?

Characteristic code group Code Text

____________________________________________________________

____________________________________________________________

____________________________________________________________

____________________________________________________________

2. There is already an inspection lot (inspection lot origin 04) for the productionorder for the material T-AQ3## in plant1200. Record inspection results thatare outside the specifications for this inspection lot.

Save your data.

Hint: You can use transactionQE51N orQA32 to record the results.

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 441

Page 452: Plm412 en Col62 Fv Part a4

Unit 9: Quality Notifications in Production PLM412

3. Display the quality notification that was created in subtask 2. Check theentries on the Items tab page.

442 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 453: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Quality Inspections and Defect Notifications During Production

Solution 23: Internal Problem Notification- Automatic Defects RecordingTask: Settings in Inspection Planning for AutomaticDefects RecordingDisplay the settings in the inspection plan

1. Display the inspection plan for material T-AQ3## (desktop PC, model 6).This plan is in plant 1200 (Dresden) and has been created in task list groupPLM410##.

For which characteristics is an automatic defects recording provided incase of a rejection?

Which defect codes are used?

Characteristic code group Code Text

____________________________________________________________

____________________________________________________________

____________________________________________________________

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 443

Page 454: Plm412 en Col62 Fv Part a4

Unit 9: Quality Notifications in Production PLM412

____________________________________________________________

a) Logistics→ Quality Management→ Quality Planning→ InspectionPlanning→ Inspection Plan→ Display (QP03)

b) Enter the following data to select the inspection plan:

Field Name EntryMaterial: T-AQ3##Plant: 1200Task list group: PLM410##

Confirm your entries.

Select the operation of the plan and choose the pushbuttonInspection Characteristics.

Select all inspection characteristics (icon ) and choose thepushbutton Catalogs.

For the following characteristics, in case of a rejection, the followingcodes are automatically recorded (you can navigate to the followinginspection characteristic with the pushbutton Next Characteristic):

Char-acteris-tic

codegroup

Code Text

10 PC B Operating system does not boot20 PC E Hard drive defective40 PC A Computer not receiving mains voltage40 PC A1 Voltage too high40 PC A2 Voltage too low

2. There is already an inspection lot (inspection lot origin 04) for the productionorder for the material T-AQ3## in plant1200. Record inspection results thatare outside the specifications for this inspection lot.

Save your data.

Hint: You can use transactionQE51N orQA32 to record the results.

a) Record the inspection results and close characteristic processing. Enteranother inspection description, if necessary.

Continued on next page

444 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 455: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Quality Inspections and Defect Notifications During Production

3. Display the quality notification that was created in subtask 2. Check theentries on the Items tab page.

a) Worklist for notifications: Quality Management -> Quality Notification-> Worklist -> Notification -> Display Data (QM11).

Select the notifications for the material T-AQ3##.

Display the notification for notification type F3. Pay attention to thestatus in the notification header and the entries on the tab page Items.

2006/Q2 © 2006 SAP AG. All rights reserved. 445

Page 456: Plm412 en Col62 Fv Part a4

Unit 9: Quality Notifications in Production PLM412

446 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 457: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Quality Inspections and Defect Notifications During Production

Exercise 24: Internal Problem Notification- General Internal Problem Notification -Optional Execersise

Exercise ObjectivesAfter completing this exercise, you will be able to:� Create a general problem notification. The notification system is very

flexible. You can use this for the widest categories of notifications.

Business ExampleYour company uses quality notifications for general internal problem notifications.

Task: Create a general internal problem notificationThe universal use of the quality notification is clarified in one simple example.

1. Your heating is not working. Inform your janitor by creating a qualitynotification for this problem.

Notification type: _______________________

2. Enter your address as the special address for the notification.

3. Enter the group to your right (user) as coordinator for the notification.

Make a note of the notification number:

______________________________________

2006/Q2 © 2006 SAP AG. All rights reserved. 447

Page 458: Plm412 en Col62 Fv Part a4

Unit 9: Quality Notifications in Production PLM412

Solution 24: Internal Problem Notification- General Internal Problem Notification -Optional ExecersiseTask: Create a general internal problem notificationThe universal use of the quality notification is clarified in one simple example.

1. Your heating is not working. Inform your janitor by creating a qualitynotification for this problem.

Notification type: _______________________

a) Logistics→ Quality Management→ Quality Notification→ Create(QM01)

Use the field-related input help (F4 help) to select the requirednotification type Z3 (General Internal Problem Notification) andconfirm your entry.

2. Enter your address as the special address for the notification.

a) In the tab page Problem choose the tab page Author Address and choosethe pushbutton Maintain Partner Address.

Enter your address data.

3. Enter the group to your right (user) as coordinator for the notification.

Make a note of the notification number:

______________________________________

a) On the tab page Problem, enter the group to your right (user) ascoordinator for the notification.

448 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 459: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Quality Inspections and Defect Notifications During Production

Lesson Summary

You should now be able to:� Record defects for a quality inspection in production.� Process the quality notifications used to record the defects.

2006/Q2 © 2006 SAP AG. All rights reserved. 449

Page 460: Plm412 en Col62 Fv Part a4

Unit Summary PLM412

Unit SummaryYou should now be able to:� Create quality notifications in the system for general internal problems.� Create and process quality notifications with order confirmation.� Record defects for a quality inspection in production.� Process the quality notifications used to record the defects.

450 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 461: Plm412 en Col62 Fv Part a4

PLM412 Test Your Knowledge

Test Your Knowledge

1. Quality notifications can be created and processed during confirmation ofthe production order.Determine whether this statement is true or false.□ True□ False

2. No complaint against the vendor can be generated from an internal problemnotification created during production.Determine whether this statement is true or false.□ True□ False

3. Data from the production order can be copied to the notification using theinitial screen for internal problem processing.Determine whether this statement is true or false.□ True□ False

4. It is not possible to automatically record defect records from the resultsrecording transaction.Determine whether this statement is true or false.□ True□ False

5. Existing defect notifications are automatically completed when you make theusage decision for an inspection lot.Determine whether this statement is true or false.□ True□ False

6. A quality notification with the status �Defects recording� is activated whentasks are recorded for the notification.Determine whether this statement is true or false.□ True□ False

2006/Q2 © 2006 SAP AG. All rights reserved. 451

Page 462: Plm412 en Col62 Fv Part a4

Test Your Knowledge PLM412

Answers

1. Quality notifications can be created and processed during confirmation ofthe production order.

Answer: True

A quality notification can be created or processed using the confirmationtransaction CO11N. The required screen areas in transaction CO11N areset in Customizing.

2. No complaint against the vendor can be generated from an internal problemnotification created during production.

Answer: False

You can use the action box to create a complaint against a vendor(forexample, notification type Q2) from an internal problem notification (forexample, notification type Q3).

3. Data from the production order can be copied to the notification using theinitial screen for internal problem processing.

Answer: True

Depending on the initial screen for the notification type, data can be copiedto the notification header from from the production order or from theproduction version.

4. It is not possible to automatically record defect records from the resultsrecording transaction.

Answer: False

If the control indicator �Automatic defects recording� is set for an inspectioncharacteristic, defect codes can be copied automatically to the defectnotification when the characteristic is rejected.

5. Existing defect notifications are automatically completed when you make theusage decision for an inspection lot.

Answer: False

Only defect notifications with the status �Defects recording� areautomatically completed. Active defect notifications are not automaticallycompleted.

452 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 463: Plm412 en Col62 Fv Part a4

PLM412 Test Your Knowledge

6. A quality notification with the status �Defects recording� is activated whentasks are recorded for the notification.

Answer: True

If a change to a notification involves entering tasks for the notification,the status �Defects recording� is reset and this means that the notificationis activated.

2006/Q2 © 2006 SAP AG. All rights reserved. 453

Page 464: Plm412 en Col62 Fv Part a4

Unit 9: Quality Notifications in Production PLM412

454 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 465: Plm412 en Col62 Fv Part a4

Unit 10General Functions of Quality

Notifications

Unit OverviewThis unit explains several general notification functions. It covers Customizingsettings for notification types, as well as status management and field selection.You also learn about the action box and the follow-up actions for tasks.

Unit ObjectivesAfter completing this unit, you will be able to:

� Define new notification types and set up the required screen areas.� Explain the functions and structure of the action box for the notification type.� List the most important functions of the general status management.� Create a status profile and assign it to the notification type.� Explain the purpose of the follow-up actions for tasks.� Use the action log to understand changes to a quality notification.

Unit ContentsLesson: Customizing Settings for Notifications ... . . . . . . . . . . . . . . . . . . . . . . . . . .456

Exercise 25: General Functions - Customizing.. . . . . . . . . . . . . . . . . . . . . . . .473Exercise 26: - Optional exercise - General Functions - Printing theQuality Notification and the Letter of Complaint . . . . . . . . . . . . . . . . . . . . . . . .479

Lesson: Status Management for Notifications .. . . . . . . . . . . . . . . . . . . . . . . . . . . . .484Exercise 27: General Functions - Status Management ... . . . . . . . . . . . .489

Lesson: Other General Functions for Notifications .. . . . . . . . . . . . . . . . . . . . . . . .495Exercise 28: - Optional exercise - General Functions - AutomaticGeneration of Tasks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .501Exercise 29: - Optional exercise - General Functions - Action Log..505Exercise 30: - Optional exercise - General Functions - DocumentManagement System .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .507

2006/Q2 © 2006 SAP AG. All rights reserved. 455

Page 466: Plm412 en Col62 Fv Part a4

Unit 10: General Functions of Quality Notifications PLM412

Lesson: Customizing Settings for Notifications

Lesson OverviewThis lesson covers the different Customizing settings for the notification types.You learn about the creation of a notification type, as well as the screen areas ofthe notification type and the structure of the action box.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Define new notification types and set up the required screen areas.� Explain the functions and structure of the action box for the notification type.

Business ExampleQuality notifications are a flexible tool that can be tailored to suit you company'srequirements. Many settings can be made in Customizing for each notificationtype.

Figure 228: General Functions: Business Scenario

456 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 467: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Customizing Settings for Notifications

You want to adapt the quality notifications functions to suit the requirements ofa particular company. You want to use the general function of the notificationsystem, independently of the notification type, when you are processingnotifications. To do this, you have to make some settings in Customizing. Thegeneral functions include:

� Displaying related notifications� Action Box� Printing shop papers� General status management� Determining Tasks - Monitoring Response Time� Action Log� Follow-up actions for tasks� Creating notifications for original documents� Connection to the document management system

Customizing Settings for the Notification Type

Figure 229: Notification Types: Customizing (1)

In the SAP system, notifications are assigned to the individual applicationcomponents using the notification category.

You use the individual notification types to:

� Define different uses of quality notifications� Select notifications

2006/Q2 © 2006 SAP AG. All rights reserved. 457

Page 468: Plm412 en Col62 Fv Part a4

Unit 10: General Functions of Quality Notifications PLM412

You specify the business purpose of the quality notification when you define thenotification type.

You use the notification origin to define whether the notification type iscustomer-related, vendor-related, or internal.

The notification origin affects the appearance of the screens; it does not affect theoptions for follow-up processes.

Notification Types: Customizing (2)

� IMG: Quality Management -> Quality Notifications� → Notification Creation→ Notification Types

� Define Notification Types: New entries: Specify notification type� Define Number Ranges→Maintain number rangeGroups : In the Not

assigned section, select new notification type and choose number rangegroup. Choose the Assign element/group pushbutton.

� Define Screen Templates→ Define Screen Areas and Tabs: For thenew notification type, choose Notification Header, Simplified View,and Extended View one after the other. In the extended view, youdefine tab pages. Select the required tab page, activate it (tab pagebutton in the tabstrip area), and assign screen areas.

� Allowed Change of Notification Type→ New entries: Enter the newnotification type and the allowed target notification types. A targetnotification type can stem from a different notification type than thenew notification type.

� → Notification Creation→ Notification Content

� Catalogs and Catalog Profiles for Notification Type: Assign� → Notification Creation→ Partners

� Define Partner Determination Procedures Assign PartnerDetermination Procedure to Notif. Type: Select suitable partnerdetermination procedure (if necessary, create one),→ Assign PartnerFunctions to Notification Type

� → Notification Processing→ Response Control

� Define Priorities Priority Type for Notification Type: Select a suitablepriority type (if necessary, create one)

458 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 469: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Customizing Settings for Notifications

Figure 230: Catalog Types in the Notification Type

You can assign several catalogs types to a notification type in Customizing for thenotification type.

When you process this notification type, the system makes available the catalogtypes you have specified

Hint: The use of code groups in notification processing can be influencedby means of authorizations. The authorization object is Q_GP_CODE.

In addition to these catalog types, you can also enter a catalog profile for thenotification type.

2006/Q2 © 2006 SAP AG. All rights reserved. 459

Page 470: Plm412 en Col62 Fv Part a4

Unit 10: General Functions of Quality Notifications PLM412

Figure 231: Entering a Catalog Profile

You can define a catalog profile for a material, a notification type and also fora report type.

The catalog profile specifies which code groups can be used for a certain material,notification type, or report type.

The notification type specifies the assignment of the catalog types to theappropriate object in the notification (for example, defect).

When processing notifications, you can manually change the catalog profile (thesystem usually proposes the catalog profile for the material; however, you can alsochoose the catalog profile for the notification type or an individual catalog profile).

460 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 471: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Customizing Settings for Notifications

Figure 232: Determining the Catalog Profile

When you create and process a quality notification, the catalog profile isdetermined as follows:

� If a catalog profile has been defined in the material, as well as the notificationtype, the system selects the catalog profile in the following sequence:

� 1) From the material� 2) From the notification type

� If there are no catalogs defined in the notification type, then no catalogentries (codes from code groups) will be offered for selection by the systemwhen processing notifications. This means that you cannot assign any codesto the notification.

� If there is no catalog profile defined in the material or in the notificationtype, then all catalog entries (codes from code groups) will be offered forselection by the system when processing notifications.

2006/Q2 © 2006 SAP AG. All rights reserved. 461

Page 472: Plm412 en Col62 Fv Part a4

Unit 10: General Functions of Quality Notifications PLM412

Figure 233: Customizing: Defining Screen Areas

You can freely structure the screens that are displayed during notificationprocessing in Customizing for the notification type.

For each notification type, you can determine:

� The tab pages (tabstrips) that are to be displayed on the screen� The text that is to appear on individual tabs� The screen areas that are to appear on each tab page

The tab pages may be structured differently for the create, change or displayfunctions.

462 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 473: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Customizing Settings for Notifications

Figure 234: Customizing: Defining Tab Pages

For enhanced views for notification transactions (transactions QM*), you canspecify the tabs and assign screen areas to each tab. First, you should copy thesettings from client 000 and check if the standard setup of the screen templates issuitable to meet the requirements of your company's quality notification processesand functions. Then, you can optimize the settings for the tab pages and screenareas. Proceed as follows:

� Look at the available tab pages and screen areas and the fields contained inthem. For each notification origin, you will need a sample notification inwhich you can examine the screen areas.

� Assign the required screen areas to the available tab pages and assignsuitable titles to these tab pages.

Note: The tab page 10\TAB* is at header level in the quality notification,and the tab page 20\TAB* is at item level.

Tip: Check the effects of the settings you make immediately in a separatesession using the sample notification.

If you have not defined any screen areas for the relevant notification type beforeyou create a notification, the system will search for a notification type with thesame notification origin in the standard client 000 and will use the screen areasettings of this notification type. You can transfer the standard settings for therelevant notification type manually into the current client (transaction OIMN)

2006/Q2 © 2006 SAP AG. All rights reserved. 463

Page 474: Plm412 en Col62 Fv Part a4

Unit 10: General Functions of Quality Notifications PLM412

Figure 235: Displaying Related Quality Notifications

Immediately after creating a quality notification, you can display other relatednotifications (dependent on the settings in Customizing).

You can display related notifications in inspection processing (results recording,defects recording and usage decision) as well as in notification processing.

The function allows you to transfer directly to a notification list or to a specificnotification. This provides you with useful additional information from a relatednotification, when you are processing the current notification.

The following is used to determine the related notifications:

� Original data� Statistical database (QMIS)

You can display the following references (dependant on the notification origin):

� Notifications for the material� Notifications for the vendor� Notifications for the customer� Notifications for the combination of material and vendor� Notifications for the combination of material and customer

464 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 475: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Customizing Settings for Notifications

Action Box for a Notification Type

Figure 236: Action Box

In the action box, follow-up functions are defined for each notification type inCustomizing. By using the pushbutton in the action box, the relevant follow-upfunctions are executed and documented in the form of an activity or task in thenotification header.

The function is partially executed directly after the selection, in other words, notwhen the notification is saved.

After the follow-up function has been implemented successfully, a task or anactivity is created.

You can also use a follow-up function to trigger a Workflow task.

The required Customizing entries can be copied from client 000. These arefollow-up functions, follow-up actions and basic data from the catalog of tasksand activities.

Examples of follow-up functions:

� Tightening/resetting quality level� Sending reports� Requesting 8D report� Generating notifications from existing notifications

2006/Q2 © 2006 SAP AG. All rights reserved. 465

Page 476: Plm412 en Col62 Fv Part a4

Unit 10: General Functions of Quality Notifications PLM412

Figure 237: Action Box (Customizing 1): Plan Follow-Up Functions

You can use the action box to execute several functions, which are required duringnotification processing, with a mouse click. These functions are integrated inthe action box as individual follow-up functions and are documented as tasks oractivities in the notification.

Some follow-up functions have already been defined for each notification type inthe standard system. These can be transferred from client 000.

You can define your own follow-up functions in Customizing.

You can define the follow-up functions as follows:

� As simple functions that can be performed repeatedly and that areindependent of other follow-up functions.

� As part of a larger process. These follow-up functions are then dependenton other follow-up functions being executed first and if required, may onlybe performed once.

If you define several follow-up functions that belong to the same process and thatare to be performed in a specific sequence, you must also define appropriate rulesfor these follow-up functions.

466 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 477: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Customizing Settings for Notifications

Figure 238: Action Box (Customizing 2): Create Follow-Up Functions

On the detail screen, you define:

� The function module that is to be called when the follow-up function isexecuted

� Whether the follow-up function is to be documented as a task or activity, ornot documented at all in the notification

� Whether the follow-up function is to be displayed in every processing mode� What view (extended/simplified view) the follow-up function is to be

displayed� Whether the follow-up function is available during notification and task

processing, or whether it is just available either in notification or taskprocessing

� How the follow-up function is to be defined in the action box (icon, textor both)

� Which code group and code is to be entered for the generated task or activityin the notification.

2006/Q2 © 2006 SAP AG. All rights reserved. 467

Page 478: Plm412 en Col62 Fv Part a4

Unit 10: General Functions of Quality Notifications PLM412

You define specific details for a task:

� Workflow tasks that are to be generated in conjunction with a follow-upfunction

� The function module that is to be called when you save the notificationFor example, you can use this function module to enter or edit data in theWorkflow container.

� The status that should be set for the generated task (for example, released orcompleted)

� Rules for the follow-up function (for example, how often you can execute afollow-up function).

Figure 239: Action Box (Customizing 3):Define Follow-Up Functions

A dependent follow-up function only becomes active if it is explicitly allowedby another follow-up function.

In our example, you must specify which follow-up functions are to be performedonce the first follow-up function (�Send confirmation of receipt�) has beenexecuted (for example, �Send interim notice� or �Send final notice�).

468 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 479: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Customizing Settings for Notifications

Figure 240: Action Box (Customizing 4): Follow-Up Functions 1

Figure 241: Action Box (Customizing 5): Follow-Up Functions 2

2006/Q2 © 2006 SAP AG. All rights reserved. 469

Page 480: Plm412 en Col62 Fv Part a4

Unit 10: General Functions of Quality Notifications PLM412

Figure 242: Action Box (Customizing 6): Follow-Up Functions 3

Figure 243: Action Box (Customizing 7): Follow-Up Functions 4

The function group QM10 includes the copy templates for own function modules.When you use the action box, please also pay attention to the documentation inCustomizing.

470 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 481: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Customizing Settings for Notifications

Print Control for Notifications

Figure 244: Printing a Quality Notification

In Customizing, you can define the papers to be printed for a notification type.

In the print dialog box, you can predefine various spool attributes (language forprintout, print immediately, etc).

The archive mode controls whether notifications are printed only, archived only,or both.

You can set the print control for each notification type, each user and each plant.

You can also use the action box to send the following additional notices by mail tothe notification partners:

� Confirmation of receipt� Interim notice� Final notice

2006/Q2 © 2006 SAP AG. All rights reserved. 471

Page 482: Plm412 en Col62 Fv Part a4

Unit 10: General Functions of Quality Notifications PLM412

Print Control: Customizing

� Definition of shop papers:

� Name, print program, form, description

� Specification of printer:

� User-dependent� Dependent on field contents

� In Customizing for print control, you assign all valid shop papers to thenotification type.

� Certain settings are contained in the standard system for individual workareas. If you want to change the layout of the lists, you should not change thestandard forms, but should copy (transaction SE71) them under a new nameand make the changes in the newly-created forms.

� In addition, you define whether the shop papers are displayed with selectionindicators when the print proposal is made.

472 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 483: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Customizing Settings for Notifications

Exercise 25: General Functions -Customizing

Exercise ObjectivesAfter completing this exercise, you will be able to:� Use Customizing to structure the notification system to suit your needs.

Business ExampleOne of the basic tasks for the implementation of quality notifications is to makethe required Customizing settings for the notification system.

Task: Customizing settings for quality notificationsAnswer the following questions concerning Customizing for quality notifications.

1. You want to create your own notification type with company-specific screenareas and tab pages. How do you proceed?

2. A contact person must always be entered when you create a customercomplaint.How can you achieve this?

3. When creating customer complaints, you want to refer to the sales order ordelivery from which the complaint comes. You can do this by defining thecorresponding initial screen in Customizing.Where do you make this setting?

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 473

Page 484: Plm412 en Col62 Fv Part a4

Unit 10: General Functions of Quality Notifications PLM412

What is the corresponding initial screen called?

4. You want to display related notifications for a customer complaint. Howcan you achieve this?

5. You want to structure the action box of the customer complaint notificationin accordance with your company-specific requirements.How do you proceed?

474 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 485: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Customizing Settings for Notifications

Solution 25: General Functions -CustomizingTask: Customizing settings for quality notificationsAnswer the following questions concerning Customizing for quality notifications.

1. You want to create your own notification type with company-specific screenareas and tab pages. How do you proceed?

Answer: Tools→ Customizing→ IMG→ Execute Project (SPRO)→ SAPReference IMG→Quality Management→ Quality Notification→ Notification Creation→Notification Types→ Define Notification TypesIn the customer namespace, you can create your own notification type.Tools→ Customizing→ IMG→ Execute Project (SPRO)→ SAP ReferenceIMG →Quality Management→ Quality Notification→ Notification Creation→Notification Types→ Define Screen Templates→ Define Screen Areas andTabs.

Related InformationYou can also get to the Customizing for Quality Management via transactionQCC0.

You can also get to the Customizing for Quality Notifications via transactionQCC2.

2. A contact person must always be entered when you create a customercomplaint.

How can you achieve this?

Answer: Tools→ Customizing→ IMG→ Execute Project (SPRO)→ SAPReference IMG→Quality Management→ Quality Notification→ Notification Creation→Partners→ Define Partner Determination ProceduresChoose Assign Partner Determination Procedure to Notif. Type. Thenotification type Q1 is assigned to the partner determination procedure Q1.Go back and choose Define Partner Determination Procedure.Select Quality Management and choose the pushbutton Display Partner.Select the entry Q1 and double-click on Functions Determination Procedure.In the contact persons line, you can set the indicator Partner mandat.

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 475

Page 486: Plm412 en Col62 Fv Part a4

Unit 10: General Functions of Quality Notifications PLM412

3. When creating customer complaints, you want to refer to the sales order ordelivery from which the complaint comes. You can do this by defining thecorresponding initial screen in Customizing.

Where do you make this setting?

What is the corresponding initial screen called?

Answer: Tools→ Customizing→ IMG→ Execute Project (SPRO)→ SAPReference IMG→Quality Management→ Quality Notification→ Notification Creation→Notification Types→ Define Screen Templates→ Define Initial Screens.Call up the F1 help for the field Initial Screen. The corresponding initialwindow is Screen 0130.

4. You want to display related notifications for a customer complaint. Howcan you achieve this?

Answer: Tools→ Customizing→ IMG→ Execute Project (SPRO)→ SAPReference IMG→Quality Management→ Quality Notifications→ Information System→Activate Reference to Related NotificationsSelect the notification type Q1 and choose the Detail pushbutton. On thedetail screen, you can select the criteria for which the related notificationsare to be displayed.Tools→ Customizing→ IMG→ Execute Project (SPRO)→ SAP ReferenceIMG →Quality Management→ Quality Notification→ Notification Creation→Notification Types→ Define Screen Templates→ Define Screen Areas andTabs.Select the notification type Q1 and select Extended View: Tabstrips andScreen Areas.Select the Internal Processing tab page and choose the Details pushbutton.Due to the inclusion of the screen area 025, the pushbutton for relatednotifications appears in your Q1 notification.

Continued on next page

476 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 487: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Customizing Settings for Notifications

5. You want to structure the action box of the customer complaint notificationin accordance with your company-specific requirements.

How do you proceed?

Answer: Tools→ Customizing→ IMG→ Execute Project (SPRO)→ SAPReference IMG→Quality Management→ Quality Notifications→ Notification Processing→Additional Notification Functions→ Define Action Box→ Define Functionsfor the Action BoxSelect the notification type Q1 and double-click the Activities pushbutton.Here you can include additional follow-up functions or change existingfollow-up functions.

2006/Q2 © 2006 SAP AG. All rights reserved. 477

Page 488: Plm412 en Col62 Fv Part a4

Unit 10: General Functions of Quality Notifications PLM412

478 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 489: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Customizing Settings for Notifications

Exercise 26: - Optional exercise -General Functions - Printing the QualityNotification and the Letter of Complaint

Exercise ObjectivesAfter completing this exercise, you will be able to:� Print a letter of complaint, as well as an 8D report for the complaint against a

vendor.

Business ExampleYou inform your vendor of the problem, by sending him a letter of complaint.

An 8D report can also be printed as an additional document and sent to the vendor.

Task 1: Optional: Create a quality notification

Hint: In training course PLM412, you can also use your Q2 notificationfrom the Quality notifications in logistics chapter. You can select thisnotification using the input help.

1. You ordered 50, 21� monitors (material: T-AQ2##) from your vendor 1000(C.E.B Berlin). When the monitors are delivered, you discover that they are17� monitors. You want to complain about the delivery. Create a complaintfor this problem with one defect item. Create the notification with referenceto the material document (goods receipt number).

Hint: Select the corresponding material document using the materialT-AQ2## and the vendor 1000 and copy the item from the document.

Task 2: Print letter of complaintThe notification overview and the item overview belong to the shop papers ofthe notifications. You can also print a letter of complaint for notifications ofnotification origin Q2.

1. Print a letter of complaint to your vendor relating to the incorrect delivery.Check the letter before printing using the print preview function.

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 479

Page 490: Plm412 en Col62 Fv Part a4

Unit 10: General Functions of Quality Notifications PLM412

2. How can you save the letter to the optical archive at the same time as itis printed?

3. Also print an 8D report using the corresponding function in the action box.

480 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 491: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Customizing Settings for Notifications

Solution 26: - Optional exercise -General Functions - Printing the QualityNotification and the Letter of ComplaintTask 1: Optional: Create a quality notification

Hint: In training course PLM412, you can also use your Q2 notificationfrom the Quality notifications in logistics chapter. You can select thisnotification using the input help.

1. You ordered 50, 21� monitors (material: T-AQ2##) from your vendor 1000(C.E.B Berlin). When the monitors are delivered, you discover that they are17� monitors. You want to complain about the delivery. Create a complaintfor this problem with one defect item. Create the notification with referenceto the material document (goods receipt number).

Hint: Select the corresponding material document using the materialT-AQ2## and the vendor 1000 and copy the item from the document.

a) Logistics→ Quality Management→ Quality Notification→ Create(QM01)

Use the field-related input help (F4) to choose the notification type Q2(complaint against vendor) and confirm your entry. In the dialog thatappears, use the field-related input help for the material documentto select the required material document by specifying the materialT-AQ2## (## is your group number) and the vendor 1000. ChooseExecute (F8) to start the selection. Copy the required materialdocument by double clicking on the document number. Copy theitem for the material document using the field-related input help andconfirm your entries.

Enter a subject as well as the coordinator.

Save your notification.

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 481

Page 492: Plm412 en Col62 Fv Part a4

Unit 10: General Functions of Quality Notifications PLM412

Task 2: Print letter of complaintThe notification overview and the item overview belong to the shop papers ofthe notifications. You can also print a letter of complaint for notifications ofnotification origin Q2.

1. Print a letter of complaint to your vendor relating to the incorrect delivery.Check the letter before printing using the print preview function.

a) Logistics→ Quality Management→ Quality Notification→ Change(QM02)

Confirm the proposed notification number and choose Notification→Print→ Notification, select the shop paper 5999 (complaint report) andchoose thePrint Preview pushbutton to display the letter of complaint.

Hint: You can use LOCL as the output device.

2. How can you save the letter to the optical archive at the same time as itis printed?

Answer: Exit the print preview. Select the shop paper 5999 (complaintreport) and choose the Select (F2) pushbutton. Use the field-related inputhelp to select the entry Print and archive for the field Store mode. Choosethe Print/Fax pushbutton to simultaneously print out the document and storeit in the optical archive.

3. Also print an 8D report using the corresponding function in the action box.

Answer: Go back into the notification and choose the follow-up functionRequest 8D report in the action box.Display the 8D report using the Print preview pushbutton.

482 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 493: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Customizing Settings for Notifications

Lesson Summary

You should now be able to:� Define new notification types and set up the required screen areas.� Explain the functions and structure of the action box for the notification type.

2006/Q2 © 2006 SAP AG. All rights reserved. 483

Page 494: Plm412 en Col62 Fv Part a4

Unit 10: General Functions of Quality Notifications PLM412

Lesson: Status Management for Notifications

Lesson OverviewIn this lesson, you learn about status management for notifications. General statusmanagement, the status profile, and user statuses are covered.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� List the most important functions of the general status management.� Create a status profile and assign it to the notification type.

Business ExampleYou want to adapt the quality notifications functions to suit the requirements ofa particular company. You want to use the general function of the notificationsystem, independently of the notification type, when you are processingnotifications. To do this, you have to make some settings in Customizing. Thegeneral functions include:

� Display of related notifications� Action box� Printing of shop papers� General status management� Determining Tasks - Monitoring Response Time� Action log� Follow-up actions for tasks� Creating notifications for original documents� Connection to the Document Management System

484 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 495: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Status Management for Notifications

Status Management for Notifications

Figure 245: Status Management for Quality Notifications

A system status is predefined in the system and cannot be changed.

You can freely define a user status in Customizing.

Statuses influence the allowed business transactions.

Figure 246: General Status Management (1)

2006/Q2 © 2006 SAP AG. All rights reserved. 485

Page 496: Plm412 en Col62 Fv Part a4

Unit 10: General Functions of Quality Notifications PLM412

General status management is used for various objects within the SAP system(such as inspection lots, production orders, CO orders etc.).

The system statuses are managed for quality notifications in general, as well as forall tasks. Activities in a quality notification are not subject to status management.

Several statuses can be active at any one time.

A status can have the following effect on a business transaction:

� Allow� Allow with warning� Prohibit

When you perform a transaction, you can set or delete a status.

A transaction is allowed:

� If it is allowed by at least one status� If it is not prohibited by a status

A status profile can be used for different object types at the same time (such as,quality notifications, maintenance notifications, tasks etc.).

Figure 247: General Status Management (2)

A system status informs the user that a certain function was carried out on anobject.

The allowed transactions usually change each time a status changes.

486 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 497: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Status Management for Notifications

Figure 248: Status Profile: Customizing

Quality notifications use the general status management functions for objects inthe SAP System. In addition to the fixed, predefined system statuses in generalstatus management, you can define your own status profiles, to control thesequence of particular processes. Examples of such processes are �Release a task�or �Complete a quality notification�.

A status profile is assigned to a notification type. Different status profiles areallowed, depending on the notification type, either for the notification as a wholeor for individual tasks.

You can define the user status for a status object by using the status profile.

You use the status sequence numbers to control the order in which the user statuscan be set.

You can freely define the user status within a status profile.

2006/Q2 © 2006 SAP AG. All rights reserved. 487

Page 498: Plm412 en Col62 Fv Part a4

Unit 10: General Functions of Quality Notifications PLM412

488 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 499: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Status Management for Notifications

Exercise 27: General Functions - StatusManagement

Exercise ObjectivesAfter completing this exercise, you will be able to:� Explain the effects of status management in notification processing.

Business ExampleWith user statuses, you can adapt notification processing to suit the requirementsof your company.

Task: System status and user status for notificationprocessingCreate an internal problem notification.

Hint: In training course PLM412, you do not need to create anotherQ3 notification here.

You can also use your Q3 notification from the chapter Qualitynotifications in production here. You can select this notification withthe input help.

1. When the PC T-AQ3## in plant 1200 (desktop PC model 6) is beingmanufactured, you identify that the hard drives (component DPC9003 (20.5GB SCSI hard drive) are defective.

Create a quality notification with reference to the production order for thematerial and describe the subject and the problems that have been identified.Enter your user as the coordinator of the notification.

Save the notification and note the status of the notification.

Notification number: ______________________________________

Notification status: _____________________________________

2. Access the notification again and perform the defect analysis. Determine thecause of the defect and create a corresponding corrective task. Enter youruser as the processor responsible for this corrective task.

Save the notification and note the status of the notification.

Notification number: ______________________________________

Notification status: _____________________________________

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 489

Page 500: Plm412 en Col62 Fv Part a4

Unit 10: General Functions of Quality Notifications PLM412

3. Access the notification again and complete the notification. What happens?

________________________________________

________________________________________

________________________________________

What must you do to complete the notification?

________________________________________

________________________________________

________________________________________

490 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 501: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Status Management for Notifications

Solution 27: General Functions - StatusManagementTask: System status and user status for notificationprocessingCreate an internal problem notification.

Hint: In training course PLM412, you do not need to create anotherQ3 notification here.

You can also use your Q3 notification from the chapter Qualitynotifications in production here. You can select this notification withthe input help.

1. When the PC T-AQ3## in plant 1200 (desktop PC model 6) is beingmanufactured, you identify that the hard drives (component DPC9003 (20.5GB SCSI hard drive) are defective.

Create a quality notification with reference to the production order for thematerial and describe the subject and the problems that have been identified.Enter your user as the coordinator of the notification.

Save the notification and note the status of the notification.

Notification number: ______________________________________

Notification status: _____________________________________

a) Logistics→ Quality Management→ Quality Notification→ Create(QM01)

Use the field-related input help to select the notification type Q3(internal problem notification).

Use the input help for the production order on the Production ordersusing Infosystem tab page, to select the required production order usingthe 1200 production plant and the T-AQ3## material and chooseExecute. Double-click the order number to transfer the specifications,and then save your entries.

In the tab page Subject enter a description of the problem.

At notification header level, choose the Status Details pushbutton todisplay the status of the notification. The notification has system statusOSNO (and possibly system status OSTS) and user status INIT.

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 491

Page 502: Plm412 en Col62 Fv Part a4

Unit 10: General Functions of Quality Notifications PLM412

2. Access the notification again and perform the defect analysis. Determine thecause of the defect and create a corresponding corrective task. Enter youruser as the processor responsible for this corrective task.

Save the notification and note the status of the notification.

Notification number: ______________________________________

Notification status: _____________________________________

a) Logistics→ Quality Management→ Quality Notification→ Change(QM02)

Confirm the proposed notification number and choose the Items tabpage. Use the field-related input help for the field Defect Type and forthe field Defect Location, to characterize the category of the defectand the defect location.

Choose the Causes tab page and use the F4 input help to enter a defectcause.

Choose the tab page Item Tasks. Use the field-related input help forthe task to enter a suitable corrective task. Enter your group name asresponsible processor and save the notification.

Select the line of the Item Task and choose the Status Details pushbuttonat the bottom of the screen. The task has system status TSOS as wellas user status INIT.

At notification header level, choose the Status Details pushbutton todisplay the status of the notification. The notification has the systemstatuses OSNO and OSTS and the user status INIT.

3. Access the notification again and complete the notification. What happens?

________________________________________

________________________________________

________________________________________

What must you do to complete the notification?

________________________________________

________________________________________

Continued on next page

492 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 503: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Status Management for Notifications

________________________________________

a) Logistics→ Quality Management→ Quality Notification→ Change(QM02)

Confirm the proposed notification number and choose the Completepushbutton. A message appears informing you that the notificationcannot be completed due to the current user status and the outstandingtasks.

Complete the outstanding task first. Note that you can only completethe task if the task no longer has the status INIT (user status). Selectthe outstanding task and on the task screen choose the pushbuttonStatus Details. Manually change the user status to Released forProcessing and return to the task screen by choosing Back (F3). Due tothis manual change, the user status was changed from INIT to REL.Choose the Successful pushbutton to complete the task. The systemstatus of the task changes from TSOS to TSCO. The system status ofthe notification changes from OSTS to ATCO.

If you now again choose the Complete pushbutton at notification headerlevel, a message appears, informing you that the notification cannotbe completed due to the current user status.

Choose the Status Details pushbutton at notification header level.Manually change the user status to Released for Processing and returnto the notification screen by choosing Back (F3). Due to this manualchange, the user status was changed from INIT to REL. Choose theComplete pushbutton to complete the notification. Confirm the popupthat appears by choosing Continue.

The system status of the notification changes from OSNO to NOCO.Furthermore, the system status NOTI is set at notification completion.

2006/Q2 © 2006 SAP AG. All rights reserved. 493

Page 504: Plm412 en Col62 Fv Part a4

Unit 10: General Functions of Quality Notifications PLM412

Lesson Summary

You should now be able to:� List the most important functions of the general status management.� Create a status profile and assign it to the notification type.

494 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 505: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Other General Functions for Notifications

Lesson: Other General Functions for Notifications

Lesson OverviewThis lesson covers the general functions for the notification types. It deals with thefollow-up actions for tasks, as well as the creation of a notification for an originaldocument and the field selection for notifications.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Explain the purpose of the follow-up actions for tasks.� Use the action log to understand changes to a quality notification.

Business ExampleYou want to adapt the quality notifications functions to suit the requirements ofa particular company. You want to use the general function of the notificationsystem, independently of the notification type, when you are processingnotifications. To do this, you have to make some settings in Customizing. Thegeneral functions include:

� Display of related notifications� Action box� Printing of shop papers� General status management� Determining Tasks - Monitoring Response Time� Action Log� Follow-up actions for tasks� Creating notifications for original documents� Connection to the document management system

2006/Q2 © 2006 SAP AG. All rights reserved. 495

Page 506: Plm412 en Col62 Fv Part a4

Unit 10: General Functions of Quality Notifications PLM412

Task Determination and the Action Log

Figure 249: Determining Tasks - Monitoring Response Time

You can use the �Determine tasks� function to generate standard tasks for thecurrent notification. You enter these standard tasks in the response profile.

You can define the following information in the response profile:

� Priority for the notification� code group� Code� Time interval� Time unit� Person responsible for task (default value)

In the response profile, you can define the days and times when tasks are to beprocessed.

The response profile and the catalog profiles are defined in Customizing andassigned to the notification type using response time monitoring. (QualityManagement→ Quality Notifications→ Notification Processing→ ResponseControl)

496 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 507: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Other General Functions for Notifications

Figure 250: Action Log for the Quality Notification

The action log displays an overview of all the changes in the life-cycle of anotification.

The log contains information about notification statuses from status managementand from change documents.

Follow-Up Actions for Tasks

Figure 251: Follow-Up Actions for Tasks (1) - Maintain Catalog

2006/Q2 © 2006 SAP AG. All rights reserved. 497

Page 508: Plm412 en Col62 Fv Part a4

Unit 10: General Functions of Quality Notifications PLM412

The Follow-up action indicator in Customizing for catalog types controls whethera follow-up action can be defined for a code.

Figure 252: Follow-Up Actions for Tasks (2): Customizing

The system can trigger a chain of function modules as a follow-up action.

You can use the function module QM10_COPY_REFERENCE_FORM (functionQM10) as a copy model for your own follow-up actions.

You can take the status of the task into account and can control authorizationsusing the transaction for the follow-up action.

The function module can be called before, after or at the same time as thenotification is updated.

498 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 509: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Other General Functions for Notifications

Other General Functions

Figure 253: Creating a Quality Notification for an Original Document

You can create a quality notification for a scanned document.

You can call up this document at any time during notification processing.

You can assign originals that are scanned retroactively to an existing qualitynotification.

Figure 254: Quality Notifications - Link to DMS

You can assign any number of master records from the document managementsystem to the header of a quality notification.

2006/Q2 © 2006 SAP AG. All rights reserved. 499

Page 510: Plm412 en Col62 Fv Part a4

Unit 10: General Functions of Quality Notifications PLM412

You can display an original document directly from a quality notification.

Figure 255: Field Selection

The fields in a notification are combined in screen groups.

There are predefined modifiable fields for each screen group.

The attributes for each field, such as (required entry, display etc.) can be selectedor deselected.

Additionally, the settings for each field can be controlled using the Influencingfield function.

500 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 511: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Other General Functions for Notifications

Exercise 28: - Optional exercise - GeneralFunctions - Automatic Generation of Tasks

Exercise ObjectivesAfter completing this exercise, you will be able to:� Include automatically generated tasks in the notification.

Business ExampleThe response time monitoring function is used to automatically generate a taskfor a notification.

Task 1: Automatic task determination for the qualitynotification

Hint: In training course PLM412, you can also use your Q1 notificationfrom the Quality notifications in logistics chapter. You can use the inputhelp to select this notification.

1. Customer 1033 (Karsson High Tech) wants to complain about a PC with thematerial number T-AQ3## (Desktop PC6/54), plant 1200. Create a qualitynotification for this problem.

Notification type:__________________________

Task 2: Determine tasks for the notificationYou can carry out a task determination for the tasks for the notification header.

1. Determine the predefined tasks. Which tasks are these?

code group Code Text

_________________________________________

_________________________________________

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 501

Page 512: Plm412 en Col62 Fv Part a4

Unit 10: General Functions of Quality Notifications PLM412

2. What settings must you make before you can use the automatic taskgeneration function?

502 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 513: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Other General Functions for Notifications

Solution 28: - Optional exercise - GeneralFunctions - Automatic Generation of TasksTask 1: Automatic task determination for the qualitynotification

Hint: In training course PLM412, you can also use your Q1 notificationfrom the Quality notifications in logistics chapter. You can use the inputhelp to select this notification.

1. Customer 1033 (Karsson High Tech) wants to complain about a PC with thematerial number T-AQ3## (Desktop PC6/54), plant 1200. Create a qualitynotification for this problem.

Notification type:__________________________

a) Logistics→ Quality Management→ Quality Notification→ Create(QM01)

Use the field-related input help (F4 help) to select the requirednotification type Q1 (Customer Complaint) and confirm your entry.

On the screen that appears, enter the following data and confirm yourentries.

Material: T-AQ3##Plant: 1200Customer: 1033

Task 2: Determine tasks for the notificationYou can carry out a task determination for the tasks for the notification header.

1. Determine the predefined tasks. Which tasks are these?

code group Code Text

_________________________________________

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 503

Page 514: Plm412 en Col62 Fv Part a4

Unit 10: General Functions of Quality Notifications PLM412

_________________________________________

a) Choose the tab page Immediate Tasks and in the application functionbar choose Determine Tasks or choose Edit→ Tasks→ Determine.

The following immediate task is displayed:

code group Code TextRADIO-01 1 Send spare part

Enter your group number as coordinator on the tab page InternalProcessing.

Save your notification.

2. What settings must you make before you can use the automatic taskgeneration function?

Answer: Tools→ Customizing→ IMG→ Execute Project (SPRO)→ SAPReference IMG→Quality Management→ Quality Notifications→ Notification Processing→ Response Control→ Define Response Monitoring→ Define ResponseProfileSelect the response Radio and double-click on Response Times. On thisscreen, you can define tasks for automatic task generation that depend onthe priority.Tools→ Customizing→ IMG→ Execute Project (SPRO)→ Display SAPReference IMG→Quality Management→ Quality Notifications→ Notification Processing→Response Control→ Define Response Monitoring→ Define Service ProfileSelect the service profile QM and choose the Choose Level - Detail (servicetimes) pushbutton. On this screen, you can define the service times ofyour company.Tools→ Customizing→ IMG→ Execute Project (SPRO)→ Display SAPReference IMG→Quality Management→ Quality Notifications→ Notification Processing→ Response Control→ Define Response Monitoring→ Response Timefor Notification TypeIn this Customizing transaction, you assign the service profile and theresponse profile to your notification type.

504 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 515: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Other General Functions for Notifications

Exercise 29: - Optional exercise - GeneralFunctions - Action Log

Exercise ObjectivesAfter completing this exercise, you will be able to:� Use the action log to trace changes that have been made to a quality

notification.

Business ExampleYou use the action log to trace changes that have been made to a qualitynotification.

Task: Action log for the notificationChange the priority of a notification that you created in training course PLM412.

1. Change the priority in a notification for your material T-*## and save thenotification.

2. Use the action log to show the changes that have been made to thenotification. What data was logged?

2006/Q2 © 2006 SAP AG. All rights reserved. 505

Page 516: Plm412 en Col62 Fv Part a4

Unit 10: General Functions of Quality Notifications PLM412

Solution 29: - Optional exercise - GeneralFunctions - Action LogTask: Action log for the notificationChange the priority of a notification that you created in training course PLM412.

1. Change the priority in a notification for your material T-*## and save thenotification.

a) Logistics→ Quality Management→ Quality Notification→ Change(QM02)

On the initial screen, enter the notification number from a previousexercise and confirm your entry.

Change the priority of the notification and save the notification.

2. Use the action log to show the changes that have been made to thenotification. What data was logged?

Answer: Access the notification again and choose the Action Logpushbutton.The changes in the priority (old priority and new priority), as well as the datesthat have changed due to the change in the priority have all been logged.

506 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 517: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Other General Functions for Notifications

Exercise 30: - Optional exercise - GeneralFunctions - Document ManagementSystem

Exercise ObjectivesAfter completing this exercise, you will be able to:� Use the Document Management System when processing notifications.

Business ExampleYou want to make design drawings that are stored in the DMS available duringnotification processing.

Task: Assign documents to the notificationConnection to the Document Management System

1. What settings must you make before you can use the document managementsystem during notification processing, and where can you find these settings?

2006/Q2 © 2006 SAP AG. All rights reserved. 507

Page 518: Plm412 en Col62 Fv Part a4

Unit 10: General Functions of Quality Notifications PLM412

Solution 30: - Optional exercise - GeneralFunctions - Document ManagementSystemTask: Assign documents to the notificationConnection to the Document Management System

1. What settings must you make before you can use the document managementsystem during notification processing, and where can you find these settings?

Answer: Tools→ Customizing→ IMG→ Execute Project (SPRO)→ SAPReference IMG→Quality Management→ Quality Notifications→ Notification Creation→Notification Types→ Define Screen Templates→ Define Screen Areas andTabs.Select the notification type Q1 and double click Extended View: Tabstripsand Screen Areas.Select the Internal Processing tab page and choose the Details pushbutton.Due to the inclusion of the screen area 092, the screen area for the DMS isdisplayed in your Q1 notification.

508 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 519: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Other General Functions for Notifications

Lesson Summary

You should now be able to:� Explain the purpose of the follow-up actions for tasks.� Use the action log to understand changes to a quality notification.

2006/Q2 © 2006 SAP AG. All rights reserved. 509

Page 520: Plm412 en Col62 Fv Part a4

Unit Summary PLM412

Unit SummaryYou should now be able to:� Define new notification types and set up the required screen areas.� Explain the functions and structure of the action box for the notification type.� List the most important functions of the general status management.� Create a status profile and assign it to the notification type.� Explain the purpose of the follow-up actions for tasks.� Use the action log to understand changes to a quality notification.

510 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 521: Plm412 en Col62 Fv Part a4

PLM412 Test Your Knowledge

Test Your Knowledge

1. The screen areas for each tab page can be defined in Customizing for thenotification type.Determine whether this statement is true or false.□ True□ False

2. When you create your own notification type, you define the notificationorigin for this notification type.Determine whether this statement is true or false.□ True□ False

3. In the settings for the action box, you can define whether or not a follow-upfunction can be executed more than once.Determine whether this statement is true or false.□ True□ False

4. The status of an activity defines whether the notification is ready to becompleted.Determine whether this statement is true or false.□ True□ False

5. You can work with the status profile only for tasks in notifications.Determine whether this statement is true or false.□ True□ False

6. A system status is predefined in the system and cannot be changed.Determine whether this statement is true or false.□ True□ False

2006/Q2 © 2006 SAP AG. All rights reserved. 511

Page 522: Plm412 en Col62 Fv Part a4

Test Your Knowledge PLM412

7. The action log is used to represent important changes in the �life cycle�of a notification.Determine whether this statement is true or false.□ True□ False

8. Documents from the Document Management System can always be assignedto a quality notification.Determine whether this statement is true or false.□ True□ False

9. You can assign follow-up actions to the codes in the code groups of thetask catalog.Determine whether this statement is true or false.□ True□ False

512 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 523: Plm412 en Col62 Fv Part a4

PLM412 Test Your Knowledge

Answers

1. The screen areas for each tab page can be defined in Customizing for thenotification type.

Answer: True

Customizing is used to define the screen areas for the simplified view andthe extended view for each notification type. In the extended view, you canalso make additional settings for the tab pages.

2. When you create your own notification type, you define the notificationorigin for this notification type.

Answer: True

You can define your own notification types in Customizing. When youare creating notification types, you define the notification category and thenotification origin to which they belong.

3. In the settings for the action box, you can define whether or not a follow-upfunction can be executed more than once.

Answer: True

You define whether or not a follow-up function can be executed more thanonce in the Customizing settings for follow-up functions. In addition,you can define whether or not a follow-up function is to be aviailable forimmediate execution or whether it is to be a dependent follow-up function.

4. The status of an activity defines whether the notification is ready to becompleted.

Answer: False

The activities in a notification do not have a status. A notification can onlybe completed if all tasks in the notification have been completed.

5. You can work with the status profile only for tasks in notifications.

Answer: False

Using Customizing you can, for each notification type, assign one statusprofile for the notification and for the tasks.

2006/Q2 © 2006 SAP AG. All rights reserved. 513

Page 524: Plm412 en Col62 Fv Part a4

Test Your Knowledge PLM412

6. A system status is predefined in the system and cannot be changed.

Answer: True

Quality notifications use general status management. The system status ispredefined. Using Customizing, you can use a status profile to also workwith user statuses.

7. The action log is used to represent important changes in the �life cycle�of a notification.

Answer: True

The log contains information about notification statuses from statusmanagement and from change documents.

8. Documents from the Document Management System can always be assignedto a quality notification.

Answer: False

Documents that are stored using the Document Management System canonly be assigned if you have entered a corresponding screen area for theassignment in the notification type in Customizing.

9. You can assign follow-up actions to the codes in the code groups of thetask catalog.

Answer: True

The follow-up actions are defined in Customizing and assigned to therelevant code when processing the code group.

514 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 525: Plm412 en Col62 Fv Part a4

Unit 11Quality-related Costs and QM Orders

Unit OverviewThis unit deals with quality-related costs and how these are processed using QMorders. It describes the properties of QM orders and the settlement options. It alsodescribes how QM orders can be used in connection with inspection lot processingand with notification processing.

Unit ObjectivesAfter completing this unit, you will be able to:

� Describe how the QM order is used.� Describe how the QM order is represented in the SAP system.� Create and assign a QM order� Describe how a confirmation is executed for the QM order.� Settle a QM order.� Display a cost report for a QM order.

Unit ContentsLesson: QM order.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .516

Exercise 31: Create a QM Order .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .527Exercise 32: Confirmations Using QM Orders... . . . . . . . . . . . . . . . . . . . . . . .531Exercise 33: Optional exercise: Settle QM order .. . . . . . . . . . . . . . . . . . . . .537

2006/Q2 © 2006 SAP AG. All rights reserved. 515

Page 526: Plm412 en Col62 Fv Part a4

Unit 11: Quality-related Costs and QM Orders PLM412

Lesson: QM order

Lesson OverviewIn this lesson you learn about cost processing using QM orders. The propertiesof the QM order, as well as the cost report, and cost settlement using the QMorder are covered.

You can execute the confirmations for the QM order during inspection lotprocessing and in the context of quality notification processing.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Describe how the QM order is used.� Describe how the QM order is represented in the SAP system.� Create and assign a QM order� Describe how a confirmation is executed for the QM order.� Settle a QM order.� Display a cost report for a QM order.

Business ExampleActivity confirmation for quality inspections and for processing qualitynotifications is carried out using QM orders. These QM orders can be used to enterand evaluate the costs related to quality inspections or notification processing.

Figure 256: QM Order: Business Scenario

516 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 527: Plm412 en Col62 Fv Part a4

PLM412 Lesson: QM order

As a result of increasing market globalization and the resulting changes toeconomic and market conditions, many companies are forced to optimize theirprocesses and to reduce their costs at all levels.

The recording of quality-related costs is integral to an effective quality assuranceprogram. If a company can effectively record, settle and evaluate its costs, it canthen reduce these costs and increase the product quality.

Quality-related costs are incurred primarily in the processing of quality inspectionsand complaints.

Cost Processing Using QM Order

Figure 257: Controlling Overhead Costs in the SAP System

SAP Controlling (CO) is responsible for planning, collecting and evaluating allthe costs incurred within a company. These costs also cover quality-related costs.

You can use Quality Management (QM) to record quality-related costs usingQM orders.

Orders are used in overhead cost controlling in CO, for example, to record andkeep track of overhead costs. A QM order is settled in the same way as anoverhead cost order in CO.

Costs collected in a QM order can be settled to cost centers, orders, projects orprocesses.

The costs collected in and settled from a QM order reduce the profit of a company.

2006/Q2 © 2006 SAP AG. All rights reserved. 517

Page 528: Plm412 en Col62 Fv Part a4

Unit 11: Quality-related Costs and QM Orders PLM412

Figure 258: Cost Processing Using QM Order

In quality management, you use QM orders to record the costs that have beenincurred (actual costs).

You can record costs when processing quality inspections (appraisal costs) orwhen processing quality notifications (defect costs).

You assign the QM order to an inspection lot in inspection processing.

You assign the QM order to a quality notification in notification processing.

The costs collected in a QM order can be settled to various account assignmentobjects in the Controlling (CO) component.

518 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 529: Plm412 en Col62 Fv Part a4

PLM412 Lesson: QM order

Figure 259: Elements of a QM Order

The QM order has order category �06�. This order category is predefined in thesystem and cannot be changed.

You can use various order types for the order type �06�. The following order typesare delivered with the standard system:

� QL01 (general QM order for appraisal costs with periodic settlement)� QL02 (Individual QM order for appraisal costs)� QN01 (QM order for defect costs)

If required, you can also create additional order types in Customizing.

You can define your own settlement rule in the order master record. This allowsyou to:

� Settle costs to one or more receivers and allows different receivers (such as,WBS element, sales order, profitability segment).

� Enter how the costs are to be shared (distribution rule).� Enter the cost elements that are to be used to settle costs.

2006/Q2 © 2006 SAP AG. All rights reserved. 519

Page 530: Plm412 en Col62 Fv Part a4

Unit 11: Quality-related Costs and QM Orders PLM412

Create and assign a QM order

Figure 260: QM order in inspection lot processing

Order type QL01 is provided in the standard system for general QM orders. Thisorder type has the following properties:

� The order is a long-term cost collector� The order accumulates costs on a lump sum basis for all the materials and/or

inspection lots that are assigned to the order. You cannot, therefore, assignthe costs to individual materials or inspection lots.

� The costs are settled in the Controlling (CO) component on a periodic basis(for example, once a month).

Order type QL02 is provided in the standard system for individual QM orders.This order type has the following properties:

� The order is a short-term cost collector.� The order accumulates only the costs associated with the assigned inspection

lot.

You cannot use QM orders to confirm activities for inspections during production(inspection lot origin 03 and 13). For these inspection lots, the relevant order fromproduction is used as the cost collector for the activity confirmation.

520 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 531: Plm412 en Col62 Fv Part a4

PLM412 Lesson: QM order

Figure 261: Opening a QM order in the context of inspection lots

You can assign a QM order for appraisal costs to a material and/or an inspectionlot. The material master record acts as a central control object for creating a QMorder. You can maintain QM orders in the material master record and you candetermine whether a general or individual QM order should be created.

The Quality Management (QM) application component also has a centralmaintenance function that you can use to assign QM orders to one or morematerials. The system then automatically maintains the respective material masterrecords. You can use the central maintenance function for QM orders to createQM orders for one or more materials and then to assign them.

The number of the assigned QM order is written in the inspection type in theinspection setup of the material.

An individual QM order is created for the inspection lot if the document forinspection lot creation contains account assignment information. This applies forgoods receipts for orders with account assignment, for example. The accountassignment object, for example, the cost center, is copied to the settlementrule of the individual QM order. During the automatic creation of a QM orderin the inspection lot creation, you can determine the order type depending onthe inspection type. In Customizing, you can assign a QM order type to eachinspection type. This is transferred during the inspection lot creation. If there is noorder type defined for the inspection type, the order type for the individual QMorders from the QM plant settings is used.

2006/Q2 © 2006 SAP AG. All rights reserved. 521

Page 532: Plm412 en Col62 Fv Part a4

Unit 11: Quality-related Costs and QM Orders PLM412

Figure 262: Task List Structure

You must work with task lists when confirming activities for the inspectionbecause the required work center is assigned to the task list at operation leveland the link to Controlling is created.

Figure 263: Cost center and work center

The work center is assigned to the operation in the task list. The operation controlkey determines what business processes are relevant for an operation in the tasklist (for example, inspection characteristics, confirmations).

522 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 533: Plm412 en Col62 Fv Part a4

PLM412 Lesson: QM order

Figure 264: Activity confirmation for the inspection

Once you have recorded and valuated results for the inspection characteristic, youcan confirm the activities for the operation. Depending on the operation controlkey setting, the system either displays the dialog box for entering the activitytimes automatically or you must call it up manually.

� If the confirmation indicator for the operation control key in QMCustomizing is set to "Milestone confirmation" or Confirmation required, thesystem automatically displays the dialog box for recording activities.

� If the confirmation indicator is set to "Confirmation possible but notnecessary", you must call up the dialog box for recording the activity timesmanually. To do this, choose Edit -> Confirm activities in the characteristicoverview.

When you are recording or changing a usage decision, you can

� Confirm activity times for an inspection operation� Cancel existing confirmations for an operation When you cancel, the system

deletes the confirmation recorded for the QM order.

2006/Q2 © 2006 SAP AG. All rights reserved. 523

Page 534: Plm412 en Col62 Fv Part a4

Unit 11: Quality-related Costs and QM Orders PLM412

Figure 265: Opening a QM order during the notification processing

When processing a quality notification, you can create a QM order and assign itto the notification.

You can also assign an already existing QM order to a quality notification.

You can define the following information in Customizing for the qualitynotification:

� Calculation parameter for QM orders� Default account assignment for the costs related to a quality notification

524 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 535: Plm412 en Col62 Fv Part a4

PLM412 Lesson: QM order

Figure 266: Linking a Quality Notification to a QM Order

You can create the QM order from the quality notification.

The confirmation to a QM order can be performed using direct activity allocation,for example transaction KB21N.

Settlement and cost report

Figure 267: Settling a QM Order

You can settle the costs incurred for an order, using various account assignmentobjects.

2006/Q2 © 2006 SAP AG. All rights reserved. 525

Page 536: Plm412 en Col62 Fv Part a4

Unit 11: Quality-related Costs and QM Orders PLM412

In Customizing, you use different settlement profiles to specify the allowedreceiver for each order type (order, cost center, sales order).

However, you do not necessarily have to settle an order.

Figure 268: Cost Report for QM Order

You can create various cost reports for an order in the system (for example, acomparison of actual costs by period or a comparison of actual costs by year).

To distinguish between different types of quality costs (for example, internal andexternal defect costs) and to summarize them accordingly using the functions inthe Controlling component, you assign the orders to a predefined class (class type013) in the SAP Classification System and make distinctions using freely definedcharacteristics in this class.

You can use the fields of the order master record (object characteristics) oryou can freely define your own characteristics (user-defined characteristics) ascharacteristics for the Classification System.

You use these summarization characteristics to create summarization reports fororders.

The controlling area always forms the first step in the hierarchy of an evaluation.If you want to summarize relevant orders, you must set the Classification indicatorfor the order type in Customizing.

526 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 537: Plm412 en Col62 Fv Part a4

PLM412 Lesson: QM order

Exercise 31: Create a QM Order

Exercise ObjectivesAfter completing this exercise, you will be able to:� Record the costs that have been incurred in inspection processing or in the

context of quality notifications in a QM order and then settle the order.

Business ExampleCreate a costs recording in the context of inspection lot processing or notificationprocessing Use QM orders to do this.

Task 1: Create a QM order for appraisal cost recordingThe times for a quality inspection must be confirmed on a QM order with referenceto the operation This QM order is assigned to the material for the inspection type.

1. Create a new QM order for your material T-BQ1## for inspection type 05.Use the following parameters for the new QM order:

Field Name EntryPlant 1000Inspection Type 05Material T-BQ1##Order type QL01Controlling area 1000Cost center 4400Profit center 1200

Task 2: Optional: QM order for notification processingYou also want to enter costs that arise in the context of quality notificationprocessing. To do this you can create a QM order from the quality notification orassign an existing QM order to the quality notification.

1. Use the quality notification for the customer complaint (notification type Q1,material T-AQ3##) and create a QM order.

2. What are the settings for the order parameters?

Order type _______________________

Controlling area ______________

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 527

Page 538: Plm412 en Col62 Fv Part a4

Unit 11: Quality-related Costs and QM Orders PLM412

Business area ________________

Account assignment object _________________

528 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 539: Plm412 en Col62 Fv Part a4

PLM412 Lesson: QM order

Solution 31: Create a QM OrderTask 1: Create a QM order for appraisal cost recordingThe times for a quality inspection must be confirmed on a QM order with referenceto the operation This QM order is assigned to the material for the inspection type.

1. Create a new QM order for your material T-BQ1## for inspection type 05.Use the following parameters for the new QM order:

Field Name EntryPlant 1000Inspection Type 05Material T-BQ1##Order type QL01Controlling area 1000Cost center 4400Profit center 1200

a) Logistics→ Quality Management→ Quality Inspection→ Costs→Order Assignment→ Create (QK01).

Go to the Create new QM order tab page and enter the data from thetask.

Then continue by choosing the F8 pushbutton (Execute) .

Now you can see the materials and you can assign the new QM order.In the application toolbar, choose the Select All pushbutton and thenthe Assign QM Order pushbutton.

Save your data.

The QM order has now been created and assigned to the material forinspection type 05.

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 529

Page 540: Plm412 en Col62 Fv Part a4

Unit 11: Quality-related Costs and QM Orders PLM412

Task 2: Optional: QM order for notification processingYou also want to enter costs that arise in the context of quality notificationprocessing. To do this you can create a QM order from the quality notification orassign an existing QM order to the quality notification.

1. Use the quality notification for the customer complaint (notification type Q1,material T-AQ3##) and create a QM order.

a) Logistics→ Quality Management→ Quality Notification→ Change(QM02)

In the application toolbar, choose the Create QM Order pushbutton.

Save your notification.

2. What are the settings for the order parameters?

Order type _______________________

Controlling area ______________

Business area ________________

Account assignment object _________________

a) Choose the tab page Internal Processing. The following orderparameters are displayed in the expenses screen area:

Order type: QN01 (nonconformity costs)

Controlling area: 1000 (CO Europe)

Business area: 1000

Account assignment: Cost center 4400 (quality assurance)

Hint: After you have saved your notification, you can changeor display the assigned QM order by choosing Notifications→Functions→ Order.

530 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 541: Plm412 en Col62 Fv Part a4

PLM412 Lesson: QM order

Exercise 32: Confirmations Using QMOrders

Exercise ObjectivesAfter completing this exercise, you will be able to:� Record all activities performed during the quality inspection and when

processing a notification in a QM order

Business ExampleAll times that were spent processing an inspection lot or a notification areconfirmed for a QM order.

Task 1: Confirmations during results recording forinspection lotDuring the results recording, there is an operation-related time confirmation afterthe inspection characteristics are completed.

1. Create a manual inspection lot for inspection lot origin 05 for your materialT-BQ1## in plant 1000. The inspection lot quantity is 50 pieces.

2. Record the results for your inspection lot. For which operations can yourecord activity times?

Operation:______________

3. Use the inspection lot to display the cost report for the QM order.

Task 2: Optional: Confirmation for the QM order in thecontext of notification processingYou can execute the confirmation using the direct activity allocation.

1. You spent 2 hours on the defect analysis and repair. In addition, you wererunning a measuring system for 1 hour. Before you could use the measuringsystem for defects analysis, you had to make certain settings in the measuringsystem. This took 15 minutes.

Record these activities in your QM order for the notification. Use thefollowing data to do this:

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 531

Page 542: Plm412 en Col62 Fv Part a4

Unit 11: Quality-related Costs and QM Orders PLM412

Field Name EntryCost center 4280Activity type 1420 (machine hours)Activity type 1421: Labor hoursActivity type 1422: Remaining hours

2. Display the costs incurred using the cost report in the quality notification.

532 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 543: Plm412 en Col62 Fv Part a4

PLM412 Lesson: QM order

Solution 32: Confirmations Using QMOrdersTask 1: Confirmations during results recording forinspection lotDuring the results recording, there is an operation-related time confirmation afterthe inspection characteristics are completed.

1. Create a manual inspection lot for inspection lot origin 05 for your materialT-BQ1## in plant 1000. The inspection lot quantity is 50 pieces.

a) Logistics→ Quality Management→ Quality Inspection→ InspectionLot→ Processing→ Create (QA01)

Save your data.

2. Record the results for your inspection lot. For which operations can yourecord activity times?

Operation:______________

a) Logistics→ Quality Management→ Quality Inspection→ Worklist→ Results Recording (QE51N)

The activity confirmation occurs for the inspection characteristics inoperation 30.

Due to the setting in the work center of the operation and in theoperation control key, you should enter the activities here.

Enter the corresponding time and then save your data.

3. Use the inspection lot to display the cost report for the QM order.

a) Logistics→ Quality Management→ Quality Inspection→ InspectionLot→ Processing→ Display (QA03)

Go to the inspection lot by choosing Extras→ Costs

Here you can display the cost report for the QM order and the activityconfirmation for the inspection lot.

Task 2: Optional: Confirmation for the QM order in thecontext of notification processingYou can execute the confirmation using the direct activity allocation.

1. You spent 2 hours on the defect analysis and repair. In addition, you wererunning a measuring system for 1 hour. Before you could use the measuringsystem for defects analysis, you had to make certain settings in the measuringsystem. This took 15 minutes.

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 533

Page 544: Plm412 en Col62 Fv Part a4

Unit 11: Quality-related Costs and QM Orders PLM412

Record these activities in your QM order for the notification. Use thefollowing data to do this:

Field Name EntryCost center 4280Activity type 1420 (machine hours)Activity type 1421: Labor hoursActivity type 1422: Remaining hours

a) Logistics→ Quality Management→ Quality Notification→ Costs→Actual Postings→ Activity Allocation→ Record (KB21N)

Choose the controlling area and confirm your entry.

Use the F4 input help to select the screen variant Order, enter thefollowing data and then save.

Item 1

Send CCtr.: 4280 (cost center)

Activity type: 1420 (machine hours)

Rec. order: QM order number for the quality notification created inthe previous exercise

Total quantity : 1

UM: H

Item 2

Send CCtr.: 4280

Activity type: 1421 (labor costs)

Rec. order: QM order number for the quality notification created inthe previous exercise

Total quantity: 2

UM: H

Item 3

Send CCtr.: 4280

Activity type: 1422 (setup costs)

Rec. order: QM order number for the quality notification created inthe previous exercise

Total quantity: 15Continued on next page

534 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 545: Plm412 en Col62 Fv Part a4

PLM412 Lesson: QM order

UM: Min

Save your entries.

2. Display the costs incurred using the cost report in the quality notification.

a) Logistics→ Quality Management→ Quality Notification→ Display(QM03)

Enter the number of the notification that you have created for this unitand confirm your entry.

In the notification, choose Environment→ Cost Report QM Order.

Hint: By adapting the layout, you can include additional fieldsin the cost report.

It is possible to display the QM order in the notification. To dothis, choose Notification→ Functions→ Order→ Display.

2006/Q2 © 2006 SAP AG. All rights reserved. 535

Page 546: Plm412 en Col62 Fv Part a4

Unit 11: Quality-related Costs and QM Orders PLM412

536 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 547: Plm412 en Col62 Fv Part a4

PLM412 Lesson: QM order

Exercise 33: Optional exercise: Settle QMorder

Exercise ObjectivesAfter completing this exercise, you will be able to:� Settle the costs in the QM order.

Business ExampleYou settle all QM orders containing costs for inspection lots and qualitynotifications to the central cost center �Quality assurance�.

Task: Settle the QM ordersYou should settle the QM orders periodically at the end of the month.

1. Settle your QM orders to cost center 4400. Take note of the settlement rulein the QM order.

2. Display the cost report again.

2006/Q2 © 2006 SAP AG. All rights reserved. 537

Page 548: Plm412 en Col62 Fv Part a4

Unit 11: Quality-related Costs and QM Orders PLM412

Solution 33: Optional exercise: Settle QMorderTask: Settle the QM ordersYou should settle the QM orders periodically at the end of the month.

1. Settle your QM orders to cost center 4400. Take note of the settlement rulein the QM order.

a) Logistics→ Quality Management→ Quality Notification→ Costs→Actual Postings→ Settlement→ Individual Settlement (KO88)

Enter the following data:

Order: QM order numbers created in the previous exercises

Settlement period: Current month

Fiscal year: current year

Hint: You can display the settlement rule for the QM orderusing the Settlement Rule pushbutton.

In accordance with the settlement rule, the full settlement is billed100% to the cost center 4400 (quality assurance).

Choose the pushbutton Execute.

Hint: If you wish, you can do a test run first. For the updaterun, the indicator Test Run may not be set in the ProcessControl screen area.

2. Display the cost report again.

a) Logistics→ Quality Management→ Quality Notification→ Display(QM03)

Enter the number of the notification that you have created for this unitand confirm your entry.

In the notification, choose Environment→ Cost Report QM Order.

Hint: By adapting the layout, you can include additional fieldsin the cost report.

It is possible to display the QM order in the notification. To dothis, choose Notification→ Functions→ Order→ Display.

538 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 549: Plm412 en Col62 Fv Part a4

PLM412 Lesson: QM order

Lesson Summary

You should now be able to:� Describe how the QM order is used.� Describe how the QM order is represented in the SAP system.� Create and assign a QM order� Describe how a confirmation is executed for the QM order.� Settle a QM order.� Display a cost report for a QM order.

2006/Q2 © 2006 SAP AG. All rights reserved. 539

Page 550: Plm412 en Col62 Fv Part a4

Unit Summary PLM412

Unit SummaryYou should now be able to:� Describe how the QM order is used.� Describe how the QM order is represented in the SAP system.� Create and assign a QM order� Describe how a confirmation is executed for the QM order.� Settle a QM order.� Display a cost report for a QM order.

540 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 551: Plm412 en Col62 Fv Part a4

PLM412 Test Your Knowledge

Test Your Knowledge

1. QM orders can be settled to different account assignment objects.Determine whether this statement is true or false.□ True□ False

2. The confirmation to a QM order can be performed using direct activityallocation.Determine whether this statement is true or false.□ True□ False

3. When a quality notification is created, a QM order is also createdautomatically.Determine whether this statement is true or false.□ True□ False

2006/Q2 © 2006 SAP AG. All rights reserved. 541

Page 552: Plm412 en Col62 Fv Part a4

Test Your Knowledge PLM412

Answers

1. QM orders can be settled to different account assignment objects.

Answer: True

A QM order can be settled, for example, to a cost center or a sales order.

2. The confirmation to a QM order can be performed using direct activityallocation.

Answer: True

The times required, for example, for a defect analysis can be recorded to theQM order using direct activity allocation.

3. When a quality notification is created, a QM order is also createdautomatically.

Answer: False

A QM order can be created from notification processing. It is also possibleto assign a QM order that already exists to a notification.

542 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 553: Plm412 en Col62 Fv Part a4

Unit 12SAP Business Workflow in QM -

Overview

Unit OverviewThe SAP Business Workflow can be used to automate the flow of informationwithin a company. The SAP Business Workflow is particularly useful inconjunction with notifications, as it ensures that the tasks are automaticallyforwarded to the right people or groups. In this unit, you learn about the differentuses of the SAP Business Workflow during inspection lot processing andnotification processing.

Unit ObjectivesAfter completing this unit, you will be able to:

� Describe the main elements of the SAP Business Workflow.� Describe the use of the SAP Business Workflow in processes in quality

management� Describe the basic Customizing activities for the Workflow.

Unit ContentsLesson: SAP Business Workflow in QM - Overview ... . . . . . . . . . . . . . . . . . . . .544

Exercise 34: Optional exercise: SAP Business Workflow for notificationprocessing ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .551

2006/Q2 © 2006 SAP AG. All rights reserved. 543

Page 554: Plm412 en Col62 Fv Part a4

Unit 12: SAP Business Workflow in QM - Overview PLM412

Lesson: SAP Business Workflow in QM - Overview

Lesson OverviewThe SAP Business Workflow automatically informs the partners of a qualitynotification about their tasks. This lesson gives you the basic knowledge you needto use the SAP Business Workflow during notification processing and duringinspection lot processing.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Describe the main elements of the SAP Business Workflow.� Describe the use of the SAP Business Workflow in processes in quality

management� Describe the basic Customizing activities for the Workflow.

Business ExampleYou can ensure an automatic flow of information throughout your businessprocesses by using the SAP Business Workflow. This is especially useful fornotification processing.

Figure 269: Workflow: Business Scenario

544 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 555: Plm412 en Col62 Fv Part a4

PLM412 Lesson: SAP Business Workflow in QM - Overview

The SAP Business Workflow is an important tool that enables you to structure andoptimize the business processes in your company. You use the Workflow to:

� Automate the information and process flow� Link task-related but organizationally separate work steps� React quickly and effectively if defects have been identified, or if an

exceptional situation occurs

The advantages of the SAP Business Workflow for the management are:

� Improved control of information, deadlines and costs� Flexible alteration of processes, organizational structures and individual tasks

SAP provides numerous workflows that represent predefined business processes.You can use these workflows without complex implementation procedures.

End users receive information about the activities they have to perform in the�Business Workplace�. This gives them a central overview of all activities theyare authorized to perform. They can start processing their activities directlyfrom this Workplace.

SAP Business WorkflowCertain workflow events and workflow templates are delivered with the standardsystem for the QM module. In transaction PFTC_DIS, you can see a completeoverview of the workflow templates contained in the standard system. In thetransaction, choose the activity type 'Workflow template' and use the F4/F8keys for the 'Activity' field to display a structured overview of the workflowtemplates contained in the application components. You can then explode the QMcomponents and select and display one of the workflows.

Figure 270: SAP Business Workflow - Internal Problems

2006/Q2 © 2006 SAP AG. All rights reserved. 545

Page 556: Plm412 en Col62 Fv Part a4

Unit 12: SAP Business Workflow in QM - Overview PLM412

You can link Workflow events to the setting or deleting of system and user statuses.

In a Workflow scenario:

� You can define tasks that have to be performed when an event takes place� You assign the person responsible for processing to the task� The persons responsible for processing are informed by mail (or work item)

that a task is to be performed

Figure 271: Quality Notification and SAP Business Workflow

The workflow scenario �Inform interested party� allows you to send a mail to apredefined person, who wants to be informed when a notification is created.

If information about the planned end of the notification processing, or of the taskexists in the notification header or in the task, this information is transferred to theSAP Business Workflow when a work item is created. This information can thenbe used for deadline monitoring and, if necessary, for escalation purposes.

546 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 557: Plm412 en Col62 Fv Part a4

PLM412 Lesson: SAP Business Workflow in QM - Overview

Figure 272: Workflow: Use During Notification Processing

The workflow template for this process is started when you manually create a newquality notification, or when you activate a defect record as a quality notification.

The system triggers one of the following events for the business object (qualitynotification): CREATED (quality notification created), ACTIVATED (notificationactivated), or INPROCESSAGAIN (notification in process again).

The triggering event then starts the workflow template WS24500047 and theassociated process as described on the slide.

Workflow Objects for Quality Notifications

Workflow Objects for Quality NotificationsWorkflow template

24500047 Process quality notification200063 Complete tasks400064 Complete tasks - new processor200081 Process defect record200035 Information: Quality notification created

Standard tasks24500068 Process new notification24500066 Process notification24500067 Complete notification

2006/Q2 © 2006 SAP AG. All rights reserved. 547

Page 558: Plm412 en Col62 Fv Part a4

Unit 12: SAP Business Workflow in QM - Overview PLM412

8323 Complete tasks20000352 Create notification based on telephone call

Standard roles172 Notification processor174 Processor of task

20000021 Interested party for notification

The following object types exist in the quality notification area:

� BUS2078 (Quality notification)� QMSM (Task)

Figure 273: Configuration (Customizing-Workflow)

548 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 559: Plm412 en Col62 Fv Part a4

PLM412 Lesson: SAP Business Workflow in QM - Overview

To activate the standard workflow processes for quality management, you mustcarry out the task-related Customizing procedures (you must assign all theprocessors for the single-step tasks and activate the event linkage for multi-steptasks).

Hint: To access Customizing, follow the menu path Quality Management-> Environment -> Central Functions -> Activate Workflow Read therelevant documentation in Customizing.

Hint: To access general Customizing for the SAP Business Workflow,follow the menu path SAP NetWeaver -> Application Server -> BusinessManagement -> SAP Business Workfow. Here, take note of the standardsettings in particular.

2006/Q2 © 2006 SAP AG. All rights reserved. 549

Page 560: Plm412 en Col62 Fv Part a4

Unit 12: SAP Business Workflow in QM - Overview PLM412

550 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 561: Plm412 en Col62 Fv Part a4

PLM412 Lesson: SAP Business Workflow in QM - Overview

Exercise 34: Optional exercise: SAPBusiness Workflow for notificationprocessing

Exercise ObjectivesAfter completing this exercise, you will be able to:� Use the SAP Business Workflow to keep the notification coordinator or

person responsible for the task informed

Business ExampleWhen notifications and tasks are created, this event can trigger the Workflow toinform the relevant employees.

Task: Using the SAP Business Workflow for qualitynotificationsProcess the quality notification using the SAP Business Workflow

1. Open your office inbox and display the work items you have received.

2. For which quality notifications and tasks are you responsible?

2006/Q2 © 2006 SAP AG. All rights reserved. 551

Page 562: Plm412 en Col62 Fv Part a4

Unit 12: SAP Business Workflow in QM - Overview PLM412

Solution 34: Optional exercise: SAPBusiness Workflow for notificationprocessingTask: Using the SAP Business Workflow for qualitynotificationsProcess the quality notification using the SAP Business Workflow

1. Open your office inbox and display the work items you have received.

a) Office→ Workplace (SBWP)

Inbox -> Workflow

Your work items are displayed grouped by tasks, content, contentcategory, and sort key.

2. For which quality notifications and tasks are you responsible?

Answer: Choose, for example, Grouped according to content→ Tasks, todisplay the tasks for which you are responsible.

552 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 563: Plm412 en Col62 Fv Part a4

PLM412 Lesson: SAP Business Workflow in QM - Overview

Lesson Summary

You should now be able to:� Describe the main elements of the SAP Business Workflow.� Describe the use of the SAP Business Workflow in processes in quality

management� Describe the basic Customizing activities for the Workflow.

2006/Q2 © 2006 SAP AG. All rights reserved. 553

Page 564: Plm412 en Col62 Fv Part a4

Unit Summary PLM412

Unit SummaryYou should now be able to:� Describe the main elements of the SAP Business Workflow.� Describe the use of the SAP Business Workflow in processes in quality

management� Describe the basic Customizing activities for the Workflow.

554 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 565: Plm412 en Col62 Fv Part a4

PLM412 Test Your Knowledge

Test Your Knowledge

1. The SAP Business Workflow can be used to monitor deadlines fornotifications.Determine whether this statement is true or false.□ True□ False

2. The standard workflow processes in the notifications area are always active.Determine whether this statement is true or false.□ True□ False

3. A series of workflow templates and standard tasks are available fornotifications. These allow for efficient notification processing.Determine whether this statement is true or false.□ True□ False

2006/Q2 © 2006 SAP AG. All rights reserved. 555

Page 566: Plm412 en Col62 Fv Part a4

Test Your Knowledge PLM412

Answers

1. The SAP Business Workflow can be used to monitor deadlines fornotifications.

Answer: True

The SAP Business Workflow can be used to monitor end dates and timesof tasks and notifications. When the end date or time is reached, a workitem is automatically created.

2. The standard workflow processes in the notifications area are always active.

Answer: False

Task-specific Customizing must be performed and event linkage activated inCustomizing for the SAP Business Workflow so that the standard workflowprocesses in the notifications area can be used.

3. A series of workflow templates and standard tasks are available fornotifications. These allow for efficient notification processing.

Answer: True

Transaction SWDM - Business Workflow Explorer, gives you an overviewof the workflow templates and standard tasks available for notifications.

556 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 567: Plm412 en Col62 Fv Part a4

Unit 13Evaluations

Unit OverviewEvaluations of the recorded inspection results and the recorded problems are animportant source of information for quality control. In this unit you learn aboutand compare different evaluation methods.

Unit ObjectivesAfter completing this unit, you will be able to:

� Explain the different evaluation options.� Carry out evaluations of inspection lots and quality notifications.� Describe the worklist functions for inspection lots (reporting).� Evaluate inspection lot data using the QM Information System.� Transfer evaluation data to a subsystem using the QM-STI Interface.

Unit ContentsLesson: Evaluations Based on Original Documents ... . . . . . . . . . . . . . . . . . . . .558

Exercise 35: Evaluations for Inspection Lot. .. . . . . . . . . . . . . . . . . . . . . . . . . . .569Exercise 36: Evaluations for Quality Notifications.. . . . . . . . . . . . . . . . . . . . .573

Lesson: Standard analyses.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .577Exercise 37: QM Information System (QMIS) ... . . . . . . . . . . . . . . . . . . . . . . .589Exercise 38: Evaluations - Early Warning System ... . . . . . . . . . . . . . . . . . .593

2006/Q2 © 2006 SAP AG. All rights reserved. 557

Page 568: Plm412 en Col62 Fv Part a4

Unit 13: Evaluations PLM412

Lesson: Evaluations Based on Original Documents

Lesson OverviewThe evaluations based on original documents provide realtime statements aboutinspection characteristics and inspection lots as well as quality notifications. Thisallows you to intervene quickly in a process, if required. You will be showndifferent options for evaluations of this kind.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Explain the different evaluation options.� Carry out evaluations of inspection lots and quality notifications.

Business ExampleYou require realtime evaluations of the processes currently in use. For thispurpose, the run chart is directly available on the recording screen in resultsrecording during an inspection.

Evaluations Using Lists

Figure 274: QM Inspection Process - Evaluations

In results recording, you can access graphical representations of current and pastdata.

558 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 569: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Evaluations Based on Original Documents

You can use different SPC functions.

In the QM Information System, there are multiple ways to display and evaluatesummarized data.

Figure 275: Evaluations using Lists with Reference to Inspection Lots

When editing inspection lot data, you can use the worklist functions to access andedit lists (reports) dynamically.

The lists enable you to analyze inspection lot data available in the system inseveral different ways.

You can use transactions QA32 (change data) and QA33 (display data) for theinspection lots.

In conjunction with Defects Recording for Inspection Lots, you can also usethe list of items in the quality notification (transaction QM14 [change data] ortransaction QM15 [display data]).

For an overview of all inspection results for an inspection lot, use transactionQGA2 (display inspection results).

2006/Q2 © 2006 SAP AG. All rights reserved. 559

Page 570: Plm412 en Col62 Fv Part a4

Unit 13: Evaluations PLM412

Figure 276: Evaluations using Lists with Reference to Quality Notifications

When you process quality notifications and tasks, you can use thenotification-related list (report) functions to dynamically call up and processworklists.

The lists provide various options for analyzing notification data in the system.

You can use transactions QM10 (change data) and QM11 (display data) fornotification lists.

You can use transactions QM12 (change data) and QM13 (display data) for tasklists.

You can use transaction QM14 (change data) and QM15 (show data) for itemsin the notification.

You can use transaction QM16 (change data) and QM17 (show data) for actionsin the notification.

In addition, the display list can also be used as a multi-level notification list(transaction QM19).

560 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 571: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Evaluations Based on Original Documents

Figure 277: Selection Variants

You can define your own selection variants on the selection screen for worklists.

You enter your selection criteria once using selection variants and save this asa variant. When you next execute a list, you only enter the variant name. Theselection screen then already contains your default values.

In a selection variant, you can hide individual fields in a report or determine thefield contents differently.

You can save a selection variant as a user variant (U_Username) or as a transactionvariant (SAP_TCODE_Transaction).

When defining selection variants, you can also define dynamic selection. Thisenables you to use further selection fields to select the inspection lot or the qualitynotification.

The selection criteria affect the run time of the report. If you use certain criteria,such as the date or status, you can reduce the response time considerably.

2006/Q2 © 2006 SAP AG. All rights reserved. 561

Page 572: Plm412 en Col62 Fv Part a4

Unit 13: Evaluations PLM412

Figure 278: display variants

You can define your own display variants for a list.

In this way, you determine which lot-related information or notification-relatedinformation is displayed after running a report.

Figure 279: inspection history

562 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 573: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Evaluations Based on Original Documents

You can access the inspection history from:

� The usage decision� Results recording

Inspection results for characteristics are displayed for several inspection lots(run-chart).

Trends and runs can be displayed using a regression line.

A time run of measured values or inspection results for a characteristic is displayedas a graphic.

The following additional functions are available:

� Calling the QM-STI Interface� Downloading data for a spreadsheet� Configurable list� Display list of single values

Figure 280: histogram

Inspection results (single values) can be displayed as a histogram. In this way, youcan analyze certain characteristics, such as distribution and dispersion area.

2006/Q2 © 2006 SAP AG. All rights reserved. 563

Page 574: Plm412 en Col62 Fv Part a4

Unit 13: Evaluations PLM412

Figure 281: Run Chart

You can display the run of values for a characteristic in relation to:

� Mean values for the sample� Single values

You can display the values for all inspection lots.

You can display a control line and the corresponding specification limits(tolerances) to identify trends and runs.

564 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 575: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Evaluations Based on Original Documents

Display General QM Evaluations

Figure 282: Display general QM evaluations

The general QM evaluations are available as of mySAP ERP2005. You can find theevaluations by following the menu path Quality Management -> Quality Control-> Evaluations of Original Documents -> General QM Evaluations (QGA4)

You can evaluate current data and archived data and compare inspection resultsfor several characteristics.

You can create various table views and graphic views and you can display them inparallel. For the data displayed in the tables and graphics, the system determinesthe key figures used, for example, mean value, dispersion and cpk value

You can display the results history with reference to the inspection lot numberor with reference to the batch.

You can use the Grouping layout to define the display and grouping of the datafor the evaluation. The fields for the layout in the group 'Grouping characteristic'control the aggregation and grouping of data.

2006/Q2 © 2006 SAP AG. All rights reserved. 565

Page 576: Plm412 en Col62 Fv Part a4

Unit 13: Evaluations PLM412

Evaluations for Control Charts

Figure 283: Control Chart

� There are the following control charts for qualitative characteristics:

� np-control chart for the number of nonconforming units� p-control chart for the fraction of nonconforming units for each sample� c-control chart for the number of defects� u-control chart for the number of defects for each unit

For both the c-control chart and u-control chart, the corresponding controlindicator must be set in the inspection characteristic for recording thenumbers of defects.

� There are the following control charts for quantitative characteristics:

� IR-control chart for moving averages, advisable for sample size n=1� EWMA-chart for moving averages with exponential weighting� IR-control chart for moving averages and ranges of mean values� Acceptance charts� Shewhart charts

566 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 577: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Evaluations Based on Original Documents

Figure 284: List of Control Charts

You can access existing control charts using the control chart list.

The following functions are available in the list:

� Accessing selected (marked) control charts� Activating one or more control charts� Closing one or more control charts� Saving changes

In Customizing, you can define general and user-specific display and list variantsfor the selection screen and list configuration.

You can use control charts to check certain stability criteria (Western ElectricRules). Violations of the Western Electric Rules are displayed in a list along withthe chart number, track, and sample.

2006/Q2 © 2006 SAP AG. All rights reserved. 567

Page 578: Plm412 en Col62 Fv Part a4

Unit 13: Evaluations PLM412

568 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 579: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Evaluations Based on Original Documents

Exercise 35: Evaluations for InspectionLot

Exercise ObjectivesAfter completing this exercise, you will be able to:� Analyze the results for a particular inspection characteristic using the

inspection history

Business ExampleYou are responsible for evaluating quality-related data in your company. You wantto create a material analysis at the end of the month. Furthermore, you need theevaluation of quantitative data for certain inspection characteristics.

Task 1: Results History for Inspection CharacteristicsYou can use the results history for the master inspection characteristic to evaluatethe inspection results for all tasks.

1. You want to analyze the results for a specific master inspection characteristic,independent of whether the master inspection characteristic was used ininspection plans or material specifications.

Display the history for master inspection characteristic MK02-## and createa run chart of single values.

Task 2: History for an inspection characteristic in thetask listIf you do not use a master inspection characteristic, you can also display the resultshistory for the inspection characteristic in the task list.

1. You use an inspection plan (task list type Q, group##, task list counter 1)for inspecting the wattage of energy-saving lamps. You want to create ananalysis of the inspection results for the inspection characteristic Wattageeach month. Display the histogram of the inspection characteristic and makea note of the following statistical values:

Process capability:

cp:__________________ cpk:________________

Inspection results:

x-bar:_______________ s:__________________

2006/Q2 © 2006 SAP AG. All rights reserved. 569

Page 580: Plm412 en Col62 Fv Part a4

Unit 13: Evaluations PLM412

Solution 35: Evaluations for InspectionLotTask 1: Results History for Inspection CharacteristicsYou can use the results history for the master inspection characteristic to evaluatethe inspection results for all tasks.

1. You want to analyze the results for a specific master inspection characteristic,independent of whether the master inspection characteristic was used ininspection plans or material specifications.

Display the history for master inspection characteristic MK02-## and createa run chart of single values.

a) Logistics→ Quality Management→ Quality Control→ Evaluationsof Original Documents→ Inspection Result→ History for MasterInspection Characteristic (QS28)

On the selection screen, you can define selection criteria for the masterinspection characteristics. Enter the following data:

Field name or data type ValuesPlant 1000Master Inspection Characteristic MK02-##

Choose the F8 function key or the pushbutton Execute. A list appearsof all the master inspection characteristics, which correspond to theselection conditions. Select the line with your master inspectioncharacteristic MK02-##. Choose the pushbutton Results history.....The screen for limiting the selection of the results history appears.On this selection screen, you can limit the results history to specificinspection lots or to a certain period of time. Enter the course dates asthe time-related delimitation. Choose the pushbutton Execute selectionor the F8 function key. The results history for your master inspectioncharacteristic MK02-## appears.

An overview is displayed of all the inspection lots in which thismaster inspection characteristic was used. Select all inspection lots bychoosing the F5 function key or the pushbutton Select all. You choosethe pushbutton Run chart: Single values to display the run chart.

Continued on next page

570 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 581: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Evaluations Based on Original Documents

Task 2: History for an inspection characteristic in thetask listIf you do not use a master inspection characteristic, you can also display the resultshistory for the inspection characteristic in the task list.

1. You use an inspection plan (task list type Q, group##, task list counter 1)for inspecting the wattage of energy-saving lamps. You want to create ananalysis of the inspection results for the inspection characteristic Wattageeach month. Display the histogram of the inspection characteristic and makea note of the following statistical values:

Process capability:

cp:__________________ cpk:________________

Inspection results:

x-bar:_______________ s:__________________

a) Logistics→ Quality Management→ Quality Control→ Evaluationsof Original Documents→ Inspection Result→ History for InspectionCharacteristic (QGP1)

On the selection screen Inspection Results for Tlist Charac., you definethe criteria for the task list or material selection. Enter the followingdata:

Field name or data type ValuesTask list (type/group/counter) Q / Group## / 1Material T-BQ1##Plant 1000

Choose the F8 function key. A hit list appears with all the characteristicsthat are available in the chosen task list. Select the task list characteristicwith the short text Wattage from this list with a double-click. Theresults history for the task list characteristic appears and all inspectionlots that correspond to the selection conditions are displayed.

Select all inspection lots by choosing the F5 function key or thepushbutton Select all. Choose the pushbutton Single values histogram.The histogram for the task list characteristic appears. In this histogram,you can use Statistical values to navigate further.

Process capability:

cp:__________________ cpk:________________

Inspection results:

x-bar:_______________ s:__________________

2006/Q2 © 2006 SAP AG. All rights reserved. 571

Page 582: Plm412 en Col62 Fv Part a4

Unit 13: Evaluations PLM412

572 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 583: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Evaluations Based on Original Documents

Exercise 36: Evaluations for QualityNotifications

Exercise ObjectivesAfter completing this exercise, you will be able to:� Use the worklists as an alternative to the workflow.� Describe the options for configuring lists (selection and display variants).

Business ExampleYou are using the lists for the quality notifications as worklists and for reporting.

Task 1: Edit the tasks using the worklistWorklist for tasks

1. Create your own personal worklist for tasks. Use the Required start/end datefor the notification as a control for the monitor.

Structure the list according to your own requirements.

Sort the list in descending order by material.

2. Complete all outstanding tasks that are assigned to you.

Task 2: Edit the quality notifications using the worklistWorklist for notifications

1. Create your own personal worklist of notifications. Select all thenotifications, in which you are assigned as coordinator.

Modify the contents of the list to suit your requirements.

2. Call the Graphic function for the material column.

3. Complete the notification.

2006/Q2 © 2006 SAP AG. All rights reserved. 573

Page 584: Plm412 en Col62 Fv Part a4

Unit 13: Evaluations PLM412

Solution 36: Evaluations for QualityNotificationsTask 1: Edit the tasks using the worklistWorklist for tasks

1. Create your own personal worklist for tasks. Use the Required start/end datefor the notification as a control for the monitor.

Structure the list according to your own requirements.

Sort the list in descending order by material.

a) Logistics→ Quality Management→ Quality Notification→ Worklist→ Task→ Change Data (QM12)

Enter your group name in the the coordinator field, use the field helpfor the reference field for monitor to select the entry required start/enddate, and choose the pushbutton Execute.

Choose the pushbutton Change layout to structure the list according toyour personal requirements. Include the Material field in your layout.

Select the Material column and choose the Sort in descending orderpushbutton.

2. Complete all outstanding tasks that are assigned to you.

a) Select your tasks and choose the pushbutton Tasks. Choose theComplete tasks pushbutton and save your data.

Task 2: Edit the quality notifications using the worklistWorklist for notifications

1. Create your own personal worklist of notifications. Select all thenotifications, in which you are assigned as coordinator.

Modify the contents of the list to suit your requirements.

a) Logistics→ Quality Management→ Quality Notification→ Worklist→ Notification→ Change Data (QM10)

Enter your group name in the Coordinator field and choose the Executepushbutton.

Choose the Change layout pushbutton to structure the list according toyour personal requirements. Include the Material field in your layout.

2. Call the Graphic function for the material column.

a) Select the Material column and choose the Graphic pushbutton�.

Continued on next page

574 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 585: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Evaluations Based on Original Documents

3. Complete the notification.

a) Select your notifications and choose the pushbutton Notification.Choose the Complete� pushbutton and save your data.

Specify whether the problem was caused internally or externally.

2006/Q2 © 2006 SAP AG. All rights reserved. 575

Page 586: Plm412 en Col62 Fv Part a4

Unit 13: Evaluations PLM412

Lesson Summary

You should now be able to:� Explain the different evaluation options.� Carry out evaluations of inspection lots and quality notifications.

576 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 587: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Standard analyses

Lesson: Standard analyses

Lesson OverviewThe evaluations using the standard analyses provide important key figures frominspection lot processing and notification processing. Depending on the inspectionor the quality notification, the analyses are created with reference to a material, orwith reference to a customer and a material, or a vendor and a material.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Describe the worklist functions for inspection lots (reporting).� Evaluate inspection lot data using the QM Information System.� Transfer evaluation data to a subsystem using the QM-STI Interface.

Business Example� QM information system� Early Warning System� Monthly reports� Lists� Ad hoc evaluations

Evaluations play an important part in successful, strategic planning in yourcompany. They allow you to determine the correct key figures and to prepare themfor use at appropriate times.

You can evaluate data in the following ways in the SAP system:

� Reporting (creating lists using worklists)� Quality Management Information System (QMIS)

2006/Q2 © 2006 SAP AG. All rights reserved. 577

Page 588: Plm412 en Col62 Fv Part a4

Unit 13: Evaluations PLM412

Standard Analyses with QMIS

Figure 285: Evaluations in QMIS

The QM Information System offers various methods for analysis, based on thedata held in the standard information structures.

The standard analyses provide you with a tool for presenting and analyzingstatistical data.

Standard analyses are delivered by SAP with the standard system and arepreconfigured (for example, the drilldown). You can however modify them tosuit your requirements.

In addition, you can also define individual views of the data in the QM InformationSystem and include other data from the SAP System.

578 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 589: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Standard analyses

Figure 286: Standard analyses

The following standard analyses are available in the QM Information System.These analyses allow you to evaluate data from quality notifications and inspectionlot processing:

� Notification overview� Problems in notifications� Defects� Inspection lots� Inspection results

The structure of the standard analyses is based on the info structures. You canswitch directly to the notification list and then to the notification display from thestandard analysis. The notification lists and individual notifications are loadedfrom the documents.

2006/Q2 © 2006 SAP AG. All rights reserved. 579

Page 590: Plm412 en Col62 Fv Part a4

Unit 13: Evaluations PLM412

Figure 287: Early Warning System

You can display defined exceptions in an exception analysis, using the EarlyWarning System. The exception analysis functions like a filter; only theexceptional situations are displayed. The exceptional situation can be highlightedin color.

The characteristics and key figures in the QM information System are the basis ofthe Early Warning System. It allows you to pinpoint and monitor weak points inyour logistical processes.

The Early Warning System helps you to promptly identify exceptional situationsthat can lead to problems in your processes.

580 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 591: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Standard analyses

Figure 288: Periodic Analysis

In the Early Warning System, you use an exception to define an exceptionalsituation. An exception contains an entry of characteristics or characteristicvalues (for example, vendor, material) and conditions. You can define conditionsas threshold values for key figures (for example, vendors with more than onenotification).

You can plan periodic exception analyses using jobs and run them automatically inthe background. You can link follow-up processes to these periodic analyses (suchas, sending a mail) that can be executed when an exceptional situation occurs.

2006/Q2 © 2006 SAP AG. All rights reserved. 581

Page 592: Plm412 en Col62 Fv Part a4

Unit 13: Evaluations PLM412

Characteristics and Key Figures for Info Structures

Figure 289: Info Structure for Inspection Results

The standard info structures form the data basis for the QM InformationSystem. The info structures are special statistics tables in which the permanentlysummarized data is updated. This data comes from operative applications.

The following standard info structures can be used to analyze inspection results:

� (S 161) - General for material analysis� (S 162) - Quantitative inspection results for material analysis� (S 163) - General for vendor/material analysis� (S 164) - Quantitative inspection results for vendor/material analysis� (S 165) - General for customer/material analysis� (S 166) - Quantitative inspection results for customer/material analysis

Other info structures for inspection lots in Quality Management:

� S 068, vendor statistics (characteristics: vendor, material, inspection type,plant)

� S 069, material statistics (characteristics: material, inspection type, plant)� S 104, customer statistics (characteristics: customer, material, inspection

type, plant)

582 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 593: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Standard analyses

Figure 290: Key Figures for the Info Structure

You can choose statistical data for quantitative characteristics, for example,standard deviation, mean value, and process capability indices.

Statistical data for samples, for cases when the specification limits are exceeded,and defects exists for all characteristics.

You can use three different process models to determine statistical data, forexample, mean value, standard deviation, cpk, and cp values.

All key figures for the characteristics can be monitored using the Early WarningSystem (EWS).

Figure 291: Updating Control

2006/Q2 © 2006 SAP AG. All rights reserved. 583

Page 594: Plm412 en Col62 Fv Part a4

Unit 13: Evaluations PLM412

Inspection results are updated depending on the settings of the followingparameters:

� Material� Material, vendor� Material, customer

Figure 292: Summarization of Notifications in QMIS

Quality notifications and inspection results from quality management are updatedin the QM Information System (QMIS). The QMIS forms part of the LIS(Logistics Information System) in the SAP system.

When you save a notification, the notification data is updated independently of thenotification status in the QMIS.

Summarization of the notification data takes place at notification and item level.

You can evaluate the updated data in summarized form using the QMIS.

584 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 595: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Standard analyses

Figure 293: Information Structure for the Notification

Info structures are special statistics tables, in which the summarized data isupdated. This data comes from the productive operations.

The following info. structures are available in the standard for evaluations ofnotifications:

S097 S097 This information structure contains the summarized data ofthe quality notifications from notification headers and tasks for thematerial analysis.

S098 S097 This information structure contains the summarized data of thequality notifications from notification headers and tasks for the vendoranalysis.

S099 S097 This information structure contains the summarized data ofthe quality notifications from notification headers and tasks for thecustomer analysis.

S100 This information structure contains the summarized data of the problemlevel (or defect level) of quality notifications for thematerial analysis.

S102 This information structure contains the summarized data of the problemlevel (or defect level) of quality notifications for the vendor analysis.

S103 This information structure contains the summarized data of the problemlevel (or defect level) of quality notifications for the customer analysis.

2006/Q2 © 2006 SAP AG. All rights reserved. 585

Page 596: Plm412 en Col62 Fv Part a4

Unit 13: Evaluations PLM412

Figure 294: Characteristics and Key Figures for the Info Structures

Characteristics are summarizing criteria without a time reference, (such asnotification type, vendor, material and so on).

Periods establish the time reference. Data is cumulated and compressed per periodduring the update.

Key figures provide information that is important for your business (for example,number of defects, nonconforming quantities, total number of notifications,number of notifications outstanding, tasks outstanding etc.)

All key figures can be monitored by the Early Warning System (EWS).

Make the corresponding settings in Customizing: Logistics - General→ LogisticsInformation System (LIS)→ Logistics Data Warehouse→ Updating.

586 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 597: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Standard analyses

Statistical interface for QM

Figure 295: QM-STI - Statistical Interface

The QM Statistical Data Interface (STI) is an open interface linking the QMapplication component to external evaluation systems. If you use a format definedby SAP, the interface transfers the inspection results from the QM component tothe external evaluation system.

The STI interface is used to perform evaluations that are not supported by thestatistical functions already provided for results recording in QM (control charts,histograms, process capability indices).

Hint: To use this function, you need an external statistical system thatsupports the QM-STI Interface. For example, an evaluation is provided inMicrosoft Excel® for linking to desktop applications. In this example,the driver is programmed in ABAP and controls Microsoft Excel® usingOLE (Object Linking and Embedding) technology. Usually the drivers arewritten on external systems as RFC server programs.

The evaluation method must be defined in Customizing. For moreinformation about defining evaluation methods, see the implementationguide (IMG) for QM in Quality Management→ Quality Inspection→Subsystems→ Define Evaluation Methods for the QM-STI Interface.

2006/Q2 © 2006 SAP AG. All rights reserved. 587

Page 598: Plm412 en Col62 Fv Part a4

Unit 13: Evaluations PLM412

Figure 296: QM-STI - Accessing the Interface

You can export results data from the following areas in QM:

Results recordingIn results recording, you can start an STI evaluation for the currentcharacteristic using the pushbutton QM-STI evaluations. A dialog boxappears. You have to specify an evaluation method and RFC destination inthis dialog box. You can also enter additional data (for example, title andaxes name).

Control chartsYou can start an evaluation from a control chart by choosing QM-STIevaluations from the menu options. The dialog box mentioned aboveappears. All samples (except those from canceled inspection lots) that wereread for the control chart are transferred to the QM-STI Interface. Thismeans that samples that were not evaluated and samples or characteristicsthat were not closed are not transferred to the interface.

Results historyFrom a results history screen, the characteristic data from several inspectionlots is exported for QM-STI evaluations. The samples are sorted accordingto the corresponding sort method.

588 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 599: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Standard analyses

Exercise 37: QM Information System(QMIS)

Exercise ObjectivesAfter completing this exercise, you will be able to:� Create standard analyses for materials.

Business ExampleYou are responsible for evaluating quality-related data in your company. At theend of the month, you require analyses for the quality inspections and qualitynotifications.

Furthermore, you need the evaluation of quantitative data for certain inspectioncharacteristics. You can also monitor the defects that have occurred using QMISstandard analyses.

Task: Evaluations using the QM Information SystemMaterial analyses using the QM Information System

1. Create an inspection lot-related material analysis for materials T-BQ100 �T-BQ120 in plant 1000 for all inspection lots of inspection type 05.

The analysis period is from 01.2000 to the current month.

Make a note of the mean value of the quality score for all materials.

____________________________________________________________

How many inspection lots were processed within the period of analysis forthese materials in inspection type 05?

____________________________________________________________

2. Create a notification-related material analysis for all quality notificationsfor the materials in plant 1000 - 1200.

The analysis period is from 01.2000 to the current month.

How many notifications were created within the analysis period for thematerials in the system?

____________________________________________________________

Which notification type has the most quality notifications?

____________________________________________________________

For which material were the most quality notifications created?

____________________________________________________________

2006/Q2 © 2006 SAP AG. All rights reserved. 589

Page 600: Plm412 en Col62 Fv Part a4

Unit 13: Evaluations PLM412

Solution 37: QM Information System(QMIS)Task: Evaluations using the QM Information SystemMaterial analyses using the QM Information System

1. Create an inspection lot-related material analysis for materials T-BQ100 �T-BQ120 in plant 1000 for all inspection lots of inspection type 05.

The analysis period is from 01.2000 to the current month.

Make a note of the mean value of the quality score for all materials.

____________________________________________________________

How many inspection lots were processed within the period of analysis forthese materials in inspection type 05?

Continued on next page

590 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 601: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Standard analyses

____________________________________________________________

a) Logistics→ Quality Management→ Quality Control→ Key Figures→ Material→ Inspection Lots→ Overview (MCXA)

The selection screen Material Analysis Overview: Lots: Selectionappears. Enter the following data on the selection screen:

Field name or data type ValuesMaterial T-BQ100 to T-BQ120Inspection type 05Plant 1000Month 01.2000 to the current month

Choose the F8 function key or the pushbutton Execute to display thebasic list for the lot-based material analysis. For this material analysis,an info structure is used in which characteristics and key figures areupdated.

The layout of this basic list can be user-specific. For example, you candefine the layout of the basic list by choosing Settings→ Column width→ Key figures (.� Characteristic). You can also display the drilldownlog for the info structure by choosing Settings→ Page header→With drilldown log. You can copy additional key figures at any timefrom the info structure to the current display by using the pushbuttonChoose key figures.

Mean value of the quality score for all materials:

___________________________

Total lots of inspection type 05 within the period of analysis:

___________________________

2. Create a notification-related material analysis for all quality notificationsfor the materials in plant 1000 - 1200.

The analysis period is from 01.2000 to the current month.

How many notifications were created within the analysis period for thematerials in the system?

____________________________________________________________

Which notification type has the most quality notifications?

____________________________________________________________

For which material were the most quality notifications created?

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 591

Page 602: Plm412 en Col62 Fv Part a4

Unit 13: Evaluations PLM412

____________________________________________________________

a) Logistics→ Quality Management→ Quality Control→ Key Figures→ Material→ Notifications→ Overview (MCXV)

The selection screen Q Notification Analysis Material Overview:Selection appears. Enter the following data on the selection screen:

Field name or data type ValuesMaterialNotification TypePlant for material 1000 To 1200Month 01.2000 To current month

The basic list for notification-related material analysis appears bychoosing the F8 function key or the pushbutton Execute. For thismaterial analysis, an info structure is used in which characteristics andkey figures are updated.

The layout of this basic list can be user-specific. For example, you candefine the layout of the basic list by choosing Settings→ Column width→ Key figures (.� Characteristic). You can also display the drilldownlog for the info structure by choosing Settings→ Page header→With drilldown log. You can copy additional key figures at any timefrom the info structure to the current display by using the pushbuttonChoose key figures.

Quality notifications in analysis period:

___________________________

Notification type with the most quality notifications:

___________________________

Material with the most quality notifications: Choose the Drilldownpushbutton and then set the radio button Material. Confirm using. Select the Total no. notif column and choose the Sort in

descending order pushbutton. Note for which materials the mostquality notifications were created.

592 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 603: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Standard analyses

Exercise 38: Evaluations - Early WarningSystem

Exercise ObjectivesAfter completing this exercise, you will be able to:� Configure the Early Warning System to alert you to exceptional situations.

Business ExampleIf more than 5 defects are identified for a material, you can use a periodic analysisto inform a colleague, enabling your company to react promptly to the problem.

Task: Settings for the Early Warning SystemCreate an exception.

1. In the Early Warning System, define the exception PLM412_## for theinfo-structure S100. If more than five defects are identified for a material,this exception should be effective in an analysis period of 12 months.

2. Execute the standard analysis Material-related defect using this exception.

3. Perform the exception analysis.

4. Schedule the exception analysis as a periodic analysis. Enter the follow-upprocessing transaction that if the exception occurs, a mail should be sentto you.

2006/Q2 © 2006 SAP AG. All rights reserved. 593

Page 604: Plm412 en Col62 Fv Part a4

Unit 13: Evaluations PLM412

Solution 38: Evaluations - Early WarningSystemTask: Settings for the Early Warning SystemCreate an exception.

1. In the Early Warning System, define the exception PLM412_## for theinfo-structure S100. If more than five defects are identified for a material,this exception should be effective in an analysis period of 12 months.

a) SAP Menu→ Logistics→ Quality Management→ Quality Control→ Key Figures→ Tools→ Early Warning System→ Exception→Create (MC=Q)

Enter the following data and choose the Characteristics pushbutton.

Field Name EntryException: PLM412_##Text for exception: Number of defects > 5Info structure: S100

Confirm your entries using Enter or choose the Characteristicspushbutton in the application toolbar.

Then choose the Select characteristic pushbutton. Select the material.Copy it into your selection and confirm your entry.

Choose the Conditions pushbutton and then the Select key figures�pushbutton. Select the problem frequency, copy it into your selectionand confirm your entry.

Choose the Define condition pushbutton, set the Threshold valueanalysis radio button and then choose the Continue pushbutton. Onthe following screen, define a problem frequency > 5 and choose theContinue pushbutton.

Enter the value 12 in the Previous periods field in the Analysis periodscreen area.

Choose the Subsequent processing pushbutton. Set the Active forperiodical analysis and the Send mail to indicators. Enter your user(PLM412-##) as the mail address and save your entries.

Continued on next page

594 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 605: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Standard analyses

2. Execute the standard analysis Material-related defect using this exception.

a) Logistics→ Quality Management→ Quality Control→ Key Figures→ Material→ Defect (MCXX)

Enter the following data and choose the Schedule pushbutton.

Field Name EntryMonth 01.2000 To current monthException: PLM412_##

Confirm your info messages by choosing Enter.

3. Perform the exception analysis.

a) SAP Menu→ Logistics→ Quality Management→ Quality Control→Key Figures→ Tools→ Early Warning System→ Exception Analysis(MCYL)

Enter the following data and choose the Execute pushbutton.

Field Name EntryException: PLM412_##

Hint: Unlike the display of the exceptions in the standardanalyses, the Exception analysis displays only data that isaffected by the exception. The exception analysis functionslike a filter; only the exceptional situations are displayed.

Continued on next page

2006/Q2 © 2006 SAP AG. All rights reserved. 595

Page 606: Plm412 en Col62 Fv Part a4

Unit 13: Evaluations PLM412

4. Schedule the exception analysis as a periodic analysis. Enter the follow-upprocessing transaction that if the exception occurs, a mail should be sentto you.

a) SAP Menu→ Logistics→ Quality Management→ Quality Control→Key Figures→ Tools→ Early Warning System→ Periodic Analysis→ Create (MC=W)

Enter the following data and choose the Create pushbutton:

Field Name EntryException: PLM412_##Type of analysis: System-driven

Create a Variant Group## and choose the Create pushbutton.

On the Variants: Change Screen Assignment screen, select For AllSelection Screens and confirm your entry using Enter. This takes youto variant maintenance and you can use the Attributes pushbutton orfunction key F6 to enter a description of your variant.

Save your variant.

Choose Periodic Analyses→ Schedule (MC=Z).

Enter the following data and choose the Schedule pushbutton.

Field Name EntryException: PLM412_##

Choose the option Immediately and then check and save your data.

596 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 607: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Standard analyses

Lesson Summary

You should now be able to:� Describe the worklist functions for inspection lots (reporting).� Evaluate inspection lot data using the QM Information System.� Transfer evaluation data to a subsystem using the QM-STI Interface.

2006/Q2 © 2006 SAP AG. All rights reserved. 597

Page 608: Plm412 en Col62 Fv Part a4

Unit Summary PLM412

Unit SummaryYou should now be able to:� Explain the different evaluation options.� Carry out evaluations of inspection lots and quality notifications.� Describe the worklist functions for inspection lots (reporting).� Evaluate inspection lot data using the QM Information System.� Transfer evaluation data to a subsystem using the QM-STI Interface.

598 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 609: Plm412 en Col62 Fv Part a4

PLM412 Test Your Knowledge

Test Your Knowledge

1. The inspection results for several inspection lots are displayed via the historyfor the inspection characteristic.Determine whether this statement is true or false.□ True□ False

2. You can use the selection variant to define that data is always selectedaccording to the same specifications.Determine whether this statement is true or false.□ True□ False

3. Data cannot be moved to an external program.Determine whether this statement is true or false.□ True□ False

4. Evaluations are performed with reference to inspection lots or with referenceto quality notifications.Determine whether this statement is true or false.□ True□ False

5. The Early Warning System can be used to monitor critical key figures.Determine whether this statement is true or false.□ True□ False

6. InfoStructures are available for the inspection results.Determine whether this statement is true or false.□ True□ False

2006/Q2 © 2006 SAP AG. All rights reserved. 599

Page 610: Plm412 en Col62 Fv Part a4

Test Your Knowledge PLM412

Answers

1. The inspection results for several inspection lots are displayed via the historyfor the inspection characteristic.

Answer: True

Depending on the characteristic, the moving averages or the moving averagesand single values are displayed across several inspection lots. A graphicaldisplay of the values is also possible.

2. You can use the selection variant to define that data is always selectedaccording to the same specifications.

Answer: True

If required, you can create user-specific selection variants. In addition, youcan create selection variants that are valid for several users.

3. Data cannot be moved to an external program.

Answer: False

The statistical interface QM-STI can be used to move data to an externalprogram. This interface can be called from the results history, for example.

4. Evaluations are performed with reference to inspection lots or with referenceto quality notifications.

Answer: True

Different InfoStructures are available for the standard analyses.

5. The Early Warning System can be used to monitor critical key figures.

Answer: True

Using the Early Warning System, the key figures on the InfoStructures canbe monitored periodically.

600 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 611: Plm412 en Col62 Fv Part a4

PLM412 Test Your Knowledge

6. InfoStructures are available for the inspection results.

Answer: True

The InfoStructures for the inspection results are updated after characteristiccompletion. This means that certain key figures are already available beforethe usage decision and, if required, they can be monitored using the EarlyWarning System.

2006/Q2 © 2006 SAP AG. All rights reserved. 601

Page 612: Plm412 en Col62 Fv Part a4

Unit 13: Evaluations PLM412

602 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 613: Plm412 en Col62 Fv Part a4

Unit 14Enterprise Portals � Optional Unit

Unit OverviewThe mySAP Enterprise Portal solution gives you access to all relevant data over aservice friendly interface. It also allows you to convert structured and unstructuredknowledge into concrete knowledge. mySAP Enterprise Portal brings togetherinformation from SAP and non-SAP systems, data warehouses, and desktopdocuments, as well as Web content and services on a central, unified platform.

This lesson provides an introduction to enterprise portals, and demonstrates theadvantages of the SAP solution.

Unit ObjectivesAfter completing this unit, you will be able to:

� Explain the purpose of an enterprise portal� Name a company's goals for a portal� Describe the advantages associated with using an enterprise portal� List some of the advantages that your business can enjoy by using mySAP

Business Suite.� Explain the basic concepts of SAP NetWeaver� Describe the central role of the SAP NetWeaver Application Server� Explain the role of SAP NetWeaver AS Java� Describe the main functions of the SAP NetWeaver Portal� Name the advantages associated with business packages� Outline the development of the SAP NetWeaver Portal

Unit ContentsLesson: Motivation for Portals.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .604Lesson: SAP's Product Strategy.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .610Lesson: SAP NetWeaver .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .615Lesson: Introducing SAP NetWeaver Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .625

2006/Q2 © 2006 SAP AG. All rights reserved. 603

Page 614: Plm412 en Col62 Fv Part a4

Unit 14: Enterprise Portals � Optional Unit PLM412

Lesson: Motivation for Portals

Lesson OverviewThis lesson presents the enterprise portal and gives reasons for implementing itin your company.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Explain the purpose of an enterprise portal� Name a company's goals for a portal� Describe the advantages associated with using an enterprise portal

Business ExampleYour employer has decided to implement an enterprise portal for certain roles inyour company. You are part of the implementation team. You want to know moreabout the purpose of an enterprise portal so that you know which goals must bedefined for your portal implementation project.

What is an Enterprise Portal?Participants' replies to this question have changed dramatically in the past 10 -15years. When the Internet was used first by companies, their Web sites were verybasic. Nowadays, however, the Internet is a platform for efficient collaborationsas well as the seamless integration of applications into a browser-based interface.This means that the focus on enterprise portals has grown considerably andcompanies now want to use an enterprise portal to perform new tasks. Forexample, enterprise portals are used to optimize business processes that comprisemany different application environments, data sources, and even companies.Companies want to make the portal, which is a powerful central access point forinformation and services, available to their employees who need it to completetheir daily tasks.

604 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 615: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Motivation for Portals

Figure 297: Evolution of Enterprise Portals

Currently, users must navigate through various applications to complete their work.As a result, employees spend much of their time calling various applications, usingapplication-specific tools to search for the data they require, and consolidating datafrom various application silos. They require a tool that integrates and consolidatesall available information and services so that company tasks are performed in onetask-dedicated, user-specific display. This is the purpose of a portal.

End users of a portal require access to all possible structured and unstructured dataand services. In general, they require access to the following information:

� Transactional systems and legacy databases� Data warehouse solutions and solutions for decision support� Internet and intranet Web sites� File servers and other storage systems for contents and documents

Structured data is the information that is collected and stored in an applicationdatabase during normal transaction processing. We access some information in itsoriginal form and other information in its extracted or edited form. For example,we access the information on the Internet in its original form (unchanged).

The various types of information that a portal user generally has to access are invarious system types. An enterprise portal must provide access to informationirrespective of its storage location. The information is accessed as follows:

� Application access and integration� Business Intelligence services� Internet access to contents and services� Knowledge Management services

2006/Q2 © 2006 SAP AG. All rights reserved. 605

Page 616: Plm412 en Col62 Fv Part a4

Unit 14: Enterprise Portals � Optional Unit PLM412

Even though access to information is good, user responsibilities vary and therequirements are high. In particular, users require tools that they can use tooptimize and speed up their many tasks, irrespective of which application,information and service they require to complete a given task. For example, endusers require single sign-on services that allow faster access to data both fordisplay and editing purposes.

An enterprise portal provides the following:

� a central point of access to applications, content and services using a Webbrowser

� a personalized, role-based user interface that can be modified to the user'sindividual requirements

� simple maintenance that is based on an open and flexible system withoutadditional client software

� secure access from everywhere

From Desktop to �Webtop�The information technology landscapes of medium-sized and large companiesare becoming more and more complex. Such landscapes are characterized bythe following:

Heterogeneous systemsDozens or even hundreds of separate systems from various providers, whichrequire intensive point-to-point integration.

Complex business environmentsThe heterogeneous system landscape results in a complex businessenvironment, especially for the front-end PCs of users, which requires anenormous maintenance effort with several dependencies and an averageindustry cost of � 8,000 per year per interface.

Protected technology and communications protocolsMany business partners do not have the same knowledge of businessprocesses or they do not have access to business information about a partnercompany. This jeopardizes future success.

606 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 617: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Motivation for Portals

Figure 298: The End User Problem

End users must frequently combine applications into interrelated business viewsand business processes. This means that users must find information and react toit. For example, a user finds information about a lost delivery to a single customer,irrespective of where this information is in the IT landscape and irrespective of thesystem or business process required to react to this information. In general, manydifferent user interfaces are required to implement the many different applicationsystems involved in the process. As a result, companies are frequently unableto avail of opportunities for improved customer service, increased efficiency inprocesses, and higher worker productivity.

2006/Q2 © 2006 SAP AG. All rights reserved. 607

Page 618: Plm412 en Col62 Fv Part a4

Unit 14: Enterprise Portals � Optional Unit PLM412

Figure 299: Advantages of a Portal: User and Role-Oriented �Webtops�

An enterprise portal can create a connection between the applications and theinformation required to complete a task. With an enterprise portal, the end userobtains a complete view of the company and its processes at a glance. Theseprocesses are based on several different data sources and they are integrated intomany operative application systems.

608 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 619: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Motivation for Portals

Lesson Summary

You should now be able to:� Explain the purpose of an enterprise portal� Name a company's goals for a portal� Describe the advantages associated with using an enterprise portal

2006/Q2 © 2006 SAP AG. All rights reserved. 609

Page 620: Plm412 en Col62 Fv Part a4

Unit 14: Enterprise Portals � Optional Unit PLM412

Lesson: SAP's Product Strategy

Lesson OverviewThis lesson provides an overview of SAP's product range, at the center of which ismySAP Business Suite.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� List some of the advantages that your business can enjoy by using mySAPBusiness Suite.

Business ExampleYou require an overview of SAP's software portfolio.

SAP's Software PortfolioSAP is continuously extending and optimizing its software portfolio,which is perfectly tailored to market and customer requirements. Forthis reason, SAP has developed many industry-specific applications overthe years. The integration of various application systems (includingthose from different manufacturers and without company limitations) isa key factor that essentially creates universal and transparent processesand therefore also greatly contributes to the return on investment (ROI).SAP's software portfolio has succeeded in keeping pace with this trend.In addition to the portfolio for large enterprises, the applications for small andmidsize enterprises also belong to SAP's software family.

The following figures give you an overview of the structure of SAP applications.

610 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 621: Plm412 en Col62 Fv Part a4

PLM412 Lesson: SAP�s Product Strategy

Figure 300: SAP's Portfolio

The basic elements of SAP applications are:

� SAP NetWeaver� mySAP Business Suite� SAP xApps (Composite Applications)� Industry Solutions� Solutions for Small and Midsize Enterprises

SAP NetWeaverSAP NetWeaver is the technological infrastructure for all SAP applications.For more information, see http://www.sap.com/netweaver.

mySAP Business SuitemySAP Business Suite groups all cross-industry business applications thatare based on SAP NetWeaver.For more information, see http://www.sap.com/solutions.

SAP xApps (Composite Applications)SAP Composite Applications (SAP xApps) allow you to integrate varioussystems into one user interface. The Composite Application Framework,which is a part of SAP NetWeaver, quickly and efficiently integrates the Webservices and data of various systems and also offers the best flexibility forthe continuous development of business processes.For more information, see http://www.sap.com/xapps.

2006/Q2 © 2006 SAP AG. All rights reserved. 611

Page 622: Plm412 en Col62 Fv Part a4

Unit 14: Enterprise Portals � Optional Unit PLM412

Industry SolutionsIndustry solutions offer business functions for selected industries. Thesefunctions are implemented in an SAP ECC system and are available as anadd-on.For more information, see http://www.sap.com/industries.

Applications for Small and Midsize EnterprisesmySAP All-in-One is a product that is based on mySAP Business Suiteand contains business functions from other SAP applications. This meansthat each combination of functions creates a different mySAP All-in-Onepackage. This product is suitable for customers who have several dozento a couple of hundred end users.SAP Business One is a product that can easily be connected to other existingSAP landscapes (using XML). The software is programmed in C++ andcan be installed on various Microsoft Windows operating systems. SAPBusiness One contains functions that are important for managing yourbusiness, such as financial accounting, customer management, purchasingand warehouse management. Even the smallest of businesses can profitfrom employing this software.For more information, see http://www.sap.com/smb.

Functions of mySAP Business SuitemySAP Business Suite is a complete package of open business applicationsthat connect all of the relevant people, information and processes to each otherand therefore make your business relationships more effective. Various SAPapplications are combined to form mySAP Business Suite. For more informationabout all of SAP's applications, see http://www.sap.com/solutions. All of SAP'sapplications, including mySAP ERP, are based on SAP NetWeaver.

mySAP Business Suite provides:

� A full range of business applications� An open, flexible, and also tried and tested, mature technological

infrastructure� Interfaces for integrating non-SAP products� Many modifiable components to meet your company's requirements� Many industry-specific functions

mySAP Business Suite offers many options for integrating both your internalbusiness processes and the systems of your business partners, to facilitatecollaborative business processes. The integration of collaborative processesis supported by various technologies including SAP Exchange Infrastructure,Application Link Enabling, Electronic Data Interchange (EDI), XML dataexchange, SAP Composite Applications (SAP xApps) and Web services.

612 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 623: Plm412 en Col62 Fv Part a4

PLM412 Lesson: SAP�s Product Strategy

mySAP ERP 2005 is one of the applications in mySAP Business Suite. Thefollowing figure provides an overview of mySAP ERP 2005 with the centralcomponent ECC 6.0 and it highlights the differences between mySAP ERP andSAP R/3. Furthermore, this figure illustrates the increased range of functions inmySAP ERP.

Figure 301: Functions of mySAP ERP 2005

Hint: Remember that the classic SAP R/3 up to and including SAPR/3 4.6C runs on SAP Basis. As of SAP R/3 Enterprise, the runtimeenvironment is available on the SAP Web Application Server (SAP WebAS), which is the evolutionary further development of SAP Basis. As ofRelease SAP ECC 6.0, the further development of SAP Web AS is calledthe SAP NetWeaver Application Server.

The above application forms part of mySAP Business Suite. An applicationcomprises many components that represent independent application systems. ThemySAP ERP application, for example, comprises the components SAP ECC, SAPSRM and SAP SEM.

2006/Q2 © 2006 SAP AG. All rights reserved. 613

Page 624: Plm412 en Col62 Fv Part a4

Unit 14: Enterprise Portals � Optional Unit PLM412

Lesson Summary

You should now be able to:� List some of the advantages that your business can enjoy by using mySAP

Business Suite.

Related InformationAdditional information is available on the following SAP Web sites. All Web sitesare freely accessible, but some require free registration.

� http://www.sap.com� http://help.sap.com� http://service.sap.com� http://www.sap.info� http://www.sapinsideronline.com

614 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 625: Plm412 en Col62 Fv Part a4

PLM412 Lesson: SAP NetWeaver

Lesson: SAP NetWeaver

Lesson OverviewThis lesson explains the central role of the SAP NetWeaver Application Server inSAP NetWeaver.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Explain the basic concepts of SAP NetWeaver� Describe the central role of the SAP NetWeaver Application Server� Explain the role of SAP NetWeaver AS Java

Business ExampleYou want to find out more about SAP NetWeaver and the role of the SAPNetWeaver Application Server (SAP NetWeaver AS) in SAP NetWeaver.

SAP NetWeaverThe technology platform SAP NetWeaver supports a flexible, step-by-step andefficient introduction of important IT processes into business. As a result of thehigh degree of integration of individual platform functions, their openness andthe use of industry standards, the integration and application platform makesa significant contribution towards reducing the total cost of ownership (TCO)across the entire IT landscape. SAP NetWeaver represents the technical basis formySAP Business Suite, SAP Composite Applications (SAP xApps) and otherindustry-specific SAP applications.

SAP NetWeaver is also the technical basis for the trendsetting EnterpriseServices Architecture (ESA). In the Enterprise Services Architecture, applicationfunctions are provided in the form of enterprise services. These are flexible Webservices that can be combined and used in business. Various providers makethese enterprise services available across networks. These services use openstandardized interfaces to communicate with other applications.

SAP NetWeaver integrates and combines people, information and businessprocesses across technologies and businesses. It offers businesses the option toquickly adapt to changes. SAP NetWeaver guarantees that any business processesthat are important for a company are reliable, secure and scalable. Furthermore,companies with SAP NetWeaver can benefit more from their current softwareand systems. Unequal integration technologies are standardized and predefinedbusiness content is made available, which means that the time and effort requiredfor manual integration is reduced. SAP NetWeaver is based on industry-standard

2006/Q2 © 2006 SAP AG. All rights reserved. 615

Page 626: Plm412 en Col62 Fv Part a4

Unit 14: Enterprise Portals � Optional Unit PLM412

technology and can be enhanced using some of the development tools that arecurrently available, for example, Java 2 Platform, Enterprise Edition (J2EE),Microsoft .NET, and IBM WebSphere.

IT Practices and IT Scenarios

Figure 302: IT Practices and IT Scenarios

SAP NetWeaver allows you to use a range of solution options known as ITPractices to implement IT processes. For each practice, SAP NetWeaver supportsa range of key IT activities, which you can execute without any problems when youuse the platform's integrated components. Here, the focus is not on systems andtechnological components, but rather on IT and the business goals of a company.In individual and manageable projects, IT Practices allow you to implement thesegoals in succession and in order of importance, depending on your company'srequirements. IT Practices, for example, increase user productivity by havingimproved collaborations, personalized accesses to applications and data, andoptimized Knowledge Management. IT Practices demonstrate how IT Scenarioscan be used in SAP NetWeaver to solve certain IT problems. For each IT Practice,SAP NetWeaver delivers suitable IT Scenarios that provide some guidelines forimplementing the IT Practice.

The goal of IT Scenarios is to assist you (the customer, partner or service provider)when you install, configure and operate SAP NetWeaver, when you operate SAP'sown applications, when you operate customer-specific applications, and when youimplement IT concepts that you have defined.

616 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 627: Plm412 en Col62 Fv Part a4

PLM412 Lesson: SAP NetWeaver

In the case of the SAP NetWeaver Portal, we use various IT Practices that involvesuitable IT Scenarios for implementing the functions you require. The individualsteps required to successfully implement a complete IT Scenario are subdividedinto individual IT Variants.

Figure 303: IT Scenarios in the SAP NetWeaver Portal Environment

Layers of SAP NetWeaver

2006/Q2 © 2006 SAP AG. All rights reserved. 617

Page 628: Plm412 en Col62 Fv Part a4

Unit 14: Enterprise Portals � Optional Unit PLM412

Figure 304: SAP NetWeaver

� People Integration

People Integration ensures that your workers have access to the informationand functions they require to do their jobs both quickly and efficiently. Inthis context, the functions of the SAP NetWeaver Portal are the mostsignificant. SAP NetWeaver Mobile is the universal platform for businessmobility. It supports SAP solutions for mobile business.

� Information Integration

This level, Information Integration, gives access to all structured andunstructured information in your company. The key capabilities ofinformation integration are modeled on SAP NetWeaver BusinessIntelligence, Knowledge Management, as a component of the SAPNetWeaver Portal and SAP NetWeaver Master Data Management. Allof the aforementioned key capabilities provide comprehensive options forensuring uniform access to the information distributed in a company.

� Process Integration

Process Integration makes sure that business processes work in aheterogeneous landscape without system restrictions. The SAP NetWeaverExchange Infrastructure (SAP XI) plays an important role because itconnects SAP systems to non-SAP systems. For this, you use open XMLand Java standards, in particular.

� Application Platform

The SAP NetWeaver Application Server is a proven infrastructure foroperating business applications that were set up on key technologies such asJ2EE or ABAP. In addition to the runtime environment for J2EE and ABAPapplications, the relevant development tools are also delivered, which supportyou when you implement your applications. Open standards, browser-basedaccess to applications and Web services complete the application platformand are important for the Enterprise Service Architecture.

Both across and parallel to these four levels, SAP NetWeaver offers LifecycleManagement and its Composite Application Framework:

Lifecycle ManagementLifecycle Management supports design, development, deployment andchange management for the entire solution, and therefore meets therequirements for security, design, modeling, testing and system landscapemanagement.

618 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 629: Plm412 en Col62 Fv Part a4

PLM412 Lesson: SAP NetWeaver

Composite Application FrameworkThe Composite Application Framework is integrated into SAP NetWeaverand enables SAP and its partners to create new applications by using tools,frameworks, rules and methods that are tailored to business processes acrossall functional areas.

SAP NetWeaver Application Server (SAP NetWeaverAS)Almost all SAP systems are based on SAP NetWeaver AS and use it as a runtimeenvironment. SAP NetWeaver AS, together with the database, represents theapplication platform of SAP NetWeaver.

Figure 305: SAP NetWeaver AS as a Fixed Component of SAP Systems

2006/Q2 © 2006 SAP AG. All rights reserved. 619

Page 630: Plm412 en Col62 Fv Part a4

Unit 14: Enterprise Portals � Optional Unit PLM412

Figure 306: SAP NetWeaver Application Server

SAP NetWeaver AS is the logical result from the further development of SAP'sapplication server technology (previously: SAP Basis). Here, particular attentionwas given to Web-based applications.

SAP NetWeaver AS provides the following:

� A dependable and comprehensively tested runtime environment that hasbeen in permanent development for more than ten years

� A framework for executing complex business processes that meet the highestsecurity standards

� A reliable and user-friendly development environment� Support for open standards including HTTP, HTTPS, SMTP, WebDAV,

SOAP, SSL, SSO, X.509, Unicode, HTML, XML and WML� High scalability� Support for various operating system and database platforms

620 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 631: Plm412 en Col62 Fv Part a4

PLM412 Lesson: SAP NetWeaver

Figure 307: SAP NetWeaver AS Installation Options

Since the applications delivered by SAP do not always require both the ABAPand Java runtime environments, there are different installation options for SAPNetWeaver AS. They are as follows:

� SAP NetWeaver AS ABAP: A complete infrastructure in whichABAP-based applications can be developed and used.

� SAP NetWeaver AS Java: A complete infrastructure in whichJ2EE-compliant applications can be developed and used.

� SAP NetWeaver AS ABAP+Java (add-in installation): A completeinfrastructure in which both ABAP-based and J2EE-based applicationscan be developed and used. This installation places emphasis on seamlessJava-ABAP integration.

Note: The SAP NetWeaver Portal requires SAP NetWeaver AS Java, butit can also work on SAP NetWeaver AS ABAP+Java.

SAP NetWeaver AS JavaAs a component of SAP NetWeaver AS Java, the J2EE Engine provides a runtimeenvironment for Java applications.

The J2EE Engine corresponds to the J2EE standard defined by Sun Microsystems(Java 2 Platform, Enterprise Edition) and it is compliant with J2EE-1.3. The aimof this specification is to use a standard Java Application Server as a runtimeenvironment for the Java applications of various providers.

2006/Q2 © 2006 SAP AG. All rights reserved. 621

Page 632: Plm412 en Col62 Fv Part a4

Unit 14: Enterprise Portals � Optional Unit PLM412

There are more than 30 different Java application servers available on the market.They differ in terms of their J2EE specification, the extent to which they supportJ2EE specifications, and whether they pass the SUN J2EE compatibility test. Thefollowing J2EE servers are the most popular:

� SAP J2EE Engine� Weblogic (BEA)� WebSphere (IBM)� Sun ONE Application Server (Netscape/Sun)� JRun (Allaire)� Oracle Application Server 10g� Inprise (Inprise/Borland)

The J2EE Engine makes a runtime environment available for various Javaapplications such as Enterprise Java Beans (EJB). The J2EE Engine providesruntime services for Java Server Pages (JSP) and servlets.

Figure 308: SAP NetWeaver AS Java

One Java instance includes two node types: the Java Server and Java Dispatcher.The Java Dispatcher receives the client orders and distributes them to the JavaServer node. The Java Servers execute the required Java code in one thread, adoptdatabase accesses and make requested Web sites available. The Java Dispatcher isthen used to send the result back to the requesting client.

Both node types run in their own Java Virtual Machine (Java VM). It is possible toconfigure several server nodes and dispatcher nodes, which are distributed acrossvarious computers that belong to one SAP NetWeaver AS Java.

622 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 633: Plm412 en Col62 Fv Part a4

PLM412 Lesson: SAP NetWeaver

Another process that also runs in its own Java Virtual Machine is the SoftwareDeployment Manager (SDM). This is used to install new Java applications and topatch these applications.

2006/Q2 © 2006 SAP AG. All rights reserved. 623

Page 634: Plm412 en Col62 Fv Part a4

Unit 14: Enterprise Portals � Optional Unit PLM412

Lesson Summary

You should now be able to:� Explain the basic concepts of SAP NetWeaver� Describe the central role of the SAP NetWeaver Application Server� Explain the role of SAP NetWeaver AS Java

Related InformationFor more information, see:

� http://www.sap.com/netweaver.� http://service.sap.com/it-scenarios

624 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 635: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Introducing SAP NetWeaver Portal

Lesson: Introducing SAP NetWeaver Portal

Lesson OverviewThis lesson deals with the main functions of the SAP NetWeaver Portal as a keycomponent of SAP NetWeaver.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Describe the main functions of the SAP NetWeaver Portal� Name the advantages associated with business packages� Outline the development of the SAP NetWeaver Portal

Business ExampleYou want to obtain an overview of the core functions of the SAP NetWeaver Portal.

SAP NetWeaver PortalThe SAP NetWeaver Portal is a comprehensive portal infrastructure completewith knowledge management and collaboration services. The predefined content,known as the business content, ensures fast implementation and lower costs forintegrating IT systems that already exist. The SAP NetWeaver Portal providesemployees, partners and customers with secure access to all information andapplications in the company, depending on their tasks. Since your users' approachto completing tasks and solving problems is faster, more efficient and morecost-effective, your company benefits from having a portal, both in the short andlong term.

2006/Q2 © 2006 SAP AG. All rights reserved. 625

Page 636: Plm412 en Col62 Fv Part a4

Unit 14: Enterprise Portals � Optional Unit PLM412

Figure 309: SAP NetWeaver Portal as Part of SAP NetWeaver

Core CharacteristicsThe SAP NetWeaver Portal provides the following core functions:

� Portal Infrastructure: The portal infrastructure provides the basic functionsof the SAP NetWeaver Portal and ensures browser-based access to varioustypes of information as well as many different systems. It combinesapplications, information and processes from SAP and other sources into oneinterrelated, role-based portal. It supports UNIX and Microsoft WindowsServer and is shipped in more than 20 different languages.

� Collaboration: The collaboration functions in the SAP NetWeaver Portalprovide a platform for efficient collaboration. Virtual rooms, known ascollaboration rooms, as well as tools for real-time collaborations provideteams with highly-efficient access to shared resources. The close integrationof existing groupware systems ensures access to shared e-mails andcalendars. Discussion forums complete the collaboration concept andprovide your employees with a virtual location for open discussions.

� Knowledge Management: As a central access point, the KnowledgeManagement functions provide access to unstructured information thatmay be persisted in different storage systems. The initial content ofknowledge management already has different connectors to different storagesystems. Third parties use the open architecture to implement connectorsfor their storage systems. A uniform, user-friendly interface facilitatesaccess to functions such as those for creating and publishing documents,intelligent classification and subscription, stable version management, aswell as powerful search and navigation functions. It also provides an openframework for creating and managing document-based and file-basedapplications as well as content and user services.

626 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 637: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Introducing SAP NetWeaver Portal

Figure 310: Core Functions of the SAP NetWeaver Portal

2006/Q2 © 2006 SAP AG. All rights reserved. 627

Page 638: Plm412 en Col62 Fv Part a4

Unit 14: Enterprise Portals � Optional Unit PLM412

The SAP NetWeaver Portal makes a large contribution to reducing the totalcost of ownership (TCO). This is achieved at the various portal levels. Frommanagement of the SAP NetWeaver Application Server, which forms the basis forthe portal, right through to the end user, SAP provides all of the relevant tools.

� Comprehensive Platform Support: When you deploy SAP NetWeaverAS as the runtime environment for the SAP NetWeaver Portal, you areguaranteed comprehensive platform support. Various UNIX derivativesand Microsoft Windows Servers in conjunction with various databases arealso supported.

� Business Packages: In addition to the initial content, SAP delivers businesspackages. Business packages contain predefined portal content such as callsfor transactions and reports in different back-end systems, applicationsbased on Web Dynpro, and applications written in Java. The purpose ofthis predefined content, which may also be provided by third parties, is tofacilitate a fast implementation phase as well as provide content managerswith the option to quickly integrate new applications into an existing SAPNetWeaver Portal.

Business packages are therefore tailored to certain target groups and all oftheir business tasks. This is also reflected in the classification of businesspackages, which are divided according to three target groups: end users,specialists and managers. Business packages provide a comprehensivebusiness content library that reflects SAP's thirty years of experience invarious industries.

You can download SAP business packages from the Web site sdn.sap.com.

� Language Support: To make the portal compatible with a company thatoperates globally in several different languages, the SAP NetWeaver Portalis shipped with more than 20 languages and the corresponding locale supportfor operating systems. Furthermore, for languages that read from right to left,the relevant support is provided in addition to a modified portal interface.

� Interoperability: The SAP NetWeaver Portal can be fully adaptedto your company's requirements. In addition to the portal's numerousconfiguration options, you can also customize your SAP NetWeaverPortal. Interoperability gives you the option to write your portal-specificapplications in the Microsoft .NET development environment or in the SAPNetWeaver Developer Studio.

� Federated Portal Network: For decentralized companies with several portalinstallations, various scenarios enable you to exchange content betweenportals or set up a central enterprise portal that houses the content of variousdecentralized portals. Since you have access here to various standards, youcan also integrate the content of portals from other manufacturers into theSAP NetWeaver Portal.

628 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 639: Plm412 en Col62 Fv Part a4

PLM412 Lesson: Introducing SAP NetWeaver Portal

SAP NetWeaver Portal GenealogyThe following figure provides an overview of the development of the SAPNetWeaver Portal. The �ancestors� of the current portal releases are the SAPWorkplace, the TopTier Enterprise Information Portal, and the EnterpriseUnification Portal.

One large step involved consolidating the best of these two worlds in SAPEnterprise Portal 5.0. In Release SAP Enterprise Portal 6.0, the platform supportwas extended considerably and key architectural changes were made. The currentrelease, SAP NetWeaver Portal 7.0, represents the latest development of thisproduct.

Figure 311: The Development of SAP NetWeaver Portal

2006/Q2 © 2006 SAP AG. All rights reserved. 629

Page 640: Plm412 en Col62 Fv Part a4

Unit 14: Enterprise Portals � Optional Unit PLM412

Lesson Summary

You should now be able to:� Describe the main functions of the SAP NetWeaver Portal� Name the advantages associated with business packages� Outline the development of the SAP NetWeaver Portal

Related Information

� SAP home page: www.sap.com� SAP NetWeaver Portal home page: www.sap.com/netweaver� Quick link /nw-ep on SAP Service Marketplace� SAP Developer Network at sdn.sap.com

630 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 641: Plm412 en Col62 Fv Part a4

PLM412 Unit Summary

Unit SummaryYou should now be able to:� Explain the purpose of an enterprise portal� Name a company's goals for a portal� Describe the advantages associated with using an enterprise portal� List some of the advantages that your business can enjoy by using mySAP

Business Suite.� Explain the basic concepts of SAP NetWeaver� Describe the central role of the SAP NetWeaver Application Server� Explain the role of SAP NetWeaver AS Java� Describe the main functions of the SAP NetWeaver Portal� Name the advantages associated with business packages� Outline the development of the SAP NetWeaver Portal

Related Information

2006/Q2 © 2006 SAP AG. All rights reserved. 631

Page 642: Plm412 en Col62 Fv Part a4

Course Summary PLM412

Course SummaryYou should now be able to:

� Use the QM master data to plan and carry out inspections� Use quality notifications in logistics processes.� Use the different evaluation possibilities in Quality Management.

632 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 643: Plm412 en Col62 Fv Part a4

Appendix 1Vendor Evaluation

Appendix A: Vendor Evaluation

� Contents:

� Business Scenario� Score Levels for Vendor Evaluation� �Quality� score� Calculating the Complaint Score� Completing the notification

Vendor Evaluation: Unit Objectives

� At the conclusion of this unit, you will be able to:

� Describe the score levels for the vendor evaluation.� Explain how the�Quality� score is made up.

� Use the formula for calculating the complaint score.

2006/Q2 © 2006 SAP AG. All rights reserved. 633

Page 644: Plm412 en Col62 Fv Part a4

Appendix 1: Vendor Evaluation PLM412

Figure 312: Vendor Evaluation: Business Scenario

Figure 313: Vendor Evaluation: Criteria

The total score represents the evaluation of a vendor. This score is the sum of thescores that the vendor receives for all the main criteria.

The scores for the main and subcriteria illustrate the performance of a vendor inmore detail than the total score.

The scores that the vendor receives for the individual criteria can be of varyingimportance for you. This is expressed by the weighting share.

634 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 645: Plm412 en Col62 Fv Part a4

PLM412 Appendix 1: Vendor Evaluation

Figure 314: Subcriteria of the �Quality� Score

The quality score for goods receipt inspections is calculated as follows:

QScGR = ( S1 + S2 ) / ( n1 + n2 )S1 = Sum of the quality scores for the inspection lotsn1 = No. of inspection lotsn2 = No. of deliveries of a material with a q-info record and without

a goods receiptS2 = n2 x QSc max

You can display this quality score calculation for the vendor, for any material ofthe vendor, as well as for each inspection type for a material.

The audit score can be calculated in the same way as the goods receipt score.However, you can overwrite the audit score.

2006/Q2 © 2006 SAP AG. All rights reserved. 635

Page 646: Plm412 en Col62 Fv Part a4

Appendix 1: Vendor Evaluation PLM412

Figure 315: Calculating the Complaint Score

QScmin =Limit for the lowest quality score from table TQSS(Customizing→ Quality Management→ Basic Settings→Maintain Settings at Client Level)

QScmax =Maximum quality score from table TQSS (Customizing→Quality Management→ Basic Settings→ Maintain Settings atClient Level)

Factor: Percentage rate, relevant share of sales volume for calculatingthe quality score from table T147 (Customizing→ MaterialsManagement→ Purchasing→ Vendor Evaluation→ DefinePurchasing Organization Data for Vendor Evaluation)

Salesvolume:

Sales by the vendor for the chosen time period and purchasingorganization

Nonconfor-mity:

Calculated nonconformity costs = Estimated nonconformitycosts x number of notifications

You maintain the estimated nonconformity costs in Customizing for notifications.No calculation of the quality score is therefore necessary.

You can control the selection of incoming notifications for the vendor evaluationwith the help of the user exit QLIB0002.

You can use the user exit QLIB0001 to influence the calculation of the qualityscore.

636 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 647: Plm412 en Col62 Fv Part a4

PLM412 Appendix 1: Vendor Evaluation

Figure 316: Relevant Elements for Vendor Evaluation

Only completed notifications with origin �Q2� and status �caused externally� areused for the calculation of the quality score.

Figure 317: Vendor Evaluations

The hit list sorts your vendor by total score, in descending order. In this way youcan see at a glance which vendors are among your best, those who are average,and those who are below average.

2006/Q2 © 2006 SAP AG. All rights reserved. 637

Page 648: Plm412 en Col62 Fv Part a4

Appendix 1: Vendor Evaluation PLM412

The list of evaluations for the material or material group shows you a list ofvendors, with respect to a certain material or group of materials. Using this list,you can determine the best vendors for delivering a particularly important material.

The evaluation comparison is an evaluation that compares the general evaluationof the vendor to the evaluation of the same vendor for delivering a certain material.This evaluation differs from the other evaluations, since it gives you a moredetailed analysis of a vendor, without having to compare him to other vendors.Instead, the total evaluation that is calculated from the scores for the deliveries ofall materials, is compared to the evaluation the vendor would have obtained, ifonly one particular material formed the basis of the evaluation.

Vendor Evaluation: Unit Summary

� One of the main criteria in the vendor evaluation is Quality. The subcriteriareceive scores (quality scores) from goods receipt inspections, audits andcomplaints processing.

� When the complaint score is calculated, the valuated quality notifications forthe vendor are given in relation to sales volume.

� Only completed notifications with origin Q2 and status caused externally areused for the calculation of the complaints score.

638 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 649: Plm412 en Col62 Fv Part a4

Appendix 2Technical Details

Contents:

� BAdls (basics)� BAdIs for quality planning and quality inspections

Figure 318: Business Add-Ins: Architecture

Business Add-Ins, unlike customer exits, take into account the changes to thesoftware delivery process. The top part of the graphic illustrates the typicaldelivery process: It no longer merely consists of provider and user. Instead, it cannow contain a whole chain of intermediate providers.

2006/Q2 © 2006 SAP AG. All rights reserved. 639

Page 650: Plm412 en Col62 Fv Part a4

Appendix 2: Technical Details PLM412

The bottom part of the graphic explains how Business Add-Ins work:Enhancements are made possible by SAP application programs. This requiresat least one interface and an adapter class that implements it. The interface isimplemented by the user.

The main advantage of this concept is the capacity for reuse: Once implemented, aBusiness Add-In can be implemented by other links in the software chain (furtherto the right in the graphic).

Furthermore, an implementation can also offer Business Add-Ins of its own.

Figure 319: Business Add-Ins: Components

A Business Add-In contains the components of an enhancement. Currently, eachBusiness Add-In can contain the following components:

� Program enhancements� Menu enhancements

In future releases, the other components included in customer exits will also beavailable as BAdI components.

Several components are created when you define a Business Add-In:

� Interface� Generated class (add-in adapter) that implements the interface

640 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 651: Plm412 en Col62 Fv Part a4

PLM412 Appendix 2: Technical Details

The generated class (add-in adapter) performs the following tasks:

� Filtering: If you implement a filter-dependent Business Add-In, the adapterclass ensures that only the relevant implementations are called.

� Control: The adapter class calls the active implementations.

Figure 320: Business Add-Ins: Process Flow Diagram

This graphic shows the process flow of a program that contains a Business Add-Incall. It enables us to see the possibilities and limitations inherent in BusinessAdd-Ins.

Not displayed: You must declare a reference variable referring to the BAdIinterface in the declaration section.

In the first step, an object reference is created. This replaces the service classCL_EXITHANDLER provided by SAP. We will discuss the precise syntax lateron. This generates the conditions for calling methods of program enhancements.

When you define a Business Add-In, the system generates an adapter class, whichimplements the interface. In call (2), the interface method of the adapter class iscalled. The adapter class searches for all of the implementations of the BusinessAdd-In and calls the implemented methods.

2006/Q2 © 2006 SAP AG. All rights reserved. 641

Page 652: Plm412 en Col62 Fv Part a4

Appendix 2: Technical Details PLM412

Figure 321: Implementing Business Add-Ins: Initial Screen

To implement Business Add-Ins, use transaction SE19 (Tools→ ABAP Workbench→ Utilities→ Business Add Ins→ Implementation).

Enter a name for the implementation and choose �Create�. A dialog box appears.Enter the name of the Business Add-In. The maintenance screen for the BusinessAdd-In then appears.

Alternatively, you can use the Business Add-In definition transaction (SE18) toreach its implementations. The menu contains an entry �Implementation�, whichyou can use to get an overview of the existing implementations. You can alsocreate new implementations from here.

642 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 653: Plm412 en Col62 Fv Part a4

PLM412 Appendix 2: Technical Details

Figure 322: Implementing Business Add-Ins: Methods

You can assign any name to the implementing class. However, it is a good idea toobserve the proposed naming convention. The suggested name is constructed asfollows:

� Namespace prefix, Y, or Z� CL_ (for class)� IM_ (for implementation)

Name of the implementation

To implement the method, double-click its name. The system starts the ClassBuilder editor.

When you have finished, you must activate your objects.

2006/Q2 © 2006 SAP AG. All rights reserved. 643

Page 654: Plm412 en Col62 Fv Part a4

Appendix 2: Technical Details PLM412

Figure 323: Implementing Business Add-Ins: Private Methods

In the implementing class, you can create private methods that you then call fromthe interface method.

To do this you must edit the implementing classes directly in the Class Builder.You create the private methods including interfaces. Specify a visibility for themethod, and implement it.

Figure 324: Implementing Business Add-Ins: Activation

Use the "Activate" icon to activate the implementation of a Business Add-In.From now on, the methods of the implementation will be executed when therelevant calling program is executed.

644 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 655: Plm412 en Col62 Fv Part a4

PLM412 Appendix 2: Technical Details

If you deactivate the implementation, the methods will no longer be called.However, the corresponding calls in the application program are still processed.The difference is that the instance of the adapter class will no longer find anyactive implementations. Unlike �CALL CUSTOMER-FUNCTION� , the �CALLMETHOD CL_EXITHANDLER=>GET_INSTANCE� call is still executed evenif there are no implementations. The same applies to the method call that calls themethod of the adapter class.

You can only activate or deactivate an implementation in its original systemwithout modification. The activation or deactivation must be transported intosubsequent systems.

If a Business Add-In can only have one implementation, there can still be morethan one implementation in the same system. However, only one can be activeat any time.

Figure 325: Business Add-In Definition: Initial Screen

To create a Business Add-In, use the BAdI Builder (Tools→ ABAP Workbench→Utilities→ Business Add-Ins→ Definition) or transaction code SE18.

2006/Q2 © 2006 SAP AG. All rights reserved. 645

Page 656: Plm412 en Col62 Fv Part a4

Appendix 2: Technical Details PLM412

Figure 326: Business Add-In Definition: Attributes

A business add-in has two important attributes that you must define:

� Reusable� Filter-dependent

If you want the business add-in to support multiple parallel implementations,select �Reusable�. The sequence in which the implementations will be processedis not defined. Even if the business add-in does not support multiple use, you canstill have more than one implementation for it. However, only one implementationcan be active at a time.

If you make a business add-in filter-dependent, you can make calls to it dependingon certain conditions. You must specify the filter type in the form of a dataelement. The value table of the domain used by the data element contains thevalid values for the implementation.

When the enhancement method is called, a filter value must be passed to theinterface.

646 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 657: Plm412 en Col62 Fv Part a4

PLM412 Appendix 2: Technical Details

Figure 327: Business Add-In Definition: Interface Methods

The system proposes a name for the interface and the generated class. You can, inprinciple, change the name of the interface to anything you like. However, yourBAdI will be easier to understand if you retain the proposed name.

The name of the generated class is composed as follows:

� Namespace prefix� CL_ (to signify a class in general)� EX_ (stands for �exit�)� Name of Business Add-In

If you double-click on the interface name, the system switches to the ClassBuilder, where you can define the interface methods.

A Business Add-In interface can have several interface methods.

2006/Q2 © 2006 SAP AG. All rights reserved. 647

Page 658: Plm412 en Col62 Fv Part a4

Appendix 2: Technical Details PLM412

Figure 328: Business Add-In Definition: Method Interface Parameters

You can use all of the normal functions of the Class Builder. For example, you can:

� Define interface methods� Define interface parameters for the methods� Declare the attributes of the interface

If the Business Add-In is filter-dependent, you must define an import parameterflt_val for each method. Otherwise, you define the interface parameters you needfor the enhancement.

Figure 329: BAdI Definition: Activating the Interface

648 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 659: Plm412 en Col62 Fv Part a4

PLM412 Appendix 2: Technical Details

Once you have finished working on your interface, you must activate it. Thisgenerates the adapter class for the Business Add-In.

If you change the interface, the adapter class is automatically regenerated.

You can also generate the adapter class explicitly in the initial screen of theBusiness Add-In maintenance at any time (by choosing Utilities→ Regenerate).

Figure 330: Default Implementation

A default implementation is executed whenever no active implementation of aBusiness Add-In exists. The default implementation is created by the enhancementprovider.

You can create a default implementation in the BAdI definition by choosing Goto→ Default code. The system automatically generates a class with a predefinedname. Implement the methods so that the required default behavior is generated.

You can also create a sample implementation. This is a template that can beinserted into the methods of the implementation.

You can create sample implementations by choosing Goto→ Sample code. Thesystem creates a class that implements the methods of the interface. The samplecode is displayed for the user as a template.

2006/Q2 © 2006 SAP AG. All rights reserved. 649

Page 660: Plm412 en Col62 Fv Part a4

Appendix 2: Technical Details PLM412

Communication using BAdIs (1)

� BAdI QM_INPUT_PROCEDURE: Input Processing

� Implementation QM_INPPROC_100: Output like input (as regardsdecimal places)

� Implementation QM_INPPROC_200: Output according to significantdigits

� BAdI QPAP_FLEX_PLAN: Flexible Specification Selection

� Characteristics and operations read in the standard can be changedbefore they are written to the database for an inspection lot. This meansthat you can change specifications such as target values, tolerances,and so on.

The implementation QM_INPROC_100 can be used in input processing when, forexample, a measuring device only displays a result with a precision of one decimalplace, but two decimal places were specified for the result.

� Example: Measured values are output with the same number of decimalplaces with which they were entered.

The implementation QM_INPROC_200 can be used in input processing if you areusing a measuring device that has a higher precision than is specified.

� Example: Measured values are rounded to a predefined number of significantdigits.

An implementation for the stability study for the BAdI QPAP_FLEX_PLANalready exists in the standard (BAdI QPAP_FLEX_PLAN_16). To use thisfunction for other inspection lot origins, you must create a separate implementationfor each inspection lot origin for which you want to use flexible inspectionspecifications. This is because the BAdI contains a filter for the inspection lotorigin. Additional criteria for the application of flexible inspection specificationscan be called in the implementation (for example, whether or not a manual samplecalculation must be performed).

650 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 661: Plm412 en Col62 Fv Part a4

PLM412 Appendix 2: Technical Details

Communication using BAdIs (2)

� BAdI CEWB_TSK_UPDATE: Inspection plan maintenance and checkin the EWB

� When you save the inspection plan in the Engineering Workbench, allof the inspection plan data is made available to a BAdI.

� BAdI CEWB_CHA_MENU_EXTERN: Menu enhancements in theEWB

� An additional pushbutton can be defined at characteristic-, operation-,and header level on the overview screen of the Engineering Workbench.This pushbutton can be used to call user-defined programs.

� BAdI CEWB_TSK_SCREENS: Additional customer-specific fields inthe EWB

Example:

� In the Engineering Workbench, you can maintain user-defined fields atcharacteristic-, operation-, and header level of the inspection plan.

Communication using BAdIs (3)

� BAdI CEWB_CHA_MENU_EXTERN: Menu enhancements in theEWB

� An additional pushbutton can be defined at characteristic-, operation-,and header level on the overview screen of the Engineering Workbench.This pushbutton can be used to call user-defined programs.

� BAdI QEVA_SUBSCREEN_1101: Subscreen for Usage Decision Data

� In the transactions for the usage decision (create, change, display),additional data can be displayed in a subscreen of the header screen. Apushbutton can be used to call another function.

� BAdI QE_SAVE: Saving in Results Recording

� During a save in results recording, all data in the relevant inspectionlot is made available to a BAdI.

The BAdI QE_SAVE is not used in:

� Process-optimized results recording� Results recording on the Web� QM-IDI� The corresponding BAPIs

2006/Q2 © 2006 SAP AG. All rights reserved. 651

Page 662: Plm412 en Col62 Fv Part a4

Appendix 2: Technical Details PLM412

Communication using BAdIs (4)

� BAdI QPL1_SUBSCR_ADDON: Assignment of Addon Data to anInspection Lot

� You can use additional subscreen areas to display any required data andchange the inspection lot data in the structure QALS_ADDON.

� BAdI QPRS_ADDON_TAB: Additional Tab Page for Sample

� An additional tab page can be activated in the transactions for thephysical-sample record (QPR1, QPR2, QPR3). This is dependent onthe screen control key for the physical-sample type. You can use anadditional subscreen area to display any required data and to changedata for the structure QPRS_ADDON in the physical-sample record.

� BAdI QEEM_SUBSCREEN_5000: Subscreen for Data in ResultsRecording

� In the transactions for results recording (create, change, display),additional data can be displayed in a subscreen of the header screen. Apushbutton can be used to call another function.

Communication using BAdIs (5)

� BAdI QE_RESULT_VALUATION: Valuation of Single Values

� You can program your own rules for the valuation of characteristicsand original values.

� BAdI QC_PROFILE_MAINTAIN: Business Add-In for CertificateProfile Maintenance

� You can maintain additional customer-specific fields for thecharacteristics.

� You can change the characteristic data in the certificate when you arecopying characteristics into the certificate profile.

� BAdI QB_Q_INFO_RECORD: Grouping Together of Q-Info Records

� The four reference fields in the quality info record, for example,material, plant, revision level and vendor, can be changed.

� BAdI QB_QM_SYSTEM_COMPARE: Comparison of QM Systems

� The required QM system in the procurement process can be checkedusing a program.

Using the BAdI QE_RESULT_VALUATION you can change a measured valuewhen comparing it to the specified tolerance limits (for example, reject if measuredvalue and tolerance limit are the same).

652 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 663: Plm412 en Col62 Fv Part a4

PLM412 Appendix 2: Technical Details

Using the BAdI QB_QM_SYSTEM_COMPARE, you can influence the check ofthe required QM system against the existing QM system. This BAdI is called justbefore the actual check and it allows you to change the following fields:

� Required QM system from the material master record� Existing QM system of vendor� Validity date of certification� Delivery date

2006/Q2 © 2006 SAP AG. All rights reserved. 653

Page 664: Plm412 en Col62 Fv Part a4

Appendix 2: Technical Details PLM412

654 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 665: Plm412 en Col62 Fv Part a4

Appendix 3Business Case

Figure 331: Task

Your company purchases a new material (see technical drawing) and inspects thismaterial at goods receipt for the purchase order.

2006/Q2 © 2006 SAP AG. All rights reserved. 655

Page 666: Plm412 en Col62 Fv Part a4

Appendix 3: Business Case PLM412

Create all of the QM data you need to inspect this material in accordance withyour quality requirements:

� All specifications made in the technical drawing are to be inspected.� If the surface is not smooth, a quality notification with the additional

information should be immediately created at goods receipt.� The quality level should always be updated based on the material/vendor

relationship.� The inspection scope should be variable. During a �normal� inspection, 10

parts should be inspected for a delivered quantity of 500 or less, 25 partsfor delivered quantities between 501 and 2000, and 35 parts for deliveredquantities over 2000 pieces. During a �reduced inspection�, only 7 parts,18 parts, and 22 parts are inspected for the same quantities. If 10 �normalinspections� are OK, the inspection scope can be reduced. After 20 OKinspections with a reduced inspection scope, the next 30 deliveries are notinspected. If a lot is rejected, a �normal inspection� is again carried out.

� If unexpected results are recorded at goods receipt for the ordered material,these are recorded as defects. Material-specific defect codes are used for this.

Hint: Supplementary Information: Hints

� Should the required specifications in the diagram be inspectioncharacteristics?

� Do you need an inspection plan or a material specification, or both?� How is the sample to be calculated?� How can you change the sample size and inspection frequency based

on past inspection results?

Business Case: Summary

� The inspection plan is used to specify the inspection operations, thecharacteristics to be inspected during each operation, and the test equipmentto be used.

656 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 667: Plm412 en Col62 Fv Part a4

Appendix 4Additional Information

Contents:

� Customer Enhancements� status management� Ease of Use� Follow-Up Actions� Evaluations� Archiving

Figure 332: Program Enhancements

2006/Q2 © 2006 SAP AG. All rights reserved. 657

Page 668: Plm412 en Col62 Fv Part a4

Appendix 4: Additional Information PLM412

You can carry out program enhancements at the following levels:

� In the ABAP module pool (program exit)� On the Graphical User Interface (GUI) (menu exit)� in screen flow logic� by inserting a subscreen in an area specified by SAP (screen exit)� by processing customer code that refers to a data element of a field on the

screen (field exit)

The following functions are available in the SAP System:

� ABAP statement CALL CUSTOMER-FUNCTION� Special function codes� CALL CUSTOMER-SUBSCREEN statement in the screen flow logic

SAP application programmers must reserve areas for program exits, menu exits,and screen exits. Field exits, on the other hand, do not need to be planned.

Figure 333: Customer Enhancement Project

SAP application programmers create SAP enhancements using program exits,menu exits, and screen exits. An administration function is available to the SAPprogrammer for this purpose (transaction code SMOD).

Customers can display a catalog of existing SAP enhancements and can combinethe required enhancements to create an enhancement project. The customer usesan administration function for this purpose (transaction code CMOD).

658 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 669: Plm412 en Col62 Fv Part a4

PLM412 Appendix 4: Additional Information

Figure 334: SAP Procedure

SAP application programmers plan possible application enhancements in theirapplications and define the required components. They then combine thesecomponents to create SAP enhancements.

Once they have created an SAP enhancement they document it in such a way thatthe customer can later implement the enhancement without extensive analysis ofthe program and screen sources.

2006/Q2 © 2006 SAP AG. All rights reserved. 659

Page 670: Plm412 en Col62 Fv Part a4

Appendix 4: Additional Information PLM412

Figure 335: Procedure at the Customer's Premises

Customers use the Project Management function to choose the SAP enhancementthat they want to implement. They then process the individual components (alsousing the Project Management function) and document the entire enhancementproject. Finally they activate the enhancement project (which in turn activatesall components).

Contents:

� Using Status Management� Defining and Creating a Status Profile� Assigning Status Profile to Object Types� Defining and Assigning User Status to Business Transactions� Selection profile

660 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 671: Plm412 en Col62 Fv Part a4

PLM412 Appendix 4: Additional Information

Figure 336: Using Status Management in QM

General status management is used in the following QM objects:

� Quality information record (supply relationship)� Inspection lot� Quality Certificate� Quality notification

Figure 337: Status

The current processing status of an object is documented using one or morestatuses.

2006/Q2 © 2006 SAP AG. All rights reserved. 661

Page 672: Plm412 en Col62 Fv Part a4

Appendix 4: Additional Information PLM412

A status is an indicator with the following functions:

� It indicates that a certain condition has been reached (for example, �Usagedecision made�).

� It influences the number of business transactions that can be performed.

If a business transaction is carried out, it can, in turn, set or delete one or morestatuses for the affected object.

You can set any number of statuses for an object.

Figure 338: status management

A system status is set by the system and informs the user that a certain functionhas been completed for an object. You cannot influence this status unless youcarry out a transaction that leads to a change in the system status.

A user status is defined by the user and can be set for a status object (such as aninspection lot) in addition to the system status.

You can use only one user status from the status profile (defined in Customizing)assigned to each status object.

You can extend control of the business transactions by the system status using theuser status. The user status can be set or deleted manually or through businesstransactions.

662 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 673: Plm412 en Col62 Fv Part a4

PLM412 Appendix 4: Additional Information

Figure 339: Defining a Status Profile

Figure 340: Create status profile

2006/Q2 © 2006 SAP AG. All rights reserved. 663

Page 674: Plm412 en Col62 Fv Part a4

Appendix 4: Additional Information PLM412

To create a status profile, proceed as follows:

1. Choose Edit→ New Entry.2. Enter any status profile name.3. Enter a descriptive text.4. Specify a maintenance language for the status profile. You can only make

changes and additions to the status profile in the maintenance language.These must then be translated into the required foreign languages. Thisensures that entries are complete and unique.

5. Choose Enter to add the new status profile to the list.6. Choose Save.

Figure 341: Assigning Status Profile to Object Types

To be able to use a status profile for objects of a certain object type, you have toassign the status to the affected object type:

1. On the screen Change Status Profile: Overview, place the cursor on thestatus profile that you want to assign to an object type.

2. Choose Goto→ Object types3. Select object types for which the status profile can be used.4. Choose Save.

664 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 675: Plm412 en Col62 Fv Part a4

PLM412 Appendix 4: Additional Information

Figure 342: Define user status

You must enter a four-character (maximum length) language-dependent ID toidentify each user status.

For each user status, you can enter the following:

1. Enter a status number in the Status number field. The status numberdetermines the order in which the status of a status profile can be set.

2. Enter a highest and lowest status number in the columns NONr and HONr.3. Enter a short text. The short text contains a short description of the status.4. Enter a long text for the user status. To do this, choose Goto -> Long text.5. Mark one user status as the initial status, if required. It is then set

automatically when an object is created. For each status profile, you maydefine only one status with a status number as the initial status, but anynumber of statuses without a status number.

6. In the Position column, define the position where the status is displayed inthe toolbar of the inspection lot. .

7. In the Priority column, define the priority of the user status if the sameposition is specified for more than one active status.

8. Save your entries.

2006/Q2 © 2006 SAP AG. All rights reserved. 665

Page 676: Plm412 en Col62 Fv Part a4

Appendix 4: Additional Information PLM412

Figure 343: Assigning User Status to Business Transactions

To assign business transactions to your user status, proceed as follows:

1. Position the cursor on the user status.2. Choose Goto→ Business transaction control.3. Choose Edit→ New Entries to display a list of the available business

transactions.4. Assign the appropriate transactions to your user status.5. By setting the indicators, you can activate the following fields for each

transaction: No influence, Allowed, Warning, Disalld.

The following prerequisites must be fulfilled before a business transactioncan be carried out:

� The transaction must be permitted by at least one active status.� The transaction must not be disallowed by any active status.

6. Using �Follow-up actions� you can determine how a specific transactionaffects the respective status when it is performed.

7. Save your entries.

666 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 677: Plm412 en Col62 Fv Part a4

PLM412 Appendix 4: Additional Information

Figure 344: Selection profile

You can use selection profiles to define the status combinations for selectingobjects (such as inspection lots). A selection profile is especially helpful if youwant to repeatedly select a large number of objects according to the same selectioncriteria.

You can specify a system status as well as a user status in the selection profile.If you also want to select objects according to user status, you must specify thecorresponding status profile.

The selection criteria are evaluated top-down. The following rules apply:

� Several consecutive lines linked by OR are combined to form a block andare evaluated together. This block must fulfill at least one of the selectioncriteria.

AND links these blocks or individual criteria. All blocks or individualcriteria linked by AND must be fulfilled. An order is eliminated from theevaluation if even one block or individual criterion is not fulfilled.

OR link is stronger than AND link

For greater efficiency, criteria that greatly limit the selection should be put atthe beginning of the selection profile.

Contents:

� Field Selection� Variable lists

2006/Q2 © 2006 SAP AG. All rights reserved. 667

Page 678: Plm412 en Col62 Fv Part a4

Appendix 4: Additional Information PLM412

Figure 345: Field Selection

Determine the name of the program, to which the screen belongs. To do this, callup the screen in question and choose System→ Status.

To find out which customer-defined field control is planned for which screengroups in a module pool, enter the name of the module pool in the maintenancefunction (transaction SFAC) and choose Display. The system displays a list ofall the screen groups. You can display a list of modifiable fields for each screengroup in the list.

For the modifiable fields, you use indicators to define how each field is displayedon the screen.

668 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 679: Plm412 en Col62 Fv Part a4

PLM412 Appendix 4: Additional Information

Figure 346: Variable Lists (Basics)

You define list variants in two steps:

1. 1. Field selection: In this step, you define the fields and the sequence for thelist display. You choose from a selection of fields proposed by the system.You can number the selected fields, or identify them as hidden.

This field selection has an automatic transport link. Users can also createtheir own selection list from within the application transaction. Thisuser-specific field selection does not belong to Customizing and does nothave a transport link. If users do not define their own field selection, thefields that are selected in this step are displayed.

2. 2. Object selection: You define the selection criteria used to selectthe objects for the list. For each function (transaction) that is directlyexecutable from this list, you can define exactly one general variant withthe accompanying selection criteria. The system saves this general variantas SAP_TCODE_xxxx. (xxxx is the transaction code that generates therespective list.) These general variants have an automatic transport link. Inaddition to the general variant, you can also define a user-specific variantfor each executable function. The system saves this variant as U_<username>. You can also define any number of other variants for each executablefunction and save them under any name (from within the application).

2006/Q2 © 2006 SAP AG. All rights reserved. 669

Page 680: Plm412 en Col62 Fv Part a4

Appendix 4: Additional Information PLM412

Figure 347: Variable Lists (Field Selection)

You can change the list display using display variants.

The following functions are available:

� You can limit the list of hidden fields according to the criteria, as required(field group).

� You can hide or show all fields or individual fields.� Using Sort in ascending order or Sort in descending order, you can sort the

hidden fields according to column content.� The order of the columns in the list is defined by the item number in the

Item field.� In the Length column, you can change the required length of a field if this

should differ from the standard setting.� If it is possible to calculate totals and subtotals in a column, in the display

fields beneath Total you can define whether totals and subtotals are to beshown in the display variant above this Total column.

� You can use a clipboard to cut a field from the display fields or the hiddenfields and paste it in the required place in the display fields.

� The columns can be grouped together in up to three rows.

670 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 681: Plm412 en Col62 Fv Part a4

PLM412 Appendix 4: Additional Information

Figure 348: Variable Lists (Object Selection)

� Type

The Type field shows whether the type is a parameter (P) or a select option(S).

� P (Protect field) selected:

The corresponding selection criterion cannot be entered at the start of theprogram using this variant.

� I (Hide field) selected:

The corresponding selection criterion is not displayed at the start of theprogram using this variant. However, the selection criterion can still besupplied with values in the variant.

� N (Hide field until)� L (Selection variable) selected:

The selection criterion is supplied with values from the variant variables atthe start of the program. To select variant variables, choose SELECTIONVARIABLES.

� P (Save field without values) selected:

The value of the corresponding selection criterion is not changed in theprogram at the start using the variant or by getting a variant.

� L (Switch SPA/GPA off)� O (Required fields)

2006/Q2 © 2006 SAP AG. All rights reserved. 671

Page 682: Plm412 en Col62 Fv Part a4

Appendix 4: Additional Information PLM412

Contents:

� Defining follow-up actions� Status for follow-up actions� Follow-up action and business process

� ABAP Workbench

� Create function module� Customizing

� Maintain the follow-up action table� If necessary, assign business transactions

In QM, there are follow-up actions for the usage decision and for tasks withinthe quality notification.

When the usage decision is made, a follow-up action is assigned to a code duringmaintenance of the selected set code.

For a quality notification, a follow-up action is assigned to a code duringmaintenance of the task catalog.

Figure 349: Follow-Up Actions: Setting the User Status

A predefined business transaction can be assigned to a follow-up action. Thisinvolves transactions QM90 to QM99 when the usage decision is made. For thetasks, this includes transactions QN90 to QN99.

Statuses can be assigned to these business transactions.

672 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 683: Plm412 en Col62 Fv Part a4

PLM412 Appendix 4: Additional Information

The statuses are set when you execute such a transaction.

Figure 350: Follow-Up Actions and Business Transactions Operation

Contents:

� Logical Databases� ALV in list output� Ad Hoc queries using QuickView� Comparison of SAP Query and QuickView

2006/Q2 © 2006 SAP AG. All rights reserved. 673

Page 684: Plm412 en Col62 Fv Part a4

Appendix 4: Additional Information PLM412

Figure 351: Generating Lists Using the LDB

Usually, data that is to be displayed in list form is read from the database.

You can use OPEN SQL or NATIVE SQL instructions to read data from thedatabase.

Instead of having to program access to the database yourself, you can use logicaldatabases. The logical database retrieves the data records and makes themavailable to the ABAP Program.

Figure 352: Logical Database: Overview

674 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 685: Plm412 en Col62 Fv Part a4

PLM412 Appendix 4: Additional Information

An ABAP program that reads data for programs of type 1 from the database anddisplays them as records, is known as a logical database.

During this process, the sequence in which the data is supplied to the programsis determined by a hierarchical structure. In addition, a logical database makes aselection screen available for the programs, (checking the user entries and errordialog). This screen can be configured in the programs.

In release 4.0, there are approximately 200 logical databases in the standardsystem. As a part of namespace enhancement, a logical database's name has beenextended to 20 characters (with a namespace prefix of a maximum of 10 places).You no longer need enter an application ID for the logical database in release 4.0.

Figure 353: What Is the ALV Classic?

� ALV stands for the ABAP List Viewer� ALV Classic is a collective term for several function modules in the function

group SALV� Tool for the standardized output of:

� Simple lists� Hierarchically-sequential lists with two hierarchy levels

You can use ALV function modules to create standardized lists with genericfunctions.

2006/Q2 © 2006 SAP AG. All rights reserved. 675

Page 686: Plm412 en Col62 Fv Part a4

Appendix 4: Additional Information PLM412

Since release 4.6C, there has been control-based further development of ALV -ALV grid control.

� Data is displayed in simple lists by calling up the function modulereuse_alv_list_display

� Transfer parameters

� Internal data table for list output� Field descriptions for data tables (field catalog)� General descriptions for list layout (optional)

� ALV sets its own status� Using the callback technique, the standard ALV functions can be flexibly

combined with application-specific logic.

The output of simple lists is triggered by the function modulereuse_alv_list_display. This function module issues an internal table with astructure in the form of edited lists with one or more lines.

All changes that are later made to the list refer directly to the internal output table.For example, the sorting of lists causes the transferred, internal output tables tobe re-sorted, since these are transferred by reference.

The module requires either a field catalog or an internal table with a dictionarystructure, as well as descriptions of the list layout that differ from the standard(optional).

After the list is displayed (ALV sets its own GUI status as a default setting), all thestandard operations can be performed.

You can make changes to the standard system to meet your requirements. Variousfunction modules are available to process a list as required. Some of them areavailable for the individual setup of the list display, others are explicitly called bythe ABAP List Viewer.

The procedure used for hierarchically-sequential lists corresponds to the procedureused for simple lists.

676 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 687: Plm412 en Col62 Fv Part a4

PLM412 Appendix 4: Additional Information

Figure 354: Standard Call for ALV

This slide describes the basic process for creating a list. Descriptions of data in theinternal table can be made either using the field catalog or a dictionary structure.You can also use a dictionary structure to describe data and then enter formattingoptions using the field catalog.

Figure 355: QuickViewer: Principle

The QuickViewer is a tool developed in 4.6A, which is used to create ad hocreports. You start the QuickViewer by entering transaction SQV1.

For example, the QuickViewer can use a database table or also a database viewas a data source. A list can be created from the fields of the named data source.There are two modes available for this: the basis and the layout mode.

2006/Q2 © 2006 SAP AG. All rights reserved. 677

Page 688: Plm412 en Col62 Fv Part a4

Appendix 4: Additional Information PLM412

The QuickViewer includes a link, for example, to the EIS, ABC analysis, or ALVgrid control. The list can also be edited further in external programs, such asMicrosoft Word.

The created list can be saved and displayed again in the QuickViewer. Theselection criteria can be stored for the saved list and can be called up at any time.

Figure 356: QuickViewer: Initial Screen

Each user creates their own QuickViews that are not visible to other users. Asa result, the QuickViews of other users cannot be copied. You can change aQuickView into a SAP Query, if the QuickView uses a functional area from thestandard area as a data source. The query is then visible to the user group.

QuickViews are not linked to correction and transport systems.

678 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 689: Plm412 en Col62 Fv Part a4

PLM412 Appendix 4: Additional Information

Figure 357: Creating a QuickView

To create a QuickView, you must specify a data source. You can specify databasetables, database views, logical databases, table joins, or functional areas for theSAP Query as data sources. The functional area must be in the standard area(client-dependent).

You have access to the specified data quantity, but you cannot enhance this byadditional fields.

Figure 358: Join Definition: Graphic

If you specify a table join as a data source, then you must first define this joinbefore you can create the list in the QuickViewer.

2006/Q2 © 2006 SAP AG. All rights reserved. 679

Page 690: Plm412 en Col62 Fv Part a4

Appendix 4: Additional Information PLM412

The table join is defined graphically. You must specify links between the tables.The system can also make proposals for you. This involves dictionary informationbeing evaluated.

The result quantity is determined by deciding for an inner or left outer join logic.For example, if you only want to print the inspection lots from table QALS in alist, for which there are entries in table QAVE, this counts as an inner join logic.However, if you want to print all inspection lots regardless of whether there areentries in table QALS, you link both tables using a left outer join logic. In thisexample, the left table is QALS.

Alias tables enable you to use the same (database) table several times whendefining the join.

Figure 359: Basis Mode: Basic Structure

The screen for the basis mode is split into 4 areas. The available fields (datasource) are displayed in the upper left corner in the form of a tree. Furtherinformation on usage is displayed in the lower left corner of the screen. You canmaintain the title and comments, and control output (list, Excel) in the upper rightscreen area. In this area, you can control the structure of the list, define the sortsequence, and enter selection criteria. You can switch to the online documentationin the lower right window.

680 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 691: Plm412 en Col62 Fv Part a4

PLM412 Appendix 4: Additional Information

Figure 360: Creating a QuickView in Basis Mode

You create the QuickView using two table controls. You select the required listfields in the right table control and transfer them to the left table control (Fieldsin the list) using the transfer functions. You also control in the left table control(Fields in list) how many lines should be entered in the list (Insert lines function).

You do the same for the sort and selection fields: You select the required fields inthe left table control and copy them to the right control.

� Ad hoc reports for a user� Each user creates their own QuickViews, which are not visible to other users� Working with available data quantities� No administrative costs (user group, functional area)� QuickView can be changed into a SAP Query� Link to internal (EIS, ABC, ALV) and external applications� Limited functions in comparison to SAP Query� No transport

2006/Q2 © 2006 SAP AG. All rights reserved. 681

Page 692: Plm412 en Col62 Fv Part a4

Appendix 4: Additional Information PLM412

Figure 361: Overview: Program and Query

If you create a list using a program (category 1), the data to be processed is, forexample, created using a logical database, processed in the program, and thenissued in a list.

A query is an evaluation of data, which a user can create using the the SAP Querytool without programming knowledge.

The query takes you through a sequence of screens in which the line and listlayout is described. From release 4.6A, you can graphically create query listsusing the query painter.

When the query is started, a program that corresponds to the listdefinition is automatically generated. This program reads and processesthe required data, and issues it in the list. The program has the nameAQmmbbbbbbbbbbbbqqqqqqqqqqqqqq. You can display the program name bychoosing the menu sequence AQL-1.

mm - coded client (standard area) or ZZ (global area)

bbbbbbbbbbbb - user group name (12 characters)

qqqqqqqqqqqqqq - query name (14 characters)

Spaces in the program name are replaced by '='.

682 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 693: Plm412 en Col62 Fv Part a4

PLM412 Appendix 4: Additional Information

Figure 362: Organization in the Query

The administrative tasks in the query environment include the creation of InfoSetsand user groups, and the assignment of the InfoSets to the user groups.

The InfoSet determines to which database tables or fields in these tables the queryis referenced. InfoSets are often based on logical databases.

Users may only create or start queries if they are assigned to at least one usergroup. A user can be assigned to several user groups. The users in one user groupall have the same authorizations.

The InfoSets are assigned to a user group, to which the users in this group haveaccess.

An InfoSet can be assigned to several user groups.

An InfoSet can be assigned to several user groups.

Queries are always created for a specific user group using a certain InfoSet. Auser in a user group has access to all queries that are created in that user group.

2006/Q2 © 2006 SAP AG. All rights reserved. 683

Page 694: Plm412 en Col62 Fv Part a4

Appendix 4: Additional Information PLM412

Figure 363: Creating a Query

If you are assigned to several user groups, you can change between these usergroups.

A query is always created using a specific InfoSet. This InfoSet area must beassigned to the user group in which the query is created.

As a rule, you can access all queries that are assigned to your user group.

If you are authorized to define a query using an InfoSet, you can list all the queriesfor this InfoSet.

A query can only be copied from another user group into your own user group, ifthe InfoSet for the query to be copied is also assigned to your own user group.

To create user groups, use transaction SQ03. To create InfoSets, use transactionSQ02. To create queries, use transaction SQ01.

684 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 695: Plm412 en Col62 Fv Part a4

PLM412 Appendix 4: Additional Information

Figure 364: Comparison of SAP Query and QuickView

Contents:

� Archiving process� Archiving object� Customizing� Organizing the Archiving of QM Data

� Storing data records from database tables to reduce the number of availabledatabase tables in the system

� Reasons for data archiving

� Determined by the system

Memory space problems, performance, difficult database administration

� Legal specifications and operational requirements

Country-dependent storage requirements, data must be available toexternal auditors, potential reusability of data

� Data deleted as a record from the tables� Access to archived data controlled by the application

2006/Q2 © 2006 SAP AG. All rights reserved. 685

Page 696: Plm412 en Col62 Fv Part a4

Appendix 4: Additional Information PLM412

ReorganizationThe term �reorganization� is from the time of R/2, when data wasdownloaded and then uploaded to optimize the physical distribution of dataon the hard disk. During this operation, data that was no longer neededcould be archived and deleted.

Backup/RestoreBy �backup� we mean a backup of the database contents in case ofbreakdown. This enables you to restore the database status to the currentstatus before the breakdown. As a rule, backups are run at fixed intervalsaccording to a set procedure. The transfer of data back to the system isknown as the 'restore' procedure.

Archiving Using SAP ArchiveLinkDuring archiving, scanned-in, incoming documents are archived in externalsystems using the SAP ArchiveLink. This is the same for outgoingdocuments created in the SAP System (for example, quality certificates)and print lists. You can display the archived documents and lists using theSAP ArchiveLink.In the data archiving function, there is an interface to the SAPArchiveLink that you can use to store archive files in an external archive.

Figure 365: Server for Archiving and Deletion Jobs

The archiving program always runs in the background, primarily on a backgroundserver that is also a database server.

686 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 697: Plm412 en Col62 Fv Part a4

PLM412 Appendix 4: Additional Information

The deletion programs look for the next available background server. You musttherefore always make sure that all application servers also have access to theused file systems.

From release 4.5A, you can specify the server, on which the background jobsshould be run.

Figure 366: Archiving: Step 1 - Archive

In the first step, the archiving program creates an (initial) archive file.

The system then reads the data to be archived from the database as a backgroundjob and copies it to the archive file. This operation continues until one of thefollowing events occurs:

1. Archiving is complete.2. Archiving is not yet complete, but the archive file has reached the size

specified in Customizing.3. Archiving is not yet complete, but the archive file already contains the

number of archiving objects specified in Customizing.

Data is stored in the archive file in a format defined by SAP.

Length Table VBAK Data Table VBAP Data ......

2006/Q2 © 2006 SAP AG. All rights reserved. 687

Page 698: Plm412 en Col62 Fv Part a4

Appendix 4: Additional Information PLM412

Figure 367: Archiving: Step 2 - Delete

After the first archive file has been closed, archive management opens a secondarchive file and proceeds with the archiving operation. At the same time, thesystem starts another program, which reads the archived records and deletesthem in the database.

This procedure ensures that only correctly archived records are deleted.

When the last archive file is closed, a deletion program is also run for the file.

The diagram shows that several deletion programs can run in parallel for thecreated archive files.

Since the archiving program does not alter any information contained in thedatabase, (unlike the deletion program), the archiving program prepares archivefiles quicker than they can be processed by the corresponding deletion program.(This is, of course, dependent on the files to be archived.)

This has a positive effect on the total run time, since the database is used moreproductively.

688 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 699: Plm412 en Col62 Fv Part a4

PLM412 Appendix 4: Additional Information

Figure 368: Archiving: Step 3 - Options for Storing Archived Information

Archive files whose data has been deleted in the database can be stored in variousways.

Apart from using magnetic tape, the most frequently used methods are HSMSystems and archiving in an external system using the SAP ArchiveLink.

2006/Q2 © 2006 SAP AG. All rights reserved. 689

Page 700: Plm412 en Col62 Fv Part a4

Appendix 4: Additional Information PLM412

Figure 369: Archiving Process

� Description of which data should be archived and how it is to be archived(data model).

� Data is bundled into a self-contained business object, independent of theconditions at the time of archiving.

� Programs for creating archive files and deleting data in the database arecontained in these objects.

� Further programs are available as required (creating/removing indices,uploading, evaluating).

� Customer settings are assigned to each archiving object.� Accessed from applications- you can define customer-specific archiving

objects for Z tables.

Determining tables for an archiving object

Up to Release 3.1G: Transaction AOBJ, definition of structure

As of Release 3.1G: Transaction SARA, menu option - database tables

690 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 701: Plm412 en Col62 Fv Part a4

PLM412 Appendix 4: Additional Information

Figure 370: Archiving Objects in Transaction SARA

All archiving processes are carried out in the archive management function.Application data that logically belongs together is grouped in an archiving object.By entering the name of the archiving object, you can access the archiving sessionfor this archiving object in the archive management function.

You can schedule the background job for the archiving sessions directly usingarchive management. Alternatively, the jobs can also be scheduled within theapplication.

The steps involved in archiving differ according to the archiving object.

The initial run, postprocessing, and reloading are not supported by all archivingobjects.

When dealing with archiving objects which require a usage, you have to triggerthese activities manually.

From release 4.0, postprocessing programs can be started automatically.

You can use archive management to control access to an archive file and if youmanage the archive files manually, to also control the data medium, in which thearchive files are stored.

You can use the Archive Information System (transaction SARI) to evaluatearchiving sessions.

Archiving Objects in QM� QM_CHARACT QM Master Inspection Characs� QM_CONTROL Movement data for quality inspections� QM_METHOD QM inspection methods

2006/Q2 © 2006 SAP AG. All rights reserved. 691

Page 702: Plm412 en Col62 Fv Part a4

Appendix 4: Additional Information PLM412

� QM_PLAN QM inspection plan� QM_QMEL Quality notification� QM_SAMPLE Physical samples

� Definition of the logical file names and the storage paths

Transaction SARA, up to 4.0 transaction FILE

� Definition of logical file names for all systems� Definition of logical file paths� Definition of physical file paths

� Settings for general archiving object

Transaction SARA

� Definition of the logical file name� Size of the archiving file� Settings for the deletion program� Variant specifications

� Customizing archiving in external archives� Object-specific Customizing in the application

In Customizing for archive objects, the logical file name is the name, with whichthe archive file is to be created on the hard disk.

In the transaction FILE, a logical path is assigned to this logical file name.

Similarly, the logical path in the transaction FILE refers to a physical path and isdependent on the operation system. In the transaction FILE, you must enter thesyntax group of the operation system that is being used.

If an archive file is to be stored in an external archive, the physical path mustcorrespond to the exchange index between the SAP System and the archive (basicpath in the archive definition).

The following slide shows how logical file names/logical file paths and physicalfile paths interact. It uses the example of an archiving object, whose files are to bestored in an external archive.

692 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 703: Plm412 en Col62 Fv Part a4

PLM412 Appendix 4: Additional Information

Figure 371: Organizing the Archiving of QM Master Data (1)

� Prerequisites for deletion:

� You must mark task lists with a deletion flag in the task list header.� There should be no where-used lists for master inspection characteristics

and methods. They should also have status 4. You can change the statusof historical versions for master records to status 4 within Archiving.

� The archiving process:

� In the first step, the system automatically changes the status of themaster records from 3 (locked) to 4 (can be archived). This step,however, only affects historical versions of the master records; thecurrent versions can only be given status 4 manually.

� In the second step, the master records are archived and deleted.

2006/Q2 © 2006 SAP AG. All rights reserved. 693

Page 704: Plm412 en Col62 Fv Part a4

Appendix 4: Additional Information PLM412

Figure 372: Organizing the Archiving of QM Movement Data

Figure 373: Archiving Session Checklist

694 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 705: Plm412 en Col62 Fv Part a4

GlossaryBusiness Package

Business packages are portal-based solutions that provide you with theapplications, information and services that you require to facilitate a quickintroduction to the SAP NetWeaver Portal and connection to back-endsystems.

ESAEnterprise Service Architecture (provision of application functions in theform of enterprise services). These are combinable Web services that canbe used in business.

mySAP Business SuiteA complete package of open business applications that connect all of therelevant people, information and processes to each other and therefore makeyour business relationships more effective.

SAP NetWeaverSAP NetWeaver is SAP's integration and application platform. It is thetechnological basis for almost all SAP solutions.

SAP NetWeaver Business IntelligenceSAP NetWeaver Business Intelligence provides comprehensive analyticalfunctions with an installable business content (optional).

SAP NetWeaver MDMSAP Master Data Management provides functions necessary for theintegrated central management of master data within a company.

SAP NetWeaver MobileSAP NetWeaver Mobile is the universal platform for business mobility. Itsupports SAP solutions for mobile business.

TCOTotal Cost of Ownership

2006/Q2 © 2006 SAP AG. All rights reserved. 695

Page 706: Plm412 en Col62 Fv Part a4

Glossary PLM412

696 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 707: Plm412 en Col62 Fv Part a4

IndexNumerics/Symbols8D report, 396Aaccount assignment objects,525

action box, 379Action Box, 465�466Action Log, 497Actions, 366ALE, 132alternative units of measure,347

application log, 290appraisal costs, 518approval requirements, 236automatic usage decision, 344Bbatch status, 346buyer�s negotiation sheet, 395Ccalculated characteristic, 186Calibration inspection, 173catalog profile, 116, 118Catalog profile, 392�393,460�461

Catalog Profile, 319catalog types, 104, 459Catalog Types, 103change documents, 208, 285change master record, 235change number, 234characteristic, 429conditional, 187

characteristic inspection, 79characteristic mapping, 288characteristic value, 429characteristic values, 205

characteristics, 583additional, 284

Characteristics, 586Class, 428classification system, 367Classification system,428�429

client 000, 463code group, 116code groups, 105, 188codes, 105collective usage decision, 343Confirmation profile, 320,392

confirmation transaction, 426Control Chart, 281control charts, 566, 588control indicator, 79Copy Inspection Resultsfunction, 286

copy modelcomplete, 185incomplete, 185

cost reports, 526customer analysis, 585Customer complaint, 20, 404,406, 409

DData Transfer Workbench,209

deadline monitoring, 546defect codes, 317, 394defect costs, 518, 524defect item, 365, 428defects recording, 9Defects Recording, 317�318,323�325, 390, 392, 394,437�439

delivery, 407

2006/Q2 © 2006 SAP AG. All rights reserved. 697

Page 708: Plm412 en Col62 Fv Part a4

Index PLM412

dependent follow-up function,468

digital signature, 293DIN ISO 2859-1, 38DIN ISO 286-2, 82DIN ISO 3951, 38display variants, 562document, 499Document ManagementSystem, 128, 499

Dynamic modification, 34dynamic modification at lotcreation, 189

Dynamic modification atusage decision, 190

dynamic modification criteria,52

dynamic modification level,189

Dynamic Modification Rule,51

Dynamic modification rules,188

EEarly Warning System, 580,586

engineering change request,235

Engineering Workbench,220�221

Equipment, 172evaluations, 9event linkage, 549Event-Controlled Processes, 3exception, 581exception analysis, 580Ffaulty delivery, 376FLEX, 246Flexible InspectionSpecifications, 243

follow-up action, 498function module, 467function modules, 498

Ggeneral QM order, 519goods receipt inspection, 390Group, 165group counter, 165Hheader level, 463histogram, 563History Management, 80Iimmediate tasks, 409individual QM order, 519initial data transfer, 209initial screen, 378, 407, 426inspection characteristic, 77inspection characteristic level,191

inspection characteristicspecificationsspecific, 184

inspection characteristics,184, 191

inspection history, 563Inspection instruction, 10, 12inspection lot creation, 9inspection lot data record,9�10

Inspection lot origin, 32inspection method, 126�127,129

Inspection method, 184Inspection Methods, 188Inspection plan, 238Inspection Plan, 164inspection plan header, 165inspection processing, 464Inspection Processing, 4inspection report, 294Inspection results, 4inspection setup, 30, 65inspection specifications, 9inspection stage change, 51Inspection Type, 31�32internal problem notification,425

698 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 709: Plm412 en Col62 Fv Part a4

PLM412 Index

Internet, 292Internet Transaction Server(ITS), 406

item level, 463KKey figures, 583, 586Mmaintenance plan, 173mass maintenance, 65master inspectioncharacteristic, 77, 129

Master inspectioncharacteristic, 188

master recipes, 240Material Analysis, 585material document, 378Material specification, 238Material Specification,136�137

material-task list assignment,203

multistep tasks, 549mySAP Business Suite, 612Nnotification category,360�361, 457

notification item, 365notification list, 464notification origin, 361Notification origin, 458notification processing, 427,499

notification systems, 360notification type, 118, 321,361, 462, 487

Notification Type, 458�460notification types, 360OObject, 428object types, 235Operations, 166order type, 526

Ppartner function, 364partner type, 364posting proposal, 341print control, 472Print Control, 471Problem processing, 17process-optimized resultsrecording, 281

Processing status, 276product structure, 138product structure browser,206

production order, 426production resources/tools,171

purchasing document, 378QQM information system, 578,584

QM order, 517�518QM-IDI Interface, 295QM-STI Interface, 587QMIS, 584qualitative, 77quality costs, 526quality improvement, 19quality level, 51quality notification, 377Quality notification, 19, 461quality notification type, 118,460

Quality notifications, 18, 560Quality Score, 345quantitative, 77Rrecording configuration, 278Reference characteristic, 185reference operation set, 205related notifications, 464repair order, 409�410report type, 118Report type, 320, 392�393,460

2006/Q2 © 2006 SAP AG. All rights reserved. 699

Page 710: Plm412 en Col62 Fv Part a4

Index PLM412

request to deviate fromspecification, 428

response profile, 496Results, 4results data origin, 288results history, 588results recording, 9, 318, 588mobile, 290

Results Recording, 272, 274return, 409return delivery, 380, 410returns and repairs processing,411

Returns and RepairsProcessing, 409

routings, 240run chart, 563Ssales order, 407sales summary, 408sample determination, 9Sample Determination, 34�35Sample size, 36Sample-drawing instruction,10, 12

Sampling Procedure, 36Sampling scheme, 38Sampling tables, 38sampling type, 37SAP Business Workflow, 545SAP NetWeaver, 615screen groups, 500screens, 462Selected set, 113, 115selected sets, 340selection variant, 561service order, 411service profile, 496shop papers, 472skip, 51source inspection lot, 287

SPC Functions, 559stage change, 50Standard analyses, 579standard info structures, 582status management, 367, 486Status profile, 486�487stock postings, 339, 346system status, 485TTab, 462tab pages, 462target inspection lot, 288Task List Header, 165task list headers, 223test equipment, 171Test Equipment, 166tolerance key, 82tolerance specifications, 280transfer log, 290transfer posting, 379UUD codes, 337usage decision, 9, 337Usage Decision, 4User status, 485, 487Vvalidity status, 81valuation mode, 36�37, 280vendor analysis, 585vendor complaint, 381vendor evaluation, 395�396Wwork area, 221work center, 169work centers, 167work environment, 221workflow scenario, 546workflow template, 547worklists, 560

700 © 2006 SAP AG. All rights reserved. 2006/Q2

Page 711: Plm412 en Col62 Fv Part a4

FeedbackSAP AG has made every effort in the preparation of this course to ensure theaccuracy and completeness of the materials. If you have any corrections orsuggestions for improvement, please record them in the appropriate place in thecourse evaluation.

2006/Q2 © 2006 SAP AG. All rights reserved. 701