2811 Extending Quality Notification Functionality through ...

Orange County Convention Center Orlando, Florida | May 15-18, 2011

Extending QM Notifications with Subscreens Chris Seitz Sr. SAP QM Consultant Enowa Consulting

]

[ Agenda












Overview of notification process – Pharma product issue Configuration for custom screen areas User exits to build screens and process logic Append structures for adding fields Activating user function codes Generic Object Services example Action box configuration Badi example during save Learning points Return on investment Best practices

Real Experience. Real Advantage.

2

[ Notification Process Overview - Flowchart

Real Experience. Real Advantage.

3

[ Notification Process Overview – Example Key Drivers








Confidentiality of “reporter” contact information In some cases, no material or SAP “customer” Ability to confirm that findings have been reviewed Ease transition from old system – users new to SAP Explicitly document certain checks such as batch review Make sure system meets FDA Audit requirements Quick replacement for out-of-support stand-alone system

Real Experience. Real Advantage.

4

[ Notification Process Overview – Design decisions







Use workflow with IQS12 to simplify investigational input Manage confidential data in append fields Manage FDA requirements in append fields where appropriate Use custom screen areas to simplify screen input Make sure that any development is upgrade compliant Create prototype for analysis within 2-week timeframe

Real Experience. Real Advantage.

5

[ Notification Process Overview – Main Screen – QM02 Standard SAP Elements

Custom Screen Area

Real Experience. Real Advantage.

6

[ Process Overview – Task processing in QM02

Custom Screen Area

Real Experience. Real Advantage.

7

[ Process Overview – WF Task processing – IQS12 Custom Screen Area

Real Experience. Real Advantage.

8

[ Notification Process Overview – Task Screen Data Transferred back to Header upon Saving

Real Experience. Real Advantage.

9

[ Notification Process Overview – Task Screen Data Transferred back to Header upon Saving

Real Experience. Real Advantage.

10

[ Configuration of Screen Areas – Activities
Activate User Exit QQMA0001- User Subscreen for Notification Header (Screen 100 is default blank screen)
Activate User Exit QQMA0011- User Subscreen for Additional Data on Task – 3 lines (Screen 100 is default blank screen)
Customize Extended View: Tabstrips and Screen Areas
Customize Notification Header and Screen Areas
Activate User Exit QQMA0003- "User data" Function in "Goto" Menu if function codes are needed.
Extend Append Structures for QMEL, QMSM, QMFE …
Activate Notification Save Badi

Real Experience. Real Advantage.

11

[ User Exit for custom screen areas - Header Code to adopt subscreen changes

Subscreens 0100 – blank Others - active

Real Experience. Real Advantage.

12

[ User Exit for custom screen areas - Task Subscreens 0100 – blank Other - active

Real Experience. Real Advantage.

13

[ Customizing Screen Areas for Header Tabstrip

Linking Subscreen to Tabstip

Real Experience. Real Advantage.

14

[ Customizing Screen Areas for Task Overview

Linking Subscreen to Tabstip

Real Experience. Real Advantage.

15

[ Customizing Header Screen Areas

Subscreen in Task Processing (3 lines)

Real Experience. Real Advantage.

16

[ User Exit for function code

User Function Code to process Attachment list directly

Real Experience. Real Advantage.

17

[ Append Structures for adding fields - QMEL

By Adding Custom fields to a QMEL append Structure, they are automatically extended to the underlying data structures that are available during notification processing.

Real Experience. Real Advantage.

18

[ Append Structures for adding fields – QMEL cont’d

Real Experience. Real Advantage.

19

[ Append Structures for adding fields – QMSM

Same is true for QMSM, QMFE, QMMA – they also transfer to Processing structures automatically

Real Experience. Real Advantage.

20

[ Generic Object Services Example – linking an F-code Button only shows up if attachments exist

Real Experience. Real Advantage.

21

[ Generic Object Services Example – screen layout

Screen links button to f-code

Real Experience. Real Advantage.

22

[ Example Badi Code – Task data move to header

Set filter to determine when code is executed

Real Experience. Real Advantage.

23

[ Example Badi Code – Task data move to header cont’d

Badi is even accessed during defects recording, unlike older user exits Real Experience. Real Advantage.

24

[ Action box Configuration - Uses Communication Tracking activities Material movements Sales order creation Regenerate CoA Launch workflows Use function group QM06 as template
(In some cases, forms are hard coded)








Real Experience. Real Advantage.

25

[ Action box Configuration – Example Functions QM06

Real Experience. Real Advantage.

26

[ Learning Points
Custom screen areas can enhance usability and comfort
Satisfy legal, process requirements directly without trying to change the business process to match SAP
Allow for input into transaction design process without breaking the development bank
Perilous to move away from standard, like SAP address management – where does the migration to Z-code stop?
Action box can help streamline transaction strings

Real Experience. Real Advantage.

27

[ Return on Investment
Notification development offers an alternative to best of breed solutions (systems like Trackwise), which required redundant support structures and licensing
Integration to score-carding, reporting, feedback to the design process, easier to achieve with one data source.

Real Experience. Real Advantage.

28

[ Best Practices
Development can be done in an SAP compliant way, minimizing issues with patching/upgrading and keeping SAP support in place.
Using notifications leverages investment in SAP & support
Workflow integration can be used to facilitate participation by infrequent users

Real Experience. Real Advantage.

29

[ Key Learnings
User subscreens are easily implemented with minimal coding.
Notifications provide flexible approach to managing event driven processes
Integration to other SAP components can be leveraged through action box integration

Real Experience. Real Advantage.

30

[

]


Thank you for participating. Please remember to complete and return your evaluation form following this session. For ongoing education in this area of focus, visit www.asug.com.

SESSION CODE: 2811

Real Experience. Real Advantage.