SAP Cloud Reference Systems. Scenario Outline. Quality Assurance

Transcription

1 SAP Cloud Reference Systems Scenario Outline

2 Content Scenario Overview Business Scenarios in a Reference System Introduction Typical Usage Process Illustration Usage Example 1: Quality Planning Usage Example 2: Planned Inspection after Production Usage Example 3: Planned Inspection at Goods Receipt Usage Example 4: Planned Inspection at Goods Issue Usage Example 5: Unplanned Quality Inspection Usage Example 6: Quality Analysis 2012 SAP AG. All rights reserved. 2

3 Scenario Overview Business Scenarios in a Reference System Introduction Typical Usage

4 Business Scenarios in a Reference System In a Reference System, you can experience how a business scenario meets specific requirements of a typical midsize company. For hands-on experience, you can take advantage of the business scenario document, which guides you through the process with detailed step-by-step instructions. The following slides outline and illustrate the individual process steps of a business scenario as it has been realized in the model company Almika SAP AG. All rights reserved. 4

5 Introduction Scenario Introduction is an integral part of supply chain management which ensures that products fulfill quality expectations. It comprises all actions necessary to determine whether a product meets predefined quality requirements. The inspection process can be either initiated automatically, such as a planned inspection by manufacturing processes, or manually as an unplanned (ad hoc) inspection. It comprises the following steps: Inspection creation Sample drawing and preparation Results recording Quality decision Detailed analysis for can be used to ensure compliance and increase competitiveness SAP AG. All rights reserved. 5

6 Typical Usage (1 of 6) Quality Planning Quality Planning focuses on setting quality objectives and specifying necessary operational processes and related resources to fulfill them. The Quality Planning work center allows the definition of basic data for the quality standards which are required to plan and execute quality inspections, such as Quality code catalogs: are used to manage, to uniformly define and to standardize information, e.g. in form of defect types or defect locations. The quality code catalog supports the management and evaluation of the qualitative data. Inspection plans: describe the standards, methods, resources and operations of inspections for relevant products, product groups or processes. Quality documents: describe inspection instructions, specifications or inspection results. It can be attached to inspection plans, inspections, check tasks, purchase orders or purchasing contracts. Quality projects: provide comprehensive functionality to develop new products (Advanced Product Quality Planning, APQP) or to significantly improve the quality (Six Sigma) of products and processes SAP AG. All rights reserved. 6

7 Typical Usage (2 of 6) Planned Inspection after Production After creating the production order, an inspection with reference to an inspection plan will be generated. At production order release, the corresponding production lot and production tasks will be created. In parallel, the related inspection will be released and a check task will be created. During inspection processing, findings and results can be recorded. Inspection results can be recorded in the form of notes, attached images, defect codes or measured values. After results recording, the system will determine whether to accept or reject the lot and will propose yield or scrap quantities for production confirmation. To finish a check task and to confirm its quantities, results recording has to be finished. Finally, to complete the inspection, it has to be decided whether the material will be accepted or not. To support defect cause identification and continuous improvement process, a customizable defect analysis and inspection analysis report can be used. These reports show detailed information on recorded defect types, showing the numbers of each defect recorded and classifying defects into categories, for example, time period, location, business partner or product SAP AG. All rights reserved. 7

8 Typical Usage (3 of 6) Planned Inspection at Goods Receipt After posting the goods receipt, an inspection with reference to an inspection plan will be generated. During the inspection processing, findings and results can be recorded. Inspection results can be recorded in the form of notes, attached images, defect codes or measured values. After results recording, the system will determine whether to accept or reject the inspected materials. To complete an inspection, results recording has to be finished and a quality decision has to be done. To support defect cause identification and continuous improvement process, a customizable defect analysis and inspection analysis report can be used. These reports show detailed information on recorded defect types, showing the numbers of each defect recorded and classifying defects into categories, for example, time period, location, business partner or product SAP AG. All rights reserved. 8

9 Typical Usage (4 of 6) Planned Inspection at Goods Issue After posting the goods issue, an inspection with reference to an inspection plan will be generated. During the inspection processing, findings and results can be recorded. Inspection results can be recorded in the form of notes, attached images, defect codes or measured values. After results recording, the system will determine whether to accept or reject the inspected materials. To complete an inspection, results recording has to be finished and a quality decision has to be done. To support defect cause identification and continuous improvement process, a customizable defect analysis and inspection analysis report can be used. These reports show detailed information on recorded defect types, showing the numbers of each defect recorded and classifying defects into categories, for example, time period, location, business partner or product SAP AG. All rights reserved. 9

10 Typical Usage (5 of 6) Unplanned Inspection An unplanned inspection is created manually with or without reference to an inspection plan. This kind of inspection can be used to process and analyze problems during goods receipt (receiving inspections for supplier deliveries, first articles, customer returns, and stock transfers) production (in-process control and final inspections for production) shipping (final inspections for customer shipments) After the results recording, a quality decision has to be made SAP AG. All rights reserved. 10

11 Typical Usage (6 of 6) Quality Analysis Customizable reports for defect analysis and inspection analysis help to identify defect causes and support the continuous improvement process. Quality managers and quality engineers can access these reports to quickly survey critical defects and characteristics in the work center Quality Control out of the Reports view. Defect Analysis Report This report shows detailed information on recorded defect types, showing the numbers of each defect recorded, and classifying defects into categories, for example, product, business partner, location or time period. Inspection Analysis Report This report shows detailed information on processed inspections, such as quota information, for example, the skip quota, total number information, such as the number of rejected inspections per month, and average value information, such as the average quality score SAP AG. All rights reserved. 11

