Upload
fathi-ibo
View
160
Download
10
Tags:
Embed Size (px)
Citation preview
Tips and Tricks on Quality Management with
SAP
Getting More Out of SAP QMIngo Panchyrz, QM Product Management, SAP AG
May 2011
Session Code: 2713
2011 SAP AG. All rights reserved. 2
Primary Goals
1. Learn how to use customer exits, Business Add-Ins (BAdIs), follow-up actions etc. to
enhance the standard QM functionality.
2. Discover how 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.
Focus
2011 SAP AG. All rights reserved. 3
Agenda
Tips and tricks on inspection lots
Tips and tricks on quality notifications
Wrap-up and Questions
General options for getting the best out of your ERP system
General Options: Getting the Best Out of
Your SAP ERP System
2011 SAP AG. All rights reserved. 5
Options for Enhancing Your System w/o Modification
Customer Exits
Menu Exits
Screen Exits
Program Exits
Customizing
Assign Own Function Modules
Search Helps
Field Selection
.
Business Add-Ins (BAdIs)
Classic Business Add-Ins
Enhancement Framework
Personalization
Simplifying Navigation and Transactions
Customer Developments
Customer-Specific Programs / Reports
2011 SAP AG. All rights reserved. 6
Customizing I Example Function Modules
Always try to use reference function modules as a copy model
Replace by own function modules.
or define function modulesas follow-up actions
2011 SAP AG. All rights reserved. 7
Customizing II Field Selection to Influence Screen Fields
via Customizingor transaction SFAC
Set certain fields to display only or mandatory
2011 SAP AG. All rights reserved. 8
Customizing III Search Help
Enhance search help via Customizing or transaction SE11
2011 SAP AG. All rights reserved. 9
Customer Exits I
SAP Customer
SMOD
Definitionof
SAPEnhancements
Definitionof
EnhancementProjects
CMOD
Customer exits act as hooks.
You can hang your own add-on functionality onto these hooks.
2011 SAP AG. All rights reserved. 10
Customer Exits II
Function Module
Program
Exit
Menu 2
Function 1
Function 2
Cust. function
Function 3
Menu 1 Menu 3
Field x
Field y
Menu
Exit
Dynpro
Exit
Different types of customer exits
2011 SAP AG. All rights reserved. 11
Business Add-Ins I
BAdIAttributes
Multiple Use
Filter Dependent
INTERFACE
.
DATA: a1 ...
ENDINTERFACE.
METHODS m2 ...
METHODS m1
EXPORTING
e_par1
e_par2
IMPORTING
i_par1.
Generated
BAdI Class
FCodes
Program
+ABC
Function Code
Subscreens
Call program
0200
Dyn-Nr
ABCD
Subscr-Area
Scr..
Descr
2011 SAP AG. All rights reserved. 12
Business Add-Ins IIAvailable BAdIs in QM
Via Customizing
(transaction SPRO)
or transaction QCC5
or transaction SE18 / SE19
Tips and Tricks on Inspection Lots
2011 SAP AG. All rights reserved. 14
Tips and Tricks on Inspection Lots Examples for Optimizing the Inspection Process
Michael Meyer has identified five points along
the inspection lot lifecycle that can be optimized.
2011 SAP AG. All rights reserved. 15
Use Case Quality Inspection I
Michael Meyer wants to have a more transparent inspection lot worklist.
Goods receipts for scheduling agreements should be created with a customer-
specific inspection type, regular goods receipt postings with standard inspection
type 01.
For his customer-specific inspection type the characteristics shall be selected
flexibly.
The inspectors need to have the possibility to record a date.
After an operation is completed an internal e-mail shall be send to
the following work center.
Inventory postings before usage decision are not allowed
(pre-release of quantities).
2011 SAP AG. All rights reserved. 16
Inspection Type Determination I
Example Material Master
Inspection Lot Worklist (e.g.QA32)
2011 SAP AG. All rights reserved. 17
Inspection Type Determination II
Customer Exit
QAAT0001
Begin
Determine order
type based on
purchase document
Order Type
NB or LP
Take inspection type 01 to create inspection lot
Customer Exit
QAAT0001
End
NB LP
Solution
Customer Exit QAAT0001
Inspection type determination different from variant 01
Take inspection type Z01_99 to create inspection lot
2011 SAP AG. All rights reserved. 18
Flexible Inspection Specification I
Example
2011 SAP AG. All rights reserved. 19
Flexible Inspection Specification II
Solution
BAdI definition QPAP_FLEX_PLAN Flexible Specification SelectionInclude function module QST05_FLEX_PLAN_SELECTION
2011 SAP AG. All rights reserved. 20
Input Processing I
Record Results
Example
2011 SAP AG. All rights reserved. 21
Input Processing II
Solution
BAdI definition QM_INPUT_PROCEDURE Set up input procedure in Customizing Create/change master inspection characteristic
Customizing
2011 SAP AG. All rights reserved. 22
Input Processing III
Master Inspection Characteristic
Solution
2011 SAP AG. All rights reserved. 23
Follow-Up Action for Operation Completion I
Example
2011 SAP AG. All rights reserved. 24
Follow-Up Action for Operation Completion II
Solution
Customizing operation completion Program follow-up action (reference function module
QFOA_COPY_REFERENCE_FORM)
Set up follow-up action in customizing Assign follow-up action to relevant selected set code
Same procedure for usage decision follow-up actions
2011 SAP AG. All rights reserved. 25
Inventory Postings Before Usage Decision I
Example
2011 SAP AG. All rights reserved. 26
Inventory Postings Before Usage Decision II
Solution Create a status profile with user status in Customizing
Assign status profile to inspection type Specify transaction control
Tips and Tricks on Quality Notifications
2011 SAP AG. All rights reserved. 28
Tips and Tricks on Quality NotificationsExamples for Optimizing the Notification Process
Peggy Parker has identified four points along the
quality notification lifecycle that can be optimized.
2011 SAP AG. All rights reserved. 29
Use Case Quality Notification I
Peggy Parker wants to add the additional field Plant of Complaint to the quality notification. Notifications shall be selectable by the new field.
In addition the new field shall be displayed in the notification worklist.
Peggy wants to enhance the notifications action box by navigating into the stock
overview.
The actions in the notification action box shall be restricted depending on the
user authorization.
When closing a notification with recorded defects it shall be checked if
causes have been created.
2011 SAP AG. All rights reserved. 30
Additional Fields in the Notification I
Example
QM10
2011 SAP AG. All rights reserved. 31
Additional Fields in the Notification II
Solution
Append view for table QMEL (Quality Notifications) & structure RQMQMEL1 -> makefield available
Customer Exit QQMA0001 QM/PM/SM: User Subscreen for Notification Header Create subscreen in function group XQQM
Customizing of notification type (assign subscreen to tab page)
Selection view of logical database QNQ (dynamic selections)
See also OSS-Note 370191 - Notification worklist: User-defined fields
Alternative BAdI BADI_EAM_SINGLELEVEL_LIST Extend Single-Level Lists
Almost same procedure for inspection lots, usage of customer exit QPL1001 QM: Inspection lot creation - editing work area on creation. Table QALS & structure QALS_D01, logical database = PGQ
2011 SAP AG. All rights reserved. 32
Action Box I
Example
2011 SAP AG. All rights reserved. 33
Action Box II
Example
2011 SAP AG. All rights reserved. 34
Action Box III
Example II In addition the usage decision shall directly be made using a separate action.
2011 SAP AG. All rights reserved. 35
Action Box IV
Solution
Reference Function Modules Description
QM10_COPY_REFERENCE_FORM_ACTI Copy Model for Activities documented as Action
QM10_COPY_REFERENCE_FORM_TASK Copy Model for Activities documented as Task
QM10_COPY_REFERENCE_FORM_NODOC Copy Model for Activities no documentation
QM10_COPY_REFERENCE_FORM Copy Model for follow-up actions
Copy the relevant function modules into the customer name space and program function. Optional: Define follow-up actions for tasks and assign them to the task code. Add activities to the notification action box.
2011 SAP AG. All rights reserved. 36
Influence Action Box I
Example
2011 SAP AG. All rights reserved. 37
Influence Action Box II
Solution
Business Add-In NOTIF_ACTIONBOX to hide, activate, or deactivate an activity in the action box
2011 SAP AG. All rights reserved. 38
Checks on Save or Status Change I
Example
QM02
2011 SAP AG. All rights reserved. 39
Checks on Save or Status Change II
Solution
Either
Customer Exit QQMA0014 QM/PM/SM: Checks before saving a notification
or
Customer Exit QQMA0005 QM: Check Validity of Status Change
2011 SAP AG. All rights reserved. 40
6 Key Points to Take HomeAbout Tips and Tricks on Quality Management
Various enhancement options available Customizing, Customer Exits, BAdIs, Follow-up actions etc.
Reference function modulesUse reference function modules as copy models.
Example coding available
Check out example coding provided by SAP.
Optimized end-to-end solution for QM
Lowering Total Cost of Ownership (TCO).
Processes compliant to regulationsData accuracy and security.
Enhance customer satisfactionFulfill customer requirements.
1
2
3
4
5
6
2011 SAP AG. All rights reserved. 41
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 CriteriaPriority
Recommendations/additional infoCategory
Consulting FAQ
http://help.sap.com/
SAP Notes (requires login credentials)
OSS Notes on QM SAP Help Portal
Questions?
Session Code: 2713
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