Plm412 en Col95
Short Description
Download Plm412 en Col95...
Description
PLM412 Quality Planning and Inspection SAP ERP - Operations Support
Date Training Center Instructors
Education Website
Participant Handbook Course Version: 95 Course Duration: 5 Day(s) Material Number: 50101093
An SAP course - use it to learn, reference it for work
Copyright Copyright © 2011 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Trademarks •
Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered 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 trademarks of Citrix Systems, Inc.
•
HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide 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.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies.
Disclaimer THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE, INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTS CONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANY KIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOST PROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDED SOFTWARE COMPONENTS.
g201112112225
About This Handbook This handbook is intended to complement the instructor-led presentation of this course, and serve as a source of reference. It is not suitable for self-study.
Typographic Conventions American English is the standard used in this handbook. The following typographic conventions are also used. Type Style
Description
Example text
Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths, and options. Also used for cross-references to other documentation both internal and external.
2011
Example text
Emphasized words or phrases in body text, titles of graphics, and tables
EXAMPLE TEXT
Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example SELECT and INCLUDE.
Example text
Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, and passages of the source text of a program.
Example text
Exact user entry. These are words and characters that you enter in the system exactly as they appear in the documentation.
Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.
© 2011 SAP AG. All rights reserved.
iii
About This Handbook
PLM412
Icons in Body Text The 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's presentation.
iv
© 2011 SAP AG. All rights reserved.
2011
Contents Course Overview .......................................................... ix Course Goals ........................................................... ix Course Objectives ..................................................... ix
Unit 1: QM Processes in the Logistics Processes ................. 1 Positioning of Quality Management ..................................2 Inspection Process Flow in Quality Management - Overview.....7 Problem Processing with Quality Notifications - Overview ...... 17
Unit 2: Basic Data in Quality Management......................... 27 Material Master and Inspection Settings ........................... 29 Sample Determination................................................ 35 Dynamic Modification................................................. 50 Inspection Setup - Mass Maintenance ............................. 64 Master inspection characteristic .................................... 76 Input Processing for Measured Values............................. 98 Code Groups and Codes ...........................................104 Selected Sets and Catalog Profile ................................. 114 Inspection method ...................................................128 Distributing QM Basic Data .........................................134 Material Specification................................................138
Unit 3: Inspection Planning........................................... 163 The Inspection Plan .................................................165 Test Equipment.......................................................173 Inspection Characteristics in the Inspection Plan................185 Reference Operation Set and Product Structure ................204 Engineering Workbench.............................................226 Engineering change management.................................239 Task List - Material Specification...................................245 Flexible Inspection Specifications .................................249 Multiple Specifications - Overview (Optional) ....................255
Unit 4: Results Recording ............................................ 279 Recording and Valuating Inspection Results .....................280
Unit 5: Defects Recording ............................................ 325 Defects Recording in Inspection Processing .....................326
2011
© 2011 SAP AG. All rights reserved.
v
Contents
PLM412
Unit 6: Usage Decision ................................................ 345 Inspection Completion with the Usage Decision.................346
Unit 7: Definition and Structure of Notifications ................ 367 Definition and Structure of Notifications...........................368
Unit 8: Quality Notifications in Logistics .......................... 387 Quality Notifications at Goods Receipt............................388 Quality Inspection and Defect Notification at Goods Receipt ..401 Customer Complaints ...............................................415
Unit 9: Quality Notifications in Production ....................... 435 Quality Notification During Production ............................436 Quality Inspections and Defect Notifications During Production.........................................................447
Unit 10: General Functions of Quality Notifications ............ 463 Customizing Settings for Notifications.............................464 Status Management for Notifications..............................494 Other General Functions for Notifications ........................505
Unit 11: Quality-related Costs and QM Orders ................... 525 QM order ..............................................................526
Unit 12: SAP Business Workflow in QM - Overview ............ 553 SAP Business Workflow in QM - Overview.......................554
Unit 13: Evaluations .................................................... 567 Evaluations Based on Original Documents.......................568 Standard analyses ...................................................589
Unit 14: Enterprise Portals – Optional Unit ....................... 615 Business Drivers for Portals ........................................616 SAP Product Overview and Release Strategy ...................622 SAP NetWeaver......................................................636 Introduction to the SAP NetWeaver Portal .......................645
vi
© 2011 SAP AG. All rights reserved.
2011
PLM412
Contents
Appendix 1: Vendor Evaluation Appendix 2: Technical Details Appendix 3: Business C
ase
................................... 655 .................................... 661
....................................... 677
Appendix 4: Additional Information
............................. 679
Glossary................................................................... 717 Index ....................................................................... 719
2011
© 2011 SAP AG. All rights reserved.
vii
Contents
viii
PLM412
© 2011 SAP AG. All rights reserved.
2011
Course Overview This course covers the processing of QM-specific basic data and provides details about inspection planning and how to carry out an inspection. You will learn how basic data is used in different task lists and see the effect of the basic data on the inspection process. In addition, this course describes the possible uses of quality notifications and the different evaluation and reporting possibilities in quality management. The SAP Quality Management applications are part of the SAP ERP (Enterprise Resource Planning) and SAP PLM (Product Lifecycle Management) solutions. The information in this course refers to the SAP ERP Central Component 6.0 software component, SAP Enhancement Package 5.
Target Audience This course is intended for the following audiences: • •
Members of the project team People in the department
Course Prerequisites Required Knowledge • •
Basic knowledge of quality management PLM400 (Quality Management)
Course Goals This 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 Objectives After completing this course, you will be able to: • •
2011
Use the QM master data to plan and carry out inspections Use quality notifications in logistics processes.
© 2011 SAP AG. All rights reserved.
ix
Course Overview
PLM412
•
Use the different evaluation possibilities in quality management.
SAP Software Component Information The information in this course pertains to the following SAP Software Components and releases: •
x
SAP ERP Central Component
© 2011 SAP AG. All rights reserved.
2011
Unit 1 QM Processes in the Logistics Processes Unit Overview This chapter deals with the general position of quality management in the SAP environment. The general QM processes in the logistics processes are considered using simple examples. The important objects inspection lot and quality notification are then briefly examined.
Unit Objectives After 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 provided by the link to the Workflow.
Unit Contents Lesson: Positioning of Quality Management ...................................2 Lesson: Inspection Process Flow in Quality Management - Overview .....7 Exercise 1: Inspection Lot - Overview .................................... 13 Lesson: Problem Processing with Quality Notifications - Overview....... 17
2011
© 2011 SAP AG. All rights reserved.
1
Unit 1: QM Processes in the Logistics Processes
PLM412
Lesson: Positioning of Quality Management Lesson Overview This lesson deals with the general positioning of quality management in the processes of a company.
Lesson Objectives After 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 planning Master data for inspection planning, material specifications Quality inspection Inspection lots, inspection results, and defects recording Usage decisions and follow-up actions
2
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Positioning of Quality Management
Quality certificate Certificate receipt, certificate issue, certificate transfer Quality notifications Internal/external problem solving Quality control SPC and control charts QM information system, key figures Audit Management Audit, Question List, Corrective and Preventive Actions, Audit Plan Test equipment management Test equipment monitoring Stability study Stability 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 receipt inspections) 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 and processed in a quality notification.
2011
© 2011 SAP AG. All rights reserved.
3
Unit 1: QM Processes in the Logistics Processes
PLM412
In addition, you can monitor critical values using the information system and if necessary, trigger tasks via the Workflow. The data collected in planned and event-controlled processes (for example, the number of complaints) is evaluated in the information system.
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 all the 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 on the results of the inspection.
4
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Positioning of Quality Management
Figure 4: Event-Controlled Processes
In addition to the standard processes, there are event-controlled processes in the logistics supply chain, which are triggered when problems occur. You record, analyze, and document these problems in quality notifications and forward them to the departments responsible for further processing. You can define follow-up actions that help resolve problems quickly.
2011
© 2011 SAP AG. All rights reserved.
5
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
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Inspection Process Flow in Quality Management - Overview
Lesson: Inspection Process Flow in Quality Management - Overview Lesson Overview In this lesson, you will learn about the inspection process flow and its most important steps. The focus of this process flow is the inspection lot.
Lesson Objectives After completing this lesson, you will 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
Business Example The inspection lot represents the request to a plant to perform a quality inspection on a certain quantity of a material. For example, inspection lots can be created because of goods movements or deliveries to customers. They can also be created with manufacturing orders and production versions to check materials during production. Inspection lots can contain several operations. An operation defines which activity is to be performed at a work center. Each operation can contain several inspection characteristics. An inspection characteristic describes what is to be inspected.
2011
© 2011 SAP AG. All rights reserved.
7
Unit 1: QM Processes in the Logistics Processes
PLM412
QM Inspection Process
Figure 5: QM Inspection Process
Figure 6: Inspection lot: General
8
© 2011 SAP AG. All rights reserved.
2011
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 a prerequisite for the inspection.
Figure 7: QM Inspection Process
An inspection lot contains the object that is to be inspected. This can be a material, the batch of a material, or a technical object (equipment, functional location). The first step in the inspection lot life cycle is the sample determination. The second step consists of results or defects recording. The usage decision completes the inspection lot. The inspection status is updated in the inspection lot. All inspection data (results, defects, usage decision) is recorded for the inspection lot. Different evaluations can be made based on the inspection lot data record.
2011
© 2011 SAP AG. All rights reserved.
9
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 current quality inspection. This data includes, for example: • • •
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 the execution of the inspection are created using the specifications from the inspection lot data record.
10
© 2011 SAP AG. All rights reserved.
2011
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 in Customizing. An “originating document” is one of the following: • • • •
Purchasing document Material document Order Delivery
You can use the “Dynamic Selections” function to add extra options to the inspection lot selection. Note the “Maximum No. of Hits” and SAP Note 307320 when selecting inspection lots.
2011
© 2011 SAP AG. All rights reserved.
11
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 the inspection instruction with reference to the inspection type in Customizing. The sample-drawing instruction contains the necessary information for taking the sample quantity or one or more physical samples. The inspection instruction describes the nature of the inspection and how to carry it out. You can print these documents for each inspection operation (work center).
12
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Inspection Process Flow in Quality Management - Overview
Exercise 1: Inspection Lot - Overview Exercise Objectives After 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 Example Inspection lot data records are normally created automatically in the logistics supply 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 data relevant for the quality inspection and the integration of QM in other application components.
Task: Display an inspection lot The 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 was automatically created. You want to display the data relevant for inspection before processing the inspection lot further. Limit the value range when searching for the inspection lot and search for the inspection lots for material T-BQ1##. “##” is your group number. Make a note of the following data from the inspection lot:
2011
Inspection lot number:
_____________________
Inspection type:
_____________________
System status:
_____________________
Vendor:
_____________________
Material document:
_____________________
Inspection lot quantity:
_____________________
Sample size:
_____________________
© 2011 SAP AG. All rights reserved.
13
Unit 1: QM Processes in the Logistics Processes
PLM412
Solution 1: Inspection Lot - Overview Task: Display an inspection lot The 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 was automatically created. You want to display the data relevant for inspection before processing the inspection lot further. Limit the value range when searching for the inspection lot and search for the 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
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Inspection Process Flow in Quality Management - Overview
Material document:
_____________________
Inspection lot quantity:
_____________________
Sample size:
_____________________
a)
Logistics → Quality Management → Quality Inspection → Worklist → Inspection → Display Data (QA33) Select the inspection lot for the material T-BQ1##. Other options for displaying the inspection lot: Logistics → Quality Management → Quality Inspection → Inspection Lot → Processing → Display (QA03) The following applies when working with QA03: For inspection lot selection, enter material T-BQ1## on the Material tab page of the F4 help, and choose Continue. All inspection lots that correspond to the selection criteria are displayed in the list. Transfer the inspection lot number by double-clicking it. Choose Enter. The Display Inspection Lot screen appears. You can see the following values on this screen: Field name or data type
Values
Inspection lot number:
........
Inspection type:
01
System status:
REL CALC SPRQ QLCH
Vendor:
1000
Material document:
........
Insp. lot quantities
2011
Inspection lot quantity:
1000 PC
Sample size:
1000 PC
© 2011 SAP AG. All rights reserved.
15
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
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Problem Processing with Quality Notifications - Overview
Lesson: Problem Processing with Quality Notifications - Overview Lesson Overview In this lesson you will get a general overview of problem processing using quality notifications.
Lesson Objectives After 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 provided by the link to the Workflow.
Business Example The procedure for processing problems plays an important part in the business processes of a company. It is important to process different types of problems efficiently. Problems that occur can be caused by external or internal events. Examples of these events are: • • •
2011
Customer complaint Complaint against a vendor Internal company problems (for example, defective materials in production)
© 2011 SAP AG. All rights reserved.
17
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 quality notifications.
Figure 12: Continuous Process Improvement
18
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Problem Processing with Quality Notifications - Overview
The quality notification system: • •
Enables a problem to be solved more efficiently, especially if more than one person in the company is involved in solving it. Supports continuous improvement of quality by checking the effectiveness of any solutions that are identified.
Procedure for problem solving
Figure 13: Procedure for Problem Processing
There are two ways of processing a quality notification: • •
2011
You can use the immediate tasks and activities that provide short-term help until an exact diagnosis is made. You can use the defect analysis that involves the investigation of the cause, and the introduction of the necessary corrective tasks and activities (long-term).
© 2011 SAP AG. All rights reserved.
19
Unit 1: QM Processes in the Logistics Processes
PLM412
Figure 14: Example: Customer complaint
•
A customer complaint can be recorded in the following ways: –
– –
20
You create a notification with reference to an SD document (sales order, delivery) for example. In this instance, additional information such as material number and customer is transferred directly to the quality notification. You enter a general description of the problem and save the notification. The “quality assurance” department is notified using the SAP Business Workflow.
© 2011 SAP AG. All rights reserved.
2011
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 provided by the link to the Workflow.
2011
© 2011 SAP AG. All rights reserved.
21
Unit Summary
PLM412
Unit Summary You 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 provided by the link to the Workflow.
22
© 2011 SAP AG. All rights reserved.
2011
PLM412
Test Your Knowledge
Test Your Knowledge 1.
When implementing QM, only the business processes in a company must be examined. Determine whether this statement is true or false.
□ □ 2.
True False
Test equipment monitoring is part of test equipment management. Determine whether this statement is true or false.
□ □ 3.
True False
QM is integrated in the processes of the logistics supply chain. Determine whether this statement is true or false.
□ □ 4.
True False
Inspection results recording must always be carried out for each inspection lot. Determine whether this statement is true or false.
□ □ 5.
True False
Inspection lots can always only be created with reference to a logistical process (for example, goods movement, order release). Determine whether this statement is true or false.
□ □ 6.
True False
Does the inspection lot data record contain the following information? Choose the correct answer(s).
□ □ □ □
2011
A B C D
Lot size and sample size Vendor or customer Assigned inspection specifications (for example, task list) Material documents that are related to the inspection lot
© 2011 SAP AG. All rights reserved.
23
Test Your Knowledge
7.
PLM412
The same type of notification is used for all notifications with reference to production. Determine whether this statement is true or false.
□ □ 8.
True False
Several defect items can be included in one notification. Determine whether this statement is true or false.
□ □ 9.
True False
The notifications can be used for various processes in the logistical chain. Determine whether this statement is true or false.
□ □
24
True False
© 2011 SAP AG. All rights reserved.
2011
PLM412
Test Your Knowledge
Answers 1.
When implementing QM, only the business processes in a company must be examined. Answer: False In addition to the business processes, standards requirements must also be taken into consideration for implementation.
2.
Test equipment monitoring is part of test equipment management. Answer: True Test equipment management uses functions from Quality Management and Plant Maintenance. The management of measuring devices is a Plant Maintenance task, calibration inspections are executed using transactions from 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 can be triggered automatically.
4.
Inspection results recording must always be carried out for each inspection lot. Answer: False Depending on the setting in the inspection type, results recording and/or defects recording can take place for an inspection lot. You can also work with defects recording only.
5.
Inspection lots can always only be created with reference to a logistical process (for example, goods movement, order release). Answer: False You can also create manual inspection lots for particular inspection lot origins, if required. In addition, you can use inspection lot origin 89 for manual inspection lots.
2011
© 2011 SAP AG. All rights reserved.
25
Test Your Knowledge
6.
PLM412
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 from inspection planning, and inspection results via the inspection lot data record.
7.
The same type of notification is used for all notifications with reference to production. Answer: False Depending on the application, different notification types can be used for internal problem notifications. You can define your own notification types in Customizing 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 defect item, 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, the notifications can be used, for example, for procurement operations, in goods receipt and goods withdrawal, or in production.
26
© 2011 SAP AG. All rights reserved.
2011
Unit 2 Basic Data in Quality Management Unit Overview QM-specific master data is required in inspection planning so that the corresponding information can be stored in the system. This unit gives you a detailed introduction to the basic data that is available. At the end of the unit, material-dependent inspection requirements are created in the system using this basic data. Material-dependent inspection requirements form the basis for the rest of the inspection process.
Unit Objectives After completing this unit, you will be able to: • • • • • • • • • • • • • • • • • • • •
2011
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.
© 2011 SAP AG. All rights reserved.
27
Unit 2: Basic Data in Quality Management
• •
PLM412
Explain the structure of the material specification. Describe the possible uses of the material specification.
Unit Contents Lesson: Material Master and Inspection Settings ........................... 29 Lesson: Sample Determination ................................................ 35 Exercise 2: Sample Determination ........................................ 41 Lesson: Dynamic Modification ................................................. 50 Exercise 3: Dynamic Modification Rule................................... 55 Lesson: Inspection Setup - Mass Maintenance.............................. 64 Exercise 4: Inspection Setup - Mass Maintenance ..................... 67 Lesson: Master inspection characteristic ..................................... 76 Exercise 5: Master Inspection Characteristics........................... 85 Lesson: Input Processing for Measured Values ............................. 98 Lesson: Code Groups and Codes ............................................104 Exercise 6: Catalogs, Code Groups, and Codes.......................109 Lesson: Selected Sets and Catalog Profile ................................. 114 Exercise 7: Selected Sets and Codes of Selected Sets...............121 Lesson: Inspection method ....................................................128 Lesson: Distributing QM Basic Data .........................................134 Lesson: Material Specification ................................................138 Exercise 8: Material Specification ........................................141
28
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Material Master and Inspection Settings
Lesson: Material Master and Inspection Settings Lesson Overview The settings in the material master have an important effect on processes in quality management. The fundamental settings that determine if a material must be inspected, and for which logistical processes, are stored here.
Lesson Objectives After completing this lesson, you will be able to: • •
Describe the inspection settings in the material master. Explain Customizing for the inspection settings.
Business Example According to the settings in the material master, automatic inspection lots are generated in logistical processes. The inspection settings are defined during quality 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 pieces of master data. These act as modular, reusable building blocks when planning quality inspections.
2011
© 2011 SAP AG. All rights reserved.
29
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
© 2011 SAP AG. All rights reserved.
2011
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 inspection plan, routing, or master recipe.
Insp with spec. means: •
2011
You inspect the inspection characteristics as defined in the material specification.
© 2011 SAP AG. All rights reserved.
31
Unit 2: Basic Data in Quality Management
PLM412
Inspection by configuration means: •
You can include customer-specific specifications for inspection characteristics in the inspection: Configurations from the customer or production order are taken into consideration during inspection lot creation and the specifications from the task list or material specification are adapted accordingly. The prerequisite is that a link exists between the class characteristic and the master inspection characteristic.
Figure 18: Customizing for Inspection Lot Origin
You define the relationship between the inspection type and the inspection lot origin in Customizing. The inspection lot origin is predefined in the system and it determines the origin of the inspection lot. The actual inspection process is defined using the inspection type. You can create your own inspection types in Customizing. You can link several inspection types to each inspection lot origin. •
For example, inspection lot origin 01 (goods receipt) can have the following inspection 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 in the Inspection Setup for the material.
32
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Material Master and Inspection Settings
When you make the inspection settings in the material master, note also the F1 Help for the Preferred Inspection Type indicator.
2011
© 2011 SAP AG. All rights reserved.
33
Unit 2: Basic Data in Quality Management
PLM412
Lesson Summary You should now be able to: • Describe the inspection settings in the material master. • Explain Customizing for the inspection settings.
34
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Sample Determination
Lesson: Sample Determination Lesson Overview Sample determination is an obligatory step in the QM inspection process. In accordance with standard requirements, there are different options for calculating the sample size. These options are described in detail in this lesson.
Lesson Objectives After completing this lesson, you will be able to: • •
Explain the master data for sample determination. Describe the tasks of the sampling procedure.
Business Example Different specifications for sample determination are required for the different inspection processes. These are created using sampling procedures and sampling schemes.
Sample Determination
Figure 19: QM Inspection Process: Sample Determination
Sample determination is an obligatory step in inspection lot processing.
2011
© 2011 SAP AG. All rights reserved.
35
Unit 2: Basic Data in Quality Management
PLM412
Dynamic modification can influence sample determination.
Figure 20: Material Master - Sample Determination
In the inspection setup of the QM view of the material master, sample determination 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 the assignment of the sampling procedure takes place at inspection characteristic level and not in the inspection setup in the QM view of the material master.
36
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Sample Determination
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 the sample, 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 for which the “Free inspection points” indicator is set. Depending on the sampling type or the valuation mode, further entries can or must 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 stage of the dynamic modification rule.
2011
© 2011 SAP AG. All rights reserved.
37
Unit 2: Basic Data in Quality Management
PLM412
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 to determine the sample.
38
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Sample Determination
The valuation “Variable inspection s-method” can occur either single-sided or double-sided.
Sampling Scheme
Figure 24: Creating a Sampling Scheme
In the sampling scheme, you can define different sampling tables with sampling plans. In the individual sampling tables, you can define corresponding sampling plans 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
You can find additional information regarding the samples in the SAP System in Customizing under the following path: Quality Management → Quality Planning → Basic Data → Sample, SPC
2011
© 2011 SAP AG. All rights reserved.
39
Unit 2: Basic Data in Quality Management
PLM412
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 determined by dividing the lot quantity by the sample quantity. The lot size determined in example 2 is 4000. As a result, the sample size of 50 is used. (In the example, this can be used for a lot size greater than 1,000 or smaller than or equal to 10,000.) If the maximum possible lot size is exceeded, the sample size for the maximum possible lot size is used.
40
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Sample Determination
Exercise 2: Sample Determination Exercise Objectives After completing this exercise, you will be able to: • Create sampling procedures and sampling schemas.
Business Example In your company, you want to determine the sample quantity that is proposed for the inspection using a suitable sampling procedure. You need a sampling procedure with the corresponding valuation mode for the different inspection types (attributive inspection, variable inspection). For certain inspections, you want to work with a fixed sample or a sample percentage.
Task: Basic data for the sample determination The sampling procedure and the sampling schemas are part of the basic data for the sample determination. 1.
Creating a sampling procedure with a fixed sample. Create a sampling procedure with the description SP01-## and a suitable short text. Use a fixed sample with the sample size n = 5 and a valuation mode that allows the sample to be created automatically using the nonconforming units. The sampling procedure is not to be used with inspection points. A stage change is possible. You do not need a control chart. Hint: Use the Sample button to define the fixed sample size n and the acceptance number c. Hint: Use the acceptance number c = 0 if nonconforming units lead to a rejection.
2.
Create a sampling procedure with a sample percentage - optional exercise Create another sampling procedure with the description SP02-## and a suitable short text. Use the sample percentage as 5% and a valuation mode without valuation parameters. The sampling procedure is not used with inspection points. A stage change is possible.
3.
Create a sampling schema - optional exercise Continued on next page
2011
© 2011 SAP AG. All rights reserved.
41
Unit 2: Basic Data in Quality Management
PLM412
You want to determine the sample size depending on the inspection lot quantity. To do this, create a sampling schema with the description S## for an attributive inspection. The first sampling table should be used without the AQL value for the inspections with the inspection severity Normal. Enter a sample size of your choice, an acceptance number (c1), and a rejection number (d1) for the following intervals. Hint: Note that for automatic valuation during a single sampling inspection, the difference between the acceptance and rejection number must be exactly 1. Lot size (to)
Sample size
c1
d1
100 1 000 10 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 lot size that you can use. Create a second sampling table (also without an AQL value) for an inspection with the inspection severity Reduced. Enter a sample size of your choice, an acceptance number, and a rejection number for the following intervals. Lot size (to)
Sample size
c1
d1
100 1 000 10 000 Over 10,000
Hint: When you create the second sampling table, set the indicator With copy model so that the data from the first sampling table can be copied. Then, you only have to change the sample size and the acceptance and rejection number. 4.
Creating a sampling procedure with a sampling schema Continued on next page
42
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Sample Determination
Create another sampling procedure with the description SP03-## for an attributive inspection according to the number of nonconforming units. Use the sampling scheme 212 or your sample schema S##. The sampling procedure is not to be used with inspection points. A stage change is possible. Use the inspection severity Normal inspection and the AQL value 1.0. The sampling procedure must not be added to the allowed relationships. If you use the sampling schema S##, an AQL value is not required.
2011
© 2011 SAP AG. All rights reserved.
43
Unit 2: Basic Data in Quality Management
PLM412
Solution 2: Sample Determination Task: Basic data for the sample determination The sampling procedure and the sampling schemas are part of the basic data for the sample determination. 1.
Creating a sampling procedure with a fixed sample. Create a sampling procedure with the description SP01-## and a suitable short text. Use a fixed sample with the sample size n = 5 and a valuation mode that allows the sample to be created automatically using the nonconforming units. The sampling procedure is not to be used with inspection points. A stage change is possible. You do not need a control chart. Hint: Use the Sample button to define the fixed sample size n and the acceptance number c. Hint: Use the acceptance number c = 0 if nonconforming units lead 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 pushbutton Sampling procedure, or Enter, the Assignment screen appears. On this screen, you can define the short text for the sampling procedure, as well as the sampling type and valuation mode. Field name or data type
Values
sampling type
Fixed sample
valuation 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 no further entries, you can skip directly to the next screen by choosing Sample and entering the value 5 in the Sample size field and the value 0 in the Acceptance number field. Save your entries. Continued on next page
44
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Sample Determination
2.
Create a sampling procedure with a sample percentage - optional exercise Create another sampling procedure with the description SP02-## and a suitable short text. Use the sample percentage as 5% and a valuation mode without valuation parameters. The sampling procedure is not used with inspection points. A stage change is possible. a)
Logistics → Quality Management → Quality Planning → Basic Data → Sample → Sampling Procedure → Create (QDV1) Enter the description SP02-## on the initial screen. On the assignment screen, enter a suitable short text for the sampling procedure, as well as the sampling type and valuation mode. Field name or data type
Values
sampling type
Sample percentage
valuation mode
Without valuation params
By choosing the F5 function key, the pushbutton Continue, or Enter, the Special Conditions screen appears. Since this exercise requires no further entries, you can skip to the next screen directly using the pushbutton Sample and enter the value 5 in the Sample percentage field. Save your entries. 3.
Create a sampling schema - optional exercise You want to determine the sample size depending on the inspection lot quantity. To do this, create a sampling schema with the description S## for an attributive inspection. The first sampling table should be used without the AQL value for the inspections with the inspection severity Normal. Enter a sample size of your choice, an acceptance number (c1), and a rejection number (d1) for the following intervals. Hint: Note that for automatic valuation during a single sampling inspection, the difference between the acceptance and rejection number must be exactly 1.
Continued on next page
2011
© 2011 SAP AG. All rights reserved.
45
Unit 2: Basic Data in Quality Management
PLM412
Lot size (to)
Sample size
c1
d1
100 1 000 10 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 lot size that you can use. Create a second sampling table (also without an AQL value) for an inspection with the inspection severity Reduced. Enter a sample size of your choice, an acceptance number, and a rejection number for the following intervals. Lot size (to)
Sample size
c1
d1
100 1 000 10 000 Over 10,000
Hint: When you create the second sampling table, set the indicator With copy model so that the data from the first sampling table can be copied. Then, you only have to change the sample size and the acceptance and rejection number. a)
Create a sampling schema: Logistics → Quality Management → Quality Planning → Basic Data → Sample → Sampling Schema → Create (QDP1) On the initial screen, enter the description S## in the Sampling schema field. ## is your group number. By choosing the Return key, the pushbutton Sampling schema, or Enter, the Header Data screen appears. On this screen, you can define the short text for the sampling schema, as well as the valuation parameters and the assignment of sampling tables. Field name or data type
Values
Valuation parameters
Attributive insp. Continued on next page
46
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Sample Determination
Field name or data type
Values
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 the inspection severity Normal inspection using the input help for your first sampling table in the field New. Enter sampling plans in the view for creating the sampling table. For example: Lot size (to)
Sample size
c1
d1
100 3
0
1
1 000 5
1
2
10 000 8
2
3
5
6
Over 10,000 10
Create an additional sampling table for the inspection severity Reduced inspection. To do this, choose the pushbutton Other table and select the corresponding inspection severity using the input help. If you want to copy entries from the first table, you must set the indicator With copy model. You can now define the sampling plan for the Reduced inspection. For example: Lot size (to)
Sample size
c1
d1
100 2
0
1
1 000 4
0
1
10 000 6
1
2
Over 10,000 8
4
5
Save your entries. 4.
Creating a sampling procedure with a sampling schema Create another sampling procedure with the description SP03-## for an attributive inspection according to the number of nonconforming units. Use the sampling scheme 212 or your sample schema S##. The sampling procedure is not to be used with inspection points. A stage change is possible. Continued on next page
2011
© 2011 SAP AG. All rights reserved.
47
Unit 2: Basic Data in Quality Management
PLM412
Use the inspection severity Normal inspection and the AQL value 1.0. The sampling procedure must not be added to the allowed relationships. If you use the sampling schema 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 pushbutton Sampling procedure, or Enter, the Assignment screen appears. On this screen, you can define the short text for the sampling procedure, as well as the sampling type and valuation mode. Field name or data type
Values
sampling type
Use sampling schema
valuation mode
Attributive inspection nonconf. units
By choosing the F5 function key, the pushbutton Continue, or Enter, the Special Conditions screen appears. In the Sampling schema field, enter the value 212 or the sampling schema S## that you created in task 3, Create a sampling schema. The sampling scheme 212 has different sampling tables for different inspection severities. If you choose the pushbutton Additional data, the inspection severities are displayed, and you can choose a sampling table using the input help. Use the sampling tables for the inspection severity Normal inspection and the AQL value 1.0. The sampling schema S## has 2 sampling tables for different inspection severities. If you choose the pushbutton Additional data, the inspection severities are displayed, and you can choose a sampling table using the input help. Save your entries. Hint: Answer the query regarding “allowed relationships” with NO.
48
© 2011 SAP AG. All rights reserved.
2011
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.
2011
© 2011 SAP AG. All rights reserved.
49
Unit 2: Basic Data in Quality Management
PLM412
Lesson: Dynamic Modification Lesson Overview In conjunction with sample determination, dynamic modification also plays an important role. Dynamic modification automatically reduces or increases the size of a sample according to the result of a previous inspection. The work involved in an inspection can then be reduced or increased, if required.
Lesson Objectives After completing this lesson, you will be able to: • •
Describe the structure of the modification rule. Explain how to use dynamic modification.
Business Example Dynamic modification is used so that inspection costs can be reduced as a result of high quality. Dynamic modification should be used to reduce the size of samples and for inspection skip.
Dynamic Modification Rule
Figure 26: Creating a Dynamic Modification Rule
50
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Dynamic Modification
You should enter all inspection stages before you maintain the stage change. When you maintain the stage change, you can specify, in addition to the number of inspections, a maximum skip duration in days for inspection stages that cause an inspection lot to be skipped. The system uses the reset period to calculate the reset date in the quality level and automatically updates it when the quality level is updated or corrected. After the reset period has passed, the quality level returns to the initial inspection stage of the dynamic modification rule.
Figure 27: Dynamic Modification Rule
The dynamic modification rule defines the inspection stages and the conditions for an inspection stage change. If you do not use a sampling scheme in a sampling procedure, you should not use the inspection severities “Tightened”, “Normal”, or “Reduced” in the dynamic modification rule. In the dynamic modification history, you can display all inspection lots or inspection characteristics (if dynamic modification by characteristic) and their respective inspection stages as a list or graphic, independent of the dynamic modification level (lot level, characteristic level, inspection type level).
2011
© 2011 SAP AG. All rights reserved.
51
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 certain dynamic modification criteria. You set dynamic modification criteria in Customizing for the inspection lot origin or the task list usage. You select from the default dynamic modification criteria in the task list header. Example: •
52
The dynamic modification criteria material, vendor, and manufacturer are used for goods receipt inspections. A quality level is updated at each goods receipt inspection with reference to these dynamic modification criteria. However, if the field Manufacturer has no entry in the inspection lot for example,the system only updates the quality level for the material and vendor.
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Dynamic Modification
General Sample Determination
Figure 29: Allowed Relationships
The allowed relationships contain combinations of dynamic modification rules and sampling procedures with reference to a sampling scheme. Sampling procedures without a sampling scheme are not relevant for allowed relationships. If you enter new entries for allowed relationships, the system checks whether corresponding entries (sampling plans) are available in the relevant sampling scheme for all inspection severities in the dynamic modification rule and for any available AQL value in the sampling procedure. In a task list only combinations of dynamic modification rules and sampling procedures with a sampling scheme are allowed that are defined as allowed relationships in QM.
Figure 30: General Sample Determination
2011
© 2011 SAP AG. All rights reserved.
53
Unit 2: Basic Data in Quality Management
54
© 2011 SAP AG. All rights reserved.
PLM412
2011
PLM412
Lesson: Dynamic Modification
Exercise 3: Dynamic Modification Rule Exercise Objectives After completing this exercise, you will be able to: • Create dynamic modification rules.
Business Example You reduce the inspection scope using suitable dynamic modification rules so that you can reduce the expense of inspections as a result of improved quality. These can also allow for an inspection skip.
Task: Basic data for the dynamic modification The dynamic modification rules are part of the basic data for dynamic modifications. The following tasks contain two examples for dynamic modification 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 you make 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 inspection stage, the inspection should be performed without a sampling scheme. If no inspection lot is rejected after four inspections with the initial inspection stage, five inspection lots should be skipped. Afterwards, an inspection is carried 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 to the beginning of the cycle. That means to the initial inspection stage. This dynamic modification rule must not be added to the allowed relationships. Make a note of the individual inspection stages:
Continued on next page
2011
© 2011 SAP AG. All rights reserved.
55
Unit 2: Basic Data in Quality Management
Stage
PLM412
Inspec- skip tion severity
Initial inspection stage
Short text
Make a note of the settings for the stage change: Insp. stage
2.
OK No. of inspections
No. of skips
Not OK New insp. stage
Rejections
New insp. stage
Creating a dynamic modification rule with a sampling scheme Define another dynamic modification rule B## for dynamic modification when you make the usage decision. A reset period is not needed for the quality level. The initial inspection stage allows an inspection with the inspection severity Normal. The inspection severity Reduced should be used in the second inspection stage. The third stage of the dynamic modification rule should be a skip. If no inspection lot was rejected after four inspections with the initial inspection stage, four more inspection lots should be inspected with the inspection severity Reduced. Then inspection lots should be skipped. The inspection lots should not be skipped for more than 100 days. After this period, four inspection lots should be inspected with the inspection severity Reduced. A rejection at any stage of the dynamic modification rule takes you back to the beginning of the cycle. That means to the initial inspection stage.
Continued on next page
56
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Dynamic Modification
Add this dynamic modification rule to the allowed relationships with your sampling procedure SP03-##. Hint: The maximum number of skips is limited to 32,767 because of the nature of the database field. You must also enter the number of skips when entering a maximum skip duration in days. Make a note of the individual inspection stages: Stage
Inspection severity
skip
Initial inspection stage
Short text
Make a note of the settings for the stage change: Insp. stage
2011
OK No. of inspections
No. of skips
Max. skip duration
Not OK New insp. stage
© 2011 SAP AG. All rights reserved.
Rejections
New insp. stage
57
Unit 2: Basic Data in Quality Management
PLM412
Solution 3: Dynamic Modification Rule Task: Basic data for the dynamic modification The dynamic modification rules are part of the basic data for dynamic modifications. The following tasks contain two examples for dynamic modification 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 you make 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 inspection stage, the inspection should be performed without a sampling scheme. If no inspection lot is rejected after four inspections with the initial inspection stage, five inspection lots should be skipped. Afterwards, an inspection is carried 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 to the beginning of the cycle. That means to the initial inspection stage. This dynamic modification rule must not be added to the allowed relationships. Make a note of the individual inspection stages: Stage
Inspec- skip tion severity
Initial inspection stage
Short text
Make a note of the settings for the stage change:
Continued on next page
58
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Dynamic Modification
Insp. stage
a)
OK No. of inspections
No. of skips
Not OK New insp. stage
Rejections
New insp. stage
Logistics → Quality Management → Quality Planning → Basic Data → Sample → Dynamic Modification Rule → Create (QDR1) Enter the description A## in the Modification rule field. ## is your group number. By choosing the Return key, the pushbutton Dynamic Modification Rule, or Enter, the Header Data screen appears. On this screen, you can define a short text for the dynamic modification rule, as well as the time of dynamic modification (For usage decision). By choosing the F5 function key or the pushbutton Next screen, you can call up the Inspection Stages screen for the dynamic modification rule. Define individual inspection stages using the following table: Stage
Inspection severity
10
001
20 30
skip
Initial inspection stage
Short text
X
Inspection start
X 001
Skip stage One-off inspection
To maintain the stage changes, you must select all inspection stages and switch to the detail screens for the individual inspection stage changes using the pushbutton Stage change. Hint: You can select all stages of the dynamic modification rule using the Select all pushbutton. Define the individual inspection stages using the following table:
Continued on next page
2011
© 2011 SAP AG. All rights reserved.
59
Unit 2: Basic Data in Quality Management
Insp. stage
10
PLM412
OK No. of inspections
New insp. stage
Rejections
New insp. stage
20
1
10
30
1
10
20
1
10
4
20 30
No. of skips
Not OK
5 1
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 modification when you make the usage decision. A reset period is not needed for the quality level. The initial inspection stage allows an inspection with the inspection severity Normal. The inspection severity Reduced should be used in the second inspection stage. The third stage of the dynamic modification rule should be a skip. If no inspection lot was rejected after four inspections with the initial inspection stage, four more inspection lots should be inspected with the inspection severity Reduced. Then inspection lots should be skipped. The inspection lots should not be skipped for more than 100 days. After this period, four inspection lots should be inspected with the inspection severity Reduced. A rejection at any stage of the dynamic modification rule takes you back to the beginning of the cycle. That means to the initial inspection stage. Add this dynamic modification rule to the allowed relationships with your sampling procedure SP03-##. Hint: The maximum number of skips is limited to 32,767 because of the nature of the database field. You must also enter the number of skips when entering a maximum skip duration in days. Make a note of the individual inspection stages: Continued on next page
60
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Dynamic Modification
Stage
Inspection severity
skip
Initial inspection stage
Short text
Make a note of the settings for the stage change: Insp. stage
a)
OK No. of inspections
No. of skips
Not OK
Max. skip duration
New insp. stage
Rejections
New insp. stage
Logistics → Quality Management → Quality Planning → Basic Data → Sample → Dynamic Modification Rule → Create (QDR1) Enter the description B## in the field Modification rule. ## is your group number. By choosing the Return key, the pushbutton Dynamic Modification Rule, or Enter, the Header Data screen appears. On this screen, you can define a short text for the dynamic modification rule, as well as the time of dynamic modification (For usage decision). By choosing the F5 function key or the pushbutton Next screen, you can call up the Inspection Stages screen for the dynamic modification rule. Define individual inspection stages using the following table: Stage
Inspection severity
10
004
20
002
30
skip
Initial inspection stage
Short text
X
Normal inspection Reduced inspection
X
Skip stage
Continued on next page
2011
© 2011 SAP AG. All rights reserved.
61
Unit 2: Basic Data in Quality Management
PLM412
Select all inspection stages and define the individual stage changes using the following table: Insp. stage
OK No. of inspections
No. of skips
Not OK Max. skip duration
New insp. stage
No. of rejections
New insp. stage
10
4
20
1
10
20
4
30
1
10
20
1
10
30
32 767
100
Save your entries. Confirm the question Add dynamic modification rule to the allowed relationships? with Yes. The system displays the message that Dynamic modification rule B## was created and then the view Allwd. Relationships: Sampling Procedures/Dynamic Mod. Rule appears. Assign sampling procedure SP03-## to dynamic modification rule B## using the pushbutton New entries and enter a short text. Save your entries. Hint: You can also maintain allowed relationships at any time by 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 → Sampling Procedure → Assign Dynamic Modification Rule (QDB1)
62
© 2011 SAP AG. All rights reserved.
2011
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.
2011
© 2011 SAP AG. All rights reserved.
63
Unit 2: Basic Data in Quality Management
PLM412
Lesson: Inspection Setup - Mass Maintenance Lesson Overview When QM is implemented, a large number of materials have to be prepared for the inspection processes. In addition, it may also be necessary to change the inspection setup when using a large number of materials. Mass maintenance can be used to accommodate these requirements.
Lesson Objectives After 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 Example Materials must have the correct inspection setup in the QM view of the material master for a quality inspection at various points in the logistical processes. To maintain this inspection setup, a large number of materials are processed.
Inspection Setup - Mass Maintenance
Figure 31: Inspection Setup - Mass Maintenance
64
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Inspection Setup - Mass Maintenance
The mass maintenance of the Inspection Setup (transaction QA08) makes processing easier: •
Mass maintenance: Activate/deactivate inspection type – –
You can activate or deactivate a chosen inspection type generally or based on the selection criteria plant, material, and material type. Activate despite inspection stock When you set this indicator, inspection lots are automatically created to avoid stock discrepancies between QM and MM, if you activate the first stock-relevant inspection type. The inspection type is copied from Customizing for this.
•
Inspection setup individual processing You can display or edit the Inspection Setup directly for one or more selected materials. Inspection setup mass processing
– •
You can change the Inspection Setup for a selected inspection type generally or based on the selection criteria. You can create change documents for each processing type. A change document provides information about which changes were made to a master record, by whom, and when. –
•
Figure 32: QM Master Data - Summary 1
You can maintain a relationship between a sampling procedure and a dynamic modification rule for each inspection type in the QM view of the material master.
2011
© 2011 SAP AG. All rights reserved.
65
Unit 2: Basic Data in Quality Management
66
© 2011 SAP AG. All rights reserved.
PLM412
2011
PLM412
Lesson: Inspection Setup - Mass Maintenance
Exercise 4: Inspection Setup - Mass Maintenance Exercise Objectives After 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 Example Materials must have the correct inspection setup in the QM view of the material master for a quality inspection at various points of the logistics supply chain. You must edit a large number of materials to maintain this inspection setup data.
Task 1: Mass maintenance of the inspection setup in the materials Changing inspection setup data in the material master 1.
For greater efficiency, you have decided to work only with defects recording for one inspection type. To do this, you must change the inspection setup for the corresponding materials. You can use the transaction for maintaining the inspection setup to make these changes. For materials T-BQ1## and T-BQ2##, the inspection setup should be changed for inspection type 05 in plant 1000. These materials should be inspected without a material specification or inspection plan. An inspection percentage of 5% and the dynamic modification rule A## are used for the sample determination. Hint: On the screen QM-specific data selection for material, choose the pushbutton for multiple selection to select the two materials and then enter the desired materials as single values. Caution: Use multiple selection to ensure that you change only your own materials and not the materials of the other course participants. Make a note on the following overview of the inspection type settings that are relevant for this exercise:
Continued on next page
2011
© 2011 SAP AG. All rights reserved.
67
Unit 2: Basic Data in Quality Management
Description
PLM412
Indicator
Description
Indicator
Insp. with mat. spec.
100 % inspection
Insp. with task list
Manual sample calc.
Automatic assignment
Skips allowed
Check Chars
Automatic UD Entry
Entry
Inspection %
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 at goods receipt. The follow-up inspection occurs for material T-BQ1## in plant 1000. The inspection lot origin is 05 (Miscellaneous goods movement) and the inspection type is also 05. The inspection lot quantity is 500 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 modification rule:
___________________________________
Task 3: Maintaining Your List of Favorites – Optional Exercise 1.
Since you often work with inspection lots, it is useful to enter the most important transactions (for example, Display inspection lot) in your list of favorites. You can do this in the following ways:
Continued on next page
68
© 2011 SAP AG. All rights reserved.
2011
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 → Settings and 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 your favorites list.
Note that your favorites are displayed differently depending on the method you used. If you want to rename your favorites, you can specify another name with a right mouse click (Change favorites).
2011
© 2011 SAP AG. All rights reserved.
69
Unit 2: Basic Data in Quality Management
PLM412
Solution 4: Inspection Setup - Mass Maintenance Task 1: Mass maintenance of the inspection setup in the materials Changing inspection setup data in the material master 1.
For greater efficiency, you have decided to work only with defects recording for one inspection type. To do this, you must change the inspection setup for the corresponding materials. You can use the transaction for maintaining the inspection setup to make these changes. For materials T-BQ1## and T-BQ2##, the inspection setup should be changed for inspection type 05 in plant 1000. These materials should be inspected without a material specification or inspection plan. An inspection percentage of 5% and the dynamic modification rule A## are used for the sample determination. Hint: On the screen QM-specific data selection for material, choose the pushbutton for multiple selection to select the two materials and then enter the desired materials as single values. Caution: Use multiple selection to ensure that you change only your own materials and not the materials of the other course participants. Make a note on the following overview of the inspection type settings that are relevant for this exercise: Description
Indicator
Description
Indicator
Insp. with mat. spec.
100 % inspection
Insp. with task list
Manual sample calc.
Automatic assignment
Skips allowed
Check Chars
Automatic UD Entry
Inspection %
Entry Dyn. mod. rule
Continued on next page
70
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Inspection Setup - Mass Maintenance
a)
Logistics → Quality Management → Quality Planning → Logistics Master Data → Material → Inspection Setup (QA08) The selection screen Mass Change of QM Inspection Setup Data in Materials appears. Specify plant 1000 in the screen area QM-specific data selection for material. You use the multiple selection pushbutton that is next to the material number field to select materials. On the Single vals tab page, enter the material numbers T-BQ1## and T-BQ2##. After leaving the multiple selection screen using the pushbutton Copy or the F8 function key, the selection screen for the inspection setup appears again. Choose the Mass processing tab page and enter inspection type 05. Execute the mass change using the F8 function key or the Execute pushbutton. The screen Parameters for Inspection Setup Data in Materials appears. In accordance with the specifications on the selection screen, you see the Customizing settings for inspection type 05. If you want to process inspection lots for this inspection type only with defects recording, no entries should exist in the inspection setup that reference specifications (for example, task list, specification). Enter the following data for sample determination and dynamic modification: Description
Indicator
Description
Insp. with mat. spec.
100 % inspection
Insp. with task list
Manual sample calc.
Automatic assignment
Skips allowed
Check Chars
Automatic UD Entry
Inspection %
5
Indicator
X
Entry Dyn. mod. rule
A##
After changing the entries and pressing Return, an overview screen of materials that you can change appears. Select the materials and save your changes. In the status column, you can see that 2 materials were edited.
Continued on next page
2011
© 2011 SAP AG. All rights reserved.
71
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 at goods receipt. The follow-up inspection occurs for material T-BQ1## in plant 1000. The inspection lot origin is 05 (Miscellaneous goods movement) and the inspection type is also 05. The inspection lot quantity is 500 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 modification rule:
___________________________________
a)
Logistics → Quality Management → Quality Inspection → Inspection Lot → Processing → Create (QA01) Enter the following data on the initial screen: Field name or data type
Values
Material
T-BQ1##
Plant
1000
Inspection lot origin
05
You can access the detail data for the inspection lot by choosing Enter. Field name or data type
Values
Insp. lot size
500
Short text
Group ##
Choose the Return key to release the data. Save your entries. Display your manually created inspection lot: Logistics → Quality Management → Quality Inspection → Inspection Lot → Processing → Display (QA03)
Continued on next page
72
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Inspection Setup - Mass Maintenance
The number of the inspection lot that was last created is displayed in the field Inspection lot. By choosing Enter, the screen Display inspection lot appears. The following data is displayed on this screen: Field name or data type
Values
Inspection lot
50000000.......
System status
REL CALC QLCH
Insp. lot quantities Sample size
25 PC
Insp. specifications Dyn. 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 most important transactions (for example, Display inspection lot) in your list of 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 → Settings and 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 your favorites list.
Continued on next page
2011
© 2011 SAP AG. All rights reserved.
73
Unit 2: Basic Data in Quality Management
PLM412
Note that your favorites are displayed differently depending on the method you used. If you want to rename your favorites, you can specify another name with a right 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 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 → Settings and 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 your favorites list.
74
© 2011 SAP AG. All rights reserved.
2011
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.
2011
© 2011 SAP AG. All rights reserved.
75
Unit 2: Basic Data in Quality Management
PLM412
Lesson: Master inspection characteristic Lesson Overview An inspection characteristic describes what is to be inspected. If particular inspection specifications are required in many task lists, you can create a suitable master inspection characteristic and include this in different task lists. Master inspection characteristics, therefore, help to simplify and standardize inspection planning.
Lesson Objectives After completing this lesson, you will be able to: • •
Describe the structure of master inspection characteristics. Explain the options for using master inspection characteristics.
Business Example To ensure consistency and standardization in inspection planning, master inspection characteristics are used. This is to enable you to process required changes centrally.
Master Inspection Characteristic
Figure 33: Master inspection characteristics: General
76
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Master inspection characteristic
A master inspection characteristic is an inspection characteristic that has been defined for frequent use in task lists or should be evaluated for all inspection plans. Master inspection characteristics help to improve and standardize inspection planning. Search and replace functions for master inspection characteristics ensure simplified processing. As of SAP ERP 6.0 (ECC 6.0), as well as using the short text and search field to search, you can also use an extended search function for master inspection characteristics. The master inspection characteristics are connected to the SAP search engine TREX. You can find the corresponding settings in Customizing under SAP NetWeaver -> Application Server -> System administration -> Search Engine Service.
Figure 34: master inspection characteristic
An inspection characteristic describes the inspection criteria. The characteristic control contains, for example: • • •
2011
Characteristic type (qualitative, quantitative) Results confirmation type (for example, summarized, single result) Characteristic processing type (required characteristic, optional characteristic)
© 2011 SAP AG. All rights reserved.
77
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 is proposed. To be able to use the master inspection characteristic, the status must be set to Released. Incomplete copy model: It is not necessary to completely maintain the master inspection characteristic at creation. The missing entries can be added in the task list. Complete copy model: The master inspection characteristic must be completely maintained at creation. When linking the master inspection characteristic to a task list or a material specification, you can change the characteristic specifications. Reference characteristic: The master inspection characteristic must be completely maintained at creation. When linking the master inspection characteristic to a task list or material specification, the characteristic is locked and can be maintained and replaced centrally. Complete copy models and reference characteristics can be used in the material specification and they can also be used as „additional characteristics“ (unplanned characteristics) in the results recording. Changes to master inspection characteristics can be carried out with and without history. The necessary default values are defined in Customizing for each plant.
78
© 2011 SAP AG. All rights reserved.
2011
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 to determine the process flow of the characteristic inspection in detail. For the control indicator, you can enter default values in Customizing: Quality Management → Quality Planning → Basic Data → Inspection Characteristic, Inspection Method → Define Default Values for Control Indicators. Read the relevant documentation in Customizing.
History Management
Figure 37: Validity of a Master Inspection Characteristic
Validity statuses of master inspection characteristics or inspection methods are possible through the use of versions. When you change a version, you can find the valid master inspection characteristic or the valid inspection method by specifying the key date.
2011
© 2011 SAP AG. All rights reserved.
79
Unit 2: Basic Data in Quality Management
PLM412
Figure 38: History Management
In Customizing, history management for master inspection characteristics or inspection methods can be activated for each plant. If the history management is active, the version counter is increased when the released master inspection characteristic or inspection method version is changed. The following occurs if you change master inspection characteristics and/or inspection methods that are referenced in a task list, a material specification or a certificate profile: •
•
80
If you change this basic data with the history, the changed data is not automatically updated in the task list, material specification or certificate profile. If you change this basic data without the history, the changed data of the referenced master inspection characteristics is immediately and automatically updated in the task list, material specification, and certificate profile.
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Master inspection characteristic
Figure 39: Effect of History Management on Master Inspection Characteristics
When you create a new version (validity status), the procedure shown above is followed if the master inspection characteristic is used in task lists or material specifications. After you change the validity status or version, the procedure described above can also be followed for a master inspection characteristic that is used in task lists or material specifications. After you change the validity status or version, the procedure described above can also be followed for an inspection method that is used in task lists The process displayed applies to master inspection characteristics that were created as reference characteristics. The process always applies if the master inspection characteristic was changed with history or if a new version of the inspection method is created. Reference characteristics can also be “unlocked” after being included in a task list or a material specification. After “unlocking” the characteristic (Undo reference), this process is no longer executed. History management for master inspection characteristics or inspection methods is set up in Customizing for the plant. Replace master data for a new version is set up in Customizing for the client.
2011
© 2011 SAP AG. All rights reserved.
81
Unit 2: Basic Data in Quality Management
PLM412
Figure 40: Tolerance Key for Quantitative Master Inspection Characteristics
The standard system contains preset tolerance tables for drill-holes and shafts according to DIN ISO 286-2. The use of target-value-dependent tolerance keys can be preset in Customizing for the tolerance key. The unit of measurement, target value, accuracy, and upper and lower specification limits are defined for each tolerance key. Tolerance keys can be assigned for quantitative master inspection characteristics (prerequisite: reference characteristic or complete copy model).
82
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Master inspection characteristic
Figure 41: Specification Determination Rule for Master Inspection Characteristics
As of SAP Enhancement Package 5 for SAP ERP 6.0 (EA-APPL 605), business function OPS_QM_PLAN_INTEGRAT, the integration of QM with the variant configuration has been improved. If a sales order or a production order contains a variant configuration with quality-related values without a value range, the inspection characteristic inherits the upper and lower tolerance value from the characteristic value of the variant configuration. As a result, even minor differences lead to the inspection characteristic being rejected. To be able to work with realistic tolerance values, you can use the specification determination rules delivered by SAP in the master data characteristic. You can use the BAdI BADI_QASDR_MASTERCHAR_TO_INSP to implement and use your own calculation logic for upper and lower tolerance limits depending on the characteristic values of the variant configuration. You can find the relevant settings in Customizing under: •
•
2011
Quality Management -> Quality Planning -> Basic Data -> Inspection Characteristic, Inspection Method -> Define Specification Determination Rule Quality Management -> Environment -> Tools -> Business Add-Ins -> Quality Planning -> Business Add-In for Specification Determination Rule
© 2011 SAP AG. All rights reserved.
83
Unit 2: Basic Data in Quality Management
84
© 2011 SAP AG. All rights reserved.
PLM412
2011
PLM412
Lesson: Master inspection characteristic
Exercise 5: Master Inspection Characteristics Exercise Objectives After 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 Example The quality inspection is performed in your company using inspection plans. You set the indicator Master inspection characteristics, so that you do not have to manually create inspection characteristics in the individual inspection plans. You can create these master inspection characteristics as master records in the planning phase and then copy or reference them in one or more task lists.
Task 1: Create a qualitative master inspection characteristic You use qualitative and quantitative master inspection characteristics according to requirements and operational area. You create a qualitative master inspection characteristic here to use later in inspection planning. 1.
You need a qualitative master inspection characteristic for the inspection of packaging materials. For plant 1000, create this master inspection characteristic 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 material specifications. A sampling procedure should be used to determine the respective inspection scope. It is very important that the correct packaging material is always used. Therefore, this characteristic must always be inspected. Summarized results recording should be used. If the characteristic is not accepted during the inspection, you may want to record additional information about the errors that occurred for this characteristic. To evaluate these recorded errors later, it is important that you use corresponding error codes when recording them. The number of units inspected during results recording must correspond to the planned number of units to be inspected. Additional documentation is not required during results confirmation. The characteristic should only be printed 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
2011
© 2011 SAP AG. All rights reserved.
85
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
[ ] Defects 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. assignment Print ( ) Print ( ) Do not print ( ) Do not print at skip
Hint: The master inspection characteristic can only be used in task lists and material specifications, if it has the status Released. Continued on next page
86
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Master inspection characteristic
Task 2: Create a quantitative master inspection characteristic You use qualitative and quantitative master inspection characteristics according to requirements and operational area. You create a qualitative master inspection characteristic 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 identifier MK02-## in plant 1000 and the short text Weight. Enter Group ## in the search field to find the master inspection characteristic. This characteristic should be used in task lists and material specifications and if necessary, it should be changed to suit the material. In this case, use the Complete copy model. A sampling procedure should be used to determine the respective inspection scope. The weight of the goods must always be known. Therefore, this characteristic must always be inspected. You must confirm single results during results recording. The number of units inspected during results recording must correspond to the planned number of units to be inspected. If the characteristic is not accepted during the inspection, you may want to record additional information for this characteristic. If you change the recorded inspection results later, you must create change documents. You should be able to assign test equipment in a task list (for example, inspection plan, routing, ..). The characteristic should only be printed on the inspection instruction, 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 above this 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
2011
© 2011 SAP AG. All rights reserved.
87
Unit 2: Basic Data in Quality Management
PLM412
Results confirmation ( ) No charac. rec.
( ) After accept.
( ) Classed recording
( ) After rejection
[ ] Defects 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. assignment
88
Print
Formula
( ) Print
( ) No formula
( ) Do not print
( ) Calculated characteristic
( ) Do not print at skip
( ) Input processing
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Master inspection characteristic
Solution 5: Master Inspection Characteristics Task 1: Create a qualitative master inspection characteristic You use qualitative and quantitative master inspection characteristics according to requirements and operational area. You create a qualitative master inspection characteristic here to use later in inspection planning. 1.
You need a qualitative master inspection characteristic for the inspection of packaging materials. For plant 1000, create this master inspection characteristic 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 material specifications. A sampling procedure should be used to determine the respective inspection scope. It is very important that the correct packaging material is always used. Therefore, this characteristic must always be inspected. Summarized results recording should be used. If the characteristic is not accepted during the inspection, you may want to record additional information about the errors that occurred for this characteristic. To evaluate these recorded errors later, it is important that you use corresponding error codes when recording them. The number of units inspected during results recording must correspond to the planned number of units to be inspected. Additional documentation is not required during results confirmation. The characteristic should only be printed 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
2011
© 2011 SAP AG. All rights reserved.
89
Unit 2: Basic Data in Quality Management
PLM412
Results confirmation ( ) No charac. rec.
( ) After accept.
( ) Classed recording
( ) After rejection
[ ] Defects 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. assignment Print ( ) Print ( ) Do not print ( ) Do not print at skip
Hint: The master inspection characteristic can only be used in task lists 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
Values
Plant
1000
Master inspection characteristic
Mk01-##
Valid from
Current date
Continued on next page
90
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Master inspection characteristic
You can display the general data for the master inspection characteristic by choosing the F5 function key, the pushbutton Master inspection characteristic or Enter. You set the indicator for a qualitative characteristic on this screen. Additional data for the general data: Field name or data type
Values
Status
Released Reference characteristic
Short text
Packaging
Search field
Group ##
You can display the settings for the control indicator for a qualitative characteristic 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
[ ] Defects 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
2011
© 2011 SAP AG. All rights reserved.
91
Unit 2: Basic Data in Quality Management
PLM412
Miscellaneous [ ] Long-term inspection [ ] Scrap share/q-score [ ] Res. rec. change docs [ ] Test-equip. assignment Print ( ) Print ( ) Do not print (•) Do not print at skip
Hint: When you have edited the first screen of control indicators, the second screen appears when you choose the Return key. Hint: If errors are detected during the inspection, you should choose the error codes manually. Therefore, you do not have to assign 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 the master inspection characteristic appears again. Save your entries.
Task 2: Create a quantitative master inspection characteristic You use qualitative and quantitative master inspection characteristics according to requirements and operational area. You create a qualitative master inspection characteristic 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 identifier MK02-## in plant 1000 and the short text Weight. Enter Group ## in the search field to find the master inspection characteristic. This characteristic should be used in task lists and material specifications and if necessary, it should be changed to suit the material. In this case, use the Complete copy model.
Continued on next page
92
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Master inspection characteristic
A sampling procedure should be used to determine the respective inspection scope. The weight of the goods must always be known. Therefore, this characteristic must always be inspected. You must confirm single results during results recording. The number of units inspected during results recording must correspond to the planned number of units to be inspected. If the characteristic is not accepted during the inspection, you may want to record additional information for this characteristic. If you change the recorded inspection results later, you must create change documents. You should be able to assign test equipment in a task list (for example, inspection plan, routing, ..). The characteristic should only be printed on the inspection instruction, 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 above this 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
[ ] Defects 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
2011
© 2011 SAP AG. All rights reserved.
93
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. assignment 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
Values
Plant
1000
Master 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 are copied from an inspection characteristic and can be changed. You can display the general data for the master inspection characteristic by choosing the F5 function key, the pushbutton Master inspection characteristic or Enter. You set the indicator for a quantitative characteristic on this screen. Additional data for the general data: Field name or data type
Values
Status
Released Complete copy model
Short text
Weight
Search field
Group ##
You can display the settings of the control indicators for a quantitative characteristic by choosing Enter or the Control indicator pushbutton. Set the control indicators as follows: Continued on next page
94
© 2011 SAP AG. All rights reserved.
2011
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
[ ] Defects 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 [x] Test-equip. assignment Print
Formula
( ) Print
(•) No formula
( ) Do not print
( ) Calculated characteristic
(•) Do not print at skip
( ) Input processing
After editing the control indicators, the tolerance key for the characteristic is displayed. You can enter 1 as the target value or you can exit the screen using the Return key. The quantitative data for the Continued on next page
2011
© 2011 SAP AG. All rights reserved.
95
Unit 2: Basic Data in Quality Management
PLM412
characteristic then appears. On this screen, you define the number of decimal places (1), the unit of measurement (kg), if necessary the target value (1), and both the lower specification limit (0.9) and the upper specification limit (1.1) for the characteristic. Exit the screen. Save your entries.
96
© 2011 SAP AG. All rights reserved.
2011
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.
2011
© 2011 SAP AG. All rights reserved.
97
Unit 2: Basic Data in Quality Management
PLM412
Lesson: Input Processing for Measured Values Lesson Overview In this lesson, you will learn about the functions and use of input processing for measured values.
Lesson Objectives After 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 Example In your company, there are particular requirements and stipulations for processing measured values. For example, particular measured values are to be rounded to a significant number of digits or a different value is to be calculated from the measured value entered using a formula.
Input Processing for Measured Values
Figure 42: Input Processing for Measured Values
98
© 2011 SAP AG. All rights reserved.
2011
PLM412
Lesson: Input Processing for Measured Values
Particular requirements for the determination and processing of measured values include: •
•
•
The measured value is to be changed after input (for example, it is to be multiplied by a specific factor or rounded according to customer-specific rules). The measured value that has been entered (original value) is to be output independently of the decimal places defined in the plan or master inspection characteristic. If, for example, two decimal places were planned in the inspection characteristic, but the measured value only has one decimal place, then only one decimal place will be output in results recording (output like input). The number of significant digits is not fixed. It is dependent on the actual measured size of the measured value. It must therefore be possible to control the rounding using a significance type that takes this dependency into consideration. A significance type can be defined as follows: –
• •
Result: 0GET_INSTANCE” call is still executed even if there are no implementations. The same applies to the method call that calls the method of the adapter class. You can only activate or deactivate an implementation in its original system without modification. The activation or deactivation must be transported into subsequent systems. If a Business Add-In can only have one implementation, there can still be more than one implementation in the same system. However, only one can be active at any time.
Figure 339: 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.
2011
© 2011 SAP AG. All rights reserved.
667
Appendix 2: Technical Details
PLM412
Figure 340: Business Add-In Definition: Properties
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 processed is not defined. Even if the business add-in does not support multiple use, you can still have more than one implementation for it. However, only one implementation can be active at a time. If you make a business add-in filter-dependent, you can make calls to it depending on certain conditions. You must specify the filter type in the form of a data element. The value table of the domain used by the data element contains the valid values for the implementation. When the enhancement method is called, a filter value must be passed to the interface.
668
© 2011 SAP AG. All rights reserved.
2011
PLM412
Appendix 2: Technical Details
Figure 341: Business Add-In Definition: Interface Methods
The system proposes a name for the interface and the generated class. You can, in principle, change the name of the interface to anything you like. However, your BAdI 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 Class Builder, where you can define the interface methods. A Business Add-In interface can have several interface methods.
2011
© 2011 SAP AG. All rights reserved.
669
Appendix 2: Technical Details
PLM412
Figure 342: 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 parameter flt_val for each method. Otherwise, you define the interface parameters you need for the enhancement.
Figure 343: Business Add-In Definition: Activating the Interface
670
© 2011 SAP AG. All rights reserved.
2011
PLM412
Appendix 2: Technical Details
Once you have finished working on your interface, you must activate it. This generates 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 the Business Add-In maintenance at any time (by choosing Utilities → Regenerate).
Figure 344: Default Implementation
A default implementation is executed whenever no active implementation of a Business Add-In exists. The default implementation is created by the enhancement provider. You can create a default implementation in the BAdI definition by choosing Goto → Default code. The system automatically generates a class with a predefined name. Implement the methods so that the required default behavior is generated. You can also create a sample implementation. This is a template that can be inserted into the methods of the implementation. You can create sample implementations by choosing Goto → Sample code. The system creates a class that implements the methods of the interface. The sample code is displayed for the user as a template.
2011
© 2011 SAP AG. All rights reserved.
671
Appendix 2: Technical Details
PLM412
BAdIs in Quality Management (1) •
BAdI QM_INPUT_PROCEDURE: Input processing –
•
Implementation QM_INPPROC_100: Output like input (as regards decimal places) – Implementation QM_INPPROC_200: Output according to significant digits BAdI QPAP_FLEX_PLAN: Flexible specification selection –
Characteristics and operations read in the standard can be changed before they are written to the database for an inspection lot. This means that you can change specifications such as target values, tolerances, and so on.
The implementation QM_INPROC_100 can be used in input processing when, for example, a measuring device only displays a result with a precision of one decimal place, but two decimal places were specified for the result. •
Example: Measured values are output with the same number of decimal places with which they were entered.
The implementation QM_INPROC_200 can be used in input processing if you are using a measuring device that has a higher precision than is specified. •
Example: Measured values are rounded to a predefined number of significant digits.
An implementation for the stability study for the BAdI QPAP_FLEX_PLAN already exists in the standard (BAdI QPAP_FLEX_PLAN_16). To use this function for other inspection lot origins, you must create a separate implementation for each inspection lot origin for which you want to use flexible inspection specifications. This is because the BAdI contains a filter for the inspection lot origin. Additional criteria for the application of flexible inspection specifications can be called in the implementation (for example, whether or not a manual sample calculation must be performed).
672
© 2011 SAP AG. All rights reserved.
2011
PLM412
Appendix 2: Technical Details
BAdIs in Quality Management (2) •
BAdI CEWB_TSK_UPDATE: Task List Maintenance and Checks in the EWB –
•
When you save the inspection plan in the Engineering Workbench, all of the inspection plan data is made available to a BAdI. BAdI CEWB_CHA_MENU_EXTERN: Menu Extensions in the Engineering Workbench –
•
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: Screen Extensions for Task Lists in the EWB Example: –
In the Engineering Workbench, you can maintain user-defined fields at characteristic-, operation-, and header level of the inspection plan.
BAdIs in Quality Management (3) •
BAdI CEWB_CHA_MENU_EXTERN: Menu Extensions in the Engineering Workbench –
•
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: VE: BAdI Subscreen for Display of Data on Screen 1101 –
•
In the transactions for the usage decision (create, change, display), additional data can be displayed in a subscreen of the header screen. A pushbutton can be used to call another function. BAdI QE_SAVE: Save Results –
During a save in results recording, all data in the relevant inspection lot is made available to a BAdI.
The BAdI QE_SAVE is not used in: • • • •
2011
Process-optimized results recording Results recording on the Web QM-IDI The corresponding BAPIs
© 2011 SAP AG. All rights reserved.
673
Appendix 2: Technical Details
PLM412
BAdIs in Quality Management (4) •
BAdI QPL1_SUBSCR_ADDON: Assignment of Add-On Data to Inspection Lot –
•
You can use additional subscreen areas to display any required data and change the inspection lot data in the structure QALS_ADDON. BAdI QPRS_ADDON_TAB: Process QPRS_ADDON Data in Dialog Using Additional Tab Page –
•
An additional tab page can be activated in the transactions for the physical-sample record (QPR1, QPR2, QPR3). This is dependent on the screen control key for the physical-sample type. You can use an additional subscreen area to display any required data and to change data for the structure QPRS_ADDON in the physical-sample record. BAdI QEEM_SUBSCREEN_5000: EE: BAdI Subscreen for Display of Data on Screen 5000 –
In the transactions for results recording (create, change, display), additional data can be displayed in a subscreen of the header screen. A pushbutton can be used to call another function.
BAdIs in Quality Management (5) •
BAdI QE_RESULT_VALUATION: Valuation of Single Values –
•
You can program your own rules for the valuation of characteristics and original values. BAdI QC_PROFILE_MAINTAIN: Certificate Profile Maintenance –
•
You can maintain additional customer-specific fields for the characteristics. – You can change the characteristic data in the certificate when you are copying characteristics into the certificate profile. BAdI QB_Q_INFO_RECORD: Summarize 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: Influence the Comparison of the QM Systems –
The required QM system in the procurement process can be checked using a program.
Using the BAdI QE_RESULT_VALUATION you can change a measured value when comparing it to the specified tolerance limits (for example, reject if measured value and tolerance limit are the same).
674
© 2011 SAP AG. All rights reserved.
2011
PLM412
Appendix 2: Technical Details
Using the BAdI QB_QM_SYSTEM_COMPARE, you can influence the check of the required QM system against the existing QM system. This BAdI is called just before the actual check and it allows you to change the following fields: • • • •
2011
Required QM system from the material master record Existing QM system of vendor Validity date of certification Delivery date
© 2011 SAP AG. All rights reserved.
675
Appendix 2: Technical Details
676
© 2011 SAP AG. All rights reserved.
PLM412
2011
Appendix 3 Business
Case
Figure 345: Task
Your company purchases a new material (see technical drawing) and inspects this material at goods receipt for the purchase order.
2011
© 2011 SAP AG. All rights reserved.
677
Appendix 3: Business
Case
PLM412
Create all of the QM data you need to inspect this material in accordance with your 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 parts for delivered quantities between 501 and 2000, and 35 parts for delivered quantities over 2000 pieces. During a “reduced inspection”, only 7 parts, 18 parts, and 22 parts are inspected for the same quantities. If 10 “normal inspections” are OK, the inspection scope can be reduced. After 20 OK inspections with a reduced inspection scope, the next 30 deliveries are not inspected. 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 inspection characteristics? 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?
Example: Conclusion •
678
The inspection plan is used to specify the inspection operations, the characteristics to be inspected during each operation, and the test equipment to be used.
© 2011 SAP AG. All rights reserved.
2011
Appendix 4 Additional Information
Contents: • • • • • •
Customer Enhancements status management Ease of Use Follow-Up Actions Evaluations Archiving
Figure 346: Program Enhancements
2011
© 2011 SAP AG. All rights reserved.
679
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)
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 347: Customer Enhancement Project
SAP application programmers create SAP enhancements using program exits, menu exits, and screen exits. An administration function is available to the SAP programmer for this purpose (transaction code SMOD). Customers can display a catalog of existing SAP enhancements and can combine the required enhancements to create an enhancement project. The customer uses an administration function for this purpose (transaction code CMOD).
680
© 2011 SAP AG. All rights reserved.
2011
PLM412
Appendix 4: Additional Information
Figure 348: SAP Procedure
SAP application programmers plan possible application enhancements in their applications and define the required components. They then combine these components to create SAP enhancements. Once they have created an SAP enhancement they document it in such a way that the customer can later implement the enhancement without extensive analysis of the program and screen sources.
2011
© 2011 SAP AG. All rights reserved.
681
Appendix 4: Additional Information
PLM412
Figure 349: Procedure at the Customer's Premises
Customers use the Project Management function to choose the SAP enhancement that they want to implement. They then process the individual components (also using the Project Management function) and document the entire enhancement project. Finally they activate the enhancement project (which in turn activates all components). Contents: • • • • •
682
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
© 2011 SAP AG. All rights reserved.
2011
PLM412
Appendix 4: Additional Information
Figure 350: 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 Physical sample
Figure 351: Status
2011
© 2011 SAP AG. All rights reserved.
683
Appendix 4: Additional Information
PLM412
The current processing status of an object is documented using one or more statuses. A status is an indicator with the following functions: • •
It indicates that a certain condition has been reached (for example, “Usage decision 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 more statuses for the affected object. You can set any number of statuses for an object.
Figure 352: status management
A system status is set by the system and informs the user that a certain function has been completed for an object. You cannot influence this status unless you carry 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 an inspection 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 the user status. The user status can be set or deleted manually or through business transactions.
684
© 2011 SAP AG. All rights reserved.
2011
PLM412
Appendix 4: Additional Information
Figure 353: Defining a Status Profile
Figure 354: Create
status profile
2011
© 2011 SAP AG. All rights reserved.
685
Appendix 4: Additional Information
PLM412
To create a status profile, proceed as follows: 1. 2. 3. 4.
5. 6.
Choose Edit → New Entry. Enter any status profile name. Enter a descriptive text. 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. This ensures that entries are complete and unique. Choose Enter to add the new status profile to the list. Choose Save.
Figure 355: Assigning Status Profile to Object Types
To be able to use a status profile for objects of a certain object type, you have to assign the status to the affected object type: 1. 2. 3. 4.
686
On the screen Change Status Profile: Overview, place the cursor on the status profile that you want to assign to an object type. Choose Goto → Object types Select object types for which the status profile can be used. Choose Save.
© 2011 SAP AG. All rights reserved.
2011
PLM412
Appendix 4: Additional Information
Figure 356: Define user status
You must enter a four-character (maximum length) language-dependent ID to identify each user status. For each user status, you can enter the following: 1. 2. 3. 4. 5.
6. 7. 8.
2011
Enter a status number in the Status number field. The status number determines the order in which the status of a status profile can be set. Enter a highest and lowest status number in the columns NONr and HONr. Enter a short text. The short text contains a short description of the status. Enter a long text for the user status. To do this, choose Goto -> Long text. 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 may define only one status with a status number as the initial status, but any number of statuses without a status number. In the Position column, define the position where the status is displayed in the toolbar of the inspection lot. . In the Priority column, define the priority of the user status if the same position is specified for more than one active status. Save your entries.
© 2011 SAP AG. All rights reserved.
687
Appendix 4: Additional Information
PLM412
Figure 357: Assigning User Status to Business Transactions
To assign business transactions to your user status, proceed as follows: 1. 2. 3. 4. 5.
Position the cursor on the user status. Choose Goto → Business transaction control. Choose Edit → New Entries to display a list of the available business transactions. Assign the appropriate transactions to your user status. You can “influence” the assignment by activating the following fields for each transaction: No infl., Allowed, Warning, Forbidd.. The following prerequisites must be fulfilled before a business transaction can be carried out:
6. 7.
688
• The transaction must be permitted by at least one active status. • The transaction must not be disallowed by any active status. Using “Follow-up actions” you can determine how a specific transaction affects the respective status when it is performed. Save your entries.
© 2011 SAP AG. All rights reserved.
2011
PLM412
Appendix 4: Additional Information
Figure 358: Selection profile
You can use selection profiles to define the status combinations for selecting objects (such as inspection lots). A selection profile is especially helpful if you want to repeatedly select a large number of objects according to the same selection criteria. 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 the corresponding 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 and are evaluated together. This block must fulfill at least one of the selection criteria. AND links these blocks or individual criteria. All blocks or individual criteria linked by AND must be fulfilled. An order is eliminated from the evaluation 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 at the beginning of the selection profile. Contents: • •
2011
Field Selection Variable lists
© 2011 SAP AG. All rights reserved.
689
Appendix 4: Additional Information
PLM412
Figure 359: Field Selection
Determine the name of the program, to which the screen belongs. To do this, call up the screen in question and choose System → Status. To find out which customer-defined field control is planned for which screen groups in a module pool, enter the name of the module pool in the maintenance function (transaction SFAC) and choose Display. The system displays a list of all the screen groups. You can display a list of modifiable fields for each screen group in the list. For the modifiable fields, you use indicators to define how each field is displayed on the screen.
690
© 2011 SAP AG. All rights reserved.
2011
PLM412
Appendix 4: Additional Information
Figure 360: 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 the list 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 create their own selection list from within the application transaction. This user-specific field selection does not belong to Customizing and does not have a transport link. If users do not define their own field selection, the fields that are selected in this step are displayed.
2.
2011
2. Object selection: You define the selection criteria used to select the objects for the list. For each function (transaction) that is directly executable from this list, you can define exactly one general variant with the accompanying selection criteria. The system saves this general variant as SAP_TCODE_xxxx. (xxxx is the transaction code that generates the respective list.) These general variants have an automatic transport link. In addition to the general variant, you can also define a user-specific variant for each executable function. The system saves this variant as U_. You can also define any number of other variants for each executable function and save them under any name (from within the application).
© 2011 SAP AG. All rights reserved.
691
Appendix 4: Additional Information
PLM412
Figure 361: Variable Lists (Field Selection)
You can change the list display using display variants. The following functions are available: • • • • • •
• •
692
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 be shown in the display variant above this Total column. You can use a clipboard to cut a field from the display fields or the hidden fields and paste it in the required place in the display fields. The columns can be grouped together in up to three rows.
© 2011 SAP AG. All rights reserved.
2011
PLM412
Appendix 4: Additional Information
Figure 362: 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 the program using this variant.
•
I (Hide field) selected: The corresponding selection criterion is not displayed at the start of the program using this variant. However, the selection criterion can still be supplied with values in the variant.
• •
N (Hide field until) L (Selection variable) selected: The selection criterion is supplied with values from the variant variables at the start of the program. To select variant variables, choose SELECTION VARIABLES.
•
P (Save field without values) selected: The value of the corresponding selection criterion is not changed in the program at the start using the variant or by getting a variant.
• •
2011
L (Switch SPA/GPA off) O (Required fields)
© 2011 SAP AG. All rights reserved.
693
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 within the quality notification. When the usage decision is made, a follow-up action is assigned to a code during maintenance of the selected set code. For a quality notification, a follow-up action is assigned to a code during maintenance of the task catalog.
Figure 363: Follow-Up Actions: Setting the User Status
A predefined business transaction can be assigned to a follow-up action. This involves transactions QM90 to QM99 when the usage decision is made. For the tasks, this includes transactions QN90 to QN99. Statuses can be assigned to these business transactions.
694
© 2011 SAP AG. All rights reserved.
2011
PLM412
Appendix 4: Additional Information
The statuses are set when you execute such a transaction.
Figure 364: Follow-Up Actions and Business Transactions Operation
Contents: • • • •
2011
Logical Databases ALV in list output Ad Hoc queries using QuickView Comparison of SAP Query and QuickView
© 2011 SAP AG. All rights reserved.
695
Appendix 4: Additional Information
PLM412
Figure 365: 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 the database. Instead of having to program access to the database yourself, you can use logical databases. The logical database retrieves the data records and makes them available to the ABAP Program.
Figure 366: Logical Database: Overview
696
© 2011 SAP AG. All rights reserved.
2011
PLM412
Appendix 4: Additional Information
An ABAP program that reads data for programs of type 1 from the database and displays them as records, is known as a logical database. During this process, the sequence in which the data is supplied to the programs is determined by a hierarchical structure. In addition, a logical database makes a selection screen available for the programs, (checking the user entries and error dialog). This screen can be configured in the programs. In release 4.0, there are approximately 200 logical databases in the standard system. As a part of namespace enhancement, a logical database's name has been extended 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 367: 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 generic functions. Since release 4.6C, there has been control-based further development of ALV ALV grid control.
2011
© 2011 SAP AG. All rights reserved.
697
Appendix 4: Additional Information
PLM412
The class CL_GUI_ALV_GRID contains methods for object-oriented programming. • •
• •
Data is displayed in simple lists by calling up the function module reuse_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 module reuse_alv_list_display. This function module issues an internal table with a structure 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 to be re-sorted, since these are transferred by reference. The module requires either a field catalog or an internal table with a dictionary structure, 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 the standard operations can be performed. You can make changes to the standard system to meet your requirements. Various function modules are available to process a list as required. Some of them are available for the individual setup of the list display, others are explicitly called by the ABAP List Viewer. The procedure used for hierarchically-sequential lists corresponds to the procedure used for simple lists.
698
© 2011 SAP AG. All rights reserved.
2011
PLM412
Appendix 4: Additional Information
Figure 368: Standard Call for ALV
This slide describes the basic process for creating a list. Descriptions of data in the internal 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 formatting options using the field catalog.
Figure 369: QuickViewer: Principle
The QuickViewer is a tool developed in 4.6A, which is used to create ad hoc reports. You start the QuickViewer by entering transaction SQV1. For example, the QuickViewer can use a database table or also a database view as 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.
2011
© 2011 SAP AG. All rights reserved.
699
Appendix 4: Additional Information
PLM412
The QuickViewer includes a link, for example, to the EIS, ABC analysis, or ALV grid control. The list can also be edited further in external programs, such as Microsoft Word. The created list can be saved and displayed again in the QuickViewer. The selection criteria can be stored for the saved list and can be called up at any time.
Figure 370: QuickViewer: Initial Screen
Each user creates their own QuickViews that are not visible to other users. As a result, the QuickViews of other users cannot be copied. You can change a QuickView into a SAP Query, if the QuickView uses a functional area from the standard area as a data source. The query is then visible to the user group. QuickViews are not linked to correction and transport systems.
700
© 2011 SAP AG. All rights reserved.
2011
PLM412
Appendix 4: Additional Information
Figure 371: Creating a QuickView
To create a QuickView, you must specify a data source. You can specify database tables, database views, logical databases, table joins, or functional areas for the SAP 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 by additional fields.
Figure 372: Join Definition: Graphic
If you specify a table join as a data source, then you must first define this join before you can create the list in the QuickViewer.
2011
© 2011 SAP AG. All rights reserved.
701
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 information being 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 a list, 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 are entries in table QALS, you link both tables using a left outer join logic. In this example, the left table is QALS. Alias tables enable you to use the same (database) table several times when defining the join.
Figure 373: Basis Mode: Basic Structure
The screen for the basis mode is split into 4 areas. The available fields (data source) are displayed in the upper left corner in the form of a tree. Further information on usage is displayed in the lower left corner of the screen. You can maintain the title and comments, and control output (list, Excel) in the upper right screen area. In this area, you can control the structure of the list, define the sort sequence, and enter selection criteria. You can switch to the online documentation in the lower right window.
702
© 2011 SAP AG. All rights reserved.
2011
PLM412
Appendix 4: Additional Information
Figure 374: Creating a QuickView in Basis Mode
You create the QuickView using two table controls. You select the required list fields in the right table control and transfer them to the left table control (Fields in 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 in the left table control and copy them to the right control. • • • • • • • •
2011
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
© 2011 SAP AG. All rights reserved.
703
Appendix 4: Additional Information
PLM412
Figure 375: Overview: Program and Query
If you create a list using a program (category 1), the data to be processed is, for example, created using a logical database, processed in the program, and then issued in a list. A query is an evaluation of data, which a user can create using the SAP Query tool without programming knowledge. The query takes you through a sequence of screens in which the line and list layout is described. From release 4.6A, you can graphically create query lists using the query painter. When the query is started, a program that corresponds to the list definition is automatically generated. This program reads and processes the required data, and issues it in the list. The program has the name AQmmbbbbbbbbbbbbqqqqqqqqqqqqqq. You can display the program name by choosing 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 '='.
704
© 2011 SAP AG. All rights reserved.
2011
PLM412
Appendix 4: Additional Information
Figure 376: Organization in the Query
The administrative tasks in the query environment include the creation of InfoSets and 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 query is referenced. InfoSets are often based on logical databases. Users may only create or start queries if they are assigned to at least one user group. A user can be assigned to several user groups. The users in one user group all have the same authorizations. The InfoSets are assigned to a user group, to which the users in this group have access. 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. A user in a user group has access to all queries that are created in that user group.
2011
© 2011 SAP AG. All rights reserved.
705
Appendix 4: Additional Information
PLM412
Figure 377: Creating a Query
If you are assigned to several user groups, you can change between these user groups. A query is always created using a specific InfoSet. This InfoSet area must be assigned 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 queries for this InfoSet. A query can only be copied from another user group into your own user group, if the 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 transaction SQ02. To create queries, use transaction SQ01.
706
© 2011 SAP AG. All rights reserved.
2011
PLM412
Appendix 4: Additional Information
Figure 378: 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 available database 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 to external auditors, potential reusability of data
• •
2011
Data deleted as a record from the tables Access to archived data controlled by the application
© 2011 SAP AG. All rights reserved.
707
Appendix 4: Additional Information
PLM412
Reorganization The term “reorganization” is from the time of R/2, when data was downloaded and then uploaded to optimize the physical distribution of data on the hard disk. During this operation, data that was no longer needed could be archived and deleted. Backup/Restore By “backup” we mean a backup of the database contents in case of breakdown. This enables you to restore the database status to the current status before the breakdown. As a rule, backups are run at fixed intervals according to a set procedure. The transfer of data back to the system is known as the 'restore' procedure. Archiving Using SAP ArchiveLink During archiving, scanned-in, incoming documents are archived in external systems using the SAP ArchiveLink. This is the same for outgoing documents created in the SAP System (for example, quality certificates) and print lists. You can display the archived documents and lists using the SAP ArchiveLink. In the data archiving function, there is an interface to the SAP ArchiveLink that you can use to store archive files in an external archive.
Figure 379: Server for Archiving and Deletion Jobs
The archiving program always runs in the background, primarily on a background server that is also a database server.
708
© 2011 SAP AG. All rights reserved.
2011
PLM412
Appendix 4: Additional Information
The deletion programs look for the next available background server. You must therefore always make sure that all application servers also have access to the used file systems. From release 4.5A, you can specify the server, on which the background jobs should be run.
Figure 380: 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 background job and copies it to the archive file. This operation continues until one of the following events occurs: 1. 2. 3.
Archiving is complete. Archiving is not yet complete, but the archive file has reached the size specified in Customizing. 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 ......
2011
© 2011 SAP AG. All rights reserved.
709
Appendix 4: Additional Information
PLM412
Figure 381: Archiving: Step 2 - Delete
After the first archive file has been closed, archive management opens a second archive file and proceeds with the archiving operation. At the same time, the system starts another program, which reads the archived records and deletes them 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 the created archive files. Since the archiving program does not alter any information contained in the database, (unlike the deletion program), the archiving program prepares archive files 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 more productively.
710
© 2011 SAP AG. All rights reserved.
2011
PLM412
Appendix 4: Additional Information
Figure 382: Archiving: Step 3 - Options for Storing Archived Information
Archive files whose data has been deleted in the database can be stored in various ways. Apart from using magnetic tape, the most frequently used methods are HSM Systems and archiving in an external system using the SAP ArchiveLink.
2011
© 2011 SAP AG. All rights reserved.
711
Appendix 4: Additional Information
PLM412
Figure 383: 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 the conditions at the time of archiving. Programs for creating archive files and deleting data in the database are contained 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
712
© 2011 SAP AG. All rights reserved.
2011
PLM412
Appendix 4: Additional Information
Figure 384: 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 session for this archiving object in the archive management function. You can schedule the background job for the archiving sessions directly using archive management. Alternatively, the jobs can also be scheduled within the application. The steps involved in archiving differ according to the archiving object. The initial run, postprocessing, and reloading are not supported by all archiving objects. When dealing with archiving objects which require a usage, you have to trigger these 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 you manage the archive files manually, to also control the data medium, in which the archive files are stored. You can use the Archive Information System (transaction SARI) to evaluate archiving sessions. Archiving Objects in QM
2011
•
QM_CHARACT
QM Master Inspection Characs
•
QM_CONTROL
Movement data for quality inspections
•
QM_METHOD
QM inspection methods
•
QM_PLAN
QM inspection plan
© 2011 SAP AG. All rights reserved.
713
Appendix 4: Additional Information
•
PLM412
•
QM_QMEL
Quality notification
•
QM_SAMPLE
Physical samples
•
QM_FMEA
Failure Mode and Effects Analysis
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 Settings for general archiving system Transaction SARI
• •
– Evaluating archive information structures – Status management in the archive information system – Customizing settings for archive information structure Customizing archiving in external archives Object-specific Customizing in the application
In Customizing for archive objects, the logical file name is the name, with which the 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 is dependent on the operation system. In the transaction FILE, you must enter the syntax group of the operation system that is being used. If an archive file is to be stored in an external archive, the physical path must correspond to the exchange index between the SAP System and the archive (basic path in the archive definition). The following slide shows how logical file names/logical file paths and physical file paths interact. It uses the example of an archiving object, whose files are to be stored in an external archive.
714
© 2011 SAP AG. All rights reserved.
2011
PLM412
Appendix 4: Additional Information
Figure 385: 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 status of historical versions for master records to status 4 within Archiving. The archiving process: –
–
2011
In the first step, the system automatically changes the status of the master records from 3 (locked) to 4 (can be archived). This step, however, only affects historical versions of the master records; the current versions can only be given status 4 manually. In the second step, the master records are archived and deleted.
© 2011 SAP AG. All rights reserved.
715
Appendix 4: Additional Information
PLM412
Figure 386: Organizing the Archiving of QM Movement Data
Figure 387: Archiving Session Checklist
716
© 2011 SAP AG. All rights reserved.
2011
Glossary business package Business packages are portal-based solutions that provide you with the relevant applications, information, and services to quickly install SAP NetWeaver Portal and connect back-end systems. Ramp-up Market introduction process of new products or new releases of SAP software Release to Customer Date that marks the initial availability of a new release for customers and the start of the restricted shipment phase. Restricted Shipment Phase First delivery phase for a new release. In the phase, the number of customers using the new release is increased in a controlled fashion. SAP Business Suite The SAP Business Suite includes a complete package of open enterprise applications that link all parties involved, information and processes, and therefore improve the effectiveness of your business relationships. SAP NetWeaver SAP NetWeaver is SAP's integration and application platform. It is the technical basis for almost all SAP applications at the moment. TCO Total cost of ownership Unrestricted shipment phase Second delivery phase for new software releases, in which all customers can request the new software.
2011
© 2011 SAP AG. All rights reserved.
717
Glossary
718
PLM412
© 2011 SAP AG. All rights reserved.
2011
Index Numerics/Symbols 8D report, 408
A account assignment objects, 535 action box, 391 Action Box, 474–475 Action Log, 507 Actions, 377 ALE, 135 alternative units of measure, 357 application log, 299 appraisal costs, 528 approval requirements, 242 automatic usage decision, 354
B batch status, 356 buyer’s negotiation sheet, 407
C calculated characteristic, 188 Calibration inspection, 175 catalog profile, 118, 120 Catalog profile, 404–405, 469–470 Catalog Profile, 329 catalog types, 106, 468 Catalog Types, 105 change documents, 210, 294 change master record, 241 change number, 240 characteristic, 441 conditional, 189 characteristic inspection, 79 characteristic mapping, 297 characteristic value, 441 characteristic values, 207
2011
characteristics, 595 additional, 293 Characteristics, 598 Class, 441 classification system, 379 Classification system, 441–442 client 000, 472 code group, 118 code groups, 107, 190 codes, 107 collective usage decision, 353 Confirmation profile, 330, 404 confirmation transaction, 438 Control Chart, 289 control charts, 579, 600 control indicator, 79 Copy Inspection Results function, 295 copy model complete, 187 incomplete, 187 cost reports, 536 customer analysis, 597 Customer complaint, 20, 416, 418, 421
D Data Transfer Workbench, 211 deadline monitoring, 556 defect codes, 327, 406 defect costs, 528, 534 defect item, 376, 441 defects recording, 9 Defects Recording, 327–328, 333–335, 402, 404, 406, 448–450 delivery, 419
© 2011 SAP AG. All rights reserved.
719
Index
PLM412
dependent follow-up function, 478 digital signature, 300 DIN ISO 2859-1, 39 DIN ISO 286-2, 82 DIN ISO 3951, 39 display variants, 572 document, 509 Document Management System, 130, 509 Dynamic modification, 36 dynamic modification at lot creation, 191 Dynamic modification at usage decision, 192 dynamic modification criteria, 52 dynamic modification level, 191 Dynamic Modification Rule, 51 Dynamic modification rules, 190
E Early Warning System, 592, 598 engineering change request, 241 Engineering Workbench, 227 Equipment, 174 evaluations, 9 event linkage, 559 Event-Controlled Processes, 3 exception, 593 exception analysis, 592
F faulty delivery, 388 FLEX, 253 Flexible Inspection Specifications, 250 FMEA, 105, 375 follow-up action, 508 function module, 477 function modules, 508
720
© 2011 SAP AG. All rights reserved.
G general QM order, 529 goods receipt inspection, 402 Group, 167 group counter, 167
H header level, 472 histogram, 573 History Management, 80
I immediate tasks, 421 individual QM order, 529 individual signature, 300 initial data transfer, 211 initial screen, 390, 419, 438 inspection characteristic, 77 inspection characteristic level, 193 inspection characteristic specifications specific, 186 inspection characteristics, 186, 193 inspection history, 573 Inspection instruction, 10, 12 inspection lot creation, 9 inspection lot data record, 9–10 Inspection lot origin, 32 inspection method, 128–129, 131 Inspection method, 186 Inspection Methods, 190 Inspection plan, 245 Inspection Plan, 166 inspection plan header, 167 inspection processing, 473 Inspection Processing, 4 inspection report, 303 Inspection results, 4 inspection setup, 30, 65 inspection specifications, 9 inspection stage change, 51 Inspection Type, 31–32
2011
PLM412
Index
internal problem notification, 437 Internet, 299 Internet Transaction Server (ITS), 418 IT practice, 637 IT scenario, 637 item level, 472
K Key figures, 595, 598
M maintenance plan, 176 mass maintenance, 65 master inspection characteristic, 77, 131 Master inspection characteristic, 190 master recipes, 247 Material Analysis, 597 material document, 390 Material specification, 139, 245 Material Specification, 139 material-task list assignment, 205 multistep tasks, 559
N notification category, 370–371, 465 notification item, 375–376 notification list, 473 notification origin, 371 Notification origin, 466 notification processing, 439, 509 notification systems, 370 notification type, 120, 331, 371, 471, 497 Notification Type, 466, 468–469 notification types, 370
O Object, 441 object types, 241
2011
Operations, 168 order type, 536
P partner function, 374 partner type, 374 posting proposal, 351 principle of dual control, 289 print control, 484 Print Control, 483 Problem processing, 17 process-optimized results recording, 290 Processing status, 284 product structure, 140 product structure browser, 208 production order, 438 production resources/tools, 174 purchasing document, 390
Q QM information system, 590, 596 QM order, 527–528 QM-IDI Interface, 304 QM-STI Interface, 599 QMIS, 596 qualitative, 77 quality costs, 536 quality improvement, 19 quality level, 51 quality notification, 389 Quality notification, 19, 470 quality notification type, 120, 469 Quality notifications, 18, 570 Quality Score, 355 quantitative, 77
R Ramp-up, 632 recording configuration, 286 Reference characteristic, 187 reference operation set, 207 related notifications, 473
© 2011 SAP AG. All rights reserved.
721
Index
PLM412
Release to Customer, 632 repair order, 421–422 report type, 120 Report type, 330, 404–405, 469 request to deviate from specification, 440 response profile, 506 Restricted Shipment Phase, 632 Results, 4 results data origin, 297 results history, 600 results recording, 9, 328, 600 Results Recording, 280, 282 return, 421 return delivery, 392, 422 returns and repairs processing, 423 Returns and Repairs Processing, 421 routings, 247 run chart, 573
S sales order, 419 sales summary, 420 sample determination, 9 Sample Determination, 35–36 Sample size, 37 Sample-drawing instruction, 10, 12 Sampling Procedure, 37 Sampling scheme, 39 Sampling tables, 39 sampling type, 38 SAP Business All-in-One, 624 SAP Business ByDesign, 623 SAP Business One, 623 SAP Business Workflow, 555 SAP NetWeaver, 636 screen groups, 510 screens, 471 Selected set, 115, 117 selected sets, 350 selection variant, 571
722
© 2011 SAP AG. All rights reserved.
service order, 423 service profile, 506 shop papers, 484 signature strategies, 300 skip, 51 source inspection lot, 296 SPC Functions, 569 stage change, 51 Standard analyses, 591 standard info structures, 594 status management, 379, 496 Status profile, 496–497 stock postings, 349, 356 Support Package, 632 system status, 495
T Tab, 471 tab pages, 471 target inspection lot, 297 Task List Header, 167 task list headers, 229 test equipment, 174 Test Equipment, 168 tolerance key, 82 tolerance specifications, 288 transfer log, 299 transfer posting, 391 TREX, 570
U UD codes, 347 Unrestricted shipment phase, 632 usage decision, 9, 347 Usage Decision, 4 User status, 495, 497
V validity status, 81 valuation mode, 37–38, 288 vendor analysis, 597 vendor complaint, 393 vendor evaluation, 407–408
W work area, 227 work center, 171
2011
PLM412
Index
work centers, 169 work environment, 227 workflow scenario, 556
2011
workflow template, 557 worklists, 570
© 2011 SAP AG. All rights reserved.
723
Index
724
PLM412
© 2011 SAP AG. All rights reserved.
2011
Feedback SAP AG has made every effort in the preparation of this course to ensure the accuracy and completeness of the materials. If you have any corrections or suggestions for improvement, please record them in the appropriate place in the course evaluation.
2011
© 2011 SAP AG. All rights reserved.
725
View more...
Comments