12 Process Illustration Usage Example 1: Quality Planning Usage Example 2: Planned Inspection after Production Usage Example 3: Planned Inspection at Goods Receipt Usage Example 4: Planned Inspection at Goods Issue Usage Example 5: Unplanned Quality Inspection Usage Example 6: Quality Analysis

13 Quality Planning Process Role Work center Form Financial Posting Create Quality Code Catalog Create Inspection Plan Set up Production Model The quality engineer creates a quality code catalog with a respective catalog structure, including quality codes used for inspection. Quality Engineer The quality engineer creates an inspection plan with a certain combination of key parameters for the inspection of a certain product. Quality Engineer To enable the quality inspection during production, a quality check operation has to be included into the bill of operation structure of the production model. To enable quality inspection in warehouse, the option Autonomic Inspection has to be set for the inspection process of the logistics model. Quality Engineer Quality Planning Quality Planning Planning and Production Master Data 2012 SAP AG. All rights reserved. 13

14 Planned Inspection after Production (1 of 2) Process Role Work center Form Financial Posting Create/Release Production Proposal Check/Release Production Order Stock Overview Confirm Production Task Record Inspection Results The supply planner creates a production proposal and releases it for production. The production planner checks and releases the production order. The warehouse manager checks if there is enough stock on hand for the components to start production. The production operator confirms quantities for the components as planned and finishes the production task. The inspector executes the task of the operation type check. He records the inspection results, confirms the quantities and finishes the task. Supply Planner Production Planner Warehouse Manager Production Operator Quality Engineer Supply Planning Production Control Internal Logistics Execution Execution Production Tasks (type make & check ) Check task Sample Drawing Instruction Inspection Instruction Inspection Results 2012 SAP AG. All rights reserved. 14

15 Planned Inspection after Production (2 of 2) Process Role Work center Form Financial Posting Complete Inspection Complete Production Lot The inspector checks the data of the material inspection and finally decides about the quality of the produced material. The production planner reviews all production related data and closes the production lot. Quality Engineer Production Planner Quality Control Production Control 2012 SAP AG. All rights reserved. 15

16 Planned Inspection at Goods Receipt Process Role Work center Form Financial Posting Create Purchase Order Post Goods Receipt Record Inspection Results and Quality Decision Goods Movement Review Quality Levels The supply planner calls the buyer about additional demand of goods purchased to stock. The buyer creates the purchase order manually. The warehouse manager maintains the delivered quantity and posts the goods receipt using data from supplier delivery. The ship-to location is set by system default. The inspector records the inspection results and confirms the number of inspected samples. Finally, he decides about the quality of the inspected material. The warehouse manager performs the goods movement from the inspection storage to the warehouse. The inspector reviews the defect analysis report for defect cause identification and continuous improvement after inspections. Buyer Warehouse Manager Quality Engineer Warehouse Manager Quality Engineer Purchase Requests and Orders Inbound Logistics Quality Control Internal Logistics Quality Control Sample Drawing Instruction Inspection Instruction Inspection Results 2012 SAP AG. All rights reserved. 16

17 Planned Inspection at Goods Issue Process Role Work center Form Financial Posting Create Sales Order Based on the sales quote, the sales representative creates a sales order. Release Sales Order for Delivery The supply planner reviews the customer demand generated by the sales order and releases the demand. Post Goods Issue and Start Inspection Process The warehouse manager posts the goods issue and the system automatically creates an outbound delivery and a new inspection at the same time. Sales Representative Supply Planner Warehouse Manager Sales Orders Outbound Logistics Control Outbound Logistics 2012 SAP AG. All rights reserved. 17

18 Unplanned Inspection (with/without reference to inspection plan) Process Role Work center Form Financial Posting Create New Inspection (with or w/o reference) The warehouse manager manually creates a material inspection with or without reference to an inspection plan. Record Inspection Results and Usage Decision The quality engineer records the inspection results and confirms the number of inspected samples. Finally, he decides about the quality of the inspected material. Warehouse Manager Quality Engineer Inbound Logistics Quality Control Inspection Sample Drawing Instruction Inspection Instruction Inspection Results 2012 SAP AG. All rights reserved. 18

19 Quality Analysis Process Role Work center Form Financial Posting Evaluate Defect Analysis Evaluate Inspection Analysis The quality engineer reviews the defect analysis report for defect cause identification and continuous improvement after inspections. The quality engineer reviews the inspection analysis report for defect cause identification and continuous improvement after inspections. Quality Engineer Quality Engineer Quality Control Quality Control 2012 SAP AG. All rights reserved. 19

20 2012 SAP AG. All rights reserved 2012 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/vm, z/os, OS/390, zenterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, purescale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the United States and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries. Oracle and Java are registered trademarks of Oracle and its affiliates. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems Inc. HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Apple, App Store, ibooks, ipad, iphone, iphoto, ipod, itunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc. IOS is a registered trademark of Cisco Systems Inc. RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited. Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc. INTERMEC is a registered trademark of Intermec Technologies Corporation. Wi-Fi is a registered trademark of Wi-Fi Alliance. Bluetooth is a registered trademark of Bluetooth SIG Inc. Motorola is a registered trademark of Motorola Trademark Holdings LLC. Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, ianywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company. Crossgate, m@gic EDDY, B2B 360, and B2B 360 Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG SAP AG. All rights reserved. 20