Quality Management PDF

Copyright(c) 2018 by Nixon Vunganai.
All rights reserved.
Neither this document nor any part of it may be copied or reproduced in any form or by any
means or translated into another language, without the prior consent of Nixon Vunganai. The
information contained in this document is subject to change without notice.
WHATSAPP +255738656506
INTRODUCTION 14
23 QUALITY MANAGEMENT 16
23.1 BASIC SETTINGS 16
23.1.1 FIRST STEPS 17

23.1.2 SETTING UP CLIENTS 19
23.1.3 MAINTAIN SETTINGS AT CLIENT LEVEL 22
23.1.4 ESTABLISH ORGANIZATIONAL UNITS (PLANTS, ...) 22
23.1.5 MAINTAIN SETTINGS AT PLANT LEVEL 24
23.1.6 AUTHORIZATIONS 25
23.2 QM IN LOGISTICS 27
23.2.1 QM IN PROCUREMENT 27
23.2.1.1 DEFINE CONTROL KEYS 29
23.2.1.2 DEFINE KEYS FOR CERTIFICATE PROCESSING 30
23.2.1.3 DEFINE DELIVERY BLOCK 30
23.2.1.4 DEFINE DOCUMENT TYPES 31
23.2.1.5 DEFINE QM SYSTEMS 32
23.2.1.6 DEFINE STATUS OF SUPPLY RELATIONSHIPS 33
23.2.1.7 DEFINE LIST VARIANTS 35
23.2.2 QM IN PRODUCTION 35
23.2.3 QM IN SALES AND DISTRIBUTION 36
23.3 QUALITY PLANNING 36
23.3.1 BASIC DATA 38

23.3.1.1 CATALOG 39
23.3.1.1.1 Define Defect Classes 41
23.3.1.1.2 Define Catalog Types 42
23.3.1.1.3 Edit Catalogs 43
23.3.1.2 INSPECTION CHARACTERISTIC, INSPECTION METHOD 43
23.3.1.2.1 Define Default Values for Control Indicators 45
23.3.1.2.2 Define Characteristic Weighting 46
23.3.1.2.3 Define Inspector Qualification 47
23.3.1.2.4 Define Tolerance Keys 47
23.3.1.2.5 Define Estimation Procedure for Fraction of Defects 48
23.3.1.2.6 Define Number Range 49
23.3.1.2.7 Define List Variants 50
23.3.1.2.8 Define Specification Determination Rule 50
23.3.1.3 SAMPLE, SPC 50
23.3.1.3.1 Define Sample Determination 53
23.3.1.3.2 Define Inspection Severities 55
23.3.1.3.3 Define Valuation Mode 55
23.3.1.3.4 Statistical Process Control 58
23.3.1.3.4.1 Define SPC Criteria 59
23.3.1.3.4.2 Define Control Chart Type 60
23.3.1.3.4.3 Define Number Range 61
23.3.2 INSPECTION PLANNING 61
23.3.2.1 GENERAL 62
23.3.2.1.1 Assign Task List Types to Material Types 63
23.3.2.1.2 Define Task List Usages 63
23.3.2.1.3 Define Task List Status 64
23.3.2.1.4 Define Planner Group 65
23.3.2.1.5 Define Overview Variants 65
23.3.2.1.6 Maintain Profiles for Default Values 66
23.3.2.1.7 Define Field Selection 67
23.3.2.1.8 Define Text Widths 67
23.3.2.1.9 Maintain Parameters for Task List Type 67
23.3.2.1.10 Maintain Number Ranges for Inspection Plans 68
23.3.2.1.11 Copy Inspection Plan from External System 69
23.3.2.1.12 Define Identifier for Inspection Points 70
23.3.2.1.13 Multiple Specifications 72
23.3.2.1.13.1 Define Object Types for Multiple Specifications 72
23.3.2.1.13.2 Define Objects for Multiple Specifications 73
23.3.2.2 OPERATION 74
23.3.2.2.1 Define Control Keys for Inspection Operations 74
23.3.2.2.2 Define User Fields 75
23.3.2.2.3 Define Reduction Strategies for Scheduling 75
23.3.2.2.4 Work Center 76
23.3.2.2.4.1 Maintain Standard Text Keys 77
23.3.2.2.4.2 Define Qualifications 77
23.3.2.2.5 Inspection Characteristic 78
23.3.2.2.5.1 Define Inspection-Characteristic Origin 78
23.3.2.2.5.2 Define Control Methods 78
23.3.2.2.5.3 Define Response Plans 79
23.3.2.2.6 Test Equipment 79
23.3.3 ENGINEERING WORKBENCH 80
23.3.3.1 DEFINE WORK AREAS 81
23.3.3.2 DEFINE PRINT LAYOUT FOR MICROSOFT WORD 81
23.3.3.3 DEFINE FIELD SELECTION 84
23.3.4 FAILURE MODE AND EFFECTS ANALYSIS (FMEA) 84
23.3.4.1 SYSTEM MODIFICATIONS 84
23.3.4.1.1 Status Profile for User Status 84
23.3.4.1.2 Field Selection 84
23.3.4.1.3 Coding Mask 85
23.3.4.1.4 Business Add-Ins (BAdIs) 85
23.3.4.1.4.1 BAdIs for Archiving 85
23.3.4.1.4.1.1 BAdI: Write Add-On-Specific Data 85
23.3.4.1.4.1.2 BAdI: Read Add-On-Specific Data 85
23.3.4.1.4.1.3 BAdI: Delete Add-On-Specific Data 86
23.3.4.1.4.1.4 BAdI: Add-On-Specific Checks 86
23.3.4.1.4.2 BAdIs Inside the Application 87
WHATSAPP +255738656506
23.3.4.1.4.2.1 Definition of Text Types for Each Audit Component 87
Text determination procedure/Object types Description 87
23.3.4.1.4.2.2 Enhancement for Search Helps 88
23.3.4.1.4.2.3 Maintenance of Help Links 89
23.3.4.1.4.2.4 Provide Signature for FMEA 90
23.3.4.1.4.2.5 Influence Generation of FMEA Actions and List Items 90
23.3.4.1.4.2.6 BAdI: Restriction of Partner Roles for FMEA Object Types 91
23.3.4.1.4.3 BAdIs for FMEA Objects and for Valuation 91
23.3.4.1.4.3.1 Valuation of Audit (Key Figure Calculation) 91
23.3.4.1.4.3.2 Definition and Structure of an Audit Object 93
23.3.4.1.4.4 BAdIs for Manipulating Individual Objects 94
23.3.4.1.4.4.1 Definition of Action Types 94
23.3.4.1.4.4.1.1 BAdI for Definition of Action Types 94
23.3.4.1.4.4.1.2 Define Action Types 95
23.3.4.1.4.4.2 Definition of List Item Types 95
23.3.4.1.4.4.2.1 BAdI for Definition of List Item Types 95
23.3.4.1.4.4.2.2 Define List Item Types 96
23.3.4.1.4.4.3 Definition of Structure Types 96
23.3.4.1.4.4.3.1 BAdI: Structural View for Investigations (Audit, FMEA...) 96
23.3.4.1.4.4.3.2 Definition of Structure Types 97
23.3.4.1.4.4.4 BAdI: Additional Tab Page in FMEA Cockpit 97
23.3.4.1.4.4.5 BAdI: Assign Question Lists to an Investigation (Audit, FMEA,...) 97
23.3.4.1.4.4.6 Identification of Audit Components (Number Assignment) 98
23.3.4.1.4.4.7 BAdI for Functional Enhancement of Investigation Type (Audit Type,...) 100
23.3.4.1.4.4.8 Linkage of Objects with the Corrective Action 100
23.3.4.1.4.5 BAdIs for Updating a Further System or Table 101
23.3.4.1.4.5.1 XML Generation 101
23.3.4.1.4.5.2 FMEA: Adjustment of Monitor & Lists 103
23.3.4.1.4.5.3 Create, Change, and Delete Question Lists 103
23.3.4.1.4.5.4 Create, Change, and Delete Actions 105
23.3.4.1.4.6 General BAdIs 106
23.3.4.1.4.6.1 Scheduling of Background Jobs 106
23.3.4.1.4.6.2 Authorization Assignment in FMEA Processing 107
23.3.4.2 LISTS 108
23.3.4.2.1 Valuation Specifications 108
23.3.4.2.2 Structure of List of Questions 109
23.3.4.2.3 Priorities 110
23.3.4.2.4 List Structure 110
23.3.4.3 FMEA DEFINITION 110
23.3.4.3.1 Rating 110
23.3.4.3.2 FMEA Types 110
23.3.4.4 CONTROL DATA 111
23.3.4.4.1 Data Objects: Define Residence Time 111
23.3.4.4.2 Define Partner Functions 111
23.3.4.4.3 Authorization Groups 112
23.3.4.4.4 Data Objects: Properties, Forms 112
23.3.4.4.5 Specify Number Range Intervals for BAdI Implementation 112
23.3.4.4.6 Digital Signature 113
23.3.4.4.6.1 Settings in User Maintenance 113
23.3.4.4.6.2 Signature Strategy 114
23.3.4.4.6.2.1 Define Authorization Groups 114
23.3.4.4.6.2.2 Define Individual Signatures 115
23.3.4.4.6.2.3 Define Signature Strategies 115
Predecessor Signatures 117
23.3.4.5 RISK ANALYSIS 119
23.3.4.5.1 Activate BC Sets for FMEA Risk Analysis 119
23.3.4.5.2 Define Risk Matrixes 119
23.3.4.5.3 Define Risk Analysis Profiles 120
23.3.5 CONTROL PLAN 121
23.3.5.1 DEFINE CONTROL PLAN TYPES 121
23.3.5.2 DEFINE CONTROL METHODS 121
23.3.5.3 DEFINE RESPONSE PLANS 122
23.3.5.4 DEFINE STRUCTURE TYPES 122
23.3.5.5 NUMBER RANGE FOR CONTROL PLAN 122
23.3.5.6 STATUS PROFILE FOR USER STATUS 122
23.3.5.7 DEFINE PARTNER FUNCTIONS 123
23.3.5.8 BUSINESS ADD-INS (BADIS) 123
23.3.5.8.1 Define Object Categories 123
23.3.5.8.2 Implement Object Categories 123
23.3.5.8.3 Define Process Types 124
23.3.5.8.4 Implement Process Categories 124
23.3.5.8.5 Define Inspection-Characteristic Origin 125
23.3.5.8.6 Implement Inspection-Characteristic Origin 125
23.3.5.8.7 Enhance Application 126
23.4 QUALITY INSPECTION 126
23.4.1 INSPECTION LOT CREATION 128

23.4.1.1 MAINTAIN INSPECTION TYPES 130
23.4.1.2 MAINTAIN INSPECTION LOT ORIGINS AND ASSIGN INSPECTION TYPES 131
23.4.1.3 MAINTAIN NUMBER RANGES 132
23.4.1.4 DEFINE DEFAULT VALUES FOR INSPECTION TYPE 133
23.4.1.5 INSPECTION FOR GOODS MOVEMENTS 134
23.4.1.6 INSPECTION FOR DEADLINE MONITORING OF BATCHES 135
23.4.1.7 INSPECTION FOR MANUFACTURING ORDER 136
23.4.1.8 INSPECTION FOR EXTERNAL PROCESSING 137
23.4.1.9 INSPECTION AT SHIPPING 138
23.4.1.10 DEFINE INSPECTIONS IN PLANT MAINTENANCE 139
23.4.2 INSPECTION LOT COMPLETION 140
23.4.2.1 MAINTAIN CATALOGS FOR USAGE DECISIONS 141
23.4.2.2 DEFINE QUALITY SCORE PROCEDURE 142
23.4.2.3 PLAN AUTOMATIC USAGE DECISION 144
23.4.2.4 DEFINE FOLLOW-UP ACTIONS 145
23.4.2.5 DEFINE INVENTORY POSTINGS 147
23.4.2.6 TRANSFER INSPECTION DECISION TO BATCH 149
23.4.3 STATUS MANAGEMENT 149
WHATSAPP +255738656506
23.4.3.1 DEFINE STATUS PROFILE 150
23.4.3.2 DEFINE SELECTION PROFILE 150
23.4.4 DEFINE APPRAISAL COST RECORDING 151
23.4.5 SAMPLE MANAGEMENT 152
23.4.5.1 DEFINE PHYSICAL-SAMPLE TYPES 152
23.4.5.2 DEFINE NUMBER RANGE 153
23.4.5.3 MAINTAIN SCREEN CONTROL KEY FOR SAMPLE TYPES 154
23.4.5.4 DEFINE PHYSICAL-SAMPLE CONTAINER 154
23.4.5.5 DEFINE PHYSICAL-SAMPLE LOCATIONS 154
23.4.6 DEFINE PRINT CONTROL, FORMS, PRINT PROGRAMS 154
23.4.7 RESULTS RECORDING 160
23.4.7.1 DEFINE RECORDING CONFIGURATION 160
23.4.7.2 DEFINE ORIGINS OF RESULTS DATA 161
23.4.7.3 SUPPLEMENT ATTRIBUTES OF INSPECTION CHARACTERISTIC RESULTS 162
23.4.7.4 DEFINE PARAMETERS FOR CALCULATED CHARACTERISTICS 162
23.4.7.5 DEFINE PARAMETERS FOR INPUT PROCESSING 163
23.4.7.6 ENTER IDENTIFIER FOR UNITS TO BE INSPECTED 164
23.4.7.7 DEFINE FILTER FOR INSPECTION CHARACTERISTICS 164
23.4.7.8 DEFINE NUMBER RANGES FOR CHARACTERISTIC CONFIRMATION 165
23.4.7.9 MAKE SETTINGS FOR OPERATION COMPLETION 166
23.4.8 MAKE SETTINGS FOR COPY OF INSPECTION RESULTS 166
23.4.9 DYNAMIC MODIFICATION 166
23.4.9.1 DEFINE REFERENCE DYNAMIC MODIFICATION LEVEL 167
23.4.10 INFORMATION SYSTEM 167
23.4.10.1 DEFINE UPDATE FOR EACH ORIGIN 169
23.4.10.2 DIVIDE QUALITY SCORES INTO CLASSES 169
23.4.11 LIST DEFINITION 170
23.4.11.1 DEFINE VARIANTS (LIST VIEW FUNCTION) 170
23.4.11.2 DEFINE VARIANTS (WITHOUT LIST VIEW FUNCTION) 170
23.4.12 ACTIVATE WORKFLOW TEMPLATE 170
23.4.13 SUBSYSTEMS 170
23.4.13.1 PROCESS QUALITY INSPECTIONS USING QM-IDI INTERFACE 171
23.4.13.2 RETRIEVE CHARACTERISTIC RESULTS VIA PC INTERFACE 173
23.4.13.3 TRANSFER DATA VIA AN ELECTRONIC COUPLER 175
23.4.13.4 DEFINE EVALUATION METHOD FOR QM-STI INTERFACE 176
23.5 QUALITY CERTIFICATES 178
23.5.1 CERTIFICATE PROFILE 182

23.5.1.1 DEFINE STATUS PROFILE FOR CERTIFICATE PROFILES 183
23.5.1.2 DEFINE CERTIFICATE TYPES 184
23.5.1.3 MAINTAIN FORM 184
23.5.1.4 DEFINE DATA ORIGIN 185
23.5.1.5 DEFINE CONFIGURATION OF CHARACTERISTICS FIELD 186
23.5.1.6 PROFILE DETERMINATION 187
23.5.1.6.1 Condition Table for Profile Determination 187
23.5.1.6.1.1 Define Field Catalog for Profile Determination 188
23.5.1.6.1.2 Edit Condition Tables for Profile Determination 188
23.5.1.6.2 Define Access Sequence for Profile Determination 189
23.5.1.6.3 Define Condition Type for Profile Determination 189
23.5.1.6.4 Define Scheme for Profile Determination 189
23.5.1.6.5 Define Number Range for Condition Records 190
23.5.2 OUTPUT DETERMINATION 190
23.5.2.1 CONDITION TABLES FOR OUTPUT DETERMINATION 190
23.5.2.1.1 Define Field Catalog for Output Determination 190
23.5.2.1.2 Edit Condition Tables for Output Determination 191
23.5.2.2 DEFINE ACCESS SEQUENCES FOR OUTPUT DETERMINATION 192
23.5.2.3 DEFINE CONDITION TYPES FOR OUTPUT DETERMINATION 192
23.5.2.4 DEFINE EXCLUSION CONDITIONS 193
23.5.2.5 OUTPUT DETERMINATION PROCEDURE 194
23.5.2.5.1 Edit Output Determination Procedure 194
23.5.2.5.2 Assign Output Determination Procedure to Delivery Item Category 195
23.5.2.6 DEFINE PARTNER FOR EACH OUTPUT 195
23.5.3 PROCESS OUTPUT 196
23.5.3.1 SET PRINT PARAMETERS 196
23.5.3.2 DISPATCH TRIGGER 197
23.5.3.2.1 Define Variants for Selection Report 197
23.5.3.2.2 Define Batch Request 197
23.5.3.3 ASSIGN PRINT PROGRAM TO OUTPUT TYPE/MEDIUM 198
23.5.3.4 DEFINE OUTPUT TYPES WITH CERTIFICATE 199
23.5.3.5 ASSIGN SENDER TEXTS TO PROCESSING PROGRAM 199
23.5.3.6 DEFINE ARCHIVE LINK 200
Business Object | Document Type 200
23.5.3.7 DEFINE IDOC PROCESSING 201
23.5.3.7.1 Define Ports 202
23.5.3.7.2 Define Partners 203
23.5.3.7.3 Activate Workflow Template 203
23.6 QUALITY NOTIFICATIONS 204
23.6.1 OVERVIEW OF NOTIFICATION TYPE 205

23.6.2 NOTIFICATION CREATION 206
23.6.2.1 NOTIFICATION TYPE 206
23.6.2.1.1 Define Notification Types 207
23.6.2.1.2 Define Number Ranges 208
23.6.2.1.3 Define Screen Templates 209
23.6.2.1.4 Allocate Start Values for Transactions 211
23.6.2.1.5 Define Allowed Changes of Notification Type 211
23.6.2.1.6 Define Notification Process 212
23.6.2.2 NOTIFICATION CONTENT 213
23.6.2.2.1 Maintain Catalogs 213
23.6.2.2.2 Define Catalog Profile 214
23.6.2.2.3 Catalogs and Catalog Profiles for Notification Type 215
23.6.2.2.4 Assign Code Groups to Disciplines 216
23.6.2.3 PARTNERS 216
WHATSAPP +255738656506
23.6.2.3.1 Define Partner Determination Procedures 216
23.6.2.3.2 Define Fields for Partner Lists 218
23.6.2.3.3 Define Standard Messages to Partners 218
23.6.3 NOTIFICATION PROCESSING 219
23.6.3.1 RESPONSE CONTROL 220
23.6.3.1.1 Define Priorities 220
23.6.3.1.2 Define Response Monitoring 221
23.6.3.2 ASSIGNED OBJECTS 221
23.6.3.2.1 Define Object Categories 221
23.6.3.2.2 Business Add-In for Implementing an Object Category 222
23.6.3.2.3 Assign Object Categories for a Notification Type 224
23.6.3.3 ADDITIONAL NOTIFICATION FUNCTIONS 224
23.6.3.3.1 Define Action Box 224
23.6.3.3.2 Define Follow-Up Actions for Tasks 226
23.6.3.4 PRINT CONTROL 228
23.6.3.4.1 Define Shop Papers, Forms, Print Programs 228
23.6.3.4.2 Define Printer 229
23.6.3.4.3 Define Download 230
23.6.3.5 STATUS MANAGEMENT 231
23.6.3.5.1 Define Status Profile 231
23.6.3.5.2 Define Selection Profiles 232
23.6.3.6 LIST DEFINITION 233
23.6.3.6.1 Define Variants for Single-Level Lists 233
23.6.3.6.2 Choose Fields for Multilevel Lists 233
23.6.3.7 DIGITAL SIGNATURE 233
23.6.3.7.1 Specify Digital Signature 233
23.6.3.7.2 Define Signature Remarks 234
23.6.3.8 ACTIVATE WORKFLOW TEMPLATE 235
23.6.3.9 DEFINE COSTING PARAMETERS 235
23.6.4 DEFECTS RECORDING 236
23.6.4.1 DEFINE NOTIFICATION TYPE 237
23.6.4.2 DEFINE CONFIRMATION PROFILE 239
23.6.4.3 DEFINE REPORT TYPE 240
23.6.5 INFORMATION SYSTEM 242
23.6.5.1 DEFINE UPDATE IN QM INFORMATION SYSTEM 242
23.6.5.2 ACTIVATE REFERENCE TO RELATED NOTIFICATIONS 243
23.6.5.3 DEFINE NONCONFORMITY COSTS FOR SUPPLIER EVALUATION 244
23.6.6 USING NOTIFICATIONS 245
23.6.6.1 PROCESS RETURN DELIVERY TO VENDOR 245
23.6.6.2 PROCESS CUSTOMER REPAIR ORDER 248
23.7 QUALITY CONTROL 250
23.7.1 QUALITY MANAGEMENT INFORMATION SYSTEM 251

23.7.2 SUPPLIER EVALUATION 251
23.7.3 DEFINE VIEW IMPLEMENTATIONS FOR EVALUATIONS OF ORIGINAL DOCUMENTS 252
23.7.4 DEFINE DATA DEFINITION FOR EVALUATIONS OF ORIGINAL DOCUMENTS 252
23.7.5 DEFINE VIEW TYPES FOR EVALUATIONS OF ORIGINAL DOCUMENTS 253
23.7.6 DEFINE GRAPHIC TYPES FOR EVALUATIONS OF ORIGINAL DOCUMENTS 253
23.8 TEST EQUIPMENT MANAGEMENT 253
23.8.1 DEFINE LIST VARIANTS 253
23.9 STABILITY STUDY 254
23.9.1 BASIC DATA 254

23.9.1.1 DEFINE PRIMARY PACKAGING 254
23.9.1.2 DEFINE PHYSICAL-SAMPLE CONTAINER 254
23.9.1.3 DEFINE STORAGE CONDITIONS 254
23.9.1.4 DEFINE STORAGE LOCATIONS 255
23.9.1.5 DEFINE BILL OF MATERIAL USAGE 255
23.9.2 SAMPLES FOR STABILITY STUDY 256
23.9.2.1 DEFINE PHYSICAL-SAMPLE TYPES 256
23.9.3 TESTING SCHEDULE FOR STABILITY STUDY 256
23.9.3.1 DEFINE TESTING SCHEDULE CATEGORY 256
23.9.4 QUALITY NOTIFICATION FOR STABILITY STUDY 258
23.9.4.1 OPEN STABILITY STUDY 258
23.9.4.1.1 Notification Type and Catalogs 258
23.9.4.1.1.1 Define Notification Types 258
23.9.4.1.1.2 Define Number Ranges 258
23.9.4.1.1.3 Define Screen Templates 259
23.9.4.1.1.4 Maintain Catalogs 259
23.9.4.1.1.5 Catalogs for Notification Type 260
23.9.4.1.2 Partner 260
23.9.4.1.2.1 Define Partner Determination Procedures 260
23.9.4.1.2.2 Define Fields for Partner Lists 262
23.9.4.2 PERFORM STABILITY STUDY 262
23.9.4.2.1 Notification Functions 262
23.9.4.2.1.1 Define Priorities 262
23.9.4.2.1.2 Define Action Box 263
23.9.4.2.1.3 Define Follow-Up Actions for Tasks 265
23.9.4.2.2 Print Control 265
23.9.4.2.2.1 Define Shop Papers, Forms, Print Programs 265
23.9.4.2.2.2 Define Printer 265
23.9.4.2.2.3 Define Download 266
23.9.4.2.3 Status Management 266
23.9.4.2.3.1 Define Status Profile 266
23.9.4.2.3.2 Define Selection Profiles 268
23.9.5 STABILITY TEST 268
23.9.5.1 CREATE INSPECTION LOT 268
23.9.5.1.1 Maintain Inspection Types 268
23.9.5.1.2 Maintain Inspection Lot Origins and Assign Inspection Types 269
WHATSAPP +255738656506
23.9.5.1.3 Maintain Number Ranges 270
23.9.5.1.4 Define Default Values for Inspection Type 270
23.9.5.2 COMPLETE INSPECTION LOT 271
23.9.5.2.1 Maintain Catalogs for Usage Decisions 271
23.9.5.2.2 Define Follow-Up Actions 271
23.9.6 SYSTEM MODIFICATIONS 272
23.9.6.1 LIST DEFINITION FOR STABILITY STUDY 272
23.9.6.2 ACTIVATE WORKFLOW TEMPLATE 274
23.9.6.3 BUSINESS ADD-INS FOR STABILITY STUDY 275
23.10 ENVIRONMENT 275
23.10.1 SETTINGS 275

23.10.1.1 SET UP SIDE PANELS FOR QUALITY MANAGEMENT 275
23.10.1.2 DEFINE TEXT FORMATS 277
23.10.1.3 SUPPLEMENT UNITS OF MEASUREMENT AND UNITS OF MEASURE 277
23.10.2 CENTRAL FUNCTIONS 278
23.10.2.1 SIGNATURE STRATEGY 279
23.10.2.1.1 Define Authorization Groups 279
23.10.2.1.2 Define Individual Signatures 280
23.10.2.1.3 Define Signature Strategies 280
Predecessor Signatures 282
23.10.2.1.4 Define Signature Remarks 284
23.10.2.2 AUTHORIZATION MANAGEMENT 285
23.10.2.2.1 Define User Authorizations 285
Functions for... authorization object 286
23.10.2.2.2 Define Authorization Groups and Digital Signature 288
23.10.2.3 DEFINE DOCUMENT TYPES 290
23.10.2.4 MAINTAIN QM ORDER TYPES 291
23.10.2.5 GENERAL STATUS MANAGEMENT 294
23.10.2.5.1 Define Status Profile 294
23.10.2.5.2 Define Selection Profile 302
23.10.2.6 ACTIVATE WORKFLOW 304
23.10.2.7 ORGANIZE ARCHIVING 307
23.10.2.8 BUSINESS ADD-INS FOR ARCHIVING 309
23.10.2.8.1 Archiving Object QM_SAMPLE: Preprocessing 309
23.10.2.8.2 Archiving Object QM_SAMPLE: Archiving Run and Deletion Run 309
23.10.3 TOOLS 309
23.10.3.1 LIST DEFINITION 310
23.10.3.2 SYSTEM MODIFICATION 312
23.10.3.2.1 Adapt Search Help 313
23.10.3.2.2 Adapt Field Selection 313
23.10.3.2.3 Display Overview of Form 316
23.10.3.3 DELETE PROTOCOLS FROM APPLICATION LOG 316
23.10.3.4 EVALUATE TABLE HISTORY 317
23.10.3.5 FUNCTIONAL ENHANCEMENT (CUSTOMER EXIT) 317
23.10.3.6 BUSINESS ADD-INS 318
23.10.3.6.1 Switch for Selection of Business Add-In Implementation 318
23.10.3.6.2 QM in Logistics 318
23.10.3.6.2.1 Business Add-In for Comparison of QM Systems 318
23.10.3.6.2.2 Business Add-In for Grouping Together of Quality Information Records 319
23.10.3.6.3 Quality Planning 319
23.10.3.6.3.1 BAdI: Creation of Inspection Plans from 3D Models 319
23.10.3.6.3.2 Business Add-In for Input Processing 320
23.10.3.6.3.3 Business Add-In for Maint. of Customer-Specific Fields at Char. Level (EWB) 321
23.10.3.6.3.4 Business Add-In When Saving Inspection Plan (EWB) 321
23.10.3.6.3.5 Business Add-In for Menu Enhancements in the EWB 321
23.10.3.6.3.6 Business Add-In for Specification Determination Rule 321
23.10.3.6.3.7 Business Add-Ins for Creating Inspection Plans from External Sources 322
23.10.3.6.3.7.1 BAdI: Copy Source Data for Creating Master Inspection Characteristics 322
23.10.3.6.3.7.2 BAdI: Create Inspection Plan from External Data Source 323
23.10.3.6.4 Quality Inspection 324
23.10.3.6.4.1 Business Add-In for Output Control of QM Print Report 324
23.10.3.6.4.2 Business Add-In for Inspection Lot Processing 325
23.10.3.6.4.3 Business Add-In for Flexible Specification Selection 325
23.10.3.6.4.4 Business Add-In for Assignment of Additional Data to an Inspection Lot 325
23.10.3.6.4.5 Business Add-In for Inspection of Correction of Actual Lot Quantity 327
23.10.3.6.4.6 Business Add-In for Processing of Data on Sample Tab Page 327
23.10.3.6.4.7 BAdI: Creation of Samples for Externally Triggered Inspection 328
23.10.3.6.4.8 Business Add-In for Display of Data for Results Recording on Subscreen 329
characters: 329
23.10.3.6.4.10 Business Add-In for Valuation of Characteristic Results 331
23.10.3.6.4.11 Business Add-In When Saving in Results Recording 331
23.10.3.6.4.12 Business Add-In for Inspection Point Processing Using IDI and BAPI 332
23.10.3.6.4.13 Business Add-In for Selection of Results Data for Copy of Insp. Results 332
23.10.3.6.4.14 Business Add-In for Data Mapping for Copy Inspection 333
RESULTS FUNCTION 333
23.10.3.6.4.15 Business Add-In for Input Help for Quantities in Usage Decision 334
23.10.3.6.4.16 Multiple Specifications: Valuations of Objects 335
23.10.3.6.4.17 Define Object Names for Multiple Specifications 335
23.10.3.6.4.18 Additional Inspections when Closing a Characteristic 335
23.10.3.6.4.19 Business Add-In for Enhancements in Overview Tree in QE51N 336
23.10.3.6.4.20 Business Add-In for Display of 1st/2nd Spec. Limits in Results Recording 336
23.10.3.6.5 Quality Certificate 337
23.10.3.6.5.1 Business Add-In for Certificate Profile Maintenance 337
23.10.3.6.5.2 Business Add-In for Creation of Outbound Certificate 338
23.10.3.6.5.3 Adjust Certificate for Multiple Specifications 338
23.10.3.6.6 Quality Notification 23.10.3.6.6.1 Business Add-In for Maintenance of Reference Object
Screen 339
for Q-Notifs 339
23.10.3.6.6.2 Business Add-In When Saving Notification Data 339
WHATSAPP +255738656506
23.10.3.6.6.3 Business Add-In to Change Functions in Action Box 340
23.10.3.6.6.4 Business Add-In for Replacement of Node Attribute in Document Flow Graphic 340
23.10.3.6.6.5 Business Add-In for Controlling the Changeability of the User Status 341
23.10.3.6.6.6 Business Add-In for Customer-Specific Fields in Notification Process 341
23.10.3.6.6.7 Business Add-In for Implementing an Object Category 342
23.10.3.6.6.8 Business Add-In for Enhancing Single-Level Lists 344
- Notification list 344
23.10.3.6.6.10 BAdI: Check of Activity Type for Notification Type 346
23.10.3.6.6.11 BAdI: Checks for Extended Change of Notification Type 346
23.10.3.6.7 Stability Study 23.10.3.6.7.1 Business Add-In for Replacement of Node Attribute in 348
Document Flow Graphic 348
23.10.3.6.7.2 Business Add-In for Maintenance of Reference Object Screen for Q-Notifs 348
23.10.3.6.7.3 Business Add-In for Controlling the Changeability of the User Status 349
23.10.3.6.7.4 Business Add-In for Processing of Data on Sample Tab Page 349
23.10.3.6.7.5 Business Add-In for Changing of Default Data (Inspection Lot IT/Stor.Cond.) 350
23.10.3.6.7.6 Business Add-In for Flexible Specification Selection 351
23.10.3.6.7.7 Business Add-In for Changing Workarea for Stabi InspLot Before Calling QPL1 351
23.10.3.6.7.8 Business Add-In for Assignment of Additional Data to an Inspection Lot 353
23.10.3.6.7.9 Business Add-In for Checking Inspection Type in Testing Schedule 354
23.10.3.6.7.10 Business Add-In for Displaying Testing Schedule Data on Subscreen 355
23.10.3.6.7.11 Business Add-In for Display of Data for Results Recording on Subscreen 356
characters: 356
23.10.3.6.7.13 Business Add-In for Quantity Check in Stability Study 358
23.10.3.6.8 Quality Control 23.10.3.6.8.1 BAdI: Data Summarization when Evaluating Original
Documents 358
23.10.3.6.8.2 BAdI: Definition of Views for Evaluations of Original Documents 359
23.10.3.6.8.3 BAdI: Thin Out List from Batch Where-Used List 360
23.10.3.6.8.4 BAdI: Process Data Nodes When Evaluating Original Documents 360
23.10.3.7 DISTRIBUTE ALE MASTER DATA 361
23.10.3.8 COMMUNICATION WITH QUALITY INSPECTION ENGINES 363
23.10.3.8.1 Assign Properties 363
23.10.3.8.2 BAdI: Creation of Inspection Lots for Externally Triggered Inspection 364
Inspection Type. 364
Inspection 365
23.10.3.8.5 Activate Event Type Linkage for Confirmations 368
23.10.3.8.6 Activation of Events for Transferring QM Data in Procurement 369
23.10.3.8.6.1 Event Type Linkage for QM Data in Procurement 369
23.10.3.8.6.2 Activation of BTE Application 370
23.10.3.8.7 Activation of BTE Application for Transferring Manufacturing Order Data 370
INTRODUCTION
This book provides system architects, technical consultants, and IT management the
tools to design system architectures to deploy SAP applications on SAP HANA.
Explore production and non-production systems, deployment options, backup and
recovery, data replication, high-availability, and virtualization in detail. Dive into on-
premise deployment options and data provisioning scenarios. Walk through scale-up
and scale-out options and data partitioning considerations. Review the advantages and
disadvantages of storage and system replication options and when to use each. Clarify
how to leverage HANA for single node and distributed systems. Dive into a discussion
on software and hardware virtualization.
WHATSAPP +255738656506
23 Quality Management
23.1 Basic Settings

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

- Implementation procedures
- The important organizational steps and decisions
Recommendation for Using the Implementation Guide
We recommend that you read the text on the screen; only then can you see and use the hyperlinks to
other texts that are highlighted as "hot spots"!
In the standard system, the text is displayed in HTML format. Instead, use the text display with
SAPscript! This gives you access to the most current version of the text and to useful additional
functions.
You can save the SAPscript text display as your default in the following way: -> Transaction SPRO ->
Settings -> User-specific -> IMG Structure. Choose the SAPscript text display and the document key
display as proposed by the system.
Links to other texts are displayed in the SAPscript text as highlighted 'hot spots'. They link to glossary
definitions (green), field documentation (yellow) or structural elements of the Implementation Guide
(violet or gray). If you click on a highlighted section of text, the linked text is immediately displayed.
However, as well as the links to the IMG structural elements, you want to read the referenced text, to see
the context of the link and also to view the tables that relate to the linked structural element. You can do
this with the help of the SAPscript editor in the following way: -> Transaction SO72, choose document
class SIMG or CHAP (identifiable by the first four letters of the structural element key) and then enter
the name of the structural element (begins with the fifth letter of the structural element key). Choose
Display. Once in the text choose the function Document -> Screen output. From here choose the link to
the referenced text. The structure containing the linked text appears and you can then display both the
text and the related tables from within this structure.
The Implementation Guide is structured and organized on the basis of functions. Process the relevant
sections and steps in the predefined sequence! The IMG guides you in logical stages and allows you to
access cross-references using hypertext links.
Requirements
The Implementation Guide for the QM application assumes that you use the application-independent
procedure model as a general guideline for implementing the SAP system. Depending on the size of the
project, there are additional implementation tools available. However, for usual QM projects, the
assistance given by the Implementation Guide should be sufficient.
Standard settings
The system has basic settings that allow you to reproduce the usual business processes without
making widescale modifications. The worksteps contained in the Implementation Guide are primarily
optional and enable you to optimize your company's processes.
Activities
The activities listed below are not intended to replace the general procedure for implementing SAP. They
only deal with the most important organizational steps that you should consider at the start of the project.
As an introduction to working with a QM consultant, we recommend the following workshops:
1. Kick-off workshop for the implementation project.

2. Define the scope of the implementation:
- Which elements of your quality management system can be supported by components of the
SAP system?
- Which of these components form part of the QM application component and which form part
of the other SAP application components?
- Which non-SAP components are to interact with the QM application component? Determine
which company departments are affected by the implementation and how they are affected.
- Which organizational units, (in particular which plants and service departments) in your
company, are affected by the implementation of the QM application component and by the
integration of QM in the SAP system?
- What part do the departments affected play in the implementation of QM?
Recommendation:
Make sure your implementation team contains at least one full-time project leader from your
company, who can
- Acquire the specialist knowledge concerning the QM functions in the SAP system
- Develop the project concept together with external consultants and internal decision-makers
- Develop prototypes for the business processes to be represented in the QM system and
maintain these in the test system (do not leave this informative task exclusively to external
consultants!)
- Control and document the project stages
- Communicate the specialist knowledge to the departments affected by the implementation
Make sure that the implementation team has access to experts with knowledge of:
- SAP components that are to be integrated in the QM application component

- Central functions, for example the SAP Business Workflow (if these functions are required)
- ABAP programming and SAPscript forms
3. Design a concept for representing business processes (Business Blueprint)
Describe the business processes supported by the SAP application component QM: Determine the
current status of the processes in your company that are to be supported in the future.
Design the target concept and discuss it with the company departments that are affected.
First describe the basic concept for business processes; adapt this description if required
during the implementation project.
This description of business processes is used in later phases of the project as the basis for test
plans and instructions for use.
4. Define the implementation stages:

- Do you want the functions of the QM application component (and other interacting SAP
application components or non-SAP systems as required) to be fully implemented in one
operation or in several stages?
- If the implementation takes place in stages, determine which components can be effectively
implemented in each individual stage.
Note: The following areas of the QM application component can be implemented independently:
WHATSAPP +255738656506
- Quality inspection (with and without inspection planning or results recording)
- Quality certificate
- Quality notification
- QM in procurement
You can also subdivide these areas, as the following examples illustrate:
- Quality inspection with and without inspection planning and results recording
- Quality notification with and without the SAP Business Workflow
5. Design of prototypes for business processes in the test system
Proceed in the following sequence:
a) Develop prototypes for QM in the logistics supply chain, for example for QM in procurement,
if these functions are within the implementation scope. Leave out the processing of quality
inspections, quality notifications and quality certificates. Find out about the control options
using the prototypes and work through the relevant Customizing steps. (These can also include
Customizing for other application components).
b) Develop prototypes for the quality inspections that occur in the logistics supply chain. Find
out about the control options using the Prototypes and work through the Customizing for:
Inspection lot processing
Quality planning, inspection planning and the relevant basic data
c) If required, develop prototypes for the quality notifications that occur in the logistics supply
chain and work through the relevant Customizing.
d) If required, develop prototypes for the quality certificates that occur in the logistics supply
chain and work through the relevant Customizing.
6. User tests prototypes and improves design
7. Acceptance of prototypes
23.1.2 Setting Up Clients
In this IMG activity, you provide the clients in the test system with the standard settings available in the
QM component. You can then use these basic settings to maintain the master data required for your
business transactions and to test the functions in the QM component.
This function is particularly useful, if you:
- Have other SAP application components active in a client and you want to implement the QM
functions retrospectively.
- Want to update or add to the system settings in the current client after changing a release.
Requirements
You have set up the client according to the general instructions.

Activities
If you did not set up the client as an exact copy of client 000, you can use the transactions listed below
to copy the basic data and default settings for the QM component in client 000 of the standard system to
other clients. Caution:
- No cancellations are possible for these transactions!

- Entries that already exist in the target client are not overwritten.
- The automatic import protection in the target client is adhered to.
- If the automatic correction recording is active, the system draws up a transport request in the target
client that contains all copied entries (you can process category 'Copy Transport' in transaction
SE01).
The system only executes the transaction if you have the authorization to create transport requests
in the current client and the transport system is set up correctly in this client. To copy this data
into subsequent target systems or target clients, you only need to transport the request with its
copied data entries.
Caution It is important to note that existing data can be deleted and/or changed when you execute a
transport into another system (not the same as transports that originate in client 000). Therefore,
you should never transport this request into a production system.
The following transactions can be used copying basic settings:
- QCCC All standard settings

- With catalogs
- With standard texts
- Without number ranges
- Without sampling systems
- Without tolerance keys
- Without forms
- QCCP Standard settings for quality planning
- QCCW Standard settings for quality inspections
- QCCZ Standard settings for quality certificates
- QCCM Standard settings for quality notifications With notification-related catalogs
- QCCU Standard settings for the QM environment
- QCCK Catalog entries; examples
- QCCT (standard texts QM_*)
You must copy the standard texts used in the forms into the current client, since there is no
automatic default to client 000 for these texts. There is, however, a default defined for the language
in table T002C in the client.
- QCCF (forms QM_*)

You do not need to copy forms into the current client, since the system automatically defaults to
client 000, if the required form does not exist in the current client.
- QCCS Sampling systems according to ISO 2859 and ISO 3951

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

- Control charts
- Inspection plans and reference operation sets
- Inspection lots
- Physical samples and physical-sample drawing
- Condition records for certificate profile determination
- Characteristic confirmation numbers
- Quality notifications
You must pay particular attention both when grouping notification types and assigning these
groups to the number ranges manually and when copying from the standard client. See text
reference and SAP Note number 52390 in the notes database.
Technical note: to improve the response times, the standard system is set up so that it stores a
certain number interval when numbers are allocated internally. The numbers contained in the buffer
are lost when the application program is terminated. You can define the scope of the number range
buffers using transaction SNRO.
Further notes
Update instead of Insert: If you want to overwrite the existing settings in the current client with the
standard settings from client 000, (instead of supplementing them) you can use the method mentioned in
the transactions above. These transactions process prepared command files with the help of transaction
SM29. To carry out an update instead of an insert, use the transaction SCC1 (in place of SM29) or the
report RSCLCCOP together with the command files stored in the transactions mentioned above. The
system, however, does not record this process in a transport request, as in transaction SM29. You can
display the copy's log with transaction SCC3 or report RSCCPROT.
Transport to Other Clients or Systems:
- Customizing tables
All Customzing tables in the QM component have an automatic transport link.
- Transporting master data of QM component

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

See SAP Note 3355 in notes database
23.1.3 Maintain Settings at Client Level
In this step, you can change several central controlling functions.

These controls relate to different components in the QM component; for technical reasons they are
collated in a single table.
Default Settings
The parameters have default settings that suit most requirements.
SAP Recommendation
Use the default settings initially. Change the settings only as the need arises in the course of the
implementation process. Recheck your settings before you enter the productive phase.
Activities
The QM components and functions you want to use determine which settings are relevant for your
requirements. Read the online documentation to familiarize yourself with the meaning of the fields in
this table. Adjust the settings only if absolutely necessary.
Activate Enhancements
Under Further Settings, you can activate enhancements for specific business processes. You can find
more details about the enhancements in the F1 help for the individual indicators.
Additional Information
- The procedure for determining the quality score is described in a separate step. See the "Inspection
Lot Completion" section under "Quality Inspection".
- The valuation rules for inspection characteristics are described in a separate step. See the Sample,
SPC section.
The valuation rule for dynamic modification at lot level that is in the standard system valuates the
lots using the valuation of individual inspection characteristics according to the worst-case
principle.
23.1.4 Establish Organizational Units (Plants, ...)
You must implement this step if you want to use the QM application component in organizational units
that are not contained in the standard system.
Only part of the organizational structure is important for the QM component. Most master data and
Customizing tables in QM are at client level and can be used and are valid in all organizational units. A
range of master data and Customizing tables are at plant level. Only very few Customizing settings
relate to other organizational units, such as, company code, storage location, shipping point.
Requirements
The organizational structure of your company has been represented in the SAP system.
Standard settings
WHATSAPP +255738656506
In the standard system, only one organizational unit for each type is predefined. For example, there is
only one plant - 0001. Large companies must therefore expand the organizational structure considerably.
Recommendation
Use the sample entries that are contained in the standard system as copy models. Only delete the
organizational units and corresponding table entries copied from the standard system, once you have
implemented the steps listed below.
Activities
Set up a new plant
If you want to set up a new plant, you must supplement the following settings if you use the
corresponding functions:
- Number ranges for Inspection characteristics and inspection methods

- Settings for the plant
- Archiving
- Physical-sample location
- Reference dynamic modification levels - Report types for error messages
- Print control for inspection documents
- Calculation parameters for quality cost orders
- Return parameters for appraisal cost orders
- Account assignment parameters for nonconformity cost orders
For inspection plans, work centers and test equipment there are various settings that are dependent on the
plant:
- Inspection planner group

- Profile for default values
- Qualifications for inspection operations
- Reduction strategies
You can find additional details on these in the Implementation Guide, Master Data Work Center or
Production Resources/Tools.
You can define an inspection type for each order type and plant for an:
- Inspection in production
- Inspection in PM
The following master data is maintained at plant level:
- QM data in the material

If you activate the QM in procurement indicator, you must enter a control key in all plant segments.
- Info-records for controlling QM in procurement

- Selected sets from catalogs
You can only make the following settings once you have defined the selected sets for catalog 3 at
plant level:
- Default values for inspection point valuations in the inspection point table - Default values for
inspection point valuations in the settings at plant level - Default values for usage decsision-
selected sets in the inspection type.
- Inspection characteristics
- Inspection methods
- Inspection plans
Setting up new company code
If you want to set up a new company code, you must supplement the following settings:
- Sender texts for certificates and inspection reports
Miscellaneous
If certificates are to be sent from a point that has been newly created, (for example shipping point,
storage location), read the Quality Certificate, Output Dispatch step Set print parameters.
23.1.5 Maintain Settings at Plant Level
In this step, you can change and supplement several central controlling functions at plant level:
These controlling functions relate to the planning and implementation of quality inspections; for
technical reasons they are collated in one table. The functions you want to use for quality inspections
determine which settings are relevant for your requirements. Read the online documentation to
familiarize yourself with the meaning of the fields in this table.
Requirements
To be able to make comprehensive settings for the functions you want to use, you must have maintained
the following master data and Customizing tables:
- Master data
- Usage decisions
- Sampling procedures
- Customizing tables
- Characteristic weighting
- Defect classes
- Field combination for inspection points
- Storage locations (coordinate with inventory management)
If you want to record quality costs, you need
controlling areas, cost centers and order types for
appraisal and nonconformity costs.
WHATSAPP +255738656506
Note: You can post quantities that have been been scrapped or were destroyed in a quality
inspection to a particular cost centers on the basis of value and can enter these cost centers in the
table. You can inidiviually set the corresponding inventory postings at the usage decision. The
account determination in materials management must be set accordingly, so that the update of
values for the corresponding goods movements takes place correctly. In particular, the account
modification must be set to check, to ensure that account assignment to the cost center you
entered and for the offsetting entry in financial accounting is active.
Recommendation
- Initially, use the standard settings from plant 0001 for all plants. Check these default values when
processing the appropriate sections of the Implementation Guide.
- Contact your accounting and inventory management department concerning the required settings
for cost settlement.
Activities
Check the standard settings before you enter the productive phase and then make your final settings for
the default values. Coordinate these settings with all affected plants.
23.1.6 Authorizations
In this section, you assign authorizations to the users of the QM application component.
Basic Information / How to Proceed
When functions are called, the system checks the authorization objects contained in the programs to
determine whether valid values are entered in the fields in these objects. If this is not the case, the system
terminates processing. To give a user the required authorizations, you must carry out the following steps:
- You define the allowed values for the fields of an authorization object in the form of
authorizations.
- You then group the authorizations required to carry out a particular function together as
authorization profiles.
You can also group together several profiles for a job description as composite profiles.
- You assign these profiles or composite profiles to a user master record.

- You must then activate the authorizations, profiles, and composite profiles before they can be
used.
Authorization Administration
With the help of this multilevel concept, the administration of the authorizations can be distributed
among several persons, to ensure that the authorizations will not be misused. For example, you can
designate different persons to:
- Maintain the authorizations

- Maintain the profiles and composite profiles
- Activate the authorizations and profiles
- Maintain the user master records
Authorization Levels
You can define various user authorization levels, depending on the project phase you are in and what
requirements must be met in your company concerning data protection. The following levels may be
appropriate:
1. At the beginning of the implementation phase, you can give your project team comprehensive
authorizations. By doing this, you avoid the maintenance effort required to assign individual
authorizations and you ensure that the testing of the system functions is not hindered by a lack of
proper authorizations. For this purpose, the standard system contains predefined, comprehensive
authorizations and profiles.
2. Before the transition to the productive phase, you define the tasks of the individual users or user
groups on the basis of job descriptions and only assign profiles with which the users can perform
the functions of their job. To do this, there are the following options and authorization levels:
a) You use the authorization generator. It generates the profiles on the basis of job descriptions
that were previously defined in the standard system, with a minimum of maintenance effort. In
most cases, this method of assigning authorizations is accurate enough for the system to be
used productively. For more information, see the section Profile Generator.
b) You can create your own, detailed job descriptions and assign each job the exact
authorizations that are needed. This procedure is described in more detail under User
Authorizations. For a general introduction to authorization maintenance see section Users and
User Authorizations.
Standard settings
The profile SAP_ALL allows you to access all the functions of the SAP functions. You use the
profile Q_ALL contained in the standard system to give authorizations for numerous functions
in the QM component.
You can use the following profiles to give comprehensive authorizations for Customizing:
- S_A.CUSTOMIZ Customizing (general)

- Z_CUSQM01 Customizing for the QM component
Since the QM application component is closely integrated with the MM, PP, SD, PM, and CO
application components, settings made in Customizing also affect these components. To make the
relevant settings, you can:
- Assign the comprehensive profile S_A.CUSTOMIZ to the person responsible for

Customizing your system.
- Assign the corresponding profile Z_CUSxx01 to the person responsible for the QM
component (where xx = MM, PP, SD, PM, or CO).
- Contact the person responsible for Customizing in the relevant components.
Activities
1. Determine which type of authorization management is useful for your company in general and
your quality management processes in particular.
2. Make sure that the system administration for the QM project team gives the required global
authorizations.
WHATSAPP +255738656506
23.2 QM in Logistics
This section describes Customizing activities that control quality management in the logistical processes.
The material master record is the most important integration element for the application components in
Logistics.
The material master record (short form: material) contains the material status that influences critical
business processes in the logistical chain. The material status is present in the views of all relevant
components.
The specific view in Quality Management for the material is activated in Customizing for the material
type. The QM view contains controlling functions for QM in procurement, as well as the control of
inspection lot processing.
Activities
Check whether the requirements for quality management have been adequately fulfilled in the general
Customizing functions for the material and whether they are compatible with the requirements in the
other Logistics components. This applies primarily to Customizing for:
- Material type
- Material status for MM/PP
- SD status
- Retail status
Further notes
The material master contains two complementary status functions that take effect from a specified date:
- The MM/PP status controls which functions are allowed in the Materials Management and
Production application components, at client level or plant level.
- The Sales and Distribution status controls which functions are allowed in the Sales and Distribution
component, at sales organization, or client level.
23.2.1 QM in Procurement
In this subsection, you define the Quality Management functions for materials procurement; you make
the relevant settings in Customizing and maintain the required master data.
The QM component provides a number of controls you can use, depending on your requirements. These
QM controls apply in part to a specific:
- Material and plant

- Vendor
- Combination of material, vendor and plant
Accordingly, these controls are stored in part in the :
- Material master (material)

- Vendor master (vendor)
- Information record (info record) for a combination of material and vendor; (the combination of
material and vendor is referred to in the following section as the supply relationship).
Prerequisites
The subcomponents Purchasing and Inventory Management in the Materials Management (MM)
component must also be active in the SAP system.
To manage the technical delivery terms or quality assurance agreements, you must use the document
management system.
Recommendation
Coordinate the QM tasks with the purchasing planning and inventory management activities for
externally procured materials.
Procedure
1. Find out about the functions for QM in Procurement. Define the options that are relevant for your
company using the master data used in the prototype. Use the field help function to do this.
a) Find out about the control functions and data that are contained in the QM view in the material
master. Recommendation: Exclude the inspection setup and deal with the acceptance
inspection as a self-contained sub-project.
b) Find out about the control functions and data in the vendor master and in the info-record for
the material and vendor.
c) Look through all the controls for this data that are contained in the corresponding Customizing
tables.
2. For the procurement activities in QM, create material groups that are processed in the same manner.
Group your externally procured materials in such a way that all materials in the same group have
the same control settings. Recommendation: Base your grouping on the material groupings that
have already been made in Materials Management.
3. Maintain the Customizing tables for QM in procurement:
First define the control keys for procurement. Depending on which QM functions you want to use,
implement additional steps, such as certificate processing or vendor block
4. Maintain the QM fields in the material master records.

Note: The control keys for QM in Procurement are valid at plant level. Using an indicator at client
level the quality management process can specify that control keys must be active in QM in
Procurement for all plants. With the help of an indicator in the control key for procurement, you
can disable any functions that may block certain activities.
5. Maintain the quality info records (Q-info records).

If the indicators quality agreement or vendor release are set in the control key for the material
master, you must closely coordinate the data you maintain in the corresponding quality info
records. Otherwise, the procurement processes may be obstructed.
6. Maintain the QM fields in the vendor masters.

7. Describe and test the QM processes in procurement for each of the groups determined above.
Further notes
-
The settings for the vendor evaluation function are described in the Implementation Guide for
Materials Management.
WHATSAPP +255738656506
- Controls for material and plant, general controls
- Material status from the MM/PP view; it controls the use of the material for certain functions
in materials management and production. Also compare the material status from the SD view
which has a corresponding, supplementary control function for QM in SD.
- Authorizations for processing certain material groups
- Documentation required
- Processing time in goods receipt
- Controls for material and plant, procurement controls
- Depending on the content of the control key, you may have to define additional specifications:
- Technical delivery terms
- Quality assurance agreements (stored in the quality info-record for the supply relationship)
- Certificate type; controls certificate processing activities
- Acceptance inspection
The section Quality inspection describes how to implement an acceptance inspection. You store
the controls for the acceptance inspection on the screen for the inspection setup in the material
master.
- Controls for vendor:

- Verification of QM system
- Vendor block
- Controls for supply relationship and plant:
- Verification of QM system
- Vendor release, with limitations on:
- duration of release and delivery quantity
- Vendor block
There are special purchasing functions (transaction MP01), for blocking in manufacturer
processing.
- Status management for supply relationships

- Special controls for receiving inspection: source inspection at vendor's premises skip
23.2.1.1 Define Control Keys
In this step, you define the control keys for QM in procurement.

The control keys in the material master are defined at plant level. They contain a range of control options
that are explained in the F1 help.
Activities
1. Determine which material groups can have the same control settings.
2. Define the control keys for each material group.
Further notes
You must carry out the following additional activities, depending on how you defined the control key:
- Define technical delivery terms for material and plant.

- Define quality assurance agreements for material, vendor and plant.
- Release material, vendor and plant.
- Define certificate types and certificate processing activities.
23.2.1.2 Define Keys for Certificate Processing
In this step, you define certificate types for quality certificates and the controlling functions linked to the
certificate type for QM in procurement.
The certificate type is stored in the material master at plant level.
Note
You only need this workstep, if there are control keys for QM in procurement, in which the indicator
certificate required is set. For requests for quotations and purchase orders, the system informs the vendor
that a certificate is required and processes the expected certificates according to the settings that have
been defined for the certificate type.
Activities
1. Use the F1 field help to find out which controlling functions are linked to the certificate type and
decide which of these functions you require.
2. Define appropriate certificate types for the material groups that require certificates.
3. Define the controlling functions linked to the certficate type.
4. If you want to use the enhanced certificate processing, (which includes management of the
certificate receipt), you must maintain a number range for the receipt of the certificate.
5. You can also receive certificates by data transfer. For the required implementation step, see the
section Quality Certificates / Output Processing / IDoc Processing.
23.2.1.3 Define Delivery Block
In this step, you define the keys to block supply relationships.

Depending on whether the block applies to all materials or only certain materials for a vendor, the
blocking key is contained in the vendor master or in the quality information record for a material/vendor
combination.
The key allows you to block the following business transactions:
- request for quotation

- selection during source determination
- purchase order
- goods receipt
WHATSAPP +255738656506
In the control key for QM in procurement, you specify how the system should respond when it
encounters a block. For example, with:
- an information message
- a warning message
- an error message
Activities
1. Together with the purchasing and inventory management departments, determine which blocking
options are used in your company and how the system and the persons responsible will respond, in
the event of a block.
2. Replace the blocking keys in the standard system with the keys that are needed in your company.
3. Set the system message type according to the arrangements made with the purchasing and materials
management departments.
To block the procurement functions, you have several options:
- blocking the vendor for general reasons (purchasing block)

This block suppresses all purchasing functions. In the vendor master, you specify whether such a
block will apply to all or to certain purchasing organizations.
- blocking the vendor for quality-related reasons

This block suppresses the procurement functions specified in the blocking key and is effective for
materials for which the indicator QM in procurement is active.
- If you set the blocking key in the vendor master, it applies to the vendor, regardless of the
materials and plants involved.
- If you set the blocking key in the quality info-record, it applies to a specific material and plant
only.
For quality-related reasons, you can use the control key for QM in procurement to override any
active blocking keys for certain plants.
23.2.1.4 Define Document Types
In this step, you define the document types for the exchange of quality documents with vendors.
Standard settings
Two document types have been defined in the standard system for QM in Procurement:
- Q01 - quality assurance agreement with vendors (QAA)

(Stored in the info record for the material and vendor supply relationship)
- Q02 - technical delivery terms (TDT)

(Stored in the material master)
The settings have been made so that
- The output function in procurement (for example, the purchase order printout) can process these
documents. Therefore, in the standard system there are only SAPscript texts allowed for this
document type.
- You can follow a procedure that complies with the rules for quality documents, for example,
whether a new document version is required, if a released document has been changed.
You should check the controls for these document types, but not change them. You should also not
define any additional document types for QM in procurement.
You can only change the settings relating to the document type, provided that this does not affect the
output functions in Procurement. For example, you may want to define a different status sequence from
the one contained in the standard system for these documents. To do this, you must temporarily remove
the Customizing block on these document types.
Further notes
General Customizing of QM Documents
You can find more information about the document types used in the QM component in the
Environment, Central Functions, Define Document Types section.
The complete Implementation Guide for the Document Management System is contained in the section
Cross-Application Functions, Document Management System.
Purchase Order Printout
- If there are no valid TDTs or QAA and you ignore the warning messages that appear when the
request for quotation and the purchase order is made, there is no reference to the TDTs or the QAA
in the procurement output.
- If the valid TDTs or QAA contains a long text of less than 2 lines, the single line of text is not
printed in the procurement output. You must therefore create another line by pressing 'Return'.
23.2.1.5 Define QM Systems
In this step, you define models for the verification of quality management systems (QM system for a
vendor).
Some organizations - in particular, government agencies and large corporations - require their vendors to
verify that an appropriate QM system is documented, implemented and in use within their organization.
Ever since the ISO 9000 series of standards have become generally recognized, many companies have
obtained corresponding certificates from accredited organizations. The scope and requirements of these
QM systems vary, however, according to the needs of individual companies. As a result, there are many
different models and requirements for QM systems. Many of these requirements apply only to certain
parts of the QM system and are thus covered by the certificates. You can determine whether the
specifications of the QM system match the certification requirements on a case by case basis using a
system audit.
In the SAP system, you can define different requirement models as target QM systems and different
existing systems as actual QM systems. In addition, for each actual QM system, you define the most
suitable target system.
You can valuate the various QM systems that are defined in the SAP system. This valuation exerts no
control; it serves as information only. For example, using this valuation you can determine whether a
valid certificate exists, the origin of the certificate, or the score for the system audit.
WHATSAPP +255738656506
Example: A customer wants a vendor to verify the existence of a QM system that complies with standard
ISO 9003. The vendor has a certificate that states that his system complies with ISO 9001, with an audit
score > 80. A comparison shows that in this particular case, both systems are equivalent:
Target QM system 9003 (ISO 9003, with certificate)
Actual QM system 1180 (ISO 9001, with certificate, audit score > 80)
Assignment Actual/target 1180 - 9003
You can assign an actual QM system with the identification skip which means that the SAP system does
not create inspection lots for an acceptance inspection.
Recommendation
Comply with the applicable standards (for example, standards ISO 9001 through ISO 9003). Do not
maintain too many standards for Q-system requirements.
Activites
1. Determine the requirements that exist for vendor QM systems in your company. Note that such
requirements may stem from the requirements of your customers. Define the target QM systems in
the table.
2. Determine which actual QM systems your vendors use. If you want to valuate these systems,
define a valuation profile. Define the actual QM systems and their valuation.
3. Assign the target QM system to the actual QM system whose requirements it fulfills. You must do
this in the following steps:
a) Make all obvious assignments. For example, the QM system that conforms to ISO 9001 also
conforms to the requirements of ISO 9003.
b) In those cases where you first have to check the specifications of the QM systems and
the certification requirements, supplement the assignment list as necessary.
The requirements for QM systems are defined in the material master at the plant level. The QM system
that is actually present is defined in the vendor master at the client level or in the quality info record for a
combination of material/vendor at the plant level. In procurement (request for quotation and purchase
order), the system checks whether the vendor's actual QM system meets the target QM system's
requirements for the material. In doing so, the system uses the assignment list that you created in activity
3. If the requirement is not fulfilled, the system responds as follows:
- Warning message for requests for quotations

- Error message for purchase orders
23.2.1.6 Define Status of Supply Relationships
In this step, you define status profiles for the supply relationships and assign an inspection type to the
statuses in the profile.
In the status profile, you can specify that the delivery of a material from a vendor must pass through a
number of statuses, for example:
- Model series
- Preliminary series
- Regular delivery
You can assign different inspection types (with corresponding task list usages) to a status. The system
then selects the appropriate inspection types and inspection plans based on the status of the supply
relationship.
Activities
1. Determine whether the supply relationships must pass through certain statuses and if this is the case,
maintain the corresponding status profiles for the object type QINF.
For a detailed description of the general status management function, refer to the chapter
Basic Settings and Environment, Central Functions, status profile.
2. If necessary, assign an inspection type (which indirectly assigns a task list usage) to the statuses in
the profiles.
3. Store the status profiles in the quality info records (QM control in procurement) for the relevant
materials, vendors and plants, and set the current statuses for the supply relationships.
Further notes
Tracking Status
Each status profile must contain an initial status for newly created supply relationships. You can also
define additional statuses that can be linked together in a status sequence. You can link all of the statuses
together or only selected ones. You do this by assigning status numbers to the statuses and by defining a
highest and lowest status number for each status in the sequence.
If a supply relationship is currently in such a status sequence, the system will only allow one current
inspection lot to be created for each status; that is, it will not allow any further goods receipts until the
usage decision is made for the current lot.
When you make a usage decision to accept an inspection lot, the system sets the next status in the status
sequence. This is repeated with every successive usage decision, until the last status is reached. If an
inspection lot is rejected, the current status is retained. You can also set a status manually.
Inspection Type Determination
You can assign an inspection type to each status.
When an inspection lot for a goods receipt is created automatically, the system selects the inspection type
that is assigned to the next status and not the inspection type that is assigned to the current status. See
example!
If there is no inspection type defined for the next status in the sequence or if the last status has been
reached, the system chooses the inspection type that has been defined as variant 01 or as the preferred
inspection type for inspection lot origin 01.
You can only control the inspection type in this way within status sequences. If you set the individual
statuses in the quality info record manually and they are not contained in a status sequence (that is, the
statuses do not have status numbers), no control is exerted when the system creates inspection lots for
goods receipts. You must create the corresponding inspection lots manually and select the inspection
type yourself. Authorization Control
The user, who carries out the goods receipt postings requires authorization for the status change to the
supply relationship. If no authorization exists, the system selects the preferred inspection type or the
inspection type that is defines as variant 01 for inspection lot origin 01. You must therefore assign all
users that are involved in creating inspection lots at the procurement stage, authorization for the object
B_USERSTAT and the object type QIN.
Example:
Status profile '*'
Object type 'QIN'
Authorization key either ' ' or '*'
WHATSAPP +255738656506
Activity '*'
When you define the object type as 'QIN', this ensures that the user only has authorization to set the user
status in inspection lot processing.
If the last status in a sequence has not been reached, you cannot post any further goods receipts between
the creation of an inspection lot and the usage decision. You can overcome this problem in the following
way. Have the goods receipt posted by a user, who has no authorization for the object B_USERSTAT or
the object type QIN. If this authorization is missing, the system allows another goods receipt posting
and chooses the usual inspection type at inspection lot creation.
Example
The delivery client 000 contains a processing example with a model and replicate sample that are subject
to a more thorough inspection than a regular delivery.
ONo. Status Ini Min Max Inspection type

1 0001 Supply rel. created X 1 5 ' '
2 0002 Model 2 3 0101 Model inspection 3 0003 Pilot
series 2 4 01 Goods receipt insp.
4 0004 Regular delivery 1 4 ' ' -> 01 GR inspection
5 0005 Replicate sample request. 6 ' '
6 0006 Replicate sample 6 7 0101 Model inspection
7 0007 Production series 5 7 ' ' -> 01 GR inspection
Once you have entered the status profile in the quality info record for the supply relationship, the system
automatically sets the initial status "Supply relationship created" and updates the status after each
successful goods receipt inspection, starting with the status "Model" until the last status in the series
"Regular delivery" is reached. If an inspection lot is rejected, the last status is retained. For the status
"Supply relationship created", the system selects the inspection type "Model inspection" that has been
defined for the next status in the sequence "Model" and searches for an inspection plan with the task list
usage described in the inspection type.
If you want to inspect a replicate sample, you have to set the "Initial status" in the quality info record and
then the status "Replicate sample requested". At the next goods receipt, the system then creates an
inspection lot with the inspection type defined for the replicate sample and searches for an inspection
plan with the task list usage described in the inspection type. Once the inspection lot has been completed
and given the valuation "Accepted" at the usage decision, the status of the info record is changed to
"Regular delivery".
23.2.1.7 Define List Variants
In this step you define list variants for collective maintenance of the Q-info records.
Variants are defined using a list view function. The procedures for this function are described in the
section Basic Settings, Tools, Define list variants.
23.2.2 QM in Production
The settings described in the subsection 'Quality Planning' / 'Basic Data' also apply to the quality
planning activities in production; otherwise, no other special settings are necessary.
The settings described in the sections 'Quality Inspection' and 'Quality Notification' also apply to the
quality management activities in production. In particular, refer to section inspection for a production
order.
The inspection planning function for routings, rate routings and master recipes allows you to define
inspection points and their corresponding partial quantities.
You can assign partial lots to the quantities of materials associated with certain inspection points
(in a ratio of n:1). You can then make usage decisions for the partial lots and trigger automatic follow-up
actions with each usage decision. If you manage your material stocks in batches, you can assign the
partial lots to batches (in a ratio of n:1).
If you carry out inspections during production on the basis of inspection points, you can not only record
the inspection results for an inspection lot, but you can also confirm the actual values for the production
order. Make sure you consider the following settings for this purpose: The control key for the operation
(confirmation) The settings for order type and order confirmation.
Depending on the production type and the desired functions, there are several settings that affect the
production planning functions themselves. For details, refer to the Implementation Guides for Production
and for production planning in the Process Industry.
Determine whether you want to intervene in the release of the production process with the help of the
MM/PP status. Coordinate your activities with the production department and take an active part in
defining the status.
23.2.3 QM in Sales and Distribution
To control quality management in Sales and Distribution, the QM component contains an info record for
the supply relationship, (that is for the object types customer or for the object types customer, sales
organization and material).
You can use the info record to:
- Define whether inspection lots should be created for a delivery and how the inspection is to be
integrated in the delivery process.
You make the settings required for this in the section Quality Inspection, Inspection Lot Processing,
Inspection Lot Creation Inspections in SD.
- Store documents that are to be managed by the general document management functions. For
more information, refer to the section Environment, Central Functions, Define document types.
See the Cross-Application Functions, section Document Management System for more
information on document management settings.
You can set a status in the Sales and Distribution data for the material that you can use to control the
release of the Sales & Distribution functions. You set the material status independently of the plant,
dependent on the sales organization and distribution channel. The status takes effect from a specified
date. The material status from the SD view supplements the material status from the MM/PP view that
you use to control the release of materials management and production functions. See also the sections
QM in Procurement and QM in Production.
You can add quality certificates to the delivery. There is a separate Implementation Guide for this in the
section Quality Certificates.
23.3 Quality Planning

This section describes the Customizing settings for quality planning.
The term "Quality Planning" covers inspection planning and its relevant basic data.
WHATSAPP +255738656506
In the Inspection Characteristic section, you can find additional conceptual information on Customizing
and how to maintain inspection characteristic master records that can be applied to other master data
types.
In the Inspection Planning section, you can find additional conceptual information on procedures. In the
Samples and SPC section, you can find specific conceptual information on the planning of samples and
statistical process control with the help of control charts.
Activities
On the basis of the information gained when creating the prototypes for your QM-supported business
processes, define in detail the maintenance of your master data and the related table settings.
1. Select the master data you need to use the SAP application component QM and define the logical
sequence in which this data is to be maintained.
a) Determine which master data is needed to implement the required range of functions. If you
decide to carry out the implementation in stages, determine which master data is required for
these steps.
b) Indicate which basic data is merged with other master data. Use this information to establish a
logical sequence for maintaining the master data.
2. Develop a plan for maintaining the master data.
a) Define the uses for the fields contained in the master data; in particular define the
nomenclatures for mnemonic keys and search fields if required. Check whether the search
help must be adapted.
b) Estimate the volume of the master data. If specific master data, for example, inspection plans
can be copied automatically from an existing volume of data, prepare the tools available for
transferring this data.
c) Determine who is responsible for maintaining the master data and what maintenance
capacities are available. Estimate the time and effort required to manually maintain the master
data. Allocate the available resources on the basis of the data volume and the implementation
schedules. Identify critical paths related to scheduling.
3. Make sure that following activities are completed on schedule:
a) Table settings
b) Manual maintenance of master data
c) Transfer of data and manual follow-up maintenance
Further notes
In the SAP system, quality planning results (quality related planning in its entirety) are stored in the
form of master data. There are two different groups of master data:
- QM-Specific Master Data

This master data is part of the QM application component. This data
includes:
- Material specification
- Inspection plan and
reference operation set (plant level)
- Catalog (Selected sets at plant level)

- Inspection characteristic and inspection method (plant level)
- Sampling procedure, sampling scheme, dynamic modification rule, and sample-drawing
procedure
- Info-record for a combination of material * vendor (plant level)
- Info-record for a combination of customer * sales organization or customer * sales
organization * material
- General Master Data

This is master data that is used by several application components. Refer to the respective
Implementation Guides for these application components for information on how to maintain this
master data and how to make the corresponding settings. This master data includes the business
partners:
- Customer
- Vendor
Master data for central functions:
- Material master
- Document
- Characteristic and class in the classification system
- Change
Master data from the PP and PP-PI application components:
- Routing, rate routing and master recipe (plant level)

- Work center (plant level)
- Production resources and tools:
- Material
- Equipment
- Document
- PRT master record
Recommendation: Coordinate the maintenance of the general, integrating master data with the
maintenance activities in the other application components that have access to this master data.
Further notes
You can access the IMG directly using the transaction QCC4.
23.3.1 Basic Data
You use this section to customize and maintain specific master data, called basic data, since it can be a
reusable building block in various higher-level objects (for example, in inspection plans). This data
includes:
- Catalogs
Catalogs are used for the following functions:
- Values of qualitative characteristics

WHATSAPP +255738656506
- Defect characteristics (such as defect type, defect cause, ...)
- Usage decisions (for inspection lots, partial lots, inspection points)
- Catalog profiles for quality notifications
- Master inspection characteristics and inspection methods
- Sampling procedures, sampling schemes, dynamic modification rules and sample-drawing
procedures
Prerequisites
The scope and sequence in which you should maintain the master data is described in the Quality
Planning section.
Recommendation
If there are no reasons for using another sequence, maintain the basic data and corresponding settings in
the sequence described above.
23.3.1.1 Catalog
In this subsection, you set up the terminology catalogs.

Catalogs provide a means of making sure you use the terminology consistently. The QM application
component uses a two-level hierarchy consisting of code groups and codes for its catalogs. The
terminology is encoded mnemonically at the client level. The codes are made up of four characters,
which in turn are assigned to eight-character code groups. These codes can also be assigned to eight-
character
selected sets at plant level.

To organize the catalogs, you must define:
- The use and description of each catalog

- Mnemonic keys for codes, code groups and selected sets
- Guidelines for creating short texts
- Guidelines for using and creating other catalog contents
Standard settings
In the standard system, catalogs 1 through 9 and A through E are defined for use. Use catalog types P
through Z to define your own supplementary catalogs.
Activities
1. Organize special catalogs

Special catalogs 1, 2, 3 and 9 have functions that differ from the remaining catalogs.
a) Catalog 1:Characteristic attributes

You need this special catalog to record inspection results; in it you define the value range for
qualitative inspection characteristics.
Refer to the section Inspection characteristics, to determine whether this characteristic type
is used in your organization. Organize catalog 1 according to its intended use for the
inspection characteristics.
You can only access characteristic attributes using selected sets. You must therefore create
selected sets at the plant level, in which you group the codes together under general
categories.
In the selected sets, you must specify a defect class for the characteristic attributes that
represent a rejection.
Determine what additional information, if any, should be stored for the characteristic attribute
in the selected set. You can enter texts for tasks and effects on an additional data screen.
b) Catalog 2: Tasks
You need this special catalog for the quality notifications. You can define automatic follow-up
actions for tasks.
c) Catalog 3: Usage decisions

You need this special catalog for inspection lot completion. You can only access the usage
decisions using selected sets. You must maintain the following additional control fields for
each code contained in a selected set:
- Valuation of the
inspection lot
- Quality score -
Follow-up
action
d) Catalog 9: Defect types
You use this special catalog to record defects in quality notifications. In this catalog, you must
define a defect class for each code contained in a code group.
2. Organize general catalogs

When you record characteristic results, you can also record the entries from several catalogs or
selected sets in addition to the characteristic values, provided they have been stored in the
inspection characteristic.
Determine which catalogs will be useful for this purpose and which catalogs will require selected
sets at the plant level. Define the catalog types in the subordinate menu item with the same name.
Furthermore, you can use certain catalogs to record data for the quality notifications and defect
records. Refer to the chapter Quality Notification for additional information.
3. Maintain catalog master records

Maintain the master records for the catalogs you previously defined, in the following sequence:
a) Code group, code (at client level)

b) Selected set (at plant level)
Once you have maintained the catalogs, set the status of the code groups and selected sets to
'Released'.
When the codes, code groups and selected sets are first used, the system gives them a usage
indicator that prevents these objects from being deleted (either by mistake, or intentionally!).
Since the usage indicators cannot be reset once they have been created, and codes cannot be
deleted once they have been used, you should exercise caution when releasing catalogs, code
groups and selected sets in a productive system.
You can maintain the catalog master records in the languages in which the catalog types have been
documented.
WHATSAPP +255738656506
- To find codes in extensive catalogs quickly, you must use mnemonic keys for code groups, codes
and selected sets. Define the structure of these keys carefully!
- When you search for a code, code group or a selected set generically using the entry * and using the
F-4 Help function, the system displays the catalogs that fulfill the selection criteria in a hierarchical
list on a screen.
You can search generically with the special characters '+' and '*'
Example
If you enter +A* in the code field, the system searches for codes whose keys have the letter A as
their second letter.
- When you display created catalog entries in transaction data (such as, inspection results and quality
notifications), the description for the code is displayed, but not for the code group. If you use the
special character & in the code group text, the system displays a combination of both code and code
group texts for the code. The code text is displayed in place of the special character with the code
group text.
Example
Code group description: Defect & assembly
Code description: Transistor
Display: Defect transistor assembly
23.3.1.1.1 Define Defect Classes
In this step, you define the defect classes that are used to valuate the defects qualitatively on the basis of
the defect consequences.
These defect classes are used in the following places or for the following purposes:
- In the selected sets for catalog 1 (characteristic attributes)

- In catalog 9 (defect types)
- For the valuation of characteristic inspection results For each defect class, you can specify:
- A quality score
- Whether a characteristic attribute in catalog 1 with this defect class can be valuated as acceptable
- Whether the following can be activated:
- Workflow event
Activities
Define the required defect classes and their properties.

If you want to trigger automatic follow-up actions that are dependent on the defect class, refer to the
following section of the Implementation Guide:
- Environment -> Central Functions -> Workflow

You need the quality score default values for each defect class if you want to use a corresponding
valuation procedure for the quality score of inspection lots.
In the Settings at Plant Level, define a default value for the defect class.
In the master data, the defect classes are used in the following catalogs:
- Catalog 1: characteristic attributes, selected sets

- Catalog 9: defect types
The following defect classes are effective during results recording:
- If a defect type is specified in the inspection plan characteristic, the system selects the defect class
associated with the defect code. The defect codes are defined in catalog 9.
- If a defect type is not specified in the inspection plan characteristic, the system proposes a defect
class. It selects the default value as follows:
- At the respective lowest level (this is the level of single values, classes, summarized characteristics
or samples, depending on the recording from), the default value is selected from the table of default
values at the plant level.
If you valuate qualitative characteristics on the basis of an attribute code, the system uses the
defect class stored in the selected set for catalog 1.
- On the more global levels - that is, when you valuate characteristics or samples - the system applies
the worst-case principle; it searches for the defect class in the respective lower levels with the
lowest quality score and proposes this class as a default value.
- During results recording, the user can change, retain or automatically copy the default values for the
defect classes.
This depends on whether or not the entry function for the defect class is active.
23.3.1.1.2 Define Catalog Types
In this step, you define the terminology catalogs and catalog languages you need, in addition to those
contained in the standard system.
Standard settings
The table has the delivery class E. In the standard system, several catalogs have predefined functions or
are reserved for later use. If you define your own supplementary catalogs, use the catalogs P through Z.
Recommendation
- During the testing phase, set up the catalog types so the codes can be deleted in the database. In the
production phase, set up the catalog types so the codes are switched to inactive, instead of being
deleted. This prevents the deleted codes from inadvertantly being restored and given another
meaning.
- Do not delete the catalogs reserved for SAP! This is especially critical for catalogs 1 and 3, since
they contain special functions that are required for quality inspection.
Activities
1. Familiarize yourself with the functions in the catalogs that can be preset (use the F1 Help in the
"Catalog Types" view).
2. Define the desired catalog types and their properties.
WHATSAPP +255738656506
3. Document the catalog types in the same languages, in which the code groups and codes of the
respective catalogs will be documented.
- The following catalogs have additional functions:

- 1 Characteristic attributes
- 2 Tasks
- 3 Usage decisions
- 9 Defect types
- You can only use catalogs 1 and 3 in conjunction with selected sets. A valuation of the codes in the
selected sets is obligatory.
- Selected sets are defined at plant level in the user language.
- For catalog 2, or for other catalogs that are used as task catalogs in quality notifications, you can
define follow-up actions at code level in the code groups.
- For catalog 3, you can define follow-up actions at code level in the selected sets.
23.3.1.1.3 Edit Catalogs
In this step, you maintain the catalogs you require for the inspection characteristics. The following
catalogs are usually delivered with the standard system:
- Catalog 1: Characteristic attributes for qualitative characteristics You

must create selected sets at plant level for this catalog.
- Catalog 9: Defect types
Standard settings
For test purposes, you can copy the examples contained in the standard client 000 into the test client,
using the method described in the section Basic Settings / Setting Up Clients.
Recommendation
Treat the catalogs as master data and make the final entries in the productive system. Note: When
catalogs are transported, usage indicators are included. Long texts, however, are not transported.
23.3.1.2 Inspection Characteristic, Inspection Method
You use this section to customize and maintain inspection characteristics and inspection methods.
Master inspection characteristics and inspection methods are defined at plant level. They are used as
copy models when you create inspection plans or material specifications.
Master inspection characteristics can be derived from class characteristics.

Master inspection characteristics can reference inspection methods and catalogs.
Prerequisites
- If you want to reference inspection methods and catalogs from the master inspection characteristics,
you must have previously maintained the corresponding master records.
- If you want to classify the master inspection characteristics or inspection methods you must have
maintained the Classification System.
Activities
The following text describes a procedure for organizing master records which you can use appropriatly
when planning other master records, for example when you plan and maintain inspection methods.
1. Define the structure of the master records.

a) Define number ranges.
Decide whether the number assignment will be made internally or externally. We
recommend that you use the automatic internal assignment of non-mnemonic numbers; for
the field for mnemonic names, you can use the master record search field. Make sure the
number ranges that have been set in the standard system will be sufficient.
b) Specify version creation.

Determine whether you want to document the changes to the master records in the system with
the help of new versions and if so, specify when these changes are to be documented. In the
Settings at Plant Level section, set the appropriate control indicators.
c) Define the nomenclature.

If the nomencalture is clearly defined, you can find the master records more easily.
For this reason, define the contents of the following master record fields:
- external number (if applicable) -
short text (language-dependent)
- search field (language-
independent)
You can use the short text to search in the master record lists and the sort field to search by
matchcode.
d) Make sure that the search help contained in the standard system is sufficient. If necessary,
define your own search help.
e) Define the classification.
With the help of the Classification System, you can:
- Organize master records according to classes
- Conduct structured searches for master records
- Ddistinguish master records on the basis of class characteristics
With the help of class characteristics, you can determine where the master inspection
characteristics are used; you can thereby evaluate the inspection results independently of plans
or materials on the basis of the master inspection characteristics.
If you want to use the Classification System, you must define:

- A class hierarchy for categorizing the master records
- Key words for master record searches
WHATSAPP +255738656506
- Class characteristics for the description of the master records
f) Define the contents of the master inspection characteristics.
Specify which fields should be used in the inspection characteristic master record and how
they should be used. Make sure the long texts are organized uniformly.
2. Make settings for the Customizing tables

3. Make preparations for the transfer of data.
If you want to transfer part or all of the master records for inspection characteristics from other
systems, you must clarify the requirements for these technical processes.
4. Create the inspection characteristic and inspection method master records. Define these master
records before you create the inspection plans.
If the inspection characteristics are to be used for the inspection specifications and for the transfer
of inspection results to the batch valuation, you must also maintain the class characteristics that are
linked to the inspection characteristics
Further notes for Version Management
The system can manage different versions of master data records for inspection characteristics and
inspection methods. The individual versions are clearly identified by a current version number that is
assigned internally by the system. For each version, there is a date from which the data record is valid
(valid-from date). Several versions can be valid for the same key date.
If you first create a master record (function "Create inspection characteristic" or "Create inspection
method"), you can either give it an alphanumeric or numerical key, or let the system assign a numerical
key (Number range definition). The system assigns this new master record version number 1. You must
specify a valid-from date for this first version.
You can create additional versions of the master record in the following ways.
1. You use the function "Create version". You must specify a date from which the version is valid.
This date must not be used in another version of the data record.
2. You use the function "Change". You can choose and change a valid version for a key date.
However, if this version is released and if history management is defined for inspection
characteristics or inspection methods in the settings at plant level, the system then creates a new
version with the same valid-from date. The original version is saved with no changes and can still
be used.
23.3.1.2.1 Define Default Values for Control Indicators
In this step, you define control keys for the attributes of inspection characteristics. The control key is
used to propose or predefine the control indicators for the master inspection characteristics and
inspection plan characteristics.
After you have specified in the control key whether or not the indicators will be predefined and whether
the characteristic is quantitative or qualitative, you must define various characteristic attributes. Refer to
the F1-documentation for information about the control indicators contained in the key.
Standard settings
The control keys in the standard system comprise a basic set with which most of the characteristic types
in the SAP application component QM can be displayed.
SAP Recommendation
- Define your own basic set of control keys.

- Define the nomenclature for the descriptive short text, so you can quickly find the appropriate
control keys.
- Set the control indicators in such a way as to avoid unnecessary problems when you record results.
- Keep the number of control keys to a minimum.
Activities
1. Determine which control indicators or characteristic attributes exist and which are important to you.
2. Determine which basic types of characteristics are commonly used in your company and how they
can be displayed using these control indicators.
3. Define mnemonic short texts for these basic types.
4. Maintain the table for the control key default values.
5. Test the effect of the control keys when you record results.
Additional informationen
- Some control indicators will be ready for input only after other control indicators have been set. If
necessary, use the "Inspect" function and complete the fields on the screen.
23.3.1.2.2 Define Characteristic Weighting
In this step, you define the characteristic weights.

You can define weight classes for the characteristics according to any desired criteria. For each weight
class, you can specify a weight factor that determines whether a skip will be allowed for a characteristic
belonging to this particular weight class.
In certain procedures, characteristic weights are used to calculate the quality score.
Standard settings
The standard system contains weight classes that correspond to the defect classes (for reasons of
compatibility with the R/2 system).
SAP Recommendation
If you want to transfer factors for defect weights from an R/2 system, you must define the corresponding
classes for the characteristic weights. Otherwise, define classes for characteristic weights according to
your needs. Internationally recognized criteria for classification and weighting purposes are not yet
available.
Activities
1. Define the desired characteristic weights and their attributes.

2. Define a default value for the characteristic weight in the menu option Settings at plant level.
WHATSAPP +255738656506
23.3.1.2.3 Define Inspector Qualification
In this step, you define the inspector qualifications.

These inspector qualifications are defined at the client level and proposed at the level of the inspection
characteristics or inspection methods in the task list.
You can also define the inspector qualifications at the plant level and propose them in the work center
data for the operation in the task list. For additional information, refer to the chapter Inspection planning,
Operation, Work center data, Define qualifications.
Activities
1. Determine whether inspector qualifications must be defined in your company, in order to use the
inspection methods or process the inspection characteristics. If necessary, coordinate the
qualification levels on a company-wide basis.
2. Maintain the check table.
23.3.1.2.4 Define Tolerance Keys
In this step, you define the tolerance keys for quantitative characteristics with tolerance ranges. (If this
table is used to define measurement tolerances in the mechanical engineering sector, the terms 'target
value' and 'limiting value' are synonymous for the terms 'nominal value and 'limit deviation').
For each tolerance key, you can define:
- A short text
- A unit of measurement
- The number of decimal places for the target value and specification limits Note: Although you can
enter a different number of decimal places for the nominal value and limit deviation from that in the
tolerance key itself, the system always uses the number of decimal places specified by the tolerance
key in the inspection characteristic.
- The target value
- Whether the target value in the key should be copied into the characteristic
- The limiting values as absolute values or differences to the target value (relative tolerance)
- Whether the relative tolerance depends on the target value; if this is the case, you must define the
relative tolerances for each target value range in a subordinate table.
Prerequisites
You have defined the units of measurement.
Standard settings
The standard system contains complete tolerance tables for holes and shafts according to DIN ISO 286-2.
The data from the DIN standards has been reproduced with the permission of the German
Institute of Standards). This data corresponds to the current version of the ISO-DIN standards.
(<Date of current release>, SAP AG)
You may copy the tolerance tables from client 000 into the current client and use them as a part
of the SAP system. SAP, however, assumes no liability for the validity of the data.
Recommendation
The standards may have changed since the date of the current release and errors may have occurred as a
result of maintaining and importing the data. For this reason, make sure the data is valid before you use it
in the production system!
Activities
1. Determine whether tolerance schemes for quantitative characteristics are used in your company and
find out how you can represent them in the SAP application component QM. If your company is
active in the mechanical engineering sector, you can use the tolerance tables for limit deviation in
the standard system for holes and shafts.
2. Store the tolerance specifications in the table.
Further notes
Normally, companies in the relevant branches need only a small selection of the tolerance tables in client
000. To copy this data into the current client, use the function provided in the table maintenance (Utilities
-> Compare with client 000) and its associated copy function. The section Basic Settings, Setting up
clients contains instructions on how you can transport all of the basic settings in the standard client 000
to the current client.
23.3.1.2.5 Define Estimation Procedure for Fraction of Defects
In this step, you can define your own processes to estimate the fraction of defects using the characteristic
inspection results. There are the following fraction estimates:
- Nonconforming units (with regard to a characteristic and in the inspection lot)

- Characteristic values outside of the tolerance range
The keys for the procedure are defined in the inspection characteristic.
Standard settings
In the standard system, fraction estimates have been maintained for the following distributions:
- Binomial distribution
- Poisson distribution
- Normal distribution
The table has the delivery class G. The following name range is reserved for the user:
- Defect share estimation procedure 9*, A*, ... , Z*
SAP Recommendation
Use the function modules contained in the standard system.
Activities
WHATSAPP +255738656506
Determine whether you need procedures other than those contained in the standard system for the
estimaton of the fraction of nonconforming units in the inspection lot or for the estimation of the fraction
of characteristic values outside the tolerances.
If necessary, define the calculation rules and program function modules for your own estimation
procedures.
23.3.1.2.6 Define Number Range
In this step, you maintain the number ranges for inspection characteristics and inspection methods.
You must define independent number ranges for each plant.
Requirements
- In the previous sections "Inspection Characteristics," "Inspection Methods", you determined

whether or not an external number assignment is necessary.
- You have defined the plants.
Standard Settings
The following number ranges are available for inspection characteristics and inspection methods:
- 01 for internal number assignment

- 02 for external number assignment
No other number ranges are allowed for purely numeric names of inspection
characteristics and inspection methods; you can only define the number interval. The system
checks the names of alphanumeric inspection characteristics and inspection methods to make
sure they are explicit.
SAP Recommendation
- For purely numeric names, use internal (automatic) number assignment.

- Use a predefined nomenclature for externally assigned mnemonic numbers.
- Use the SAP standard settings.
Activities
For each plant, define the ranges for the externally and internally assigned numbers.
Further notes
Number range objects can be transported as follows:

On the initial screen, select "Interval - Transport."
All intervals for the selected number range object are first deleted in the target system, so that only the
exported intervals will be present after the import. The number levels are imported with the value they
have at the time of the export.
23.3.1.2.7 Define List Variants
In this step, you define the list variants for inspection characteristics and inspection methods.
This function uses list view techology. The technology and procedure are described in the section
Environment, Tools Define list variants.
23.3.1.2.8 Define Specification Determination Rule
Use
In this IMG activity, you define the specification determination rule that you can enter in the master
inspection characteristic.
The specification determination rule allows plan characteristic specifications to be changed when a plan
is transferred to the inspection lot.
For each rule, you are given the status of all the logs created when used in a productive system.
In change mode, you can also display the logs using a pushbutton.
Activities
For each specification determination rule, you require an implementation of the BAdI
BADI_QASDR_MASTERCHAR_TO_INSP.
23.3.1.3 Sample, SPC
This subsection describes how to implement sampling procedures, sampling schemes, dynamic
modification rules, sample-drawing procedures, and control charts.
Samples in the SAP System

The sampling procedure is stored in the inspection plan for the inspection characteristic, or in the
material for the inspection type. The sampling procedure determines the sampling plan when an
inspection lot is ready for processing.
The system takes the current quality level into consideration, together with a dynamic modification rule
that has also been defined. The quality level determines the inspection stage or skip stage for subsequent
inspections, based on the inspection history.
If the sample size is to be controlled based on the lot size, the sampling procedures reference sampling
schemes and the inspection severities that form the basis of the sampling schemes are assigned to the
inspection stages that have been defined in the dynamic modification rule.
In the SAP system, the sampling procedure defines the sampling type and the valuation mode. If the
sampling procedure is to be used to retrieve data for quality control charts, it also includes the control
chart type.
While the sampling procedure determines the size and the valuation of the sample, the sample-drawing
procedure controls the type and number of the physical samples to be taken.
Standard settings
WHATSAPP +255738656506
Sampling Schemes
The standard system contains ready-to-use sampling schemes that conform to:
- DIN ISO 2859-1 for qualitative inspections

- DIN ISO 3951 for quantitative inspections
The data from the DIN ISO standards has been reproduced with the permission of the German Institute of
Standards (DIN). This data corresponds to the current version of the ISO-DIN standards.
You can copy the sampling schemes from client 000 into the current client and use them as a function of
the SAP system. SAP, however, accepts no liability for the validity of the data.
The SAP system uses the following nomenclature for the three-digit 'ABC' name of the sampling
schemes:
- 'A' (description of standard): 2 = ISO 2859-1 (attribute inspection) / 3 = 2859

(without valuation parameters) / 4 = ISO 3951-1 (var. inspection, s-method)
- 'B' (description of method): 1 = s-method or single sample

- 'C' (description of level): 1=I / 2=II / 3=III / 4=S-1 / 5=S-2 / 6=S-3 / 7=S-4
Sampling Procedures
The standard system contains complete sampling procedures that use the sampling schemes mentioned
above. Note that you must manually adapt the respective sampling procedures or create new ones when
the above-mentioned ISO standards and the corresponding sampling schemes are updated.
The SAP system uses the following nomenclature for the eight-digit 'ABCDEFGH' name of the sampling
procedures:
- 'A' sample type: S = use sampling scheme

- 'B' valuation mode:
1 = Attribute inspection using the number of nonconforming units
2 = Attribute inspection using the number of defects
3 = Variable inspection according to the double-sided s-method
- 4 = Variable inspection according to the single-sided s-method
- 'CDE' sampling scheme
- 'F' number of samples: n = n-fold sample
- 'G' preferred inspection severity
- 'H' AQL: A = 0.01; B = 0.015; C = 0.025; D = 0.04; E = 0.065; F = 0.1; G = 0.15;
H = 0.25; I = 0.4; J = 0.67
K = 1.0; L = 1.5; M = 2.5; N = 4.0; O = 6.5
P = 10; Q = 15; R = 25; S = 40; T = 65;
U = 100; V = 150; W = 250; X = 400; Y = 650;
Z = 1000
Dynamic Modification Rules
The standard system contains the following dynamic modification rules that can be used in connnection
with the sampling procedures mentioned above:
- S01 dynamic modification of the inspection severity according to ISO 2859-1, §9.3
(no limiting values according to §9.3.3b)
- S02 dynamic modification with skip lot according to ISO 2859-3
(no limiting values according to table 1 and table 2, as well as without cubing calculation according
to appendix B)
Recommendation
Do not maintain the data until you have familiarized yourself with the terms used in the above text.
The standards may have changed since the date of the current release and errors may have occurred as a
result of maintaining and importing the data. For this reason, make sure the data is valid before you use it
productively.
In the chapter Basic Settings -> Setting Up Clients, you are instructed how to transport the sampling
data contained in the standard client 000 to the current clients. Activities
1. Develop a sampling concept
Decide on a basic approach: Do you want to retain the procedures used in your company or do you
want to re-evaluate the objectives of the sampling procedures and possibly redefine them? You can
implement most of the common sampling procedures in the SAP application component QM. With
the support provided by the SAP application component QM, however, you have additional
options, especially for dynamic modification. If you want to re-evaluate your philosophy with
respect to the sampling procedures, ask yourself the following questions:
a) What purpose should the sampling inspection serve?

b) Which sampling procedure (sampling type and valuation mode) is best for this purpose?
c) Are the sampling procedures currently being used supported by sampling schemes?
d) Can the inspection scope be optimized through dynamic modification?
e) Are control charts to be displayed or used for valuation purposes?
f) Is the drawing of physical samples to be defined?
2. Maintain the settings and master data in the correct sequence:
a) Set the sampling types.
b) Set the valuation modes.
c) Maintain the sampling schemes (create master records).
Provided you want to use sampling schemes in the sampling procedures that do not
already exist in the standard system.
If you want to use inspection severities other than the ones set in the standard system, you
must first define them.
d) Define the dynamic modification rules (create master records).

e) Maintain the sampling procedures (create master records).
f) Maintain the allowed combinations of sampling procedures and dynamic modification rules.
When you maintain the sampling procedures and dynamic modification rules, the system will
prompt you to maintain these combinations. You can ignore this initially. If you only need a
few dynamic modification rules, but many sampling procedures, it may be convenient to
maintain the dynamic modification rules first and then assign these rules immediately when
you maintain the sampling procedures.
g) Maintain sample-drawing procedures

If the number of samples is to be calculated dependent on the lot container, you need
corresponding units of measure for the container.
Settings for Sample Management are contained in the Quality Inspection section.
WHATSAPP +255738656506
You can implement the most common, internationally standardized sampling systems (sampling types,
valuation modes, dynamic modification rules) in the QM application component without having to make
any modifications. For example, this applies to:
- ISO 3951, s-method

- ISO 2859, part 1; valuation according to number of defects or number of nonconforming units,
but without multiple samples or limiting values
- ISO 2859, part 3; skip lot with inspection frequencies that can be predefined
The QM application component handles the input parameters for the sampling procedures (inspection
level, inspection severity, acceptable quality level (AQL)) in a special way:
- In the QM application component, inspection levels are neither stored in the sampling
schemes nor in the sampling procedures. This means if you want to work with several
inspection levels, you must store separate master records for the sampling scheme and
sampling procedure for each level.
- In the QM application component, the inspection stage and AQL are input parameters for the
sampling scheme. This means that you can maintain the sampling plans for several inspection
severities and AQLs in one sampling scheme master record.
- With the help of the two input parameters inspection severity and AQL, the sampling
procedure selects the appropriate sampling plan from the sampling scheme based on the lot
size. Depending on whether or not dynamic modification is specified, the sampling procedure
proceeds differently:
- If no dynamic modification of the inspection severity takes place, the inspection severity and
AQL are taken from the sampling procedure. This means there is one sampling procedure
master record for each inspection severity and AQL.
- If dynamic modification of the inspection severity takes place, only the AQL is taken from the
sampling procedure. The sampling procedure takes the inspection severity specified in the
current quality level. You must maintain a sampling procedure master record for each AQL.
- The sampling procedure and the dynamic modification rule are both included in the inspection
plan. To make sure the inspection severities in the sampling scheme (that supports the
sampling procedure) fit the inspection severities in the dynamic modification rule, you must
define the allowed combinations of sampling procedures and dynamic modification rules.
You must decide which combinations of sampling procedures and dynamic modification rules are
compatible with each other and can be used together in an inspection plan. This applies only to
sampling procedures with sampling schemes; sampling procedures without sampling schemes can
be combined with any dynamic modification rules in the inspection plan.
The system allows you to assign a dynamic modification rule only if all of the inspection severities
in the sampling scheme associated with the sampling procedure have been maintained, which have
been assigned an inspection stage in the dynamic modification rule. This means: for the AQL
defined in the sampling procedure, the sampling scheme contains sampling plans for all inspection
stages supported by the dynamic modification rule. Skip stages are not assigned an inspection
severity.
23.3.1.3.1 Define Sample Determination
In this step, you maintain:

- Sampling types
- Rules for determining the sampling instruction
The sampling type defines the basic conditions for determining the sample size for each inspection
characteristic. A distinction is made between certain basic forms, such as:
- 100% inspection
- Fixed sample
- Percentage sample
- Sample according to the sampling scheme
To define or adapt the rules for determining samples, integrate the function module responsible for
determining the sampling plan in your system. These rules form part of the function that supports the
sampling type and are therefore dependent on the same parameters as this sampling type.
Default Settings
The standard system already contains entries for the sampling types. Appropriate rules already exist for
each of these entries for the sample determination.
- Sampling type 9*, A*, ... Z*.

- Sample determination rule 9*, B*, ... Z*.
SAP Recommendations
Do not delete the sampling types and rules for the sample determination contained in the standard
system! You can disable the use of the sampling types you do not need.
You only need to maintain your own sample determination rules in special cases.
Match the short texts of the sample determination rules to the texts of the corresponding sampling types,
so that you can easily assign a suitable sample determination rule to the sampling type, when you
maintain the sampling procedure.
Activities
Determine whether you need sampling types and sampling rules in addition to those contained in the
standard system.
1. Maintain the additional sampling types.

2. Maintain the additional rules for determining samples. Ensure that the necessary function modules
are programmed.
You enter the sampling type when you maintain the sampling procedure. On the basis of this entry, the
system proposes an appropriate selection of rules for the sample determination. If there is only one
appropriate rule, the system selects it automatically. There is usually only one appropriate rule for sample
determination for each sampling type.
Depending on the sampling type and the corresponding rule for the sample determination, the system
requires certain input parameters (for example, the sample size of the fixed sample). The input
parameters have no units of measure. The sampling procedure, stored at the characteristic level in the
WHATSAPP +255738656506
inspection plan, determines the sample sizes by multiplying the input parameters by the sample units of
measure stored in the inspection plan.
The sample determination rule is stored in the sampling procedure itself and not in the sampling type.
This means that the system has the highest degree of flexibility when it determines the sample sizes.
Make sure, however, that the system is able to check whether the parameters for the sampling type and
the sample determination rule are consistent. You must ensure that the function behind the sample
determination rule is compatible with the desired sampling type.
The system also contains sample determination rules that are active on a global level, and do not solely
affect the sampling procedure in the inspection characteristic. This occurs, for example, if you define a
100% inspection for all characteristics in the inspection setup of a material.
23.3.1.3.2 Define Inspection Severities
In this step, you define the inspection severities that can be used for dynamic modification.
Internationally used standards (for example, ISO 2859) define several inspection severities; for example,
normal, reduced and tightened. In addition, these standards also propose several skip stages that do not
have inspection severities assigned to them.
Standard settings
- Inspection severity 01*, ... 09*, 9*
Recommendation
Retain the standard settings.
Activities
Define the desired inspection severities.
Further notes
When you maintain the dynamic modification rules, the system expects you to enter an inspection
severity for all inspection stages that are not skip stages, even if you actually use sampling procedures
without sampling schemes. For this reason, define one or more inspection severities, in case you carry
out an inspection without a sampling scheme.
23.3.1.3.3 Define Valuation Mode
In this step, you can:
- Define how a decision is made to accept or reject inspection characteristics (valuation mode).
These decisions are used in the sampling procedure.
- Integrate your own function modules that allow you to make the decision whether to accept or reject
You must decide which one of the basic forms you want to use. These forms are as follows:
- Manual decision
This is required for attributive characteristics (that is, characteristics for which no values are
recorded). These are characteristics you simply accept or reject. This type of decision is also used in
all other cases, where an automatic valuation is not possible or allowed.
- Code valuation: a decision on the basis of qualitative attributes.

The decisions are stored in the catalog for characteristic attributes.
- A decision based on a sampling plan for discrete characteristics (attributive inspection) with the
following options:
- Number of defects
- Number of nonconforming units
This decision can also be used in conjunction with tolerance specifications for the measured
values of quantitative characteristics.
- A decision based on a sampling plan for quantitative characteristics (variable inspection) with the
following options:
- Complying with the distribution limits of the characteristic values (s-method)
- Complying with the mean value limits of characteristic values (checking the tolerance
specifications)
This is a special application of the s-method, where k = 0.
- A decision based on a control chart.

You can assign suitable, different valuation rules to these basic forms and thereby define different
valuation modes, such as:
Simple valuation
- Manual valuation
- Code valuation. This valuation is based on the attributes of qualitative characteristics
- Valuation based on the number of defects
- Valuation based on the number of nonconforming units
Valuation for the mean value of quantitative characteristics, based on the tolerance
specifications
Valuation modes for procedures using sampling schemes:
- Valuation according to sampling plan for:

- Attribute inspection, for discrete characteristics (in accordance with ISO 2859)
- Variable inspection, for continuous characteristics (in accordance with ISO 3951) The system
supports a single-sided and double-sided s-method.
Valuation based on the limits of a control chart
Valuation modes for procedures using independent multiple samples:
- Valuation according to the:

- Worst case principle
- Last case principle
- Best case principle
The valuation modes for procedures with independent multiple samples are suitable for the valuation of
characteristics in:
WHATSAPP +255738656506
- Inspections during production with inspection points
- Inspection of partial lots
- Inspection of physical samples
- Inspection of maintenance objects
Standard settings
In the standard system, the table of valuation rules is designed so that all commonly used valuation
modes are supported at characteristic level.
The tables have the delivery class G. The following name range is reserved for the user:
- Valuation mode 9*, A*, ... Z*

- Valuation mode 9*, A*, ... Z*
SAP Recommendation
Use the valuation modes contained in the standard system.

Do not delete any of the valuation modes contained in the standard system; instead, you can lock the
entries you do not need.
Do not delete any of the valuation rules contained in the standard system and under no circumstances
delete valuation rules A1, A2, A3, A4, A5, since these were used for programming.
You only need to maintain your own valuation rules in special cases.
Activities
1. Determine whether additional or other valuation modes are used in your company. If necessary, you
must also define and program appropriate valuation rules for these valuation modes.
2. Determine whether you need additional or other valuation rules. Define these rules only if required.
a) Substitute the function modules
b) Program your own function modules.
c) Enter the valuation rules in the relevant valuation modes.
Valuation Levels
The valuation of an inspection characteristic is usually made up of several steps that take place at the
following levels:
- Valuation of original values or value classes

In summarized results recording original values or value classes are not valuated.
- Valuation of samples
If the system does not allow for multiple samples, there is no valuation at sample level
- Valuation of a characteristic
The valuation rules mentioned above are active at characteristic or sample level. At original value, or
value class level, the valuation rules that are dependent on the control key for the characteristic are fixed
automatically by the system:
- Manual valuation
- Code valuation for qualitative characteristics with characteristic attributes
- Valuation based on tolerance specifications for quantitative characteristics
Definition of Valuation Rules
The valuation rule is usually defined in the valuation mode and is included in this way in the sampling
procedure.
There are two valuation rules for inspecting independent multiple samples; one for characteristic-based
decisions for individual samples and one for characteristic-based decisions for all samples. The valuation
rule that links the decisions relating to the individual samples to a collective decision for the
characteristic is stored directly in the sampling procedure, together with the valuation mode for the
samples.
For inspections with partial lots and inspections with inspection points, for example, inspections during
production, inspection of physical samples or inspection of maintenance objects (equipment or functional
locations), two valuation rules are also required. In these cases, the combining valuation rule is not stored
in the sampling procedure, but taken directly from this table.
If you want to change the collective valuation, you must substitute or change the function module
contained in the following valuation rules:
- A1 Manual valuation
- A2 Inspection with partial lots
- A3 Inspection with inspection points
- A4 Inspection of physical samples
- A5 Inspection of equipment or functional locations
23.3.1.3.4 Statistical Process Control
In this section, you make the necessary preparations to use control charts.
In the Customizing application for control charts, you define:
- which charts will be available

- how results recording will be controlled for these charts
- which function modules will be used to process the control charts
- how parameters will be used in these functions
- how the charts will be assigned to the processes (SPC criteria)
Requirements
You can only use control charts for inspections in which planned inspection characteristics are used and
measured values are recorded (that is, the indicators inspect with inspection plan or material specification
and results recording based on characteristics are set in the material master, and the control indicator for
measured value recording is set in the inspection characteristic).
- You define the SPC criteria in the inspection plan characteristic (that is, the assignment to the
process).
- You define the control chart type in the sampling procedure.
When you plan the use of control charts, you must create sampling procedures with fixed samples. You
can also use independent multiple samples or inspection points.
WHATSAPP +255738656506
Further notes
The following control chart types are supported:
- mean value chart with tolerances (acceptance chart)

- mean value chart without tolerances (Shewhart chart)
- standard deviation chart
You can combine a mean value chart and a standard deviation chart in a single control chart with two
tracks.
You can call up and process the control chart for an inspection characteristic when you record results for
an inspection characteristic.
A separate authorization object exists for the definition of the control limits. Refer to the chapter
Environment/ authorizations for additional information.
You must use an appropriate valuation rule when you evaluate the characteristic values on the basis of
the control limits. Refer to the chapter Quality planning, Basic data, Sampling procedures, Valuation for
additional information.
If the control limits are exceeded, the system creates a defect record or quality notification. Refer to the
chapter Quality notifications, Defects recording for additional information.
23.3.1.3.4.1 Define SPC Criteria
In this step, you define the criteria that will be used to summarize and assign the inspection results for
control charts to the processes.
The SPC criteria determine whether the system will maintain separate or collective control charts for
different orders, work centers, materials, manufacturers or customers.
Requirements
You have defined the inspection types, inspection lot origins and task list usages for which control charts
are to be used.
Standard settings
Several combinations of criteria have already been preset in the standard system. With this criteria, you
can assign the control charts to the most common applications. Make sure you read the online
documentation for the corresponding function modules.
- SPC criterion 9*, A*, ... , Z*
Recommendation
Make sure the criteria for the summarization of inspection results is compatible with the dynamic
modification criteria that apply when the inspection plan is selected. To do this, compare the task list
usages and inspection lot origins in which the control charts are used.
Activities
1. Determine which inspection types require control charts.

2. Determine which combinations of criteria are needed to collect the results for the inspection
characteristics.
3. If you need certain combinations of criteria that are not contained in the standard system, have a
qualified person create the corresponding function modules and store them in the table.
Further notes
The system cannot determine whether you combine the criteria logically.
23.3.1.3.4.2 Define Control Chart Type
In this IMG activity, you define the control chart types.

For each control chart type, you define the requirements based on the control indicators and sampling
procedures used in the inspection characteristic.
In a second step, define the control chart tracks. For each track, determine which control variable is used
and how the warning limits or action limits are calculated.
Standard settings
A number of common control charts have already been defined in the standard system. Appropriate
control indicators and parameters have been set for these control charts, so the system can calculate the
control limits.
- Control chart type 9*, A*, ... , Z*
Note
Note that a change in the control chart type has an immediate effect on the display of existing control
charts and that any change can cause inconsistencies.
Recommendation
Refer to the online documentation for the corresponding function modules for information on:
- the editing of data

- calculating the warning limits and action limits
Define the characteristics, for which control charts will be maintained, as master inspection
characteristics. In the long text for the characteristics (or in an inspection method assigned to the master
inspection characteristic) describe how the user must proceed. In particular, you should specify the
sampling procedure, parameter set-up and initial run.
Activities
1. Determine which types of control charts will be used in your company.

2. For purposes of retrieving data, define appropriate control indicators for the control chart type.
This control must be compatible with the control for the inspection characteristics and the sampling
procedure being used.
3.
Define the function modules and parameters according to which the system will calculate the
warning limits and action limits. Also plan the initial run.
WHATSAPP +255738656506
Note
The system can display examples of the control charts, so you can check the format in which they are
displayed.
23.3.1.3.4.3 Define Number Range
In this step, you define the number ranges for the control charts.
Recommendation
Retain the standard setting.
Activities
Check to make sure an adequate number interval has been set.
Further notes

Select 'Interval - Transport' on the initial screen.
All intervals for the number range object are first deleted in the target system, so that only the exported
intervals will be present after the import. The number levels are imported with the value they have at the
time of the export.
23.3.2 Inspection Planning
In this chapter, you implement the functions for inspection planning using the SAP application
component QM.
Although these implementation steps are described for the inspection plan (task list type Q), they also
apply to inspection planning activities for other task list types.
The inspection plan uses a variety of other master data in the form of building blocks. The
Implementation Guide contains separate chapters that describe how to maintain this data:
- Basic data in the chapter Quality planning

- Work centers and test equipment in the Implementation Guide for Production
Recommendation
Since the inspection plan is integrated in the routing, the implementation activities correspond to a great
extent with those of the routings. If you intend to implement both the QM and PP application
components, coordinate the corresponding Customizing activities.
Activities
1. Plan the conversion of old inspection plans to SAP QM inspection plans.

a) Compare the inspection plan structures typically used in your company with those contained
in the SAP application component QM.
b) Determine whether an automatic conversion of existing data to SAP master data is technically
possible and feasible.
c) Plan and test the conversion. Use the tools for data transfer available in the system.
2. Plan the implementation phases.
a) Identify the critical paths in the structure of the basic data.
For example, consider the path Inspection method -> Master inspection characteristic ->
Reference operation set -> Inspection plan; this data must also be maintained in this sequence.
b) Organize the inspection planning functionality into manageable subsections. For example, you
can logically organize the information according to the following criteria, depending on the
existing structures in your company:
- Organizational units (plants)
- Material groups
- Inspection types or task list usages
c) Estimate the time and effort, compare the available capacities, identify the critical paths and
set the priorities for implementing the inspection plans in the individual application areas.
d) If necessary, define modular stages for expanding the inspection plans. For example, you can
initially work with core inspection plans that you can use globally. You can improve and
customize the contents of these plans later, as necessary.
e) Define and carry out the steps that ensure the availability of a complete set of inspection plans.
The special task list type "Q" (inspection plan) is reserved exclusively for the "Q" (quality inspection)
application.
The inspection plan conforms to the structure of the routing to a great extent. In contrast to the routing,
the inspection plan:
- Can only have a standard sequence of operations (no alternative sequences)

- Recognizes not only an assignment to a material, but also an assignment to a
- Material and vendor or manufacturer
- Material and customer
Other task list types can also contain the structure level of inspection characteristics, if quality
inspections are to be integrated in the production process. The implementation activities for inspection
plans and other task list types (routings, rate routings, master recipes and reference operation sets) are
more or less the same.
23.3.2.1 General
The settings you make in this section apply to the task list group as a whole or to the task list header.
You are only offered the settings that are important for maintaining task list types Q and S. In the
Implementation Guide for Production, you can find additional settings for task lists that you normally do
not need when you use task list types Q and S. Nevertheless, you should familiarize yourself with these
settings and the implementation projects for other task list types, so you do not make any settings that
could adversely affect the QM component. Note: The following functions for task list determination are
WHATSAPP +255738656506
offered in the Implementatuion Guide for Production and you can use these to control user-related and
automatic task list selection. Although these functions are not supported for inspection plans, there must
be an entry with the key Q* in the relevant tables. Check if these entries exist and if not, transfer the
entries form the standard client.
The inspection plans are linked to the central engineering change management function for Logistics
objects. Refer to the section Logistics, Engineering change management for a description of the settings.
Some fields in the task list header are only required to record inspection results based on characteristics.
These include:
- Definition of identfiers for units to be inspected

- Identifiers for inspection points
To carry out these steps, see the Results Recording subsection of the Quality Inspection section.
23.3.2.1.1 Assign Task List Types to Material Types
In this step, you specify which material types can be inspected using inspection plans.
Requirements
You have maintained the material types.
Default Settings
In the standard system, several common material types have already been assigned to task list type Q
(inspection plans).
Activities
1. Check the settings of the material types in the menu item "Material master/Define attributes of
material types."
2. Determine which material types should be inspected with task list type Q (inspection plan).
3. Maintain the assignment table.
Further notes
Other task list types such as routings may also contain inspection operations. You must also make such
assignments to the material type for these task list types.
This table is used by the system for controlling screens and selecting fields in the inspection setup of the
material. If there is no assignment of the task list type to the material type, the fields related to the task
list are hidden.
23.3.2.1.2 Define Task List Usages
In this step, you define your task list usages.

Within a task list group, you can create different task list types with different usages. For example, you
can distinguish among the following usages: model inspections, goods receipt inspections, inspections
for goods returned from a customer, product audits and goods issue inspections. With the task list usage,
the system can find an appropriate task list for a certain inspection type.
For each task list usage, you also define appropriate dyn. modification criteria to update the quality
level. The dynamic modification criteria defined in the task list usage only serve as default values for
the dynamic modification criteria in the task list.
Activities
1. Define the usages for which you intend to use your own inspection plans, and for which your own
criteria should be suggested for updating the quality level. Define the usages on the basis of the
inspection types that are commonly used in your company.
2. For each task area, define the appropriate criteria that will be used to update the quality level.
3. Maintain your task list usages.
The table of task list usages is also used for other task list types.
Do not confuse the task list usage used within this text with the following terms:
- task list usage for work centers and production resources and tools, which controls the use of the
aforementioned objects in the various application components. - task list usage as a parameter that can
be set for production orders
23.3.2.1.3 Define Task List Status
In this step, you define the Status that is used in the logistical task lists (inspection plan, reference
operation set, routing, ...)
The status controls the following functions in the QM application component:
- Release for use

- Of reference operation sets in inspection plans
- Of inspection plans in inspection lots
- Release for standard cost estimate
(The standard cost estimate currently does not apply to inspection plans.)
- Consistency check
Recommendation
Retain the standard settings in this table!

Deactivate the function for the consistency check while you are testing the system; reactivate the function
when the system is ready to be used productively.
The table of statuses also applies to other task list types (for example, routings). When you maintain this
table, be sure to coordinate the activities with all other affected departments!.
Activities
Define the task list status.
WHATSAPP +255738656506
For each inspection lot origin, you can specify a suitable task list type and task list status.
The task list status is taken into consideration when the task list is selected. It is one of several criteria.
A task list is selected when:
- A task list is created on the basis of a copy model

- An inspection lot is created
The task list selection is currently programmed in such a way that the first entry found for task list type Q
in tables V_TCA43 und V_TCA44 is selected. You do not need to make any additional entries in the
selection table or change the existing entries in the standard system. You will not find these tables in the
Implementation Guide for this reason. Make sure, however, that the settings in the standard system for
the SAP-QM-relevant entries in the task list selection tables are not changed by the other applications!
23.3.2.1.4 Define Planner Group
In this step, you define the inspection planner groups.
Activities
1. Find out how the inspection planners are grouped in the plants within your company.
2. Maintain the planner groups for each plant in the table.
- The inspection planner group serves as a source of information (for example, when you carry out
matchcode searches or make reports).
- The inspection planner groups are part of the general planner groups.
23.3.2.1.5 Define Overview Variants
In this step, you can create your own object overviews for an inspection plan. This procedure uses the
technique for "variable lists". In the Implementation Guide for Production Planning (Routing -> General
data -> Overview variants), you will find a corresponding step for other task list types such as the routing
and reference operation set.
For each overview that you create, you also create an overview variant. For this overview variant, you
must specify:
- Which objects are to be displayed in the overview (for example, operations or characteristics)
- Which fields are to be displayed for each object
Standard settings
The standard system contains an overview variant.
Activities
To create your own overviews, proceed as follows:
1. Create overview variants

This section describes how to create overview variants.
2. Define objects
This section describes how you can define the objects that are to be included in the overview.
3. Define fields
This section describes how to select fields and define the layout for the overview.
4. You can transport your settings by selecting Table view ->Transport.
Further notes
You can call up the "object overview" from the inspection plan transaction and also print the created
overview list.
This same technique is used in several places (for example, at the operation level for scheduling
overviews). This maintenance procedure is not specifically offered in the Implementation Guide for
functions that are seldom used. Nevertheless, you should be familiar with these tools: the allowed fields
in the overviews are predefined in the system (transaction CNVL); the fields displayed in the overviews
are stored in the view V_TCNVL.
Inspection characteristic values are only displayed in exponential form in the variable lists. If you want
to display the characteristic values in decimal form, you must use the normal print list (transaction
QP05).
23.3.2.1.6 Maintain Profiles for Default Values
In this step, you can maintain profiles for the default values in inspection plans.
When you maintain the inspection plans, the SAP System makes it easier for you to enter data in the
following ways:
- data is proposed from the material (for example, the material short text)
- data is proposed or referenced from the work center
- data is proposed from a profile
When you maintain an inspection plan, you can enter a profile identifier. The values in this profile
are proposed when you create a new inspection plan or plan object (header, operation,
characteristic). You can retain or overwrite this data.
The default values stored in the material master or work center master have priority over the values in the
profile.
Profiles with default values are available for the following levels:
- inspection plan in general

- inspection plan header
- operation
- inspection characteristic
Activities
1. Identify the fields in the inspection plan for which you can (and should) store default values in
profiles.
2. If necessary, define several different profiles and specify when these profiles should be used. Define
the nomenclature for a mnemonic profile short text.
WHATSAPP +255738656506
3. Maintain the default values for the general management of inspection plans.
4. Maintain the default values for the management of inspection characteristics.
23.3.2.1.7 Define Field Selection
In this step, you adapt the field selection in task lists. For more information, see section Environment/
Tools/ System Modification / Adapt Field Selection.
23.3.2.1.8 Define Text Widths
In this step, you define the line length of the long texts in the inspection plans.
The long texts for the following objects are affected by this table setting:
- plan header
- sequence
- operation
- sub-operation
- production resources and tools assignment
The length of the short text is always 40 characters. If you define a line length for the long text that is
greater than 40 characters, the associated short text will display only the first 40 characters of the first
long text line.
Recommendation
Retain the standard setting.
Activities
Define the line lengths for the individual objects.
Further notes
This function has priority over the system's central text format setting.
23.3.2.1.9 Maintain Parameters for Task List Type
In this step, you assign number ranges to the task list types. You can also
activate the following options for each task list type:
o Creation of change documents
o For the material, task list group and sales document: the last value maintained is
displayed as a default value
o Deletion of task lists and operations (but only with special authorization) (Controlled by
the authorization object Q_ROUT)
Requirements
The number ranges for the inspection plans and reference operation sets have been
maintained.
Standard settings
In the delivery system, the parameters for the inspection plans (type Q) and reference operation
sets (type S) have already been set up in a meaningful way.
Recommendation
Make sure you consult with someone in the PP module concerning the settings you make for
task list type S!
Activities
Determine whether the parameter settings you need for task list type Q will be different from the
standard settings. If necessary, maintain the table.
23.3.2.1.10 Maintain Number Ranges for Inspection Plans
In this step, you maintain the number ranges for the task list groups associated with the following task list
types:
- Inspection plans
- Reference operation sets
Number allocation can take place internally and externally.
You can also use alphanumeric, mnemonic keys for the task list groups. The system merely checks such
keys to determine if they are unique; it does not take number ranges into account.
Standard Settings
Number ranges have already been predefined in the standard system.
Recommendation
- Retain the standard setting.

- Make sure the number range is large enough to make the internal number assignments.
Activities
Maintain the number ranges for the external and internal number assignment.
Further notes

exported intervals will be present. The number levels are imported with the value they have at the time
they are exported.
WHATSAPP +255738656506
23.3.2.1.11 Copy Inspection Plan from External System
In this step, you prepare the transfer of data for inspection plans from external systems into the SAP
system.
The Customizing function available for this purpose (data-transfer workbench) supports all the single
steps that can be standardized to transfer data.
Requirements
The inspection plan data in the external system exists in a form that is compatible with the data structure
for inspection plans in the SAP system.
Recommendation
Read the documentation on the report RCPTRA01.
Activities
1. Prepare transfer
a) Generate transfer structure
The SAP system creates table structure source descriptions for the data to be transferred
(transfer structures) and writes them to a sequential file that you can use for the data
agreement in the transfer program.
Generate a sequential file with the transfer structures (F5 function in data transfer workbench).
You can display the generated transfer structure (Shift + F7) and change the data fields (F6).
Create the data agreements for this transfer structure in COBOL, C, PL/1 or ASSEMBLER
languages (Shift + F7).
b) Prepare transfer program

Use the generated data agreements as the basis for creating a transfer program that writes the
inspection plan data from the external data processing system to a sequential file. Batch input
sessions can then be created from these sequential files to transfer the data to the SAP system.
2. Prepare transfer data

a) Create a sequential file using the inspection plan data from the external data processing system
and make this data available to the SAP system.
b) Enter the name of these sequential entry files in the following form: </path/name of sequential
file>
c) Create batch input sessions to execute the transfer program (F8).
3. Perform data transfer
a) Load the batch-input sessions (Ctrl + F1).
b) Check the data that has been transferred to the SAP system.
Further notes
You can test the data transfer before transferring a large number of inspection plans to the SAP system.
To do this, proceed as follows:
- Create a model inspection plan in the SAP system.

- Generate a sequential entry file (using the workbench function "Generate test data").
- Create the corresponding batch-input session (F8).
- Load this batch-input session in the foreground (Strg + F1), and check how the program runs.
- Check the result.
23.3.2.1.12 Define Identifier for Inspection Points
You define inspection points in this step. This involves defining the following:
- Identification of inspection points

- Default values for valuating the inspection points
- Function modules for generating the inspection points
To identify the inspection points, the inspection point data record can contain a date and time field. For
each of these fields, there are two text and number fields of variable length that you can freely define.
You use these fields when recording inspection results, to assign the inspection points to the units that
have been inspected or to the partial quantities. You do this by selecting one of the flow variants stored at
operation level.
You can use this identification technique in several application areas. The standard system, therefore,
provides the following inspection point types
- Freely defined inspection points to identify partial lots in production You need this inspection
point type, for example, if you create inspection lots for a production order and want to carry out
several inspections for each operation during the production process.
- Inspection points to identify samples
You need this inspection point type if you want to manage samples and record inspection results for
physical samples
- Inspection points to identify maintenance objects

You need this inspection point type if you want to carry out calibration inspections and record the
results of test equipment inspections or inspections of functional locations.
Inspection points during the production process
The identifiers for the inspection points are defined in the task list header and are valid for all operations.
If you do not define an inspection point identifier in the task list header, the system uses a general
identifier, that is stored in the settings at plant level.
Inspection points form the basis for defining partial lots with their own usage decisions. When used with
control charts, inspection points are suitable for statistical process control.
If you define the use of inspection points in the task list header, you must specify whether the inspection
points are to be based on time, quantity, or to be freely defined at the operation level. For inspection
points based on time or quantity, you must also specify an inspection interval in the operation. During the
production process, you create a data record that contains inspection results for each inspection point.
You must assign a produced quantity to each inspection point. You can combine the partial quantities for
inspection points into partial lots and the partial lots into batches.
If you use freely defined inspection points with inspection plans outside the production area, the time-
based or quantity-based inspection interval and the management of batches or partial lots is not
supported.
WHATSAPP +255738656506
In Customizing, you can define function modules to generate time-based or quantity-based inspection
points. In addition, for the fields that are to be identified, you can define function modules that propose
and test entries and display entries for selection.
Inspection points to identify physical samples
The identifier for this inspection point type contains an additional field for entering the physical-sample
number.
This inspection point type does not contain functions for partial lot assignment or for time or quantity-
based inspection intervals.
Inspection points to identify maintenance objects
The identifier for this inspection point type contains an additional field for entering the equipment or
functional location number.
This inspection point type does not contain functions for partial lot assignment or for time or quantity-
based inspection intervals.
Standard settings
- The table has the delivery class G. The following name range is reserved for the user: User
field combination 9*, A*, ... , Z*
- The system contains function modules for generating
- Freely defined inspection points
Executable example
- Default values for the inspection point identification Non-executable example

Read the online documentation for these function modules.
Recommendation
Due to the summarization of data at the characteristic level, the maximum number of inspection points
for each operation is limited in the standard system.
For performance reasons, retain the settings in the standard system.
Inspection point definitions are keys for data records in table QAPP. They should therefore not be deleted
in productive operation. Do not change an inspection point definition that has already been used. Instead,
create new entries in the table where required, and flag the old ones as 'no longer to be used'.
Activities
1. Determine:
a) Whether your company carries out multiple inspections for an operation during production or
for other operations and how the intervals for these inspections are defined.
b) Whether you need special identifiers to record inspection results for physical samples. If the
equipment number is sufficient, you should only require the standard entries.
c) Whether you need special identifiers to record inspection results for maintenance objects. If
the sample number meets your requirements, the standard entry should be sufficient.
2. Define appropriate inspection point identifiers by assigning a suitable definition and sequence to the
fields contained in the "Inspection Point Identifiers" table.
3. Specify default values for the usage decisions relating to the inspection points. To do this, refer to
the steps contained in the subsection Inspection Completion. This describes how to define the
quantity of usage decisions as well as the follow-up actions linked to the decisions. You assign
follow-up actions for inspection points in production at partial lot level, and actions for other
inspection points at lot level.
4. Determine whether the number of inspection points at an update is to be limited at characteristic
level, and if necessary set the maximum number accordingly.
5. Determine whether you want to generate inspection points or default values for inspection point
identification with your own function modules and make sure these modules are programmed.
6. Make sure appropriate sampling procedures are maintained for the inspections carried out on the
basis of inspection points. For additional information, refer to the chapter Quality Planning, Basic
Data.
7. Check the settings at plant level. If necessary, define the following default values:
- Sampling procedure used in conjunction with inspection points in production, physical-sample
processing or calibration inspections.
- General inspection point identifier for inspections in production.
- Way the partial lots are created
- Usage decisions for inspection points or partial lots
23.3.2.1.13 Multiple Specifications
23.3.2.1.13.1 Define Object Types for Multiple Specifications
Use
In this IMG activity, you define the object types for multiple specifications. You can define, for example,
whether the object in question is a pharmacopoeia, country, or customer.
The object type controls the transfer of a batches suitability for an object based on multiple
specifications. You must assign a control key to the object type. This control key determines whether the
batch classification is to be performed based on the customer, country, or general object.
The control is technically implemented via a field name. This field name also allows you to use custom
objects for classification.
If you want to store the suitability of a batch for a multiple specification object, you must specify class
characteristics in the table of object types. For each object type, you can specify a characteristic with the
description Suitable For and a characteristic with the description Not Suitable For. Whether you need a
characteristic with a positive valuation or a characteristic with a negative valuation depends on the type
of batch search you plan to use:
If you want to search using the question "Is the batch suitable for...?", you just need characteristics with
positive valuations.
If you also want to search with the question "Is the batch unsuitable for...?", characteristics with negative
valuations are also required.
You define the suitability of a batch for a multiple specification object when making the usage decision.
The system determines a proposed value for each object based on the multiple specification. The user can
WHATSAPP +255738656506
accept or change this proposed value as required. This value is transferred to the corresponding class
characteristic for the batch class when you save the usage decision.
Requirements
You have defined batch classes and class characteristics.
Standard settings
The following three object types are supplied with the standard system:
- Customer
- Country
- Pharmacopoeia
Activities
1. Define which object types require multiple specifications.

2. Define whether the suitability of batches is to be determined based on multiple specifications and
transferred to batch classification.
3. If required, define the class characteristics for each object type that describe whether a product is
suitable or not suitable.
23.3.2.1.13.2 Define Objects for Multiple Specifications
Use
In this IMG activity, you define the objects for multiple specifications. You define the objects for which
dependent characteristic specifications in the form of multiple specifications can be maintained in
inspection planning. These objects can then be used for material-task list assignments in inspection
planning.
In this table, you must also specify an object type for the object. This object type controls the transfer of
batch suitability for an object based on multiple specifications.
You can also use this Customizing table to create a reference to the SAP country key to determine the
suitability of a batch for a country.
Customer numbers can be specified in the material-task list assignment, but the object type Customer
must also be specified in the table of object types so that batch suitability for a customer based on
multiple specifications can be transferred.
Activities
Define the required objects and, if required, assign the countries for which the objects are
valid.
23.3.2.2 Operation
This subsection describes the settings for inspection operations.

You can maintain master records for three object types that are subordinate to an operation:
- Work center
- Production resources and tools (PRT)
- Inspection characteristic
The settings for these three object types are not included in this section, but are described in separate
sections of the Implementation Guide.
23.3.2.2.1 Define Control Keys for Inspection Operations
In this step, you define the control keys for the inspection operations.
Using the operation control key, you can influence the planning and processing of an inspection
operation in several ways. The following indicators are relevant to inspection plans:
- Characteristics
- Inspection characteristics exist.
- Printing
- Shop papers are printed for the operation.
- Scheduling
- The operation is scheduled.
- Costing
- The operation is taken into consideration for costing purposes.
- Processing of confirmations
- The operation is confirmed.
- The operation is confirmed as a milestone.
- External processing
- The operation is processed externally (outside of your own company).
Note: no goods receipt inspection is carried out for the externally processed item upon its
return.
You can describe the control keys using long texts.
Recommendation
WHATSAPP +255738656506
- Define the nomenclature for mnemonic control keys.
- Define your own control keys according to the scope of the logistics functions you intend to
implement. In this way, you will avoid having to repeatedly define new control keys. Activities
1. Make sure you know which functions for the inspection operations are influenced by the control
key.
2. Find out which control keys are needed and coordinate these requirements with all affected
departments.
3. Maintain the table of operation control keys (if necessary, coordinate this with the other modules).
23.3.2.2.2 Define User Fields
In this step, you can define your own fields for the detail screen of an operation, in addition to those that
are already present in the standard system.
The inspection plan contains a group of fields at the operation level that can be defined by the user. You
activate these fields by entering a key word ID in the detail screen for the operation. You use the key
word ID to identify a group of fields.
In the Customizing application, you define such groups of fields by:
- defining key word ID's

- selecting key words for each key word ID from a predefined selection of key words representing
different data types
- assigning a name and a meaning to each of these keywords
Activities
Determine whether you need user-defined fields. If so, define the key word ID's and any associated key
words.
23.3.2.2.3 Define Reduction Strategies for Scheduling
In this step, you specify the reduction strategy to be used when the reduction measures are carried out on
operations. Scheduling reduces the lead_time automatically if the basic dates given are not adhered to,
that is if the scheduled dates lie outside the basic dates.
In this work step, you also define the reduction levels. The reduction takes place level by level no further
than the level that you have specified in the control parameters.
You can specify a reduction strategy in every operation.
- Reduction strategies
You use the reduction strategies to determine how the operation lead time can be reduced step by
step. You can enter a reduction strategy in every operation.
- Reduction levels
You can define up to six reduction levels for each reduction strategy. For every reduction level you
can enter what is to be reduced and by how much.
The SAP system carried out reduction step by step no further than the reduction level specified in the
scheduling parameters.
Note
The order/network is rescheduled after every reduction level. To improve performance we recommend
that you keep the number of reduction steps to a minimum.
Standard settings
The reduction levels are predefined in the SAP standard package.
Activities
1. You should define the reduction strategies.

2. You should define the reduction levels for all the reduction strategies.
23.3.2.2.4 Work Center
In this section, you maintain the settings that can be copied from the work center into the operation.
You can assign a work center to operations. This allows you to use a wide range of data from the work
center master record in the operation. This data can either be referenced, or used as default values. The
data can be used for:
- Scheduling
- Capacity planning
- Costing
- Linking subsystems to process operations and record results
To use the controlling functions of the work center assignment, you must maintain the work center
master data. You can find information on the relevant settings in the Production, Basic Data, Work center
section.
A basic requirement for costing is that you must assign the work center to a cost center.
Activity types and tariffs must also be defined for this cost center. As a prerequisite you must install the
Controlling (CO) application component.
You can find additional information on the linking of subsystems in the Quality Inspection, Subsystems
section.
This section only contains the settings that apply to the use of inspection plans. If you want to carry out
inspections during production, refer the instructions on how to make the settings for the work center
(routing data)! There you will find such settings as the setup optimization and wage determination.
The data from the work center can be used in the operation in two ways:
- as default values
The system proposes the values when you maintain the operations; the inspection planner can
change these values.
- as reference values
WHATSAPP +255738656506
The system always retrieves the current values from the work center and uses them in the operation;
the inspection planner cannot change these values. The person responsible for the work center,
however, can change these values centrally in the work center.
Recommendation
Carefully consider which specifications can be copied from the work center and how they will become
effective in the inspection plan. If you change the way these specifications are used after you have
maintained a large number of inspection plans, considerable problems may result.
23.3.2.2.4.1 Maintain Standard Text Keys
In this step, you maintain the text keys and standard texts for the description of inspection operations.
In the inspection operations, you can specify standard text keys that reference standard texts. These texts
are then displayed as operation texts. Only the long text for the standard text key is displayed and not the
40-character short text for the text key.
Note
Since the standard text keys are treated as master data, they are not transported. You must therefore
maintain the standard text keys in the production system.
Recommendation
Standardize the operation texts as much as possible.

Use mnemonic keys for the standard texts.
Activities
1. Determine which operation texts can be defined as standard texts and coordinate the
definition of these texts with the affected departments.
2. Define the short and long texts for the previously defined keys.
3. Maintain the texts keys and the associated standard texts in the production system.
Additional information
The standard text key can be stored in the work center as a reference value or default value.
The text keys can be used in the following situations:
- for operations in task lists and orders

- for test equipment assignments in task lists and orders
23.3.2.2.4.2 Define Qualifications
In this step, you can define the qualifications that are required for certain inspection operations.
Do not confuse the qualifications at the operation level with the inspector qualifications at the
characteristic level.
You must define the qualifications at the operation level for each plant.
Activities
1. Determine whether qualifications for inspection operations should be managed in your system. If
necessary, have the responsible department in your company define the required qualification
levels.
2. Maintain the table of qualification keys.
The qualifications can be stored in the work center as a reference value or default value.
23.3.2.2.5 Inspection Characteristic
In this section, you maintain the controls at the characteristic level of the inspection plan.
You can store basic data relating to the inspection characteristic in the system in the form of master
inspection characteristics. You can find the relevant settings in the section Quality Planning, Basic Data,
Inspection Characteristic.
You only require the other settings at characteristic level, if you want to record results based on
inspection characteristics. For these settings, see section Quality Inspection / Results Recording.
23.3.2.2.5.1 Define Inspection-Characteristic Origin
Use
In this IMG activity, you define the inspection characteristic origin.

The inspection characteristic origin defines the source, from which the characteristic was copied into the
plan.
Activities
You can store the origins in the Engineering Workbench with the inspection characteristics.
23.3.2.2.5.2 Define Control Methods
Use
In this IMG activity, you define the control methods.

The control method defines the way in which the process is controlled.
Requirements
WHATSAPP +255738656506
The Display Control-Plan Fields indicator is set in the activity, Maintain Settings at Client Level.
Activities
You can store the control method in the Engineering Workbench with the inspection characteristics.
23.3.2.2.5.3 Define Response Plans
Use
In this IMG activity, you define response plans.

The response plan describes the response when the value for product or process characteristics deviates
from the specifications.
Requirements
In the IMG Activity Maintain Settings at Client Level, the Display Control-Plan Fields indicator is set.
Activities
You can store the response plans in the Engineering Workbench with the characteristics.
23.3.2.2.6 Test Equipment
You can represent test equipment (production resources/ tools) according to its purpose, by using
different master record types, such as:
- Material
- Equipment
- Document
- PRT-master record (production resource/ tool master record)
You can find the relevant settings for this in the section Prduction, Basic Data, Production Resources/
Tools.
Depending on the master record type you use, there are additonal settings for document master record,
material master record and equipment master record.
- PRT-master record
This record contains the usual administrative data for planning master records as well as
information relating to status, location and if applicable classification in a PRT group or record.
You can use the link to the Classification System to add additional user-defined specifications.
- Document
The PRT master record can reference document master records; document master records can also
be used directly as test equipment in task lists. An inspector has immediate access to drawings and
other document types using the document management interfaces to CAD systems or to the
ArchiveLink.
- Material
If you need to procure, store or inspect test equipment (general, logistical functions), you must
maintain the material master records for this test equipment.
Batch
If you want to manage individual items or groups of test equipment and differentiate between them,
you can create batch master records in addition to the material master records. If test equipment is
managed in batches, you have the option of triggering calibration inspections using the deadline
monitoring function.
- Equipment
The equipment master record contains the comprehensive functions of PM for the monitoring,
maintenance and calibration of test equipment.
- When production orders are released, the system checks the status of the test equipment, to confirm
that it is available, provided that the equipment has been identified as a production resource/tool.
- Maintenance intervals are controlled on the basis of equipment usage.
- If a maintenance deadline is reached, the system automatically creates a maintenance order.
- Calibration results are stored in a history.
Further notes
The following functions are not currently contained in the standard system. Make sure you guarantee
these functions by taking organizational measures.
- Status monitoring of test equipment that is not represented as equipment or a PRT master record
When production orders are released, the system checks the status of the equipment and PRT
master record. For other types of test equipment, you must make sure that only suitable test
equipment is used.
- Capacity monitoring of test equipment

The following is taken into account for orders/ inspection operations
- Scheduling/ Capacity planning

- Costing
- Confirmation
You can check the availability of test equipment using a report program that displays the current
use of test equipment in production orders.
- Location monitoring (Checking out and checking in of test equipment).
23.3.3 Engineering Workbench
In this section, you make the settings for the Engineering Workbench.
WHATSAPP +255738656506
23.3.3.1 Define Work Areas
In this step, you define the Engineering Workbench work areas for the usage area 'inspection plan'.
Requirements
You must have defined the profiles for default values.
Recommendation
Take note of the F1 field help!
Activities
Define the work areas required by your company.
23.3.3.2 Define Print Layout for Microsoft Word
In this IMG activity, you define templates (layouts) with which you can print header and operation data
via Microsoft Word 97.
Depending on the layout, one or more pages can be printed per header or operation, which you select in
the Engineering Workbench. A layout can include the following data:
- Individual header or operation data, such as description of the work center

- Tables, operation data, component assignments, production resources/tools or inspection
characteristics
- Graphics
You proceed as follows:
1. You define a layout in the ERP system.

2. You define one or more tables.
3. You set the number of graphics you want to appear in each printout.
4. You create a Word document.
5. You create the tables defined in the layout and format them.
6. You create links to the graphics and individual fields.
Then you can begin printing from the Engineering Workbench. The ERP system sends the data to
Microsoft Word and thereby fills the tables, inserts the graphics and then prints the document.
Requirements
Setting up Word 97
To ensure smooth interaction between the ERP system and Microsoft Word 97, set the Options in Word
97, proceeding as follows:
1. Choose Extras -> Options.
The Options dialog box appears.
2. Choose the tab page General, and de-select the indicators Update links automatically and
Display macro warning.
3. Choose the tab page Print and deselect the Update links check box.
4. Choose OK and exit Word.
Creating graphics in the ERP system

Create the graphics that you want to print in the ERP system. You can use graphics with the graphic
formats BMP, GIF and JPG.
1. First of all check in Customizing for the document management system whether the workstation
applications are defined for the appropriate graphic formats. Pay attention to the following in the
detail view:
a) If you want to print bitmaps, you must have the file suffix BMP and MIME type image/x-ms-
bmp .
b) If you want to print GIF files, you must have the file suffix GIF and MIME type image/gif.
c) If you want to print JPEG files, you must have the file suffix JPG and MIME type image/jpeg.
2. Create the graphic as a document in the ERP Document management system. In the group
Original, enter the work station application that is defined in Customizing and then choose the
storage data of the graphic. Finally release the document.
3. Afterwards create this document as a production resource/tool and assign it to the corresponding
operation in the rate routing. For the production resource/tool number enter only a number from a
specific number area (e.g. 800-900) in order to differentiate between the graphics and other
documents, which you have also created as production resources/tools. You must enter this area
later, when you create a layout in the ERP system.
Recommendation
If you want certain printouts, such as operational method sheets, to have the same layout enterprise-wide,
you should first of all create a layout as template, in which you can enter general data, such as the
company logo or page format settings. You can then copy this template for all other layouts that you
want to create.
If you want to print several operations in one step, you can create an additional layout that you use for
printing a cover sheet.
Activities
To print header or operation data via Microsoft Word 97 you first create a layout in the ERP system and
then a Word document. Proceed as follows:
Creating a Layout in the ERP System
1. First of all create a new template in the work step Header data template, by
a) Choosing New entries
b) entering the name and the description of the template
WHATSAPP +255738656506
c) entering the maximum number of graphics that you want to print per operation
d) entering the number area of the production resources/tools, in which you have placed the
graphics
e) Save your entries.
2. In the work step Table assignment define the tables that you would like to print for each
operation. Enter the following data:
a) a key for the table (freely definable)
b) the ERP table that sends the data to Word.
You can, for example, choose the table OPR (operation data)
c) the current Table number in the Word document

You should also enter
d) whether the system is to automatically adjust the number of lines in the table in the Word
document
e) which row is the First row of data in the Word document table
3. Save your entries.
4. In the work step Field assignment, assign the field name of an ERP table to each column of the
Word table. On printing, this field provides the data to Microsoft Word.
5. Save the layout so that you can edit the document in MS Word.
Creating a document in Microsoft Word 97
6. Select a template and then the function key Template to begin Microsoft Word. The system
automatically opens an empty document template in Microsoft Word, which contains the macros
necessary for printing. Therefore you should always begin Word from Customizing for OMS.
7. Create the following objects in the Word document: For each table that you have already defined in
Customizing, create a table in Word.
Note that Word numbers the tables in columns from top to bottom and from left to right. You must
insert the tables in such a way that the table number corresponds to the number which you have
entered in the template in the ERP system.
If you subsequently insert a table into a Word document, Word renumbers all following documents
and you must update the layout in the ERP system.
8. Insert links (placeholder) in the document for the graphics that you would like to print.
a) To do so, select the function key Link and then select the desired graphic from the selection
list. Whilst doing so, keep Microsoft Word constantly open in the background.
The graphics have the key 'PS_PICTURE' followed by a two figure number.
b) Choose Copy to clipboard. The system inserts the links onto the clipboard.
c) Change to Microsoft Word and place the cursor on the place in the document in which you
would like to insert the link.
d) Then choose Edit -> Insert contents.
A dialog box appears.
e) Choose Links.
f) Choose OK.
You have inserted the link.
9. As well as links to graphics, you can also insert links to individual fields of an ERP table. To do so,
proceed as for inserting graphics. The selection list contains all fields of the tables of operation data
OPR and task list header data TSK. You can insert all fields with a name beginning with OPR- or
with TSK-.
10. After you have inserted all objects and the data has been received from the ERP system you can
format the tables and if necessary insert further objects such as your company logo, for example.
Word then prints these objects with every operation.
11. You can save the layout and the document simultaneously in Microsoft Word by choosing Save.
23.3.3.3 Define Field Selection
In this step, you can modify the field selection for the Engineering Workbench. For more information,
see the section Environment / Tools / System Modification / Adapt Field Selection.
23.3.4 Failure Mode and Effects Analysis (FMEA)
23.3.4.1 System Modifications
23.3.4.1.1 Status Profile for User Status
Use
You can use this activity to adjust the general status management to suit your requirements.
Activities
Proceed as described in the documentation for the activity Define Status Profile for User Status
.
Then assign the status profiles to the audit components or, in the case of the audit component "audit", to
the audit type.
The status profile maintained in the audit type takes precedence over the status profile maintained for the
audit component "audit".
23.3.4.1.2 Field Selection
In this process step, you change the field selection.

You can change the properties of the modifiable fields within the constraints pre-defined by SAP. Such
changes to modifiable fields can be made dependent on the influencing fields.
The field selection is valid for a specific program and a specific screen group. For each program used in
audit management, there is a corresponding maintenance function for the field selection. You can find
WHATSAPP +255738656506
the name of the program responsible for a screen using the F1 field help or using the status display in the
system.
23.3.4.1.3 Coding Mask
Use
In this IMG activity, you can define the nomenclature and the corresponding coding masks used in the
FMEA.
From a technical view, this IMG activity is the same as the Audit Coding Mask IMG activity.
23.3.4.1.4 Business Add-Ins (BAdIs)
23.3.4.1.4.1 BAdIs for Archiving
23.3.4.1.4.1.1 BAdI: Write Add-On-Specific Data
Use
The Business Add-In (BAdI) is used in the Failure Mode and Effects Analysis (FMEA)
component (QM-PT-FA) in the WRITE_ADDONS method of class CL_PLM_FMEA_ARCHIVING.
The method is retrieved by program PLM_FMEA_ARC_WRITE (Write Program for Archiving
FMEAs) using the WRITE method of the same class. It enables you to write additional data to the
archive using the WRITE method.
For further information about implementing the BAdI method please see SAP Note 673030.
Standard settings
The Business Add-In can be used more than once.
23.3.4.1.4.1.2 BAdI: Read Add-On-Specific Data
Use
The Business Add-In (BAdI) is used in component Failure Mode and Effects Analysis
(FMEA) (QM-PT-FA) in the WRITE_ADDONS method of class CL_PLM_FMEA_ARCHIVING.
The method is retrieved by program PLM_FMEA_ARC_WRITE (Write Program for Archiving FMEAs)
using the WRITE method of the same class. It enables you to read additional data using the
PREPARE_WRITE method.
Requirements
None.
Standard settings
23.3.4.1.4.1.3 BAdI: Delete Add-On-Specific Data
Use
The Business Add-In (BAdI) is used in the Failure Mode and Effects Analysis (FMEA)
component (QM-PT-FA) in the DELETE_ADDONS method of class CL_PLM_FMEA_ARCHIVING.
The method is retrieved by program PLM_FMEA_ARC_DELETE (Delete Program for Archiving
FMEAs) using the DELETE method from the same class. It enables you to delete extra data from the
databank using the DELETE method.
Standard settings
23.3.4.1.4.1.4 BAdI: Add-On-Specific Checks
Use
The Business Add-In (BAdI) is used in the Failure Mode and Effects Analysis (FMEA) component
(QM-PT-FA) in program PLM_FMEA_ARC_CHECK (Preprocessing Program for Archiving FMEAs).
It enables additional checks of individual archivability criteria using the CHECK method (FMEA
Archivability Check).
Standard settings
WHATSAPP +255738656506
23.3.4.1.4.2 BAdIs Inside the Application
23.3.4.1.4.2.1 Definition of Text Types for Each Audit Component
Use
This Business Add-In (BAdI) is used in the Audit Management (CA-AUD) component.
You use this BAdI to set long text processing for the different audit components.
Requirements
The method GET_TEXT_IDS is only relevant outside of a CRM system.

If you are working in a CRM system, you edit the activity Define Text Objects and Text Types in the
Implementation Guide (IMG) instead of the method GET_TEXT_IDS. The text types used in audit
management are defined using the text object CGPL_TEXT in the CRM standard system.
Standard settings
The following text types are supplied in the standard system:
Text determination procedure/Object types Description

AQN Audit Management: Audit question
AUO Audit Management: Audit
AUP Audit Management: Audit plan
COR Audit Management: Corrective actions
QUE Audit Management: Question
QUN Audit Management: Question lists
Activities
After you call the IMG activity, the system displays a dialog box where you enter a name for the
implementation.
If implementations of this Business Add-In have already been created, the system displays them in a
dialog box. You then choose one of them by choosing Create, and continue as follows:
1. In the dialog box, enter a name for the implementation of the Add-In and choose Create. The
system displays the initial screen for creating Business Add-In implementations.
2. On this screen, enter a short description for you implementation in the Implementation Short Text
field.
3. If you choose the Interface tab, you will notice that the system has filled in the Name of the
Implementing Class field automatically, by assigning a class name based on the name of your
implementation.
4. Save your entries and assign the Add-In to a package.
5. To edit a method, double-click its name.
6. Enter your implementation code between the method <Interface Name>~<Name of
Method>. and endmethod. statements.
7. Save and activate your code. Navigate back to the Change Implementation screen.
Note: You can also create an implementation for an Add-In and not activate it until later. If you
want to do this, do not carry out the following step:
8. Choose Activate.
When the application program is executed, the system carries out the code in the method you wrote.
Copy the standard implementation and change the text types for each audit component.
Example
To display the sample code, choose Goto --> Sample Code --> Display.
See also:
Method:
Edit Text Type
Returns the Text IDs for the XML Transfer of Questions
Returns the Text IDs for the XML Transfer of Audit Questions
23.3.4.1.4.2.2 Enhancement for Search Helps
Use
This Business Add-In (BAdI) is used in the Audit Management (CA-AUD) component.
You can use this BAdI to change the input help (F4 help) values for a number of fields.
Standard settings
This Business Add-In is not active in the standard system.
Activities
implementation.
field.
implementation.
WHATSAPP +255738656506
8. Choose Activate.
Example
To display the sample code, choose Goto--> Sample Code --> Display.
See also:
Methods
- Read Values for Grouping

- Read Values for 'Search Field'
23.3.4.1.4.2.3 Maintenance of Help Links
Use
This Business Add-In is used in the Audit Management (CA-AUD) component.

You can use this BAdI to implement enhancements within Audit Management (transaction code
PLMD_AUDIT).
Standard settings
Activities
implementation.
field.
implementation.
8. Choose Activate.
Example
To display sample code, choose Goto -> Sample Code -> Display.
See also:
Methods
Getting the URL for Initial Screen
Object-Specific Processing of Help Request
####################################################################################
#
23.3.4.1.4.2.4 Provide Signature for FMEA
Use
This Business Add-In (BAdI) is used in the Failure Mode and Effects Analysis (FMEA) component.
You can use this BAdI to influence the signing of a FMEA. You can, for example, display a digital
signature.
Method Description
SIGN_FMEA Sign FMEA
DISPLAY_SIGNATURES Display Signatures
SIGNATURES_EXISTS Existing Signatures for FMEA
23.3.4.1.4.2.5 Influence Generation of FMEA Actions and List Items
Use
This Business Add-In (BAdI) is used in the Failure Mode and Effects Analysis (FMEA) component.
You can use this BAdI to influence how defects, causes, and actions are copied from a quality
notification to a Failure Mode and Effects Analysis (FMEA).
For more information, see the documentation for the methods:
- ACTION_TYPE_ALLOWED
- ADOPT_ACTION_DATA
- ADOPT_LIST_ITEM_DATA
WHATSAPP +255738656506
Standard settings
This BAdI is filter-independent and cannot be used more than once.
Activities
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for
SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.
Example
In the standard system, the actions are copied from a quality notification as detection actions, for
example. You can use this BAdI to override this.
23.3.4.1.4.2.6 BAdI: Restriction of Partner Roles for FMEA Object Types
Use
You can use the Business Add-In (BAdI) BADI_PLM_AUD_ROLES_RSTR (Restriction of Partner
Roles for Audit Components) to restrict the partner roles for an FMEA, preventive and detection actions,
and question lists.
You can find the BAdI and the BAdI documentation under Cross-Application Components
-> Audit Management -> System Adjustment -> Business Add-Ins (BAdIs) -> BAdIs Within the
Audit Application -> BAdI: Restriction of Partner Roles for Audit Components.
23.3.4.1.4.3 BAdIs for FMEA Objects and for Valuation
23.3.4.1.4.3.1 Valuation of Audit (Key Figure Calculation)
Use
This Business Add-In is used in the Audit Management component and in derived components such as
the Failure Mode and Effects Analysis (FMEA).
This BAdI contains the methods for the calculating and valuating the audit question list and the audit as a
whole, or the general valuation of an investigation.
When implementing this BAdI, you must specify a filter type before the implementation of the methods
can take place. This filter type corresponds to the field Procedure in the question list, in the audit
question list, and in the audit, or in the investigation and its list items.
Standard settings
Activities
implementation.
field.
3. If you choose the Interface tab, you will notice that the system has filled in the Name of
the Implementing Class field automatically, by assigning a class name based on the name of your
implementation.

8. Choose Activate.
Example
See also:
Interface
IF_EX_PLM_AUDIT_CALCULATE.
Methods
- Calculation of Audit Question List

- Calculation of the Audit
- Read Various Settings
- Display of Valuation Information
- Check Whether Valuation Information Can Be Displayed
###################################################################
WHATSAPP +255738656506
23.3.4.1.4.3.2 Definition and Structure of an Audit Object
Use
This Business Add-In Business Add-In(BAdI) is used in the Audit Management, Failure Mode and
Effects Analysis (FMEA) and other components.
This BAdI contains the methods for checking, selecting and displaying the object for an investigation,
depending on the investigation type. In Audit Management, we use the terms Audit Objects and Audit
Types. The information below relates specifically to use in Audit Management but the description
applies to investigations in general.
Since it is not possible to plan all possible audit objects in a standard software, and external data may
have to be accessed, the audit object is connected using this interface. As a result, you can create your
own implementations (in addition to those supplied by SAP) without having to make modifications.
Within this interface, you can access the detailed information about the audit object that was defined in
Customizing for the audit type.
A filter type must be specified when this BAdI is implemented. This filter type is assigned in
the field Input Values for Audit Object (BAdI) (technical field name PLMV_AUDIT_TYPE-FILTER)
in Customizing for the audit type.
Standard settings
Activities
implementation.
field.
implementation.
8. Choose Activate.
Example
Audit type: External product audit of product 4711 for the vendor IDES.
The audit object "Product 4711 for vendor IDES" is described by the two attributes Product (attribute
type 01) and Vendor (attribute type 02). You define the associated data elements for the entry fields in
Customizing. During the BAdI implementation, the system then accesses the data for the business
partner and the product master record that exists in the system.
Audit type: Internal system audit in development AREA1 according to ISO 9000.
The audit object is described by the two attributes QM System and Area. The auditor therefore sees two
entry fields for the audit object with those field labels that were defined in Customizing for the audit
type.
You define the input values for the possible QM systems in a separate value table in Customizing for the
audit type. No value table exists for the individual areas in the system yet. During BAdI implementation,
you access an external system.
Recommendation
The implementation must be in line with the Customizing entries for the audit type. The technical
properties of the entry fields are defined in Customizing. This allows you to cover different audit types
during an implementation.
Further notes
You can find technical details about the individual methods in the interface documentation for the
interface: IF_EX_PLM_AUDIT_OBJECT.
Methods
- Consistency Check of Audit Object (->Error Log)

- Input Help Using F4 for the Audit Object
- Display Audit Object (Table) in the Audit Overview
- Read Description of Audit Object
- Display of the Audit Object
- Conversion of User Entries to Internal Data Format
23.3.4.1.4.4 BAdIs for Manipulating Individual Objects
23.3.4.1.4.4.1 Definition of Action Types
23.3.4.1.4.4.1.1 BAdI for Definition of Action Types
Use
This Business Add-In (BAdI) is used in the Audit Management component and and other derived
components, such as Failure Mode and Effects Analysis (FMEA).
You can use this BAdI to influence the interface and behavior of action types. You can control the use of
action types using the BAdI BADI_PLM_AUDIT_ACTION_TYPE.
WHATSAPP +255738656506
Standard settings
The BAdI is filter-dependent and not designed for multiple use.

In the standard system, the implementations of the action types supplied by SAP are activated. There is
no default code. In the implementation, you can change the screens and functions of the action.
To use your own implementation, first create an action type and then an implementation for it.
Activities
See also
This BAdI uses the interface IF_EX_PLM_AUDIT_ACTION_TYPE.

For more information, display the interface in the Class Builder.
23.3.4.1.4.4.1.2 Define Action Types
Use
In this activity, you create action types. You can create implementations for the BAdI
BADI_PLM_AUDIT_ACTION_TYPE for these action types. With your own implementation of the
BAdI you can create actions of the appropriate type.
23.3.4.1.4.4.2 Definition of List Item Types
23.3.4.1.4.4.2.1 BAdI for Definition of List Item Types
Use
This Business Add-In (BAdI) is used in the Audit Management component and other derived
components, such as the Failure Mode and Effects Analysis (FMEA).
You can use this BAdI to change the interface and the attributes for a list item type that is used in an
investigation (audit, FMEA, and so on). You can assign list item types to the items of hierarchy profiles.
Standard settings

In the standard system, the implementations of the list item types supplied by SAP are activated. There is
no default code. In the implementation, you can change the screens and the functions for the list items or
audit questions.
To use your own implementation, first create a list item type and then an implementation.
Activities
See also
This BAdI uses the interface IF_EX_PLM_AUDIT_LIST_ITEM_TYPE.

23.3.4.1.4.4.2.2 Define List Item Types
Use
In this activity, you create list item types. You can create implementations for the BAdI
BADI_PLM_AUDIT_LIST_ITEM_TYPES for these list item types.
When you define the hierarchy profile, you can use the list item types defined here.
23.3.4.1.4.4.3 Definition of Structure Types
23.3.4.1.4.4.3.1 BAdI: Structural View for Investigations (Audit, FMEA...)
Use
You can use this BAdI to display investigations (audits, FMEA, and so on) and linked objects
hierarchically. To do this, you open the Hierarchy Display view in the cockpit.
Requirements
You have stored a structure type for the investigation type (audit type, FMEA type, and so on).
Standard settings

To fulfill your own requirements, define a new structure type and create an implementation for
BADI_PLM_AUDIT_STRUCTURE.
In the standard system, the BAdI implementation PLM_AUDIT_STRUCTURE_500 is activated. This
implementation allows you to display the history of the same investigation object for an investigation.
Activities
WHATSAPP +255738656506
See also
This BAdI uses the interface IF_EX_PLM_AUDIT_STRUCTURE.

23.3.4.1.4.4.3.2 Definition of Structure Types
Use
In this activity, you create structure types. For these structure types, you can create implementations for
the BAdI BADI_PLM_AUDIT_STRUCTURE.
You can specify the structure type when you define the investigation type (audit type, FMEA
type, and so on).
23.3.4.1.4.4.4 BAdI: Additional Tab Page in FMEA Cockpit
Use
This Business Add-In (BAdI) is used in the Failure Mode and Effects Analysis (FMEA) (QM-PT-FA)
component. Using this BAdI, you can map a new tab page with additional data to the FMEA in the
FMEA cockpit.
Activities
23.3.4.1.4.4.5 BAdI: Assign Question Lists to an Investigation (Audit, FMEA,...)

Use

You can use this BAdI to influence the assignment of question lists to the audit, or the creation of an
audit question using a template of a question list item.
Standard settings
Activities
implementation.
field.
implementation.
8. Choose Activate.
Example
See also:
Methods
- Changing the Attributes of the Audit Question List Item

- Check whether a question list can be assigned to the audit
- Check whether the question list can be assigned to the audit
23.3.4.1.4.4.6 Identification of Audit Components (Number Assignment)
Use
WHATSAPP +255738656506
You can use this BAdI to influence the following functions within Audit Management:
- Internal number assignment

- Description and identification of audit components within the navigation structure
- Change options for the key of an audit component
Standard settings
Activities
implementation.
field.
implementation.
8. Choose Activate.
Example
See also:
Methods:
- Preassign Key When Creating Audit Component

- Define Display of Audit Component in Navigation Structure
- Can Key Be Changed ('0' -> Not Changeable)
Interfaces
IF_EX_PLM_AUDIT_IDENTIFIER.
##############################################################
23.3.4.1.4.4.7 BAdI for Functional Enhancement of Investigation Type (Audit

Type,...)
Use
You can use this BAdI to define additional menu functions for an investigation (audit, FMEA, and so on)
and its processing.
Standard settings

You can create one implementation per investigation type.
In the standard system, BAdI implementations for some investigation types supplied by SAP are
activated. There is no default code. Additional menu functions were included in the implementations.
Activities
See also
This BAdI uses the interface IF_EX_PLM_AUDIT_TYPE.

23.3.4.1.4.4.8 Linkage of Objects with the Corrective Action
Use
This Business Add-In (BAdI) is used in the Audit Management (CA-AUD) component and in other
derived components such as the Failure Mode and Effects Analysis (FMEA).
You can use this BAdI to create objects for a corrective action via the cockpit. The objects you create in
this way are displayed under the corrective action in the tree structure.
For more information on the indivual methods, see the documentation of the interface methods.
Standard settings
WHATSAPP +255738656506
Activities
implementation.
field.
implementation.
8. Choose Activate.
Example
The quality notification is being connected using the sample code.

To display the sample code, choose Goto --> Sample Code --> Display.
See also:
Methods:
Request Menu with Assignment Functions
Generate Objects
Request for Display Characteristics
Request for Context Menu Functions
Transfer Interface Function Code for Execution
######################################
23.3.4.1.4.5 BAdIs for Updating a Further System or Table
23.3.4.1.4.5.1 XML Generation
Use
This BAdI can be used to change the way in which the audit confirmation is displayed in HTML format.
It can also be used to control the generation of the XML file when importing and exporting audit
components.
Standard settings
The Business Add-In is not active in the standard system.
Activities
implementation.
field.
implementation.
8. Choose Activate.
Example
Description
See also:
Methods:
- Add Data to Audit XML

- Determine XSLT File Name for Survey Generation
- Change XML File During Export
WHATSAPP +255738656506
- Change XML File During Import
23.3.4.1.4.5.2 FMEA: Adjustment of Monitor & Lists
Use
You can use this BAdI and the corresponding methods for all changes to the ALV lists for FMEAs, list
items and actions. Traffic lights with a defined status can also be shown for all three categories.
Standard settings
This BAdI has a default implementation for the traffic lights for list items and actions.
See also: Methods
- Adjust Appearance in ALV Display

- Adjust Columns in ALV Table
- Add User-Defined Function
- Execute User-Defined Function
- Adjust FMEA Table
- Adjust Action Table
- Adjust List Item Table
- Adjust Settings for ALV Table
23.3.4.1.4.5.3 Create, Change, and Delete Question Lists
Use

You can use this BAdI or the corresponding methods to record all changes made to a question list and the
related items (create, change, delete). can then use it to replicate the changes in another system.
You can process changes at the following points in time:
- AT_SAVE
The user has called the function Save in the dialog. At this point in time, you can implement
another check of the data to be saved. If errors are found during this check, this information can be
returned. The data is not saved, and the user is informed.
- BEFORE_UPDATE
The call is performed immediately before the data is transferred to the update. No messages can be
output at this point. The save cannot be stopped.
- IN_UPDATE
The call takes place in the update. No messages can be output at this point.
Standard settings
Activities
implementation.
field.
implementation.
8. Choose Activate.
Example
See also:
Methods:
- Create Header When Saving

- Create Header Before Update Task Is Called
- Create Header in Update Task
- Create Item When Saving
- Create Item Before Update Task Is Called
- Create Item in Update Task
- Change Header When Saving
- Change Header Before Update Task Is Called
- Change Header in Update Task
WHATSAPP +255738656506
- Change Item When Saving
- Change Item Before Update Task Is Called
- Change Item in Update Task
- Delete Header When Saving
- Delete Header Before Update Task Is Called
- Delete Header in Update Task
- Delete Item When Saving
- Delete Item Before Update Task Is Called
- Delete Item in Update Task
############################################################################
#############################################
23.3.4.1.4.5.4 Create, Change, and Delete Actions
Use
You can use this Business Add-In (BAdI) or the corresponding methods to enter all changes to a
corrective/preventive action (create, change, delete). You can then use it to replicate the changes in
another system.
You can process changes at the following points in time:
- AT_SAVE
The user has called the function Save in the dialog. At this point in time, you can implement still
implement a check of the data to be saved. If errors are found during this check, this information
can be returned. The data is not saved and the user is informed.
- BEFORE_UPDATE
The call is performed immediately before the data is updated. No messages can be output at this
point. The save cannot be stopped.
- IN_UPDATE
The call takes place during the update process. No messages can be output at this point.
Standard settings
This BAdI is not active in the standard system.
Activities
implementation.
field.
implementation.
8. Choose Activate.
Example
See also:
Methods
- Create Action When Saving

- Create Action Before Update Task Is Called
- Create Action in Update Task
- Change Action When Saving
- Change Action Before Update Task Is Called
- Change Action in Update Task
- Delete Action When Saving
- Delete Action Before Update Task Is Called
- Delete Action in Update Task
########################################################################
23.3.4.1.4.6 General BAdIs
23.3.4.1.4.6.1 Scheduling of Background Jobs
Use

You can use this BAdI to transfer job information that is required for background processing.
Standard settings

WHATSAPP +255738656506
Activities
implementation.
field.
implementation.
8. Choose Activate.
Example
See also:
Methods
- GET_JOBLIST
23.3.4.1.4.6.2 Authorization Assignment in FMEA Processing
Description
This BAdI contains the method "SET_AUTHORITY_ACTIVITIES". It is used to choose the possible
activities for a user in audit processing.
You can find technical details about this method in the interface documentation
IF_EX_PLM_AUDIT_AUTH_CHECK.
Example
- If activity "3105" is assigned to a user, this user can valuate the audit.
- If the activity "3214" is not assigned to a user, this user cannot confirm the audit.
Standard settings
In the transaction for definition of the BAdI "PLM_AUDIT_AUTH_CHECK", you can find the default
coding delivered by SAP and the proposed activities.
Activities
implementation.
field.
implementation.
8. Choose Activate.
#################################################
23.3.4.2 Lists
23.3.4.2.1 Valuation Specifications
In this process step, you define valuation profiles and the associated valuation levels.
You define for each valuation profile, whether the valuation is to be qualitative (coded) or quantitative.
- For each qualitative valuation profile, you create codes in a values set in a subordinate valuation
table, and you determine the optimum and minimum points, as well as the number of points for the
WHATSAPP +255738656506
codes. On the basis of the number of points, you can assign a quantity to a qualitative valuation.
You can flag a code as a proposed value for the valuation.
- For each quantitative valuation profile, you define the scale area, the scale increments, and a
valuation proposal on a detail screen. You can flag a scale value as a proposed value for the
valuation.
In the valuation profile, you can reverse the scale direction for the valuation, that is, you can define that
the least number of points or the lower end of the scale represent the optimum result.
Standard settings
The tables of the view cluster have delivery class G.
For your own entries, use keys in the namespace 1* to 4*, and A* to Z*.
Recommendation
Do not make any changes to the audit profiles once these have been used, because this could lead to error
interpretations for audits that have been completed. If necessary, replace these profiles with changed
profiles.
23.3.4.2.2 Structure of List of Questions
In this process step, you define the hierarchical structure of question lists and the hierarchy levels at
which valuations are performed.
Question list profiles can be subdivided over several hierarchy levels. Questions are possible for all
hierarchy levels, but valuations are only possible for the levels that you define.
Standard settings

For your own entries, use numerical keys in the namespace 1* to 4*.
23.3.4.2.3 Priorities
In this process step, you define priorities for objects in the question list. These priorities can, for example,
be used during the valuation of these objects.
Standard settings
This table has delivery class G.

For your own entries, use keys in the namespace 1* to 4*, and A* to Z*.
23.3.4.2.4 List Structure
Use
In this IMG activity, you define the hierarchical structure of the lists that you can use in the Failure Mode
and Effects Analysis (FMEA).
The hierarchy profile can be subdivided into several hierarchy levels.
Standard settings
The view cluster tables are delivery class G. For your own entries, only use purely numerical keys with
namespace 1* to 4*.
23.3.4.3 FMEA Definition
23.3.4.3.1 Rating
In this process step, you define the ratings.
Standard settings

For your own entries, use the keys 1* to 4*, and A* to Z*.
23.3.4.3.2 FMEA Types
Use
In this IMG activity, you define the FMEA type.
WHATSAPP +255738656506
The FMEA type is described in more detail by a FMEA category (System FMEA, Process FMEA or
Product FMEA) .
Otherwise the FMEA type is technically similar to the audit type.
23.3.4.4 Control Data
23.3.4.4.1 Data Objects: Define Residence Time
Use
In this work step, you define the residence times of the following, mandatory audit components:
- Question list
- Audit
- Audit plan
Standard settings
The table has the delivery class G.

There is no dedicated namespace reserved for the user.
Activities
Do not create any entries in this table. Process the residence times for the entries available in the standard
system.
23.3.4.4.2 Define Partner Functions
Use
In this IMG activity, you define roles that you can use for the Failure Mode and Effects Analysis (
FMEA) and the control plan ( CP).
For more information about roles, see the Implemenataion Guide (IMG) under Partner Roles in Audit
Management.
23.3.4.4.3 Authorization Groups
In this process step, you define authorization groups. These authorization groups can or must be entered
in audit components.
Requirements
If you want to use authorization groups, you must assign authorization profiles that contain the
authorization object AUDIT_AUTH to the users.
23.3.4.4.4 Data Objects: Properties, Forms
Use
In this IMG activity, you define the properties of data component categories, such as for the
FMEA.
For more information about data component categories, see Definition of Audit Components.
23.3.4.4.5 Specify Number Range Intervals for BAdI Implementation
Use
For the elements of an FMEA and an audit, you can define that sequential external numbers are
generated automatically when an object is created. You can define different number range intervals,
which you then assign to the individual object types.
Requirements
There must be an active implementation for the BAdI PLM_AUDIT_IDENTIFIER:
- BAdI implementation using your own implementation class

To be able to use automatic number assignment, a call of the static method
"GENERATE_NEW_EXTERNAL_ID" from the example implementation class
"CL_EXM_IM_PLM_AUDIT_IDENTIFIER" must be implemented in the method
"IF_EX_PLM_AUDIT_IDENTIFIER~GET_EXTERNAL_ID".
- BAdI implementation using example implementation class

"CL_EXM_IM_PLM_AUDIT_IDENTIFIER"
No other steps are required to use automatic number assignment.
WHATSAPP +255738656506
Activities
1. Define the number range intervals.

2. In Customizing activity Audit Components: Properties, Forms, assign a number range interval
to the different object types.
23.3.4.4.6 Digital Signature
23.3.4.4.6.1 Settings in User Maintenance
Use
In this Customizing activity, you specify the data in the user master record of the person who is to
execute the signature. You enter the full name of the user and their time zone. When a signature is
executed, the system copies the signatory name together with the local time according to the signatory's
personal time zone to the signed document.
Note
You must enter the user data in the productive system, that is, in each system in which the digital
signature is to be available, as the settings in the user master cannot be transported.
Caution
Each user can maintain his or her address data and default values under System -> User Profile -> Own
Data. This data includes the general user settings and the SFF settings for the user. If you are working
with the digital signature, you should therefore not allow all users authorization to maintain their own
data.
Requirements
Basic Information for Digital Signature
Activities
Specify the general user settings:
1. To do this, either execute the Customizing activity or choose Tools -> Administration -> User
Maintenance in the SAP Easy Access menu.
2. Enter the user ID of the user whose data you want to maintain and choose Change.
3. Choose the Address tab and enter the user's first and last name.
4. Choose the Defaults tab and enter the user's personal time zone.
5. Choose Save.
6. If you want to use the user signature, you must also enter the SSF information in the user master
for the user who is to execute a digital signature:
a) Choose the Address tab of the user.
b) Choose the Other Communication pushbutton and double-click the SSF entry to open the
dialog box for maintaining SSF addresses.
c) Enter the SSF information for the security product used.
How the entries must be structured depends on the security product you are using. For more
information, see the document Maintaining User SSF Information in the SAP NetWeaver
documentation.
d) Choose Copy and save your entries.
23.3.4.4.6.2 Signature Strategy
23.3.4.4.6.2.1 Define Authorization Groups
Use
In this activity, you define the authorization group that can provide a specific individual signature when
executing signature strategies.
You use user groups if individual signatures are to be executed in succession by different groups of
users, such as production operators, shift managers, and QM employees, and this process is to be
implemented with a signature strategy. This has the advantage that an individual signature is only
executed when the system has verified that the correct user group was assigned to the user for this
individual signature.
You use the authorization groups to restrict the authorization for executing digital signatures in
applications as follows:
- You define different authorization groups for users with different areas of responsibility.
- In the user master record, you assign authorizations for the authorization group that corresponds to
the user's area of responsibility (authorization object C_SIGN_BGR). Depending on the application,
it may also be necessary to assign the authorizations for the C_SIGN authorization object.
- You define individual signatures that must be created by the user of a specific authorization group
and use them in the signature strategies for the relevant application.
Activities
1. Determine which user groups or which areas of responsibility must be distinguished in your
company.
2. Define an authorization group for each user group.
Example
In your company, specific input values must be entered by an employee and then verified by a second
employee. Make the following settings:
- Define the authorization groups EING (entry) and VERIF (verification).

- The employees that enter data receive authorization for the EING group and the employees that
check data receive authorization for the VERIF group.
- Define two individual signatures for the relevant applications and assign the first to authorization
group EING and the second to authorization group VERIF.
Further notes
WHATSAPP +255738656506
Authorization groups are valid in all areas in which the digital signature with signature strategy is used.
Therefore, before you change existing authorization groups or use them for your purposes, ensure that
this will not lead to conflicts of interest with other areas.
23.3.4.4.6.2.2 Define Individual Signatures
Use
In this IMG activity, you define the digital individual signatures that must be executed by users in a
specific authorization group.
You can then use the individual signatures as substeps of a signature strategy that is executed in the
relevant application if you sign a process step or confirm an input value outside the permitted value
range.
Requirements
You have defined authorization groups (see Defining Authorization Groups).
Activities
Define the individual signatures that must be executed in the relevant application when signing a process
step or for an invalid input value.
Example
In your company, invalid input values must be signed by the employee responsible for the values and
must be checked and signed by another employee. You define the following individual signatures:
- S1 with authorization group EING

- S2 with authorization group VERIF
Further notes
Individual signatures are also valid in other areas in which the digital signature is used. Therefore, before
you change existing individual signatures or use them for your purposes, ensure that this will not lead to
any conflicts of interest with other areas.
23.3.4.4.6.2.3 Define Signature Strategies
Use
In this Customizing activity, you define signature strategies. To do this, make the following settings:
- Group individual signatures of different user groups into one signature process. - Define
which signature method is used when the signature process is executed.
In Customizing for the application you can then define which signature strategy is used to execute a
process step.
Requirements
You have defined individual signatures (see Define Individual Signatures).
Activities
To create a new signature strategy, execute the following activities:

A. Create new entry for the signature strategy
1. Choose New Entries.

2. Create the key, name, and signature method for the signature strategy.
3. Define whether the following options are required, possible, or disallowed:
- Comment
Here, you can specify if the user has the option of entering a text comment when signing the
application. You have the following options: Disallowed (no comment field is provided),
Possible (comment field can be called up), and Required (signature is only possible after a
comment has been entered).
- Remark
Here, you enable the user to select a remark from a list of predefined remarks and add it to the
signature. The availability of remarks depends on the respective application. You have the
following options: Disallowed, Required, and Possible.
- Document
Here, you specify if the document to be signed should also be displayed to the signatory. You
have the following options: Disallowed, Possible, and Required.
- Verification
Here, you allow signatures that have already been executed to be verified. A check is run in
the background to determine if this document is still identical to the original document and if
the previously executed signatures have been stored correctly in the system.
Note:
These settings are overridden if you chose the setting Disallowed for these options in the
transaction SIGNO (Register Signature Objects for Digital Signature) for the application.
B. Assign individual signatures
In this step, you assign the individual signatures that can or must be executed when executing the
strategy, to the signature strategy.
You can assign the same individual signature more than once or you can assign several individual
signatures with the same authorization group. However, when executing the signature strategy, each user
in the authorization group can only execute one signature.
When saving, the system specifies a counter for each assigned individual signature. The counter
identifies the assignment within the signature strategy but has no influence on the signature sequence
when the strategy is executed.
1. Select the signature strategy to which you want to assign individual signatures and choose Assign
Individual Signatures.
2. To assign new signatures, choose New Entries.
3. Enter the key for the required individual signatures.
4. Save the settings.
WHATSAPP +255738656506
C. Define the signature sequence
In this step, you define the sequence in which the individual signatures in a signature strategy must be
executed.
You determine the signature sequence by selecting a predecessor for each individual signature, in a
sequence matrix.
Then you can also list the predecessors for each individual signature. However, you cannot edit the data
in the individual display.
Example:
Individual signatures S1, S2, S3, and S4 are assigned to a signature strategy. The
signature sequences are specified in the matrix, as follows:
Predecessor
Signatures
Signatures to Be Executed S1 S2 S3 S4
S1
S2 X
S3 X
S4 X X
This means:
- S1 must be executed first.

- S2 and S3 can be executed after S1.
- S4 can be executed as soon as S3 is available.
Defining signature sequences in the matrix:
1. In the Define Signature Strategy view, select the signature strategy for which you want to specify
the signature sequence.
2. Choose the Signature Sequence pushbutton.
The system displays the dialog box for the signature sequence of the signature strategy. The dialog
box shows the matrix of the individual signatures.
3. In each row, flag the direct predecessors of the individual signature listed at the start of the row.
4. Choose Enter.
If necessary, the system adds the indirect predecessors for the signatures.

Displaying predecessors for individual signatures:
1. Select the signature strategy for which you wish to display data.
2. Choose Assign Individual Signatures.
3. Select the individual signatures for which you wish to display the predecessor.
4. In the navigation area, choose Display Predecessor.
D. Define release statuses

In this step, you define one or more alternative release statuses for a signature strategy. For each release
status, you determine a combination of individual signatures with which the signature process can be
completed.
A signature process is only complete if all the signatures belonging to a release status have been
executed.
If you do not define a release status for a signature strategy, all the individual signatures in a signature
strategy must be executed in each signature process.
To define a release status, you flag the required signature combinations in the overview of possible
signature combinations.
You can then also list the individual signatures for each release status. However, you cannot edit the data
Example:
The following signature sequence is defined in a signature strategy:

Predecessor Signatures
S1
S2
X S3
X
S4 X X
In the tabular overview, select the following release statuses:
Individual Signatures Required for Release
S1 S2 S3 S4
X X X
X X X
The signature strategy can be completed with either S2 and S3 or with S4.
Flagging the release status in the tabular overview:
1. Select the signature strategy for which you want to define release statuses.
2. Choose Display Release Statuses.
A table is displayed with all the possible signature combinations contained in the signature strategy.
3. Select the signature combinations that you want to use as the release statuses for the signature
strategy.
4. Choose Enter and save the settings.
Displaying individual signatures for each release status:
3. Select the release status whose data you wish to display and choose Display Individual Signatures.
A list appears with the counters for the individual signatures that are assigned to the release status.
Further notes
WHATSAPP +255738656506
Signature strategies also apply in other areas where digital signatures are used. Therefore, before you
change existing signature strategies or use them for your purposes, ensure that this will not lead to
conflicts of interest with other areas.
23.3.4.5 Risk Analysis
23.3.4.5.1 Activate BC Sets for FMEA Risk Analysis
Use
In this Customizing activity, you activate the Business Configuration Sets (BC Sets) with which sample
Customizing settings are delivered for the FMEA risk analysis.
Activating a BC Set means that all data from the BC Set is transferred to the corresponding original
tables. Note that existing entries for an object in the original tables are overwritten when this is done.
You can only activate a BC Set if there is no production client in the system.
Requirements
As the respective BC Set refers to objects in FMEA sample Customizing, which is included in the switch
BC Set CA-AUD_PLM_ASSESS_CL_C, this must have been activated first.
Standard settings
When you activate the BC Set, you must adhere to a specific sequence. This sequence is stored in the
hierarchical BC Set QM-PT-FA_RISK_ANALYSIS_SAMPLE_S4.
Proceed as follows:
1. Open the BC Sets by choosing New BC Set Selection -> Select by Attributes. Specify the ID of
the BC Set QM-PT-FA_RISK_ANALYSIS_SAMPLE_S4 as the selection criterion and leave all
other fields empty.
2. Display the contents of the BC Sets.
3. To activate the BC Set, choose Goto -> Activation Transaction.
For more information, see the documentation for the Business Configuration Sets (BC-CUS) component
under Help -> Application Help.
23.3.4.5.2 Define Risk Matrixes
Use
In this IMG activity, you define risk matrixes with which you can perform a risk analysis of the defect
causes in the FMEA.
For the x-axes and y-axes, you specify valuation categories that are used to specify which defect criteria
are taken into account. The valuation categories relate to the different list elements in the FMEA:
- The valuation of the severity is done at the level of the effects.

- The valuation of the probability of occurrence is done at the level of the preventive actions or at the
level of causes if no preventive actions exist yet.
- The valuation of the probability of detection is done at the level of the detection actions.
In addition, you assign a valuation profile to each axis to determine the values displayed below the
respective axis. To be able to use the risk matrixes, they must be assigned to a risk analysis profile.
Requirements
You define valuation profiles in Customizing under Quality Management -> Quality Planning ->
Failure Mode and Effects Analysis -> Lists -> Valuation Specifications.
23.3.4.5.3 Define Risk Analysis Profiles
Use
In this IMG activity, you define risk analysis profiles. You can thus perform a common analysis of
different FMEAs in the FMEA monitor by specifying a risk analysis profile.
Requirements
You have defined risk matrixes.
Activities
You assign the risk matrixes to a risk analysis profile once you have created them under Risk Analysis -
> Define Risk Matrixes.
Make the following settings for the risk analysis:
Classification
You specify a classification for the cells of a risk matrix. Here, the individual cells of the matrix are
assigned a traffic light color (red, yellow, or green) to classify a cause in the matrix appropriately.
Total risk
WHATSAPP +255738656506
You can use the Total Risk indicator to specify that the classification of a cause in a matrix is included in
the total risk. The total risk is used to determine a general risk value for a cause from various different
risk matrixes.
The values result from the classification of the cause:
- Green = 0
- Yellow = 1
- Red = 2
Traffic Light Color for Resulting Classification
In the risk analysis profile, you can define a resulting classification for the color combinations of the
three traffic light colors. The resulting classification is assigned a traffic light color that is displayed for
a cause in the risk analysis in the FMEA monitor or FMEA cockpit. The resulting classification for a
cause is determined from its classification in the individual matrixes. Only those matrixes are taken into
account for which the Traffic Light Color indicator was set.
Views
In the FMEA monitor or cockpit, the risk matrixes are displayed on tabs in the risk analysis. A
maximum of three risk matrixes can be displayed per tab. You define views to display the risk matrixes.
- You specify the matrixes that are to be displayed in a view.

- You specify the order of the display using the sort sequence.
- You define the width dependent on the number of matrixes displayed.
- You specify the position of a risk matrix.
23.3.5 Control Plan
23.3.5.1 Define Control Plan Types
Use
In this IMG activity, you define the control plan type.

When you create a control plan (CP), choose the relevant control plan type.
Requirements
You have already defined structure types and number range intervals in the following IMG activities:
Define Structure Types and Number Range for Control Plan.
23.3.5.2 Define Control Methods
Use
In this IMG activity, you can define the control methods that you can assign to an inspection
characteristic in a task list or inspection plan in the Engineering Workbench.
Requirements
The field is only visible in the Engineering Workbench, if you have set Display CP Fields indicator in
Maintain Settings at Client Level.
23.3.5.3 Define Response Plans
Use
In this IMG activity, you define the response plans, which you can assign to inspection characteristics in
a task list or inspection plan in the Engineering Workbench.
Requirements
The field is only visible in the Engineering Workbench, if you have set the Display CP Fields
indicator in the Maintain Settings at Client Level IMG activity.
23.3.5.4 Define Structure Types
Use
In this IMG activity, define the structure types for the control plan (CP).
You can use this structure type to determine the selection and view of the structure in the control plan.
The structure type is used in the Define Control Plan Types IMG activity.
23.3.5.5 Number Range for Control Plan
Use
In this IMG activity, you can define the number range interval for the control plan.
The number range interval can then be stored for the plan type in the IMG activity, Define Control Plan
Types.
23.3.5.6 Status Profile for User Status
Use
WHATSAPP +255738656506
You can use this IMG activity to adjust the general status management.
Activities
Choose the Define Status Profile for User Status IMG activity.
Finally, assign the status profiles in the Define Control Plan Types IMG activity to the Control Plan
Types.
23.3.5.7 Define Partner Functions
Use
In this IMG activity, you define roles that you can use for the Failure Mode and Effects Analysis (
FMEA) and the control plan ( CP).
For more information about roles, see the Implemenataion Guide (IMG) under Partner Roles in
Audit Management.
23.3.5.8 Business Add-Ins (BAdIs)
23.3.5.8.1 Define Object Categories
Use
In this IMG activity, you define object categories that can be displayed in the control plan (CP).
The object category is stored at the object-type level in the Define Structure Type IMG activity.
23.3.5.8.2 Implement Object Categories
Use
This Business Add In (BAdI) is used in the Control Plan (QM-PT-CP) component.
You can use this BAdI to implement your own object categories, which can be displayed in the structure
of the control plan (CP).
The BAdI contains the following methods:
- READ_ROOT
- READ_CHILDS
- GET_NODE_PROPERTIES
- GET_FUNCTIONS
- GET_FUNCTIONS_FOR_PROCESS
- EXECUTE_FUNCTION
- GET_KEY_FIELDS
- GET_SELECTION_FIELDS
- GET_RELEVANT_FIELDS
- IS_PROCESS_RELEVANT
- RELOAD
- ON_LANGUAGE_CHANGED
- FREE
Requirements
You have defined a object category in the Define Object Category IMG activity.
23.3.5.8.3 Define Process Types
Use
In this IMG activity, you define process categories that can be displayed in the control plan (CP).
In the Define Structure Type IMG activity, store the process type at the process-type level.
23.3.5.8.4 Implement Process Categories
Use
This Business Add In (BAdI) is used in the Control Plan (QM-PT-CP) component.
WHATSAPP +255738656506
You can use this BAdI to implement your own object categories, which can be displayed in the structure
of the control plan (CP).
- GET_FUNCTIONS
- GET_NODE_PROPERTIES
- EXECUTE_FUNCTION
- CHECK_CONSISTENCY
Requirements
You have defined your own process category in the Define Process Categories IMG activity.
23.3.5.8.5 Define Inspection-Characteristic Origin
Use
In this IMG activity, you define the inspection characteristic.
23.3.5.8.6 Implement Inspection-Characteristic Origin
Use
This Business Add-In (BAdI) is used in the control plan CP) (QM-PT-CP) component.
You can use this BAdI to copy characteristics from different sources to an inspection plan or task list.
- GET_CHARACTERISTICS
- CONVERT_CHARACTERISTIC
- REFERENCE_CONVERSION
- SHOW_REFERENCE
- GET_SELECTION_FIELD_LABEL
- GET_SELECTION_FIELD_DATA
- CHANGE_BEFORE_CREATION
Standard settings
The Business Add-In is not active in the standard system.
Activities
Example
You can copy characteristics from a Failure Mode and Effects Analysis (FMEA) into the control plan.
See also
For more information, see the documentation on the methods.
23.3.5.8.7 Enhance Application
Use
You can use this BAdI to change the control plan (CP) application.
In addition, methods that enable you to extend the consistency check are also available.
GET_HEADER_FIELDS
SET_HEADER_FIELDS
IS_STRUCTURE_RELOAD_NEEDED
HAS_CONTROL_PLAN_ALL_CHARS
GET_HEADER_FIELD_ATTRIBUTES
23.4 Quality Inspection

This section deals with the implementation of quality inspection procedures.
SAP QM supports diverse variants for quality inspections. The basic variants among these control
options can work alongside one another and are:
- Basic inspection lot processing; partial functions:

- Inspection lot creation, inspection lot processing, sample calculation
- Defects recording for inspection lot
WHATSAPP +255738656506
- Inspection lot completion, usage decision with quality score, follow-up actions, data update in
QM information system
- Inspection lot processing with inspection plan; supplementary functions:
- Inspection plan selection
- Sample calculation with lot-based dynamic modification based on usage decision
- Printing of shop papers (inspection instruction, sample-drawing instruction, physical-sample
labels)
- Defects recording for inspection operation and inspection characteristic - Inspection
lot processing with results recording; full functionality:
- Recording characteristic results
- Transfer of inspection results to batch valuation
- Sample calculation with dynamic modification based on characteristic valuation -
Inspection with inspection points and the following additional functions:
- Freely-defined inspection points for an operation
- Recording characteristic results and defects for an inspection point - Creation of partial lots
and batches, based on the results for inspection points
A standardized interface supports the processing of the inspection operations in subsystems.
Requirements
- If you only want to use the basic variant "simple inspection lot processing", you must have
performed the necessary steps described in the Quality Planning section Catalog so you can
maintain the usage decision catalog.
To set up the Defects recording function, you must process the corresponding section in "Quality
Notifications".
- If you want to use a basic variant with an inspection plan, you must have performed all of the steps
described in the Quality Planning section under Basic Data and Inspection Planning.
- If you want to use the basic variant "inspection lot processing with results recording", you must
have maintained inspection plans ormaterial specifications
SAP Recommendation
Since SAP QM functions support several modular basic variants, you can implement inspection
processing in stages. Use this to your advantage, so you can coordinate the implementation of the module
with the project capacities you have available.
Activities
1. First, determine:
a) The areas in your company where inspections are to be planned and implemented.
b) The inspection lot origins that are to be used
c) Which basic variants are relevant for your inspection lot processing
2. Then decide on the stages in which inspection processing with SAP QM is to be implemeted
(Bear in mind that you can also expand the inspection plan and inspection characteristic functions
in stages.)
3. Process the detailed steps in the Inspection Lot Processing section and the remaining sections.
Create prototypes in your test system for the various types of quality inspections, to find out about
the range of control options.
Inspection lot processing
This section serves as a guide for implementing the functions for inspection lot processing.
SAP QM can create inspection lots in different situations. The inspection lots are differentiated using the
inspection lot origin.
SAP QM supports a range of inspection processing variants that are differentiated using the inspection
type. The control functions required for this are contained in the following tables and master data:
- Inspection lot origin

- Inspection type
- Material master, inspection setup
Defines the inspection type at plant level. The controls proposed in the inspection type can be
modified and supplemeted in the inspection data for the material.
- Info record for the supply relationship.

- In procurement
Controls the creation of the inspection lot and the inspection type in an acceptance inspection.
- In sales and distribution

Controls the creation of the inspection lot for inspections on goods delivered to customers.
- Inspection plan and other task lists

- Task list header
Controls the creation of
Inspection points and the dynamic modification of sample sizes.
- Operation
Controls the results recording processes and several aspects of inspection point processing.
Contains the inspection specifications and controls results recording. Recommendation
Familiarize yourself with the different options for controlling inspections. To do this, use the F1-Help.
Note: The scope of the control options in the inspection setup for the material depends on the inspection
lot origin that is assigned to the relevant inspection type.
23.4.1 Inspection Lot Creation
In this subsection, you define the controls for inspection lot creation.
Automatic Inspection Lot Creation
If you activate the corresponding inspection type in the inspection setup for the material, the system
creates inspection lots for the following inspection lot origins:
WHATSAPP +255738656506
- Inventory Postings
- 01 Goods receipt for purchase order
- 04 Goods receipt from production
- 06 Return from customer
- 05 Miscellaneous goods movement
- 02 Goods issue
- 08 Stock transfer (for example, from unrestricted-use stock to inspection stock)
- Production
- 03 Production order
- 03 Process order
- 13 Repetitive manufacturing
- Deadline Monitoring of batches
- 09 For the date of the recurring inspection
- 09 For the shelf life expiration date
- Deliveries
- 10 Deliveries to customer with sales order
- 11 Deliveries to customer without sales order
- 12 Other deliveries
- Sample Management
- 15 Inspection lots for physical samples
- External inspection
- 17 Externally triggered inspections
For the system to create inspection lots, you can (or in some cases) must specify the inspection type in
the order type for the following inspection lot origins:
- Production
- 03 Production order
- 03 Process order
- 13 Repetitive manufacturing
An inspection type given in the order type has priority over the inspection type given in the
material.
- Plant Maintenance (for example, with calibration inspection).

- 14 Maintenance orders
In this case the inspection type is only determined using the order type.
Manual Inspection Lot Creation
You can currently only create inspection lots manually for the following inspection lot origins:
- 07 Vendor audit
- 89 Miscellaneous
Activities
1. Determine which inspection lot procedures occur in the work centers where you want to implement
the SAP QM application component.
Create material groups for this purpose, with each group having unique control of the inspection
process. Note: A comparable material group formation is suggested for Quality Management in
Procurement.
2. Choose the appropriate inspection lot origins and inspection types.

3. Determine whether you need several different inspection types for each origin, for example for
model series inspections and normal inspections.
Define these variant Inspection types.
The inspection lot origins are predefined in the standard system. You can assign several inspection
types to each origin; however, you can only use each inspection type for a single inspection lot
origin.
4. If you want to inspect with task lists, determine which task list types are suitable for these origins
and which task list usages are relevant for these inspection types.
(The task list types are proposed by the system in table TCA01.) Currently, the
following task list types are available:
- Q (inspection plan) for general inspections

- N (PP-routing) for production
- M (PP-rate routing) for simple production processes
- 2 (master recipe) for processes
- E (equipment task list) for calibration inspections
- T (task list for functional location)
- A (general maintenance task list ) for general plant maintenance If necessary, define
your own task list usages.
Once you have defined the concept for inspection lot processing as outlined in this documentation, work
through the steps relating to inspection lot creation. Make sure you maintain the inspection types,
inspection origins, number ranges and default values for the inspection type. In addition, implement the
work steps that are dependent on the inspection lot origin.
23.4.1.1 Maintain Inspection Types
In this step, you maintain the inspection types and the controls associated with the inspection type.
Using the online documentation, first familiarize yourself with the meaning of the individual fields in this
table!
Requirements
Depending on the functions and control options you want to use, you must make sure the following
conditions are met before you can maintain the table:
WHATSAPP +255738656506
- Catalog 3 for usage decisions and the associated selected sets have been created at the plant level.
- Status profiles for inspection lots have been defined.
- Order types for appraisal costs have been defined.
- Quality notification types have been defined.
- Task list usages have been defined.
- Control keys for inspection operations have been defined.
- Sample types for sample management have been defined.
Standard settings
- Inspection type 9*, A*, ... , Z*

Activities
1. Define the eight-character keys and the short texts for each inspection type that you want to use.
Note that you are only allowed to use each inspection type for one inspection lot origin.
2. Determine which control fields are relevant for each inspection type.
Define the contents of the controlling fields for each inspection type. If necessary, you must make
sure the conditions mentioned above have been met.
Further notes
The default values in the material specification take effect, if inspections are planned exclusively with
a material specification and there is no inspection plan. For these inspection lots, the system creates an
inspection operation using these specifications (operation number, control key and text for the operation).
Note: If there is an inspection plan, the system assigns the inspection characteristics from the material
specification to the last operation in the plan, providing that these characteristics are not already
contained in this plan.
If the inspection characteristics contained in the material specification are identical to those in the plan,
and if the default values for these inspection characteristics in the material specification differ from
those in this plan, the system uses the specifications from the material specification and ignores the
default values in the inspection plan.
If inspection characteristics are linked to class characteristics, the system takes the specifications from
these class characteristics and ignores the specifications in the inspection characteristics.
23.4.1.2 Maintain Inspection Lot Origins and Assign Inspection Types
In the "Origin" step, you define the inspection lot origin-dependent controls.
The inspection lot origins are predefined in the system.
You cannot define your own inspection lot origins. However, for each available inspection lot origin, you
must define the following parameters:
- Number range
- Available dynamic modification criteria
- Task list type
- Inspection plan status
In addition, you must define which inspection type variants should exist for each origin. An example of
an inspection type variant is a model inspection with a separate inspection type and associated task list
usage.
Requirements
- The inspection plan status is defined.

- The possible combinations of dynamic modification criteria are defined. These have already been
predefined in the standard system; the corresponding view V_TQ39 cannot be accessed using
Customizing.
Standard settings
The inspection lot origins are predefined by SAP.
SAP Recommendation
Retain the settings contained in the standard system.
Activities
1. For each inspection lot origin used in your company, define:

a) Which inspection lot number range is to be used.
If you want to define new number ranges, refer to the corresponding step Maintain Number
Ranges.
b) Which dynamic modification criteria can be used.

Define the maximum number of dynamic modification criteria that can be combined for each
inspection lot origin.
Note:
If you use dynamic modification without a task list, the quality level for the dynamic
modification criteria is managed in the inspection lot origin.
If you inspect with a task list, the intersection of the dynamic modification criteria in the task
list and in the inspection lot origin is used for the quality level. You can define default values
for the dynamic modification criteria in the task list using the control parameter task list
usage.
c) Which status the inspection plan must have.

The status "Released" (proposed in the standard system) is generally used.
2. Maintain the properties for the inspection lot origins in the control table. Look for appropriate
number ranges, dynamic modification keys and a task list status.
3. Maintain the inspection type variants for each inspection lot origin.
Make sure that a variant '01' (zero one) is available for each inspection lot origin!
23.4.1.3 Maintain Number Ranges
In this step, you determine the number ranges for the inspection lots. These number ranges are stored in
the inspection lot origin; they apply to the entire client.
WHATSAPP +255738656506
The system only allocates the inspection lot numbers internally, based on the defined number range.
Therefore, it is not advisable to define an external number range.
Standard settings
An individual number range is defined for each inspection lot origin.
SAP Recommendation
Copy the standard settings.
Activities
1. Estimate how many inspection lot numbers are required for each inspection lot origin in your
company.
2. Maintain the number ranges for the inspection lots.
Further notes

23.4.1.4 Define Default Values for Inspection Type
In this step, you define default values for a material's inspection setup.
You can define different inspection lot processing sequences for individual materials or material groups
by changing the default values for the inspection types in the material master.
Refer to the online documentation to familiarize yourself with the significance of the default values.
Requirements
Before you can maintain the default values, you must assign the inspection type to an inspection lot
origin. This is because the fields for which you can store default values for an inspection type are
dependent on the inspection lot origin.
Recommendation
For inspection processing purposes, the system allows you to store your own combination of control
parameters for each material. Such a wide range of different processes, however, is generally not
required or desired. You should therefore combine the materials into groups and define a standard
profile for the controls for each material group in the material master. If these parameters are the same
for all material groups for each inspection type, you can include them in the default values for the
inspection type.
Activities
1. Determine which control parameters are relevant for the individual inspection types and which of
these parameters can be predefined uniformly for each inspection type.
2. Define the default values for each inspection type.
Store only those default values that you will always use when you maintain the material master.
3. Maintain the table of default values.

4. Although some controls cannot be predefined uniformly in the system by means of default values
for an inspection type for all materials, they could still be defined uniformly for comprehensive
material groups. For such material groups, define the profiles using organizational measures and
make sure the inspection planners use these profiles.
23.4.1.5 Inspection for Goods Movements
In this step, you control the creation of inspections for goods movements or other inventory postings.
For the system to be able to create an inspection lot for a goods movement, the appropriate inspection lot
origin must be entered in the update view for the movement type.
You can deactivate the creation of inspection lots in an additional view.
Requirements
The inventory management system is in use.

The inventory management system can control materials that have the stock type "In quality inspection"
without the QM component, as long as there is no stock-controlling inspection type active in the
inspection setup. If a stock-controlling inspection type is active, you can only make postings in the QM
component from the inspection stock, when you make usage decisions for inspection lots. If you change
the person responsible for making the usage decision, make sure they are aware of the following; The
stock for a material "In inspection stock" should be zero before a stock-controlling inspection type can be
activated for the first time, and must be zero before a stock-controlling inspection type can be deactivated
for the last time.
Standard settings
Appropriate inspection lot origins have been entered for all movement types in the standard system that
contain materials to be inspected. The use of other inspection lot origins is not supported.
For certain movement types that do not usually require inspections (such as reversal movement types)
inspection lot creation is deactivated.
Activities
- If an inventory posting does not cause an inspection lot to be created, even though an appropriate
inspection type is active in the inspection setup for the material, you should check the setting for
the corresponding movement type, to make sure the correct inspection lot origin has been entered,
and inspection lot creation has not been deactivated.
- If you do not want an inspection lot to be created at an inventory posting, but the standard settings
specify this, you can deactivate the unwanted inspection lot creation for the relevant, specified
posting key relating to the movement type.
Activating the Quality Inspection with Copy of Current Inspection Lots
If a material is already being inspected when the quality inspection is activated in the QM component,
you must create an inspection lot in the SAP system to document the inspection process accurately. This
is especially necessary, if the material is to be kept in inspection stock for the duration of the quality
WHATSAPP +255738656506
inspection, since this stock type can only be managed on the basis of an inspection lot. There are two
possible scenarios:
1. Inspection stock does not yet exist in the SAP system for this material, (for example, as a
result of a data transfer from an old system or external system).
a) Maintain and activate the inspection setup in the material master for inspection type 05
(inspection for miscellaneous goods receipt). Depending on your requirements, you can
control whether or not a material for this inspection type is posted to inspection stock.
b) Enter the inspection lot origin 05 for movement type 563 (if necessary, only temporarily).
c) Post a goods receipt using this movement type for the quantity of goods being inspected. The
system creates an inspection lot and posts the lot quantity to the required stock type.
d) When the usage decision is made, you can now make the required inventory postings (even
from inspection stock).
2. An inspection stock already exists in the SAP system for the material for example,
because the QM component was installed after the inventory management system in the
MM component). In this case, you have the following options:
a) Removing inspection stock before an inspection type is activated
First make sure that the quantity of goods in inspection stock is reduced to zero; that is,
complete the current inspection and post the inspected quantity to unrestricted-use (or
blocked) stock.
b) Activate the required inspection types in the inspection setup for the material. You can now
create and process inspection lots for the quantities of materials to be inspected.
c) Managing inspection stock with the help of inspection lots
Take the following steps:
- Define an additional inspection type for the inspection lot origin 08 stock
transfer (inspection type 0800 in the standard system). - Define
default values for this inspection type.
- Enter this inspection type in the settings at plant level
Once you have fulfilled these prerequisites, activate the inspection types in the material master
records, using transaction QA08 for mass maintenance of inspection setup data. The system
then creates inspection lots for each material, batch and storage location that have stock in
quality inspection. These inspection lots have the preset inspection type that managed this
stock. To create these lots, the system does not retrieve the inspection setup that is entered in
the material master, but takes the default values that are defined for this inspection type in
Customizing.
Use these inspection lots to make inventory postings for the existing inspection stock.
23.4.1.6 Inspection for Deadline Monitoring of Batches
In this step, you plan the creation of inspection lots by monitoring the deadlines of materials whose
stocks are managed in batches.
The monitoring of deadlines involves two activities:
- changing the batch status when the following deadlines are reached:
- shell life expiration date
- date of the next recurring inspection
- creating an inspection lot before the date of the next recurring inspection expires and posting
the materials to inspection stock
To create inspection lots automatically, the system starts a job that triggers the monitoring of deadlines at
certain intervals:
- on a one-time basis
- at predefined intervals
Requirements
You must maintain the stocks of the monitored materials in batches.

An inspection type for inspection lot origin 09 must be active in the material master.
Activities
1. Plan the jobs to create the inspection lots.
a) Define report variants for triggering the inspections with the help of the deadline monitoring
function.
b) For each plant and material, define the intervals in which the deadlines are to be monitored.
Further notes
If the interval for the recurring inspection is defined in the material master, the date of the next recurring
inspection is recorded when a batch is created.
You can enter the expiration date manually when you create a batch or the system can determine the
date on the basis of the shelf life specified in the material master. If the inspection type for inspection lot
origin 09 (recurring inspection) is active in the material master, then a periodically executed program
can identify all batches that qualify for the creation of an inspection lot, a status change or a transfer
posting.
Jobs do not have a transport link; you must therefore plan the jobs in the production system.
23.4.1.7 Inspection for Manufacturing Order
In this step, you define the inspections during production.

You or the system can create inspection lots for the following methods of production:
- Production orders
Inspection lot origin 03 <- task list type N (routing)
Inspection lot origin 03 <- task list type M (rate routing)
- Process orders
Inspection lot origin 03 <- task list type 2 (master recipe)
- Repetitive manufacturing
WHATSAPP +255738656506
Inspection lot origin 13 <- the task list type can be set using the production version of the
material.
Requirements
- When you maintain the corresponding task list type, you must provide for inspection characteristics
and use corresponding control keys for the operations.
- In task lists, you can define define results recording based on inspection points. For more
information on the necessary settings, see the sections on Quality Planning, Inspection Planning,
and Inspection Points.
Standard settings
If you enter a task list type or task list status, when maintaining inspection lot origins 03 and 13, this has
no effect, since the system does not take these entries into account when selecting task lists for
production orders, process orders, and production versions.
Activities
1. For inspection lots in production, the system selects the preferred inspection type or inspection type
with variant 01 for the corresponding inspection lot origin, unless you specify another inspection
type in the settings for the order type.
Determine whether you need different inspection types in production that are dependent on the
order type. If necessary, define variants for these inspection types and predefine them for the order
type at plant level. Note that the table is a part of the Production area.
2. You must make a usage decision for the inspection lots associated with production orders. Since the
production lots have no relevance to the actual use of the produced quantities, you only need to
define a job that makes automatic usage decisions at predefined intervals, after the orders have been
completed.
In this case, inspection results do not affect the usage decision. If you want to change this standard
system response, see note 158455.
23.4.1.8 Inspection for External Processing
In this step you can make settings to inspect goods receipts from an external process, or subcontract
(external process with material to be provided).
When a goods receipt is created from an external process, the system creates an inspection lot for the
production order, as long as an inspection type is entered in the external operation for inspection lot
origin 01. If there are several externally processed operations in a task list or order, the inspection lots
can be identified by their inspection types. By specifying a task list usage in the inspection type, you can
cause the system to select different inspection plans for different external processes.
Requirements
- Control keys for production operations allow for an external process.

- There is an inspection type assigned to the inspection lot origin 01 for the affected operations.
- This inspection type is active in the material master for the finished product.
Activities
1. Identify the types of external processes for which goods receipt inspections are required.
2. Define suitable inspection types and task list usages
3. Maintain these inspection types in the material master records for finished products and in
their corresponding task list operations.
4. If required, create inspection plans with suitable task list usages.
23.4.1.9 Inspection at Shipping
In this step, you define the delivery types in the Sales and Distribution (SD) component, for which
inspections are to be triggered in the QM component. To do this:
- You assign one of the following inspection lot origins to the delivery type predefined in the SD
component:
- 10 for delivery to customer with sales order
- 11 for delivery to customer without sales order
- 12 for other deliveries (without customer reference)
- Assign an inspection type to the combination inspection lot origin/ delivery category (called usage
indicator in the SD component).
Requirements
- The delivery types and usage indicators are maintained in the SD component.
- The inspection lot origins and inspection types are maintained in the QM component.
Standard settings
In most cases, the creation of inspection lots is not required for a delivery. There are, therefore, no
inspection lot origins entered in the standard system for the delivery types.
Recommendation
Only enter inspection lot origins, if you specifically want to create inspection lots for a delivery.
Otherwise, the system has to search for the inspection type that is assigned to the delivery type and
origin each time and to check whether the inspection type is also active in the inspection setup for the
material.
Activities
1. Determine which delivery types are defined in the SD module. Determine whether quality
inspections are to be triggered for these delivery types.
2. If inspections are to be triggered:
a) Assign suitable inspection lot origins to these delivery types
WHATSAPP +255738656506
Note: You can only enter the inspection lot origins 10,11 or 12. This also applies to
inspections for return deliveries; the inspection lot origin 06 cannot be used for these.
b) Assign suitable delivery types and inspection types to these inspection lot origins
Further notes
If no special inspection type is defined for a delivery type/delivery category combination, the system
uses the following algorithm to search for an alternative inspection type: The system searches the
inspection setup of the material for a preferred inspection type, or searches in the table "Assignment
Inspection Lot Origin - Inspection Type" for an inspection type that is assigned to the inspection lot
origin as variant 01. The system then creates an inspection lot or partial lot with this replacement
inspection type, provided that this inspection type is active in the inspection setup for the material.
If the delivery contains a customer number, the quality inspection can be influenced by the customer-
specific information record.
Using the QM-SD control, you can specify whether:
- The inspection must be completed before goods issue posting

- The inspection can be completed after goods issue posting
- The customer will carry out the inspection himself (that is, an inspection lot is not created)
23.4.1.10 Define Inspections in Plant Maintenance
In this step you make the settings for plant maintenance inspections, for example, for calibration
inspections of test equipment.
Apart from defining suitable inspection types for the inspection lot origin 14, the only thing you have to
ensure from a QM standpoint is that for identifying the equipment a suitable user field combination
exists for the inspection point type equipment. This is required, for example, if you want to carry out
calibration inspections on test equipment.
You can find all other settings for the maintenance of equipment in the Implementation Guide for Plant
Maintenance.
Standard settings
The standard system contains a corresponding inspection lot origin, inspection type, and inspection point
definition. You can find these in the tables for delivery class G.
The entry of a task list type and task list status has no effect on the inspection lot origin 14, since this
origin is not taken into account when a task list is selected for a maintenance order.
The standard system contains an automatic follow-up action for updating equipment data. The function
modules that are linked to this follow-up action:
- Transfer inspection results from the QM component to the measurement reading for the equipment
in the PM component
- Update the PRT status of the equipment
Activities
Check the Customizing for:
1. Inspection type
2. Default values for inspection type
These default values provide valid standard values for inspection types of inspection lot origin 14.
3. Inspection lot origin 14 and assignment of the inspection types for inspection lot origin 14. Note: A
number range must be maintained for the inspection lot origin 14.
4. User field combinations for inspection types of the Plant Maintenance objects equipment and
functional location.
5. Order types for maintenance orders.
6. Assigning the inspection types to the order types
7. Follow-up actions for the usage decision that are used to update the equipment data.
Further notes
Refer to the recommendation for using the IMG (hypertext link in the IMG structure instead of using the
display view in the SAPscript editor).
23.4.2 Inspection Lot Completion
In this section, you determine system functions which are related to the usage decision:
The inspection lot completion includes:
- Inspection Completion
You can complete the inspection temporarily or definitively (short-term completion or final
completion) even without having entered a usage decision. Entry of a usage decision, however,
causes the inspection lot to be completed. If long term characteristics are still open in this case,
completion only applies to the short-term inspection.
- Usage Decision
The usage decisions are defined in catalog 3.
- Quality Valuation
A quality score must be defined as well as the usage decision for the inspection lot.
- Updating the Quality Level

Provided that a dynamic modification rule is entered in the inspection setup for the material or in
the task list.
Since in dynamic modification based on characteristics the quality level is only run for
characteristics that have been completed at the the usage decision, the system does not write a
quality level for long-term characteristics.
- Updating the QM Information System

Provided that an update group for the QM information system was assigned to the inspection lot
origin and that this update group is active
- Transfer of Inspection Results to the Batch Specification

Provided that the inspection characteristics are linked to characteristics of the batch class or that the
transfer of the inspection decision to batch is arranged for corresponding characteristics of the
batch class.
- Follow-Up Actions
WHATSAPP +255738656506
You can specify a follow-up action for the usage decision that can consist of a chain of
automatically triggered function modules.
Note:
The system automatically performs certain actions that are related to the origin of the inspection lot
and you do not need to define these individually as follow-up actions.
- Stock that was posted from inspection lots in goods movements to inspection stock can be posted
out of inspection stock to unrestricted -use when the usage decision is made.
You can post out of inspection stock at any time, irrespective of whether the inspection is
completed, with the help of the usage decision transactions.
- The update of the vendor evaluation in inspection lots from goods receipts for purchase orders or
from related shopfloor complaints takes place when a new vendor evaluation is made.
Further notes
Once a usage decision has been made, it cannot be revoked, since the usage decision triggers subsequent
functions that often cannot be canceled. These include:
- Stock postings
- Posting of costs - Updates of:
- Quality level
- QM Information System
You can use the customer exit QEVA0008 to cancel the usage decision on your own responsibility.
For additional information, refer to the OSS system, note number 33924 and related notes.
23.4.2.1 Maintain Catalogs for Usage Decisions
In this step, you maintain catalog 3, which is provided for making usage decisions.
Requirements
Before you can maintain the selected sets for the usage decision, you must implement the following steps
in this section:
- Define Quality Score Procedure

- Define Follow-Up Actions
- Define Inventory Postings
Standard settings
For test purposes, you can copy the examples contained in the standard client 000, using the method
described in the section Basic Settings Setting Up Clients.
Recommendation
Treat the catalogs as master data and make the final entries in the productive system. Note: When
catalogs are transported, usage indicators are also copied. Long texts, however, are not.
Activities
1. Check whether catalog type 3 exists in the table. Copy and keep the standard settings.
2. In catalog 3, enter the code groups and codes for the UD.
3. Maintain the selected sets from catalog 3 at plant level.
Further notes
For more information, see section Catalogs.
23.4.2.2 Define Quality Score Procedure
In this step, you define the procedures for determining the quality score.
The quality score procedure is defined in the inspection setup for the material master at plant level. You
can define a default value for this procedure in the inspection type.
Requirements
- The following specification limits have been defined in the Settings at Client Level.
- Highest quality score
- Lowest quality score
- Lower limit for good quality
- If you want to use quality score procedures that access the weighted shares of defects for the
characteristics, you must maintain the characteristic weights.
- If you want to use quality score procedures that access the quality score of the characteristics,
you must maintain the defect classes.
- If you want to use quality score procedures, in which the system calculates the share of scrap,
you must:
- Check whether procedures for estimating the scap share have been defined in
Customizing
- Assign suitable procedures for estimating the scrap share to the characteristics in the task list
- Identify inspection characteristics as relevant for scrap in their control indicators
Standard settings
A number of commonly used procedures for determining the quality score are implemented in the
standard system:
- Quality score from the usage decision

- Quality score from the share of defects in the lot
- Quality score from the shares of defects for the characteristics
- From the maximum share of defects
- From the weighted average share of defects
- Quality score from the quality score of the characteristics
WHATSAPP +255738656506
- From the minimum (worst) quality score
- From the weighted average quality score
The table has the delivery class G. The following name range is reserved for the user
- Quality score procedure 9*, A*, ... , Z*
Recommendation
- Use the procedure in the standard system.

- Decide on certain procedures for each inspection type; if possible, do not differentiate according to
material groups or plants.
Activities
1. Determine which procedures for calculating the quality score should be used. You can make a
distinction on the basis of the:
- Plant
- Inspection type
2. Modify the table of quality score procedures according to your needs. If the procedures contained in
the standard system are not sufficient, you must create additional procedures using function
modules.
3. Define the quality score procedures in the Default Values for the Inspection Type or in the
inspection setup for the material.
Further notes
Example for representing the quality score procedure according to VDA-1 (VDA
= Association of German automobile manufacturers).
According to VDA-1 the best quality score = 100, the worst = 1. In this
industry sector, the vendors are divided into three classes:
a) Quality score >= 96

b) Quality score >= 90 and < 96
c) Quality score < 90
The formula for calculating the quality score is:
Quality score = 101 - (1 * A1 + 5 * A2 + 30 * A3 + 100 * A4) : A5 A list of the
characters and their meanings follows:
- A1 = Number of goods receipts without defects

- A2 = Number of goods receipts with minor defects - A3 = Number of goods receipts with
major defects
- A4 = Number of goods receipts with critical defects
- A5 = Total number of goods receipts
To reproduce the procedure in the system according to VDA-1, proceed as follows:
1. Define defect classes with the following quality scores:

a) Critical defect with quality score = 101-100 = 1
b) Major defect with quality score = 101-30 = 71
c) Minor defect with quality score = 101-5 = 96
2. Assign these defect classes to the codes defined in the defect catalog.
3. Define defect codes in the task list characteristics in case a characteristic is rejected.
4. Choose the procedure contained in the standard system that determines the quality score using the
minimal quality scores from all inspection characteristics.
In this way, an inspection lot with no defects receives a quality score of 100, an inspection lot with minor
defects receives a quality score of 96, an inspection lot with major defects receives a score of 71 and an
inspection lot with critical defects receives a score of 1. On this basis you can classify vendors according
to VDA-1 in the QM info system, if you have predefined the corresponding class limits in the info
system.
23.4.2.3 Plan Automatic Usage Decision
In this step, you plan the process for the automatic usage decision (UD) for inspection lots.
You can enable the automatic UD for each inspection type in the material master. The system then makes
the usage decision automatically if all characteristics that must be inspected have been accepted and if no
defects or quality notifications were recorded. (You do not have to inspect optional characteristics and
characteristics that are in a skip stage.)
Before making the usage decison, however, the system waits until a specified amount of time has elapsed
from the date the inspection lot was created. During this time period, you can still intervene in the
automatic process.
The system records the automatic UD in the usage decision long text.
The automatic UD must be specifically activated. You can find the corresponding function in the Quality
inspection menu under the "Work list" option. In addition to triggering the UD, this menu option also
contains several customizing functions:
- Definition of report variants for the

- Selection of inspection lots that are ready for an automatic UD
- Usage decisions that correspond to these selections
- Planning the times when the automatic UD is to be carried out:
- On a one-time basis
- Periodically
Inspection lots for production orders (inspection lot origin 03) are a special case. You must make
formal decisions for these inspection lots, once the orders have been completed (even though these usage
decisions have no bearing on the use of the lot quantity). These formal usage decisions only update the
status of the inspection lots, so that they can be identified as completed and ready for archiving. The
evaluation of inspection results does not play a part in this type of automatic usage decision.
There is a separate job control available for automatic usage decisions involving production lots;
however, no intervention periods are supported with this function.
Production orders must have a particular status for automatic usage decisions for their inspection lots to
take place. The following are possible:
- "Completely completed"
The orders are completed from a Financial Accounting standpoint, as well as from a Logistics
standpoint.
WHATSAPP +255738656506
- "Technically completed".
The orders are then completed in terms of the Logistic processes, but can still be processed by
Financial Accounting.
- "Confirmed"
No further confirmations are expected for these orders.
Requirements
You must have maintained the entries required for the automatic usage decision in the UD catalog and
the associated follow-up actions.
Standard settings
The intervention periods in the standard system are set to a value greater than 24 hours; the automatic
usage decision function is not active.
Recommendation
Use the capabilities of the report variants, for example, to propose different usage decision codes for
automatic OK decisions based on the inspection type.
Activities
1. Identify the plants, inspection types and materials for which the automatic usage decision will be
used. Specify this in the inspection setup for the material.
2. Define the intervention periods for individual plants so that you can intervene in the automatic a)
Skip
b) Usage decision
3. Define the intervals, in which the automatic usage decision is to be made in the individual plants
and arrange the intervention periods.
4. Enter the periods or intervals, after which the automatic usage decision is to be made.
5. If you create inspection lots for production orders, you must also specify a cycle according to which
the automatic UD is to be made for these lots, once the production orders have been completed.
Define the periods or intervals for this purpose.
23.4.2.4 Define Follow-Up Actions
Use
In this step, you define follow-up actions for the usage decisions.
Several processing variations are possible for follow-up actions:
- A manual trigger of activities to be carried out manually.

- A manual trigger of activities to be processed by the system.
- An automatic trigger of activities to be carried out manually -> Workflow link.
- An automatic trigger of activities to be processed by the system -> (subject of this step).
- The automatically triggered, system-supported follow-up actions are particularly important. You
can define a series of follow-up actions the system will carry out in sequence.
For each follow-up action, you must define the level on which the follow-up action will take effect. The
system carries out automatic follow-up actions when a usage decision has been made for:
- An inspection lot
- A partial lot in production
- Operation completion in results recording
You can also specify the business transaction that is to be linked to this follow-up action and how the
update is to be processed.
Requirements
You should have maintained the catalog for the usage decision to such an extent that you only need to
enter the name of the follow-up action in the selected set codes, once you complete this step.
Standard settings
To make it easier for users to program their own follow-up actions, the system contains a non-
executable example of a function module for follow-up actions. You can copy the interface in this
example and use it to create your own function modules.
The standard system also contains several executable examples of function modules for follow-up
actions:
- Sending a mail to a distribution list with information about the usage decision and quality score.
- Sending a mail to a distribution list with information about the usage decision, quality score and
stock posting.
In the standard system, the distribution list only contains the name of the user who made the usage
decision.
- Updating the equipment data in a calibration inspection (inspection lot origin 14).
Recommendation
- Provide a detailed description of the follow-up actions for a usage decision in the long text for the
usage decision code (also include the follow-up actions that will be processed automatically).
- Do not change the function modules that are provided as examples. Make copies of these modules
instead and save them under different names.
Activities
1. Determine which follow-up actions for usage decisions are needed in your company. Be sure to
consider all inspection types, plants and usage decisions.
2. For the automatic follow-up actions, specify:
a) The series of function modules to be used and the update form for each of these function
modules.
b) The operations for the follow-up actions (if the activities carried out by the function module
are linked to the status management function for the inspection lot).
3. Maintain the table of follow-up actions. You must do this before you can maintain selected sets in
the usage decision catalog.
WHATSAPP +255738656506
4. Create the necessary function modules.
Maintaining the Usage Decision Catalog

The follow-up actions are defined for a code in a selected set of catalog 3 (usage decision). The catalog
does not differentiate between the levels (inspection lot, operation completion, or partial lot), at which
the follow-up action is defined. However, the usage decision transaction checks whether the follow-up
action is valid for the relevant usage decision level, when you choose a usage decision code or change a
follow-up action.
To prevent an invalid usage decision code from being chosen, we recommend that you define the level of
the usage decisions or their related follow-up actions when maintaining catalog 3 by either defining your
own code for each level, or creating a separate selected set for each level
If you do not want to trigger a follow-up action from the usage decision, leave the follow-up function
field in the selected set blank.
Follow-up action chains
Quality Management allows you to implement automatic follow-up actions in the form of function
modules. If a follow-up action consists of a series of individual activities, these partial activities must be
numbered in the sequence to be carried out and each activity must be linked to a separate function
module.
Links to operations
- If you want to assign an operation from the general status management function to a follow-up
action, the operation must be supported for the inspection lot's object type and it must be compatible
with the status profile assigned to the inspection type. Also refer to the step Define status profile.
The F4 help for the operation field shows you which operations are available for use.
Operations play an important role in managing the statuses of inspection lots. For more information
on this subject, refer to Status Management.
To help you select an appropriate operation for a follow-up action, you can display the definitions
of operations that support follow-up actions for usage decisions (you cannot, however, change these
definitions). To do this, proceed as follows:
- Display the list of operations. Call up the operations for inspection lots by entering QM*; then select
the desired operation.
- Select the function Where-used list (not Follow-up action). In this view you see:
- That the operation applies to the object type insp. lot, ...
- Which inspection lot statuses this operation sets and deletes - Which other statuses influence
this operation
23.4.2.5 Define Inventory Postings
In this step you can adapt the inventory postings that are linked to the usage
decision.
Standard settings
Several movement types are delivered with the standard system for transfer posting the stocks managed
in the inspection lot.
- Inspection lot origin 01, 04, 05, 08, 09
Recommendation
Keep the standard settings!
Activities
Check if you need to change the table entries and adapt the table if required. You may
need to make changes if:
- You do not want to allow certain movement types.

- You want to replace the movement types contained in the standard system with your own modified
movement types 9*.
- You want to supplement the quantity postings planned in the standard system with other quantity
postings.
In this case, SAP cannot guarantee that all of the possible variants for quantity postings will function
perfectly without program modification. If necessary, you may have to use the function enhancement
(customer exit) QEVA0001 to achieve your aims.
Use the keys VMENGE08 for additional quantity postings. Key VMENGE09 is reserved for SAP.
- These quantity postings appear on the screen when you make the usage decision. You can define
the descriptions of these postings individually in project management for the function enhancements
(transaction CMOD). Use the function "Global enhancements/Change keywords" to modify the data
elements, e.g. QVMENGE08. Unfortunately, these adjustments are not visible in the
Implementation Guide. They only have effect in the transaction for the usage decision.
Further notes
Printing of accompanying papers for goods movements

If the system does not print any goods issue slips, even though the printing function works from MM,
this is usually due to the following:
- The user parameter NDR = X is not set.

- In the settings for the MM component, the print for inventory postings is not taken into
consideration when you are in the usage decision.
If either of these occurs, proceed as follows:
1. In the user master record, set the parameter NDR = X.

This is necessary for automatic printing because the inventory posting is made in the background
and the print indicator cannot therefore be set manually.
2. Make the required Customizing settings in the MM component.

a) Set a print version for usage decision transactions QA11 and QA12 in the general settings for
print control (transaction OMBR).
b) Set a print indicator for the relevant movement types for goods receipts or goods issues and
transfer postings.
c) Maintain condition records for output determination for the relevant output types with
operation type WQ (transaction MN22).
WHATSAPP +255738656506
3. To print labels, you need the following additional steps:
a) Perform all the functions given in the settings for label printing (transaction OMCF).
b) Create a condition record for the label form and label type (transaction MN22).
c) Maintain the label form and label type in the storage view for the material.
23.4.2.6 Transfer Inspection Decision to Batch
In this step, you create the preconditions that cause the usage decisions for inspection lots to be
automatically transferred to the batch valuation.
When the usage decision is made, the system copies the following data from the inspection point into the
batch valuation:
- Usage decision
- Quality score
Requirements
The following class characteristics must exist in the current client and must be assigned to the batch class
of the corresponding material:
- LOBM_UDCODE (usage decision)

- LOBM_QSCORE (quality score)
Standard settings
These characteristics exist in client 000.
Activities
Determine whether you want to use the automatic transfer function for the usage decision to the batch
valuation and if this is the case, proceed as follows:
1. Copy the class characteristics for the usage decision and the quality score, using the functions
available in the current client.
2. Maintain a batch class in the Classification System and assign the characteristics mentioned above.
3. Assign this batch class to all relevant materials.
23.4.3 Status Management
This subsection describes how to use the general status management function for inspection lots.
For a detailed description of the general status management function, refer to the chapter Environment ->
Central Functions -> Status Management.
23.4.3.1 Define Status Profile
You can use the general status management function for inspection lots to:
- incorporate your own conditions in the inspection lot processing activities (this occurs with the help
of the inspection type)
- define your own business transactions as follow-up actions
- define your own selection profiles for the selection of inspection lots
- to automatically create workflows as a result of certain inspection lot statuses; for additional
information, refer to the section Environment -> Central functions -> Workflow
In this step, you can define your own status profiles for inspection lots. You can assign these status
profiles to the inspection types.
Recommendation
The inspection lots are already subjected to a series of system statuses. Try not to define any additional
user statuses, if possible.
Activities
1. Check whether additional user statuses are required for certain inspection types.
2. Define the corresponding status profiles.
3. Assign the status profiles to these inspection types.
Check whether the process variants (with/without inspection plan/characteristic results) defined in
the default values for the inspection type are suitable for the object types that are assigned to these
status profiles.
Further notes
For more information, refer to the chapter Environment, Central Functions, General Status
Administration, Status Profile.
23.4.3.2 Define Selection Profile
In this step, you can define your own selection profiles for inspection lots. You can then use these
profiles to find inspection lots by means of their status.
For a detailed guideline, please refer to the chapter Environment, Central Functions, General Status
Management, Selection Profile.
Recommendation
You do not have to define your own status profiles to make use of this function, since inspection lots
already pass a complete array of system statuses that can be used for selection.
Activities
1. Determine which system statuses and possibly which user statuses the inspection lots can pass. Note
that the status profiles for the user statuses can differ depending on the inspection type.
WHATSAPP +255738656506
2. Determine which logical links of these statuses result in relevant selection profiles, and define these
profiles.
23.4.4 Define Appraisal Cost Recording
In this step, you make settings that allow you to settle the appraisal costs.
You can skip this step if you only want to record appraisal costs for inspection lots that were created on
the basis of production orders, or maintenance orders. In this case, you confirm and settle the costs using
the production order or maintenance order.
Activities
1. First read the instructions contained in the section Environment -> Central Functions -> QM Order
Types.
Make sure the required order types are available and the settings for the costing parameters have
been made.
2. For each plant, define the confirmation parameters for the order types to be used for appraisal costs.
3. Check the settlement and evaluations of the appraisal costs by:
- Assigning an appraisal cost order to a material
- Processing an inspection lot for this material and confirming the
costs To be able to record appraisal costs, you must perform the following steps:
1. In Controlling, you must
a) define activity types for inspection activities
b) Assign these activity types to cost centers
c) Define an activity price for each activity type
d) Enter the cost center in the work centers
e) Define order types for QM orders
f) Define
g) settlement rules for the QM order types.
Note: The controllng data (activity type, cost center) are only valid for certain periods of time (such
as fiscal year).
2. In Customizing, you must define control keys for operations and activate the following functions in
them:
a) Costing
b) Confirmation
3. You must define these control keys in the inspection operations of the task lists.
4. You must predefine the activity types in the work centers and in the inspection operations of the
task lists
5. You must create QM orders in one of the following ways:
a) Collective generation and transfer to the inspection setup data for the material In this case, the
order type is either copied from the inspection type or from the settings at plant level.
These types of QM orders are automatically copied into the inspection lot
b) Individual generation for the inspection lot

In this case, the order type is either copied from the inspection type or from the settings at
plant level.
Once these prerequisites have been created, you can record inspection activities for the inspection lot
when you record results or make the usage decision.
23.4.5 Sample Management
In this section you make the settings for managing physical

samples.
You must also consider the following worksteps in other sections of the Implementation Guide,
depending on which functions you want to use in sample management:
- If you want the system to generate physical-sample records for inspection lots, you first must define
a physical-sample type for the corresponding inspection type
- If sample-drawing procedures are to take the lot container into account, you can define the entry of
a container for a goods receipt in the settings at plant level.
- You can predefine an appropriate sampling procedure procedure for managing samples in the
settings at plant level.
- If you want to record inspection results for physical samples, you must define a user field
combination for this inspection point type in Customizing for Inspection Planning. To do this, use
the function for identifying inspection points.
- If the physical-sample drawing is to be authenticated by a digital signature, you must first define a
corresponding material authorization group.
23.4.5.1 Define Physical-Sample Types
In this step you define the physical-sample types for sample management.
Standard settings
The table of sample types has the delivery class G. The following name range is reserved for the user:
- Sample types 9*, A*, ... , Z*.
Recommendation
- When you define new sample types, familiarize yourself with the table entries given in the standard
system.
- First test the label printing function using the function modules, forms, print reports and settings
contained in the standard system. Then, if necessary, make additional adjustments.
Activities
WHATSAPP +255738656506
1. Use the F1 help function to find information about the control functions that are linked to
the samples, and identify which sample types occur in your company.
a) Define the physical-sample types in the table.

b) Determine whether you need number ranges dependent on the sample type and maintain these
if required.
c) Determine whether you need status profiles and maintain these if required.
2. Plan the printing of the physical-sample labels.
a) Define the function module for each physical-sample type that prepares the print procedure for
the physical-sample labels and determine whether the labels are to be printed immediately,
when the physical-sample records are generated. Note: If you want to define your own
printing of labels, use the function module QPRS_LABEL_PRINT_REFERENCE as a copy
model!
b) Define the print control for the label printing.
Further notes
You must define a physical-sample type for the inspection type, if you want the system to create
physical-sample records for physical-sample drawing on the basis of the sample calculation.
23.4.5.2 Define Number Range
In this step you define the number ranges for sample management. These number ranges are defined for:
- Physical sample numbers

- Physical-sample-drawing numbers
Number ranges for samples are valid for certain fiscal years.
Recommendation
- Physical sample numbers

- For the sample numbers familiarize yourself with the standard settings.
Tip: Since the number area for physical-sample numbers is generously calculated, you can use the
first places as mnemonic coding for organizational purposes.
Note: You cannot delete number range 00, since this number range is required by the program, if
you create physical samples manually and enter purely numeric physical-sample numbers.
Alphanumeric physical-sample numbers are only checked for unambiguity.
- Physical-sample-drawing numbers
- Copy the standard settings for the physical-sample-drawing numbers.
Activities
1. Identify the sample types for which you need your own number ranges and define these number
ranges for the fiscal years that have been set.
2. Check whether you need number ranges that are different from the standard settings for the drawing
of physical samples and define these, if required.
Further notes
You must transport number ranges manually.
23.4.5.3 Maintain Screen Control Key for Sample Types
Use
In this work step, you can define a screen control key for each sample type.
The screen control key is a field in the field control for the sample master record. On the basis of the
value of the screen control key that has been defined for the sample type, you can control various screen
fields of the sample master record according to their properties (input, output, active, required, in the
foreground, in the background). One value range in the screen control key is reserved for SAP and one is
reserved for the customer.
The value range that can be maintained by the customer is : A* , B*, D* etc. , to Z*. In this value
range, you can use the screen control key to control modifiable standard fields (if planned), as well as
customer-specific fields in the customer field selection for the sample master record.
You can find detailed information about the uses of field control (SFAW, SFAC) in the Customizing
menu under: Adapt Field Selection.
The screen control key is also used as a filter for the Business Add-In QPRS_ADDON_TAB. For more
information about this, see the documentation for this BADI, or the corresponding IMG Documentation.
23.4.5.4 Define Physical-Sample Container
In this step, you define the physical-sample container for physical samples.
23.4.5.5 Define Physical-Sample Locations
In this step you define the physical-sample locations.
23.4.6 Define Print Control, Forms, Print Programs
In this step, you set up the print control for the shop papers (print lists) to meet the needs of your
company.
If you are not familiar with the technical capabilities of the print control, first read the concepts contained
in the section Further notes, before performing the steps in "Activities" section.
WHATSAPP +255738656506
Requirements
- You have set up the printer(s) and defined the printer destination(s).
- You specified whether the shop papers should be printed immediately when the inspection lots are
created, (dependent on the sample calculation). You make these predefined settings:
- In the settings for the inspection type, for sample-drawing instructions and inspection instructions.
- In the settings for the physical-sample type, for physical-sample labels.
- To set up the shop papers, you need the ABAP reporting and SAPscript functions.
Standard settings
The standard system allows you to print out the following lists with the help of forms:
- Sample-drawing instruction (instruction for physical-sample drawing)

- Physical-sample label - Inspection instruction
The predefined table settings, layout sets and print programs are provided for test purposes. In most
cases, you will probably have to modify these settings to meet your individual needs.
Recommendation
Before you change the tables, try to print the shop papers to the spool file using the standard settings!
Activities
1. List Definition Clarify the

following points:
- Determine which lists in each list class are used in your company.
- What these lists are to be called
2. Spool Parameters
Determine which print lists (shop papers) should be available for each plant and user.
For each of these lists, specify the printer (destination) for the lists.
Refer to the step "Printer determination" below for more information.
- Whether the spool order will be output immediately

A setting in the inspection type or physical-sample type determines whether the system will
create the spool order automatically within the transaction.
- Whether the list should remain in the spool file for a specified period of time
3. Order Types
Find out whether the print control is the same for certain order types.
If necessary, you can define reference order types and assign them to all order types that have the
same print control settings.
In normal circumstances, you retain the standard settings.
Note: If you select an order type in this view and proceed to the subsequent views that relate to the
assigned reference order type, the system only displays the entries that apply to the referenced order
type. If you want to display entries for several reference order types, in subsequent views, you must
first select all the relevant reference order types.
4. Forms
For each reference order type, plant, printer (destination) and list, specify:
- Which form should be used
- How many sections should be printed on a single page
- Whether a separate data record should be created for each list in the spool file
- Whether barcodes should also be printed
- Whether the print layout is to be displayed on the screen for subsequent printouts
5. Print Programs
For each reference order type, list and print variant, specify which program will supply the form
with data. The print program must be compatible with the SAPscript form that was assigned to the
reference order type.
6. Transactions
For each reference order type, plant, MRP controller and transaction, specify:
- Which lists in a list class should actually be printed

Note: The system displays all the lists on the detail screen. However, you can only activate
lists for each order type, that were assigned in the views for the order type mentioned above.
In the standard system:
- For the order type QM01 only list LG01 (sample-drawing instruction)
- For the order type QM02 only list LV01 (inspection instruction)
- For the order type QM03 only list LG02 (physical-sample label)
- Which general print variants are desired and how many printouts are needed
- Whether the print indicator in the operation control key should be taken into
consideration
(Note: This indicator is not considered for the print examples contained in the standard
system.)
- Whether the print lists should be created as single lists

Note: We recommend that you create the print lists as individual lists, otherwise shop papers may
be added to old spool requests and may be difficult to find. Note: Although the print examples
contained in the standard system do not take the MRP controller field into account, it must
contain the entry '*'.
Note: If the system cannot find either a specific transaction or a generic entry in this table, it does
not print the shop papers. This occurs, for example, if you create inspection lots by batch jobs and
have the system create print lists, since the system does not recognize a transaction. We therefore
recommend that you keep the generic entry contained in the standard system.
7. Printer determination
For each reference order type, plant, MRP controller and list, specify which output device
(destination) should be used.
- The printer in the work center.

In this case, the program RQEEAS20 prints the header for the inspection instruction and all
the consecutive inspection operations that are to be printed on this printer. This means that if
you use a different printer for each work center and define a different work center for each
operation, the inspection instructions are printed by operation. If, however, you define the
same work center for several consecutive operations, or if you use the same printer in the
work centers for these operations, the inspection instructions are grouped together.
- The printer in the user master.

- A printer that is dependent on the user, plant and list.
- A printer that is dependent on order type, plant, MRP controller and list.
WHATSAPP +255738656506
8. Form design and programming
a) Create samples of all lists used in your company.
b) Have qualified individuals create the required SAPscript forms and print programs.
c) Tip: do not use the standard programs to print customer-specific forms; if necessary, copy the
programs under another name.
9. Maintaining and testing the print control
a) First test the print lists in the standard system by printing them using the standard settings.
b) Maintain the print control according to the specifications you defined previously.
c) Test the print control and the printed lists.
Testing notes:
- You can use program PPCO85EI as a testing aid; it specifies the lists and parameters for a
predefined combination of user, order type, plant, MRP controller and transaction.
- For test purposes, in the settings for the inspection type or physical-sample type, you can
define that the system issue detailed error messages if a problem occurs while the system is
printing the shop papers
- In the settings for the inspection type, or physical-sample type, you can specify whether the
documents will be printed immediately when the inspection lots are created.
Troubleshooting tips:
- Check the system installation! Make sure you refer to the step -> Basic Settings -> Set up
clients.
- Are valid forms available? If you copied forms into the current client, you should consider one
of the following steps after you implement a new maintenance level, to make sure the forms
and print reports are still compatible: - delete the copied forms (as a precautionary measure)
- compare the contents of this client with client 000
- Have the order types QM01, QM02 and QM03 been maintained (transaction KOT2)?
- Have you set up the printers specified in the views for the 'Lists' and 'Output device
control'(transaction SPAD)?
- Have you set the indicators for immediate output in the "Lists" view and in the inspection type
or physical-sample type?
- Have you activated the required lists (and only these lists) in the "Transactions" view?
- Is this list to be printed as an individual list?
- Do the tables contain the generic entries you may require?
Further notes, Concept information

Since this same print control is also used for production orders, it contains functions and
settings that extend beyond the scope of the QM component.
A "print list" consists of a complete set of shop papers of a specific type (for example, an
inspection instruction for all operations contained in an inspection plan).
You can maintain the descriptions and texts for the print lists in several languages; the control
for the list printout, however, is not language-dependent.
The system contains several list classes that are assigned to the segments of an inspection
plan or an order; each list class contains the following lists:
- General lists at header level: LG01 to LG04
- Lists for an operation: LV01 to LV04
- Lists for material components: LK01 to LK04
- Lists for an inspection characteristic: LP01 to LP04
- Lists for test equipment: LF01 to LF04
You maintain the print control in several different views. For reasons of expediency, you should
maintain them in the following sequence:
o List
In the "List definition" view, you define the descriptions of all lists you need. The following
lists are defined in the standard system:
- Sample-drawing instruction (list LG01)
- Physical-sample label (list LG02)
- Inspection instruction (list LV01) o Spool parameters
In the "Spool parameters" view, you define the user-dependent spool parameters for the
list printout. The standard system contains a generic entry for <User> and <Plant>. On
the detail screens for these entries, the lists LG01, LG02 and LV01 are marked for
printing.
o Order type
You can individually control the list printout for various order types (document types).
The standard system supports separate order types for the quality inspection lists. This
enables you to print out the sample-drawing instructions and inspection instructions from
different transactions at different times. The separate order types are:
- QM01 for sample-drawing instructions
- QM02 for inspection instructions
- QM03 for physical-sample labels
These order types are defined for order category 50.
The shop floor control uses many more order types. Since not all order types require different
print controls, it is easier for you to maintain the print control. The system allows you to make
assignments to the same reference order type from several other order types and it only requires
you to maintain the print control for the reference order type.
Since this case does not apply to the QM component, you only need to assign the order types to
themselves as reference order types:
- QM01 -> QM01 - QM02 -> QM02

- QM03 -> QM03 o Form
The system uses SAPscript forms to print the lists. The forms are supplied with data from ABAP
reports. You can specify which list should be printed with which form. You can also select
different forms for different printers.
The following forms are contained in the standard system and set up for the corresponding
reference order types:
- * * LG01 * QM_SAMPLE_INSTR (sample-drawing instruction)

- * * LG02 * QM_SAMPLE_LABEL1 (physical-sample labels)
WHATSAPP +255738656506
(requires a printer that can print bar codes)
- * * LV01 * INSP_INSTRUCTION
You can use these forms as copy models to create you own custom-designed forms! The order
type, plant and printer destination are generically masked in this view. This means that you
can print the list independent of the order type. In the "Transactions" view, you determine
which paper is actually printed in which transaction. Notes:
- The system first searches for the specified form in the current client.
If the form in the current client:
- does not exist,
- does not exist in the desired language,
- is not active,
The system searches for a standard form with this name in client 000.
You can use transaction SE71 to confirm this.
Since the print programs are valid for all clients, it is advisable to maintain the forms in
client 000 only.
- Note: The standard system creates a new spool list with each print operation.
- The indicator display print layout is not evaluated in the standard system.
o Print program
To supply the lists with data, you can define several variants (with the associated report programs)
for each list. For example, you can print inspection instructions in a detailed or condensed form
by printing or omitting the explanatory texts for an inspection characteristic.
One variant and one report program exists for each list in the standard system:
- * 1 LG01 RQDSES20 (sample-drawing instruction)

- * 1 LG02 RQPRPP10 (physical-sample labels)
- * 1 LV01 RQEEAS20 (inspection instruction)
The order type is generically masked in this view. This means that you can print the shop
papers independent of the order type. In the "Transactions" view, you determine which
paper is actually printed in which transaction.
o Transaction
In this view, you specify which lists can be printed for which order types and the transactions in
which they can be printed.
There are numerous transactions you can consider, for example:
- QM01 -> MIGO (GR for purchase order) -> LG01 (sample-drawing instr.)
- QM02 -> QA02 (inspection lot change) -> LV01 (inspection instruction)
In the standard system, the reference order types are set and the fields <Plant>, <MRP controller>
and <Transaction> are generically masked. Important: Only one list is marked for printing for each order
type! o Printer determination
The system searches for the output device (printer destination) for a print list in the following
sequence:
- Work center
(Only if you set the indicator in this view and the print program evaluates the indicator
and if a printer is entered in the work center master record).
- Depending on the determination procedure defined in this view:

- In the "Printer determination" view for each MRP controller.
- In the "Spool parameters" view for each user.
- In the user master.
An entry exists in the standard system for each reference order type in which the fields <order
type> <plant> <MRP planner> and <list> are generically masked.
Technical note
You can use generic keys to maintain the individual views of the print control; for example,
plant *, MRP planner *, order type * transaction *, printer *, list * (exception: print variant in the
"Reports" view). The system searches for the most completely specified entry. The significance
of the key fields decreases from left to right (for example, the key field "user" has a higher rank
than the field "plant").
The MRP controller key is not evaluated by the print reports and forms contained in the
standard system. Keep the setting MRP controller *, unless you evaluate the field with your own
user-defined reports.
23.4.7 Results Recording
In this section, you define certain aspects for recording and processing characteristic-related inspection
results.
Requirements
In order to be able to record characteristic results, you must fulfill the inspection planning requirements.
For further details, refer to the section Quality Planning, subsections Basic Data and Inspection Planning.
Pay particular attention to the section Inspection Characteristic.
Activities
Determine which categories of inspection results occur in your company and define how they are
processed.
Usually, a distinction is made between two categories of inspection results:
a) Characteristic values and other inspection characteristic results

These refer to either planned characteristics, which are stored in the inspection plan, or
unplanned characteristics which only occur during the inspection. This section relates
exclusively to the settings for this category of inspection results.
b) Defect data
Defect data consists of data records that are used to record the defect type, defect location,
defect cause and defect valuation. These records can relate to inspection lots, inspection
operations, or inspection characteristics. The settings for recording defect data are described in
the chapter Quality Notifications Defects Recording.
23.4.7.1 Define Recording Configuration
In this step you define various background functions for recording characteristic inspection results.
You can set the system to process specific functions in the background, when you record results as soon
as certain prerequisites are met. You can find additional information about this function in the F1 field
help for the fields in this view.
Recommendation
WHATSAPP +255738656506
Carefully read the F1 field help for this view.
Activities
1. Using the F1 field help, determine which background functions are possible when recording
characteristic inspection results.
2. Determine which background functions are required in your company, and maintain the
corresponding entries in the view.
3. Define the required entry configuration, according to your requirements:
a) In the Settings at plant level and
b) As a parameter in the user master data
Tip: You can also create the user parameters using the results recording transaction.
Further notes
Do not confuse the Recording configuration dealt with in this step, with the Recording view. You use the
recording view to control the display of inspection characteristics on the overview screens. You can
choose between several predefined recording views and specify the recording view you require in the
inspection type or inspection operation. You can also set the recording view as a user parameter.
23.4.7.2 Define Origins of Results Data
In this step, you can define inspection result origins for inspection characteristics.
The user can specify a results origin during results recording, as long as the inspection characteristic has
the status "in process". The results origin entry is a source of information only.
In addition to the description of the results origin, you can also choose a data source for the inspection
results. If you specify the results origin during inspection planning for an inspection characteristic, the
inspection results for the affected characteristic characteristic are taken from this data source.
Example
Recorded results do not just come from an inspection. They can also come from:
- Technical data
- Quality certificates
- Batch specifications
Standard settings
- Data origin 9*, A*, ... , Z*
Activities
Determine whether results origins must be defined and recorded for inspection characteristics, and
maintain the table if required.
23.4.7.3 Supplement Attributes of Inspection Characteristic Results
In this step, you can change the attributes of the inspection characteristic results. You can:
- Change the descriptions of the existing attributes

- Add your own attributes
Example
For example, you can supplement the existing system attribute with the attribute "X = visible".
Standard settings
The table has the delivery class G.

The following namespace is reserved for the user:
Attributes U V W X Y Z ( ) [ ] { }
Recommendation
Use the attributes contained in the standard system.
23.4.7.4 Define Parameters for Calculated Characteristics
In this step, you define the formula parameters for the input values of calculated characteristics.
You can do this in two ways:
- the formula parameters directly reference the fields in the input characteristics
- the formula parameters reference function modules, which calculate the values in the fields of the
input characteristics
Example
To determine the difference between the mean values of two characteristics or samples, you need the
mean values of both characteristics or samples as input values. Since these mean values are available in
the characteristic record, you can reference the corresponding fields in the input characteristics directly.
To determine how many values for a quantitative characteristic are above a target value, you need a
special function module that calculates this using a counting function.
Standard settings
The system contains several predefined formula parameters that are often required. The table of field
names has the delivery class E. The following name range is reserved for the user:
- Field names Q*, ..., Z*
Recommendation
Keep the predefined formula parameters.
Activities
WHATSAPP +255738656506
1. If necessary, determine which formula parameters are needed for a calculated characteristic and
check whether these parameters have already been preset in the table.
2. If a formula parameter does not yet exist, you must first define it and then decide:
a) whether you can reference a field in the characteristics records, or
b) whether the value of an input characteristic must be calculated with the help of a function
module
3. The characteristic fields you can reference to calculate the values have been predefined
comprehensively in the system. Only in certain exceptions will you need to expand this selection of
fields.
Further notes
You can reference any desired fields in the tables of characteristic results in order to calculate
the values:
- QAMR Summarized results for a characteristic

- QASR Summarized results for a sample
- QASE Single values for a characteristic or sample
23.4.7.5 Define Parameters for Input Processing
Use
In this step, you define the key fields and the parameter values for input processing. A filter value of an
implementation of the Business Add-In QM_INPUT_PROCEDURE is assigned to every key input-
processing field.
Requirements
If you want to use one of the implementations delivered by SAP, select the relevant implementation
using the F4 help for the "BADI Filter Value" field.
If you want to use your own logic for the input processing of quantitative measured values, you must first
create an active customer implementation with a filter value in the Business Add-Ins structure in
Customizing, or using transaction SE19. You can find additional information under Business Add-In for
Input Processing.
Standard settings
If you have activated the input processing control indicator for a characteristic, you can access the
following implementations:
QM_INPPROC_100Output like Input (Decimal Places) and
QM_INPPROC_200Output According to Significant Characters
The first implementation uses the "input like output" process to clarify the principle behind input
processing.
The second implementation shows you how the output of significant characters can be changed using
input processing.
These implementations can be used as templates to help you to represent your own input processing
procedures for quantitative measured values.
Activities
1. If you are using the SAP implementation "Output According to Significant Characters", you define
the number of significant characters using parameter 1 on the detail screen.
2. If you have created a customer-specific, active implementation with a filter value, you define
a key for input processing in the customer namespace (A* ... Z*, 9*) and assign a suitable short text to it.
Then enter the relevant filter value in the Procedure column. If your customer-specific implementation
works using parameters, you maintain the values of these parameters on the detail screen.
23.4.7.6 Enter Identifier for Units To Be Inspected
In this step, you define the control indicators in the inspection plan header that affect the recording of
information for the units to be inspected. These indicators determine whether:
- The entry of identifiers (for example, serial numbers) for the units to be inspected is:
- Not required
- Optional
- Mandatory
- The identifiers must be unique
Irrespective of these indicators, you can also specify the inspection of single units using serial numbers
(in the inspection setup for material for each inspection type), if you define a serial number profile in the
plant data. In this case, the recording of serial numbers has priority over the control indicator settings in
the inspection plan.
Activities
1. Determine whether and how the identifiers for units to be inspected are recorded in your company.
2. You can delete unnecessary table entries and adapt the remaining keys and short texts as necessary.
Note: Do not delete the entry contained in the standard system <blank> with short text <blank>!
This entry is used to improve the ergonomics of the interface, if the function is not used.
23.4.7.7 Define Filter for Inspection Characteristics
In this step, you determine which inspection characteristics are displayed for certain transactions (for
example, for results recording and for the usage decision).
This depends on:
- The control indicators for the inspection characteristic

- Optional characteristic
- Required characteristic
WHATSAPP +255738656506
- The recording status of the inspection characteristic
- In the skip
- In process
- Valuated
- Closed
- Fixed
- Blocked
- Transferred to a subsystem for processing
- The valuation of the inspection characteristic
Characteristics for partial samples can also be selected.
Standard settings
The standard system contains very comprehensive characteristic filters.

The processing modes table has the delivery class G. The following name range is reserved for the user:
- Sample types 8*, 9*, X*, Z*.
Recommendation
Do not change the standard settings. Do not delete any entries!
Activities
1. Determine whether all of the transactions in the table (for example, for results recording QE0x - and
for the usage decision - QA1x -) are used in your company and whether the characteristic filters
required in your company differ from the standard setting.
2. If necessary, modify these characteristic filters.
23.4.7.8 Define Number Ranges for Characteristic Confirmation
In this step, you define the number range interval for the completion confirmation numbers of the
The completion confirmation numbers are assigned automatically by the system (internal number
assignment). You can modify the number interval and the current number level.
Standard settings
In the standard system, the eight-digit number interval is used to the fullest extent.
Recommendation
Do not change the default setting.
Activities
Determine whether the number range is in your company should be tighter. If necessary, correct the
default setting.
Further notes

23.4.7.9 Make Settings for Operation Completion
Use
You can use this IMG activity to define the combination of inspection type and plant for which the
operation completion is to be allowed.
Activities
1. Choose New Entries an enter the inspection type and the plant.
2. Set the indicator Operation Completion and save your entries.
23.4.8 Make Settings for Copy of Inspection Results
Use
You use this IMG activity to make settings for the copy inspection results function that are absolutely
necessary if you wish to use this function.
The settings are relevant to the inspection type and the plant of the inspection lot into which the results
are to be copied.
23.4.9 Dynamic Modification
In a sequence of inspection lots, dynamic modification controls the inspection scope with regard to
inspection characteristics and sample sizes, so that a predefined quality goal is achieved in the majority
of cases. To reach this goal, the system determines the inspection stages after each usage decision for the
subsequent lot of a material, by using dynamic modification rule defined in the task list. The system then
updates the quality level. This update can take place at various dynamic modification levels.
WHATSAPP +255738656506
23.4.9.1 Define Reference Dynamic Modification Level
In this step you specify the initial inspection stage for when you are creating a new quality level. The
system can either take the initial inspection stage from the dynamic modification rule, or can suggest an
inspection stage from one of the reference dynamic modification levels as the initial inspection stage.
If there is no inspection stage in the proposed reference dyanamic modification level, the system searches
the more general levels. If an inspection stage is not found in this way, the initial inspection stage is
taken from the dynamic modification rule.
Example
For an inspection with a task list, dynamic modification has been lot-based up to now. You now want to
use characteristic-based dynamic modification. You can use the inspection stage reached during lot-
based dynamic modification as the initial inspection stage for characteristic-based dynamic modification.
Requirements
You perform inspections using sampling procedures and a dynamic modification rule.
Standard settings
The dynamic modification levels are already logically linked.
Recommendation
Keep the standard settings for the reference dynamic modification levels.
Activities
Check whether you need to deviate from the standard settings, and if required make different settings.
Further notes on Manually Creating the Quality Level
At present, you can only create quality levels manually for lot-based dynamic modification using
transaction QDL1 during an inspection with an inspection plan. However, you cannot create quality
levels manually for characteristic-based dynamic modification or lot-based dynamic modification at the
level of the material or inspection type. In the latter cases, the system creates the quality level when the
first inspection lot is created. Such inspection lots are inspected at the start of production using the initial
inspection stage. By choosing a suitable initial inspection stage, you can avoid high inspection costs
immediately after the start of production.
You can also avoid an unnecessary change of inspection stages after the start of production by
transferring inspection stages from the old system. For more information, see note 136395 in OSS.
23.4.10 Information System
In this section, you define how the inspection lot data is summarized and updated in the Logistics
Information System (LIS).
Default settings
The standard SAP system already contains several predefined structures for standard reports.
Recommendation
Use these predefined structures. Modify the parameters to meet your requirements.
If you need new structures, you should consult an LIS expert.
Activities
1. Determine whether the update parameters predefined by SAP meet your requirements. If
necessary, modify the parameters of the update groups in the Implementation Guide for Logistics
Controlling.
2. Determine whether the standard analyses predefined by SAP meet your requirements. If
necessary, modify the parameters for the standard analyses in the Implementation Guide for
Logistics Controlling.
If the predefined information structures do not meet all your requirements for the reporting, you
must define your own additional information structures.
Procedure for user-defined analyses of inspection characteristics using statistical

key figures and process capability indices.
The following supplementary information helps you to create user-defined analyses for evaluating
inspection characteristic values with your own calculation methods. These calculation methods contain
the following key figures:
- Mean value x-bar

- Standard deviation s
- Process capability indices Cp and Cpk
When compressing values in the standard system, the LIS calculates the total of the field values. This is
not sufficient for calculating statistical key figures or process capability indices. If you want to use the
required algorithms to do this, you must alter the generated source code of your user-defined analysis. To
alter the code you require knowledge of the Data Dictionary as well as ABAP programming. Proceed as
follows:
1. To create the data basis for your own information structure, copy one of the existing information
structures in client 000 that contains all the relevant fields. Information structures S162, S164 or
S166 are suited for use as copy models. Generate your own information structure.
2. In the current client, define an update rule for your own information structure. The update rules
corresponding to information structures S162, S164 or S166 are suited for use as copy models.
Generate and activate your own information structure.
3. Add the code for calculating the key figures to the application program.
a) Use the include file RMCQCPKC, development class QG02 as copy model and save the form
routine list_method_sxxx under another name (replacing the 'sxxx' with the name of your own
information structure).
b) In this form routine, replace the type of the s000 transferred information structure with your
own information structure type.
c) Give the include file an identifier in the main program belonging to your user-defined
analysis. The main program is named RMCYxxx0 (whereby xxx is the number of your user-
defined information structure).
WHATSAPP +255738656506
d) In Customizing, link your user-defined analysis with your own form routine. To do this, use
the Implementation Guide section LIS -> Reporting -> Standard Analyses -> Change settings.
23.4.10.1 Define Update for Each Origin
In this step, you define the summarization and updating of the inspection lot data by specifying an update
group for each inspection lot origin.
Standard settings
Suitable update groups have already been defined in the standard system for all possible inspection lot
origins.
Actions
1. Determine whether the assignments of update groups to the inspection lot origins predefined by
SAP meet your requirements.
2. If necessary, modify the table according to your requirements.
The update group is used to update the statistics for different types of business transactions.
The update rules for the key figures of an information structure are always defined in reference to an
update group.
If an inspection lot origin is not assigned an update group, the data for these inspection lots is not
updated in the information system. The relevant update group must be active in the LIS, for the system
to update the data.
You can record a user-specific update log to monitor the update function.
23.4.10.2 Divide Quality Scores Into Classes
In this step:
- You define the classification of quality scores for inspection lots into a maximum of five classes.
- You assign these classifications to the information structures that have been defined in the LIS for
update purposes.
Standard settings
Both uniform and exponentially weighted classifications are predefined in the standard system. The
uniform classification is proposed as the default.
Activities
1. Coordinate the classifications for the quality scores on a company-wide basis and maintain the class
limits in the table.
2. Assign the required classification to each information structure.
Warning: You cannot change classifications that have already been used! First, you must delete the data
contents in the related information structures. You can then change the classification. Finally, you must
update the information structures to provide them with data entries, provided that the original documents
have not already been archived.
For more information about information structures, refer to the Implementation Guide for Controlling in
Logistics, sections Data Basis and Self-Defined Information Structures.
23.4.11 List Definition
In this section, you define list variants for processing inspection lots and inspection results.
For some of the lists you can define variants for field selection, as well as variants for data selection. For
the remaining lists you can only define variants for data selection.
23.4.11.1 Define Variants (List View Function)
In this step, you define the list variants for various objects that are related to quality inspections or
worklists.
To do this you use the list view function. The function and procedure are described in the section
Environment, Tools, List definition.
23.4.11.2 Define Variants (Without List View Function)
In this step, you define only the list variants for data selection. You cannot define variants for field
selection.
23.4.12 Activate Workflow Template
In this step, you activate the workflow template that is to run in inspection processing.
Further notes
For more information, see the section Environment / Central Functions / Activate Workflow.
23.4.13 Subsystems
You can link CAQ subsystems to the SAP system, in order to implement solutions for special tasks.
Depending on what type of general conditions need to be fulfilled, different procedures are available:
WHATSAPP +255738656506
- Processing a quality inspection over the QM-IDI interface
This technique is used in the QM module to process inspection operations on CAQ subsystems.
The interface exchanges data in both directions. The transmission of data is triggered by the
subsystem; the transmission process is carried out automatically on the basis of an SAP defined and
publicized protocol and the process is monitored by the system. SAP supplies the programs that are
needed for the transmission process for a variety of platforms.
The time and effort required to implement this solution is comparatively high.
- Retrieving characteristic results via a PC interface

With this technique, the system can transmit complete data records (that is, records consisting of
several fields); it is used to transfer the results records for individual characteristics (for example,
measured values and inspection descriptions) from a subsystem to the QM module.
The transmission process is triggered and monitored by the user.
The QM module has a predefined connection for the required user exit.
The time and effort required to implement this solution is comparatively low.
- Data transfer using an electric coupler

You can use this technique to fill the individual input fields on a display monitor with values. This
technique replaces the manual entry of character strings using a keyboard.
The transmission process is controlled and monitored by the user.
The SAP terminal's serial interface for the keyboard is connected to the subsystem's serial interface
using an electrical coupling device (that is, switched in parallel to the electronic measurement
equipment).In most cases, an RS232C interface is used for this purpose. If necessary, you can adapt
any noncompatible signals in the measurement equipment to this interface standard. No special
system software is required for this solution.
23.4.13.1 Process Quality Inspections Using QM-IDI Interface
You can delegate the processing of inspection operations to subsystems.
For a technical description of the interface specification, refer to the SAP online documentation.
Sequence:
- The subsystem initiates the action by requesting a work list of inspection lots from the SAP system
that are waiting to be processed in a work center.
- The SAP system then transmits the current work list.
- From this work list, the subsystem can select inspection lots for processing.
- The SAP system then transmits the inspection specifications to the subsystem and waits until results
are confirmed by the subsystem. During this time, the operation cannot be processed in the SAP
system.
- The subsystem can confirm:
- characteristic results for an operation; prerequisite: the recording of characteristic results must
active for the material.
- characteristic results for an inspection point; prerequisite: the inspection plan header must specify
inspection processing on the basis of inspection points.
If a characteristic is rejected, the SAP system can automatically update the defect data;
prerequisite: defects recording must be supported by the inspection characteristic in the plan
and you must have activated the automatic selection of a report category for the corresponding
work center.
- usage decisions for inspection lots The SAP system logs the transmission sequences.
Recommendation
Have the vendor of the subsystem show proof that his system has been certified by SAP.
Activities
1. Make sure the organizational and technical prerequisites have been fulfilled. Plan the
interaction of the CAQ system and the SAP system.
a) Define how the responsibilities will be delegated.
The master data must be maintained in the SAP system and the SAP system must generate the
inspection lots.
b) Make sure the appropriate interface programs for the subsystem are available. Remote
Function Call (RFC) is used for the interface to the subsystem. This means that programs
installed on the subsystem must conform with the interface definition. Vendors of CAQ
subsystems can obtain a certificate from SAP stating that there is a successful connection to
the QM-IDI interface.
2. Make the system settings.
a) Define the subsystem keys and mail addresses for the transmission protocols. Note: The
standard system contains an entry ' *' that is used to call up the interface without a
subsystem. You cannot delete this entry, but can only change the contents.
b) Store these keys in the master records for the work centers.
Since the processing is controlled via the work center, the materials must be processed on the
basis of an inspection plan. In addition, you must have specified the defined subsystems
(before the inspection lots are created) in work center the master records where the the
operations will be processed.
c) Determine whether defect records need to be generated automatically. If so, you must activate
the function for the automatic selection of a report type for the affected work centers. For
additional information, refer to the chapter the Quality Notifications, Defects recording,
Report Type.
d) An application log is written for the interface. You can display the logs using the report
program RQEIFML10 and delete them using the report program RQEIFML20. Make sure
that you delete the logs on a regular basis.
Further notes
RFC function modules for downloading operations
- Selecting the operations to be processed and transmitting the associated work list.
QIRF_SEND_INSP_REQUIRMENTS
- Transmitting the characteristic specifications and catalog entries for the work list.
QIRF_SEND_INSP_DATA_FOR_WL
- Selecting the operations to be processed; transmitting the operations, characteristic specifications

and catalog data.
QIRF_SEND_REQUIRMENTS_GET_DATA
- Updating the lock entries.
WHATSAPP +255738656506
QIRF_SEND_COMMIT_TO_QM
- Transmitting the catalog entries.

QIRF_SEND_CATALOG_DATA
RFC function modules for uploading operations
- Confirming single results.

QIRF_GET_ORIGINAL_VALUES
- Confirming sample results.

QIRF_GET_SAMPLE_VALUES
- Confirming characteristic results.

QIRF_GET_FEATURE_VALUES
- Confirming inspection points. QIRF_GET_INSP_POINT

- Confirming all result types.
QIRF_GET_ALL_DATA_VALUES
- Confirming usage decisions for inspection lots. QIRF_GET_USAGE_DECISION
23.4.13.2 Retrieve Characteristic Results Via PC Interface
In this step you can set the system to copy characteristic results from subsystems using a PC interface.
You can use the transactions for recording characteristic results to copy data directly from test equipment
or PC applications. To do this you must use a function enhancement. The system contains a
corresponding model coding for the QEEM0021 user exit.
This model coding allows the data transfer to be planned at characteristic level and to be triggered using
an additional pushbutton in the results recording function. The coding provides the structure for calling
up the test equipment driver.
Test equipment drivers are function modules with an interface predefined by SAP. They are responsible
for copying the data from the subsystem. These drivers can be installed as ABAP programs in the SAP
system, or as RFC server programs in the subsystem.
The following test equipment drivers are provided:
- Model driver for copying quantitative single results from MS-Excel using OLE technology.
- Model driver for copying qualitative single results (attribute codes) with an inspection description
from a PC file.
- Driver body for copying results from an external system (with the option of generating a framework
program in C or Visual Basic to implement the transfer).
Requirements
For the current release the PC interface is not completely integrated in the standard system. The system
therefore plans the use of the test equipment drivers with the help of the information fields contained in
the task list characteristics. If you need to use these fields for other purposes you must store the
information for the drivers elsewhere and alter the model coding accordingly.
Activities
1. Check whether the ABAP model driver is suitable for your application. If required create copies and
adjust these to meet your needs.
(Transaction SE37)
2. If you want to link external driver programs, make sure that:

a) These programs are available in the relevant locations
b) The data required for calling up these programs is stored in RFC destinations.
(Transaction SM59)
3. Activate the function enhancement QEEM0021 with the model coding or the coding you
have adjusted.
(Transaction CMOD)
Overview of test equipment drivers
QINT_GET_PCFILE_DATA
This driver provides the model for a group of drivers that copy inspection results from measurement logs.
If you want to use a driver for a specific measurement log, copy the driver and customize the copy for
your required data format.
The driver copies catalog entries (code groups and codes) and inspection descriptions (short text) from a
PC file. For each record this file contains a line with three fields, separated by commas. The first field
contains the code, the second the code group, and the third contains the inspection description.
The driver loads a number of records that correspond to the sample size at once, and you can then select
the data containing the codes from a file selection dialog box.
If you want to use this driver, maintain the information fields for the characteristic as follows:
- Information field 1: Is not used -

Information field 2: Is not used
- Information field 3:
QINT_GET_PCFILE_DATA
QINT_GET_EXCEL_DATA
This driver is a model for copying inspection results from PC applications into the QM component, with
the help of OLE technology.
The driver uses OLE technology to call up a user-defined MS Excel function. You can select the Excel
file contained in this function from a file selection dialog box. The name of the Excel function is stored
in information field 1 for the characteristic.
Example of a user-defined Excel function:
The function is called GetValue and finds an entry from the table Table 1 using a measured value. This
table contains measured values in column B from line 5 onwards.
Public Function GetValue(Number As Integer) As String
Sheets("Tabelle1").Select
Range("B"&Number + 4).Select
GetValue = Active.Cell.FormulaR1C1
End Function
If you want to use this driver, maintain the information fields for the characteristic as follows:
- Information field 1: GetValue

- Information field 2: Is not used
- Information field 3: QINT_GET_EXCEL_DATA
WHATSAPP +255738656506
QINT_GET_RFC_DATA
This driver defines the interface for test equipment drivers in external systems. External drivers are
configured using RFC destinations that contain all the data necessary for calling up an external program.
You can start the external driver in the following ways:
1. Front end workstation

In this option you start the external program from the SAP system on the relevant PC for the
external workstation. When you close the SAP transaction, the SAP system also closes the external
program.
2. Registration
In this option the external program is started independently of the SAP systems. After it has been
started, the external program logs on to the SAP gateway and is ready to be contacted by the SAP
system. The functions of drivers started in this way are not just limited to one specific front-end PC,
but can be called up from several different workstations (sharing of test equipment).
If you want to use an external driver, maintain the information fields for the characteristic as follows:
- Information field 1: Is not used

- Information field 2: RFC destination for the driver or NONE
- Information field 3: QINT_GET_RFC_DATA
Example
The external driver for a set of scales is called 'SC.EXE' and is installed in directory'C:\'. Maintain the
RFC destination as follows:
1. Start transaction 'SM59'

2. Switch to the 'TCP/IP connections'
3. Create the RFC destination 'SCALE01'
Connection type 'T'
Activation type 'Start'
Start on 'Front end workstation'
Program 'C:\SC.EXE'
Description 'Scale 01'
4. Save the settings

You can check the settings by testing the connection.
If you want to use this driver for a task list characteristic, enter the RFC destination 'SCALE01' in
information field 2. Enter the driver QINT_GET_RFC_DATA in information field 3.
If you want to create your own external programs, you can generate a suitable RFC server program using
the C or Visual Basic programming languages. You can then use this program as a copy model for your
driver.
Further notes
You can find additional information about drivers in the function group documentation QINT.
You can find a description of the RFC function in the SAP documentation Basis -> Development
Workbench -> Remote Communication.
23.4.13.3 Transfer Data Via an Electronic Coupler
In this step, you plan the recording of characteristic values using electronic keyboard couplers.
This method of recording data is recommended if:
- the data is available in the form of electrical signals (for example, measured values supplied by an
electronic scale)
- an operator is available who will start and monitor the transmission of data
Activities
1. Determine the situations in which it would be practical to record data using an electronic coupler
(for example, for the continuous recording of quantitative characteristic values).
2. Make sure the necessary hardware is available (for example, electronic couplers, signal converters,
bar code readers)
Further notes
The required hardware can be obtained from numerous suppliers of electronic equipment on the market.
If you use a solution that conforms to the latest technical standards, you be able to program the
transmission formats and additional control characters.
23.4.13.4 Define Evaluation Method for QM-STI Interface
In this step you define the statistical evaluations that you want to carry out in an external system
with the help of the QM STI (QM statistical interface). QM STI evaluations are defined using
evaluation methods and evaluation steps.
in the QM transactions you can only use the evaluation methods that you define and release in this work
step.
Requirements
- You must use quantitative characteristics with single-value recording - You want to evaluate
the inspection results in an external system.
- You have a statistical system that uses an interface compatible with the QM STI.
Standard settings
The following evaluation methods are provided in the standard system:
- SAP_DOWNLOAD stores the content of the interface tables on the front-end server as data.
- SAP_EXCEL loads the content of the interface tables transferred by SAP_DOWNLOAD into a
Microsoft Excel work folder and displays the run-chart of all single values.
- SAP_WEIBULL_REGRESSION determines the Weibull distribution for predefined fractions of
nonconforming units.
- Evaluation method X*, Y*, Z*

- Evaluation steps 1*, ..., 8*
Recommendation
WHATSAPP +255738656506
When creating evaluation steps, consult the documentation for the associated statistical system. This
should give you the names and parameters of the evaluation steps you can use.
Activities
Proceed in the following order:
1. Maintain the RFC destinations

2. Define the evaluation methods
3. Define the evaluation steps
Technical information About RFC destinations
From the SAP standpoint, the associated statistical systems represent server programs that can be called
up by the QM STI using Remote Function Call (RFC). You use RFC destinations to communicate with
RFC server programs. These destinations are maintained with transaction SM59, and they specify which
program on which computer can be used, and how the program can be accessed in the network.
Recommendation for allocating names to RFC destinations

In a SAP system there can be several different RFC destinations. For QM STI evaluations however,
you can only use those destinations that are connected to a compatible statistical system. To ensure
that the user only accesses these compatible RFC destinations, you can define a generic key for the
allowed RFC destinations in the evaluation method. You should take the generic key name into
consideration, when allocating names for the RFC destinations.
For example, if you name your RFC destinations for the QM STI QM_STI_01, QM_STI_02 and
QM_STI_03, and define the generic key in the evaluation method as QM_STI_, the system only
offers the user the RFC destinations that start with QM_STI_.
RFC destinations of type 'T' for TCP/IP connections are used for the QM STI. With this connection type
you have the following options for starting external programs:
- Starting on the local PC

The statistical system is started on the respective PC when you call up the QM STI evaluation. In
this option you maintain the file name and the directory path of the statistical system on the local
PC. You can find information on how to do this in the documentation for the statistical system.
Tip: If you want to use the same RFC destination on several different PCs you should install
the statistical system in the same directories on the local PCs.
- Starting on the application server

The statistical system is started on the application server when you call up the QM STI evaluation.
In this option you maintain the file name and the directory path of the statistical system on the
application server.
- Registration
The statistical system is started without involving the SAP system and logs on to the SAP gateway.
By using the type 'T' RFC destination, the same program on the same PC is always called. In this
option you maintain a program ID and define an SAP gateway. The statistical system always logs
on to the same program ID and the same SAP gateway.
Tip: Use this option if you want to make automatic valuations in the background.
23.5 Quality Certificates
The section 'Quality Certificates' is a part of the Implementation Guide for the QM (Quality
Management) component.
Quality certificates (or certificates as they are commonly called) apply to certain materials; they can be
created for different objects in the SAP system:
- In the QM (Quality Management) component for the inspection lot

- In the MM (Materials Management) component for a batch
- In the SD (Sales and Distribution) component for a delivery
The integration of the certificates in the SD component means that the settings in QM to a great extent,
overlap with the settings in the SD componnte. Since you have to coordinate some of the settings in the
QM module with those in the SD module, access certain tables in the SD component and have
appropriate skills in this area, it may be advisable to have an SD expert make these settings.
Important: The function for creating certificates is not active in the standard system! To activate the
function, you must:
- Maintain an output determination procedure

- Assign this output determination procedure to the relevant delivery item categories
You can design the certificate layouts with considerable flexibility and thereby fulfill a variety of
requirements; from simple quality certificates (without reference to quality characteristics) to certificates
of specification (with reference to general values of quality characteristics) and inspection certificates
(with references to values of quality characteristics, that are determined for a specific batch). You can
combine the elements of these basic certificate types in any combination and you can design the
certificate forms freely, allowing you to satisfy all requirements in terms of form and content.
You can tailor the layout and content of the certificates to the needs of the partner for whom the
corresponding delivery item is intended.
Finally, you can also flexibly define the printing and dispatch parameters for the certificates.
Recommendation
Before you make any changes to the default settings, test the function for creating certificates using the
settings and sample data contained in the standard system. Follow the instructions described below:
1. Make sure the following conditions have been fulfilled:

- Create a certificate profile; in the profile, assign the sample form QM_CERT_01 (contained in
the standard system) to the profile.
- Create a material and make sure all of the data that is required by the certificate is available
for the material (for example, the characteristic results).
- Set the print control parameters.
2. Release the certificate profile and assign it to the material.
3. Define the output dispatch:
Define an explicit certificate recipient ('goods receipt' function). Use the output type
'LQCA' and set the dispatch time to '3.'
4. Create a delivery for the material.

- Create a customer order in the SD component (type 'TA').
WHATSAPP +255738656506
- Create a delivery with an item for the material in question.
- Post the goods issue.
5. Check the delivery item to see if the system created an output.
6. Trigger the certificate dispatch for this delivery item and check whether a print job was created for
the required certificate.
Further notes
Troubleshooting strategy in the event the system does not create a certificate for the
delivery.
1. Did you find an output for the delivery item?
Transaction: change delivery (Logistics -> Sales/distribution -> Shipping -> Delivery -> Change).
Select the appropriate item on the fast entry screen and then select Item -> Output, to call up the
fast entry screen for the item outputs. Does an entry exist that corresponds to a quality certificate
in your system (for example, output type 'LQCA' or 'LQCB')?
a) If an entry does not exist: no output was found yet.

Select Goto -> Determination analysis to display a log for the output determination.
Double-click the mouse (F2) to display several levels of detailed information.
If a log is not available, check the following items in the Customizing application: - Is a
suitable output determination procedure available?
- Is the procedure assigned to the delivery item category?

Explanatory information is provided below.
The log indicates which data the system used to try to find an output.
b) If you find a line associated with the expected output that contains the message
'Condition ... not fulfilled,' a specified condition must be fulfilled (for example, 'picking for
delivery carried out' or 'goods issue has been posted') before the system can find the output
automatically. This requirement is predefined in the Customizing application. In this case, the
system responded properly by indicating that it had not yet found the output. If you still want
to create a certificate, you have to enter the desired output type manually (for example,
'LQCA' or 'LQCB'); the system then proposes various data automatically (which you can still
change, if necessary).
- If you find a line associated with the expected output that contains the message 'Output
not found,' the system could not find a recipient (condition record). The detail function
(F2 or double-click) shows which keys the system used to try to find a recipient. In a new
session (select System -> Create session), you can determine whether a recipient record
exists for this key. To verify this, select Logistics -> Quality management -> Quality
certificates -> Certificate recipient -> Display; enter the output type (for example,
'LQCA') and choose any key combination after you select 'Enter.' The system then
displays a selection screen that contains the function 'Condition info.' If you select this
function (and, if necessary, specify an output type again), the system displays another
selection screen. If you select the function 'Execute' (F8), the system displays a list of
certificate recipients that meet your selection criteria.
If you do not find the desired recipient in the list, create a corresponding data record by
selecting Certificate recipient -> Create.
If the recipient is contained in the list, check the following items in the Customizing
application:
- Is the condition table entered in the access sequence?
- Is the access sequence assigned to the output type?
- Is the output type contained in the profile?
- Is the profile assigned to the delivery item category? Explanatory information is provided
below.
c) If an entry does not exist: an output was found.
What status does the output have? (The 'Status' field is located to the left of the 'Language'
field.) The statuses have the following significance:
0 = Not processed
1 = Successfully processed
2 = Unsuccessfully processed
- If the output has the status 0, it has not been processed yet. Mark the output. Select the
function 'Additional details' to display detailed information about the processing activities.
The field 'Dispatch time' defines when the output should be processed. The certificate will be
printed or displayed after this time has passed.
- If the output has the status 1, it has been successfully processed by the output processing
system. Check whether problems exist with the output devices (System -> Services -> Print
requests; transaction SP01). It is possible that the printer or telefax server cannot be reached.
- If the output has the status 2, it was not processed properly. It is possible that the system did
not find all of the data. To obtain more information, mark the output and select the function
Goto -> Processing log. Using the 'Documentation' function, you can call up the long text for
the corresponding program message for each line. Check the individual messages. An
explanatory note is contained in item number 2. Special note: if the system could not find all
of the data for a characteristic that was defined as 'Required' in the certificate profile, the
output of all data for the affected batch or the output of the entire certificate (if the item only
has one batch or no batches) is suppressed.
2. The output was found; however, since not all data could be found it has the status 'unsuccessfully'
processed.
a) No certificate profile was found.
To be able to create a certificate, the system requires a valid assignment for the certificate
profile. Check whether a valid certificate profile assignment exists for the delivery item data
(material, customer, ...., output creation date). To do this, select Logistics -> Quality
management -> Quality certificates -> Certificate profile -> Display, and then use the search
function (F6). On the subsequent selection screen, you can narrow down the selection further.
The system will then display a list of profile assignments. By selecting the function 'Choose,'
you can call up the respective certificate profile.
If the system could not find a valid assignment, you must create a valid certificate profile
assignment. To do this, select Logistics -> Quality management -> Quality certificates ->
Certificate profile -> Assignment -> Change. After narrowing down your selection and
executing the program, the system displays a list of assignments that already exist for the key
date. You can now make a new assignment.
b) No inspection lot was found.

The quality inspection was specified as the data origin (for specifications or results) for at least
one characteristic in the certificate profile. As a result, the system tries to find an appropriate
inspection lot, taking the restrictions for selecting an inspection lot (defined in the certificate
profile) into consideration. In addition, the inspection lot must have a usage decision and it
WHATSAPP +255738656506
must not have been cancelled or marked for cancellation. If the system finds several
inspection lots, it selects the lot with the latest inspection and create date (not the date of lot
creation). Partial lots are then treated equally.
Check whether an applicable inspection lot or partial lot exists. Use the information in the
certificate profile for this purpose. You can display a list of the possible inspection lots by
selecting Logistics -> Quality management -> Quality inspection -> Inspection lot processing
-> Usage decision -> Display, and then selecting the function 'Find insp. lot.'
If the material is maintained in batches, a batch must be specified in the delivery item. (->
Picking). The system then searches for inspection lots and partial lots for the batch specified
in the delivery item.
c) Not all data was found for the individual characteristics.

Two situations can then prevent a certificate from being printed or displayed:
- The indicator 'Required' is set for a characteristic in the certificate profile. In this case, the
output of data for the batch or for the entire certificate is suppressed. Find out which data
is missing. For the characteristic, change the data origin in the certificate profile or make
sure that the data can be found.
- The data could not be found completely for any of the characteristics in the certificate
profile.
In this case, the output of data is also suppressed for the batch or the entire certificate. If you
want to create a certificate without characteristics, the certificate profile must only contain the
header and not any characteristics.
3. Customizing: Check the settings.

a) Output determination
- Is an output determination procedure assigned to the delivery item category? Check the
settings in the Implementation Guide for -> Quality certificates -> Output determination ->
Output determination procedure -> Assign output determination procedure to delivery item
category. If there is no entry for the delivery item category you are using, assign a suitable
output determination procedure to the delivery item category.
- Is there a suitable output determination procedure available?

Check the settings in the Implementation Guide for -> Quality certificates -> Output
determination -> Output determination procedure -> Process output determination procedure.
Select -> Navigation -> Control to display a list of the output types. At least one output type
for quality certificates must be present in the procedure used for the item messages. Also
check the specified conditions for these output types. Use the possible entries help (F4) to
obtain additional information about the conditions.
- Checking the output type(s).

At least one output type for quality certificates must exist in the Implementation Guide for ->
Quality certificates -> Output determination -> Define condition types. In the detail screen
(F2), check the following items:
Is an access sequence entered?
Should the output be found by accessing a condition?
Are default values stored for the condition record?
Have entries been made for the processing program? (Pushbutton 'Processing
program'; SAP standard: RQCAAP00; you do not have to specify a form for the certificates.)
Is there an entry in the printer parameters for the automatic determination of a printer?
Is the proposed archiving mode (for example, print and archive) correct?
- Is the access sequence correct?
In the Implementation Guide for -> Quality certificates -> Output determination ->
Define access sequences, select the access sequence that is entered in the output type. To do
this, select -> Navigation -> Accesses. Do the table entries meet your expectations (that is,
was the certificate recipient maintained under one of the key combinations specified here)?
Using the function Navigation -> Fields, for each field you can check how the data for the
delivery item is transferred to the key combinations for the condition tables via the
communications structure.
b) Output dispatch
- Check the output type to determine whether the proper identifier has been entered for the
printer parameters. Use the possible entries help (F4) to obtain the explanation (for example, 5
= shipping point).
- In the Implementation Guide, select -> Quality certificates -> Output determination -> Set
printer parameters. Position the cursor on the entry 'Shipping.' In the list that is displayed,
select the the output type(s) that correspond to certificates by double-clicking the mouse. The
system displays a fast entry screen in which you can enter the output devices for the affected
organizational units (for example, shipping point). Check the entries.
c) Finding Inspection Results
You must define a characteristic filter in order to access characteristic inspection results.
Check if view V_TQ78 contains an entry for transaction QC00 and if the control indicator
corresponds to the system standard.
23.5.1 Certificate Profile
In this chapter, you make the settings for the certificate profiles. You are also required to create the
necessary certificate profiles (master data).
A certificate profile specifies:
- What information is to be contained in the certificate:

- Default values
- Inspection results
- Texts
- The origin of the data in the certificate:
- Master inspection characteristics from task lists
- Batch characteristics from material specifications
- How the data is be displayed
Make sure the profiles are compatible with the certificate types.
Requirements
If you want to access quality characteristics in the certificates, you must have previously maintained
these characteristics as one of the following:
WHATSAPP +255738656506
- As characteristics in the classification system
- As master inspection characteristics
Standard settings
Client 0 in the standard system contains at least one example of a layout set. This layout set uses four
standard texts.
- The sample layout set is stored under the generic name QM_QCERT*.
- The standard texts are stored under the generic name QM_QCERT*.
Be sure to note the remarks about the MAIN window in the layout set that has been provided as an
example (select text elements!).
To be able to use the example, you must copy the corresponding standard texts to the current client.
Activities
1. Design the layout for your certificates.

2. Complete the SAPscript layout sets and standard texts used for this purpose. Use the example
contained in the standard as a basis.
a) Create layout sets.
b) Create standard texts
c) Create profiles
Further notes
You can have the system display a certificate that was created with a selected profile. To be able to do
this, you need a delivery item for a material for which the required data (for example, inspection results)
is available in the system.
23.5.1.1 Define Status Profile for Certificate Profiles
In this step, you can define your own status profiles for certificate profiles. These are then assigned to the
certificate type.
Activities
1. Check whether user statuses are required for certificate profiles.

2. Define the corresponding status profiles.
Further notes
For more information, please refer to the chapter Environment, Central functions, General Status
Administration, Status Profile.
Tip: You can delete blocked certificate profiles with the help of the user status, that is, the system allows
the "delete" operation in the "Blocked" status. Otherwise, you can only delete profiles that have not been
released (profiles that still have the system status "Created").
23.5.1.2 Define Certificate Types
In this step, you define the certificate types.

You only define the keys and short texts for the certificate types. When you define the certificate profiles,
you must make sure the certificates conform to the standard type in both form and content.
You can assign a status profile to each certificate type.
Recommendation
- Note that the table of certificate types is used both in procurement and Sales & Distribution.
- Define the certificate types according to the applicable standards.
Activities
Determine which certificate types are required in your company for procurement and sales/distribution
and define these certificate types in the table.
Further notes
Refer to the chapter 'Environment' for information on the general status management function and the
status profile.
23.5.1.3 Maintain Form
In this step you maintain the SAPscript forms for the certficate profiles.
Requirements
To process forms, you need to have experience in SAPscript.
Standard settings
The standard system provides the universally applicable QM_QCERT_01 form.
Recommendation
Use this form as it is, or use it as a copy model for your requirements.
If you need to adapt the certificates, consider the following in sequence to achieve your aim with the least
possible effort.
a) Adapt forms
In most cases this should be enough for your requirements. You can, for example, use the
SAPscript user exit for selecting additional data. (You can find more information on this in
the Extended help for the SAPscript control command
PERFORM).
b) Adapt the function module for data retrieval

This step is required if you want to allow other data origins for characteristics.
c) Change the output programs

WHATSAPP +255738656506
This complicated procedure is only necessary if you want to alter the structure of the form, for
example, if you want to interchange columns or lines in the certificate.
Activities
Determine whether you need your own forms for quality certificates and ensure that these are created to
accepted standards.
Also determine whether you need your own function module for data retrieval, or whether you need to
adapt the output program.
Further notes
The forms must be compatible with the output program. In the standard system the following output
programs are available:
- RQCAAP00 for certificates for a delivery item

You can access this program in Customizing for message dispatch and the program can be
exchanged.
- RQCAAP01 for certificates for an inspection lot

- RQCAAP02 for certificates for a batch
- SAPLQC07 for certificates for a batch on the Internet
23.5.1.4 Define Data Origin
In this step, you define data origins for certificates.
If you are using certificate types which contain value information for inspection characteristics or class
characteristics, the values can have the following origin:
- Default values for characteristics

- From master inspection characteristics
- From batch specifications
- Results for characteristics
- From result records for the inspection lot or partial lot
- From batches
You can define sources for language-specific characteristic short texts irrespective of the origin of the
value specifications:
- Characteristics from a certificate profile

If no text is found here, the system accesses further master records:
- Master inspection characteristics

- Class characteristics
If the results are loaded from inspection lots or partial lots, you must specify strategies for the skip
procedure when maintaining the certificate profiles.
If the results for inspection points or samples were loaded, the mean values and original values for the
last inspection point or last sample (or for all inspection points or samples in an inspection lot) can be
included in the certificate.
You can define keys for all of the listed data origins in the system and assign function modules for data
retrieval to these keys.
In certain circumstances you need to include differing materials in certificates, for example, if the same
material is sold in different forms, but the properties of the material remain the same.
To avoid incorrect assignments of data origins, you define allowed combinations of data origins for
characteristic specifications and characteristic values. You can also define that specifications and values
must come from the same source.
Standard settings
The system already contains predefined keys and function modules for the data origins.
Proposals are also implemented in case of a skip.
Recommendation
- Use the data origins set in the system. Consult an expert if you want to implement your own data
origins.
- Do not change the function modules implemented in the standard system. Create your own function
modules, if necessary. Use the available function modules as copy models, for the interfaces in
particular.
Activities
You can use the online documentation for the table fields and function modules to determine from where
the system retrieves the characteristic data in the standard system. It is only necessary to define your own
origins and function modules if this manner of retrieval is not acceptable. In doing so, consider the
following origins:
1. Origin of the default values

2. Origin of the short texts
3. Origin of the result values
4. Alternative strategy in case of a skip
5. Allowed combinations of default origins and characteristic values
The report RQCFTQ65 determines the usual combinations using the characteristic data in the
existing certificate profiles and makes entries in the table.
Further notes
You can specify which inspection characteristic results are used for data retrieval. In the standard system,
these are all of the valuated characteristics. In the chapter Quality Inspection/Results Recording, you will
find more detailed information under filter for inspection characteristics. The table entry QC00 is
responsible for retrieval of the certificate data.
23.5.1.5 Define Configuration of Characteristics Field
Use
In this Customizing activity, you define characteristic-field configurations that you use in the certificate
profiles to print using Adobe forms.
WHATSAPP +255738656506
A characteristic field configuration is comprised of text elements that are equivalent to the text elements
in a SAPscript form. As when printing using SAPscript forms, the text elements are assigned to the
individual characteristics in the certificate profiles when printing certificates using Adobe forms.
A text element for a characteristic configuration is comprised of a list of structure fields. In the
certificate, the system only prints fields from the QCRES and QCSPEC data structures for a
characteristic that are in the field list for the text element assigned to the characteristic.
Correspondingly, only the fields for the assigned text elements are copied when creating IDocs.
Standard settings
Characteristic field configuration 001 is provided in the standard system. This characteristic field
configuration contains six text elements. The fields of these text elements regulate the use of the text
elements from SAPscript form QM_QCERT_01.
Activities
Check whether you need further text elements (in addition to those provided in the standard system) to
print certificates for your own Adobe forms.
Specify the fields that are relevant for transfer to your certificate form.
23.5.1.6 Profile Determination
In this section, you determine how the certificate profiles are found.
The certificate profile determination function uses condition functions from the Sales and Distribution
module.
The source element is the so-called plan. Usually, a plan can contain several lines with condition types
that are processed in sequence. Processing can be subject to conditions.
Every line uses a certain condition type that in turn refers to an access sequence. The access sequence
determines the sequence in which the condition records are accessed from the condition tables.
The user can define the keys for condition tables by selecting one or more fields from a field catalog.
The system searches for the certificate profile that matches this key when a certificate is created. If it
does not find a reference under this key, it searches further keys in accordance with the access sequence.
The condition technique used here for profile determination is also used for output determination where it
is implemented to an even greater extent.
23.5.1.6.1 Condition Table for Profile Determination
In this section, you set the condition tables that are used to control the profile determination function. The
method used here also applies to the condition tables for output determination.
23.5.1.6.1.1 Define Field Catalog for Profile Determination
In this step, you define the field catalog for the condition tables.
You can create condition tables for profile determination using the fields contained in the field catalog.
Standard settings
The system already contains a very comprehensive field catalog.
Recommendation
Use the field catalog contained in the standard system.
Activities
Determine whether it is necessary to change the field catalog contained in the standard system and, if so,
adapt it accordingly.
Further notes
If you have to include new fields in the field catalog, please refer to the chapter System Modification,
New Fields in the Implementation Guide for the Sales and Distribution module. Additional fields for the
condition tables of the certificate profiles must be included in the DDIC structure KOMI. You can fill
the new fields with the help of the function enhancement QCPA0003 (user exit
EXIT_RQCAAP00_001).
23.5.1.6.1.2 Edit Condition Tables for Profile Determination
In this step, you process the condition tables.

To create a condition table, first choose the fields from the field catalog that is to be used for profile
determination. Then generate the condition table.
Standard settings
The standard system contains several examples of condition tables.
Recommendation
- Only define special conditions as necessary - for example, to issue customer-specific certificates.
- Define the conditions as globally as possible by specifying the customer group instead of the
customer or the material group instead of the material (for example, to restrict the number of
certificate profiles and reduce the effort involved in maintaining them).
Activities
1. Determine the criteria that are to be used to find certificate profiles in your company.
a) Which fields are used in the condition records?
b) Which condition records form a continuous sequence from special to global access
which ensures that the system always finds a suitable reference?
WHATSAPP +255738656506
2. Define and generate the required condition tables.
23.5.1.6.2 Define Access Sequence for Profile Determination
In this step, you maintain the access sequence that is used to find the certificate profile.
The system searches for the certificate profile sequentially using the condition records contained in the
access sequence.
Standard settings
The systems contains an access sequence QCA1 as an example. This access sequence ranges from
special to general and contains the condition tables:
- Material + customer + partner function

- Material
- Material group
Activities
Define a suitable sequence of conditions for your application in the access sequence QCA1 or define
your own access sequence.
Further notes
Note that this setting is applies to all clients!
23.5.1.6.3 Define Condition Type for Profile Determination
In this step, you maintain the condition type to determine the certificate profiles.
Standard settings
The current release has only one predefined condition type.
Activities
Check whether condition type QCA1 exists in the system and whether it contains the access sequence
QCA1 (or an access sequence you have defined yourself).
23.5.1.6.4 Define Scheme for Profile Determination
In this step, you define a scheme for profile determination.

The current release features only one predefined scheme.
Standard settings
The scheme QC0001 is predefined.
Recommendation
Do not change the predefined scheme.
Activities
Check whether the scheme QC0001 is set in the system and whether it refers to the condition type QCA1.
23.5.1.6.5 Define Number Range for Condition Records
In this step, you define the number range for the condition records for profile determination. This number
range applies to the entire client.
Recommendation
Retain the number range contained in the standard system.
Further notes

In the initial screen, select "Interval - Transport."
exported intervals will be present. The number levels are imported with the value they have at the time of
the export.
23.5.2 Output Determination
In this chapter, you define the settings for output determination; that is, you determine how the certificate
recipient is found and assigned. The certificate recipient here means: partner function (for example, sold-
to party or goods recipient) and shipping type (for example, fax, immediate shipping, language English).
The technical concept of the output determination function is identical to that used for profile determination.
However, the options contained in the concept are used to a greater extent for output determination.
The output determination concept is described in detail in the Implementation Guide for the Sales and
Distribution module. Refer to the chapter Basic Functions, Messages with the subchapter Output
Determination and the section Message Default for Condition Technique.
23.5.2.1 Condition Tables for Output Determination
In this section, you edit the condition tables for output determination. Here you use a similar method as
for the condition tables for the profile determination.
The output determination procedure using condition tables is described in detail in the Implementation
Guide for the Sales and Distribution module.
23.5.2.1.1 Define Field Catalog for Output Determination
In this step, you define field catalogs for condition tables for output determination.
WHATSAPP +255738656506
The procedure is identical to the one used for the field catalogs for profile determination.
Standard settings
The system already contains a very comprehensive field catalog.
Recommendation
Use the field catalog contained in the standard system.
Activities
Determine whether it is necessary to change the field catalog contained in the standard system and, if so,
adapt it accordingly.
Further notes
If you have to include new fields in the field catalog, please refer to the explanation of the step 'New
fields' in the chapter System Modification in the Implementation Guide for the Sales and Distribution
module.
For certificates, that is for messages on the delivery item, the structures KOMKBV2, KOMPBV2,
KOMB are relevant.
23.5.2.1.2 Edit Condition Tables for Output Determination
In this step, you process the condition tables for the output determination.
The procedure is identical to the one used to maintain the condition tables for profile determination.
Standard settings
The standard system contains several examples of condition tables.
Activities
1. Determine which criteria is used in your company to find the recipients (partner function, shipping
type).
2. Which fields are used in the condition tables?
Make sure that access sequences can be defined (on the basis of the tables defined by these fields)
that progress from a special access to a global access.
3. Define and generate the required condition tables.
Further notes
When you define a table, first choose the fields that are suitable as criteria. Then supplement this
selection (with the help of the function key 'Technical view') by determining whether each field is to
appear in the header or in the line when the output condition records are processed and whether a
descriptive short text is to be displayed.
23.5.2.2 Define Access Sequences for Output Determination
In this step, you determine the access sequences for output determination.
The procedure is identical to the one used to define the access sequences for profile determination.
The system searches for the messages (partner functions and shipping type) in sequence with the
condition records contained in the access sequence.
Standard settings
The system contains an example of an access sequence that progresses from special to general access
with the condition records
- Sales organization + distribution channel + division + customer

- Sales organization + customer
Activities
Set the access sequences that are suitable for you application.
Further notes
- This setting applies to all clients!

- Note the documentation for the 'Condition' and 'Exclusive' fields.
23.5.2.3 Define Condition Types for Output Determination
In this step, you define condition types for the output determination.
The condition types correspond to the output types contained in an output determination procedure.
The procedure is identical to the one used to specify the condition types for the profile determination;
however, it makes greater use of the control possibilities in the condition type.
In the condition type, you define the following items (among other things):
- access via the condition table

Generally, only this access method is recommended.
- document type for the archive

The document type QMOCERT is defined in the standard system.
Furthermore, you determine the following default values for the condition records:
- output medium (printer or fax)

- time of output
- partner function for which an output is intended
- print parameters
You can disregard the other fields that are not used in the standard settings.
Standard settings
WHATSAPP +255738656506
The following condition types are set up in the standard system:
- LQCA (for quality certificates intended for the ship-to party)

- LQCB (for quality certificates intended for the sold-to party)
QMOCERT is used as the document type for the archive. The archiving function, however, is not active
in the standard system.
Recommendation
Use the condition types that are available in the standard system. If your system has a link to the archive,
you can activate it by selecting a suitable archiving mode.
Activities
Check the details of the condition types. In doing so, be sure to refer to the field documentation.
Further notes
With respect to the partner function, also refer to the step Define partner for each output.
23.5.2.4 Define Exclusion Conditions
In this step, you can define exclusion conditions that prevent certain condition types in the output
determination procedure from being accessed.
Example
You want to prevent the same addressee from receiving several versions of a certificate if the sold-to
party and goods recipient are identical.
Standard settings
The standard system contains several conditions which you can use as a reference:
- Exclusion condition 012 -

Exclusion condition
012 - Exclusion condition
012
- Exclusion condition 012
Recommendation
Use the conditions 015 and 016 if you want to print the certificate only when the delivery item can no
longer be modified (printing after goods issue).
If you want to print the certificate earlier, you can use conditions 012 and 013 (printing after picking).
Activities
1. Determine whether conditions can occur, under which certain condition types are not to be carried
out.
2. Formulate these conditions in ABAP/4 FORM routines.
3. Store these routines in the table and assign them the Shipping V2 application.
Further notes
The conditions can also be used in the access sequences.

You can define your own conditions. Technical instructions for doing so can be found in the
Implementation Guide for the Sales and Distribution module in the chapter System Modification,
subchapter Routines, section Conditions.
23.5.2.5 Output Determination Procedure
In this section, you edit the output determination procedures for creating certificates.
The output determination procedure contains one or more condition types, that is, it can trigger one or
more individual outputs (certificates).
23.5.2.5.1 Edit Output Determination Procedure
In this step, you define the output determination procedure.

The output determination procedure contains all condition types, that is, all messages which are in turn
processed in accordance with certain conditions. Messages are implemented at different levels of the
delivery. Certificates are messages for the delivery item. If the schema contains two condition types, for
example, two certificates can be issued.
The output determination procedure can link the condition types contained in it to conditions which
prevent further processing.
Standard settings
The determination procedure V20001 contained in the standard system contains all of the messages for
the delivery item. It refers to the condition types LQCA and LQCB. If this procedure or the entries
contained in it are not contained in the current client, then you must copy the determination procedure
V20001 and the corresponding control with condition types LQCA and LQCB from client 000.
Recommendation
Keep the schema V20001 contained in the standard system.
Activities
1. Check whether you want to maintain the condition types

predefined in the standard system.
2. Check the conditions linked to the condition types. Read the
long texts for the conditions.
Further notes
The conditions can also be used in the access sequences.
WHATSAPP +255738656506
You can define your own conditions. Technical instructions for doing so can be found in the
Implementation Guide for the Sales and Distribution module in the chapter System Modification,
subchapter Routines, section Conditions.
23.5.2.5.2 Assign Output Determination Procedure to Delivery Item Category
In this step, you assign output determination procedures to the delivery item categories and in doing so,
you activate the creation of certificates.
There are many delivery item categories; different messages or no messages are to be issued, depending
on the item category.
Requirements
The delivery item categories that can be used in your company have been defined.
Standard settings
An output determination procedure has not been assigned to any of the delivery item categories in the
standard system.
Recommendation
Assign the output determination procedure V20001 contained in the standard system to the delivery item
categories for which you want to create certificates.
Activities
1. Determine which output determination procedures are to be used for which delivery item categories.
2. Set these output determination procedures and maintain the assignment table.
23.5.2.6 Define Partner for Each Output
In this step, you determine the partners for each output.

You determine the output medium and the functions of the partners who should receive the output for
each output type.
Requirements
The partner functions are defined.

The following partner functions are predefined for quality certificates:
- goods recipient
- sold-to party
- Q1 quality certificate recipient at the goods recipient
- Q2 quality certificate recipient at the sold-to party
Activities
1. Check the partner functions contained in the system. These may have to be adapted.
2. Allocate the appropriate partner functions to the condition types (individual messages).
Further notes
Partner functions are also required for other applications, for example, quality notifications. For detailed
notes on maintaining partner functions, please refer to the Implementation Guide for the Sales and
Distribution module in the chapter Basic Functions, subchapter Partner Determination, section Partner
Functions.
23.5.3 Process Output
In this chapter, you make the necessary settings to create the certificates. This includes making the
preparations to print the certificates and dispatch the outputs.
23.5.3.1 Set Print Parameters
In this step, you set the output parameters.

The condition types set for the output determination, which the system can find automatically, appear
under the category "Shipping". Per condition type, you specify - depending on which output location in
the condition type is set as a print parameter - one or several locations and determine an output device as
well as some parameters for the printout per condition type and position. For more information on the
output parameters, please refer to the field documentation.
Requirements
The locations (for example, shipping points, sales offices ... ) are defined.
Standard settings
In the standard system, there are entries for the condition types LQCA, LQCB.
Activities
1. Determine which output locations are possible for each condition type.
2. Maintain the output parameters for each condition type and position.
Further notes
The output location for certificates - generally the shipping points - are components of the company
structure. For further details on the shipping points, refer to the Implementation Guide for the company
structure (chapter Logistics, Sales and distribution Define and allocate shipping points).
- This step is a part of the setting for the print parameters in the Sales and Distribution module.
WHATSAPP +255738656506
23.5.3.2 Dispatch Trigger
In this section, you define the triggers for dispatching the certificates.
If you want to dispatch the certificates at a specific time or on a periodic basis, you can define batch jobs
that will select and display/print the outputs according to certain predefined criteria. Four processing
times (time options) are available for the output dispatch:
1. Dispatch with the next selection run.

2. Dispatch with a time reference.
SAP recommends that you define batch jobs for time options 1 and 2.
3. Dispatch on the basis of an explicit request (using the function create certificates).
4. Dispatch immediately after saving the delivery.
The batch jobs use variants that you create for a selection program.
The technique that is used is described in the Implementation Guide for the Sales and Distribution (SD)
module. Refer to the chapter Basic functions, Output, Initiate dispatch.
23.5.3.2.1 Define Variants for Selection Report
In this step, you define variants for the selection report.
Standard settings
The standard system contains the basic report RSNAST00 and the output types LQCA and
LQCB. Certificates for the delivery item belong to the application V2.
Activities
Maintain the variants required in your company for the selection report,based on the relevant output
types and transmission media.
Further notes
Use the output control method that is also used to define the start of shipping activities in the Sales and
Distribution module.
23.5.3.2.2 Define Batch Request
In this section, you define the batch requests for dispatching an output.
Standard settings
The selection program RSNAST00 is available in the standard system.
Activities
Define which period will be used to select the outputs. Set up the corresponding jobs.
Further notes
Every user can use an individual job and an individual selection variant. Depending on the setting, the
job runs either immediately after it is saved or at the predefined time.
The procedure for defining jobs is described in greater detail in the Implementation Guide for the Sales
and Distribution module (chapter Basic Functions, Output, Initiate dispatch, Initiating shipping).
23.5.3.3 Assign Print Program to Output Type/Medium
In this step, you assign the processing programs to the output types (condition types) and the media used.
Standard settings
The message processing program RQCAAP00 is implemented in the standard system for both condition
types LQCA and LQCB.
There are two subprograms that you can use: ENTRY and ENTRY_01.
The ENTRY_01 subprogram gives a better system performance for certificate profiles with a large
number of class characteristics. The subprogram, however, has its limitations. ENTRY_01 filters out
class characteristics. Subsequently, the program only processes the class characteristics that fulfill the
following criteria:
- If they are marked as obligatory characteristics.

- If they are in the batch class of the material.
- If they have a link to a material from the material list in the certificate profile.
Activities
1. Determine the output media (printer, fax) on which the certificates are to be issued.
2. If the processing program RQCAAP00 does not fulfill all of the requirements, create your own
processing programs and assign them to the output types in the table.
Further notes
In this step, you determine the processing programs for issuing delivery certificates. In the standard
system, the following processing program exists:
- RQCAAP00 Certificate output for delivery

In addition, there are the following processing programs in the standard system:
- RQCAAP01 Certificate output for inspection lot

- RQCAAP02 Certificate output for batch
Both these programs are linked to transactions QC21 and QC22 and cannot be set in Customizing.
In addition, the processing program RSNASTED is included in the standard system for the condition
types LQCA and LQCB. This program is used for certificate processing using IDocs (medium EDI).
WHATSAPP +255738656506
23.5.3.4 Define Output Types with Certificate
In this step, you define with which output types and transmission mediums certificates can be issued.
You only need to maintain these settings, if you want to create certificates for delivery items in the
Internet.
Example
If your business partners want to access certificates for output type LQCA from the archive using the
Internet, enter output type LQCA and dispatch type 1 (print output) in the table, and set the indicator
"Archive".
Requirements
Output determination must be maintained. Make sure that the output types are defined and the following
assignments are maintained.
- Output type to a valid output determination procedure

- Output type and transmission medium to the partner role
- Output type and transmission medium to the output program
Standard settings
The standard system contains a few entries for the output types LQCA and LQCB.
Recommendation
See the F1-help in the table.
Activities
Determine which output and transmission mediums are required in your company. If you want to transfer
certificates for deliveries using the Internet, you must maintain the affected entries in the table.
Further notes
Archiving is only supported for the transmission mediums print output and fax. The indicator Archive
display from the Internet has no effect on other transmission mediums.
23.5.3.5 Assign Sender Texts to Processing Program
In this step, you can define certain sender texts for the certificates. You only
need the sender texts in certificates created for:
- An inspection lot
- A batch
In the certificates for a delivery item, the sender texts are retrieved from the sales organization.
The sender texts include the:
- Header text
- Footer text
- Signature text
- Sender
The sender texts are assigned to the company code.
Requirements
The corresponding texts are available in SAPscript in the current client.
Standard settings
The following program assignments are available for company code 0001 in the standard system:
- RQCAAP01
- RQCAAP02
- SAPLQC07
Activities Determine whether you want to define copy models for the above
referenced sender texts at the company code level. If necessary, maintain the
table.
23.5.3.6 Define Archive Link
In this step you define the links for archiving certificates in the optical archive.
For more detailed information refer to the Implementation Guide Documentation for Basis / Services /
ArchiveLink / Basic Settings section Define Links.
Requirements
An (optical) archive exists

You can only archive certificates for the following business objects:
- Delivery item
- Inspection lot
- Certificate in procurement
You cannot archive certificates for a batch.
There is currently only an archive link for outbound certificate and the print output medium; there is no
connection for the telefax output medium.
Standard settings
The standard system contains the following entries:
Business Object | Document Type

------------------------------------|-----------------------------------
BUS2045 Certificate for insp. lot | QMOCERT
LIPS Cert. for delivery item | QMOCERT
WHATSAPP +255738656506
BUS2117 Cert. in procurement | QMICERT for fax
BUS2117 Cert. in procurement | QMICERTPDF as PDF file
--------------------------------------------------------
-
---------------
Recommendation
Use the standard settings.
Activities
Determine whether you need to archive certificates and maintain the assignments if required.
23.5.3.7 Define IDoc Processing
In this step, you make the preparations for the IDoc processing of quality certificates. These apply to both
outbound and inbound certificates.
The organizational control of the certificate receipt is dealt with in the section Quality Management / QM
in Logistics / QM in Procurement / Certificate Processing.
Requirements
Before you can use IDocs to dispatch certificates, you must make sure that your system actually creates
certificates for delivery successfully. You can find instructions for testing the certificate creation function
and on troubleshooting in the documentation for section Quality Certificates.
Standard settings
1. Archiving using SAP ArchiveLink has already been set up. The following Customizing settings are
relevant:
a) The document class PDF is defined (client-independent).
b) The document type QMICERTPDF is defined.
c) The link between document type QMICERTPDF and business object BUS2117 has been
entered.
2. The following data has been maintained in the IDoc application:
a) The process code for outbound processing of QCERT_OUT has been entered in the IDoc
transaction WE41.
b) The process code for inbound processing of QCERT_IN has been entered in the IDoc
transaction WE42.
c) The logical message type QCERT has been entered in the IDoc transaction WE81 (client-
independent).
d) The logical message type QCERT has been linked to the IDoc type QALITY01 in the
IDoc transaction WE82 (client-independent).
e) In the IDoc transaction WE57, the function module IDOC_INPUT_QALITY01 has been
assigned to the link given in the previous step (client-independent).
3. In Customizing for quality certificates, the following have been entered:
a) Transmission medium 6 has been entered in the step Output Determination Define Partner for
Each Output for the relevant output types and partner functions.
b) Output program RSNASTED with form EDI_PROCESSING has been entered for
transmission medium EDI in the step Output Processing / Output Program
Recommendation

Note: You can copy the standard settings for quality certificates to the current client with the help of
transaction QCCZ. To do this, refer to the documetation on the workstep Setting up clients.
Activities
1. Check whether the standard settings are complete. Supplement the settings if necessary.
2. Work through the steps listed below.
a) Define Ports
b) Define Partners
23.5.3.7.1 Define Ports
In this step, you define the ports for the data transfer, using IDocs.
Information on the technical hook-up of external systems is stored in the port description. IDocs can be
transmitted to an EDI system, using the port type DATEI. The INTERNET port type allows you to send
IDocs as mail attachments via the Internet.
Requirements
There must be at least one port for each external system. To use the port, you must also make settings
outside the IDoc interface:
- An EDI system must be set up for the DATEI port type.

- The gateway (SAP gateway or MS Exchange server) must be set up for the INTERNET port type.
Activities
Define a port for inbound and outbound certificates.
- Enter the address that you want to use to send or receive certificates. - Enter a function
module that clearly names the outbound IDocs
WHATSAPP +255738656506
23.5.3.7.2 Define Partners
In this step, you define the partners that are involved in the data transfer using IDocs.
Requirements
- The ports for sending certificates are defined.

- The master data for the business partners, that is creditors (vendors), or debtors (customers)
exist.
Activities
Maintain the following partner data for the certificate issue:
- Partner function: KU - Outbound parameter:

- Partner type: WE, AG, Q1 or Q2
- Message type: QCERT
- Basic type: QALITY01 (for transfer in text form)
- Basic type: QALITY02 (for the transfer of characteristics values)
- Application: V2
- Output type: LQCA, LQCB, ...
- Process code: QCERT_OUT
Maintain the following partner data for the certificate receipt
- Partner function: LI
- Inbound parameter:
- Partner type: LF
- Message type: QCERT
- Process code: QCERT_IN
23.5.3.7.3 Activate Workflow Template
In this step, you activate the workflow template that should be used during certificate transfer.
Further notes
You can find a more detailed description in the section Environment/Central Functions/Activate
Workflow.
23.6 Quality Notifications

This chapter contains instructions on how to use the quality notifications and functions for defects
recording.
In the course of processing problems and initiating corrective actions, the quality notification supports
you in a number of tasks. These tasks include:
- Documenting the nature of the problem

- Diagnosing the defects
- Defining and implementing tasks
- Recording costs
- Managing the statuses of notifications and tasks
- Communicating with the parties who are involved with the problem
- Evaluating the notification data
While you can use the quality notifications independently of the other functions in the QM
application component you can also create quality notifications using these other functions (for example,
when you record defects for an inspection lot).
The defects recording function is a supplementary feature of the Q-notification. It provides a quick and
simple means of recording the defects that are encountered during quality inspections. Once you have
recorded the defect data, you can process this data further in the form of quality notifications.
You can use the defects recording function to document the following defect criteria:
- Defect type
- Defect location
- Defect cause
- Activity
- Defect valuation
Note
In addition to the notification category quality notification, there are the following special notification
categories:
- General Notification
This is used to process and document problems or requests in various scenarios.
- Maintenance Notification
This is used initiate and document maintenance tasks.
- Claim
WHATSAPP +255738656506
This is used to identify partners, who are responsible for variances from specification or to avert
demands from third parties who hold the company responsible for a variance.
You make the system settings for these notification categories in joint tables; this means that in certain
tables there are entries for other notification categories.
Recommendation
Use the standard settings as a basis for your system.

Implement the work steps contained in the Notification Creation step. First, read through the steps to gain
an understanding of the required settings. At the second reading, you can then decide which settings you
need to make.
You only need to implement the Defects Recording step, if you want to record defect data records
quickly in a quality inspection.
Most of the settings are dependent on the notification type. Once you have made the basic settings, it is
therefore often advisable to make final adjustments to the definitions of the notification types, and then
to adapt the settings which are dependent on these types accordingly.
Further notes
You can access this Implementation Guide directly using transaction QCC2.
23.6.1 Overview of Notification Type
This step gives you an overview of:
- The notification types that are available in the system.

All notification types for all notification categories and notification origins are listed.
- The settings of a particular notification type

You can display all assignments of notification parameters for one
notification type.
Requirements
The notification types and the parameters assigned to the notification must have been assigned for you to
be able to use the overview function described in this step.
Recommendation
Think of this function as a tool for the expert, who wants to gain an overview of Customizing for the
notification type.
Activities
When implementing notifications, first work through the sections Notification Creation and Notification
Processing. These provide an ideal basis for using this function.
23.6.2 Notification Creation
In this section, you define the notification types. For each notification type, you define the screen layout
and the basic data required in the notification.
The basic data includes the following objects:
- The catalogs specified in the catalog profile; these catalogs are used to define the subject matter of
the problem, defect criteria and tasks.
The chapter Quality Management -> Quality Planning -> Basic data -> Catalogs contains general
instructions on how to set up the catalogs. For this reason, this section only covers the
supplementary activities for the notifications.
- The partners responsible for the problem solution.

You can use different partner types in the notifications (for example, vendors, customers,
administrative offices, system users). This means you must access the master data in other
applications.
A notification can reference one or more objects that appear as master data or transaction data in the
Logistics applications.
- Master data:
- Vendor/manufacturer, customer
- Material/plant
- Batch
- (Project and WBS element in category 'claim' only)
- Transaction data
- Inspection lot
- Purchasing document/material document
- Manufacturing order
- Sales order/delivery
Notification items can reference bill of material (BOM) items (assemblies).
(Note: in the settings at the client level, you can store a special default value for the BOM usage.)
Depending on the origin of the notification, you require different basic data and reference objects and as
a result, different screens. Different notification types have been defined for this purpose.
You can create quality notification types for the following origins:
- Customer complaint
- Complaint against vendor
- Internal problem notification
23.6.2.1 Notification Type
In this step, you define the notification types and their basic functions.
WHATSAPP +255738656506
23.6.2.1.1 Define Notification Types
In this step, you define the quality notification types.
Each notification type has a reference to a notification category and an origin. The category of a
notification is fixed, based on the origin of the notification.
You can create quality notification types for the following origins:
- Customer complaint
- Complaint against a vendor
- Internal problem notification
- SAP notification to SAP Support Line
The origin includes an appropriate screen control in the transactions for the notification.
There are very comprehensive controls for the notification type. Due to the scope of these controls, they
are described in separate sections of the Implementation Guide.
Standard Settings
With the notification type, you define the use of the notification. In the standard system, there are the
following types of origin of the notification:
- General Q-notification types Q*

- Complaints against vendors Q1
- Complaints filed by customers Q2
- Internal problem notifications Q3
- Q-notification types for recording defects for inspection lots F*
- Defect records for a goods issue inspection F1
- Defect records for a goods receipt inspection F2
- Defect records for an inspection during production F3
Notification type $$ is reserved for the SAP Online Service (OSS).
Recommendation
Use the notification types predefined in the standard system, if you define your own notification types.
Above all, determine which criteria will be used to distinguish the notification types. The possible criteria
might include:
- Origin
This distinction is required because it allows you to provide the appropriate screen controls.
- The organizational units, departments or process stages in which the notification originates or which
the notification references.
If you use this criterion in the defects recording function to define report categories, you can avoid
subdividing the notification types excessively.
- The control parameters that are assigned to the notification type

This additional means of differentiating between the notification types allows you to implement
different notification processing sequences and they may be useful for this reason.
- The grouping methods for evaluations

The QM information system summarizes the key figures for Q-notifications on the basis of
notification types. Make sure you take this into consideration from the beginning!
Activities
1. Determine which notification types will be used in your company and define their parameters:
- Origin
- Catalog profile
(You can also define the catalog profile later in the view "Basic data for the
notification type") Also specify:
- Whether the notification number should be displayed immediately when a Q-notification is created.
- Which update group will be used for the summarization of data in the QM information system
Further notes
In the settings for the quality inspection, you can reference a notification type in the inspection type. The
system uses this notification type to record defects for an inspection lot.
23.6.2.1.2 Define Number Ranges
In this step, you define number ranges for the notifications. Each notification type must be assigned to a
number range. You can assign several notification types to a single number range (a group).
Activities
1. Define which notification types or groups of notification types can be distinguished on the basis of
the number ranges. Define the group titles.
2. Reserve the number ranges for the notifications and assign the corresponding notification types to
these number ranges.
Further notes for Maintaining Number Ranges
To add a new group (number range) and to assign a notification type, proceed as follows:
1. Access the maintenance function. The screen "Number Range: Notification" appears 2. Choose
Group -> Maintain (F6). The screen "Maintain Number Range Groups" appears.
3. Choose Group -> Insert (F6). The screen "Insert Group" appears.
4. On this screen, make the following entries:
a) Description for group
b) Number range interval and identification for internal/external number assignment
c) For internal number assignment, the current status of the number (lower limit for the number
interval)
5. Exit the "Insert Group" screen and return to the "Maintain Number Range Groups" screen. The new
group you have inserted now appears in the overview.
At the bottom of the list, all notification types appear that have not been assigned to a group.
WHATSAPP +255738656506
6. Select a group (such as, the one you added)
7. Select one of the unassigned notification types and choose Edit -> Assign element to a group (F5).
The notification type has now been assigned to a group.
Further notes for Transporting the Number Ranges
The number range objects can be transported as follows:

On the initial screen, select "Interval -> Transport."
exported intervals will be present after the import. The number ranges are imported with the value they
The group texts are also included in the transport.
The groups themselves do not need to be individually transported, because each notification type has a
group (number range) specified. This is defined when the notification type is assigned to the group. The
grouping is therefore transported with the notification types and is available without having to take
further action.
If you make settings in your test client as described in the section Setting Up Clients in Customizing for
notifications, you must copy both the number ranges (using transaction QCCN) and the basic settings
(for example, for quality notifications using transaction QCCM) from client 000, to preserve the group
formations. See SAP note 52390 for more details.
23.6.2.1.3 Define Screen Templates
In this step, you structure the screen templates you want to use for quality notifications.
Requirements
The notification types are predefined.
Recommendation
Activities
A Screen Areas
You can assign the groups of information contained in the quality notifications to various tab pages and
screen areas to give a flexible structure to the screen templates. You perform the following tasks in
separate screen areas:
1. Define screen areas for the notification header.

Here you can assign up to 5 user-defined screen areas in addition to an origin-related screen area.
2. Define screen templates for the simplified view. transactions. Assign the required screen areas.
3. Define screen templates for the extended view.
You can define tabstrips for complex notification transactions and assign screen areas to each
tabstrip.
First copy the settings from client 000.
Determine whether the standard settings for the screen templates are suitable for the contents and
functions of the quality notifications in your company and optimize the settings for the tab pages
and screen areas. Follow these steps:
a) Gain an overview of the available tabstrips and screen areas and their related fields. You need
a sample notification for each notification origin, in which you can check the screen areas.
b) Assign the required screen areas to the tab pages available and give these tab pages a suitable
title.
Note: Tab pages 10\TAB are at header level; tab pages 20\TAB at item level in the Q-
notification.
Tip: Check the effect of the settings immediately in a parallel session using a sample
notification.
Hide the fields that you do not require.
For more information on this method, refer to the section Environment / Tools / System
Settings / Field Selection
Note: If you have not yet defined any screen areas for the relevant notification type, when you
create a notification, the system searches in the standard client 000 for a notification type with the
same notification origin and uses its screen area settings. You can also copy the standard settings
for the relevant notification type into the standard client manually (transaction OIMN). This
transaction does not contain an automatic transport connection. You must add the relevant entries
to a transport order manually (see note 745169).
Note: The screen area with the reference to related notifications is only shown if the appropriate
settings have been made in the QM Information System.
Note (for specialist only): The available screen areas are defined in a subscreen table per
notification type and are accessed via view V_TQSUB. Caution: The table affects all clients and
has the delivery class E. You must NOT change or delete the SAP entries because standard
programs use these. This is why the view is not offered for maintenance in the Implementation
Guide.
B Initial Screens
You can cause the system to offer additional recording screens when you access the quality notification
by assigning the corresponding function modules and initial screens to the notification types. The
system contains examples of this. You can find a list of these initial screens, if you call up the reference
documentation stored for the words initial screens, or if you use the F1-Help (not F4-Help) in the table.
1. Determine the notification origins and notification types for which you require this function and use
the examples provided, or create your own program. Note: The structure RQM01 (SE12) contains
all fields that can be copied into the notification in this way.
2. Hide the fields that you do not require.
For more information on this method, refer to the section Environment / Tools / System Settings /
Field Selection.
C Long Texts
You can control the formatting of the long text on the notification screen. If required, the system can
- Automatically insert log lines

- Prevent changes to text
For more details see the online documentation for corresponding view.
Determine whether you need such functions for specific notification types.
Determine whether such functions are needed for certain notification types.
WHATSAPP +255738656506
23.6.2.1.4 Allocate Start Values for Transactions
In this step, you can define for the notification transactions:
- Whether a particular notification type should be set automatically

- Which notification processing screen is accessed automatically
- Whether the initial screen is processed in the foreground
Recommendation
Copy the standard setting. If you use your own notification types instead of the standard notification
types, copy the standard settings as required.
Activities
Determine whether the recommendation should be deviated from for certain transactions.
23.6.2.1.5 Define Allowed Changes of Notification Type
Use
In this Customizing activity, you define which changes of notification type are allowed.
Standard settings
Included with the scope of delivery are some changes of notification type that are regarded by SAP as
being noncritical.
Simple Change of Notification Type

When creating or changing notifications using the non-QM-specific notification transactions (IQS21,
IQS22), the following applies:
- When creating notifications, you can change the notification type under the following conditions:
- The change was explicitly allowed in this table.
- The notification still has the status Outstanding Notification.
- When changing notifications, you can change the notification type under the following conditions:
- The change was explicitly allowed in this table.
- The notification still has the status Outstanding Notification.
- The original notification type has the notification category General Notification (G0).
You can only allow changes of notification type in which no inconsistencies can occur.
Example
You have created a notification of the category General Notification and want to change it to a
notification of the category Quality Notification to be able to store defect data in the notification items.
Extended Change of Notification Type

The extended change of notification type using the QM-specific notification transactions (QM01,
QM02) allows a change of notification type in the following cases:
- The extended change was explicitly allowed in this table.

- The original notification type and the target notification type have the notification category Quality
Notification.
- The notification does not yet have the status Notification Completed.
Note that a subsequent change of notification type is also not possible if the notification was reset
to the status Notification in Process after being completed.
- The notification does not have the status Defects Recording.

Requirements
You have used the authorization object B_NOTIF_EX to specify for certain user groups whether an
extended change of notification type is allowed for the current notification type.
Activities
After you have established which changes of notification type are necessary in your enterprise, proceed
as follows:
1. Enter the relevant combinations of notification types in the table.

2. For the notification types for which you want to allow an extended change, set the relevant
indicator.
Further notes
When the notification type is changed, the system does not assign a new notification number. For
example, a customer complaint (Q1) still retains its original number from the Q1 number range even
after being changed to a complaint against the vendor (Q2).
In the same manner, all data in the original notification type (such as reference objects) are retained after
a change of notification type. This also applies even if specific data is irrelevant for the target
notification type. To override this behavior, implement the Business Add-In (BAdI)
BADI_IQS0_NOTIF_TYPE_CHANGE.
23.6.2.1.6 Define Notification Process
Use
In this IMG activity, you define QM processes.

Note
You can use these QM processes as filters in the Business Add In
BADI_IQS0_SUBSCREEN_ADDON.
By assigning the QM process to a QM notification type, you can influence which additional fields the
system displays for the notification type. To do this, you must create a BAdI implementation with the
relevant filter value for each relevant QM process.
WHATSAPP +255738656506
23.6.2.2 Notification Content
In this section, you use catalogs and catalog profiles to define the range of values for the qualitative
information contained in the notification. You then assign catalogs and catalog profiles to the
notification type.
23.6.2.2.1 Maintain Catalogs
In this section, you define the contents of the notifications while also taking the next step into
consideration (defining the catalog profiles). This means that you must:
- Define which elements (for example, catalog entries, short text, long text) of the notifications
will be used and which information these elements will contain
- Organize and maintain the catalogs that are used for the notifications and the defects recording
function
Example
Depending on the scope of your catalog profile, you may need catalogs for:
- Problem descriptions (coding) at the notification header level - Defect criteria at the
notification item level
- Defect type
- Defect location
- Defect cause
- Tasks and activities
You can define tasks and activites on two levels in the notification:
- Notification header (immediate tasks, immediate activities)

- Notification item (tasks, activities)
Important: in the notifications, you can only use code groups at the plant level (and not selected
sets). As an alternative, you can limit the selection of available catalogs with the help of the catalog
profile.
Activities
1. First determine which elements in the notification are to contain information that can be
described with the help of terminology catalogs. The answer to this question generally depends
on:
- The scope of the required quality documentation
- The evaluations that are required for quality control purposes
The answer may also depend on the purpose and origin of the notification. The information may be
different for:
- Complaints against vendors

- Internal problem notifications
- Customer complaints
On the basis of this criteria, you can later define different notification types, each with their own
catalog profile.
2. After you clarify this, organize and create the catalogs you need.
a) Define the catalogs in a directory for catalog types.
With the help of the predefined catalogs, you can define the catalog profiles for the individual
notification types later.
b) Maintain the contents of the catalogs.
Refer to the chapter Quality Planning -> Basic Data -> Catalog for detailed information about the
organization of the catalogs.
Further notes
For the 'defect type' and 'defect location' fields in the notification items, the system uses the keywords
from the corresponding catalog types as field descriptions. The field descriptions in the defect records
are predefined.
The catalog processing function does not have a transport link. Enter the details and final entries for the
catalogs in the target system!
23.6.2.2.2 Define Catalog Profile
In this step, you define the catalog profiles for notifications.

The initial view for the catalog profile relates to notifications in general. In this view, you specify:
- Which catalogs and code groups from the individual catalogs should be used for the notifications.
If you enter a generic key for the code group, you can display a selection of the code groups
contained in the catalog.
Use the special characters '+' and '*' for this purpose. For example, if you enter '+A*' in the field for
the code group, the selection will only contain the code groups whose keys contain the letter 'A' in
the second character position.
- Which class in class type 015 should be proposed for the classification of the notification items.
You can use the classes to define general additional problem criteria flexibly, if the problem criteria
in the data structure (defect type, defect location, defect cause) cannot be described adequately
using the catalogs and texts.
For example, if you maintain the class 'problems in production' along with the class characteristic
'cause,' then you can record the causes of production problems as characteristic values.
- The type of system message that will be issued, if you do not adhere to the assigned catalog profile.
Another view applies specifically to the defects recording function. In this view, you specify:
- The unit of measurement and number of decimal places to be used when you record the quantitative
defect valuations.
In the defects recording function, you can valuate the defects quantitatively and, if necessary, assign
a unit of measurement to the value. For example, you can use the potential for damage or the time
and effort required to correct a defect as a criterion for weighting the defects.
Requirements
WHATSAPP +255738656506
- You have defined the catalogs for the notifications.
Recommendation
- Configure the system to respond with an warning (category W), if the assigned catalog profile is not
used.
Activities
1. Define the required code groups for each catalog in the catalog profile.
a) You should agree with all other catalog users how to best define the eight character mnemonic
keys for the code groups. Make a note of the generics of the keys. For example, you can
specify that separate code groups be created for each notification type and that the first two
characters correspond to the notification type.
b) Define the maintenance of the code groups. You can maintain the codes in retrospect.
c) Determine whether you want to classify the notification items. If necessary, create the classes
in the classification system and assign them to the catalog profile. The class characteristics
should be defined and maintained at the same time.
Class type 15 is provided for classifying notification items.
If required you can record class characteristic values in a dialog box when you process
classified notification items.
2. If you want to use the defects recording function, determine:

a) Whether you want to valuate defects
b) Whether a unit of measurement should be predefined in the catalog profile for this purpose.
The unit of measurement must have been defined previously. Refer to the step Units of
measurement in the chapter Basic Settings and Environment.
Further notes
- Each notification type is assigned a specific catalog profile.

You can also store a catalog profile in the material master. This catalog profile takes precedence
over the catalog profile assigned to the notification type.
23.6.2.2.3 Catalogs and Catalog Profiles for Notification Type
Activities
1. Define the information that is to be entered for the notification item and choose the most
appropriate catalog.
2. Define the catalog profile for the notification type, if this did not already take place when the
notification type was created.
3. Activate the Classification of the notification items, if you want to use class characteristics to store
additional information for the notification item.
23.6.2.2.4 Assign Code Groups to Disciplines
Use
In this IMG activity, you assign disciplines of the 8D report to code groups.
With this assignment you define which quality notification data the system uses in the PDF form
QM_QN8D_REP_AUTO.
23.6.2.3 Partners
In this section, you define the partners who are involved in the notifications.
Depending on the notification type, different partners may be involved in a notification. These partners
can play various roles.
When you define the partner functions, proceed as follows:
- Define partner determination procedures that contain the relevant partner functions.
Define the appropriate partner type for each partner function.
Assign the partner determination procedure to the notification type. The
possible partner types are predefined in the system.
- For each partner type, define the fields displayed in the partner lists.
23.6.2.3.1 Define Partner Determination Procedures
In this step, you define the partners for processing notifications.

Several partners are usually involved in processing a notification - internal and external partners. The
types of partners and their functions can be different for each notification type. To define the functions,
proceed as follows:
- Certain partners have been predefined in the system; for example, the following partners apply
to notifications:
- Customer (customer number)
- Vendor (vendor number)
- Person (personnel number)
- System user (SAP user)
- Organizational unit
- You can centrally define partner functions for all logistics applications. You must assign a
partner type to the partner function; for example, you can assign the partner type "Customer"
WHATSAPP +255738656506
(with customer master and customer number) to the partner function "Complainant." You can
also define a higher-level function for a partner function; for example, you can assign the
higher-level function "Customer purchasing department" to the partner function "Customer
purchasing agent."
- Next, define the partner determination procedures. In each partner determination procedure,
you define which partner functions are allowed. In doing so, you can specify whether a partner
function in a notification can be changed or whether it is a mandatory function.
- Each notification type is assigned a group of partners; for example, author, processed by,
person responsible. For this reason, you must assign an appropriate partner determination
procedure to each notification type. For each notification type, you must also assign the
partner functions that will appear in the notification header. All other partner functions can be
maintained in the notification itself, on the partner overview screen.
Standard settings
The internal partner functions (for example, author, coordinator, person responsible) exist for both the
partner types 'system user' and 'HR master record.' The partner type 'system user' was selected for
internal partner functions. If you are also using the HR module and you want to work with personnel
numbers, you only have to exchange the following partner functions:
- In the view 'Assign Partner Functions to the Notification Type'

- Author A0 -> AU
- Coordinator KU -> KO
- In the view 'Define notification types'
- Person responsible (person processing the notification) VU -> VW
Recommendation
Use the notification types and their assigned partner determination procedures, as defined in the standard
system, unless you want to use your own partner determination procedures. If your business organization
is currently using the SAP application components HR Org. or SD, it may be advantageous to select the
partner type "employee" for internal partners, in place of the partner type "system user", as defined in the
standard system. Make sure all other applications are in agreement!
If you want to use your own partner determination procedures you can adapt the predefined SAP
notification types and partner determination procedures to your own requirements.
Activities
1. Define the partner functions and the partner determination procedures.

a) Define the partner functions.
If required, assign multilingual keys to the partner functions
b) Define the partner determination procedure and determine which functions are contained in
each procedure.
2. Assign a partner determination procedure to each notification type.
3. Specify the appropriate partner function in the notification header for each notification type.
Further notes
Multilingual Capability
You can use mnemonic keys for partner functions. The system supports this by assigning multilingual
keys to these functions. You can find this function when maintaining the partner functions in the section
Environment/ New Key Assignment for Functions. Such multilingual keys are displayed if you log on in
a language other than the original language. However, only the original key has an effect in the technical
sense, for example, in SE16 or in the transport system.
Partner Objects
Similar partner determination procedures are also used in other applications (for example, for quality
certificates)and in the Implementation Guide for the Sales and Distribution component
23.6.2.3.2 Define Fields for Partner Lists
In this step, you define which fields will be displayed in the partner lists for notifications.
You can number the fields that are to appear in the list or you can mark them as invisible. From this
predefined field list, each user can create his own user-specific list. The user can only select the
numbered fields and those fields that are not marked as invisible. If you assign numbers to the fields, the
numbers are displayed in the corresponding sequence in the application transactions. If a single user has
not defined his or her own field selection, the fields you activated here will be displayed.
Standard settings
The standard system contains a comprehensive field catalog.
Activities
For each partner type, select the fields that are of interest to you.
23.6.2.3.3 Define Standard Messages to Partners
In this step, you can define standard texts for messages to a contact person for each notification type.
These messages can be sent by the following methods:
- Mail (SAPoffice)
- E-mail (Internet)
- Paging
Example
From the contact person screen in the notification, you can send messages to the following partner types:
- Contact person
- Customer
- User
- Employee
The system sends the message when the notification is saved and sets the corresponding notification
status.
WHATSAPP +255738656506
Requirements
- The basic components SAPoffice or SAPconnect are available in the system.

- The settings for the general application function address management, as well as the subtypes of the
paging services are maintained.
- The sending media and services (subtypes) that are used by the partner must be entered in the
relevant master records, depending on the partner type.
Note: If several services are entered, the system accesses the services in the following order:
- a) Paging
- b) Internet
- c) SAPoffice
Standard settings
The following settings are used for the message short texts:
- The text object TEXT

If you choose this reference object, it allows you to enter texts as freely defined standard texts using
transaction SO10. You can also use any other text objects, such as text for the notification header
(object QMEL).
- The text identification (text ID) QMQN

Although transaction SO10 proposes the text ID ST, your own text ID QMQN gives you the
advantage of differentiating message short texts from other standard texts.
You display and edit text objects with transaction SE75.
Recommendation
Use the text object TEXT that has been defined in the standard system and the text ID QMQN for all
notification types.
Activities
1. Determine whether you want to, or are able to use the services mentioned above, to send
information to the partners involved in the notification. If necessary, you must make sure that the
necessary prerequisites are fulfilled and:
a) Provide the technical back-up
b) Make the relevant settings in the SAP system (see above!)
2. Determine whether you can use standard texts for the messages. If necessary, you must:
a) Define the standard texts
For more information, see the step Text formats / SAPscript in the section Basic Settings and
Environment / Settings.
b) Assign the texts to the notification types.
23.6.3 Notification Processing
In this section, you define a number of controls that will be needed to process notifications. This
includes:
- Additional controls that pertain to the notification type; for example:

- Priority of the notification
- Response monitoring
- Print control
- Miscellaneous controls
23.6.3.1 Response Control
In this section, you define the response to a notification:
- With a priority (this means how quickly you respond)

- According to which response profile that is you can define the timescale and the proposals for
tasks).
23.6.3.1.1 Define Priorities
In this step, you define the priorities for the notifications.

You can define different priority types and assign a priority type to each notification type. For each
priority type, you define:
- Which priority (rank) a notification warrants

- Which start date and finish date (based on the creation date) the notifications should have
Recommendation
Modify the parameters for the priority types after you have collected enough values based on experience.
Activities
Determine which priorities and target basic dates will be valid for the notification types used in your
company.
1. First define the different priority types.

2. For each priority type, define its priority (rank) and basic dates.
3. Assign a suitable priority type to each notification type.
Further notes
The system finds the basic dates for the notification header with the help of the priority; the system
automatically suggests tasks to be included in the notification header using the response profile and
specifies the processing deadlines. These two scheduling functions work independently of one another.
If you choose the unit "day" for the relative start and end time of the notification, the system takes the
factory calender into account. If you choose other units, for example, "hour" or "week", non-working
hours are not considered.
WHATSAPP +255738656506
23.6.3.1.2 Define Response Monitoring
In this step, you define the response time monitoring functions for notifications. For this purpose, you
must first define response profiles and service profiles.
You must then assign these profiles to the quality notification types.
In the response profile, you define a sequence of standard tasks (based on the priority of the notification)
that can be proposed in the notification and which must be carried out within a predefined period of time.
When the system processes a notification, it always assigns the tasks that have been selected on the basis
of a response profile to the notification header.
The service profile defines the times during each work day when a notification is processed. You can
also specify several time periods for each weekday and you can assign a separate response profile to each
of these periods.
Requirements
- You have maintained the task catalog.
Activities
1. Define the response profiles your company needs to process the notifications. The field for the
hierarchy level applies to the service notifications only; it serves no purpose for other notifications,
since only one response profile can be assigned to each notification type.
2. Define valid service profiles for your company. If necessary, specify corresponding response
profiles for these service profiles.
3. Identify the notification types for which response profiles or service profiles are to be predefined
and maintain these assignments.
Note that when you defined your service profiles, you may already have assigned a response profile
to each service profile. This response profile overrides any response profile that you assign to the
notification type. The response profile for the notification type only takes effect, if the notification
is created outside of the service window.
Further notes
Service Windows
The processing times defined in the service profile are only valid for the tasks defined in these profiles
that the system suggests for the notification header. The resulting processing deadlines take precedence
over the basic dates that come from the notification priority.
23.6.3.2 Assigned Objects
23.6.3.2.1 Define Object Categories
Use
In this Customizing activity, you define object categories that can be used for the assignment of objects
to a notification item.
An object category is assigned in the Assign Object Categories for a Notification Item Customizing
activity.
An object category is used as a filter value for the Business Add-In to define its properties.
Example
Object category 001 is provided in the standard system. It implements the properties of a batch. Batch
assignment is provided in the standard Customizing, for example, assignment to notifications with type
(Defect for Material).
23.6.3.2.2 Business Add-In for Implementing an Object Category
Use
This Business Add-In (BAdI) is used in the Quality Notification (QM-QN) component.
You can use this BAdI to implement your own object categories, which can be assigned to a notification
item.
WHATSAPP +255738656506
______________________________________________________________
SAP System
GET_SEARCH_ATTRIBUTES
- CHECK_EXISTENCE
- GET_FUNCTIONS
- EXECUTE_FUNCTION
- GET_FIELD_ATTRIBUTES
- CHECK_CONSISTENCY
- MAP_DATA_UI_TO_DB
- MAP_DATA_DB_TO_UI
- CALL_VALUE_HELP
- MAP_RANGES
- DISPLAY
- CONSISTENT_ON_QMEL_CHANGED
- GET_CONCATENATED_KEY_UI
Requirements
You have defined an object category in the Define Object Category Customizing activity.
You have added an append structure to structure QNAOS_OBJ_DATA_UI, which contains the fields that
you want to change or display for your object category.
Standard settings
The BAdI cannot be used multiple times and is filter-dependent.

Implementations for the following object categories are available and active in the standard system:
- Batch
- Serial number
- Inspection lot
- Order
- Delivery item
Example
The implementation of the BAdI provided with the standard system can be used as a template.
______________________________________________________________
SAP AG 223
______________________________________________________________
SAP System
-
23.6.3.2.3 Assign Object Categories for a Notification Type
Use
In this Customizing activity, you assign object categories to a notification type with the quality
notification category.
This enables you to assign objects to a notification item in the notifcation applications. Multiple
assignment may also occur, such as several batches or serial numbers for one notification.
Requirements
You have defined the object category in the Define Object Categories Customizing activity.
You have implemented the properties for the object category in the Business Add-In for Implementing an
Object Category Customizing activity.
23.6.3.3 Additional Notification Functions
In this section, you define additional functions that you can call up when processing notifications.
SAP delivers some examples of these functions with the standard system; users can also add their own
functions.
23.6.3.3.1 Define Action Box
In this step, you define additional functions, known as actions, that can be performed during the
processing of a notification. You define these functions using a key and an identifier and assign them to a
notification type. The functions appear as actions in a separate screen section (action box) in the header,
when you process notifications or tasks.
You can control the structure of the action box in the following way:
- To call the function, you can define an icon with a descriptive quick info in addition to the identifier.
- You use the sort number to define the order of the functions as they are to appear in the action box.
- In addition to the notification type, you can enter a scenario. If you do this, the function only appears
in the action box if this scenario is also assigned to the notification.
______________________________________________________________
SAP AG 224
______________________________________________________________
SAP System
You define the transactions in which the function is to appear in the action box by choosing an
activity type.
- The usage defines whether the function is available at notification level or at task level.
You can control the execution of the function in the following way:
- You can document the processing of the function using a task or activity for the notification or
notification item.
Note: When you display the notification, the system only offers the functions that were defined with
the attribute "No documentation". The assigned function module cannot make any changes to the
notification.
- You can enter a user-defined function module for each function. This module is processed when the
function is called. You can also program a dialog box to be used with this function module.
- If you link a business transaction to the function, it will only be triggered if the respective status of
the transaction in the quality notification allows this. (The system checks the user authorization for
this transaction.)
- If the function is generated for a task, there are two statuses for this task: either released or
completed. Additionally, you can define a workflow task that is activated when the notification is
saved. You can also enter a function module that changes the workflow container when the
notification is saved.
For each function, you can also define several dependent functions (dependent follow-up functions). The
system offers these dependent follow-up functions for selection in the action box after the higher-level
function has been executed. In this way, you can ensure adherence to certain sequences during
processing. For more information about setting up these sequences, see the documentation for the
function module QM07_MERGE_ACTIONBOX.
Standard settings
To simplify the programming of your own function modules, the standard system contains non-
operational examples for tasks, activities, and change workflow containers. You can choose the interface
that supports your own function modules from these examples.
The standard system contains various sample functions that you can use as sources and copy templates for
your own definitions. You can find the relevant function modules using the following generic entries:
- QM06_FA* Function modules for activities

- QM06_FM* Function modules for tasks
The data relating to these examples (table settings and corresponding catalog entries) is contained in
client 000 in the standard system and must be transferred to the current client if required.
Recommendation
Note that with each release, there may be additional useful examples contained in the standard system.
Transfer these examples if required into the current client.
______________________________________________________________
SAP AG 225
______________________________________________________________
SAP System
-
Activities
1. Determine which recurring functions you can define, dependent on the notification type.
2. Define these functions. Perform any programming necessary for the function modules you require.
Proceed as follows:
a) Assign the function to the notification type. On the detail screen:
b) Define the key and description for the function.
If a function can be used for an item, you can make this clear in the description.
c) Define the controls for the function.

d) Enter a function module with the required flow logic (optional).
e) Define icon and quick info.
In the quick info, you can also indicate whether a function can be selected for an item.
f) Enter code group and code for the task or activity from the catalog that is assigned to the
notification type, if the function is to be documented as a task or activity. You must enter a
status for the task that is to be included in the notification.
3. Determine if tasks are to be supplemented by a workflow and define the workflow tasks as required.
If the assigned function module has a container for the workflow task, the container must also have
an entry.
4. Determine whether the functions are to be triggered in a particular sequence and if so, define the
dependent follow-up functions.
Further notes
In the notification header, only those functions appear for which the user has authorization. Tip: For tasks
and activities, use the authorization for use of certain code groups.
23.6.3.3.2 Define Follow-Up Actions for Tasks
In this step, you can define follow-up actions for tasks.

You can define a series of follow-up actions that the system will carry out sequentially.
For each follow-up action, you must define:
the level at which the follow-up action will be effective

(Only the task level is relevant.) You
can also define:
______________________________________________________________
SAP AG 226
______________________________________________________________
SAP System
- how the update will be processed

- when the follow-up action will be triggered; that is, with which business transaction will the follow-
up action be carried out.
(The system will check whether the user has authorization for this transaction.)
Requirements
The task catalog must be set up to allow the assignment of follow-up actions.
The task catalog should be maintained to such an extent that you should only have to supplement the task
codes with the names of the follow-up actions, once you complete this step.
Standard settings
To make it easier for users to program their own follow-up actions, the standard system contains a non-
executable example of a function module for follow-up actions. You can copy the interface in this
example and use it in your own function modules.
Recommendation
- Provide a detailed description of the follow-up actions for a task in the long text for the task code.
Make a distinction between follow-up actions that:
- must be carried out manually by a partner
- are carried out automatically by the system
- Do not change the function modules that have been provided as examples. Instead, make copies of
these function modules and save them under different names.
Activities
1. Determine which follow-up actions for tasks are needed in your company and which should be
automated.
2. For automatic follow-up actions, define:
a) the series of function modules and their update form
b) the business transactions for the follow-up actions (provided the function module is to be
linked to the status management function for the task)
3. Maintain the table of follow-up actions.
4. Create the corresponding function modules.
Further notes
- The system allows you to implement automatic follow-up actions in the form of function
modules. If a follow-up action consists of a series of individual actions, these actions must be
numbered in the sequence they are to be carried out and each action must be linked to a
function module.
______________________________________________________________
SAP AG 227
______________________________________________________________
SAP System
-
- If you want to assign a business transaction from the general status management function to a
follow-up action, the transaction must be supported for the object type "Task for Quality
Notification." The F4-help for the "Transaction" field shows you which transactions you can
use.
Business transactions are pertinent to the status management of tasks. Refer to the chapter Basic
settings, Central functions, Status management for additional information. Also refer to the item
Status profile for notification type.
To be able to select an appropriate transaction for a follow-up action, you can display the definitions
of the business transactions for follow-up actions for tasks. You cannot, however, change these
definitions yourself. To select a transaction, proceed as follows:
- Display the list of business transactions. Select the transactions used for notification tasks by
entering 'QN9*'; then select the desired transaction.
- Select the 'Where-used list' function (not the 'Follow-up action' function). In the resulting
display, you can see:
- that this transaction supports the object type 'task'
- which task status this transaction sets and deletes
- which statuses influence this transaction
- The follow-up actions for tasks use the same techniques as the follow-up actions for the usage
decision.
23.6.3.4 Print Control
In this section, you define the print control for the notification shop papers. In particular, you specify:
- The type and format of the shop papers

- Where the shop papers are to be printed
- The archiving mode (provided an archiving link is active)
23.6.3.4.1 Define Shop Papers, Forms, Print Programs
In this step, you specify:
- Which shop papers will be printed and archived

- The form in which these shop papers will be printed and archived
Which shop papers will be printed for which notification types
Default Settings
______________________________________________________________
SAP AG 228
______________________________________________________________
SAP System
The standard system contains several predefined examples that you should not change.
Recommendation
- When you assign the shop papers to the notification types and select a printer, you can call up the
shop papers generically. For this reason, define a nomenclature for the shop papers that supports
generic selections.
- If you want to create reports and layout sets for your own shop papers, you must be familiar with
SAPscript techniques and possess ABAP/4 programming skills.
Activities
1. Determine which shop papers are needed for the notifications.

a) Determine whether you need shop papers other than the ones already provided in the standard
system.
b) If necessary, have a qualified person create the ABAP reports and SAPscript layout sets for
these shop papers.
c) Define these shop papers in the table.
2. For each document type (notification type), specify which shop papers are available for printout and
whether these shop papers should be displayed with a selection indicator. Notes:
- The user can change the selection indicator manually when printing the shop papers.
- The document type and the shop paper can be selected generically.
Further notes
The same print control is also used for other applications in the SAP system. The notifications are
permanently assigned to the application area "N".
For reasons of general use, the term document type is used in place of the term "notification type" in this
particular case.
23.6.3.4.2 Define Printer
In this step, you set the parameters for the print control.
The print control allows you to individually define the output devices and print parameters for each user
and shop paper.
Using a table-controlled printer rerouting, you can also define special printers and print parameters for the
individual shop papers, based on the contents of certain fields.
Activities
______________________________________________________________
SAP AG 229
______________________________________________________________
SAP System
-
1. Define a printer and the corresponding print parameters for the individual users and shop papers.
Note that generic entries are possible.
2. Determine whether the printout of individual shop papers should be rerouted based on the contents
of certain objects and fields.
a) Define these objects and fields. Use the objects and fields proposed by SAP and activate them
for the printer rerouting, as necessary.
b) For each active printer rerouting, define the appropriate contents of the controlling fields and
the special print parameters. The entries for the controlling fields can be generic.
23.6.3.4.3 Define Download
In this step, you define how the quality notification data will be downloaded to subsystems.
- Define the addresses for the download:

- Specify the subsystem TCP/IP addresses for the Remote Function Call (RFC).
- Define the names of the files in which the transmitted data will be stored.
- Define the structures of the data that will be downloaded to the subsystem.
Activities
1. Define the subsystem addresses and the file names in the subsystem.
You will need two RFC destinations (TCP/IP connections for the front-end workstation) to:
a) create the tables of SAP DDIC structures in an MS-ACCESS database (program path to
Wdpsastr.exe).
b) copy the SAP tables to MS-ACCESS (program path to Wdpsatab.exe). You can find these
programs in the Windows GUI via the path \ps\access\. For proper operation, you will also
need the remaining programs contained in this directory (for example, VBRUN300.DLL, etc.).
The system must also be able to access the RFC-DLL files (librfc2.dll, librfc3.dll, librfc4.dll,
librfc5.dll, librfc6.dll, vrfc.dll); specify a corresponding PATH command.
2. Define the data structures to be transferred to the subsystem. Use the names of the system tables in
which the data in the SAP system will be prepared for downloading. Refer to the documentation for
the downloading program RIACCESS to obtain the names of the SAP tables.
a) First create the necessary download structures. Specify the RFC destination defined in step 1a).
b) Define the download RFC destination and the PC database. Specify the RFC destination
defined in step 1b) and the path for the database you created. Application
______________________________________________________________
SAP AG 230
______________________________________________________________
SAP System
code 'N' applies to the quality notifications.
23.6.3.5 Status Management
This section describes how to use the general status management function for notifications.
For a detailed description of the general status management function, refer to the section Environment ->
Central Functions -> Status Management.
23.6.3.5.1 Define Status Profile
In this step, you define the status management function for the notifications.
Notifications use the general status management function for SAP objects. A brief explanation of this
concept is provided at the end of this text. For a detailed description of the status management function
and related technical information, refer to the chapter "Basic Settings and Environment" in the section
Status Profile.
Using the general status management function, you can also define your own status profiles to
supplement the predefined system statuses. You can use these status profiles to control the sequence of
certain transactions. Examples of such transactions are:
- Releasing a task
- Completing a notification
For each notification type, you can define different status profiles for:
- The notification header

- A task
Activities
1. Determine whether additional user statuses are required for certain notification types.
2. Define the status profiles for the notifications. For each notification type, you can define appropriate
status profiles for the following object types:
a) Notification header
b) Task
3. Choose the appropriate status profiles for each notification type.
In the SAP system, a distinction is made between a system status and a user status.
- System Status
The SAP system contains a collection of statuses that apply to and can be used by all applications.
These statuses cannot be changed.
- Business Transaction
______________________________________________________________
SAP AG 231
______________________________________________________________
SAP System
The SAP system contains all business transactions that apply to and can be used by all applications.
These business transactions cannot be changed.
- Business Transaction / System Status

A system status is assigned to each business transaction. A determination is also made whether the
corresponding system status is to be deleted or set when the transaction is carried out.
- Objects / Business Transaction

In addition, which business transactions can be used with which SAP objects is also defined. This
definition specifies the maximum number of system statuses allowed for an object and which
statuses can be set for individual transactions.
- Status Profile
You can define your own status profiles. You must assign at least one object to each status profile.
Each status profile contains one or more allowed statuses. Within the scope of the business
transactions predefined by SAP, you can specify how the system will behave for each of these
statuses. In the status profile, you define:
- Your own statuses (user statuses) and document their functions in a corresponding long text
The user status allows you to refine the sequence of system statuses predefined by SAP to
your own requirements. However, this is only possible within the fixed profile defined by
SAP; you cannot override the system status with the user status.
- The status order numbers for user statuses which determine the possible sequence of user statuses
- An initial status that is automatically activated when you create the object
- Which user status is automatically activated when you execute a business transaction
- Which transactions are allowed or not allowed when a certain status is active
- Status Order Number
You can define a status order number for each user status. With the help of the status order number,
you determine the sequence in which the user statuses can be activated. If you do not assign a status
order number to a user status, this user status can always be set. However, only one user status with
status order number may be active at one time. If you assign a status order number to a user status,
you must also specify a lowest and a highest status order number for this status. These numbers
limit the order number interval from which the next user status can be chosen.
- Changeability of the User Status

You can use the Business Add-In for Control of Changeability of the User Status to determine for
each notification type whether or not a particular user status can be changed.
When you maintain the status profile, you can, for example, specify whether quality notifications can be
processed in this status or whether a deletion flag can be set. You can also specify whether a deletion flag
is to be set automatically and whether the system should respond with a warning message or an error
message when a deletion flag is set.
23.6.3.5.2 Define Selection Profiles
In this step, you can define selection profiles for notifications. You can use these selection profiles to find
the notifications on the basis of their statuses.
Refer to the chapter Environment, Central Functions, Status Management, Selection Profile for detailed
information about selection profiles.
Activities
______________________________________________________________
SAP AG 232
______________________________________________________________
SAP System
1. Determine which system statuses (and user statuses, if necessary) the notifications will have. Make
sure the status profiles for user statuses are different from one notification type to another.
2. Determine how these statuses can be linked in a logical fashion, to produce useful selection profiles;
then define the selection profiles.
23.6.3.6 List Definition
In this work step, you define list variants to process quality notifications.
These varaints differentiate between single-level andn multi-level lists.
23.6.3.6.1 Define Variants for Single-Level Lists
In this step, you define the list variants for displaying single-level lists of notification worklists.
Variants are defined using a list view function. The procedures for this function are described in the
section Basis Settings, Tools, List Definition.
23.6.3.6.2 Choose Fields for Multilevel Lists
- Use
In this step, you choose the fields for multi-level selection lists. The procedure is similar to the one
described for single-level lists.
Multi-level lists are available for the following objects and sub-objects:
- Partner
- Notification item
- Activity
- Task
- Cause
- zugeordnete Objekte
Multi-level lists can contain more information than single-level lists. From the multi-level lists, however,
you cannot go to the display or processing screens for the objects.
23.6.3.7 Digital Signature
23.6.3.7.1 Specify Digital Signature
Use
______________________________________________________________
SAP AG 233
______________________________________________________________
SAP System
In this process step, you can activate the digital signature call for each notification type and business
transaction.
Requirements
You defined data for the signature strategy. Execute the following process steps for this data:
- Define Authorization Groups

- Define Individual Signatures
- Define Signature Strategies
23.6.3.7.2 Define Signature Remarks
Use
In this Customizing activity, you can define different signature remarks for each step of the signature
process, which the user can select from a list in the digital signature dialog box.
Requirements
You have made the required settings for the digital signature (see Specify Digital Signature).
Standard settings
The SAP standard system does not provide any entries for the signature remarks table.
Activities
Execute the following steps:
1. For each required combination of application, signature object, and status of signature process,
define one or more signature remarks. If necessary, use the predefined placeholders to include
context information into the signature remark.
2. Indicate which signature remark is to be displayed as the default value.
Further notes
If you want to allow the remark to be changed during the current signature process, set the relevant
indicator:
- For inspection lot processing: in the Customizing activity Define Authorization Groups and
Digital Signature, activity option Material Authorization Groups, Inspection Lot Approval,
Digital Signature
- For the processing of quality notifications: in the Customizing activity Specify Digital Signature
______________________________________________________________
SAP AG 234
______________________________________________________________
SAP System
23.6.3.8 Activate Workflow Template
In this step, you activate the Workflow template that is to run when notifications are processed.
Further notes
For more information about activating the Workflow, see the Environment / Central Functions section
23.6.3.9 Define Costing Parameters
In this step, you define a number of parameters for the order type that the system uses to create a QM
order.
You can also define a costing variant to plan costs for individual notifications. For more information, see
the step costing variant in the Implementation Guide for general notifications.
You can create a QM order directly from a notification, to record and settle the costs that are incurred
while processing the notification, or assign an existing QM order. You must set the order parameters for
each notification type and plant. If a business area requirement exists for a plant, you can also define a
default value for the business area to which the QM order is assigned.
Requirements
The Controlling (CO) module is active in the system.
Recommendation
Obtain advice from your CO consultant.
Activities
1. First read the instructions in the section Environment -> Central Functions -> QM Order Types.
Make sure the required order types are available and the settings for the costing parameters have
been made.
2. For each notification type and plant, assign the following parameters:
a) Order type for the QM order
(The system only proposes order types from order category 06.)
b) Business area (if required)

c) Settlement rule proposal for the QM order
You can select the following objects for the settlement rule:
- Order number (for example, CO order)
- Cost center
______________________________________________________________
SAP AG 235
______________________________________________________________
SAP System
- Sales order
3. Check the settlement of the nonconformity costs by processing a quality notification and recording
costs for the notification.
Further notes
The QM order is assigned to the notification header. You use the QM order to record defect costs and the
Controlling component can evaluate these costs.
In addition, you can also independently record a quantitative defect valuation for each notification item.
See the documentation for the step confirmation profile in the defects recording section. The Quality
Management component uses this defect valuation to weight defect types and evaluate them in the QM
Information System.
23.6.4 Defects Recording
In this section, you make the necessary preparations to record defects for the inspection lot.
Contents of Defect Records
Defect records contain coded and textual information on the defect type, defect location, defect cause,
activity, defect valuation. You define which information is to be contained in the defect record in a
confirmation profile.
Creation of Defect Records
As long as no usage decision has been made for the inspection lot, defect records can be created with the
following transactions:
- Results recording for the inspection characteristic

- Manual creation of defect records
- Automatic creation of defect records
- Usage decision for the inspection lot
- Defects recording for the inspection lot
Assignment of Defect Records
You can assign defect records to the inspection lot at the following levels:
a) Inspection lot
You must always make this assignment.
b) Operation
This assignment is not mandatory. You make it manually when recording defects for the
inspection lot.
c) Inspection characteristic
This assignment is not mandatory. You make it manually, or it takes place automatically,
when defect records are created at results recording. Note: If you record inspection results for
independent multiple samples, inspection points, physical samples, or equipment and if defect
records are created automatically in the case of a rejected characteristic, the system generates
an additional defect record with the assignment inspection lot/operation/sample (or inspection
point, physical sample, equipment.
______________________________________________________________
SAP AG 236
______________________________________________________________
SAP System
Automatic Creation of Defect Records
If you set the control indicator Autom. defects recording in the inspection characteristic, and enter a
defect code from catalog 9 in the catalog data, the system generates a defect record with this defect type,
if the inspection characteristic is rejected. The characteristic can be rejected for the following reasons:
- General rejection of a characteristic

- Rejection caused by a tolerance violation
- Of the upper specification limit
- Of the lower specification limit
Note: The defect record is generated as a result of a valuation rule. This rule determines whether a defect
record is to be created and if so, which code is to be used for the record. Since the valuation rules are
stored as function modules in Customizing, you can adapt the way defect records are generated and their
contents without having to make a program change. Example: If you record results for samples,
inspection points, etc., the system creates a defect record with the assignment inspection
lot/operation/inspection characteristic, each time an inspection characteristic is refected. In addition, the
standard system creates an additional defect record for the inspection lot/operation/sample (or inspection
point, physical sample, equipment). This is, however, not always advisable. To ensure that this additional
defect record is not created, you can store your own valuation module (or change an existing one) in
Customizing.
Customizing Settings
From a technical standpoint, defects recording for the inspection lot is a quick way of recording quality
notification items using recording lists. Defects that have been recorded can be processed as quality
notifications.
Note: A quality notification that is created while recording defects for an inspection lot receives
the status 'Defects recording'; when you make the usage decision for the inspection lot, it
automatically receives the status 'Completed.' You can delete the status 'Defects recording ' and
still process the notification once the usage decision has been made, provided that you select the
function 'Activate quality notification' while processing the inspection lot or change the
notification using a processing function.
For this reason, you must first define the quality notification types that form the basis for defects
recording.
Defects are confirmed during inspections and recorded for specific inspection lots. You must therefore
assign a suitable quality notification type to each inspection type, for which defects are to be recorded.
Note: You use the inspection type to make sure that only one quality notification is created, even if defect
records have been created for several operations
Depending on the source of the defect data, and how you want to use it, you may need different
structures for the defect records. You therefore need to define corresponding confirmation profiles.
Finally, you may want to group the defect data on the basis of other criteria, and not just on the basis of
the notification type that is assigned to the inspection type. For this purpose, you must define
corresponding report types for these criteria.
23.6.4.1 Define Notification Type
In this step, you process the quality notification types that will be used with the defects recording
function.
______________________________________________________________
SAP AG 237
______________________________________________________________
SAP System
The chapter Notification Creation describes how to define the notification types. This chapter also
contains detailed instructions on how to make the settings for all of the notification type-dependent
controls.
In the section 'Notification Types' (chapter Defects Recording), carry out the following steps:
- Check the settings of the notification types to be used for defects recording. These include:
- The defined notification types themselves and the screen templates that belong to them
- The content of the notification types (catalogs and catalog profiles) - Complete the settings
associated with the notification type:
- In the catalog profile, define the unit of measurement to permit the defects to be valuated
quantitatively.
- Assign a quality notification type to the inspection type.
Requirements
You have processed the section 'Notifications':
- You have defined the notification types, catalogs and catalog profiles to be used for defects
recording.
- You have maintained all settings that are dependent on the notification type.
- You do not need to maintain partners to use the defects recording function.
Standard settings
Notification types suitable for different inspection lot origins and inspection types have already been set
up in the standard system.
Recommendation Copy the notification types that are contained in the system.
- If you define your own notification types, use the settings contained in the standard system as a
reference.
- Use separate notification types for defects recording and for other types of quality notifications, so
you can distinguish the defect data from the other problem data on the basis of the notification type.
Activities
1. Check the notification types that will be used for defects recording.
a) Identify the notification types that will be used for defects recording
b) Check the catalogs and catalog profiles as well as their assignment to the notification type.
c) Check the screen settings for these notificaton types.
2. if you want to use a defect valuation, you can assign units of measurement to the appropriate
catalog profiles.
3. Assign an appropriate notification type to all inspection types with which you intend to record
defects.
Further notes
______________________________________________________________
SAP AG 238
______________________________________________________________
SAP System
- You can valuate defects quantitatively if you activate the defect valuation function in the
confirmation profile. You can specify a unit of measurement for the defect valuation and propose it
in the catalog profile. The unit of measurement must have been previously defined. For more
information, refer to the step units of measurement in the section Environment.
- When you assign notification types to the inspection types, the definition of the screens
(subscreens) for the notification type is important. These screens must be compatible with the
inspection lot origin to which the inspection type in question is assigned.
23.6.4.2 Define Confirmation Profile
In this step, you define confirmation profiles for defects recording.

In the confirmation profile, you specify which fields are to appear on the screens when you record
defects and whether the user must enter data in these fields. The confirmation profile essentially mirrors
the various recording forms used by the inspectors in the work centers.
With the help of the fields in the confirmation profile, you can include a variety of defect data in the
defect record (for example, defect type and defect cause). You can:
- Individually pinpoint the defects and assign them to inspected single units
- Document the activities needed to correct the defects
- Valuate the defects quantitatively
- Identify systematic defects
Example
- If you only copy the defect type and number of defects fields into the confirmation profile, you are
defining a summarized form of defects recording.
- If you select the defect type and defect location, you can explicitly identify the individual defects.
- If you select the defect type, defect location and serial number, you can record defects individually
for a single unit.
The serial number field contained in the confirmation profile is primarily controlled by the material;
that is, it becomes effective only if serial numbers are maintained in the inspection setup for the
material. In such a case, the confirmation profile determines whether a serial number entry is
mandatory or optional when you record defects.
- By recording additional defect criteria (defect cause and defect valuation), you will complete the
confirmation profile.
In doing so, you will provide the basis for carrying out Pareto analyses for the defect types and
defect causes (in terms of frequency and importance).
- You can also mark the defects that are systematic, in order to keep them separate for evaluation
purposes.
Recommendation
Define the confirmation profiles after you have defined the report categories. It may be advisable to
define a separate confirmation profile for each report category.
Activities
______________________________________________________________
SAP AG 239
______________________________________________________________
SAP System
1. Determine which report categories are required in your company and what information should be
contained in the defect records that will be created on the basis of these report categories.
(The fields in the confirmation profile must be compatible with the catalog profile).
2. Define the corresponding confirmation profiles.
Further notes
In the report type, you link the confirmation profile to the catalog profile.
23.6.4.3 Define Report Type
In this step, you define the report types for defects recording.
The report type restricts the size and contents of the defect data records. In the report type, you link a
confirmation profile to a catalog profile. You use the confirmation profile to define the catalogs and
defects for defects recording and the catalog profile to define code groups.
Since the notification type is defined using the inspection type, you need the report type to make finer
distinctions between defect data. You can define report types for different purposes and according to
various criteria, to suit your requirements. We recommend the following:
Recommendation
- Defects Recording
Usually, each department that records defects needs its own recording forms. For example, the
department that carries out visual inspections can only make a note of the defect type and defect
location, while a department that makes defect analyses and carries out repairs also records the
defect cause, the defect valuation and activities. You can use the report type to provide each
recording center with the appropriate form for recording defects. You can assign specific report
types to work centers or users. In addition, you can stipulate a suitable report type for each center
in an internal memo.
- Defect Analysis
The definition of the report type depends on the evaluations that are needed for the defect data,
since the report type is a criterion (like the notification type) for summarizing and analyzing defect
data in the QM Information System. The report type provides another option for differentiating
defect data for evaluation purposes.
Activities
1. Determine which criteria is to be used to define the report categories and which report categories
are needed. Define the report categories by assigning a catalog profile and a confirmation profile to
each report category; this permits the report category to be determined automatically.
2. If you define report categories on the basis of the inspecting work center, and if you use inspection
plans containing specified work centers, you can assign the report categories to the respective work
centers.
The table allows generic entries in the plant and work center fields. Note: Also define a report
category for plant '*' and work center '*', so that the system can find a valid report type when defect
data is created automatically.
3. Determine whether you want:
______________________________________________________________
SAP AG 240
______________________________________________________________
SAP System
a) The system to propose report categories in the user master record (User parameter QFE =
report type key)
b) The user to be able to change a report type that is automatically found by the system (User
parameter QF1 = X)
If necessary, set the user parameters accordingly.
4. Determine whether inspection results are to be transferred from subsystems and if defect records are
to be generated automatically if characteristic results are rejected. If necessary, you must uniquely
specify a report type for the relevant work center.
Further notes for Finding the Report Type
You can assign a report type to the work center master record and define a report type in the user master
record. When a defect record is created, the system searches for the report type in the following
sequence:
a) Work Center
Note: Generic entries for the work center are allowed in the assignment of report types to
work centers. When you record defects for an operation or inspection characteristic, the
system automatically selects the most suitable report type that has been assigned. If this
assignment is not clear, and the system cannot find a report type the user must choose one of
the report types.
If the control key for the inspection characteristic stipulates that defect records are to be
generated automatically, but there is no work center entered in the operation, the system
chooses the report type that is stored under plant '*' and work center '*'.
b) User Master Record

Note: To store a report type in the user master, use the user parameter 'QFE' and assign the
appropriate report type to this parameter as a value.
When users record defects manually in the results recording function or make the usage decision, if you
want to allow them to choose a report type other than the one found by the system, use the user
parameter 'QF1' and assign the value 'X' to it.
You can use transaction 'QF01' to choose any report type when recording defects for the inspection lot,
without having to set the user parameter QF1.
However, if report types have been defined for the work center, the system only allows you to select one
of these types when recording defects for the operation or inspection characteristic manually.
Further notes for Finding the Catalog Profile
You can define a catalog profile in the following objects:
a) Material master record (or master record for equipment or functional location)
b) Notification type
c) Report type
In the report type, you can define the object from which the catalog profile is to be taken. The system
then searches for a catalog profile in the sequence already mentioned, provided that the material and
notification type fields have been checked in the report type and an entry has been made in the catalog
profile field. If the system cannot determine a catalog profile, it issues an error message when a defect
record is created.
Note: In contrast, you can create a quality notification without having assigned a catalog profile
to the notification type. In such a case, there are only text fields and no catalog fields for the
______________________________________________________________
SAP AG 241
______________________________________________________________
SAP System
individual notification elements (such as, subject, defect type, defect location, defect cause,
activity).
Further notes for Dependent Characteristic Specifications
In the inspection characteristic, if you define code groups or selected sets from catalogs that are
contained in the notification type assigned to the report type, these code groups and sets provide the
values when you record defects for the inspection characteristic. Although the code groups in the catalog
profile are not taken into account, the confirmation profile still applies.
23.6.5 Information System
In this section you define:
- The update of information from quality notifications to the QM information system

- The creation of key figures relating to the frequency of quality notifications The data is
displayed when processing quality notifications and can come from:
- Original documents
- The QM information system
23.6.5.1 Define Update in QM Information System
In this step, you define the function for updating the quality notifications in the QM Information System
by defining an appropriate update group for each quality notification type.
Standard settings
Suitable update groups have already been defined in the standard system for all applicable quality
notification types.
Activities
1. Determine whether the SAP-defined assignments of update groups to quality notification types meet
your requirements.
2. Adapt the table, if necessary.
Further notes
The update group is used to update the different types of business transactions in the statistics.
The update rules for the key figures of an information structure are always described in reference to an
update group.
If a quality notification type is not assigned an update group, data is not updated in the information
system for the affected quality notifications.
You can record a user-specific update log to monitor the update function.
______________________________________________________________
SAP AG 242
______________________________________________________________
SAP System
23.6.5.2 Activate Reference to Related Notifications
In this step you specify for each notification whether a reference should be made to existing Q-
notifications for the same material, customer, vendor and manufacturer and if so, how this is to be done.
You determine how the absolute frequency of the Q-notifications should be determined according to the
following:
- Criteria
The criteria depend on the notification origin. The frequency of customer complaints can be
determined for example according to materials, customers, or to a combination of material and
customer.
- Data source
The following data sources are available:
- The original data for the Q-notification

- The compressed data in the QM information system
- The time-frame in the past
The related notifications are displayed by the system in the notification header when the
notification is processed, if the absolute frequency that is determined according to the given criteria is
greater than zero.
Requirements
If you want to use the QM Information System as the data source, you must have specified an update for
the relevant notification type.
Recommendation
Make sure you are aware of all the function options, by reading the F1 online documentation on the table
fields contained in the view.
Activities
Decide whether you require key figures to be displayed for the frequency of the notification when the
notifications are processed. If necessary, maintain suitable criteria for data compression, the data source,
and the screen display control for each notification type.
Further notes
The area on the screen containing the reference to related quality notifications is only displayed, if it has
been defined in the Define screen template section for the notification type.
The reference to related notifications is displayed when results are recorded and when the usage decision
is made for the inspection lot, if such notifications exist.
Even a notification that is being processed is included in the evaluation of related notifications.
______________________________________________________________
SAP AG 243
______________________________________________________________
SAP System
23.6.5.3 Define Nonconformity Costs for Supplier Evaluation
In this step, you define an estimated amount for any work performed that relates to the nonconformity of
goods (nonconformity costs, costs incurred as a consequence of defects), as a result of a quality
notification.
If the buyer makes a vendor evaluation, the system gives the subcriteria quality/complaint a quality score
that is calculated as follows: If no quality notifications exist, the vendor receives the highest possible
quality score. This score decreases directly in proportion to the number of quality notifications for a
given period, until the lowest quality score is reached. The proportional factor is the ratio of the average
damage determined by the user (as a result of one complaint) to the weighted value of all deliveries
within the given period. The value of the deliveries (value of vendor's sales) is weighted using a
percentage share of business volume.
The system takes into account all quality notifications with origin Q2 (complaint against vendor) that
have the status "Caused externally" and "Completed".
Quality as a Criterion in the Vendor Evaluation
The main criterion quality contains the automatically valuated subcriteria - goods receipt, audit and
complaints.
- Goods Receipt (GR)

The goods receipt score is calculated from the quality score (QSc) for the inspection lots, according
to the following formula:
QSc = (S1 + S2) / (n1 + n2)
S1 = Sum of quality scores for the inspection lots n1 = Number of inspection lots n2 =
Number of deliveries for materials with a quality information record, for which no inspection
lots exist.
S2 = n2 * QScmax
You can break down the GR score for the vendor according to the material and the inspection
type.
- Audit:
The audit score is either the average quality score for the audits or is made up of the quality scores
for the most recent audits. You can also enter an audit score manually.
- Complaints:
The complaints score is calculated from the number of complaints against the vendor, according to
the following formula:
QSc = QScmin + (QScmax - QScmin) * (1 - (N * K) / (F * U))
QSc = QScmin if (N * K) > (F * U)
QScmin = Lower limit for QSc

QKZmax = Upper limit for QSc
N = Number of Q-notifications in the applicability period
K = Estimated nonconformity costs
F = Share of business volume for QSc calculation
U = Sales of the vendor in the applicability period
______________________________________________________________
SAP AG 244
______________________________________________________________
SAP System
Requirements
- The range of values for for the quality scores was defined in Basic Settings/ Settings at Client
Level.
- The reference period and the business volume factor were defined in the Purchasing Organization
Data for Vendor Evaluation.
Activities
If you use the vendor evaluation in the MM component and want to use the estimated complaints
valuation to contribute to the criterion "Quality", define a currency value (number and unit) for the
estimated nonconformity costs for each notification type.
Further notes
The denominator of the proportional factor mentioned above contains the weighted value of deliveries to
the relevant purchasing organization in the reference period.
If this value is high, the quality score remains at its maximum level and the influence of the complaints
on the quality score (whole number) only becomes apparent if there is a large number of corresponding
quality notifications.
If this value is less than the estimated damage as a result of a quality notification, the quality score is
reduced to its lowest level based on the existence of one quality notification.
23.6.6 Using Notifications
This section explains the procedure and the system settings required to implement processes that result
from, or include a quality notification.
23.6.6.1 Process Return Delivery to Vendor
In this step, you make the settings required to process returns that arise from complaints against a vendor.
Several partial processes for returns are triggered from a quality notification. These include:
- Stock transfer postings

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

The material type must be set so that both purchasing and sales an distribution data can be
maintained, if the shipping of returned goods to the vendor is to be supported. To do this, you must
define a transportation group and a loading group in the general sales and distribution data.
Inspection type 08 must be active in the inspection setup, so that an inspection lot is created, when
the stock is transfer posted to inspection stock.
- Vendor Master Record

A vendor master record with an account group as well as a customer master record must exist for
the vendors.
If you set the Returns with shipping processing indicator in the purchasing data for the vendor, the
system requests the data for the vendor relating to the customer. This data must have been created
with an account group for the sold-to party (or must be created if no data exists). The shipping data
(for example, the shipping condition in the sales data area for the customer master record must be
maintained. If you want to use the ERS procedure for vendors, you can activate the automatic
goods receipt settlement for returns. Note: If the control indicators are not ready for input, when
you maintain the master record, you must modify the screen control for the vendor account group.
- Purchasing Info Record

If the system can access a purchasing info record for the supply relationship, it proposes the
appropriate price and terms of payment, even if there is no reference to an original document.
- Release Procedure
If you define a release procedure for purchasing you must make sure that the order type return
delivery is not included in the release procedure, when defining the release strategy, so that the
system can create the return delivery automatically.
Standard settings
The standard system contains all the required quality notification functions. These include:
- Tasks
These are contained in catalog 2, in code group QM-G2.
- Default tasks for the action box with their related function modules. The following functions
are delivered with the standard system:
- Transfer posting from unrestricted-use stock to blocked stock
______________________________________________________________
SAP AG 246
______________________________________________________________
SAP System
- Transfer posting from unrestricted-use stock to inspection stock
- Making the usage decision
- Assigning the purchasing document
- Creating a return delivery
- Changing the outbound delivery
- Follow-up actions (and their related function modules) The standard system contains the
following follow-up actions:
- Making the usage decision (UD)
- Creating the outbound delivery (DELIVERY)
- Changing the outbound delivery VL02
Recommendation
Copy the standard settings from client 000 into the current client.
If you want to define your own code groups and codes in the task catalog with names, based on the
examples contained in the standard system, you must also modify the corresponding follow-up actions.
Use the recommendation for implementing the IMG (hypertext link in the IMG structure) in place of
displaying the IMG text in the SAPscript editor, using the screen display function).
Activities
Check the following Customizing settings:
1. The GR reversal despite invoice at GR related invoice verification must be allowed for the
movement types that are used for the return delivery:
- 161 return delivery without reference to the original document
- 122 return delivery with reference to the original document
2. At partner determination for the delivery, the partner determination procedure RLL (return delivery
to vendor should be assigned to the delivery types RL (return to vendor - return delivery with
reference to purchase order) and RLL (return to vendor without reference to purchase order)
Note: You can find the assignment of the partner determination procedures to the delivery
types in the function for maintaining the partner determination procedure for the partner object
"delivery".
3. Since the plant that receives the returned goods from a delivery subsequently becomes the issuing
plant, a sales area (sales organization, distribution channel and division) must be assigned to this
plant.
4. The shipping point must be set for the shipping condition that is used, the loading group and the
plant.
Further notes
You can find more information about this subject in the note database under note 113844.
______________________________________________________________
SAP AG 247
______________________________________________________________
SAP System
23.6.6.2 Process Customer Repair Order
In this step, you make the required settings to process returns and repairs of materials that have to be
processed as a result of customer repair orders. The following procedures are taken into account:
- Basic procedure: Repair order

This procedure forms the basis for the following complementary variants:
- Variant 1: With quality notification

- Variant 2: With quality notification and quality inspection
- Variant 3: With quality inspection
The text for this step deals with the basic procedure and the individual variants separately.
Recommendation
Use the recommendation for implementing the Customizing.
Repair Order
Requirements
The starting point for processing is a repair order from the customer. The repair order is an SD sales
document which references a serviceable material.
Variant 1: With Quality Notification

Standard settings
The following follow-up actions for tasks are defined for this variant in Customizing for notifications:
- G_MOVE: Enter goods movements

- REP_ORD: Create repair order
- REP_VE: Confirm decision in repair order
Catalog 2 (tasks) contains codes in code group QM-G1 Codes, to which these follow-up actions are
assigned.
- Code 0014: Create repair order

Follow-up action REP_ORD
- Code 0015: Enter goods movements for the repair order

Follow-up action G_MOVE
- Code 0018: Confirm decision in repair order

Follow-up action REP_VE
In Customizing for quality notifications, appropriate follow-up functions (generated tasks/activities) are
already defined for notification type Q1 for this variant.
- Function: Create repair order

- Function: Enter goods movement
- Function: Decision in repair order
______________________________________________________________
SAP AG 248
______________________________________________________________
SAP System
Recommendation
Copy the standard settings from client 000 into the current client.
If you define your own code groups and codes following the standard example, because you want your
own nomenclature, you must also adapt the corresponding follow-up function.
Further notes:
This variant does not support serial numbers.
Variant 2: With quality notification and defect determination using an

inspection lot.
Standard settings
The follow-up actions listed below are defined for this variant in Customizing for quality notifications:
- REP_ORD Create repair order/follow-up function

Catalog 2 (tasks) contains a code in code group QM-G1, to which this follow-up action is assigned.
- Code 0014: Create repair order

In Customizing for quality notifications, appropriate follow-up functions (generated tasks/activities) are
already defined for notification type Q1 for this variant.
- Function: Create repair order

Recommendation
Copy the standard settings from client 000.

If you define your own code groups and codes following the standard example, because you want your
own nomenclature, you must also adapt the corresponding follow-up function.
Activities
In Customizing for an inspection for a goods movement, inspection lot creation is not active for the
following goods movements and must be activated:
MvT SpecStck MvTId Cons. MvType Text
653 E L E WL Returns unrestricted use
653 E L P WL Returns unrestricted use
653 E L V WL Returns unrestricted use
Variant 3: Without notification, with defect determination using inspection lot

Activities
In Customizing for an inspection for a goods movement, inspection lot creation is not active for the
following goods movements and must be activated:
MvT SpecStck MvTId Cons. MvType Text
653 E L E WL Returns unrestricted use

______________________________________________________________
SAP AG 249
______________________________________________________________
SAP System
653 E L P WL Returns unrestricted use
653 E L V WL Returns unrestricted use
23.7 Quality Control

This section describes the procedure for defining settings for quality control using the QM component.
Note
Take note of the connection to the step Archiving in the section Basic Settings and Environment ->
Central Functions
Evaluations of the following transaction data form an integral part of quality control:
- Original datasets, for example for inspection lots and Q-notifications - Compressed data in
the QM information system.
Once the datasets have been archived, evaluations can only be performed from the archive. Special tasks,
however, are required for this purpose and certain data accesses are no longer automatically possible.
Important transaction data, therefore, is transferred to the QM Information System (part of the Logistics
Information System LIS) in compressed form before it is archived.
Recommendation
You should
- Define standard time periods for the evaluations and archiving

- Archive transaction data immediately upon completion of all evaluations for the previous time
interval and if no more accesses to original data are required
Actions
1. Specify the time period for evaluations for the Logistics Information System (LIS). Read the
chapter Information System.
2. Determine for how long the original transaction data must be kept:
- For examinations based on the regular evaluations of the information system
- For validations of the inspections and inspection results (for example, in form of certificates)
- For examining Q-notifications
Refer to the chapter Archiving for further details.
3. Organize the processes in your company in such a way that the datasets are reorganized upon
completion of all of the evaluations.
4. Organize the accesses to archived datasets.
______________________________________________________________
SAP AG 250
______________________________________________________________
SAP System
23.7.1 Quality Management Information System
In this section you can make settings for data processing in the Logistics Information System (LIS).
These settings are part of the LIS settings. You can find additional information in the Implementation
Guide section on the Logistics Information System Logistics Data Warehouse. More details are in the
sections
- Update Control
- Data basis, Tools Set Up
The QM component provides the LIS with data from quality inspections and quality notifications.
- Quality Inspection
See section Quality Inspection / Information System for the relevant settings.
- Quality Notification
See section Quality Notification / Information System for the relevant settings.
23.7.2 Supplier Evaluation
The vendor evaluation belongs primarily to the purchasing area. Its functions and the relevant
Customizing can therefore be found in the SAP purchasing component.
The QM component contributes to the calculation of the criterion "Quality".
Quality as a Criterion in the Vendor Evaluation
The main criterion quality contains the automatically valuated subcriteria - goods receipt, audit and
complaints.
- Goods Receipt (GR)

The goods receipt score is calculated from the quality score (QSc) for the inspection lots, according
to the following formula:
QSc = (S1 + S2) / (n1 + n2)
S1 = Sum of quality scores for the inspection lots n1 = Number of inspection lots n2 =
Number of deliveries for materials with a quality information record, for which no inspection
lots exist.
S2 = n2 * QScmax
You can break down the GR score for the vendor according to the material and the inspection
type.
- Audit:
The audit score is either the average quality score for the audits or is made up of the quality scores
for the most recent audits. You can also enter an audit score manually.
- Complaints:
The complaints score is calculated from the number of complaints against the vendor, according to
the following formula:
______________________________________________________________
SAP AG 251
______________________________________________________________
SAP System
QSc = QScmin + (QScmax - QScmin) * (1 - (N * K) / (F * U))
QSc = QScmin if (N * K) > (F * U)
QScmin = Lower limit for QSc
QKZmax = Upper limit for QSc

N = Number of Q-notifications in the applicability period
K = Estimated nonconformity costs
F = Share of business volume for QSc calculation
U = Sales of the vendor in the applicability period
Activities
Refer to the following sections of the IMG for the required Customizing work steps:
- Materials Management/Purchasing Vendor Evaluation

- Weighting Key
- Criteria
- Purchasing Organization Data
- Quality Management/Basic Settings/ Settings at Client Level
Quality Score Areas
- Quality Management/Quality Inspection/Inspection Lot Completion/

Quality Score Procedure
- Quality Manangement/Quality Inspection/Inspection Lot Creation/

Inspection Lot Origin 07
Vendor Audit
- Quality Management/Quality Notification/Information System / Nonconformity Costs
23.7.3 Define View Implementations for Evaluations of Original Documents
Use
You can use this activity to define filter values for the Business Add-In (BAdI) QM Evaluations: View
Types (QG_EVAL_VIEWTYP).
23.7.4 Define Data Definition for Evaluations of Original Documents
Use
You can use this activity to define filter values for the Business Add-In QM Evaluations: Data
Administration (QG_EVAL_MANAGER).
______________________________________________________________
SAP AG 252
______________________________________________________________
SAP System
23.7.5 Define View Types for Evaluations of Original Documents
Use
You can use this IMG activity to define the view types, such as tables, graphics, or pictures, for the
online evaluation of QM data.
The system only uses the view types defined here.
You can assign graphic types to the view types.
23.7.6 Define Graphic Types for Evaluations of Original Documents
Use
You can use this IMG activity to define graphic types for online evaluations of QM data.
The graphic type determines the layout of a graphic.
23.8 Test Equipment Management

This section contains instructions on Customizing for test equipment management.
The SAP system offers different types of test equipment. For more information, see section Quality
Planning / Inspection Planning / Operation / Test Equipment.
The widest range of functions is provided by the test equipment type "equipment", which is contained in
the PM component. The interaction of PM and QM functions allows you, in particular, to process
calibration inspections. For more information about planning calibration inspections, see section Quality
Inspection / Inspection Lot Creation / in Plant Maintenance.
Depending on your requirements, you must include the relevant steps from the PM and QM components
in your implementation project.
23.8.1 Define List Variants
In this step, you define standard variants for lists that are used in test equipment management.
This function uses list view technology. For more information, see section Environment / Tools /
Define List Variants.
______________________________________________________________
SAP AG 253
______________________________________________________________
SAP System
23.9 Stability Study
23.9.1 Basic Data
23.9.1.1 Define Primary Packaging
Use
You determine your primary packaging in this step.
Activities
Enter an abbreviation and an explanatory text for the primary packaging material.
Example
Abbreviation 'BLISTER01', long text 'Tablet Blister Pack (Alu, Clear Plastic)'.
23.9.1.2 Define Physical-Sample Container
Use
You define the sample containers for your stability studies in this step.
Activities
You can find the relevant activity under Define Physical-Sample Containers in QM Customizing.
The path is: Quality Inspection > Sample Management.
The descriptions are also stored here. If necessary, consult the person responsible for QM sample
management, as other people may be affected by your changes.
23.9.1.3 Define Storage Conditions
Use
You define the storage conditions for your stability samples in this step.
______________________________________________________________
SAP AG 254
______________________________________________________________
SAP System
Activities
Maintain a key and a text for the storage condition.
Example
Key '0001', text 'refrigerator 3°'.
23.9.1.4 Define Storage Locations
Use
In this step you define the descriptions for the storage locations of your stability samples.
Activities
You can find the relevant activity under Define Physical-Sample Locations in QM Customizing.
The path is: Quality Inspection > Sample Management.
If necessary, consult the person responsible for QM sample management, as other people may be affected
by your changes.
23.9.1.5 Define Bill of Material Usage
Use
In this step, you define the Bill of Material (BOM) usage for the stability study. You create the new
BOM usage 8, which is for a stability study with the control indicator "Optional Entry" for "Item
Relevant to Construction".
Activities
You can also find this activity under Define BOM Usages in Customizing under Production > Basic Data
> Bill of Material.
This is where BOM usages are stored. You should consult the person responsible for production planning
before making any changes.
______________________________________________________________
SAP AG 255
______________________________________________________________
SAP System
23.9.2 Samples for Stability Study
23.9.2.1 Define Physical-Sample Types
Use
You define the physical-sample type for your stability samples in this step.
A new sample type "Sample for Stability Study" is delivered. You can adapt this sample type to suit
your requirements.
Activities
You can find the relevant activity under Define Physical-Sample Types.
You can also find this activity in QM Customizing. The path is Quality Inspection > Sample
Management.
This is where the sample types are stored.
Consult the person responsible for sample management in QM before making any changes.
Use
In this step, you define the number range intervals for your stability samples.
Activities
You can perform this activity under Define Number Range.

You can also find this activity in QM Customizing. The path is Quality Inspections > Sample
Management.
This is where the number ranges for samples are defined. If necessary, consult the person responsible for
QM Sample Management before you make any changes.
23.9.3 Testing Schedule for Stability Study
23.9.3.1 Define Testing Schedule Category
Use
______________________________________________________________
SAP AG 256
______________________________________________________________
SAP System
In this step, you define the testing schedule category that you want to use to schedule the stability tests
for your stability samples.
Activities
You can find the relevant activity under Set Maintenance Plan Categories.
This is where the maintenance plans are stored. If necessary, consult the person responsible, as other
people may be affected by your changes.
Use
In this step, you define the type of number assignment for the testing schedule (special form of the
Maintenance Plan) that you want to use to schedule your stability tests.
Every testing schedule must have a unique number assigned to it.
For testing schedules, you can define one Number Range for external or internal number assignment.
The following are possible:
- Internal number assignment

In this case, the numbers are assigned automatically by the SAP system. For internal number
assignment to take place, a number range for internal number assignment must be flagged.
- External number assignment

In this case, the numbers are manually assigned by the user. For external number assignment to take
place, a number range for external number assignment must be flagged. During external number
assignment, numbers that are just numerical (no letters), are checked for validity against the
corresponding number range.
Requirements
External number assignment must be defined for the testing schedule in a stability study. The default
value of the notification number must be within the defined external number range interval. The number
must be unique, that is, it cannot have been previously assigned.
Activities
Create the number range, bearing in mind that the type of number range you create depends on whether
you want to use internal or external number assignment.
You transport number range objects as follows:

Choose Interval -> Transport in the accounting document Number Range screen.
All intervals for the selected number range object are deleted in the target system first. After the import,
only the intervals you export are present. The number statuses are imported with their values at the time
of export.
______________________________________________________________
SAP AG 257
______________________________________________________________
SAP System
Dependent tables are not transported or converted.
23.9.4 Quality Notification for Stability Study
23.9.4.1 Open Stability Study
23.9.4.1.1 Notification Type and Catalogs
23.9.4.1.1.1 Define Notification Types
Use
You define the notification type that is to be used for the execution of stability studies in this step.
There are two new notification types in the stability study - QS and QR. Notification type QS is for
stability studies with a material; notification type QR is for stability studies without a material.
You can transport the Customizing settings for quality notifications (notification type Q*), which are
delivered by SAP for client 000 (notification type Q*), automatically to another client of your choice. To
do this, use transaction QCCM, which initiates the corresponding transfer order.
You can transport the entire Customizing for the stability study using transaction QCC_STABI (without
number ranges) or transaction QCC_STABI_NK (only number ranges for the stability study). Before you
transport number ranges, you should check whether these number ranges already exist in your system.
Activities
You can also find this activity under Define Notification Types in the QM notification Customizing. The
path is Quality Notifications > Notification Creation.
Consult the person responsible for QM Customizing in your company before making changes.
23.9.4.1.1.2 Define Number Ranges
Use
You create the number range for the notification type of the stability study in this step. Every notification
type must be assigned to a number range.
Requirements
External number assignment must be specified, and the default value from the notification number must
be within the specified external number range interval. In addition, the number cannot be assigned to
anything else.
Activities
______________________________________________________________
SAP AG 258
______________________________________________________________
SAP System
You can find this activity under Define Number Ranges in QM Customizing. The path is: Quality
Notifications > Notification Creation > Notification Types. This is where the number ranges are stored.
If necessary, consult the person responsible for QM Customizing, as other people may be affected by
your changes.
23.9.4.1.1.3 Define Screen Templates
Use
In this step you structure the screen templates of the quality notification for stability studies.
Activities
You can also find this activity under Define Screen Templates in QM Customizing. You can access it by
choosing Quality Notifications > Notification Creation > Notification Types.
This is where the screen templates are stored. If necessary, speak to the person responsible before you
make any changes.
23.9.4.1.1.4 Maintain Catalogs
Use
You structure the contents of the quality notification for a stability study in this step.
You:
- Determine which structural elements of the quality notification will be used and what information is
to be contained in them.
- Organize and maintain the catalogs that are used in notifications and during defects recording.
Such a catalog can, for example, contain a series of tasks, such as 'Create Initial Sample' and 'Change
Initial Sample'.
Activities
You can find the relevant activity under Maintain Catalogs in QM Customizing. The path is Quality
Notifications > Notification Creation > Notification Content.
This is where the contents of quality notifications are stored. If necessary, consult the person responsible
for QM Customizing, as other people may be affected by your changes.
______________________________________________________________
SAP AG 259
______________________________________________________________
SAP System
23.9.4.1.1.5 Catalogs for Notification Type
Use
In this step you define what contents are available in a quality notification for the stability study
notification type.
Activities
You can find the relevant activity under Catalogs and Catalog Profiles for Notification Type.
You need to:
- Define what information is to be recorded for the notification item and select suitable catalogs.
- Activate classification of notification items if you want to use class characteristics to store
additional information about the notification item.
23.9.4.1.2 Partner
23.9.4.1.2.1 Define Partner Determination Procedures
In this step, you define the partners for processing notifications.

Several partners are usually involved in processing a notification - internal and external partners. The
types of partners and their functions can be different for each notification type. To define the functions,
proceed as follows:
- Certain partners have been predefined in the system; for example, the following partners apply
to notifications:
- Customer (customer number)
- Vendor (vendor number)
- Person (personnel number)
- System user (SAP user)
- Organizational unit
- You can centrally define partner functions for all logistics applications. You must assign a
partner type to the partner function; for example, you can assign the partner type "Customer"
(with customer master and customer number) to the partner function "Complainant." You can
also define a higher-level function for a partner function; for example, you can assign the
higher-level function "Customer purchasing department" to the partner function "Customer
purchasing agent."
- Next, define the partner determination procedures. In each partner determination procedure,
you define which partner functions are allowed. In doing so, you can specify whether a partner
function in a notification can be changed or whether it is a mandatory function.
______________________________________________________________
SAP AG 260
______________________________________________________________
SAP System
- Each notification type is assigned a group of partners; for example, author, processed by,
person responsible. For this reason, you must assign an appropriate partner determination
procedure to each notification type. For each notification type, you must also assign the
partner functions that will appear in the notification header. All other partner functions can be
maintained in the notification itself, on the partner overview screen.
Standard settings
The internal partner functions (for example, author, coordinator, person responsible) exist for
both the partner types 'system user' and 'HR master record.' The partner type 'system user' was selected
for internal partner functions. If you are also using the HR module and you want to work with personnel
numbers, you only have to exchange the following partner functions:
- In the view 'Assign Partner Functions to the Notification Type'

- Author A0 -> AU
- Coordinator KU -> KO
- In the view 'Define notification types'
- Person responsible (person processing the notification) VU -> VW
Recommendation
Use the notification types and their assigned partner determination procedures, as defined in the standard
system, unless you want to use your own partner determination procedures. If your business organization
is currently using the SAP application components HR Org. or SD, it may be advantageous to select the
partner type "employee" for internal partners, in place of the partner type "system user", as defined in the
standard system. Make sure all other applications are in agreement!
If you want to use your own partner determination procedures you can adapt the predefined SAP
notification types and partner determination procedures to your own requirements.
Activities
1. Define the partner functions and the partner determination procedures.

a) Define the partner functions.
If required, assign multilingual keys to the partner functions
b) Define the partner determination procedure and determine which functions are contained in
each procedure.
2. Assign a partner determination procedure to each notification type.
3. Specify the appropriate partner function in the notification header for each notification type.
Further notes
Multilingual Capability
You can use mnemonic keys for partner functions. The system supports this by assigning multilingual
keys to these functions. You can find this function when maintaining the partner functions in the section
Environment/ New Key Assignment for Functions. Such multilingual keys are displayed if you log on in
a language other than the original language. However, only the original key has an effect in the technical
sense, for example, in SE16 or in the transport system.
Partner Objects
______________________________________________________________
SAP AG 261
______________________________________________________________
SAP System
Similar partner determination procedures are also used in other applications (for example, for quality
certificates)and in the Implementation Guide for the Sales and Distribution component
23.9.4.1.2.2 Define Fields for Partner Lists
In this step, you define which fields will be displayed in the partner lists for notifications.
You can number the fields that are to appear in the list or you can mark them as invisible. From this
predefined field list, each user can create his own user-specific list. The user can only select the
numbered fields and those fields that are not marked as invisible. If you assign numbers to the fields, the
numbers are displayed in the corresponding sequence in the application transactions. If a single user has
not defined his or her own field selection, the fields you activated here will be displayed.
Standard settings
The standard system contains a comprehensive field catalog.
Activities
For each partner type, select the fields that are of interest to you.
23.9.4.2 Perform Stability Study
23.9.4.2.1 Notification Functions
23.9.4.2.1.1 Define Priorities
Use
You define the priorities of notifications in this step.

You can define different priority types and assign one to each notification type. For each priority type,
you define:
- Which priority (grade) is suitable for a notification,

- Which start and end dates the notification should have, based on the date of creation.
Recommendation: When you have some sample values , you should change the parameters of the priority
types according to your experiences.
Activities
- Determine which priorities and target basic dates are to be valid for the notification types used in
your company.
- First, you need to define the different priority types.
- For each priority type, define the priority (rank) and basic dates.
- Assign the corresponding priority type to each notification type.
______________________________________________________________
SAP AG 262
______________________________________________________________
SAP System
Further notes
If you choose the unit "Day" for the relative start and end dates for the notification, the system uses the
factory calendar. If you choose other units, for example, "Hour" or "Week", days off (for example,
weekends) will not be taken into consideration by the system.
23.9.4.2.1.2 Define Action Box
In this step, you define additional functions, known as actions, that can be performed during the
processing of a notification. You define these functions using a key and an identifier and assign them to a
notification type. The functions appear as actions in a separate screen section (action box) in the header,
when you process notifications or tasks.
You can control the structure of the action box in the following way:
- To call the function, you can define an icon with a descriptive quick info in addition to the
identifier.
- You use the sort number to define the order of the functions as they are to appear in the action box.
- In addition to the notification type, you can enter a scenario. If you do this, the function only
appears in the action box if this scenario is also assigned to the notification.
- You define the transactions in which the function is to appear in the action box by choosing an
activity type.
- The usage defines whether the function is available at notification level or at task level.
You can control the execution of the function in the following way:
- You can document the processing of the function using a task or activity for the notification or
notification item.
Note: When you display the notification, the system only offers the functions that were defined
with the attribute "No documentation". The assigned function module cannot make any changes to
the notification.
- You can enter a user-defined function module for each function. This module is processed when the
function is called. You can also program a dialog box to be used with this function module.
- If you link a business transaction to the function, it will only be triggered if the respective status of
the transaction in the quality notification allows this. (The system checks the user authorization for
this transaction.)
- If the function is generated for a task, there are two statuses for this task: either released or
completed. Additionally, you can define a workflow task that is activated when the notification is
saved. You can also enter a function module that changes the workflow container when the
notification is saved.
For each function, you can also define several dependent functions (dependent follow-up functions).
The system offers these dependent follow-up functions for selection in the action box after the higher-
level function has been executed. In this way, you can ensure adherence to certain sequences during
processing. For more information about setting up these sequences, see the documentation for the
function module QM07_MERGE_ACTIONBOX.
______________________________________________________________
SAP AG 263
______________________________________________________________
SAP System
Standard settings
To simplify the programming of your own function modules, the standard system contains non-
operational examples for tasks, activities, and change workflow containers. You can choose the
interface that supports your own function modules from these examples.
The standard system contains various sample functions that you can use as sources and copy templates
for your own definitions. You can find the relevant function modules using the following generic entries:
- QM06_FA* Function modules for activities

- QM06_FM* Function modules for tasks
The data relating to these examples (table settings and corresponding catalog entries) is contained in
client 000 in the standard system and must be transferred to the current client if required.
Recommendation
Note that with each release, there may be additional useful examples contained in the standard system.
Transfer these examples if required into the current client.
Activities
1. Determine which recurring functions you can define, dependent on the notification type.
2. Define these functions. Perform any programming necessary for the function modules you require.
Proceed as follows:
a) Assign the function to the notification type. On the detail screen:
b) Define the key and description for the function.
If a function can be used for an item, you can make this clear in the description.
c) Define the controls for the function.

d) Enter a function module with the required flow logic (optional).
e) Define icon and quick info.
In the quick info, you can also indicate whether a function can be selected for an item.
f) Enter code group and code for the task or activity from the catalog that is assigned to the
notification type, if the function is to be documented as a task or activity. You must enter a
status for the task that is to be included in the notification.
3. Determine if tasks are to be supplemented by a workflow and define the workflow tasks as required.
If the assigned function module has a container for the workflow task, the container must also have
an entry.
4. Determine whether the functions are to be triggered in a particular sequence and if so, define the
dependent follow-up functions.
Further notes
In the notification header, only those functions appear for which the user has authorization. Tip: For tasks
and activities, use the authorization for use of certain code groups.
______________________________________________________________
SAP AG 264
______________________________________________________________
SAP System
23.9.4.2.1.3 Define Follow-Up Actions for Tasks
Use
In this step, you define the follow-up actions for tasks that are triggered during a stability study when
follow-up functions are executed. Follow-up actions that control the behavior of the stability study are
defined for most of the follow-up functions.
Activities
You can also find the relevant activity under Define Follow-Up Actions for Tasks in QM Customizing.
The path is: Quality Notifications > Notification Processing > Additional Notification Functions.
This is where the follow-up actions for tasks are stored.
A range of follow-up actions are delivered with the stability study.
If necessary, consult the person responsible for QM Customizing, so that he or she is aware of the
purpose of your data.
23.9.4.2.2 Print Control
23.9.4.2.2.1 Define Shop Papers, Forms, Print Programs
Use
You determine the shop papers (for example, storage list and sample removal list) and the forms for the
stability study in this step. In addition, you also determine what programs will be used to output these
shop papers and forms.
Activities
You can find the relevant activity under Define Shop Papers, Forms, Print Programs in QM
Customizing. The path is: Quality Notifications > Notification Processing > Print Control. If necessary,
consult the person responsible for QM Customizing, as other people may be affected by your changes.
23.9.4.2.2.2 Define Printer
In this step, you set the parameters for the print control.
The print control allows you to individually define the output devices and print parameters for each user
and shop paper.
Using a table-controlled printer rerouting, you can also define special printers and print parameters for
the individual shop papers, based on the contents of certain fields.
Activities
______________________________________________________________
SAP AG 265
______________________________________________________________
SAP System
1. Define a printer and the corresponding print parameters for the individual users and shop papers.
Note that generic entries are possible.
2. Determine whether the printout of individual shop papers should be rerouted based on the contents
of certain objects and fields.
a) Define these objects and fields. Use the objects and fields proposed by SAP and activate them
for the printer rerouting, as necessary.
b) For each active printer rerouting, define the appropriate contents of the controlling fields and
the special print parameters. The entries for the controlling fields can be generic.
23.9.4.2.2.3 Define Download
In this step, you define how the quality notification data will be downloaded to subsystems.
- Define the addresses for the download:

- Specify the subsystem TCP/IP addresses for the Remote Function Call (RFC).
- Define the names of the files in which the transmitted data will be stored.
- Define the structures of the data that will be downloaded to the subsystem.
Activities
1. Define the subsystem addresses and the file names in the subsystem.
You will need two RFC destinations (TCP/IP connections for the front-end workstation) to:
a) create the tables of SAP DDIC structures in an MS-ACCESS database (program path to
Wdpsastr.exe).
b) copy the SAP tables to MS-ACCESS (program path to Wdpsatab.exe). You can find these
programs in the Windows GUI via the path \ps\access\. For proper operation, you will also
need the remaining programs contained in this directory (for example, VBRUN300.DLL,
etc.).
The system must also be able to access the RFC-DLL files (librfc2.dll, librfc3.dll, librfc4.dll,
librfc5.dll, librfc6.dll, vrfc.dll); specify a corresponding PATH command.
2. Define the data structures to be transferred to the subsystem. Use the names of the system tables in
which the data in the SAP system will be prepared for downloading. Refer to the documentation for
the downloading program RIACCESS to obtain the names of the SAP tables.
a) First create the necessary download structures. Specify the RFC destination defined in step
1a).
b) Define the download RFC destination and the PC database. Specify the RFC destination
defined in step 1b) and the path for the database you created. Application code 'N' applies to
the quality notifications.
23.9.4.2.3 Status Management
23.9.4.2.3.1 Define Status Profile
In this step, you define the status management function for the notifications.
______________________________________________________________
SAP AG 266
______________________________________________________________
SAP System
Notifications use the general status management function for SAP objects. A brief explanation of this
concept is provided at the end of this text. For a detailed description of the status management function
and related technical information, refer to the chapter "Basic Settings and Environment" in the section
Status Profile.
Using the general status management function, you can also define your own status profiles to
supplement the predefined system statuses. You can use these status profiles to control the sequence of
certain transactions. Examples of such transactions are:
- Releasing a task
- Completing a notification
For each notification type, you can define different status profiles for:
- The notification header

- A task
Activities
1. Determine whether additional user statuses are required for certain notification types.
2. Define the status profiles for the notifications. For each notification type, you can define appropriate
status profiles for the following object types:
a) Notification header
b) Task
3. Choose the appropriate status profiles for each notification type.
In the SAP system, a distinction is made between a system status and a user status.
- System Status
The SAP system contains a collection of statuses that apply to and can be used by all applications.
These statuses cannot be changed.
- Business Transaction
The SAP system contains all business transactions that apply to and can be used by all applications.
These business transactions cannot be changed.
- Business Transaction / System Status

A system status is assigned to each business transaction. A determination is also made whether the
corresponding system status is to be deleted or set when the transaction is carried out.
- Objects / Business Transaction

In addition, which business transactions can be used with which SAP objects is also defined. This
definition specifies the maximum number of system statuses allowed for an object and which
statuses can be set for individual transactions.
- Status Profile
You can define your own status profiles. You must assign at least one object to each status profile.
Each status profile contains one or more allowed statuses. Within the scope of the business
transactions predefined by SAP, you can specify how the system will behave for each of these
statuses. In the status profile, you define:
- Your own statuses (user statuses) and document their functions in a corresponding long text
______________________________________________________________
SAP AG 267
______________________________________________________________
SAP System
The user status allows you to refine the sequence of system statuses predefined by
SAP to your own requirements. However, this is only possible within the fixed profile defined
by SAP; you cannot override the system status with the user status.
- The status order numbers for user statuses which determine the possible sequence of user statuses
- An initial status that is automatically activated when you create the object
- Which user status is automatically activated when you execute a business transaction
- Which transactions are allowed or not allowed when a certain status is active
- Status Order Number
You can define a status order number for each user status. With the help of the status order number,
you determine the sequence in which the user statuses can be activated. If you do not assign a status
order number to a user status, this user status can always be set. However, only one user status with
status order number may be active at one time. If you assign a status order number to a user status,
you must also specify a lowest and a highest status order number for this status. These numbers
limit the order number interval from which the next user status can be chosen.
- Changeability of the User Status

You can use the Business Add-In for Control of Changeability of the User Status to determine for
each notification type whether or not a particular user status can be changed.
When you maintain the status profile, you can, for example, specify whether quality notifications can be
processed in this status or whether a deletion flag can be set. You can also specify whether a deletion flag
is to be set automatically and whether the system should respond with a warning message or an error
message when a deletion flag is set.
23.9.4.2.3.2 Define Selection Profiles
In this step, you can define selection profiles for notifications. You can use these selection profiles to find
the notifications on the basis of their statuses.
Refer to the chapter Environment, Central Functions, Status Management, Selection Profile for detailed
information about selection profiles.
Activities
1. Determine which system statuses (and user statuses, if necessary) the notifications will have. Make
sure the status profiles for user statuses are different from one notification type to another.
2. Determine how these statuses can be linked in a logical fashion, to produce useful selection profiles;
then define the selection profiles.
23.9.5 Stability Test
23.9.5.1 Create Inspection Lot
23.9.5.1.1 Maintain Inspection Types
Use
______________________________________________________________
SAP AG 268
______________________________________________________________
SAP System
In this step, you maintain the inspection types and the controls associated with inspection types, which
you require for the execution of stability studies.
Requirements
Three inspection types for origin 16 (inspection lots for storage conditions) are delivered with the
stability study:
- 16: for inspection lots automatically created using scheduling.

- 1601: for initial tests.
- 1602: for manually created inspection lots for storage conditions using a follow-up function.
Activities
You can execute the relevant activity under Maintain Inspection Types.
You can adapt the new inspection types to suit your requirements.
You can also find this activity in QM Customizing under Quality Inspections > Inspection Lot Creation.
Consult the person responsible for QM Customizing before making any changes.
23.9.5.1.2 Maintain Inspection Lot Origins and Assign Inspection Types
Use
In this step, you define the controls which depend on the inspection lot origin. The inspection lot origins
themselves are fixed and cannot be changed.
Requirements
The inspection lot origin 16 is delivered for stability studies.
Standard settings
In QM Customizing, you will find the inspection lot origin 16 with the delivered inspection types: 16
(Inspection for Storage Condition), 1601 (Initial Test), and 1602 (Manual inspection for Storage
Condition).
Activities
You can perform the relevant activity under Maintain Inspection Lot Origin and Assign Inspection
Types. You can also find this activity in QM Customizing. The path is: Quality Inspections > Inspection
Lot Creation.
Consult the person responsible for QM Customizing before making any changes.
______________________________________________________________
SAP AG 269
______________________________________________________________
SAP System
23.9.5.1.3 Maintain Number Ranges
Use
You define the number ranges for inspection lots for stability studies in this step. These number ranges
are defined for the Inspection Lot Origin. They are valid for the whole client.
Activities
You can perform this activity under Maintain Number Ranges. You can also find this activity in QM
Customizing under Quality Inspections > Inspection Lot Creation.
23.9.5.1.4 Define Default Values for Inspection Type
Use
In this step, you define the default values for the inspection setup of the stability samples.
Standard settings
The default values are delivered as follows:
- Inspect According to Task List: X

- Assign Specifications Automatically: X
- Enter Characteristic Results: X
- Mean Inspection Duration: 10 (Inspection Type 16 and 1602) / 15
(Inspection Type 1601)
- Quality Score Procedure: 06
Activities
You can execute this activity under Define Default Values for Inspection Type. You can find this activity
in QM Customizing. The path is Quality Inspection > Inspection Lot Creation.
______________________________________________________________
SAP AG 270
______________________________________________________________
SAP System
23.9.5.2 Complete Inspection Lot
23.9.5.2.1 Maintain Catalogs for Usage Decisions
Use
In this step, you maintain entries relevant to the stability study in the catalog type 3 for usage decisions
(UDs).
Requirements
Note the prerequisites in the documentation of the IMG activity referenced below.
Activities
You can perform this activity under Maintain Catalog for Usage Decisions.
You can adapt the new code groups, codes, and selected sets to suit your requirements. You can also find
this activity in QM Customizing. The path is Quality Inspection > Inspection Lot Completion.
You should consult the person responsible for QM Customizing before making any changes.
23.9.5.2.2 Define Follow-Up Actions
Use
In this step, you maintain the follow-up actions for the usage decision codes defined for the stability
study. These codes are in catalog 3.
Requirements
Note the prerequisites mentioned in the documentation for the IMG activity referenced below.
Activities
You can find this activity under Define Follow-Up Actions.

You can adapt the follow-up actions for the usage decision to suit your requirements.
You can also find this activity in QM Customizing. The path is Quality Inspection > Inspection Lot
Completion. Consult the person responsible for QM Customizing before you make any changes.
______________________________________________________________
SAP AG 271
______________________________________________________________
SAP System
23.9.6 System Modifications
23.9.6.1 List Definition for Stability Study
This section contains instructions on how to define variants for selection lists.
You can control the list display, in which SAP objects are available for selection with the help of the list
view function. This function is used in the following sections in QM:
- Inspection Characteristic, Inspection Method

- QM in Procurement
- Quality Notifications
- Test Equipment Management
Type and Use of Variants

There are the following variant types:
- Selection Variants for initial screens (report variants)

You use the selection variants to determine the length of the list by specifying field values on a
selection screen that control object selection.
- Layouts (Display Variants)

You use the layout to determine the width and structure of lists by defining the fields that are
displayed in the columns. As well as specifying column layout, you can specify selection criteria
and how the list can be filtered.
These 2 variant types are subdivided into the following categories:
a) Standard Variants (General Setting)

b) User Variants (User-Related Setting)
c) General Variants (Only possible with selection variants)
When you call an object list (for example, worklist) from the application menu, a screen for selecting
objects appears. The system first tries to select a user variant. If it cannot find one, it searches for a
standard variant. If the system cannot find a standard variant, it displays a screen for manual selection of
the objects. You can then make manual entries, or use existing general variants and add entries manually,
if required. You must also enter a layout on the selection screen.
As the next step, you start the object search using the default values on the selection screen and the
system creates the object list (worklist). To display the list, the system selects the layout specified on the
selection screen. Users can choose another layout directly from the displayed object list and define their
own layouts, by adapting existing ones.
You maintain the standard variants in a similar way in Customizing.
Maintaining Variants
Selection Variants
- Standard variants
The standard system contains one standard variant "SAP&TCODE_xxxx". "xxxx" is the transaction
code that creates the relevant list. The system chooses this variant, if no other preferred variant
exists.
______________________________________________________________
SAP AG 272
______________________________________________________________
SAP System
You can define one standard variant for data selection in Customizing for each list. The system
saves this standard variant with the name "SAP_TCODE_xxxx".
This variant takes precedence in the system over the standard variant "SAP&TCODE_xxxx" and
has an automatic transport link. Note: In a client with a documentation requirement, the dialog box
for the transport request appears when you leave the editing mode and not when you save the
variant (as is usually the case).
- User variants
In the application transaction, you can define a user-specific variant for each list and user. The
system stores these variants under the name "U_<user name>". This variant is chosen in preference
to the standard variant, but does not have a transport link.
- General variants
In addition, you can create any number of miscellaneous variants for each list and store these under
your own, freely-defined names. Such variants are not automatically chosen by the system and do
not have a transport link.
Layouts
- Standard layout
In the standard system, there are one or more standard variants available for displaying each list.
SAP has reserved name space 1* for these pre-defined variants. You can also define any number of
your own standard variants for each list. SAP has reserved name space /* for these user-defined
standard variants.
You can maintain such standard variants in Customizing, as well as in the application transaction.
However, you can use the authorization object S_ALV_LAYO to ensure that only certain users can
maintain standard layouts. To do this, you enter the value 23 in the ACTVT field of the
authorization profile for the user.
Such variants have a manual transport link. Note: You can find the transport link as follows. First,
from the maintenance function, choose Settings -> Layout -> Administration. The screen "Layout:
Administration ". The system displays the list of all standard layouts. Select the entries to be
transported, and then choose Layout -> Transport
- User-layout
In the application transaction, you can define any number of layouts for each list and save them
with any number of names. These layouts have no transport link. Although these variants are called
user-layouts, the system does not choose them first in the QM component, dependent on the user.
Instead it chooses the layout that is proposed in the selection variant.
You can copy layouts from other clients. This applies to both standard and user layouts. To do this, on
the "Layout: Administration" screen, choose Environment -> Import layout.
Procedure
When defining the selection variant, you can propose a layout. We therefore recommend that you define
the variants in the following order:
1. Define standard layouts in Customizing.

It is usually adequate to use one preferred standard layout. If you define additional standard
layouts, you can use these to define user variants subsequently.
2. Define standard selection variant in Customizing.

You can only define one standard selection variant. When defining this variant, enter the standard
layout that you previously defined as the default.
3. Define general selection variants in the transaction.

Different user groups usually have different responsibilities and therefore require different selection
variants. When defining these variants, reference the standard layouts that you have defined
______________________________________________________________
SAP AG 273
______________________________________________________________
SAP System
previously in Customizing. Note: Since these general selection variants do not have a transport link,
you must create them in the productive system.
4. Define user variants in the transaction.

The variants that have already been defined are usually sufficient for your needs. You can,
however, define additional selection variants and layouts in the transaction. You can define your
own selection variant and create a reference in this variant to any other layout. In this case, when
you call up the transaction, the system chooses this user-defined variant containing your proposal
for the layout. Note: Since these user variants do not have a transport link, you must create them in
the productive system.
1. Define selection criteria

When the function is called, a screen appears with all or some of the following selection options:
- List for selection screen: Display mode

- List for selection screen: Change mode
- Maintain list for field selection
Once you have chosen the selection screens, an intermediate screen appears for screen assignment.
This screen is not relevant for the QM component and can be skipped. The selection screen now
appears, on which you make entries to select your objects. Note of the information available on
this screen:
- General help for the selection screen (i-icon)

- Report documentation
- Field help
By choosing "Continue" a screen appears, on which you can enter specific attributes for the
selection screens. On this screen, find out about the meaning of the attributes by checking the
information related to the variant attributes (i-icon). Save the selection variant.
2. Select fields
Once you have chosen this function, a general selection screen appears. To access the field
selection for the list, execute the report and then choose the "Layout" function from the list. You
can find this function by choosing Settings -> Layout. Define the fields contained in the list
columns and save the layout.
Further notes
There are various settings available for the individual lists. These functions are either self-explanatory or
can be learned by testing. Determine which functions are available and which you want to use.
You can use a predefined selection profile as part of the selection criteria. Refer to the section Status
Management for additional information.
23.9.6.2 Activate Workflow Template
In this step, you activate the Workflow template that is to run when notifications are processed.
Further notes
For more information about activating the Workflow, see the Environment / Central Functions section
______________________________________________________________
SAP AG 274
______________________________________________________________
SAP System
23.9.6.3 Business Add-Ins for Stability Study
Use
In this step, you can implement customer-specific enhancements using Business Add-In technology.
Activities
You can find the Quality Management BAdIs under Business Add-Ins under Environment. Here, you can
also find the enhancements that must be performed for the stability study on certain quality management
objects, for example, the physical-sample record, inspection lot, and quality notification. Note the
enhancements specific to the stability study. You can access these under Switch for Selection of Business
Add-In Implementation.
23.10 Environment
In the section 'Environment' of the QM Implementation Guide:
- You make central settings that cannot or should not be assigned to any particular section.
- Central Customizing functions are described that are used in several areas of the QM component.
- You have access to general Customizing tools.
23.10.1 Settings
In the section "Settings," you make central settings.
Recommendation
Copy the settings contained in the standard system initially. Modify these settings during the project
implementation project if required, when you work through the relevant sections in the Implementation
Guide for the QM component.
23.10.1.1 Set Up Side Panels for Quality Management
Use
In Quality Management, you can use a side panel to display additional information about a QM
function. In SAP NetWeaver Business Client Desktop (NWBC), the information is displayed in a
separate screen area.
The following CHIPs are delivered for the side panel:
______________________________________________________________
SAP AG 275
______________________________________________________________
SAP System
- Top 5 defects of material
- Top 5 defective materials by supplier
- Top 5 defective materials of customer
- Top 5 defective materials of plant
Note
The following additional CHIPs are also delivered:
- Average quality score

- Average quality score by supplier (vendor)
However, you do not need to make any Customizing settings for these CHIPs.
Requirements
Authorizations for personal object worklist (POWL):

The CHIPs collect data via a query that was defined in a personal object worklist (POWL). You therefore
require the following authorizations for authorization object CA_POWL:
- Field POWL_APPID = QAM_QI_XXNO_IT_POWL

- Field POWL_QUERY = 02
- Field POWL_CAT = 03
- Other fields = disallowed Copying the technical role:
You have created a copy of the technical role SAP_BSSP_LO_SIDEPANEL. You have assigned
the copy to the users that are to use the side panels.
Registration of the POWL type for application ID (role-based):
In the transaction POWL_COCKPIT, choose the setting Standard POWL and select the application
QAM_QI_XXNO_IT_POWL.
Choose Register Type -> New Entries.
Assign your copy of the role SAP_BSSP_LO_SIDEPANEL to the combination of the POWL type ID
QAM_QI_XXNO_IT_POWL and the application ID QAM_QI_XXNO_IT_POWL.
See also
For more information about side panels, see the application help for SAP NetWeaver under
Technology -> SAP NetWeaver Platform -> Application Help: Function-Oriented View -> UI
Technologies in SAP NetWeaver -> UI Frameworks Based on Application Server ABAP ->
Creating Mashups with the Page Builder -> Implementing Side Panels.
______________________________________________________________
SAP AG 276
______________________________________________________________
SAP System
23.10.1.2 Define Text Formats
In this step, you define the text formats for the long texts used in the objects of the QM component. The
inspection lot text and the text for quality notifications at the header or item level are examples of this.
You assign the sender texts that are used in SAPscript forms to the output programs at company code
level. Such texts are used as header or footer texts in quality notifications or in inspection descriptions.
Standard settings
The text widths are set to 72 characters in the standard system.
Recommendation
Retain the settings contained in the standard system.
Activities
1. Determine whether other settings are needed for SAPscript texts for objects in the QM component
and change the settings, if necessary. You can find the corresponding objects using the generic key
Q*.
Caution: these settings apply to all clients!
2. Determine which of the following forms should contain sender texts, and if required, adapt the copy
models for these texts for each company code to suit your company:
a) Inspection instruction (printing of inspection results for inspection characteristics)
b) Quality certificate
Further notes
- For task list objects, you can specify other text widths. These have priority over the central text
format settings.
- Short texts are usually 40 characters long; any additional characters from the the first long text line
are not displayed in the associated short text.
23.10.1.3 Supplement Units of Measurement and Units of Measure
In this step, you define supplementary units of

measurement and units of measure for quality
management purposes.
Activities
1. Units of measurement
- The units of measurement are managed centrally in the SAP system for all applications and
are usually maintained in the global settings. From a quality management standpoint, you may
need to supplement the predefined units of measurement, in order to:
- Display measured values in a meaningful form.
- Have additional sample units of measure available.
______________________________________________________________
SAP AG 277
______________________________________________________________
SAP System
- Represent inspection lot quantities as the number of containers and the lot container.
- Define units of measurement for defect valuation purposes.
Check whether the units of measurement required in QM exist and are correctly defined.
2. Units of measure groups for materials.

You can use different units of measure to represent the quantity of a material. To simplify the
maintenance of the material master records, you can predefine units of measure groups together
with their respective conversion factors for the base unit of measure.
3. Define additional physical dimensions and units of measure in the system. Check whether the
predefined units of measure groups required to maintain the material master records are
completely and correctly defined.
Further notes
100% inspection
In a 100% inspection, the number of decimal places in the sample unit of measure plays an important
role: This is the case if no sampling procedure is being used. This means one of the following:
- You define a 100% inspection.

- You do not define a sampling procedure for the inspection characteristic.
- The sample size that was determined from the sampling procedure is greater than the lot size and is
therefore limited to the lot size.
The system then reverts to accessing special sample determination rules with the following results:
- If the sample unit of measure has decimal places, the sample size is always 1, this means that the
sample quantity is equal to 1 sample unit of measure.
- If the sample unit of measure has no decimal places, 100% of the lot size in sample units of measure
(rounded up) has to be inspected.
You can also have a 100% inspection, if you use a sampling procedure with the sampling type 100%
inspection, or inspect with a percentage sampling procedure and define the inspection scope as 100%. In
the latter case, the inspection scope is independent of the number of decimal places and is 100% of the
lot size, measured in sample units of measure.
Share of scrap in the inspection lot
In an inspection without the recording of characteristic values, the share of scrap in the inspection lot is
only determined, if the unit of measure in the inspection lot has no decimal places.
Physical-sample container for the physical sample
In the sample-drawing procedure you can enter a physical-sample container for each sample-drawing
item and sample type. This physical-sample container is used for drawing physical samples and is
displayed in the physical-sample record. The physical-sample container is not connected with the lot
containers in the inspection lot. You define physical-sample containers in the Quality Inspection,
Sample Management section of the Implementation Guide.
23.10.2 Central Functions
In this section, you can make the settings for several central functions that are also used in other
components of the SAP system.
______________________________________________________________
SAP AG 278
______________________________________________________________
SAP System
Requirements
To be able to make the proper settings, you must have processed the remaining chapters in the
Implementation Guide for the QM component.
Recommendation
If you need to use the functions that extend beyond the scope of the QM component, individual members
of your project team should get to know the respective application area(s).
23.10.2.1 Signature Strategy
23.10.2.1.1 Define Authorization Groups
Use
In this activity, you define the authorization group that can provide a specific individual signature when
executing signature strategies.
You use user groups if individual signatures are to be executed in succession by different groups of
users, such as production operators, shift managers, and QM employees, and this process is to be
implemented with a signature strategy. This has the advantage that an individual signature is only
executed when the system has verified that the correct user group was assigned to the user for this
individual signature.
You use the authorization groups to restrict the authorization for executing digital signatures in
applications as follows:
- You define different authorization groups for users with different areas of responsibility.
- In the user master record, you assign authorizations for the authorization group that corresponds to
the user's area of responsibility (authorization object C_SIGN_BGR). Depending on the application,
it may also be necessary to assign the authorizations for the C_SIGN authorization object.
- You define individual signatures that must be created by the user of a specific authorization group
and use them in the signature strategies for the relevant application.
Activities
1. Determine which user groups or which areas of responsibility must be distinguished in your
company.
2. Define an authorization group for each user group.
Example
In your company, specific input values must be entered by an employee and then verified by a second
employee. Make the following settings:
- Define the authorization groups EING (entry) and VERIF (verification).

- The employees that enter data receive authorization for the EING group and the employees that
check data receive authorization for the VERIF group.
______________________________________________________________
SAP AG 279
______________________________________________________________
SAP System
- Define two individual signatures for the relevant applications and assign the first to authorization
group EING and the second to authorization group VERIF.
Further notes
Authorization groups are valid in all areas in which the digital signature with signature strategy is used.
Therefore, before you change existing authorization groups or use them for your purposes, ensure that
this will not lead to conflicts of interest with other areas.
23.10.2.1.2 Define Individual Signatures
Use
In this IMG activity, you define the digital individual signatures that must be executed by users in a
specific authorization group.
You can then use the individual signatures as substeps of a signature strategy that is executed in the
relevant application if you sign a process step or confirm an input value outside the permitted value
range.
Requirements
You have defined authorization groups (see Defining Authorization Groups).
Activities
Define the individual signatures that must be executed in the relevant application when signing a process
step or for an invalid input value.
Example
In your company, invalid input values must be signed by the employee responsible for the values and
must be checked and signed by another employee. You define the following individual signatures:
- S1 with authorization group EING

- S2 with authorization group VERIF
Further notes
Individual signatures are also valid in other areas in which the digital signature is used. Therefore, before
you change existing individual signatures or use them for your purposes, ensure that this will not lead to
any conflicts of interest with other areas.
23.10.2.1.3 Define Signature Strategies
Use
In this Customizing activity, you define signature strategies. To do this, make the following settings:
______________________________________________________________
SAP AG 280
______________________________________________________________
SAP System
- Group individual signatures of different user groups into one signature process. - Define
which signature method is used when the signature process is executed.
In Customizing for the application you can then define which signature strategy is used to execute a
process step.
Requirements
You have defined individual signatures (see Define Individual Signatures).
Activities
To create a new signature strategy, execute the following activities:

A. Create new entry for the signature strategy
1. Choose New Entries.

2. Create the key, name, and signature method for the signature strategy.
3. Define whether the following options are required, possible, or disallowed:
- Comment
Here, you can specify if the user has the option of entering a text comment when signing the
application. You have the following options: Disallowed (no comment field is provided),
Possible (comment field can be called up), and Required (signature is only possible after a
comment has been entered).
- Remark
Here, you enable the user to select a remark from a list of predefined remarks and add it to the
signature. The availability of remarks depends on the respective application. You have the
following options: Disallowed, Required, and Possible.
- Document
Here, you specify if the document to be signed should also be displayed to the signatory. You
have the following options: Disallowed, Possible, and Required.
- Verification
Here, you allow signatures that have already been executed to be verified. A check is run in
the background to determine if this document is still identical to the original document and if
the previously executed signatures have been stored correctly in the system.
Note:
These settings are overridden if you chose the setting Disallowed for these options in the
transaction SIGNO (Register Signature Objects for Digital Signature) for the application.
B. Assign individual signatures
In this step, you assign the individual signatures that can or must be executed when executing the
strategy, to the signature strategy.
You can assign the same individual signature more than once or you can assign several individual
signatures with the same authorization group. However, when executing the signature strategy, each user
in the authorization group can only execute one signature.
When saving, the system specifies a counter for each assigned individual signature. The counter
identifies the assignment within the signature strategy but has no influence on the signature sequence
when the strategy is executed.
______________________________________________________________
SAP AG 281
______________________________________________________________
SAP System
1. Select the signature strategy to which you want to assign individual signatures and choose Assign
Individual Signatures.
2. To assign new signatures, choose New Entries.
3. Enter the key for the required individual signatures.
C. Define the signature sequence

In this step, you define the sequence in which the individual signatures in a signature strategy must be
executed.
You determine the signature sequence by selecting a predecessor for each individual signature, in a
sequence matrix.
Then you can also list the predecessors for each individual signature. However, you cannot edit the data
Example:
Individual signatures S1, S2, S3, and S4 are assigned to a signature strategy. The
signature sequences are specified in the matrix, as follows:
Predecessor
Signatures
S1
S2 X
S3 X
S4 X X
This means:
- S1 must be executed first.

- S2 and S3 can be executed after S1.
- S4 can be executed as soon as S3 is available.
Defining signature sequences in the matrix:
1. In the Define Signature Strategy view, select the signature strategy for which you want to specify
the signature sequence.
2. Choose the Signature Sequence pushbutton.
The system displays the dialog box for the signature sequence of the signature strategy. The dialog
box shows the matrix of the individual signatures.
3. In each row, flag the direct predecessors of the individual signature listed at the start of the row.
4. Choose Enter.
If necessary, the system adds the indirect predecessors for the signatures.

Displaying predecessors for individual signatures:
2. Choose Assign Individual Signatures.
______________________________________________________________
SAP AG 282
______________________________________________________________
SAP System
3. Select the individual signatures for which you wish to display the predecessor.
4. In the navigation area, choose Display Predecessor.
D. Define release statuses

In this step, you define one or more alternative release statuses for a signature strategy. For each release
status, you determine a combination of individual signatures with which the signature process can be
completed.
A signature process is only complete if all the signatures belonging to a release status have been
executed.
If you do not define a release status for a signature strategy, all the individual signatures in a signature
strategy must be executed in each signature process.
To define a release status, you flag the required signature combinations in the overview of possible
signature combinations.
You can then also list the individual signatures for each release status. However, you cannot edit the data
Example:
The following signature sequence is defined in a signature strategy:

Predecessor Signatures
S1
S2
X S3
X
S4 X X
In the tabular overview, select the following release statuses:
Individual Signatures Required for Release
S1 S2 S3 S4
X X X
X X X
The signature strategy can be completed with either S2 and S3 or with S4.
Flagging the release status in the tabular overview:
1. Select the signature strategy for which you want to define release statuses.
A table is displayed with all the possible signature combinations contained in the signature strategy.
3. Select the signature combinations that you want to use as the release statuses for the signature
strategy.
4. Choose Enter and save the settings.
Displaying individual signatures for each release status:
______________________________________________________________
SAP AG 283
______________________________________________________________
SAP System
3. Select the release status whose data you wish to display and choose Display Individual Signatures.
A list appears with the counters for the individual signatures that are assigned to the release status.
Further notes
Signature strategies also apply in other areas where digital signatures are used. Therefore, before you
change existing signature strategies or use them for your purposes, ensure that this will not lead to
conflicts of interest with other areas.
23.10.2.1.4 Define Signature Remarks
Use
In this Customizing activity, you can define different signature remarks for each step of the
signature process, which the user can select from a list in the digital signature dialog box.
Requirements
You have made the required settings for the digital signature (see Specify Digital Signature).
Standard settings
The SAP standard system does not provide any entries for the signature remarks table.
Activities
Execute the following steps:
1. For each required combination of application, signature object, and status of signature process,
define one or more signature remarks. If necessary, use the predefined placeholders to include
context information into the signature remark.
2. Indicate which signature remark is to be displayed as the default value.
Further notes
If you want to allow the remark to be changed during the current signature process, set the relevant
indicator:
- For inspection lot processing: in the Customizing activity Define Authorization Groups and
Digital Signature, activity option Material Authorization Groups, Inspection Lot Approval,
Digital Signature
______________________________________________________________
SAP AG 284
______________________________________________________________
SAP System
- For the processing of quality notifications: in the Customizing activity Specify Digital Signature
23.10.2.2 Authorization Management
In this section you define in detail the user authorizations in Quality Management and which functions
users are allowed to implement, as well as the business processes, for which special authorizations are
required.
23.10.2.2.1 Define User Authorizations
In this section, you assign detailed authorizations and authorization profiles to the users of the QM
component.
These supplement or replace the general authorizations that you assigned to the project team in the Basic
Settings at the start of the implementation project.
This description applies if you maintain the authorizations and profiles manually. There are three
steps to this procedure:
- Maintaining the authorizations

- Maintaining the authorization profiles and collective profiles
- Maintaining the user master records
If you have opted to use the profile generator, use the relevant description.
Requirements
You must have defined a higher-level authorization administration for your company:
- You have designated a head administrator to manage the user authorizations.

- You have determined whether an authorization administration needs to be created for quality
management.
If applicable, you have defined these positions and made sure the head administrator has assigned
the necessary QM authorizations to these positions.
- You have determined whether you want to have separate administrators for:
- The maintenance of authorizations and profiles
- The activation of authorizations and profiles
- The maintenance of user masters
Recommendation
- Consolidate the authorization functions. Create decentralized responsibilities, only as far as is

advisable for the size of your company and its security requirements.
______________________________________________________________
SAP AG 285
______________________________________________________________
SAP System
First step: Maintaining the authorizations
Authorization objects
The authorization objects contained in the programs and the fields in these authorization objects (to
which you assign values when maintaining the authorizations) provide the basis for defining the
authorizations.
Comprehensive authorization objects:
Functions for... authorization object
Table maintenance authorization S_TABU_DIS
Transaction authorization Q_TCODE
Material authorization Q_MATERIAL
Authorization objects for maintaining the master data:

Catalog maintenance
- Code groups Q_CAT_GRP

- Selected sets Q_CAT_SSET
Insp. method based on status Q_STA_QMTB
Insp. charac. based on status Q_STA_QPMK
Inspection plan maintenance Q_ROUT
Plan characteristics according to
Task list type Q_PLN_FEAT
Access to QM master data Q_MASTERD
Authorizations for inspection processing:

Insp. type for insp. lot Q_INSPTYPE
Usage of codes from catalogs
- Group codes Q_GP_CODE
- Usage decision code Q_UD_CODE
Inventory postings Q_STCK_CHG
Results recording Q_CHAR_PRC
Inspection completion Q_INSP_FIN
Change control charts Q_SPC
Authorization objects for quality notifications:

Process quality notifications
- General Q_QMEL
- Business transactions Q_VORG_MEL
Authorization objects for quality certificates:

Certificate profile
- Edit Q_CERT_PRF
Standard settings
______________________________________________________________
SAP AG 286
______________________________________________________________
SAP System
The SAP standard system contains an authorization'<Object name>_A' for each authorization object,
which allows all functions for the relevant object.
Recommendation
- Use a set nomenclature for the authorizations.

- Bear in mind there may be users who are not a part of the quality department, but who may
nevertheless require certain display or access authorizations for the quality management functions.
Activities
1. Display the authorization objects for the quality management functions and observe what effects
they have. These authorization objects are in the quality management object class and have the
generic name Q_*.
If you want to give limited authorizations for Customizing functions, the following applies:
Authorization groups are assigned to the tables in the QM component. You can find these
authorization groups in the table TDDAT using the generic entry QM-*. In certain cases, you may
also need authorization groups from other application areas. Examples of such authorization groups
are:
- PMD and PMTD for the print control for quality notifications
2. Make a distinction between the individual users or groups of users according to the tasks they
perform. Create job descriptions that contain the applicable authorization objects. Create
appropriate authorizations for these jobs and their respective functions.
3. Maintain the necessary authorizations.
Authorizations are transported manually.
Second step: Maintaining the profiles
You maintain the authorization profiles for the job areas that deal with the functions of the QM
component.
Standard settings
The QM component contains standard profiles that include comprehensive authorizations for the various
areas of activity within quality management. You can find these profiles using the entry Q_*.
The system also contains comprehensive profiles for the Customizing application.
- S_A.CUSTOMIZ: profile for Customizing functions for all applications

- Z_CUSxx01: profile for Customizing in component xx (for example, xx = QM)
Recommendation
- When you define the profiles, be sure to consider the user groups who are not directly involved in
QM processes, but who still require information from the QM component.
- Use a set nomenclature for the profiles; use mnemonic descriptions.
Activities
______________________________________________________________
SAP AG 287
______________________________________________________________
SAP System
1. Display the authorization objects and authorization profiles contained in the standard system.
2. Create your own profiles and collective profiles, according to your needs.
3. Assign suitable profiles to all defined jobs.
4. Activate the authorizations and profiles.
Profiles are transported manually.
Third step: User maintenance
As a third step, maintain the user master records for all individual users who are familiar with the QM
functions.
SAP Recommendation
In the test system, keep the authorizations of users down to the necessary number. Test the effectiveness
of authorization administration for all user groups.
Activities
1. Create the user master records.

2. Assign the authorization profiles.
3. Maintain the user parameters.
Further notes
The user maintenance does not have a transport link. However, you can copy all user masters into the
target system using the function for copying the source client. The copy profile SAP_USER is available
for this purpose in the standard system. For additional information about the function for copying the
client, refer to the step set up client in the Customizing application.
23.10.2.2.2 Define Authorization Groups and Digital Signature
In this step, you define the authorization groups for
- Material-related activities in QM
- Master data in QM
You only need to process this step if you want to use the following authorization objects:
- Material authorization
- Master data authorization
If you use the material authorization you can also do the following:
______________________________________________________________
SAP AG 288
______________________________________________________________
SAP System
- Stipulate an approval procedure for inspection lots - Request digital signatures (electronic
signatures).
- When drawing physical samples
- When recording inspection results
- When the usage decision is made
Recommendation
Using authorization groups requires a certain amount of organization. You must maintain authorization
groups in the master data and issue appropriate authorizations to users. Use the authorization objects with
due care.
Activities
1. Decide whether you really want to use the authorization groups. If required, define suitable:
- Material groups
- Master data groups
Define the keys for the authorization groups.
2. Maintain the necessary authorizations and profiles for the user master records for those users who
are to have authorization.
3. Maintain the authorization groups in the relevant master data.
4. Determine whether you need approval procedures for inspection lots, and if required, define the
inspection lot creation procedure for each material group.
5. Determine whether you need digital signatures. You can request a digital signature in the following
circumstances:
- When you draw physical samples
- During results recording
- At the usage decision
Make the technical and organizational arrangements for this, as required.
a) Specify a signature method for the circumstances in which a digital signature is required.
b) Make sure that you make the required basic settings.
c) Make sure that the user master records for the persons authorized to give digital signatures are
properly maintained.
Further notes
Approval of Task Lists and Inspection Lots
In certain branches of the process industry (for example, the pharmaceutical industry), Good
Manufacturing Practice (GMP) requires that certain master data and master data changes must be
subjected to an approval procedure. Work orders can only be executed if they are controlled or explicitly
approved using released master data. In the QM component these are:
- The inspection plan (as a controlling master data object)
______________________________________________________________
SAP AG 289
______________________________________________________________
SAP System
To subject the inspection plan to an approval procedure, define a change rule and change type in the
inspection plan header.
- The inspection lot (in the context of a work order)

To subject the inspection lot to an approval procedure, define an identification in the material
authorization group for the inspection lot approval.
Digital Signature
Mainly in the pharmaceutical sector but also in other sectors, the rules of Good Manufacturing Practice
(GMP) require that certain operations only be implemented, monitored, or approved by authorized users.
In the QM component these are:
- Confirming the physical-sample drawing

- Saving characteristic inspection results
- Saving a usage decision
The digital signature can be used as a technical tool for this. Authorized users can, for example, enter
individual identification cards containing their user ID and password using a microchip card reader.
Authorized users must enter a password if they want to save data. The system then checks whether this
data matches the data from the user's master record before it saves the data in the database.
Recommendation
If you use a user signature with an external security product as a signature method, you should always
work with a verification in the productive system. For signatures that do not have a verification, the
validity of the user certificate is not checked. You should therefore only use this signature method for
test purposes.
23.10.2.3 Define Document Types
In this step, you specify the document types for the quality documentation (Q-documents).
The document type is a part of the document key in the document management system. Among other
things, it controls the:
- Number range
- Version management
- Status change when maintained
- Screen layout
Requirements
The document management system is available for use as a cross-application function.
Standard settings
- The system supports the exchange of Q-documents with vendors in two forms:
- Technical delivery terms (document type Q02)
______________________________________________________________
SAP AG 290
______________________________________________________________
SAP System
If the control key for the material stipulates technical delivery terms, you must store
documents of the corresponding document type in the material master at plant level.
- Quality assurance agreements (document type Q01)

If the control key for the material requires quality assurance agreements with the vendor, you
must store documents of the corresponding document type in the Q info-record for the supply
relationship (vendor/material/plant).
These documents are accessed during procurement transactions (that is, when requests for
quotations are received and when purchase orders are issued) and dispatched to the vendor. The
standard system contains fixed settings for these document types, for example:
- When a document is changed, a new version is created in the system.

- The status sequence of a document has been appropriately defined. The definition and
adaptation of these document types is described in the section Quality Planning, Quality
Management in Procurement.
- There are two document types available for documenting the quality management activities in
sales and distribution:
- Quality assurance agreements (document type Q03); These documents are stored in the
customer info-record.
- Quality specifications (document type Q04);
These documents are assigned to a material in the customer info-record. The documentation
for QM in sales and distribution is for information only; unlike the documentation for QM in
procurement it is not automatically processed. You can therefore freely define the settings for the
relevant document types.
Recommendation
Retain the settings contained in the standard system for the document types.
Activities
1. Check the settings of the document types Q01 through Q04 for Quality Management.
2. Check the settings of the document types in the document management system, insofar as they may
be significant to quality management.
Further notes
You can find more information on the document management system in the Implementation Guide
section Cross-application functions, Document management system. In this section you can also find the
setting options relating to the document status and the document assignments to specific master records.
23.10.2.4 Maintain QM Order Types
In this step, you make the settings for the order categories and order types that are used for the following
functions in the QM component:
- Print control for the shop papers relating to the quality inspection
- Sample-drawing instruction
- Inspection instruction
______________________________________________________________
SAP AG 291
______________________________________________________________
SAP System
- Recording of quality costs
- Appraisal costs
- Nonconformity costs
Requirements
- The following order types for printing shop papers must be maintained for order category 50
(inspection lot):
- QM01 Sample-drawing instruction
- QM02 Inspection instruction
- The following order types must be maintained for order category 06 (quality costs):
- QL01 Appraisal costs accumulated and settled for several materials or inspection lots
- QL02 Appraisal costs associated with a single inspection lot
- QN01 Nonconformity costs
You must have maintained default values for these order types.
You must have imported evaluations (reports) for these order types from the standard client 000
into the current client and generated them in the current client (report group 7K0O for the QM and
PM components).
Standard settings
These requirements have been met in the standard system.
Recommendation
Coordinate your actvities with your controlling area and ask their advice with regard to
determining, recording, settling, and analyzing quality costs.
Activities
1. Determine whether the following order categories and order types have been maintained in the
system:
a) Order category 50 (inspection lot) with order types:
- QM01 Printing the sample-drawing instruction
- QM02 Printing the inspection instruction
b) Order category 06 (quality costs) with the order types:
- QL01 Collective settlement of appraisal costs, (periodic)
- QL02 Individual settlement of appraisal costs
- QN01 Nonconformity costs
2. Determine whether the relevant settings for these order types have been maintained in the system.
a) For each plant, define the costing variants that are used in all default values for order types
relating to quality costs.
______________________________________________________________
SAP AG 292
______________________________________________________________
SAP System
b) Define two order types for appraisal costs in the settings at plant level; one for individual
settlement of costs and one for the periodic collective settlement of costs. (See section Basic
Settings and Environment / Settings).
c) For each plant, define the default values for the following order types relating to quality costs:
- Appraisal costs (in the Quality Inspection / Inspection Lot Processing section). -
Nonconformity costs (in the Quality Notification / Notification Processing section).
d) Check whether suitable order types have been maintained in the Print control for inspection
documents (in the Quality Inspection / Inspection Lot Processing section).
3. Determine whether further order types are necessary, for example:
- To differentiate between appraisal costs depending on inspection lot origin or inspection type
- To differentiate between nonconformity costs depending on notification type. Maintain the
relevant table entries if necessary.
Further notes
The Controlling (CO) application is responsible for managing all costs in the system (for example,
planning, settlement and evaluation). This also includes recording, settling and evaluating the quality
costs that are recorded in the QM component. (The planning of quality costs will be supported in later
releases.) Additional settings are described in the Implementation Guide for Controlling, Product Cost
Controlling section. You should make sure, that the corresponding settings have been made correctly in
the Controlling component. For more information, see the Implementation Guide for Controlling,
sections: Product Cost Controlling / Cost Object Controlling
- Generating the orders for quality costs

- Orders for appraisal costs are generated when the user assigns the orders to one or more
materials.
- Orders for nonconformity costs are generated when the user assigns the order to a quality
notification.
- Summarization of quality costs
To distinguish between various types of quality costs, such as, internal and external nonconformity
costs, and to summarize them appropriately in Controlling, you assign orders to a default class in
the SAP classification system and use class characteristics to differentiate between the orders. The
characteristics are defined freely. You can, for example, separate internal nonconformity costs from
external nonconformity costs, by assigning the characteristic "Origin" to the class containing the
nonconformity cost orders and by allowing this class characteristic to have both the attributes
"internal" and "external". To do this, you must activate the classification in the corresponding order
types.
- Analyzing the quality costs

The Controlling module uses flexibly structured, generated reports for making cost analyses.
The preparatory steps for using these reports are described in detail in the Implementation Guide for
the Information System for Product Cost Controlling. Note: You can use the report group 7K0O to
evaluate the quality-related costs.
For more information, see the Implementation Guide for Controlling, Product Cost Controlling /
Information System / Cost Object Controlling.
______________________________________________________________
SAP AG 293
______________________________________________________________
SAP System
23.10.2.5 General Status Management
This section of the Implementation Guide contains instructions on how to use the general status
management function.
The QM module uses the general status management function for the following objects:
- quality info record for the supply relationship

- inspection lot
- quality notification
- certificate profile
With the help of the status management function, you can:
- define your own user statuses for these objects (in addition to the predefined system statuses)
- define selection profiles that will supply you with status-related lists for these objects
23.10.2.5.1 Define Status Profile
This section provides instructions on how to use the general status management function for system
objects, to define your own status profiles.
General
This status management is used in the following objects of the QM component:
- Quality info-record for the material/vendor supply relationship

- Inspection lot
Details for the inspection type
- Certificate profile
Details for the certificate type
- Notification header
- Notification task at header and item level Details of the notification type
Features of general status management
In the SAP system, a distinction is made between the system status and user status.
- System status
The system contains a central set of statuses that apply to and can be used by all applications. These
statuses are maintained by SAP and cannot be changed. This type of status is called a system status.
- Business transactions
The system also contains a set of business transactions that apply to and can be used by all
applications. These business transactions are maintained by SAP and cannot be changed.
- Business transaction - system status

SAP predefines a system status for each business transaction and defines whether the corresponding
system status is deleted or set during the transaction. SAP also defines the business transactions that
______________________________________________________________
SAP AG 294
______________________________________________________________
SAP System
are allowed for a particular system status. A business transaction is only allowed if it is not
forbidden by a status.
- Objects - business transactions

SAP also defines which objects are allowed for which business transactions.
- Result
The assignments listed above indicate which system statuses are possible for an object, and which
system statuses are set in the various transactions.
- Status profile for user status

You can define your own status profiles and assign them to an object. Each status profile contains one
or more authorized user-defined statuses. For each of these statuses, you can determine the system
response within the framework of the business transactions predefined by SAP. The user status refines
the sequence of system statuses predefined by SAP to suit your requirements. However, this is only
possible within the SAP fixed profile. You cannot overide the system status with the user status. In the
status profile:
- You define your own statuses (user status) and document their functions in an accompanying long
text
- You define the status numbers for the user status, which specify the possible sequence of user status
changes
- You define an initial status that is automatically activated when the object is created
- You define which user status is automatically activated when a business transaction is carried out
- You define which transactions are allowed or not allowed when a certain status is active
- Status number
You can define a status number for each user status. The status number determines the sequence
in which the user statuses can be activated. There can only be one user status with a status number
active at any one time. If you assign a status number to a user status, you must also specify a
lowest and highest status number for this status. These values delimit the status number interval
from which the next user status can be chosen. If you do not assign a status number to a user
status, this user status can always be set, even in addition to a status with a status number.
- Authorization key
For each status, you can define an authorization key.
Execution
The following steps describe how you can supplement the general status management with your own user
statuses and how to assign certain business transactions to these statuses.
a) Create a status profile.

b) Assign the status profile to the object types in question.
c) Define user statuses.
d) Assign business transactions to the user statuses.
e) Translate the status profile and the user statuses.
Note: The mnemonic keys (names) of the statuses are also translated, as well as the short text.
f) If required, assign the authoriaztion keys that you previously defined to the statuses.
______________________________________________________________
SAP AG 295
______________________________________________________________
SAP System
Defining status profile You
define a status profile as follows:
Creating status profile

To create a status profile, proceed as follows:
1. Choose "Edit" -> New Entries".

2. Enter a name for the status profile.
3. Enter an explanatory text.
4. Specify a maintenance language for the status profile.
Changes and additions to the status profile can only be made in the maintenance language and must
then be translated into the respective foreign languages. This ensures that the entries are complete
and unambiguous.
5. Press "ENTER" to add the new status profile to the list.

6. Press "Save."
Assign status profile to an object type

To be able to use a status profile for objects of a certain object type, you must assign the profile to
the object type in question:
1. In the screen "Change status profile: overview", position the cursor on the status profile, which you
want to assign to an object type.
2. Choose "Goto -> Authorized object types".
3. Mark the object types for which the status profile can be used.
Note that the following object types are relevant to the quality notification:
- Notification header
- Immediate action (for notification header)
- Task (for notification item)
4. Select "Save."
Define user status

To define user status for a status profile, proceed as follows:
1. Position the cursor on the status profile you want to maintain in the screen "Change Status Profile:
Overview."
2. Choose "Goto -> User status."
3. For each user status, you must enter a four-digit, language-specific identification code to identify
the status.
4. You can make the following specifications for each user status:
a) Enter a Status order number in the field "ONr."
The status order number determines the sequence in which the statuses of a status profile can
be set.
______________________________________________________________
SAP AG 296
______________________________________________________________
SAP System
b) Also enter a lowest and a highest status order number in the columns "NONr" and "HONr."
c) Enter a short text.
The short text contains a short description of the status.
d) Specify a long text for the user status.

To do this, choose "Goto -> Long text".
e) If necessary, mark a user status as initial status.

As a result, it is set automatically when you create an object. For each status profile, you can
only define one status with a status order number as initial status; on the other hand, you can
define as many statuses without status order number you want.
f) Use "Position" to specify at which position the status is displayed in the bar in the order
header.
g) Use "Priority" to specify which priority the user status has at a position, if the same position is
specified for several active statuses.
Assign business transactions to a user status

To assign business transactions to your user statuses, proceed as follows:
1. Position the cursor on the required user status.

2. Choose "Goto -> Transaction control".
3. Choose "Edit -> "New entries" to display a list of the available business transactions.
4. Allcoate the corresponding transactions to your user statuses.
5. You can use "Influence" to activate the following fields per transaction:
a) "No Influence"
The transaction is not influenced by the current user status.
b) "Allowed"
The transaction is allowed by the current user status.
c) "Warning"
The transaction is allowed by the current user status but with a warning. It is up to you
whether you take note of the warning or not.
d) "Prohibited"
The transaction is not allowed by the current user status.
The following requirements must be met in order to be able to carry out a business transation:
- At least one active status must allow the transaction.

- No active status must prohibit the transaction.
6. You can use "Follow-up actions" to determine the effect the execution of a certain transaction has
on the respective statuses:
a) "No action"
The status is neither set nor deleted by the transaction.
______________________________________________________________
SAP AG 297
______________________________________________________________
SAP System
b) "Set"
Transaction sets the respective status.
c) "Delete"
The transaction deletes the respective status. You cannot, however, delete a user status with a
status order number this way.
Such statuses can only be deleted by setting a subsequent status which also has a status order
number.
Translating status profiles and user statuses

You can translate the status profile and the user statuses assignd to it into other languages. If you
want to create a translation, you must consider the following:
- The user statuses can only be created, changed or deleted in the original maintenance language.
- If all user statuses in a status profile are not fully translated, the system displays all user statuses in
the original maintenance language.
If you want to translate a status profile, proceed as follows:
1. Choose "Extras -> Profile translation" in the status profiles overview.

2. Press function key "F4" to call up a list of the foreign language ID codes.
3. Make your selection using the function key "F2."
4. Press "ENTER."
5. Translate the name of your status profile into the required foreign language.
6. Save your translation.
If you want to translate a user status, proceed as follows:
1. Position the cursor on the status profile in question.

2. Choose "Goto -> User status".
The system lists all the user statuses in the profile.
3. Choose "Goto -> Status translation".

4. Use the function key "F4" to call up a list of the foreign language ID codes.
5. Make your selection using the function key "F2."
6. Press "ENTER."
7. Translate the identification code, the short description and, if necessary, the long text into the
required foreign language.
8. Save your translation.
Status simulation
With this function, you can simulate the status development for an object. To do this, for a status
profile, you branch to the screen "Authorized Object Types" and position the cursor on one of
the allowed object types.
______________________________________________________________
SAP AG 298
______________________________________________________________
SAP System
- Via "Extras -> Status simulation, you can simulate the status changes for the corresponding
object that result from the execution of business transactions or from manual status maintenance.
- You can branch from the simulation directly into the status maintenance of the respective object
type to obtain further information on the allowed and prohibited transactions.
- You can use the protocol function to have all the steps you go through recorded. You can then go
back any time to see how the status developed.
Status profile information
This function displays a list which groups the specifications of your status profile together in the screen
"Change Status Profile: Overview".
The list is set up as follows:
- The allowed object types for this status profile are in the first block.
- The user statuses that are defined for this profile are in the second block.
- In the third block, you specify for each user status which business transactions the status
- Allows
- Allows with a warning
- Does not allow Object type information
This function displays a list which groups the specifications for the system statuses for an object type in
the screen "Change Status Profile:Allowed Object Types".
The list is set up as follows:
- The defined system statuses for this object type are in the first block.
- In the second block, the allowed business transactions are listed for this object type.
The general status management
The general SAP Status Management is described in this section.
Status
The current processing status of an object is documented by one or more statuses.

A status is an indicator which fulfills the following functions:
- It informs you that a certain status has been reached (for example, "Order released").
- The status influences the set of feasible business transactions.
When a business transaction is carried out, this in turn can set or delete one or more statuses for the
object in question.
You can set as many statuses as you require for an object.
For example, the following statuses can be set in a production order at the same time:
- Released
- Precosted
- Printed
- Confirmed
______________________________________________________________
SAP AG 299
______________________________________________________________
SAP System
Statuses are displayed in the system either as a 30-character text or as a four-digit identification code.
Both display formats are language-specific.
- A status is active if it is effective at present.

- A status is inactive, either if it has never been active before, or has already been active and has then
been deactivated again.
A status can
- Allow a business transaction

- Allow a business transaction with a warning
- Not allow a business transaction
If a transaction with a warning is allowed for an object, you will receive a warning message when
carrying out the transaction. However, you can carry out the business transaction in spite of the warning.
Example
You want to mark a released production order for deletion. However, the order is not marked with the
status "Finished". In this case, you first receive a warning message which tells you that the order is not
yet finished.
Requirements
To carry out a business transaction, the following conditions must be fulfilled:
- at least one active status must allow the transaction.

- No active status must prohibit the transaction.
In the general SAP Status Management, two different types of statuses are distinguished:
- system status
A system status is a status set by the system informing the user that a specific function was
performed on an object.
If you release an order, for example, the system automatically sets the system status "Released".
You can only influence this status if you carry out a transaction which results in a change to the
system status.
- user status
A user status is a status you set, which can be created in addition to the available system
statuses. You can define and activate as many user statuses as you want. User statuses are defined
in a status profile.
Both statuses influence the business transactions in the same way.
Object type
The object type is used to distinguish between objects with different status controls. It determines which
system statuses are activated automatically when a new object is created and which transactions are
generally possible.
Each object that uses the general SAP Status Management is definitively assigned to an object type by
the system.
Examples of object types:
______________________________________________________________
SAP AG 300
______________________________________________________________
SAP System
- Projects
- Internal orders
- Production orders
- Networks
Status profile
A status profile is a set of user statuses and rules which can be defined by the user. The status profile can
be used either for one or several object types. You generally specify in Customizing which status profile
is to be used for an object.
For orders, for example, you specify via the order type which status profile is used. A status profile can
be used in several order types.
In a status profile, you can define as many user statuses as required using a four-digit identification code.
These status IDs are language-specific and can be translated into other languages. However, you can only
change a status profile in its maintenance language.
Status order number
User statuses can be used to specify a sequence for the processing steps of an object. To do this, you
must define a user status for every step and assign a status order number to this status.
A status, which has no status order number, can be set or deleted any time and regardless of whether
other user statuses are active.
However, at any time, only one user status with a status order number must be active. If another user
status with a status order number is set, the old user status is deleted automatically.
Example
The individual steps in the construction of a building should be monitored using the user status. You
create the following user statuses in a status profile:
stat.ord.no status short text NOrd.no

HOrd.no
------ ------ -------- ------ -------
10 PLAN planning 10
20
20 PGEN planned approval 10
30
30 BAU building execution 30
40
40 ABNA building inspection 30
50
50 ABSL building finished 50
50
The statuses are normally run through in the sequence of the status order numbers. It is, for example, not
possible, however, to change directly from status PLAN to status BAU, since you may switch from order
number 10 to order number 20 at the most. Once you have reached status BAU you can no longer return
to status PLAN or PGEN.
______________________________________________________________
SAP AG 301
______________________________________________________________
SAP System
Recommendation
The status order numbers should be assigned so that they are passed in ascending order. The sequence, in
which the user statuses may be set with a status order number can be controlled using a lowest and
highest status order number.
Initial status
You can characterize a user status as an initial status in the status profile. This status is then automatically
set when a new object is created (for example, order, project). As many user statuses as you like can be
an initial status, only one of which may have a status order number.
Process control
A user status can either allow or prohibit business transactions as well as be set or deleted by a
transaction.
Example
You can define your status profile in the above-mentioned example so that the user status
ABSL is automatically set (in the order master) for the performance of the function Edit -> End.
Status display
The active statuses of an object are listed either one below the other, or are displayed in the form of a
status line.
A maximum of eight statuses can be displayed side by side in the status line. The position where a user
status is displayed in this line can be defined in the status profile. Several statuses can be output at the
same position. You can then use the "Priority" column in the status profile to determine which status is
actually displayed.
All active statuses, sorted by position and priority, are output in the list display.
23.10.2.5.2 Define Selection Profile
In this menu option you define selection profiles that you can use to specify status combinations for
selecting objects (for example, orders or operations). A selection profile is especially useful if you select
a large number of objects repeatedly according to the same selection conditions (for example, orders for
printing shop papers, for collective release, or for creating order valuations).
Selection procedure
The selection conditions are evaluated top-down. Here the following rule applies:
- Several lines following one another that are linked by an OR are combined and evaluated together.
From the block at least one selection condition must be fulfilled.
- AND links blocks or individual conditions. All the blocks or individual conditions linked with AND
must be fulfilled. An order is no longer part of the evaluation as soon as a block or individual
condition is not fulfilled. That means that with every freshly inserted AND a bracket is inserted
______________________________________________________________
SAP AG 302
______________________________________________________________
SAP System
around the preceding expressions (conjunctive normal form). To select the desired status
combinations a reforming of the selection conditions is necessary.
- In general one can say that OR links more strongly than AND!
Example
You want to define a selection profile with which orders with the following status combinations are
selected:
- REL (released)
- CRTD UND MACM (created and material committed)
To do this formulate:
REL OR (CRTD AND MACM)
But the system interprets:

(REL OR CRTD) AND MACM
Orders with the following status combinations are selected:
- REL AND MACM

- CRTD AND MACM
Thus the original formulation must be reformulated by "multiplying out" to:
(REL OR CRTD) AND (REL OR MACM)
Status 'active', 'inactive', or 'never active'
You can also define the state of a status according to which a selection is to be made:
- If you set the state active the system searches for objects where the given status is presently active.
- If you set the state inactive the system searches for objects where the status entered is presently
inactive.
- If you set the state never active the system searches for orders where the status entered was never
active.
Example
The following is an example of a selection profile that should select all released orders that either have a
missing material or a missing PRT.
link status state

REL (released) active
AND MMAT (missing material availability) active
OR MPRT (missing PRT availability) active
The selection is carried out in two steps:
- First, all released operations are selected (that is, orders with the active status 'REL').
- Out of this group the system selects all the orders with missing material or PRT availability (that is,
orders with the active status 'MMAT' or 'MPRT'). All the orders are selected with the following
status combinations:
- RELEASED and MMAT
- RELEASED and MPRT
______________________________________________________________
SAP AG 303
______________________________________________________________
SAP System
- RELEASED and MMAT and MPRT
Indicator 'not'
With this indicator you can reduce the effort required when maintaining selection conditions in particular
cases. Many status conditions can be represented more simply by setting the indicator 'not'.
Example
Selection conditions without 'not' indicator:

link not state
<Status> _ inactive
OR <Status> _ never active
Same selection condition with indicator 'not':
link not state
<Status> X inactive
Recommendation
For performance reasons, conditions that limit the selection strictly should be placed at the start of the
selection profile.
System status/user status
You can enter both system status and also user status in a selection profile. If you want to select objects
according to user status, you must enter the appropriate status profile.
If you have maintained a status profile in the status selection profile, you have to assign this status profile
to all objects. Selection is restricted via the status selection profile only if you have assigned the status
profile to the objects. If you enter a system status in addition to entering a status profile, the system will
ignore it unless it has been assigned to the status profile.
The status profile is assigned to the objects via
- the project profile for the project definition and the WBS elements
- the network type for the network header and the activities
Language dependence of a selection profile
If a selection profile has been created in a language then it can be used in all languages defined in the
system. If user statuses are defined in a selection profile then you should make sure that the user statuses
are translated in the corresponding status profile. If no translation exists then you must enter the user
status in the language in which it was created.
Action
Define your own selection profiles if necessary.
23.10.2.6 Activate Workflow
In this step, you can activate workflows that are triggered from within the QM application component.
______________________________________________________________
SAP AG 304
______________________________________________________________
SAP System
To do this, you use the SAP Business Workflow component. The settings for this are described in the
Implementation Guide for the SAP Basis System (chapter Workflow Management).
Standard settings
In the standard system, certain workflow events and workflow templates are predefined for the QM
component. You can use the transaction PFTC_DIS to find a complete overview of the workflow
templates contained in the standard system. In this transaction, choose the task type 'workflow template'
and display a structured overview of the workflow templates contained in the application components,
using the F4/F8 keys in the 'Task' field. You can expand the QM component, choose and display one of
the workflows.
Examples
- Workflows for inspection lot processing

The workflows are linked to the status management func tion for the inspection lot.
- WS 200066 - No inspection plan assigned

Start condition: when the inspection lot is created, no inspection plan can be explicitly
assigned.
End condition: an inspection plan is assigned to the inspection lot.
- WS 200067 - No sample calculated

Start condition: no sample is calculated when the inspection lot is created. End
condition: sample calculation is carried out.
- WS 200068 - Receipt of certificate is not confirmed

Start condition: receipt of certificate is not confirmed when inspection lot is created. End
condition: receipt of certificate is confirmed when usage decision is made.
- WS 200069 - Open stock postings

Start condition: usage decision is made, however, open stock postings still exist for the
inspection lot.
End condition: stock postings are carried out.
- WS 200070 - Inspection not completed

Start condition: inspection completion for the short-term inspection is set. End
condition: inspection completion for long-term inspection is set.
- WS 200071 - Usage decision has not been made

Start condition: inspection completion for short-term inspection is set, even though a usage
decision has not been made. End condition: a usage decision is made.
- WS 200072 - Usage decision is made before inspection is completed Start condition: a usage
decision is made, even though the inspection completion for the long-term inspection is still
open.
End condition: inspection completion for the long-term inspection is set.
- Workflows for a quality notification

The workflows are linked to the status management function for the quality notification. Workflow
templates exist for the notification header and notification tasks.
- WS 24500047 - Process the notification This workflow template consists of 3 steps:

Step 1
Start condition: The notification is given the status 'outstanding' or 'activated'.
Step 2
Start condition: The notification is given the status 'outstanding task(s) exist(s)'.
______________________________________________________________
SAP AG 305
______________________________________________________________
SAP System
Step 3
Start condition: The notification is given the status 'all tasks completed'. End
condition: The notification is given the status 'completed' or 'marked for deletion'.
- WS 200063 - Task created

Start condition: The task has the status 'outstanding'.
End condition: The task is given the status 'completed'.
- WS 200064 - Person responsible changed

Start condition: The person responsible for the notification is changed. End
condition: The task is given the status 'completed'.
- Workflows for defects recording

The worklflows are linked to the status management function for the quality notification via the
defect record.
- WS 200081 - Defect record created

Start condition: if an inspection characteristic is rejected and the defects recording function is
active, a defect class is assigned to the defect; the defect class has a workflow trigger assigned
to it.
End condition: the quality notification associated with the defect record is activated or
completed.
- Workflows for the electronic transmission of a quality certificate

- WS 20001057 Transfer of results from an IDoc to an inspection lot
Start condition: An electronically transferred quality certificate without a reference to a
purchase order is received for processing as an IDoc.
End condition: The Workflow must be explicitly ended (this means manually)
- WS 03100078 Automatic transfer of results from an IDoc to an inspection lot with origin 01
(goods receipt)
Start condition: An electronically transferred quality certificate with a reference to a purchase
order is received for processing as an IDoc. An inspection lot has been created for the GR
document, for which a a certificate is expected (Status CERTIFICATE).
The Workflow transfers the data from the certificate to inspection lot results table for the GR
document.
End condition: The Workflow ends automatically.
Requirements
You are familiar with the Implementation Guide for the SAP Business Workflow and you have
processed the following steps in the guide: 1. Basic settings (workflow system)
a) Create local destination for tRFC.

b) Maintain workflow editor administrative data.
2. Enterprise organization
a) Maintain plan versions and set active plan versions.

b) Maintain prefix number.
c) Edit organizational plan.
Activities
______________________________________________________________
SAP AG 306
______________________________________________________________
SAP System
1. Determine which workflow events are needed in the QM module.
2. Carry out the task-specific Customizing steps.
a) Select the individuals who will responsible for processing the tasks (TS* key).
b) Activate the event links for the workflow templates (WS* key).
Note: Only activate the event link for workflow templates, not for standard tasks! you do not
need to activate the event link for standard tasks, because these are a part of the workflow
templates. If you were to activate the event link for standard tasks as well as for workflow
templates, you would receive 2 workitems in your inbox.
3. Test the workflows.
23.10.2.7 Organize Archiving
In this step, you define the time intervals for the archiving and deletion of master data and movement
data in the QM component. These definitions apply to a single plant.
Additionally, you define the corresponding business processes.
Master Data
Since the master data is contained in a hierarchy, you should archive data in the following sequence:
- Task lists
- Inspection characteristics
- Inspection methods
When inspection characteristics and inspection methods are archived, the system checks their usage in
existing task lists. Note: Master inspection characteristics that were only used as copy models in the
inspection plan also receive a usage indicator and are noted in the inspection plan. They appear in the
where-used list.
You must therefore archive the inspection plans before you can archive the master inspection
characteristics and inspection methods used in the plans. Additionally, you should archive and delete
master data only after you have archived and deleted the associated transaction data.
Inspection Methods and Master Inspection Characteristics
You must define retention periods for the inspection methods and master inspection characteristics. The
system uses the retention period to calculate the period of time before the archiving date, before which a
master record must have become valid, so that it can be deleted. Archiving takes place in two stages:
1. The status of the master records is automatically changed from status 3 (locked) to status 4 (can be
archived).
This step only affects the historical versions of the master records; the currently valid versions can
only be changed to status 4 manually. Only master records with status 4 can be deleted.
2. The master records are archived and deleted.
Inspection Plan
______________________________________________________________
SAP AG 307
______________________________________________________________
SAP System
There are no retention periods for inspection plans. You can also delete inspection plans without
archiving them.
To delete inspection plans, you must set a deletion flag in the plan headers.
Transaction Data
Data from the Quality Inspection
The prerequisites for archiving are listed in the documentation for the archiving program. You must
define retention periods and deletion times.
The hierarchy of the data requires you to delete the data in the following sequence:
- Single results
- Samples
- Characteristics and operations
- Inspection lots
This sequence is upheld by staggered deletion times.
Quality levels cannot be archived, but can be deleted as soon as they have passed their expiry period.
Data from Quality Notifications
You do not need to define retention periods for archiving notification data.
Activities
1. For each plant, define the requirements concerning the retention periods for master data and
transaction data.
When defining the deletion time for the transaction data, you should take the following into
account:
- The cycle of summarization of data for the QM Information System.

- The time period over which evalutaions will be needed, (for example, for quality certificates).
- The mutual dependency of the QM component on other components, such as Production
Planning (PP) and Materials Management (MM).
- Relevant legal requirements.
2. Maintain the archiving times in the table for each plant.
3. Define the authorizations for archiving and the archiving and deletion procedure.
Refer to the SAP documentation "Database Management" for technical information on the archiving
function.
The archiving objects for the QM component are defined under the generic key QM_* in the ARCHIVE
view cluster (transaction SM34, or AOBJ).
Your system administrator is responsible for archiving, using the transaction SARA. You can find more
information about individual QM archiving objects in this transaction.
______________________________________________________________
SAP AG 308
______________________________________________________________
SAP System
23.10.2.8 Business Add-Ins for Archiving
23.10.2.8.1 Archiving Object QM_SAMPLE: Preprocessing
Use
This Business Add-In (BAdI) is used in the Quality Management (QM) component. It allows you to
perform additional checks in the preprocessing for archiving of the archiving object
CHECK.
23.10.2.8.2 Archiving Object QM_SAMPLE: Archiving Run and Deletion Run
Use
This Business Add-In (BAdI) is used in the Quality Management (QM) component. It
provides interfaces for archiving additional data when archiving the archiving object
QM_SAMPLE.
This BAdI has the following methods:
- PREPARE_WRITE
- WRITE
- DELETE
23.10.3 Tools
This section describes several central tools you can use to adapt and enhance the QM component to meet
your special needs.
You only need these tools after you have processed the remaining chapters in the Implementation Guide
for the QM component.
You should process the step Add organizational units immediately after you have set
up a new system, client or other organizational unit.
Recommendation
______________________________________________________________
SAP AG 309
______________________________________________________________
SAP System
These tools are normally used by a consultant.
23.10.3.1 List Definition
This section contains instructions on how to define variants for selection lists.
You can control the list display, in which SAP objects are available for selection with the help of the list
view function. This function is used in the following sections in QM:
- Inspection Characteristic, Inspection Method

- QM in Procurement
- Quality Notifications
- Test Equipment Management
Type and Use of Variants

There are the following variant types:
- Selection Variants for initial screens (report variants)

You use the selection variants to determine the length of the list by specifying field values on a
selection screen that control object selection.
- Layouts (Display Variants)

You use the layout to determine the width and structure of lists by defining the fields that are
displayed in the columns. As well as specifying column layout, you can specify selection criteria
and how the list can be filtered.
These 2 variant types are subdivided into the following categories:
a) Standard Variants (General Setting)

b) User Variants (User-Related Setting)
c) General Variants (Only possible with selection variants)
When you call an object list (for example, worklist) from the application menu, a screen for selecting
objects appears. The system first tries to select a user variant. If it cannot find one, it searches for a
standard variant. If the system cannot find a standard variant, it displays a screen for manual selection of
the objects. You can then make manual entries, or use existing general variants and add entries manually,
if required. You must also enter a layout on the selection screen.
As the next step, you start the object search using the default values on the selection screen and the
system creates the object list (worklist). To display the list, the system selects the layout specified on the
selection screen. Users can choose another layout directly from the displayed object list and define their
own layouts, by adapting existing ones.
You maintain the standard variants in a similar way in Customizing.
Maintaining Variants
Selection Variants
- Standard variants
The standard system contains one standard variant "SAP&TCODE_xxxx". "xxxx" is the transaction
code that creates the relevant list. The system chooses this variant, if no other preferred variant
exists.
______________________________________________________________
SAP AG 310
______________________________________________________________
SAP System
You can define one standard variant for data selection in Customizing for each list. The system
saves this standard variant with the name "SAP_TCODE_xxxx".
This variant takes precedence in the system over the standard variant "SAP&TCODE_xxxx" and
has an automatic transport link. Note: In a client with a documentation requirement, the dialog box
for the transport request appears when you leave the editing mode and not when you save the
variant (as is usually the case).
- User variants
In the application transaction, you can define a user-specific variant for each list and user. The
system stores these variants under the name "U_<user name>". This variant is chosen in preference
to the standard variant, but does not have a transport link.
- General variants
In addition, you can create any number of miscellaneous variants for each list and store these under
your own, freely-defined names. Such variants are not automatically chosen by the system and do
not have a transport link.
Layouts
- Standard layout
In the standard system, there are one or more standard variants available for displaying each list.
SAP has reserved name space 1* for these pre-defined variants. You can also define any number of
your own standard variants for each list. SAP has reserved name space /* for these user-defined
standard variants.
You can maintain such standard variants in Customizing, as well as in the application transaction.
However, you can use the authorization object S_ALV_LAYO to ensure that only certain users can
maintain standard layouts. To do this, you enter the value 23 in the ACTVT field of the
authorization profile for the user.
Such variants have a manual transport link. Note: You can find the transport link as follows. First,
from the maintenance function, choose Settings -> Layout -> Administration. The screen "Layout:
Administration ". The system displays the list of all standard layouts. Select the entries to be
transported, and then choose Layout -> Transport
- User-layout
In the application transaction, you can define any number of layouts for each list and save them
with any number of names. These layouts have no transport link. Although these variants are called
user-layouts, the system does not choose them first in the QM component, dependent on the user.
Instead it chooses the layout that is proposed in the selection variant.
You can copy layouts from other clients. This applies to both standard and user layouts. To do this, on
the "Layout: Administration" screen, choose Environment -> Import layout.
Procedure
When defining the selection variant, you can propose a layout. We therefore recommend that you define
the variants in the following order:
1. Define standard layouts in Customizing.

It is usually adequate to use one preferred standard layout. If you define additional standard
layouts, you can use these to define user variants subsequently.
2. Define standard selection variant in Customizing.

You can only define one standard selection variant. When defining this variant, enter the standard
layout that you previously defined as the default.
3. Define general selection variants in the transaction.

Different user groups usually have different responsibilities and therefore require different selection
variants. When defining these variants, reference the standard layouts that you have defined
______________________________________________________________
SAP AG 311
______________________________________________________________
SAP System
previously in Customizing. Note: Since these general selection variants do not have a transport link,
you must create them in the productive system.
4. Define user variants in the transaction.

The variants that have already been defined are usually sufficient for your needs. You can,
however, define additional selection variants and layouts in the transaction. You can define your
own selection variant and create a reference in this variant to any other layout. In this case, when
you call up the transaction, the system chooses this user-defined variant containing your proposal
for the layout. Note: Since these user variants do not have a transport link, you must create them in
the productive system.
1. Define selection criteria

When the function is called, a screen appears with all or some of the following selection options:
- List for selection screen: Display mode

- List for selection screen: Change mode
- Maintain list for field selection
Once you have chosen the selection screens, an intermediate screen appears for screen assignment.
This screen is not relevant for the QM component and can be skipped. The selection screen now
appears, on which you make entries to select your objects. Note of the information available on
this screen:
- General help for the selection screen (i-icon)

- Report documentation
- Field help
By choosing "Continue" a screen appears, on which you can enter specific attributes for the
selection screens. On this screen, find out about the meaning of the attributes by checking the
information related to the variant attributes (i-icon). Save the selection variant.
2. Select fields
Once you have chosen this function, a general selection screen appears. To access the field
selection for the list, execute the report and then choose the "Layout" function from the list. You
can find this function by choosing Settings -> Layout. Define the fields contained in the list
columns and save the layout.
Further notes
There are various settings available for the individual lists. These functions are either self-explanatory or
can be learned by testing. Determine which functions are available and which you want to use.
You can use a predefined selection profile as part of the selection criteria. Refer to the section Status
Management for additional information.
23.10.3.2 System Modification
This chapter contains several sections with general technical guidelines, to which you are referred from
other chapters.
Recommendation
At the moment, skip this chapter of the Implementation Guide. You are referred elsewhere to
______________________________________________________________
SAP AG 312
______________________________________________________________
SAP System
the corresponding sections of this chapter.
23.10.3.2.1 Adapt Search Help
This section explains how you can adapt or redefine search help.
Recommendation
To maintain the search help function, you require technical expertise in the ABAP Dictionary. Leave the
maintenance of the search help to your system administration.
Standard settings
The search help contained in the standard system is sufficient to fulfill most companies' needs.
Activities
1. Check whether the search help in the standard system is sufficient for your requirements.
2. If required, supplement the search help functions in the relevant search help objects.
Further notes
Search help functions are created for all clients.

You can find the search help objects in the QM component using the generic key Q*.
Note that a large number of search help functions can impede the performance of the system. Determine
which search help functions you want to use for your work area. You can then deactivate any search help
functions that you do not need.
To improve performance, you may need to structure indices for the new or modified search help
functions.
23.10.3.2.2 Adapt Field Selection
This section describes where and how you can make your own field selection for screens.
Requirements
Determine the name of the program, to which the screen belongs. Go to the relevant screen and from the
menu choose System -> Status. Make a note of the content of the program field (SCREEN).
To identify the screens of a module pool that have a modification planned for the field control, enter the
name of the module pool only in the maintenance function (transaction SFAW or SFAC) and choose the
'Display' or 'Edit' function. The system displays a list of all screen modification groups. From this list,
you can display a list of fields that can be modified for each screen modification group.
You can modify the field control for the following QM programs:
- Master inspection characteristic

Module pool SAPMQSDA
______________________________________________________________
SAP AG 313
______________________________________________________________
SAP System
- Central replacement of master inspection characteristics Module pool SAPMQPDA
- Inspection method
Module pool SAPMQSCA
- Inspection plan
Module pool SAPLCPDI (header and transaction data)
Module pool SAPLQPAA (inspection characteristic data)
- Quality info record

Module pool SAPMQBAA
- QM in SD
Module pool SAPMQVDM
- Inspection lot
Module pool SAPLQPL1
- Inspection lot-usage decision

Module pool SAPMQEVA
- Results recording for inspection point Module pool SAPLQAPP

Module pool SAPMQCPA (certificate profile)
Module pool SAPLQM03 (initial screens)
Module pool SAPLIQS0 (subscreens)
Module pool SAPMQM00 (reference object subscreens)
Module pool SAPLIPAR (partner subscreens)
For partner lists in notifications, there is a specific method for customer-specific field selection, in
addition to the general method described in this documentation. For more information, refer to the
Implementation Guide for Quality Notifications
Execution
All screens for which a field selection is possible are grouped together in individual screen modification
groups (for example, all lists or detail screens for an object).
Modifiable and influencing fields are defined for each screen modification group:
- For the modifiable fields, you use indicators to define how the individual fields will be
displayed on the screen:
- Field is ready for input (default setting)
- Field requires an entry (required entry)
- Field is only displayed
- Field is hidden
- Field is highlighted
For example, if you define the work center as a required entry for the list and detail screens in the
inspection plan, you must maintain the work center in all inspection plans.
______________________________________________________________
SAP AG 314
______________________________________________________________
SAP System
- For the influencing fields, you define how the modifiable field will be displayed on the screen
by means of a value (for example, that the work center is a required entry for a certain plan
usage).
Note
The field selection settings can be transported. These settings are retained in a release upgrade.
If a modified field becomes mandatory due to a change in an influencing field (that is, the field becomes
a required entry field), the system does not check whether this field has entries in all existing objects.
Standard settings
No default settings are provided for the field selection.

The modifiable and influencing fields are predefined for each screen modification group and cannot be
supplemented.
You define a field selection as follows:
There are several ways of defining a field selection.

You maintain the indicators of the modifiable fields independently of an influencing value.
1. Position the cursor on a screen group.

2. Choose the function key Modifiable.
All fields you can modify for this screen modification group appear on the screen.
3. Maintain the indicators and save their entries.

You maintain an influencing value for an influencing field and then the indicators for the
modifiable fields
2. Choose the function key Influencing.
All fields for which you can maintain influencing values appear on the screen.
3. Double-click to choose the influencing field for which you want to maintain a value. All fields that
can be modified for the influencing value appear on the screen.
4. Maintain a value in the field Influencing value and the corresponding indicators for the modifiable
fields.
5. Press ENTER.
The entries are copied.
6. Maintain additional values for the influencing field or choose further fields by pressing Influencing.
You maintain an indicator for a modifiable field and specify the values of the influencing fields
2. Choose the function key Modifiable.
All fields you can modify for this screen modification group appear on the screen.
3. Double-click to choose a modifiable field for which you want to maintain influencing values.
All influencing fields appear on the screen.
______________________________________________________________
SAP AG 315
______________________________________________________________
SAP System
4. Position the cursor on an influencing field for which you want to store a value and select New
Values.
A dialog box appears on the screen.
5. Maintain value and indicator for the influencing field and press Continue. The values are copied.
Activities
1. Determine for which screen modification group you want to modify fields.
2. Maintain the indicators for the modifiable fields and the values for the influencing fields.
3. If necessary, transport your settings. To do this, choose Field selection -> Transport.
23.10.3.2.3 Display Overview of Form
In this step, you modify forms that are used in Quality Management.
23.10.3.3 Delete Protocols from Application Log
This step provides you with a function that allows you to delete the logs that you no longer require from
the application log.
Recommendation
To perform this task, set up a batch job that runs periodically.
Activities
Logs are saved in the application log for the following activities:
- QALS Inspection lot processing Expiration period = 30 days

- AUTO_UD Automatic usage decision
- AUTO_UD_PM Automatic usage decision requests
- RECUR_INSP Deadline monitoring of orders (recurring inspections)
- INSPOPER BAPI for Business Object inspection lot operation
Expiration period = 30 days
- QMQI QM-IDI Interface for subsystems

- QCERT_IN Incoming IDoc for electronic certificates

Identify the intervals, in which the information contained in the application log is evaluated. Define
deletion deadlines to correspond with these intervals.
______________________________________________________________
SAP AG 316
______________________________________________________________
SAP System
23.10.3.4 Evaluate Table History
In this step you can evaluate table histories.

The system is set to log changes to all the main tables in the QM component. You can display the table
history, to identify who has made changes at a particular time.
Requirements
- The technical settings for tables in the Repository (Dictionary) were not changed; the indicator Log
data changes is set.
- The system was started with a profile that contains the parameter rec/ client.
Standard settings
You can find the tables in the QM component using the generic description Q* and TQ*.
Recommendation
Keep the standard settings for tables that are in the Repository.
Activities
To display the history, proceed as follows:
a) Display a list of the tables, for which a history has been logged; select the relevant tables.
b) Display the selective list of change documents.
Further notes
The evaluations are global for all clients.

See also the section Tables Changes Recording in the Implementation Guide for Basis.
23.10.3.5 Functional Enhancement (Customer Exit)
The QM component contains a series of predefined interfaces for customer enhancements. This section
provides instructions on how to implement the enhancements.
For general information about the technology used in these interfaces, refer to the documentation for the
transaction SMOD. (Use Displaying text with SAPscript!)
For specific information about the individual interfaces, refer to the documentation for the respective
enhancements in the transaction CMOD.
Interfaces for customer enhancements in the QM component
You can obtain an overview of the enhancements contained in QM by initiating a generic search using
'Q*' or development class 'Q*' in transaction SMOD. Report RSMOD001 carries out the same function
using a corresponding variant.
To find the enhancements for linking to the QM information system, use the following generic search:
- MCQ* Enhancements in updating data from quality inspections
______________________________________________________________
SAP AG 317
______________________________________________________________
SAP System
- MCI* Enhancements in updating data from quality notifications
23.10.3.6 Business Add-Ins
23.10.3.6.1 Switch for Selection of Business Add-In Implementation
Use
Switch for the selection of active implementations.

For the following Business Add-Ins (BAdIs), you must choose between the standard SAP
implementation and the customer-specific, active implementation:
- Display of additional data on object screen 0170 Phys. Sample(IWO1_SUBSCREEN_0170)

- Check of sample type in maintenance plan for inspection lot origin
(IWP3_INSP_TYPE_CHECK)
- Replacement of node attribute in the document flow graphic (QM11_NODE_ATTRIBUTE)
Requirements
You have created a customer-specific implementation using transaction SE19 or the relevant IMG
activity in the Business Add-Ins menu.
If there is no (active) customer-specific implementation available and the switch is set to customer
implementation, nothing will happen.
Standard settings
If the switch is set to the standard SAP implementation, then the active implementation delivered by
SAP (default implementation) of the relevant Business Add-In is run.
Activities
Set the switch for the relevant Business Add-In to customer implementation if you want to use a
customer-specific program logic.
23.10.3.6.2 QM in Logistics
23.10.3.6.2.1 Business Add-In for Comparison of QM Systems
Use
The Business Add-In (BAdI) QB_QM_SYSTEM_COMPARE contains a method that is called up in the
purchase order. You can use this method to influence the check of the required vendor QM system
against the existing vendor QM system.
______________________________________________________________
SAP AG 318
______________________________________________________________
SAP System
The method is called up just before the actual check and allows you to change the following fields:
- Required QM system from the material master,
- Existing QM system of vendor,
- Validity date of certification, - Delivery date.
23.10.3.6.2.2 Business Add-In for Grouping Together of Quality Information

Records
Use
The Business Add-In (BAdI) QB_Q_INFO_RECORD contains a method that is always called up when a
user accesses the quality info record in read or write mode.
The four reference fields in the Q-info record - material, plant, revision level, and vendor - can be
changed.
This enables a reduction in the number of Q-info records. A single Q-info record can refer to different
combinations of the fields mentioned above.
Requirements
23.10.3.6.3 Quality Planning
23.10.3.6.3.1 BAdI: Creation of Inspection Plans from 3D Models
Use
This Business Add-In (BAdI) is used in the Quality Planning (QM-PT-VP) component. You use this
BAdI to create inspection plans from 3D models.
This BAdI is created under the QPVP_ES_TRANSLATE_PMI_DATA enhancement spot.
This BAdI definition uses the IF_QPVP_TRANSL_PMI_METADATA standard interface.
The following methods are defined in the BAdI:
TRANSLATE_PMI_METADATA
Using this method, you can convert product manufacturing information (PMI) from 3D models into
inspection characteristic values when you create or change an inspection plan (transaction QPC1 or
QPC2). The PMI metadata in the model contains measures and tolerances for the characteristics that
need to be saved in the inspection plan.
______________________________________________________________
SAP AG 319
______________________________________________________________
SAP System
GENERATE_XML_EXCEL
Using this method, you can generate a user-specific template for the Excel file by using the Export to
Excel function when you create or change an inspection plan (transaction QPC1 or QPC2).
Standard settings
For more information about the standard settings (filters, single or multiple uses), see the Enh. Spot
Element Definitions tab page in the BAdI Builder (transaction SE18).
This BAdI is designed for single use.
This BAdI is not filter-dependent.
Example
The PMI data for the PMILW_DIM_cylindrical node could be 25##h6##<diameter>.

This BAdI implementation interprets the main values, the low values, and the high values from the PMI
data by reading the value and tolerance key information.
23.10.3.6.3.2 Business Add-In for Input Processing
Use
The Business Add-In QM_INPUT_PROCEDURE is used during the recording of measured values for
quantitative characteristics. If you implement this BAdI, the system can automatically perform roundings
or other operations related to the measured value.
This BAdI contains the methods:
- INPUT_PROCEDURE (Perform input processing)

The actual input processing is performed in this method. The measured value entered in results
recording can be changed in this method.
- DISPLAY_DOCU (Display documentation for implementation)

You can use this method to display documentation related to the current input processing
implementation. The relevant pushbutton is located behind the field in which the implementation is
defined, for example, in Customizing, in the master inspection characteristic, and in the task list
characteristic.
Requirements
After a new BAdI implementation, the input processing must be planned both in Customizing, and in the
master inspection characteristics or task list characteristics.
______________________________________________________________
SAP AG 320
______________________________________________________________
SAP System
23.10.3.6.3.3 Business Add-In for Maint. of Customer-Specific Fields at Char.
Level (EWB)
Use
The methods of this business add-in are for managing customer-specific enhancements to task list
objects on the detail screens of the engineering workbench.
The plant of the task list header is used as a filter criterion.
23.10.3.6.3.4 Business Add-In When Saving Inspection Plan (EWB)
Use
The methods defined here can be used to define customer-specific modifications or checks in the
engineering workbench, for task list data.
Requirements
The data to be processed must be loaded in the engineering workbench.
23.10.3.6.3.5 Business Add-In for Menu Enhancements in the EWB
Use
You can use BAdI CEWB_CHA_MENU_EXTERN to define your own pushbutton on the characteristics
overview screen of the engineering workbench.
Choosing the pushbutton calls method CHA_EXTENSION_EXTERN, which provides you with all the
key fields of the selected characteristic.
23.10.3.6.3.6 Business Add-In for Specification Determination Rule
Use
This Business Add-In (BAdI) is used in the Quality Management (QM) component. You can
______________________________________________________________
SAP AG 321
______________________________________________________________
SAP System
use this BAdI to change characteristic specifications when you transfer a plan characteristic to an
inspection lot. The specification determination rule stored in the master inspection characteristic serves
as the filter value.
The BAdI is used when maintaining the master inspection characteristic to provide the parameters
required for specification determination and a simulation of the specification determination. For this, it
provides the following methods:
- SET_MASTERCHAR_DATA
- GET_MASTERCHAR_DATA
- SET_PARAMETERS
- GET_PARAMETERS
- CHECK
- SAVE
- SIMULATE
- REFRESH_BUFFER
It is also called when a plan is assigned to an inspection lot:
- EXECUTE
Requirements
The plan characteristic must be linked to a master inspection characteristic. It can also have been
unblocked in the plan.
The changes to the plan characteristic specifications defined via an implementation of the BAdI
SMOD_QEEV0002 are in accordance with the implementation of this BAdI.
23.10.3.6.3.7 Business Add-Ins for Creating Inspection Plans from External

Sources
23.10.3.6.3.7.1 BAdI: Copy Source Data for Creating Master Inspection

Characteristics
Use
This Business Add-In (BAdI) is used in the Quality Planning component. With this BAdI, you can read
data from different sources and save it as master inspection characteristics.
The BAdI uses the following methods:
- GET_CHARACTERISTICS
- GET_STRUCTURE_NAME
______________________________________________________________
SAP AG 322
______________________________________________________________
SAP System
- CONVERT_CHARACTERISTIC
- CHANGE_DATA_BEFORE_SAVE
- GET_EDIT_MODE
- SAVE_MASTER_INSPCHAR
- CHECK_MASTER_INSPCHAR
- GET_SHORTTEXT
- SET_EDIT_MODE
- GET_MIC_FIELDATTR
- GET_SOURCE_FIELDATTR
Requirements
You have defined a corresponding object type for the data source in the IMG activity Define Inspection-
Characteristic Origin.
23.10.3.6.3.7.2 BAdI: Create Inspection Plan from External Data Source
Use
This Business Add-In (BAdI) is used in the Quality Planning component. With this BAdI, you can
transfer data from any data source to an inspection plan.
The following steps are executed:
- The system searches for or creates an inspection plan that fulfills the conditions of the source
object.
- The system searches for the corresponding master inspection characteristics for the data source that
were not yet assigned.
- The data for the plan characteristic is supplemented not only with the data from the master
inspection characteristic but also with the data from the source.
- A consistency check is run before saving.
Requirements
Master inspection characteristics exist that create a connection to the data source.
______________________________________________________________
SAP AG 323
______________________________________________________________
SAP System
23.10.3.6.4 Quality Inspection
23.10.3.6.4.1 Business Add-In for Output Control of QM Print Report
Use
You can use this Business Add-In (BAdI) to change the document output when the results are printed,
when the results are printed from the archive, when the inspection instruction is printed, and when the
sample-drawing instrcution is printed.
Example
If you have selected the output device "MAIL", the predefined example code sends an inspection report
via e-mail to the mail address of the current user when you execute the report for the printing of results.
Activities
After calling up the IMG activity, a dialog box appears, in which you can enter a name for the
implementation.
If you have already made other implementations for this BAdI, another dialog box appears, in which the
existing implementations are displayed. In this case, choose Create, and proceed as follows:
1. In the dialog box, enter a name for the BAdI implementation in the Implementation field, and
choose Create.
The screen for creating BAdI implementations is now displayed.
2. Enter a short text for the implementation in the Short text for implementation field.
3. From the tab index, choose Interface.
The Name of implemented class field is already filled on the tab page, as a class name was
automatically assigned to the implementation when you named it.
4. Save your entries, and assign the implementation to a development class.

5. Place the cursor on the method, and double-click to enter method processing.
6. Enter the code for the implementation between the statements method <Interface name> ~
<Name of method> and endmethod.
7. Save and implement your code. Return to the Edit Implementation screen.
8. Save the entries on the Edit Implementation screen.
Note: You can also create an implementation, and then activate it at a later time. In such a case, end
the processing stage at this point.
9. Choose Activate
The code you stored in the method will be run when the application program is executed.
______________________________________________________________
SAP AG 324
______________________________________________________________
SAP System
23.10.3.6.4.2 Business Add-In for Inspection Lot Processing
The Business Add-In (BAdI) INSPECTIONLOT_UPDATE is called when inspection lots are created
and changed, and usage decisions are made and changed.
23.10.3.6.4.3 Business Add-In for Flexible Specification Selection
Use
This Business Add-In allows you to change the characteristics and operations read in the standard system
before they are written to the database for an inspection lot.
A customer can influence and change specifications such as target values, tolerances, and so on, for an
inspection lot using the method PLMKB_QAPO_MODIFY.
The inspection lot origin is used as the filter for this method. This allows you to implement the change
capability for the specifications based on a particular origin.
Example
An example for the use of this BAdI is the flexible inspection specifications function, which can be
implemented using the method PLMKB_QAPO_MODIFY.
This allows you to make additional changes to inspection specifications, or to impose additional
restrictions on inspection specifications.
When the task list has been selected, all specified inspection characteristics (table T_PLMK) are listed
with the inspections specifications in a popup. In this popup you can select the characteristics that are
actually to be inspected, and, in addition, you can make changes to certain specifications.
This function is available with the stability study.
23.10.3.6.4.4 Business Add-In for Assignment of Additional Data to an

Inspection Lot
Use
You can use this Business Add-In to display data in an inspection lot via additional subscreen areas, and
to change the inspection lot data of the structure QALS_ADDON.
This BAdI is filter-dependent. You can maintain a user-specific implementation for each inspection lot
origin.
______________________________________________________________
SAP AG 325
______________________________________________________________
SAP System
Several subscreen areas are available for implementation in this BAdI. Depending on the inspection lot
origin for which you wish to implement the BAdI, you select the required subscreen areas.
The following subscreen areas are available for implementation:
SAPLQPL1 201 SUBSCREEN_ADDON QALS_ADDON Data (Vendor)

Implement this subscreen in your BAdI implementation for the inspection lot origins 01, 05, 07, 08, 09,
and 15.
SAPLQPL1 204 SUBSCREEN_ADDON QALS_ADDON Data

(Customer)
Implement this subscreen in you BAdI implementation for the inspection lot origins 02, 06, 10, 11, and
12.

(Production)
Implement this subscreen in your BAdI implementation for the inspection lot origins 03, 04, 13, and 14.
SAPLQPL1 208 SUBSCREEN_ADDON QALS_ADDON Data (Stabi)

An active implementation is already delivered for inspection lot origin 16 (stability study). Use this
active implementation as a template for your user-specific implementation.
SAPLQPL1 212 SUBSCREEN_ADDON QALS_ADDON Data (Origin

89)
Implement this subscreen in your BAdI implementation for the inspection lot origin 89.
All of the subscreen areas mentioned above are only active in the change transaction for the inspection
lot. A different subscreen area (see below) is required for the display transaction (QA03). If you have
accessed the inspection lot using the change transaction, you can also change the data of the structure
QALS_ADDON using the subscreen areas.
SAPLQPL1 301 SUBSCREEN_ADDON QALS_ADDON Data (Display

Mode)
This subscreen area is always available when displaying an inspection lot. It is independent of the
inspection lot origin. Implement this subscreen area with every implementation if you want to be able to
display additional data in the display transaction for the inspection lot.
To implement the methods of this Business Add-In, you can either use the sample coding delivered by
SAP as a template, or use the active implementation for the filter value 16 as a template.
If all subscreens are implemented, the following additional data is available:
QALS Inspection lot record
RMQEA Screen fields for processing of the inspection lot
MODUS Change mode (A = Create, B = Change, Z = Display)

In change mode, you can use the method PT_DATA_PAI of your subscreen implementation to return the
changed QALS_ADDON Data to the inspection lot.
______________________________________________________________
SAP AG 326
______________________________________________________________
SAP System
23.10.3.6.4.5 Business Add-In for Inspection of Correction of Actual Lot
Quantity
Use
This Business Add-In (BAdI) is used in the Quality Management (QM) component. It can be used to
implement customer-specific inspections during the explicit correction of the actual lot quantity (using
the corresponding inspection lot transaction).
Requirements
This BAdI is only run if a correction of the actual lot quantity is permitted for the inspection lot origin.
Example
For example, in conjunction with inspection lots for repetitive manufacturing, you can use this BAdI to
implement an inspection that checks that the new actual lot quantity does not exceed the maximum
quantity of the corresponding production version.
23.10.3.6.4.6 Business Add-In for Processing of Data on Sample Tab Page
Use
You can use this Business Add-In to activate an additional tab page in the transactions of the physical-
sample record (QPR1, QPR2, QPR3). This depends on the screen control key for the physical-sample
type. The additional tab page contains a subscreen area that can be implemented using the filter. This
subscreen area is used to display data and to maintain data in the structure QPRS_ADDON in the
physical-sample record.
The structure QPRS_ADDON also contains new data from the physical-sample record that is required
for the stability study. If you want to maintain any additional (customer-specific) data using this Business
Add-In, you must supplement the QPRS_ADDON structure with a customer-specific append structure.
The screen control key is defined in Customizing for the physical-sample type. The screen control key
itself is customizable. If you define a new screen control key and assign it to a physical-sample type, you
can use it to implement various tab pages with data and functions for different physical-sample types,
according to your requirements.
The tab page is labelled using a method in the Business Add-In. If there is no implementation active for
the current filter value (screen control key), the additional tab page will be hidden.
An active implementation of the Business Add- In is delivered for the physical-sample type defined for
stability studies in standard Customizing, and for the screen control key assigned there. Use this active
implementation as a template for your own, customer-specific implementations.
If you want to implement this Business Add-In, use the delivered sample coding for the implementation
of the methods as a template.
______________________________________________________________
SAP AG 327
______________________________________________________________
SAP System
23.10.3.6.4.7 BAdI: Creation of Samples for Externally Triggered Inspection
Use
This Business Add-In (BAdI) is used in the Quality Inspection (QM-IM) component.
When creating inspection lots, you can use this BAdI to create additional physical samples, and to
explicitly assign the associated inspection point to the work centers for an inspection operation in the
inspection plan.
The BAdI is called in the function module QPRE_PREPARE_ALL_PHYS_SAMPLES.
Standard settings
In the standard, this BAdI is active for the origin 17 (external inspection). If you activate this BAdI
without making any changes to it, externally created samples will be represented as physical samples in
Quality Management (QM) in the SAP system, and, if planned, assigned to a specific work center.
The BAdI is filter-dependent. Create implementations for the required origins. If required, you can use
the implementation for the origin 17 as a template.
This BAdI is not designed for multiple uses.
Activities
implementation.
field.
implementation.
8. Choose Activate.
Example
To display sample coding, choose Goto -> Sample Code -> Display.
See also
______________________________________________________________
SAP AG 328
______________________________________________________________
SAP System
Methods
Read External Sample Data
Read Existing Inspection Operations
23.10.3.6.4.8 Business Add-In for Display of Data for Results Recording on

Subscreen
Use
This Business Add-In allows you to display additional data in a subscreen of the header data (screen
5000 in function group QEEM) in the transactions for results recording (Create, Change, Display). You
can also call up another function by choosing a pushbutton on this screen.
Data cannot be changed here.
The relevant entries in the tables QALS, QALT, QAPO, and QAPP for the existing inspection lot are
available in the Business Add-In.
The inspection lot origin is used as the filter for this method, so that the content of the subscreen can be
implemented based on a particular origin.
Requirements
If a customer-specific pushbutton is to be implemented on the subscreen for the header data in results
recording using this Business Add-In, the FCODE used must begin with the following
characters:
+BADI5000
Example: +BADI5000_1
Example
You can use this Business Add-In, for example, to supplement the header area of the results recording
screen by adding a new pushbutton. This can be implemented using the method
PROCESS_OK_CODE.
In this case, you can execute an additional function (for example, you can display additional data) by
activating a specific OK code.
This function is, for example, available in the stability study.

The stability study contains an implementation of this BADI, which adds a supplementary pushbutton to
call the stability history in the header data of screen 5000 for function group QEEM (results recording).
This implementation was performed by defining a new screen as the subscreen in a separate function
group. This new screen was exactly the same size as the subscreen area BADI_SUBSRC_5000 in screen
5000 and contained a pushbutton. This pushbutton is linked to the FCODE '+BADI5000_1'.
In the PBO of the new screen, the adapter class of the instance for BADI
QEEM_SUBSCREEN_5000 is read, and the data in QALS, QALT, QAPO, and QAPP is transferred
(method GET_DATA).
In the implementation of the method PROCESS_OK_CODE, the value '+BADI5000_1' of the OK code
calls a function module in the function group of the subscreen. This function module then calls a module
for the display of the stability history using the global QALS data.
______________________________________________________________
SAP AG 329
______________________________________________________________
SAP System
23.10.3.6.4.9 Business Add-In for Display of Data for Usage Decision on
Subscreen
Use
This Business Add-In allows you to display additional data in a subscreen of the header data
(screen 1101 in program SAPMQEVA) in the transactions for the usage decision (Create, Change,
Display). You can also call up an additional function by choosing a pushbutton on this screen.
The relevant entries in table QALS and in structure RQEVA for the existing inspection lot are available
in the Business Add-In.
Requirements
If a customer-specific pushbutton is to be implemented on the subscreen for the header data in the usage
decision using this Business Add-In, the FCODE used must begin with the following characters:
+BADI1101
Example
You can use this Business Add-In, for example, to supplement the header area of the usage decision
PROCESS_OK_CODE.

call the stability history in the header data of screen 1101 for program SAQMQEVA (usage decision).
QEVA_SUBSCREEN_1101 is read, and the data in QALS and RQEVA is transferred (method
GET_DATA).
______________________________________________________________
SAP AG 330
______________________________________________________________
SAP System
23.10.3.6.4.10 Business Add-In for Valuation of Characteristic Results
Use
The Business Add-In (BAdI) QE_RESULT_VALUATION contains two methods, which are called up in
results recording. You can use both methods to influence the valuation of a measured value when
comparing this against a predefined tolerance limit.
Activities
Implement the methods:
RESULT_VALUATION und RESULT_VALUATION_MEAN.
23.10.3.6.4.11 Business Add-In When Saving in Results Recording
Use
This Business Add-In (BAdI) QE_SAVE makes different tables or structures from results recording
available just before the system saves the data. The save can therefore be prevented.
This BAdI contains the methods:
- IS_ACTIVE (Checks if BAdI is active)

A parameter must be set in this method so that the implementation can be run.
- TABLES_IN_OPERATION (Tables/Structures for operation)
In this method the different tables or structures are made available before results recording is saved.
This BAdI should not be used:
- In process-optimized results recording.

- For results recording on the Web.
- In QM-IDI.
- For the relevant BAPIs.
Example
This BAdI can, for example, be used:
- To check data.
- To prevent saving.
______________________________________________________________
SAP AG 331
______________________________________________________________
SAP System
- To update data.
- To output information.
23.10.3.6.4.12 Business Add-In for Inspection Point Processing Using IDI and
BAPI
Use
You can use this Business Add-In to change the result quantity of inspection points or partial lots that are
read for an inspection lot using the function modules of the IDI or the BAPIs in results recording. You
can then, for example, remove inspection points that have already been valuated from the list.
Activities
Implement and activate the BAdI.
Example
In the sample coding that is delivered by SAP, all valuated inspection points and the corresponding
partial lots are removed from the list.
23.10.3.6.4.13 Business Add-In for Selection of Results Data for Copy of Insp.
Results
Use
You can use this Business Add-In (BAdI) to execute the data selection for the copy inspection results
function using the method SELECTION.
The method INSPECTION_LOT_CHANGE is only called when data is being transferred from
inspection lot creation or inspection lot processing. It allows you to record the copy of the inspection
reults in the inspection lot data record.
If the data transfer is to be performed in results recording, you should update the inspection lot yourself.
The method SETTINGS_CHANGE allows you to change the settings for the copy inspection results
function. You can, for example, use this method to implement a material dependency for the settings.
Activities
implementation.
choose Create.
______________________________________________________________
SAP AG 332
______________________________________________________________
SAP System

9. Choose Activate
23.10.3.6.4.14 Business Add-In for Data Mapping for Copy Inspection
Results Function
Use
You use this Business Add-In (BAdI) to perform the mapping for the copy inspection results function.
Requirements
You have already selected the data that is to be transferred using a suitable data selection procedure, and
you have made this data available in results structures. In this enhancement, you can now link the source
data with the target characteristics and transfer the data.
Activities
implementation.
choose Create.
______________________________________________________________
SAP AG 333
______________________________________________________________
SAP System

9. Choose Activate
23.10.3.6.4.15 Business Add-In for Input Help for Quantities in Usage Decision
Use
You can use this Business Add-In (BAdI) to define an input help for the quantity fields on the stock
screen when making the usage decision. This means that you can record quantities in other units of
measure than the base unit of measure.
Using the methods of this BAdI, you can use an implementation to define a dialog box in which the
quantity value can be entered for a different unit of measure. This value will then be converted to the
base unit of measure within the implementation. In the framework of the usage decision, quantities can
only be passed on to stock posting in the base unit of measure.
To do this, the you select the input help (F4) on one of the quantity fields and then you can enter a
quantity in a unit of measure that differs from the base unit of measure in the dialog box that appears.
This BAdI is only relevant for stock-relevant inspection lots as you can only enter quantities for such
inspection lots.
Example
Code is available in function group QEVA_ALT_QUANTITY_INPUT that allows the input of

quantities in alternative units of measure. This code can be used as it is, or you can use it as a template
for customer-specific functions. For more information, see the relevant consulting note.
______________________________________________________________
SAP AG 334
______________________________________________________________
SAP System
23.10.3.6.4.16 Multiple Specifications: Valuations of Objects
Use
You can use this BAdI to change the valuation of multiple specification objects in the usage decision
transaction. That is, you use this BAdI to define a different, customer-specific logic at object level for the
valuation of multiple specifications.
23.10.3.6.4.17 Define Object Names for Multiple Specifications
Use
You can use the method GET_OBJECT_NAME in this BAdI to change the description of a multiple
specification object, as well as the description of the related object type.
These changed descriptions are then used in results recording, in the usage decision, and in the result
printout instead of the standard descriptions.
23.10.3.6.4.18 Additional Inspections when Closing a Characteristic
Use
Using this Business Add-In (BAdI), you can program additional checks for closing a characteristic in
results recording.
Requirements
Note that these checks are only active if no digital signature is set for the inspection lot in the results
recording area.
Standard settings
Documentation for the method:

CHECK_CLOSING
Activities
Example
In the example implementation, a check of the dual control principle is put into practice.
This means that it is not possible for the person who created a value to also close the characteristic. This
is only possible, if the user is authorized to enforce closure of the characteristic.
______________________________________________________________
SAP AG 335
______________________________________________________________
SAP System
23.10.3.6.4.19 Business Add-In for Enhancements in Overview Tree in QE51N
Use
The Business Add-In (BAdI) BADI_QE_TREE_QE51N is used in the Quality Management (QM)
component. You use this BAdI to include additional fields in the overview tree of the Results
Recording Worklist (transaction QE51N). The BAdI contains the following methods:
FILL_ADDITIONAL_DATA Fill Additional Fields
SET_FIELDCAT_TAB Change of Field Catalog Field Names
Requirements
You have activated the BAdI in Customizing for Quality Management under Basic Settings ->
Maintain Settings at Client Level. There, under Further Settings for the business process Quality
Inspection, you set the QE51N Enhancements to Overview Tree indicator.
Activities
Other components were assigned to the structure QETREEINFO to the levels operation, characteristic,
inspection point, and partial lot in the overview tree of the results recording worklist, to which customer-
specific append fields can be added:
Component Description
QETREEINFO_ADD_FIELDS_OPR For other fields for the operation
QETREEINFO_ADD_FIELDS_CHA For other fields for the characteristic
QETREEINFO_ADD_FIELDS_IP For other fields for the inspection point
QETREEINFO_ADD_FIELDS_PL For other fields for the partial lot
If you have made the fields known to the implementation in type definition, they can be filled via the
method FILL_ADDITIONAL_DATA of the implementation. Additional fields can be added at the
header level of the lot by adding append fields to the structure QETREEINFO.
The fields of the components are assigned groups, which can be accessed in the layout of the transaction.
23.10.3.6.4.20 Business Add-In for Display of 1st/2nd Spec. Limits in Results

Recording
Use
The Business Add-In (BAdI) BADI_QEEM_ADD_SPECIFICATIONS is used in the Quality

Management (QM) component. You can use this BAdI to set the contents of the columns 1st Limit, 2nd
Limit, Valuation 1st Limit, and Valuation 2nd Limit for quantitative inspection characteristics in results
recording.
This BAdI has the following methods:

GET_SPECIFICATIONS
______________________________________________________________
SAP AG 336
______________________________________________________________
SAP System
GET_SPECIFICATION_ICONS
Requirements
You have activated the BAdI in Customizing for Quality Management under Basic Settings ->
Maintain Settings at Client Level. There, under Further Settings for the business process Quality
Inspection, you set the Display Additional Specification Limits in Results Recording indicator.
Activities
The table control SUMPLUS in the dynpro SAPLQEEM 0202 was extended to include the columns 1st
Limit (QTOLGRENZE1), 2nd Limit (QTOLGRENZE2), Valuation 1st Limit (QTOLGRENZE1ICON),
and Valuation 2nd Limit (QTOLGRENZE2ICON). You can use the method GET_SPECIFICATIONS
to set the content of the columns QTOLGRENZE1 and QTOLGRENZE2 in the totals row. You can use
the method GET_SPECIFICATION_ICONS to set icons.
In the standard system, the class CL_IM_QEEM_ADD_SPECIFICATIONS is delivered as a default
sample implementation that displays the first upper and lower specification limit of the inspection
characteristic in the 1st Limit column and the second upper and lower specification limit of the
inspection characteristic in the 2nd Limit column.
In the Valuation 1st Limit column, an icon can be displayed, if required, based on the evaluation using
the function module QEST_TOLERANCE_INSPECTION, where the values for the first upper and
lower specification limit are used as the limit values. In the Valuation 2nd Limit column, the second
upper and lower specification limit is used as the basis for the evaluation.
Note that you can influence only the display of the columns using this BAdI. You cannot use this BAdI
to influence control over the application.
23.10.3.6.5 Quality Certificate
23.10.3.6.5.1 Business Add-In for Certificate Profile Maintenance
Use
This Business Add-In contains interfaces for the maintenance of the certificate profile.
A subscreen area appears on the characteristic detail screen, where you can maintain your own fields for
the characteristic.
In addition, you can specify default values for the fields of the certificate profile characteristic, when
transferring master inspection characteristics or task list characteristics.
Requirements
To be able to maintain customer-specific fields for certificate profile characteristics, you must enhance
the customer-specific append structure CI_QCVM, of the database table QCVM.
______________________________________________________________
SAP AG 337
______________________________________________________________
SAP System
In addition, you require a function group with the subscreen that you want to use on the characteristic
detail screen.
23.10.3.6.5.2 Business Add-In for Creation of Outbound Certificate
Use
You can use this Business Add-In to influence certificate creation.
Further notes
There are also a number of customer enhancements available that can be used to influence certificate
creation. You can select these using QC*.
23.10.3.6.5.3 Adjust Certificate for Multiple Specifications
Use
You can use this Business Add-In (BADI) to change how certificates containing specifications from
multiple specifications are output.
You can, for example, change the order of the relevant objects for the determination of multiple
specifications. You can also suppress characteristics when creating certificates.
Example
See also:
Specification Search Relevant for Document Data (SEARCH_MS_OBJECTS)

New Fields for Certificate Profile Determination (FILL_KOMI)
Check Relevance of Characteristic in Certificate (CHECK_CHAR_RELEVANCE)
______________________________________________________________
SAP AG 338
______________________________________________________________
SAP System
23.10.3.6.6 Quality Notification 23.10.3.6.6.1 Business Add-In for Maintenance
of Reference Object Screen
for Q-Notifs
Use
You can use this BAdI to implement the user-defined reference object screen according to your
requirements. This implementation is dependent on the notification type.
To perform this implementation, you must first have selected the value O550 (object:
user-defined reference object) in the "Object" screen type in Customizing for the notification type. You
do this when maintaining the screen areas for the notification header.
This Business Add-In allows you to display and maintain data related to notifications (VIQMEL).
The following notification data is available in the subscreen that is called in the Business Add-In
implementation:
VIQMEL Notification header

TQ80 Notification type
MODUS Processing mode (H = Add, V = Change, A = Display)
You can return the complete VIQMEL (with changes) to the calling program.
An active implementation of the Business Add-In already exists for the notification types QS (stability
study with material reference and QR (stability study without material reference), which are delivered
with the standard Customizing.
Use this active implementation as a template for your customer-specific implementations.

23.10.3.6.6.2 Business Add-In When Saving Notification Data
Use
This Business Add-In can be used for any notification type (maintenance notification, QM notification,
CS notification, claim, or general notification)
Using this Business Add-In, notification data can be changed when the notification is saved. These
changes are dependent on the notification type. You can also use this Business Add-In when the saving
of the notification is triggered directly by calling the function module IQS1_POST_NOTIFICATION,
and not using the dialog transaction. You can, for example, use this Business Add-In for defects
recording in Quality Management.
The following notification data is available in the Business Add-In implementation:
VIQMEL Notification header data
T365 Processing mode AKTYP ( A = Add, C = Change, D = Display)
______________________________________________________________
SAP AG 339
______________________________________________________________
SAP System
IWQMFE Item data (defect data)
IWQMSM Tasks
IWQMMA Activities
IWQMUR Causes for item
You can return the following with changes to the calling program:
VIQMEL Notification header data
IWQMFE Item data (defect data)
IWQMSM Tasks
IWQMMA Activities
IWQMUR Causes for item
Requirements
The notification type serves as the filter variable.
23.10.3.6.6.3 Business Add-In to Change Functions in Action Box
Use
You can use this Business Add-In to hide, activate, or deactivate a follow-up function in the action box.
You can override the set of rules in standard Customizing in this way.
This Business Add-In is filter-dependent. Depending on the notification type, you can define your own
rules.
Example
In task processing, depending on the coding of the task to be processed, it is possible to offer functions
in the action box.
You can create your own authorization concept.
23.10.3.6.6.4 Business Add-In for Replacement of Node Attribute in Document

Flow Graphic
Use
This Business Add-In is used to replace the node attribute of an object in the document flow graphic of a
quality notification. You can, for example, display the inspection lot short text as an attribute for an
inspection lot object, or display the quantity, status, or storage location of a physical sample.
This Business Add-In is filter-dependent. Depending on the value of the field BADI_IMP_ORIGIN
(Origin of Business Add-In Implementation (SAP, Customer)) in the maintenance view V_TQ01G,
either the implementation delivered by SAP or the customer implementation is run. The maintenance
view is delivered with an entry for all Business Add-Ins (if the implementation of these Business Add-
Ins is controlled using this filter value). The default value for the field BADI_IMP_ORIGIN is 0 (in the
SAP Implementation).
______________________________________________________________
SAP AG 340
______________________________________________________________
SAP System
You can maintain this Business Add-In, or switch from the SAP implementation to your customer
implementation, using the following IMG activity Switch for Selection of Business Add-In
Implementation.
23.10.3.6.6.5 Business Add-In for Controlling the Changeability of the User

Status
Use
You can use this Business Add-In to control whether the user status can be changed for each notification
type.
If you want to forbid changes to the user status (in so far as it is defined for the notification type) for a
particular notification type, then set the export parameter DISPLAY_ONLY to 'X'. Then the user status
can be displayed but not changed, regardless of which processing mode you are in.
This implementation is effective for the following functions in the notification:
Pushbutton Status Detail for the system status of the notification
Pushbutton Set Status for the user status of the notification
Pushbutton Status Detail for the system status of the task
Pushbutton Set Status for the user status of the task
This Business-Add-In is filter-dependent. You can create an implementation for each notification type.
if you do not create any implementation, the user status can be changed in the display- and change mode.
Activities
INCLUDE BADI_ACTIVITY OBJECT DOCU ID TX
23.10.3.6.6.6 Business Add-In for Customer-Specific Fields in Notification

Process
Use
The Business Add-In (BAdI) BADI_IQS0_SUBSCREEN_ADDON is used in the Quality Notifications

component (QM-QN).
You can use this BAdI to include customer fields on the detail screens for the cause and task of a quality
notification. To do this, you create customer subscreens that you can add to the user interface of
transactions QM01, QM02, and QM03 using this BAdI.
The subscreen area BADI_SUBSCREEN_ON_4010 allows you to display additional fields for tasks. The
subscreen area BADI_SUBSCREEN_ON_7116 lets you display additional fields for causes.
Requirements
______________________________________________________________
SAP AG 341
______________________________________________________________
SAP System
You have assigned a QM process to the QM notification type in Customizing for Quality
Management, by choosing Quality Notification -> Notification Creation -> Notification Type ->
Define Notification Types. The QM process is used as a filter in the BAdI implementation.
Standard settings
There is no active BAdI implementation in the standard system. The BAdI is not designed for multiple
implementation.
The BAdI is filter-dependent; it uses the QM process that can be defined in Customizing as a filter. By
assigning the QM process to the QM notification type, you can determine which additional fields the
system displays for which notification type. For each relevant QM process, you must create a BAdI
implementation with the relevant filter value.
Activities
For more information about the procedure, see the SAP Library under Enhancement Framework ->
Business Add-Ins (BAdIs) -> BAdIs Concept -> Screen Enhancements.
Example
You have added customer fields to the structure for tasks (QMSM) and want to display or change these
fields on the detail screens for tasks. They should only be displayed for a QM process with the QM
notification type Q1.
Proceed as follows:
1. Create a function group with a subscreen that contains the fields you require.
2. Create an implementation of this BAdI for the filter value 0001. Do this by copying the example
implementation.
3. Enter your new subscreen for the subscreen area BADI_SUBSCREEN_ON_4010.
4. Make the required Customizing settings for the QM notification type and the QM process.
For more information, see
Documentation for the interface IF_EX_BADI_IQS0_SUBSCREEN_ADDO.

Documentation for the method PUT_4010_DATA_TO_SCREEN
Documentation for the method GET_4010_DATA_FROM_SCREEN
Documentation for the method PUT_7116_DATA_TO_SCREEN
Documentation for the method GET_7116_DATA_FROM_SCREEN
23.10.3.6.6.7 Business Add-In for Implementing an Object Category
Use
______________________________________________________________
SAP AG 342
______________________________________________________________
SAP System
You can use this BAdI to implement your own object categories, which can be assigned to a notification
item.
- GET_SEARCH_ATTRIBUTES
- CHECK_EXISTENCE
- GET_FUNCTIONS
- EXECUTE_FUNCTION
- GET_FIELD_ATTRIBUTES
- CHECK_CONSISTENCY
- MAP_DATA_UI_TO_DB
- MAP_DATA_DB_TO_UI
- CALL_VALUE_HELP
- MAP_RANGES
- DISPLAY
- CONSISTENT_ON_QMEL_CHANGED
- GET_CONCATENATED_KEY_UI
Requirements
You have defined an object category in the Define Object Category Customizing activity.
You have added an append structure to structure QNAOS_OBJ_DATA_UI, which contains the fields
that you want to change or display for your object category.
Standard settings
The BAdI cannot be used multiple times and is filter-dependent.

Implementations for the following object categories are available and active in the standard system:
- Batch
- Serial number
- Inspection lot
- Order
- Delivery item
Example
The implementation of the BAdI provided with the standard system can be used as a template.
______________________________________________________________
SAP AG 343
______________________________________________________________
SAP System
23.10.3.6.6.8 Business Add-In for Enhancing Single-Level Lists
Use
This Business Add-In (BAdI) is used in the Plant Maintenance(PM) and Quality Management
components. You can use this BAdI to append and fill additional fields for single-level lists.
The BAdI supports the following list types:
- Order list
- Operation list
- Order and operation list
- Notification list
- Equipment list
- Fleet object list
- Functional location list
The BAdI uses the following methods:
- FILL_ADD_FIELDS
- CHANGE_FIELD_CATALOG
Requirements
You use an append structure to append additional fields to the output structure of a list.
You use the following output structures for the relevant list type:
In Plant Maintenance
List Type Output Structure
Order list RIHAUFK_LIST
Operation list RIHAFVC
Order and operation list RIH_ORDER_OPERATION_LIST
Notification list RIHQMEL_LIST
Equipment list RIHEQUI_LIST
Fleet object list RIHFLEET_LIST
Functional location list RIHIFLO_LIST
In Quality Management
List Type Output Structure
Quality notification list RQMQMEL1
General quality notification list RQMQMEL3
Task list RQMQMSM
General task list RQMQMSM1
Notification item list RQMQMFE
Action list RQMQMMA
To select additional fields by double-clicking them, you must define appropriate control entries in the
tables T354T and T354S.
______________________________________________________________
SAP AG 344
______________________________________________________________
SAP System
Standard settings
In the standard system there is no active or default implementation available.

The BAdI is designed for multiple use and is not filter dependent.
In the standard system, there is an inactive example implementation. For more information, see the
documentation for the example implementation.
Activities
- Implement the BAdI methods.

See also
This BAdI uses the interface IF_EX_BADI_EAM_SINGLELEVELLIST. For more information, see the
documentation for the interface and the methods.
23.10.3.6.6.9 Business Add-In for Determination of Other Key Figures for

Notification
Use
With this BAdI, you can determine and display customer-specific key figures for quality notifications for
any criteria of a quality notification.
- GET_ADD_KEYFIGURES
- SHOW_DETAILS4ADD_KEYFIGURES
Requirements
In Customizing for Quality Management under Activate Reference to Related Notifications, you have
activated the display of key figures for the quality notification type.
Standard settings
In the standard system, there is no activated BAdI implementation.

The BAdI is not designed for multiple use and is not filter-dependent.
Activities
Implement the methods of the BAdI.

Example
______________________________________________________________
SAP AG 345
______________________________________________________________
SAP System
The sample implementation class CL_EXM_IM_QM08_SALV_DISPLAY of the BAdI supplied with
the standard system can serve as a template and an example.
23.10.3.6.6.10 BAdI: Check of Activity Type for Notification Type
Use
You can use this BAdI to check the activity type, that is the type of processing of quality notifications,
for any notification type.
The following activity types are possible:
- H - Add (= Create)
- V # Change
- A # Display
The BAdI contains the following method:
- CHECK_ACT_QTPYE
You can use this BAdI method to check the activity type of quality notifications for any notification
type. If an activity type is forbidden for a specific notification type, the system can, for example,
issue an error message.
Standard settings
Element Definitions tab in the BAdI Builder (transaction SE18).
BAdI Implementations
In ths standard system, the following BAdI implementation is active when the business function
OPS_QM_EXTENSION_2 (Enhancements in FMEA and Quality Notifications) is activated:
- QQM_QUM_ACT_QTYPE
The BAdI implementation forbids the creation of a notification of notification type Q9 (Complnt
f.Vend.(Ext) - Complaint from Vendor (Ext.)).
Activities
23.10.3.6.6.11 BAdI: Checks for Extended Change of Notification Type
Use
______________________________________________________________
SAP AG 346
______________________________________________________________
SAP System
This Business Add-In (BAdI) is used in the components Quality Notifications (QM-QN) and Plant
Maintenance (PM).
- EXECUTE_ADD_CHECKS
You can use this BAdI method to execute additional enterprise-specific checks following a change
of notification type. For example, changes of notification type that are generally allowed can be
prohibited under certain circumstances, such as for specific customers or materials.
The BAdI method is called in two places:
- With the filter value "original notification type" when you start the function Change Notification
Type using the respective pushbutton
- With the filter values "original notification type" and "target notification type" when you select the
required target notification type from the selection list
- EXECUTE_TYPE_CHANGE
You can use this BAdI method to determine which notification data is to be deleted or retained
when the notification type is changed. The default setting is that all notification data is retained
when the notification type is changed.
Requirements
If you want to allow the notification type to be changed in quality notifications and maintenance and
service notifications, you must activate the following switches:
- Quality Management: Switch QM_SFWS_UI_QQM_CHANGE_TYPE

- Plant Maintenance: Switch EAM_SFWS_CC3_NTF_TYPE_CHANGE
In Customizing for Quality Management or for Plant Maintenance, you have specified which
notification types can be changed to which other notification types. The original notification type and
the target notification type are used as filter values for the BAdI:
- Quality Management: Define Allowed Changes of Notification Type

- Plant Maintenance: Define Allowed Changes of Notification Type
Standard settings
In the standard system, there is no activated BAdI implementation.

Element Definitions tab in the BAdI Builder (transaction SE18).
Activities
______________________________________________________________
SAP AG 347
______________________________________________________________
SAP System
23.10.3.6.7 Stability Study 23.10.3.6.7.1 Business Add-In for Replacement of
Node Attribute in
Document Flow Graphic

Use
This Business Add-In is used to replace the node attribute of an object in the document flow graphic of a
quality notification. You can, for example, display the inspection lot short text as an attribute for an
inspection lot object, or display the quantity, status, or storage location of a physical sample.
This Business Add-In is filter-dependent. Depending on the value of the field BADI_IMP_ORIGIN
(Origin of Business Add-In Implementation (SAP, Customer)) in the maintenance view V_TQ01G,
either the implementation delivered by SAP or the customer implementation is run. The maintenance
view is delivered with an entry for all Business Add-Ins (if the implementation of these Business Add-
Ins is controlled using this filter value). The default value for the field BADI_IMP_ORIGIN is 0 (in the
SAP Implementation).
You can maintain this Business Add-In, or switch from the SAP implementation to your customer
implementation, using the following IMG activity Switch for Selection of Business Add-In
Implementation.
23.10.3.6.7.2 Business Add-In for Maintenance of Reference Object Screen for

Q-Notifs
Use
You can use this BAdI to implement the user-defined reference object screen according to your
requirements. This implementation is dependent on the notification type.
To perform this implementation, you must first have selected the value O550 (object:
user-defined reference object) in the "Object" screen type in Customizing for the notification type. You
do this when maintaining the screen areas for the notification header.
This Business Add-In allows you to display and maintain data related to notifications (VIQMEL).
The following notification data is available in the subscreen that is called in the Business Add-In
implementation:
VIQMEL Notification header

MODUS Processing mode (H = Add, V = Change, A = Display)
You can return the complete VIQMEL (with changes) to the calling program.
An active implementation of the Business Add-In already exists for the notification types QS
(stability study with material reference and QR (stability study without material reference), which
are delivered with the standard Customizing.
______________________________________________________________
SAP AG 348
______________________________________________________________
SAP System
Use this active implementation as a template for your customer-specific implementations.
23.10.3.6.7.3 Business Add-In for Controlling the Changeability of the User

Status
Use
You can use this Business Add-In to control whether the user status can be changed for each notification
type.
If you want to forbid changes to the user status (in so far as it is defined for the notification type) for a
particular notification type, then set the export parameter DISPLAY_ONLY to 'X'. Then the user status
can be displayed but not changed, regardless of which processing mode you are in.
This implementation is effective for the following functions in the notification:
Pushbutton Status Detail for the system status of the notification
Pushbutton Set Status for the user status of the notification
Pushbutton Status Detail for the system status of the task
Pushbutton Set Status for the user status of the task
This Business-Add-In is filter-dependent. You can create an implementation for each notification type.
if you do not create any implementation, the user status can be changed in the display- and change mode.
Activities
INCLUDE BADI_ACTIVITY OBJECT DOCU ID TX
23.10.3.6.7.4 Business Add-In for Processing of Data on Sample Tab Page
Use
You can use this Business Add-In to activate an additional tab page in the transactions of the physical-
sample record (QPR1, QPR2, QPR3). This depends on the screen control key for the physical-sample
type. The additional tab page contains a subscreen area that can be implemented using the filter. This
subscreen area is used to display data and to maintain data in the structure QPRS_ADDON in the
physical-sample record.
______________________________________________________________
SAP AG 349
______________________________________________________________
SAP System
The structure QPRS_ADDON also contains new data from the physical-sample record that is required
for the stability study. If you want to maintain any additional (customer-specific) data using this Business
Add-In, you must supplement the QPRS_ADDON structure with a customer-specific append structure.
The screen control key is defined in Customizing for the physical-sample type. The screen control key
itself is customizable. If you define a new screen control key and assign it to a physical-sample type, you
can use it to implement various tab pages with data and functions for different physical-sample types,
according to your requirements.
The tab page is labelled using a method in the Business Add-In. If there is no implementation active for
the current filter value (screen control key), the additional tab page will be hidden.
An active implementation of the Business Add- In is delivered for the physical-sample type defined for
stability studies in standard Customizing, and for the screen control key assigned there. Use this active
implementation as a template for your own, customer-specific implementations.
23.10.3.6.7.5 Business Add-In for Changing of Default Data (Inspection Lot

IT/Stor.Cond.)
Use
You can use this BAdI in a stability study to prepopulate fields on the follow-up function screen when
creating an inspection lot for an initial test, or when manually creating an inspection lot for a storage
condition.
To do this, you must create a customer-specific implementation for this BAdI.
You can use this customer-specific implementation to prepopulate the following fields according to your
requirements:
- Inspection Lot Short Text (E_KTEXTLOS)

- Inspection Type (E_ART) => Change of default
- Inspection Plan Number (E_PLNNR)
- Group Counter (E_PLNAL)
This BAdI also recognises work areas of the physical-sample drawing (I_QPRN) and the sample
(I_QPRN), as well as a field that tells you about the inspection lot type (I_QSTABI).
The parameter I_QSTABI can have the following values in the context of stability studies:
1 = Inspection Lot for Initial Test
3 = Inspection Lot for Storage Condition (Manually Created)
______________________________________________________________
SAP AG 350
______________________________________________________________
SAP System
Example
This BAdI is used on screen 1000 of the function group QST02 for the creation of an inspection lot for
the initial test, or the creation of a manual inspection lot for a storage condition.
If you implement this BAdI accordingly, you can, for example, prepopulate the inspection lot short text
when creating an inspection lot for an initial test, according to your requirements.
Other fields on the screen, apart from the ones named above, cannot be changed using a BAdI
implementation.
23.10.3.6.7.6 Business Add-In for Flexible Specification Selection
Use
This Business Add-In allows you to change the characteristics and operations read in the standard system
before they are written to the database for an inspection lot.
A customer can influence and change specifications such as target values, tolerances, and so on,
for an inspection lot using the method PLMKB_QAPO_MODIFY.

The inspection lot origin is used as the filter for this method. This allows you to implement the change
capability for the specifications based on a particular origin.
Example
An example for the use of this BAdI is the flexible inspection specifications function, which can be
implemented using the method PLMKB_QAPO_MODIFY.
This allows you to make additional changes to inspection specifications, or to impose additional
restrictions on inspection specifications.
When the task list has been selected, all specified inspection characteristics (table T_PLMK) are listed
with the inspections specifications in a popup. In this popup you can select the characteristics that are
actually to be inspected, and, in addition, you can make changes to certain specifications.
This function is available with the stability study.
23.10.3.6.7.7 Business Add-In for Changing Workarea for Stabi InspLot Before
Calling QPL1
Use
______________________________________________________________
SAP AG 351
______________________________________________________________
SAP System
The method of this Business Add-In is run directly before an inspection lot for a stability study is created.
It can be used to make changes in the transferred inspection lot work area. You can, for example, use this
Business Add-In to enter your own inspection lot short text, or to fill in your own customer-specific
inspection lot data.
This Business Add-In is filter dependent. You can create an implementation for each inspection type.
A sample implementation and a default implementation exist for this Business Add-In. If the default
implementation is used, the short text of an inspection lot for a stability study is filled with the
following data:
- The package number

- The short text for the storage condition
- The key of the stability study
Requirements
The interface of method CHANGE_QALS_WA contains the following parameters:
Importing:
I_QALS Inspection lot record
I_MHIS Table of testing schedule calls; contains exactly one entry for the current call
of the testing schedule item
I_MPOS Testing schedule item
FLT_VAL Filter value, that is, the current inspection type
Exporting:
E_QALS Changed inspection lot record
E_IMP_ACTIV Flag, that the changed data is to be copied
If you implement a method, you must:
- Always fill E_QALS with data. When you begin your implementation, you can transfer data from
I_QALS to E_QALS using the instruction 'move I_QALS to E_QALS.'
- Set the export parameter E_IMP_ACTIV to 'X' if you want the changed data to be transferred to
inspection lot creation.
The following inspection lot data is already reserved and should NOT be changed:
WARPL
ABNUM
WAPOS
STRAT
PLNTY
PLNNR
PLNAL
WERK
HERKUNFT
ART
MATNR
CHARG
XCHPF
STAT32
______________________________________________________________
SAP AG 352
______________________________________________________________
SAP System
If you do make changes to this data, it can lead to data inconsistencies and errors at inspection lot
creation.
The following inspection lot data is also reserved. Be particularly careful when changing this data.
KTEXTLOS
QMATAUTH
KUNNR
LIFNR
HERSTELLER
LOSMENGE
MENGENEINH
LMENGEIST
KTEXTMAT
PASTRTERM
PASTRTERM
ENSTEHDAT
GUELTIGAB
Standard settings
The default implementation of the method CHANGE_QALS_WA is run as the standard.
Example
SAP delivers a sample implementation for the method of BAdI CHANGE_QALS_WA. You should
use the sample implementation or the default implementation delivered by SAP as the basis for your
own, customer-specific impementations.
23.10.3.6.7.8 Business Add-In for Assignment of Additional Data to an

Inspection Lot
Use
You can use this Business Add-In to display data in an inspection lot via additional subscreen areas, and
to change the inspection lot data of the structure QALS_ADDON.
This BAdI is filter-dependent. You can maintain a user-specific implementation for each inspection lot
origin.
Several subscreen areas are available for implementation in this BAdI. Depending on the inspection lot
origin for which you wish to implement the BAdI, you select the required subscreen areas.
The following subscreen areas are available for implementation:
SAPLQPL1 201 SUBSCREEN_ADDON QALS_ADDON Data (Vendor)

Implement this subscreen in your BAdI implementation for the inspection lot origins 01, 05, 07, 08, 09,
and 15.

(Customer)
______________________________________________________________
SAP AG 353
______________________________________________________________
SAP System
Implement this subscreen in you BAdI implementation for the inspection lot origins 02, 06, 10, 11, and
12.

(Production)
Implement this subscreen in your BAdI implementation for the inspection lot origins 03, 04, 13, and 14.
SAPLQPL1 208 SUBSCREEN_ADDON QALS_ADDON Data (Stabi)

An active implementation is already delivered for inspection lot origin 16 (stability study). Use this
active implementation as a template for your user-specific implementation.
SAPLQPL1 212 SUBSCREEN_ADDON QALS_ADDON Data (Origin

89)
Implement this subscreen in your BAdI implementation for the inspection lot origin 89.
All of the subscreen areas mentioned above are only active in the change transaction for the inspection
lot. A different subscreen area (see below) is required for the display transaction (QA03). If you have
accessed the inspection lot using the change transaction, you can also change the data of the structure
QALS_ADDON using the subscreen areas.
SAPLQPL1 301 SUBSCREEN_ADDON QALS_ADDON Data (Display

Mode)
This subscreen area is always available when displaying an inspection lot. It is independent of the
inspection lot origin. Implement this subscreen area with every implementation if you want to be able to
display additional data in the display transaction for the inspection lot.
To implement the methods of this Business Add-In, you can either use the sample coding delivered by
SAP as a template, or use the active implementation for the filter value 16 as a template.
If all subscreens are implemented, the following additional data is available:
QALS Inspection lot record
RMQEA Screen fields for processing of the inspection lot
MODUS Change mode (A = Create, B = Change, Z = Display)

In change mode, you can use the method PT_DATA_PAI of your subscreen implementation to return the
changed QALS_ADDON Data to the inspection lot.
23.10.3.6.7.9 Business Add-In for Checking Inspection Type in Testing

Schedule
Use
You can use this Business Add-In to make your own check of the chosen inspection type in the schedule.
______________________________________________________________
SAP AG 354
______________________________________________________________
SAP System
The schedule for the stability study defines for every storage condition (reference object "physical
sample") with which inspection type the inspection lots should be generated, that emerge as maintenance
call objects using the maintenance plan scheduling.
The inspection type must be maintained in Customizing of Quality Management for Origin 16
(inspection lot for stability study).
Ensure that you assign an inspection lot for which the default values are maintained in Customizing in
Quality Management. These are read as the current settings for inspection generation. This means that
the system does NOT read the active inspection type in the inspection settings of the material master.
SAP delivers an active implementation in a PLM Add-On. This checks whether
- The inspection type for origin 16 is maintained

- The default values for the inspection type are maintained
Use this active implementation as a template for your internal implementation
Requirements
For your active customer implementation to run through, you must set the switch for selecting the
BAdI implementation under Business Add-Ins to Customer Implementation for the BAdI in
Customizing for Quality Management.
The BAdI interface gives you the inspection lot origin and the selected inspection type.
Activities
23.10.3.6.7.10 Business Add-In for Displaying Testing Schedule Data on

Subscreen
Use
You can use this Business Add-In (BAdI) in the object subscreen 0170 for the physical sample (storage
condition) in the schedule for the stability study using an additional BADI subscreen area to display
further data on storage conditions.
Requirements
This BAdI can only be implemented in a schedule for a stability study.

An active SAP implementation was already delivered.
This implementation displays the following data on the physical sample (storage condition) on the detail
screen for the schedule item:
- Status of the physical sample

- Material number and the short text for the material number
- Batch number
- Plant and short text for the plant
- Primary packaging and short text for the primary packaging
______________________________________________________________
SAP AG 355
______________________________________________________________
SAP System
- Storage condition and short text for the storage condition
Standard settings
If you want to make your own implementation of this BAdI, then perform the following steps:
- Create an implementation for the filter value 1 (customer implementation). Use the existing SAP
implementation as a template for your implementation. Activate your implementation.
- In QM Customizing for the stability study, use the activity "Switch for selecting the Business Add-
In implementation" to switch the origin for this Business Add-In to "Customer Implementation".
Activities
23.10.3.6.7.11 Business Add-In for Display of Data for Results Recording on

Subscreen
Use
This Business Add-In allows you to display additional data in a subscreen of the header data (screen
5000 in function group QEEM) in the transactions for results recording (Create, Change, Display). You
can also call up another function by choosing a pushbutton on this screen.
The relevant entries in the tables QALS, QALT, QAPO, and QAPP for the existing inspection lot are
available in the Business Add-In.
Requirements
If a customer-specific pushbutton is to be implemented on the subscreen for the header data in results
recording using this Business Add-In, the FCODE used must begin with the following
characters:
+BADI5000
Example
You can use this Business Add-In, for example, to supplement the header area of the results recording
PROCESS_OK_CODE.
______________________________________________________________
SAP AG 356
______________________________________________________________
SAP System
call the stability history in the header data of screen 5000 for function group QEEM (results recording).
QEEM_SUBSCREEN_5000 is read, and the data in QALS, QALT, QAPO, and QAPP is transferred
(method GET_DATA).
23.10.3.6.7.12 Business Add-In for Display of Data for Usage Decision on

Subscreen
Use
This Business Add-In allows you to display additional data in a subscreen of the header data
(screen 1101 in program SAPMQEVA) in the transactions for the usage decision (Create, Change,
Display). You can also call up an additional function by choosing a pushbutton on this screen.
The relevant entries in table QALS and in structure RQEVA for the existing inspection lot are available
in the Business Add-In.
Requirements
If a customer-specific pushbutton is to be implemented on the subscreen for the header data in the usage
decision using this Business Add-In, the FCODE used must begin with the following characters:
+BADI1101
Example
You can use this Business Add-In, for example, to supplement the header area of the usage decision
PROCESS_OK_CODE.
______________________________________________________________
SAP AG 357
______________________________________________________________
SAP System
call the stability history in the header data of screen 1101 for program SAQMQEVA (usage decision).
In the PBO of the new screen, the adapter class of the instance for BADI QEVA_SUBSCREEN_1101 is
read, and the data in QALS and RQEVA is transferred (method GET_DATA).
23.10.3.6.7.13 Business Add-In for Quantity Check in Stability Study
Use
This Business Add-In (BAdI) is used in the Stability Study (QM-ST) component. You use this BAdI to
create your own check routines for maintaining building blocks in transaction QST09.
These checks in the method of the BAdI are called in the SAVE event. The BAdI uses the following
method:
- CHECK_QUANTITY
Standard settings
The BAdI is not dependent on a filter and cannot be used multiple times.
Activities
Implement the method of the BAdI.

See also
The BAdI uses the interface IF_EX_STABI_BUILDING_BLOCK. For more information, see the
documentation for the method.
23.10.3.6.8 Quality Control 23.10.3.6.8.1 BAdI: Data Summarization when

Evaluating Original Documents
Use
This Business Add-In (BAdI) can be used to implement the processing and summarization of data based
on the freely-definable aggregate structure.
This BAdI is also used to define and execute the selection and export of the data.
Requirements
______________________________________________________________
SAP AG 358
______________________________________________________________
SAP System
The aggregate structure must satisfy the following conditions:
1. The first element is an include of the structure QGEVAL_NODE_KEYS.

2. A structure of the group KPI is included at the end of the aggregate structure. This contains all
fields that are not used for grouping purposes and contain key figures.
3. A structure of the group INFO is included at the end of the aggregate structure. This contains all
fields that are not used for grouping purposes, but to display additional information.
Activities
Create your own implementation for a new filter type.

Use the function module QG_EVAL_START_EVALUATION so that you can use the filter type in the
program of transaction QGA4.
Example
The data type 001 with the aggregate structure QGEVAL_INSPECTION_LOTS, as supplied by SAP,
can be used as an example for your own implementations.
See also
This BAdI uses the interface IF_EX_QG_EVAL_MANAGER. For more information, call up the
interface in the class builder.
23.10.3.6.8.2 BAdI: Definition of Views for Evaluations of Original Documents

Use
You can use this Business Add-In (BAdI) to implement views for use in the transaction for general QM
evaluations.
An implementation can support several view types.
Requirements
The filter value is an implementation type, which you must redefine in Customizing.
Standard settings
Use the implementations supplied by SAP.
Activities
See also
______________________________________________________________
SAP AG 359
______________________________________________________________
SAP System
This BAdI uses the interface IF_EX_QG_EVAL_VIEWTYP. For more information, call up the interface
in the class builder.
23.10.3.6.8.3 BAdI: Thin Out List from Batch Where-Used List
Use
This Business Add-In (BAdI) is used in the Quality Management component.

Using this BAdI, you can change lists that result from the batch where-used lists as part of the QM
evaluation.
Standard settings
The BAdI default implementation filters the results of the batch where-list, so that only entries that
represent batches from the preliminary products remain.
Example
Sometimes, as part of your operating schedule, more than one batch from the same component is
included in a production order (from a tracking view, this is a batch split). However, you do not want to
check all batches according to characteristic data; you only want to check certain batches, such as
batches that you can find yourself by name.
See also
Method
23.10.3.6.8.4 BAdI: Process Data Nodes When Evaluating Original Documents

Use
This Business Add-In (BAdI) is used in the Quality Management component.
You can use this BAdI to change individual data nodes in the data tree of the QM evaluation cockpit. The
BAdI includes two methods:
- You can hide data nodes using the CHANGE_VISIBILITY method.

- You can calculate your own key figures for the data nodes using the CALCULATE_KPI method.
You can create BAdI implementations, depending on data category filters (inspection lot data,
notification data, component data) and the data node category.
Example
______________________________________________________________
SAP AG 360
______________________________________________________________
SAP System
You can hide all inspection lot nodes that have a quality score higher than a limit that you have defined.
You can analyze PPM values and quality costs. See example implementation.
23.10.3.7 Distribute ALE Master Data
In this step, you define the controls for the ALE distribution of QM master data.
Here, a distinction is made between the initial distribution and a change distribution.
Example
An ALE distribution is possible for the following master data in the QM component:
- Inspection setup for the material

- Inspection method
- Catalog/code group
Requirements
The systems involved are already prepared for the ALE. The logical systems involved must be defined.
Standard settings
The standard system is also already prepared for the distribution of QM master data, as far as possible.
Recommendation
The technical ALE settings are normally made for several application components in the SAP system and
not just for the QM application component. Therefore, for details on ALE distribution, see the general
documentation for ALE, in particular the ALE Implementation Guide.
Have an expert, who has experience of ALE in the SAP system make the required settings.
Activities
General settings
a) Check whether the general settings for the distribution of QM master data exist. These settings
are required for the initial distribution and the change distribution. For general information,
see the ALE Implemetation Guide, sections "Distribution Model" and "Configuring Systems
in a Network".
Note: Data is distributed in Quality Management using BAPIs (special function modules).
Since a different technology is used than with the distribution of material master data, you
must maintain your own model view in the distribution model. The distribution model must
be maintained. This involves at least one model view for the BAPI "SaveReplica" for the
affected objects. You specify the source and target system in the model view. The following
objects are involved:
Object Usage
MatInspectionControl Inspection setup for material
InspectionMethod Inspection method
______________________________________________________________
SAP AG 361
______________________________________________________________
SAP System
MasterInspectionChar Inspection characteristic
CodeGroup Catalog/code group
b) If required, you must also maintain a dependency between the "SaveReplica" method and a
message type (for example, MATMAS)(transaction BD48). Such dependencies are not
normally required.
This dependency affects receiver determination for the BAPI. The receiver determination only
finds receivers that are allowed or planned for the BAPI or the assigned message type. For
example, if a BAPI is assigned to the message type MATMAS, it is no longer possible in the
distribution model for this BAPI to enter a filter for the material as an object value.
c) You must also generate a partner profile for the model view, if this has not already been done
by other applications that use ALE. You create this profile in the distribution model as
described above in a).
d) You must also define the target systems for RFC calls , if this has not already been done by
other applications that use ALE.
e) You must maintain a process code in the inbox, if this has not already been done by other
applications that use ALE (transaction WE42). The standard value for the distribution with the
BAPI is the process code BAPI. A function module is assigned to this process code (in the
standard, BAPI_IDOC_INPUT1). The system uses the following message types to find and
call a suitable function module in table TBDME:
Message type Usage
MATQM Inspection setup for material
QSMT Inspection method
QPMK Inspection characteristic
QPGR Catalog/code group
f) You must maintain an inbound and outbound parameter for the message types, if this has not
already been done by other applications that use ALE (transaction WE20). For the relevant
logical systems (sending and receiving systems), you must also maintain the corresponding
message type with its basic type and receiver port (-> partner profile) in the inbound and
outbound parameters. You must enter the process code. The default value is BAPI.
Settings for the distribution of changes
The procedure is dependent on whether change documents can be written automatically for objects that
should be distributed using ALE.
1. Changing the inspection setup for the material

Change documents are written for the the inspection setup of the material. Check whether the
settings for the change distribution have been defined and if the QM component has been taken into
account in these settings. Perform the following steps:
a) The writing of change pointers/indicators (or change documents) must be active in the general
system settings.
b) Activate the change pointers for each individual inspection setup of a material. For this, all
fields from the "inspection setup" table (QMAT) must be entered in the distribution table
"DQMAT" for the message type MATQM.
c) Activate the writing of change pointers for the corresponding message type.
d) Maintain the additional data for the message type. Select the relevant message type in this
table and process the related data. Enter the function module, (here:
MASTERIDOC_CREATE_SMD_MATQM), which prepares both the change pointers and
the data to be sent using IDOCs.
______________________________________________________________
SAP AG 362
______________________________________________________________
SAP System
2. No change documents are written for master inspection characteristics, inspection methods, and
code groups. The changes are distributed in the following way:
a) In the default settings at client level, you set the indicator Distribute master inspection
characteristic, Distribute inspection method, or Distribute code groups.
Further notes
Data is distributed using ALE because of the following problems:
- If you send data from the source system to the target systems, data in the target system with the
same key may be overwritten. The system does not take into consideration, whether the data in the
target system is:
- Already in use
- More up-to-date than in the source system
- The system also sends data that has not been released from the source system to the target systems.
This means, that the status is also not taken into consideration.
Take measures to prevent any unwelcome effects from these factors.
- Create strict master-slave relationship for responsibilites in the source system and target systems
using organizational tasks. Make a clear distinction between responsibilities by marking the
authorizations accordingly. You can find details in the steps, user authorizations and authorization
groups.
- Avoid changing data records in the source system. Instead, create new data records or new versions
of data records.
23.10.3.8 Communication with Quality Inspection Engines
23.10.3.8.1 Assign Properties
Use
You can use SAP's Quality Inspection Engine (QIE) to perform quality inspections while using a
combination of different SAP solutions or even non-SAP applications. Other systems consumer systems
- deliver data to the QIE for the inspection. From the QIE, you can transfer inspection requests to Quality
Management (QM) in the existing system and then use additional functions, for example,
characteristic-based results recording. It is possible that the properties of the inspection object types will
have different descriptions in the different systems.
In this IMG activity, you define neutral codes for these properties. The system then uses these neutral
codes to exchange property values between the different systems.
Instead of the QIE, you can also use an external QM system with a similar range of functions.
Example
One property that is frequently transferred by consumer systems is the material number. In Supply Chain
Management (SCM) systems, this is known as the product number.
______________________________________________________________
SAP AG 363
______________________________________________________________
SAP System
23.10.3.8.2 BAdI: Creation of Inspection Lots for Externally Triggered
Inspection
Use
This BAdI enhances the creation functions for inspection lots for externally triggered inspections, that is
for inspection lots with the origin 17 (external inspection). You can use this BAdI to transfer your own
data from the external inspection document and from the external samples into the inspection lot and the
samples that were created in the SAP system when the inspection document was created and released in
the external system.
This BAdI is called in the function module QPLEXT_INSPECTION_LOT_CREATE.
Requirements
You have made the Customizing settings required for external inspections. In addition, you should check
if the following settings exist:
- Check if the inspection type 17 (inspection from external system) supplied by SAP, or a customer
inspection type for the origin 17 exists under Maintain Inspection Types.
- Check if an entry for the inspection type exists under Maintain Inspection Lot Origins and Assign
Inspection Types.
- Check if a number range exists for the origin 17 under Maintain Number Ranges.
- Check if an entry exists for the inspection type under Define Default Values for
Inspection Type.
- Check if the sample type 10 (sample from external inspection) supplied by SAP exists under
Define Physical-Sample Types.
- Check if a number range exists for the sample type 10 under Define Number Range.
- Check if the screen control key 07 (external inspection) supplied by SAP is available under
Maintain Screen Control Keys for Sample Types.
Standard settings
For more information about the standard settings (filters, single or multiple uses), see the Properties tab
in the BAdI Builder (transaction SE18).
- CL_DEF_IM_QPLEXT_LOT_CREATE
The system runs the existing standard implementation automatically (see Note 1947572). For a
customer-specific implementation, proceed as described under Activities. After a customer-specific
implementation is activated, the standard implementation is no longer taken into consideration. If
you want the standard implementation to be run for the customer-specific implementation, you can
use the example implementation as a template.
Example
You can find example implementations in the BAdI Builder on the Interface tab.
The following example implementations exist:
______________________________________________________________
SAP AG 364
______________________________________________________________
SAP System
- CL_EXM_IM_QPLEXT_LOT_CREATE
In the existing example implementation, the determination of the related document
references for an inspection lot is implemented (see Note 1956479). The standard implementation is
taken into consideration in this example implementation.
Activities
implementation.
field.
implementation.
8. Choose Activate.
See also
Methods
Transfer of Individual External Fields
23.10.3.8.3 BAdI: Change of Inspection Lots for Externally Triggered

Inspection
Use
This BAdI enhances the change functions for inspection lots for externally triggered inspections, that is
for inspection lots with the origin 17 (external inspection). You can use this BAdI to transfer your own
data from the external inspection document and from the external samples into the samples that were
created in the SAP system when the external inspection document was changed and released.
This BAdI is called in the function module QPLEXT_INSPECTION_LOT_CHANGE.
______________________________________________________________
SAP AG 365
______________________________________________________________
SAP System
Requirements
Inspection Types.
- Check if an entry exists for the inspection type under Define Default Values for Inspection Type.
Standard settings
For more information about the standard settings (filters, single or multiple uses), see the Properties tab
in the BAdI Builder (transaction SE18).
- CL_DEF_IM_QPLEXT_LOT_CHANGE
The existing standard implementation is run as standard (see Note 1947572). For a customer-
specific implementation, proceed as described under Activities. After the customer-specific
implementation is activated, the standard implementation is no longer taken into consideration.
Activities
implementation.
field.
implementation.
______________________________________________________________
SAP AG 366
______________________________________________________________
SAP System
8. Choose Activate.
See also
Methods
Transfer of Individual External Fields
23.10.3.8.4 BAdI: Copying of Inspection Decisions for Externally Triggered

Inspection
Use
This BAdI enhances the copy functions for inspection decisions for externally triggered inspection, that
is, inspections with the origin 17 (external inspection). You can use this BAdI to transfer own data from
a Quality Management (QM) inspection decision in the SAP system to an inspection document in the
external system.
This BAdI is called in the function module QPLEXT_INSP_DECISION_REPLICATE.
Requirements
Inspection Types.
- Check if an entry exists for the inspection type under Define Default Values for Inspection Type.
Standard settings
This BAdI is not active in the standard system. The BADI is not designed for multiple use. The BAdI is
filter-dependent. Create implementations for the required inspection types.
Activities
______________________________________________________________
SAP AG 367
______________________________________________________________
SAP System
implementation.
field.
implementation.
8. Choose Activate.
See also
Methods
Transfer of Internal Fields
23.10.3.8.5 Activate Event Type Linkage for Confirmations
Use
In this IMG activity, you activate event type linkage so that the system can send confirmations from SAP
to the Quality Inspection Engine (QIE) or to another system. The existing system sends these
confirmations if it has executed the following activities based on external data received from the QIE or
from the other system:
- It has created an inspection lot.

- It has changed an inspection lot.
- It has deleted an inspection lot.
- It has started recording results.
Activities
In transaction Type Linkages, activate event type linkage for the following events for the object type
BUS2045:
- CREATED
______________________________________________________________
SAP AG 368
______________________________________________________________
SAP System
- CHANGED
- CANCELED
- RESULTSRECORDINGSTARTED
Example
If you use SAP's QIE, a corresponding system status is set for the relevant inspection document when a
confirmation is received by the system. If a confirmation is not sent, because an event type linkage is
missing, the system status will not be set. This can lead to errors in the existing system if the inspection
document is changed in the QIE. It is therefore important that you activate event type linkage.
23.10.3.8.6 Activation of Events for Transferring QM Data in Procurement
23.10.3.8.6.1 Event Type Linkage for QM Data in Procurement
Use
In this IMG activity, you activate event type linkage so that the system can send QM data from the Q-
info record to an EWM system in conjunction with an SAP Quality Inspection Engine (QIE).
The transfer of data from the Blocking Function and Inspection Control fields from the Q-info
record is triggered by the following events:
- A Q-info record was created.

- A Q-info record was changed or the deletion indicator was set.
Requirements
You also need to execute the IMG activity Activate BTE Application so that the data is transferred in
full.
Standard settings
If you are using an EWM system with SAP's QIE, inspection rules are created or adjusted based on the
Q-info records transferred.
The data transfer is logged in transaction SLG1 in an application log:
- In the S/4HANA system for the object QLEXT, subobject QINF_CREATE_IRULE

- In the EWM system for the object QIE, subobject IRULEDISTR
Activities
Activate event type linkages for the object type BUS2101 for the following events:
- CREATED
- CHANGED
______________________________________________________________
SAP AG 369
______________________________________________________________
SAP System
The data transfer is performed using the report RQBAAEXT. To find out which data is transferred, see
the report documentation.
23.10.3.8.6.2 Activation of BTE Application
Use
In this IMG activity, you activate applications to send QM data from the material master to an EWM
system in conjunction with a Quality Inspection Engine (QIE) of SAP via Business Transaction Events.
The transfer of QM data for procurement from the QM view of the material master record is triggered by
the following events:
- The setting for the QM Procurement Active indicator in the material master was changed.
- The QM control key in the material master was changed.
Requirements
You also need to execute the IMG activity Event Type Linkage for QM Data in Procurement so that the
data is transferred in full.
Standard settings
If you are using an EWM system with SAP's QIE, inspection rules are created or adjusted based on the
Q-info records transferred.
- In the S/4HANA system for the object QLEXT, subobject QINF_CREATE_IRULE

- In the EWM system for the object QIE, subobject IRULEDISTR
Activities
To transfer QM data from procurement in the material master, you need to activate the application
QBEXT:
1. Execute the activity and choose Settings -> Identification -> SAP Applications on the following
screen.
2. Select the Application Active indicator for the application QBEXT.
The data transfer is performed using the report RQBAAEXT. To find out which data is transferred, see
the report documentation.
23.10.3.8.7 Activation of BTE Application for Transferring Manufacturing Order

Data
Use
In this IMG activity, you activate an application to provide data (using Business Transaction
______________________________________________________________
SAP AG 370
______________________________________________________________
SAP System
Events) from the production order or process order in an EWM system, in conjunction with a Quality
Inspection Engine (QIE), for EWM inspection planning. This data can be used in EWM for an early
inspection for the goods receipt from production.
The order data is transferred for the following events:
- The order is released

- A deletion indicator is set for a corresponding order
- In the case of a released order: The fields Batch, Total Quantity, Assignments to Sales Order or
WBS Element, Inbound Delivery Exists, Stock Exists are changed.
Standard settings
With the relevant EWM system settings, an inspection document is created or adjusted based on the order
data transferred if you are using an EWM system with SAP's QIE.
- In the S/4HANA system for the object QLEXT, subobject QIPP_CREATE_INSP

- In the EWM system for the object QIE, subobject INSPECTIONDOCUMENT
Activities
You need to activate the application QBEXTP for the order data transfer:
1. Execute the activity and choose Settings -> Identification -> SAP Applications on the following
screen.
2. Select the Application Active indicator for the application QBEXTP.
Inspection planning is called up in the EWM with the order data using the report RQBPPEXT.
______________________________________________________________
SAP AG 371
412

Quality Management PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Quality Management PDF

Uploaded by

Copyright:

Available Formats

Copyright(c) 2018 by Nixon Vunganai.

All rights reserved.

23.1 BASIC SETTINGS 16

23.1.1 FIRST STEPS 17

23.3 QUALITY PLANNING 36

23.3.1 BASIC DATA 38

23.4 QUALITY INSPECTION 126

23.4.1 INSPECTION LOT CREATION 128

23.5 QUALITY CERTIFICATES 178

23.5.1 CERTIFICATE PROFILE 182

23.6 QUALITY NOTIFICATIONS 204

23.6.1 OVERVIEW OF NOTIFICATION TYPE 205

23.7 QUALITY CONTROL 250

23.7.1 QUALITY MANAGEMENT INFORMATION SYSTEM 251

23.8 TEST EQUIPMENT MANAGEMENT 253

23.8.1 DEFINE LIST VARIANTS 253

23.9 STABILITY STUDY 254

23.9.1 BASIC DATA 254

23.10 ENVIRONMENT 275

23.10.1 SETTINGS 275

RESULTS FUNCTION 333

23.1 Basic Settings

This section provides you with instructions for:

- Applying the Implementation Guide to your system

Recommendation for Using the Implementation Guide

1. Kick-off workshop for the implementation project.

- SAP components that are to be integrated in the QM application component

4. Define the implementation stages:

Proceed in the following sequence:

23.1.2 Setting Up Clients

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

- No cancellations are possible for these transactions!

- QCCC All standard settings

- QCCF (forms QM_*)

- QCCS Sampling systems according to ISO 2859 and ISO 3951

- Inspection characteristics and Inspection methods

- Transporting master data of QM component

- Transporting SAPscript objects

In this step, you can change several central controlling functions.

The parameters have default settings that suit most requirements.

23.1.4 Establish Organizational Units (Plants, ...)

Set up a new plant

- Number ranges for Inspection characteristics and inspection methods

- Inspection planner group

- QM data in the material

- Info-records for controlling QM in procurement

Setting up new company code

- Sender texts for certificates and inspection reports

23.1.5 Maintain Settings at Plant Level

Basic Information / How to Proceed

- You assign these profiles or composite profiles to a user master record.

- Maintain the authorizations

- S_A.CUSTOMIZ Customizing (general)

- Assign the comprehensive profile S_A.CUSTOMIZ to the person responsible for

- Material and plant

- Material master (material)

4. Maintain the QM fields in the material master records.

5. Maintain the quality info records (Q-info records).

6. Maintain the QM fields in the vendor masters.

- Controls for vendor:

- Status management for supply relationships

23.2.1.1 Define Control Keys

In this step, you define the control keys for QM in procurement.

- Defect share estimation procedure 9, A, ... , Z*