2714 increase your business value with standard enhancements for sap qm
DESCRIPTION
qmTRANSCRIPT
-
Getting More Out of SAP QM
Increase your business value with
standard enhancements for SAP QM
Ingo Panchyrz, QM Product Management, SAP AG
May 2012
Session Code: 2714
-
2011 SAP AG. All rights reserved. 2
Primary Goals
1. Get a sneak peak on enhancement options in different areas of Quality Management
with SAP ERP.
2. Discover how to common enhancements can look like by touring a demo.
3. Get a concrete list of ideas on how to fulfill common user requirements via
customer-specific enhancements.
-
2011 SAP AG. All rights reserved. 3
Agenda
inspection lots
quality notifications
Wrap-up and Questions
General options for getting the best out of your ERP system
quality certificates
quality evaluations
Tips and Tricks on
-
2011 SAP AG. All rights reserved. 4
Options for Enhancing Your System w/o Modification
Customer Exits
Menu Exits
Screen Exits
Program Exits
Customizing
Adjust System
Assign Own Function Modules
Field Selection
.
Business Add-Ins (BAdIs)
Classic Business Add-Ins
Enhancement Framework
Personalization
Simplifying Navigation and Transactions
Customer Developments
Customer-Specific Programs / Reports
Activation of a Business Function (Transaction SFW5 OPS_QM*)
-
2011 SAP AG. All rights reserved. 5
Tips and Tricks on Quality Certificates Examples for Optimizing the Certificate Process
Lance has identified two issues in the
process of incoming certificates that can
be optimized.
-
2011 SAP AG. All rights reserved. 6
Use Case Quality Certificates
Incoming certificates should electronically be transmitted as a PDF document
and confirmed by the system.
Inspection results of the incoming certificate should automatically be copied into
the goods receipt inspection lot.
-
2011 SAP AG. All rights reserved. 7
Incoming Quality Certificates Business Process
Certificate
included?
Send
Reminder
Attach
Certificate
Update
Inspection Lot
Status (OK)
Update
Inspection Lot
Status (not OK)
Create
Certificate
Record
Usage decision
can be made
Usage decision
blocked
Yes No
End
Goods Receipt
-
2011 SAP AG. All rights reserved. 8
Goal: Electronic Certificate Transmission in order to
improve Transparency and Traceability
Order
Delivery
Certificate
Creation
Goods Issue
Purchase
Order
Vendor
Certificate Certficate Record
Optional:
Results
Transfer
Goods
Receipt
Inspection
Lot
Update Status
-
2011 SAP AG. All rights reserved. 9
Improved Process for Incoming Quality Certificates -
Solution Approach
Incoming Certificate with PDF and Results Transfer
SAP Enterprise Release 4.6C
Master Data, Customizing, (potentially Data Mapping), IDOC, Workflow
-
2011 SAP AG. All rights reserved. 10
Quality Certificates Electronic Transmission How does it Look Like
Inspection lot status is automatically updated.
Certificate is transmitted as PDF document and
attached to the quality certificate record.
Quality certificate record is automatically
updated with the goods receipt.
-
2011 SAP AG. All rights reserved. 11
Quality Certificates Transfer of Inspection Results How does it Look Like
-
2011 SAP AG. All rights reserved. 12
Quality Certificates - Electronic Transmission
Solution Approach, Part 1
Technical Implementation
Prerequisites (Target System)
Inspection Plan with Master Inspection Characteristics (orgin results data 07 Quality Certificate Transmission must be set).
Material Master QM View: QM in Procurement must be active > Control Key - Certificate is required.
Q-Info Record in Procurement Certificate control 1 Electronic certificate with PDF
and data transfer.
Idoc = Message Type QCERT Customizing Logical System Customizing Port Customizing Partner (Idoc)
Process Code QCERT_IN Activate Workflow Template
-
2011 SAP AG. All rights reserved. 13
Quality Certificates - Electronic Transmission
Solution Approach, Part 2
Technical Implementation, continued
Prerequisites (Source System)
Create Certificate Profile (Transaction QC03). Define Mapping: Either by using the certificate profile or by using transaction QCE2
(partner dependend).
Define Certificate Recipient (Transaction VV22) - Medium = 6 (EDI). Idoc = Message Type QCERT Customizing Logical System Customizing Port Customizing Partner (Idoc)
Process Code QCERT_OUT Activate Workflow Template
-
2011 SAP AG. All rights reserved. 14
Tips and Tricks on Inspection Lots Examples for Optimizing the Inspection Process
Michael has identified six process steps along
the inspection lot lifecycle that can be optimized.
-
2011 SAP AG. All rights reserved. 15
Use Case Quality Inspection
Michael Meyer wants to implement a 4-Eyes-Principle within results recoding.
When changing a result, the reason of change has to be documented.
An additional button within in the usage decision transaction should be used.
The quantities to be released by an inspection lot should be recorded in the
alternative unit of measure.
Send an inspection report automatically when making a usage decision.
Results should be copied from a preceding inspection.
-
2011 SAP AG. All rights reserved. 16
Improved Inspection Process - Solution Approach
4-Eyes-Principle
SAP Enterprise Release 6.0, EhP 3
BAdI Defintion BADI_QEEM_CLOSE_CHARACTERISTIC
Reason of Change
SAP Enterprise Release 4.70, Extension 1.10
BAdI Defintion QE_SAVE, OSS Note # 653965
Buttons/Subscreen in UD
SAP Enterprise Release 4.70, Extension 1.10
BAdI Defintion QEVA_SUBSCREEN_110
Alternative Unit in UD
SAP Enterprise Release 4.70, Extension 2.00
BAdI Defintion QEVA_ALT_QTY_INPUT
Send Inspection Report via Follow-Up Action
SAP Enterprise Release 6.0
Customizing and Follow-Up action for UD
BAdI Defintion QG_INSP_RESULT_PRINT
Copy Inspection Results
SAP Enterprise Release 4.70, Extension 2.00
Customizing and BAdI Implementations
QEC_SELECTION* (Selection)
QEC_MAPPING_* (Mapping)
-
2011 SAP AG. All rights reserved. 17
4-Eyes-Principle Requested Process How does it Look Like
Business Goal
Within results recording an inspection characteristic shall be processed by at
least two different users for valuation and closing.
-
2011 SAP AG. All rights reserved. 18
4-Eyes-Principle
Solution Approach
Technical Implementation
Apply enhancement spot (BAdI) within results recording transactions QEEM_CHARACTERISTIC
SAP provides sample code Checking whether the subsequent user is different from the previous one
Sample code of BAdI includes
Persons who enters results and person who valuates / closes the characteristic must have different users.
Possibility to force completion of a characteristic (do you really want to ).
Customer-specific coding possible.
Enhancement spot can have several parallel implementations.
Does not apply for formula characteristics.
Does not apply for inspection points / physical samples.
-
2011 SAP AG. All rights reserved. 19
Reason of Change - Business Process I
How does it Look Like
-
2011 SAP AG. All rights reserved. 20
Reason of Change Business Process II How does it Look Like
-
2011 SAP AG. All rights reserved. 21
Reason of Change
Solution Approach
Technical Implementation
Described in OSS Note # 653965 (Consulting note).
Use of the BAdI QE_SAVE.
Sample BAdI implementation uses the field: documentation req. in material master (QM view) as trigger.
Use of user exit QEEM0024 (push button in results recording for display of the change
documentation); the same can be applied to the usage decision using QEVA0008.
Business Background
To enter reasons for changes on quality relevant inspection results is an essential GMP requirement for
regulated industries.
Business Process
If an inspection result or another change relevant data is changed by a user, the user must be forced to
enter a reason for his changes. He may not be able to save his changes. A change log must be in place,
where all changed values and change reasons are listed.
Changes can happen any time, independent on the status of the inspection characteristic (valuated,
confirmed or closed) and must be tracked and documented accordingly.
-
2011 SAP AG. All rights reserved. 22
Subscreen / Buttons in UD Transaction
How does it Look Like - Example
Example to show attached documents
Call attachment list (GOS)
-
2011 SAP AG. All rights reserved. 23
Subscreen / Buttons in UD Transaction
Solution Approach
Technical Implementation
Subscreen QEVA_SUBSCREEN_1101 Call GOS attachments via function module e.g. GOS_ATTACHMENT_LIST_POPUP
For an inspection lot documents are assigned as generic documents (GOS). Via a button the attachment list can be called. [Optional: Dynamically display the buttons (e.g. only show button if an an
attachment is avalaible].
Business Process
Please note that function module GOS_ATTACHMENT_LIST_POPUP is not officially
released by SAP.
-
2011 SAP AG. All rights reserved. 24
Alternative Quantity Input within Usage Decision How does it Look Like
1. F4 on quantity field
2. Enter quantity in
allowed unit
3. ENTER
4. Quantity will be
recalculated into lot
unit
Allowed units:
Maintained in material
master
Stock posting in
lot unit only!
-
2011 SAP AG. All rights reserved. 25
Alternative Quantity Input within Usage Decision
Solution Approach
Technical Implementation
Developed via Business Add-In: QEVA_ALT_QTY_INPUT Filter: Inspection type
Example Implementation with help of function group QEVA_ALT_QUANTITY_INPUT Taking the maintained alternative Uoms in the material master into account
Implementation guide: see note 613717 Available with Enterprise Extension 2.00 (EA-PLM) Customer specific implementation possible
Remember: Stock posting in lot unit only!
-
2011 SAP AG. All rights reserved. 26
Follow-Up Action for Usage Decision
How does it Look Like Example
Send inspection report or separate E-Mail
-
2011 SAP AG. All rights reserved. 27
Follow-Up Action for Usage Decision
Solution Approach
Technical Implementation
Implement follow-up action recommended: use reference function module QM10_COPY_REFERENCE_FORM as copy model.
Set up follow-up action in customizing. Assign follow-up action to relevant selected set code. Use BadI QG_INSP_RESULT_PRINT (send inspection report via Email) .
-
2011 SAP AG. All rights reserved. 28
Copy Inspection Results
How does it Look Like
Source Target
Option 1: Copy results automatically during sample
calculation
Option 2: Copy results automatically during results
recording (also manually)
Option 3: Manual selection of an inspection lot during
results recording
Transfer Log can be displayed
-
2011 SAP AG. All rights reserved. 29
Copy Inspection Results
Solution Approach, Part I
Mapping Source Target
Inspection Lot 4711
Operation A
Inspection Point 1 Characteristic 10
Characteristic Value
10 pH-Value
Characteristic Value
10 pH-Value 7,5
Inspection Lot 2
Operation B
Inspection Point 1
Characteristic 10
Characteristic 20
Selection
(BAdI)
Mapping
(BAdI)
Characteristic Value
10 Iron 0,02
20 Viscosity 45
30 pH-Value 7,5
-
2011 SAP AG. All rights reserved. 30
Copy Inspection Results
Solution Approach, Part II
Technical Implementation
The following implementations of BAdIs are available: Selection procedure:
QEC_SELECTION_100 Recurring Inspection of a batch QEC_SELECTION_110 Recurring Inspection of equipment QEC_SELECTION_120 Recurring Inspection for physical samples QEC_SELECTION_200 Inspection Data of the preliminary product by usage of a batch where-used list.
QEC_SELECTION_300 Free selection of the inspection lot, procedure, inspection point
Mapping procedure:
QEC_MAPPING_100 Usage of a task list key QEC_MAPPING_200 master inspection characteristic and method QEC_MAPPING_300 ID of feature
Customizing
-
2011 SAP AG. All rights reserved. 31
Tips and Tricks on Quality Notifications Examples for Optimizing the Notification Process
Peggy has identified six steps within the quality
notification process that can be optimized.
-
2011 SAP AG. All rights reserved. 32
Use Case Quality Notification
Peggy wants to create quality notifications automatically during
production confirmation.
The notification type should be changed after creation.
Digital Signature should be used within notification process.
Multiple objects shall be assigned to a notification item.
Peggy wants to see in the quality notification worklist QM10 if an object has
been assigned.
The notification including attachments should be sent via Email.
-
2011 SAP AG. All rights reserved. 33
Improved Quality Notification Process - Solution
Approach
Autom. Creation of Notifications within Production
SAP Enterprise Release 6.0, EhP 3
Customizing
Change Notification Type
SAP Enterprise Release 6.0, EhP 6
Customizing
Digital Signature for a Notification
SAP Enterprise Release 6.0, EhP 3
Customizing
Enhanced Mail Sending Process
SAP Enterprise Release 6.0, EhP 4
Customizing
Multiple Objects per Notification Item
SAP Enterprise Release 6.0, EhP 4
Customizing
Enhanced Worklist
SAP Enterprise Release 6.0, EhP 4
BADI_EAM_SINGLELEVEL_LIST
-
2011 SAP AG. All rights reserved. 34
Create Q-Notification in Production
How does it Look Like
Defect item codes have to be assigned to
the relevant quantities in customizing.
Notification including defects is automatically created in
the background.
-
2011 SAP AG. All rights reserved. 35
Create Q-Notification in Production
Solution Approach
Technical Implementation Customizing: Production orders: Production Shop Floor Control Operations Confirmation Define Confirmation Parameters
Production orders: Production Shop Floor Control Operations Confirmation Single Screen Entry Define Single Screen Entry
Process orders: Production Planning for Process Industries Process Order Operations Confirmation Define Confirmation Parameters
Process orders: Production Planning for Process Industries Process Order Operations Confirmation Single Screen Entry Define Single Screen Entry
As of SAP ERP 6.0, Enhancement Package 3, you can automatically create a
quality notification for the following confirmation transactions:
Time ticket (single screen entry) using transaction CO11N (production order) or COR6N (process order). Confirmation of production order or process order (order header) using transaction CO15 or CORK.
Business Process
-
2011 SAP AG. All rights reserved. 36
Change Notification Type
How does it Look Like
-
2011 SAP AG. All rights reserved. 37
Change Notification Type
Solution Approach
Technical Implementation
Possible via standard QM transactions Create Notification (QM01) and Change Notification
(QM02), but under certain circumstances also in the simplified notification processing, i.e. via the non-QM-specific notification transactions (IQS21 and IQS22).
Prerequisites
You have authorization to perform the extended change for the current notification type (authorization object Extended Change of Notification Type B_NOTIF_EX).
In QM Customizing settings are defined specifying which combinations of quality notification types allow an extended change (origin and target).
The original notification type and the target notification type must have the same notification category (Quality Notification).
The notification does not yet have the status Notification Completed. This also applies if the notification was reset to the status Notification in process after being completed.
The notification does not have the status Defects Recording.
Comments
System does not assign a new notification number on change of the type. Changes are also reflected in QMIS and related notifications function (i.e. data is updated).
-
2011 SAP AG. All rights reserved. 38
Digital Signature within Quality Notification Process How does it Look Like
Example: Step Put notification into process requires a signature
-
2011 SAP AG. All rights reserved. 39
Digital Signature within Notification Process
Solution Approach
Technical Implementation
Business Goal
When processing a notification within SAP ERP, digital signatures are required for distinct steps. It
shall be possible to provide them with status change and when performing distinct activities at header
or task level. Also signature strategies shall be allowed.
New system status in the notification indicate the signature status:
DSAC
Digital Signature Process active DSCL
Digital Signature Process completed
New customizing functions for notifications
New functions during notification processing
The signature can be activated for
Notification type and business transaction
For header or task level
Synchronously or asynchronously
With strategy assignment
-
2011 SAP AG. All rights reserved. 40
Sending Mail with Attachments Process
Quicker processing and enhanced usability
Avoiding of manual effort
Automatic proposal of assigned partners and attached documents
Guidance through the sending procedure
Flexible selection of additional recipients and documents
Clear documentation of transmission
Improved information flow
Need to send out notification data and attachments separately
Lack of information
Additional manual steps
Create Q-
Notification to
record quality issue
during production
Attach documents
to describe current
situation, assign
partners
Send notification
with attachments
via e-mail to all
partners to inform
Perform CAPA
process
Current Business Challenge Value of new Approach
Sales Clerk
QA Person
-
2011 SAP AG. All rights reserved. 41
Sending Mail with Attachments
How does it Look Like
New follow-up action
for mail sending
Dialog to select relevant attachments
Dialog to select relevant recipients
Automatic proposals
of recipients and
attachments
Documentation of the
transmission
-
2011 SAP AG. All rights reserved. 42
Sending Mail with Attachments
Solution Approach
Technical Implementation
Function modules and customizing settings are described in OSS-Note 1375654 Sending E-Mail with Attachments: Activating
-
2011 SAP AG. All rights reserved. 43
Multiple Objects at Item Level
How does it Look Like, Part I
(scroll down)
Multiple assignments of objects to a notification at item level
Standard object categories provided: Batch, Serial Number, Inspection Lot, Delivery Item, Production Order
Preconfigured for standard notification types F1 - F3, Q1 - Q3
Usable for all types of quality notifications
Extensible for further object categories
Search for notifications via assigned objects in the notification lists and via extended search.
Printout of assigned objects in notification papers.
Archiving of assigned objects with notification archiving.
-
2011 SAP AG. All rights reserved. 44
New tab at item level for assigned objects
There can be multiple objects of the same category, e.g. several batch numbers
Multiple Objects at Item Level
How does it Look Like, Part II
-
2011 SAP AG. All rights reserved. 45
Multiple Objects at Item Level
Solution Approach
Technical Implementation
Customizing, SAP Standard provides the object categories:
Batch
Serial number
Inspection Lot
Order
Delivery Item
Add register for displaying the assigned objects
BAdI BADI_QNAO_OBJCAT can be used to implement your own object
categories, which can be assigned to a notification item
-
2011 SAP AG. All rights reserved. 46
Enhanced Worklist for Notifications - Requirement
Example: Display that objects have been assigned
Improved reporting capabilities for quality notifications
Extended visibility of information
Flexible adjustment of capability for reports
Lack of information in Quality Notification reports.
Need to create customer-specific report to add further information in
list output.
Current Business Challenge Value of new Approach
-
2011 SAP AG. All rights reserved. 47
New Columns via Implementation of BAdI
Enhanced Worklist for Notifications
How does it Look Like
-
2011 SAP AG. All rights reserved. 48
Enhanced Worklist for Notifications
Solution Approach
Technical Implementation
Business Add-In (BAdI) BADI_EAM_SINGLELEVEL_LIST is provided to influence the list output for notification reports (PM and QM).
You can activate it for all notification reports, i.e. for notifications, tasks, actions, and items
Prerequisite is the extension of the related list output structure, and via implementing a BAdI the data determination and display is provided
Sample implementation is given for listing of assigned objects for notifications / items
Example Coding available!
-
2011 SAP AG. All rights reserved. 49
Tips and Tricks on Quality Evaluations Examples for Optimizing Evaluations
Laureen wants to analyze quality notifications.
-
2011 SAP AG. All rights reserved. 50
Use Case for Analysis of Quality Notifications via the QM
Evaluation Cockpit
Based on Quality Notifications (complaints against a vendor) the key figure PPM
shall be calculated.
When working on a concrete quality notification, the analysis shall directly be
called with the given context (i.e. of the QM notification transaction
QM02/QM03).
Defects shall be analyzed using a Pareto chart.
-
2011 SAP AG. All rights reserved. 51
Improved Analysis of Quality Notifications Solution Approach
Present Defects via Pareto Chart
SAP Enterprise Release 6.0, EhP 3
Customizing
Calculate PPM
SAP Enterprise Release 6.0, EhP 3
Customizing, Define Grouping Layout in QGA4
Call QGA4 directly from given notification
SAP Enterprise Release 6.0,
Create Function Module (based on QM10_COPY_REFERENCE_FORM_NODOC)
-
2011 SAP AG. All rights reserved. 52
Flexible Reporting Capabilities with Transaction QGA4
The QM Cockpit for Evaluations allows you to
Create analytical reports on quality data combined with meaningful graphical representation
For inspection lots, characteristics, and results
For defects
For notifications
For components from production chain
Flexibly select the data to be analyzed
Evaluate online and archived data
Compare results for several characteristics, graphically or via table views
Determine and display key figures
Create control charts without detailed planning
Influence the layout (table or graphic) and key figures
Export selected data
-
2011 SAP AG. All rights reserved. 53
QM Evaluation Cockpit (QGA4)
Evaluate Key Figure PPM
Define Grouping Layout for QGA4
-
2011 SAP AG. All rights reserved. 54
QM Evaluation Cockpit (QGA4) New Features with EhP 3 e.g. Pareto Chart
Business Goal
Provide extended analytical functions for evaluating notifications and components
and new graphic types.
Solution
Evaluation of Notifications
Evaluation of Components (e.g. data from a batch where-used list)
New graphics types:
Pareto Chart
Scatter Plot
Multilevel Batch Analysis
-
2011 SAP AG. All rights reserved. 55
QM Evaluation Cockpit (QGA4)
CalI Evaluation Cockpit QGA4 from Q-Notification
-
2011 SAP AG. All rights reserved. 56
CalI Evaluation Cockpit QGA4 from Q-Notification
Solution Approach
Technical Implementation
Define Activity for Action Box (use reference function module
QM10_COPY_REFERENCE_FORM_NODOC as a copy model).
Include function module QG_EVAL_START_EVALUATION.
Please note that function module QG_EVAL_START_EVALUATION is not officially released by SAP.
-
Summary
-
2011 SAP AG. All rights reserved. 58
6 Key Points to Take Home About Tips and Tricks on Quality Management
Various enhancement options available Customizing, Customer Exits, BAdIs, Follow-up actions etc.
Reference function modules Use reference function modules as copy models.
Sample coding available
Check out sample coding provided by SAP.
Optimized end-to-end solution for QM
Lowering Total Cost of Ownership (TCO).
Processes compliant to regulations Data accuracy and security.
Increase customer satisfaction Fulfill customer requirements.
1
2
3
4
5
6
-
2011 SAP AG. All rights reserved. 59
Interesting Links
http://forums.sdn.sap.com/forum.jspa?forumID=405&start=0
Forum: ERP Operations - Quality Management (QM)
https://service.sap.com/qm
Media Library (requires login credentials)
General Brochures on QM
SAP Service Marketplace
Additional Search Criteria Priority
Recommendations/additional info Category
Consulting FAQ
http://help.sap.com/
SAP Notes (requires login credentials)
OSS Notes on QM SAP Help Portal
-
Questions?
Session Code: 2714
-
Thank You! Contact Information:
Ingo Panchyrz
Senior Product Specialist
Product Management Quality Management
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf, Germany
M +49/160-8896680
F +49/6227/78-39222
mailto: [email protected]
http://www.sap.com