Enablement Kit for SAP NetWeaver Business Client – V1.30 How to Develop POWER Lists Overview

1. Enablement Kit for SAP NetWeaver Business Client – V1.30How to Develop POWER Lists Overview SAP AG

2. APPLID Feeder Class The POWER List: Technical Background • POWER Lists are based on a well defined framework Role POWER List Framework BackendDatabase POWER List Cache

3. Feeder Class How to Create a POWER List: Concept Mandatory Steps GET_OBJECT_DEFINITON 1 Define a container to store data provided by data retrievals GET_OBJECTS 2 POWER List Framework Define data retrieval (e.g. database select, function module) POWER List Cache

4. Feeder Class How to Create a POWER List: Concept Optional Steps GET_SELECTION_CRITERIA 3 Define selection criteria that can be used to define new queries against your Feeder 4 GET_FIELD_CATALOG POWER List Framework Define the field catalog to be used for query results table display 5 GET_ACTIONS & HANDLE_ACTIONS Define buttons and their explicit actions POWER List Cache 6 GET_ACTION_CONF Define confirmation messages for explicit actions 7 GET_DETAIL_COMP Define detail component area which can be used to improve visualization of selected data

5. How to Create a POWER List: Concept DESIGN DEVELOP TEST GO LIVE

6. How to Create a POWER List: Technical Flow • With transaction SE24, a new POWER List can be developed based on the POWER List framework • Transaction SE24 <POWER List Name> “Create” “Ok” TransactionSE24

7. How to Create a POWER List: Technical Flow • The interface “IF_POWL_FEEDER” provides all necessary methods to start building a new POWER List

8. How to Create a POWER List: Technical Flow • The tab “Methods” offers all “IF_POWL_FEEDER”-related methods 5 6 3 4 1 2 7 5

9. How to Create a POWER List: Technical Flow • Double-click on specific method to open up the editor • Top frame shows all possible parameters provided by the method

10. Registering a POWER List & Making it Visible TransactionFPB_MAINTAIN_HIER TransactionPOWL_TYPE TransactionPOWL_TYPER

11. Defining a Query “SAVE” TransactionPOWL_QUERY

12. Default Query Parameters & Settings

13. Making a New Query Visible TransactionPOWL_QUERYR

14. Testing Your POWER List Using the SAP Menu (1) • Use your Application ID • It‘s necessary to select the parameter APPLID via input help!

15. Testing Your POWER List Using the SAP Menu (2)

16. Connecting a POWER List to a Role

17. Testing the POWER List

18. Business Object Defining OBN Targets: Technical Background User’s Role Business Object Repository Button (defined by GET_ACTION & ACTION_HANDLER) calls transaction via target definition in role business object) Target Definition(BO Name)(BO Operation) Transaction A

19. APPLID Business Object Defining OBN Targets: General Concept OBN allows to launch applications from a POWL with the needed parameters. If all parameters of the target application are passed the selection screen is skipped by NWBC. Mandatory Steps Prerequisites Reminder: POWER List with GET ACTION & HANDLE ACTION needs to be defined Business Object Repository Role Transaction SWO1 1 Transaction Define business object and dedicated methods Business Object “KYK_DISP_CHAN_QUOTES” Transaction PFCG 2 Business Object “KYK-OPS-SD-ORDERS” Add specific transaction to the role Transaction PFCG 3 Add business object to the specific transaction and specify parameters in “Details for NetWeaver Business Client”

20. Defining OBN Targets: Transaction SWO1 The Business Object Methods are used as hooks by the OBN Framework. Enhance existing Business Objects or create new Business Objects. Start Transaction SWO1:

21. Defining OBN Targets: Transaction PFCG • Start Transaction PFCG and add the target transaction, Choose Details for NetWeaver Business Client* * The menuentryis still calledAdditional Details in SAP ERP 6.0 EhP3

22. Defining OBN Targets: Transaction PFCG, Details for NetWeaver Business Client Maintain the Parameter mapping in the Details for NetWeaver Business Client of the target application Use this column to define the parameters needed by the target application Use this column to define the mapped values. Use {} in order to define the parameters which contain the values (dynamic version). Not using {} defines fixed values Dynpro information of the target application Data from the related Business Object

