1. Process overview & detailed discussion HERUG 2002, Melbourne Development Requests Juergen Hollberg, SAP AG

2.  SAP AG 2002, HERUG_2002_DR J.Hollberg 2 Process outline Agenda Development background Process suggestions to HERUG Detailed discussion

3.  SAP AG 2002, HERUG_2002_DR J.Hollberg 3 Process outline Agenda Development background Process suggestions to HERUG Detailed discussion

4.  SAP AG 2002, HERUG_2002_DR J.Hollberg 4 Process outline: What SAP suggests  SAP encourages the definition of development requests via user groups HERUGs general approach is in line with the desired process  The user groups internal process that leads to an official requirement is not specified by SAP HERUG and the designated SAP contact can and need to define this process based on the needs and possibilities

5.  SAP AG 2002, HERUG_2002_DR J.Hollberg 5 Process outline Agenda Development background Process suggestions to HERUG Detailed discussion

6.  SAP AG 2002, HERUG_2002_DR J.Hollberg 6 Development background: What SAP has to consider  SAPs development resources are committed for many activities Maintenance of the existing product Education Test Strategic developments Development requests  SAP needs to look at the importance of the request for the requesting customers the economic success that the requested development has

7.  SAP AG 2002, HERUG_2002_DR J.Hollberg 7 Development background: What happens to requests?  Two request channels exist today: Requests entered via OSS Requests directly referred to User Group’s SAP contact  Both channels are supposed to provide fast response OSS system generates internal reminder if request is not treated after 14 days After 4 weeks without treatment, the request is automatically denied Manual channel has no automatism  All requests are discussed frequently with the development management Discussion takes place every month Major development planning only takes place once for each release

8.  SAP AG 2002, HERUG_2002_DR J.Hollberg 8 Process outline Agenda Development background Process suggestions to HERUG Detailed discussion

9.  SAP AG 2002, HERUG_2002_DR J.Hollberg 9 Suggestion to HERUG  Goals of this suggestion HERUG members and SAP can already estimate the necessary timeframe involved Clearly separate developments within the IBUs responsibility from developments which affect others Provide good basis for DR discussion at HERUG conference  Define requests in 3 categories 1.Minor changes which enhance the usability of the system  Can only affect existing modules  Possibility to merge into existing development plan 2.Enhancements of existing functionality  Can only affect existing modules  Might require separate project in development plan 3.Entirely new functionality  Might require development of a new solution  Certainly needs a project within a development plan

10.  SAP AG 2002, HERUG_2002_DR J.Hollberg 10 Suggestion to HERUG  SAP will screen the requirements presented by HERUG To assign the requirement to one of the 3 categories if the customer was not sure, or to review assignment if already existing To provide quick feedback on categories 1 and 2 regarding ability to fulfill To provide an initial statement to category 3 as a basis for further discussion at a HERUG conference For all categories, to provide feedback on  The feasibility of the request (in line with SAP architecture or not)  The estimated effort required (small, medium, large, very large)  HERUG decides Which topics finally should be discussed at the conference What priority is assigned to the request  For items that don’t need discussion, priority should be assigned as fast as possible  Items that are to be discussed can be voted on after the annual HERUG meeting

11. Thank You

12.  SAP AG 2002, HERUG_2002_DR J.Hollberg 12 Process outline Agenda Development background Process suggestions to HERUG Detailed discussion

13.  SAP AG 2002, HERUG_2002_DR J.Hollberg 13 Discussion of latest requests

14. Thank You

15.  SAP AG 2002, HERUG_2002_DR J.Hollberg 15 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 ®, NT ®, EXCEL ®, Word ®, PowerPoint ® and SQL Server ® are registered trademarks of Microsoft Corporation. IBM ®, DB2 ®, OS/2 ®, DB2/6000 ®, Parallel Sysplex ®, MVS/ESA ®, RS/6000 ®, AIX ®, S/390 ®, AS/400 ®, OS/390 ®, and OS/400 ® are registered trademarks of IBM Corporation. ORACLE ® is a registered trademark of ORACLE Corporation. INFORMIX ® -OnLine for SAP and Informix ® Dynamic Server TM are registered trademarks of IBM Corporation. UNIX ®, X/Open ®, OSF/1 ®, and Motif ® are registered trademarks of the Open Group. Citrix ®, the Citrix logo, ICA ®, Program Neighborhood ®, MetaFrame ®, WinFrame ®, VideoFrame ®, MultiWin ® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C ®, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA ® is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT ® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP, mySAP.com, 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 in several other countries all over the world. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP Markets and Commerce One. All other product and service names mentioned are the trademarks of their respective owners. Copyright 2002 SAP AG. All Rights Reserved