23. Defining OBN Targets: Triggering OBN in Feeder Class: Method if_powl_feeder~handle_action METHOD if_powl_feeder~handle_action. DATA: ls_portal_actions TYPE powl_follow_up_sty,        ls_namevalue  TYPE powl_namevalue_sty.FIELD-SYMBOLS: <fs_result>  LIKELINEOF me->mt_result,                 <fs_selected> TYPE rstabix.READTABLE c_selected  ASSIGNING <fs_selected> INDEX1.READTABLE c_result_tab ASSIGNING <fs_result>  INDEX <fs_selected>-tabix.  ls_namevalue-key  = 'MaterialDocumentNo'.  ls_namevalue-value = <fs_result>-mblnr.APPEND ls_namevalue TO ls_portal_actions-parameters.  ls_namevalue-key  = 'MaterialDocYear'.  ls_namevalue-value = <fs_result>-mjahr.APPEND ls_namevalue TO ls_portal_actions-parameters.  ls_portal_actions-bo_name   = 'KYK_MM_MATDOC'.  ls_portal_actions-bo_system = /kyk/cl_service_powl=>GC_OBN_SYSTEM.CASE i_actionid.WHEN'DISPLAY'.      ls_portal_actions-bo_op_name = 'Display'. WHEN'CANCEL'.       ls_portal_actions-bo_op_name = 'Cancel_Mat_Doc'. WHEN'POST'.       ls_portal_actions-bo_op_name = 'Post_Ret_Delv'.ENDCASE.   ls_portal_actions-fire_wdevent = 'X'.  e_portal_actions = ls_portal_actions.ENDMETHOD. Parameters which need to be defined in the business object (SWO1) and mapped in the role 1 2 Reference to Business Object i_actionid: Defined in IF_POWL_FEEDER~GET_ACTIONS Methods which need to be defined in the business object (SWO1) 3

24. Defining Business Objects in Transaction SWO1 2 In SWO1 Choose Details to get the Object Name 3 1 Select the relevant method and Choose Parameters

25. Defining OBN Targets: POWL as navigation target (1) • You can call a POWL via OBN like a usual WD application • Create an entry in the role menu • WD application = POWL • APPLID = application ID of the target • possibly set REFRESHQ = X • Define a method in your BOR object with parameters you need: • QNAME – name of the target admin query (which must be defined) that is to be shown: mandatory if the POWL has several types! • QSELPARA – if you want to dynamically set the selection parameters (see next slide) • Associate the BOR method with the role entry (additional details) • If you want to start the POWL only via OBN set the „hidden“ flag • if the target POWL serves as homepage too, set the „homepage“ flag

26. Defining OBN Targets: POWL as navigation target (2), how to set the query parameters • In the coding of the calling application you have to do following: • fill selection table of type rsparams_tt with desired values: selection criteria of the target POWL data: lt_selpara TYPE rsparams_tt, ls_selpara TYPE rsparams. ls_selpara-selname = 'SD_SAKNR'. "#EC NOTEXT ls_selpara-kind = 'P'. ls_selpara-sign = 'I'. ls_selpara-option = 'EQ'. ls_selpara-low = <fs_result>-saknr. INSERT ls_selpara INTO TABLE lt_selpara. desired value • encode the selection table with the function module POWL_ENCODE_SELPARA into string: CALL FUNCTION 'POWL_ENCODE_SELPARA' EXPORTING i_selpara = lt_selpara IMPORTING e_selpara_string = ld_selpara_string. • pass the string as parameter QSELPARA via OBN: DATA: ls_portal_actions TYPE powl_follow_up_sty, ls_namevalue TYPE powl_namevalue_sty. ls_namevalue-key = 'QSELPARA'. "#EC NOTEXT ls_namevalue-value = ld_selpara_string. INSERT ls_namevalue INTO TABLE ls_portal_actions-parameters. admin query of the target POWL • pass the query name as parameter QNAME via OBN: ls_namevalue-key = 'QNAME'. "#EC NOTEXT ls_namevalue-value = gc_items_all. INSERT ls_namevalue INTO TABLE ls_portal_actions-parameters.

27. Tips (possible error sources) • The user has to have assigned the employee role (SAP_AIO_EMPLOYEE-S, SAP_BPR_EMPLOYEE-S or SAP_NBPR_NBPR-S) which provides some generic authorization and functionality. • The OBN targets defined by a POWL have to be part of the same role as the POWL, otherwise an OBN error occurs when the user selects the corresponding button in the POWL.

28. © 2010 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, and PowerPoint 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, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. •  Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. •  Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. •  Oracle is a registered trademark of Oracle Corporation. •  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. •  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, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects Explorer, 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 SAP France in the United States and in other countries. •  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. •  This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice. •  SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. • SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. •  The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.