SAP POWL Best Practice

SAP ECC 6.00 .00 April 2007 English

How to… to … Develo Develop p POWER OWER Lis Li s ts How-to Guide: SAP Best Practices for New A1 Enablement Kit

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany

Titles you can't find anywhere else

Try Scribd FREE for 30 days to access over 125 million titles without ads or interruptions! Start Free Trial Cancel Anytime.













SAP Best Practices

How to to Develop Develop POWE P OWER R Lists

Copyright

©Copyright 2007 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 permission of SAP S AP AG. AG. The The information information contained herein herein may be be changed without without prior prior notice. Some software products products marketed by SAP AG and its distributors contain proprietary proprietary software components components of other software vendors. Microsoft, Micros oft, Windows, Outlook, Outlook, Excel, and P PowerP owerPoint oint are registered trademarks trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Universal Database, Database, OS/2, P arallel arallel Sysplex, Sysplex, MVS/ES MVS /ESA, A, AIX, S/390, S/390, AS/400, AS/400, OS/390 O S/390,, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System System z9, z/OS, z/OS , AFP A FP,, Intellig Intelligent ent Mine Miner, r, Web W ebSpher Sphere, e, Net N etfin finity ity,, Tivol T ivoli, i, Inf I nform ormix ix,, i5/OS, POWER POW ER,, P OWER5, OWE R5, P OW OWE ER5+, OpenPower OpenPower and Power P owerP P C are trademar trademarks ks or registered tr tradem ademarks arks of IBM IB M Corporation. Corporation. 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 HTML,, XML, XML, XHTML, XHT ML, and W3C are a re trademarks trademarks or registered trademarks trademarks of W3C® W3C ®, World Wide Web Consortium, Massachusetts Institute of Technology. J ava ava is a regis egisttere ered trade ademark ark of Sun Mic Microsy rosyst ste ems, Inc. Inc. J avaSc avaScrript ipt is a regi egister stered ed trade ademark ark of Sun Micr Microsy osyst ste ems, Inc., Inc., used sed unde nder lice licen nse for for techn chnolog ology y inv invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP SA P , R/3, R/3, mySAP mySAP,, mySA mySAP. P.com com,, xApps, xApp, xApp, SAP SA P NetWeaver, NetWeaver, and other other SAP SAP products 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. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves information purposes only. National product specifications may vary. These These materia erials ls are are subj subje ect to chan change ge witho ithout ut not notice ice. The These mate aterials ials are are prov rovide ided by SAP AG an and its its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, kind, and a nd SAP Group shall not be liable liable for errors or omissions omissions with with respect to the the materials. materials. The T he only warranties warranties for SAP SAP Group products products and services are those those that are set forth in the express express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
















SAP Best Practices

Icons Ic o n

Mean i n g

Caution Example Note or Tip Recommendation Syntax

Typographic Ty pographic Conve Conventions ntions Typ e St y l e

Des c r i p t i o n

Example text

Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options. Cross-references to other documentation.

Example text

Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT

Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Exampl e t ext

Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE PL E TEXT T EXT

Keys on the keyboard, for example, function keys (such as ENTER key.

Example text

Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

Variable user entry. entry. P ointed brackets brackets indicate that you you replace these words and characters with appropriate entries.

F2) or the















SAP Best Practices


Contents How to Develop POWER Lists.....................................................................................................5 1

P urpo urpose se ............... ....................... ................ ................ ............... ............... ................ ................ ............... ............... ................ ................ ............... ............... ................ ...........5 ...5

2

P rere rerequ quisit isites es....... ............... ................ ............... ............... ................ ................ ............... ............... ................ ................ ............... ............... ................ ................ ............5 ....5

3

Devel Develop opm ment ent of own own POWE P OWER R Lists..... Lists............. ............... ............... ................ ................ ............... ............... ................ ................ ............... ............5 .....5

4

3.1 3.1

Basic Basic Conce Concept pt of POWER Lists Lists ........ ............ ....... ....... ........ ........ ........ ........ ........ ....... ....... ........ ........ ........ ........ ........ ........ ....... ....... ........ .....5 .5

3.2 3.2

P OWER List List Desi Design gn.... ........ ........ ........ ....... ....... ........ ........ ........ ........ ........ ........ ....... ....... ........ ........ ........ ........ ........ ........ ....... ....... ........ ........ ........ ......6 ..6

3.3 3.3

P OWER List List Imp Implem lement entation...... ation.......... ........ ........ ........ ....... ....... ........ ........ ........ ........ ........ ........ ....... ....... ........ ........ ........ ........ ........ ........ ......7 ..7

3.3.1 3.3.1

Creat Creating a new new P OWER List.......... List.................. ............... ............... ................ ................ ............... ............... ................ ................ ...........7 ...7

3.3.2 3.3.2

Maint Mainta ainanc inance e of the the Feeder Feeder Class Class meth method ods s ............... ....................... ................ ............... ............... ................ ..............9 ......9

3.3.3 3.3.3

Regist Register er a POWE R List and and make ake it it visib visible... le........... ................ ............... ............... ................ ................ ............... .........11 ..11

3.3.4 3.3.4

Creat Create a Query Query for a P OWER List ............... ....................... ................ ............... ............... ................ ................ ............... ..........13 ...13

3.3.5 3.3.5

Connect Connectin ing g a POWER PO WER List to a Role.......... Role................. ............... ................ ................ ............... ............... ................ .............16 .....16

3.3.6 3.3.6

P OWER List Cache Cache and and User defin defined ed quer querie ies s ............... ....................... ................ ............... ............... ................18 ........18

Descr Descrip ipti tion on of the F eede eederr Inter Interfa face.......... ce.................. ................ ............... ............... ................ ................ ............... ............... ................ .............19 .....19 4.1 4.1

Descr Descrip ipttion ion of of the the Feeder Feeder Inter Interfa face ce IF_POWL_ IF_ POWL_ FEEDER FE EDER ........ ............ ........ ........ ....... ....... ........ ........ ........ ........1 ....19 9

4.1.1 .1.1

Metthod GET_ ACTIONS ........ Me ............ ........ ........ ........ ........ ....... ....... ........ ........ ........ ........ ........ ........ ....... ....... ........ ........ ........ ........ ........ .....19 .19

4.1.2 .1.2

Metthod GET_ ACTION_CONF Me ACTION_ CONF ....... ........... ........ ........ ........ ....... ....... ........ ........ ........ ........ ........ ........ ....... ....... ........ ........ ........ ........ .....22 .22

4.1.3 .1.3

Metthod GET_ Me GE T_SE SEL_C L_CRITE RITERIA RIA ....... ........... ........ ........ ........ ....... ....... ........ ........ ........ ........ ........ ........ ....... ....... ........ ........ ........ ........ .....23 .23

4.1.4 .1.4

Metthod GET_ FIELD_CAT Me FIE LD_CATALOG ALOG ....... ........... ........ ........ ....... ....... ........ ........ ........ ........ ........ ........ ....... ....... ........ ........ ........ ........ .....27 .27

4.1.5 .1.5

Metthod GET_ OBJ ECT_DEF Me ECT _DEFINITION. INITION..... ........ ........ ....... ....... ........ ........ ........ ........ ........ ........ ....... ....... ........ ........ ........ ........ .....33 .33

4.1.6 .1.6

Metthod GET_ OBJ ECTS ....... Me ........... ........ ........ ....... ....... ........ ........ ........ ........ ........ ........ ....... ....... ........ ........ ........ ........ ........ ........ ....... ......34 ...34

4.1.7 .1.7

Metthod GET_ DETAIL_COMP Me DETAIL_ COMP ....... ........... ........ ........ ........ ....... ....... ........ ........ ........ ........ ........ ........ ....... ....... ........ ........ ........ ........ .....37 .37

4.1.8 4.1.8

Metho Method d HANDLE_ ACTION............. ACT ION..................... ................ ................ ............... ............... ................ ............... ............... ................38 ........38
















SAP Best Practices

How to t o De Develop velop PO POWE WER R Lists Lis ts 1 Purpose This This guide ide descr escrib ibes es the tech echnica ical back ackgrou round as well as the con concep cept of POWER List Lists. s. In the main main part, the the development development of of own POW P OWE ER List List is explained.

For information about the available POWER Lists and the scope of their functions, and services, services, see s ee the documentation: documentation: Available POWER POWER Lists in SAP A1N A1N.

2 Prerequisites Required Authorizations for for development, development, role management management and mainten maintenance ance of cross client views.

3 De Develop velopment ment of ow own n PO POWE WER R Li List sts s 3.1 3. 1 Basic Concept of POWER POWER Li List sts s The The POWER List List is basic asical ally ly a fra framework ork that can can list list busin siness ess ob object jects s and and allo allow ws sp specif ecific ic activities (actions) based on these business objects. The The cen central idea idea is that all proper opertties ies of of a POWER List List (the whole ole scop scope e descr escrib ibed ed in HOW_TO_USE) can be specified via one central, standardized class (the so called feeder class). This This way an easy easy to hand andle thoug ough power owerfu full tool ool is provid ovide ed to modif odify y pre-d re-de efin fined POWER List Lists resp. develop own ones.

The Feeder Class The The feed feeder er clas class s com communica icates with ith the database ase sele select ctin ing g spe specif cific data, for forwards rds the data to a P OW OWER ER List’s interna internall cache and refreshes refreshes the the POW P OWER ER List on the user’s user’s client on deman demand. d. Moreover the feeder class class includes includes the handling of actions initiated by the the user while press pressing ing a button.

POWER List Framework

Feeder Class
















SAP Best Practices

Embedded into a well defined framework the feeder class is the central and most important place while developing developing or modify modifying ing POW POWER ER Lists. There T herefore fore developin developing g an own POWE POW ER List in principle means developing an own feeder. Before we can go into details on the feeder class and its specific methods, another aspect of POWER Lists must be mentioned: the role dependency.

Role Dependency As the connection between the user and the POWER Lists is done via the roles, it is possible to arrange arrange several several different different POWE POW ER Lists from SAP and/or and/or Part P artner ners s into one or severa severall roles. The T he roles are the access point to all the POWER Lists in the system. While exceptions may apply, in most cases, POWER Lists are launched as “homepages” within the canvas area of the SAP NetWeaver Business Client while having the navigation panel on the left side. F rom a technical point of view a so called AP AP P LID LI D (application ident identifier) ifier) determ determines, ines, which POWERL List (POWL Application) will be called. Therefore the assignment of APPLIDs to a particular role role determines which POW P OWE ER List List will will be available for tthe he role.

APPLID

POWER List Framework

Backend Database

Feeder Class

POWER List Cache

Beneath development development of of an own feeder the creation creation of a new POW P OWE ER List List requires the definition definition and assignment of an APPLID and assignment to appropriate roles as well.

3.2 POWER POWER Li st Desig n Before starting developing a feeder (and a new POWER Lists), please also note the following aspect of the whole concept. Developing a POWER Lists doesn’t mean to develop some feeder coding, only. Developing the coding is one task of a sequence you need to do. The The most ost imp import ortant step step to high ighligh ight is the desig esign n phase. ase. Be aware are that a good ood desig sign upfron frontt can not only speed up the process of developing the coding but also to increase the efficiency of

















SAP Best Practices




The selection criteria you want to offer. Most common questions: Which selection makes sense for the user? Are there performance impacts to be considered?



The buttons you want to include. Most common questions: What are the actions? Button names? Can I use function modules? Will the buttons launch transactions?



Detailed component. Most common questions: Do I need the detailed component? Which data do I need to show up in the detailed view?

After developing the coding, you also need to test your POWER List. Make sure, especially for the pre-defined setting you might add to your feeder, that you are testing in a real environment, not only with with real data, data, but also with a u user ser which doesn’t h hold old SAP S AP _ ALL AL L or similar authorization. authorization.

3.3 POWE POWER R Li st Implementatio Impl ementatio n SAP ships pre-defined POWER Lists with the new version of SAP All-in-One. These lists can be used as templates templates to define oth other er POW P OWE E R Lists, Lists, or to slightly m modify odify them. them. A customer could also use them directly without modification. However, this needs to be checked in every case, as the business objects in the system for sure depend on the customizing settings of the customer. In some cases, a pre-defined POWER List cannot be used as it is, because of these customer specific settings and needs to be adjusted. In all cases, SAP recommends to copy the pre-defined POWER Lists into customer namespace (Z* or Y*) to avoid conflicts in later system upgrades. For sure, also SAP Partners can pre-define POWER Lists for their customers. They can leverage from the SAP SAP P ower Lists Lists or they they can develop develop complet completely ely new P OW OWE E R Lists Lists from scratch.

3.3.1 3.3 .1

Creatin g a new PO POWER WER Li List st

Use We will create a new feeder via the Class Builder . However instead of developing a new class from the scratch scratch we we will use the the pre-defined pre-defined interface interface IF_P IF_ P OW OWL_ L_F F EE DER DER and modi modify fy the the contained methods afterwards.

Procedure


















SAP Best Practices

4. In the dialog box Object Type leave the fields Name and the default option Class as they are and press Enter . 5. On the the Create Class screen provide an appropriate description for your POWER List Fi el el d n am am e

Us er er ac ac ti ti on on an an d va val ue ues

Description

Appropriat Appropriate e Description Description for the the new POWE PO WER R List

Leave all other fields as they are and choose Save. 6. On the Create Object Directory Entry subscreen choose a package for the new development Fi el el d n am am e


Package

Specify the package name or choose via F4-help

Choose Enter in order to acknowledge the package or Local Object in case of a local development. 7. Move to tab Interfaces on the Class Builder: Change Class screen Fi el d n am e

Us er ac t i o n an d v al u es

Interface

Insert IF_POWL_FEEDER

Co m m en t

This This is the int interfa erface ce provi rovid ded by SAP th that contains all methods for the feeder

Choose Enter to save the specified value. 8. P ress the the Save button.

Result All available methods and attributes of the feeder class are uploaded into the class builder and can now be modified according to your requirements (please see Maintainance of the the Feeder F eeder Class methods for a description of all feeder class methods).


















SAP Best Practices

2. On the Class Builder: Initial Screen screen, make the following entries: Fi el d n am e


Object Type

/KYK/CL_MM_POWL_VENDOR_LIST

3. Choose Copy Class/Interface (CTRL+F5). 4. In the the dialog dialog box Copy provide an appropriate name for the target feeder class. Fi el d n am e


Copy to

e.g. Z_MM_POWL_VENDOR_LIST

5. Press Continue (Enter). At this point you have created a 1:1-copy of feeder the class for Vendors. Y ou could activate activate the copied class by pressing Activat A ctivate e (Ctrl+ (C trl+F 3) and proceed with Register a POWER List and make it visible. visible.

3.3. 3. 3.2 2

Maintainance Maintainanc e of the Fe Feeder eder Class meth method od s

After creation of a new feeder class (described in Creating a new POWER List) List) all available methods of the class are available and can be specified. If you have just created a new class and are still in the screen Class Builder: Change Class you can proceed with specifying the code for the methods methods required (4). Otherwise use transaction SE SE24 to modify the the newly created feeder. 1. Access Acces s the the transaction transaction choosing one one of the the following navigat navigation ion options: options: SAP ECC menu

Tools  ABAP Workbench Workbench  Class Builder

Transaction Transaction cod e

SE24

2. On the Class Builder: Initial Screen screen, make the following entries: Fi el el d n am am e


Object Type

Specify the name of the feeder you want to modify.

















SAP Best Practices


technology will be handled automatically in the background based on these settings. So there is no need to explicitly take care on things like caching data and so on. (see details and example for Me Mettho hod d GET_ GET_OBJ OBJ ECT ECT_DE _DEFINITION FINITION ) 

Retrieve data data from the the backend backend system system (Method (Method “GE “GET_ T_OB OBJJ ECTS CT S”) Here you need to define the data retrieval itself. This can be either a very simple database select (e.g. select * from xyz) or a complex selection where you use existing SAP SAP function function modules or your own coding (see details and example example for Mettho Me hod d GET_ OBJ EC ECTS TS ).

With maintaining only these two methods with coding, a feeder with minimal functionality is available. Since there is no default query defined yet, the resulting POWER List will be more or less unusable. However, if you want want to test test the feeder feeder at this this stage, you can register the POWE PO WER R List as described in Registering a POWER List and make it visible and enhance it step by step. The The foll follow owin ing g add additio ition nal methods ods are are part art of the sta standard fee feeder int interfa erface ce:: 

Define selection criteria (Method “GET_SEL_CRITERIA”) With this method you can define, which selection criteria is visible and selectable by the user. Example: You have a POWER List showing billing documents. You could offer the selection criteria “billing date” so that the user can later retrieve the data directly the way he searches for it. (see details and example for Method GET_SEL_CRITERIA). GET_SEL_CRITERIA ).



Define the field catalog (Method ‘GET_FIELD_CATALOG”) (see details and example for Me Mettho hod d GET_ FIE FIELD_CATALO LD_CATALOG G)



Define butto buttons ns and their their actions (Methods (Methods “GE “GET_ T_ ACTI AC TIONS ONS” ”& “HANDLE_ACTION”) By maintaining the two methods GET_ACTIONS and HANDLE_ACTION, you have a huge variety of options to improve the POWER Lists significantly. First you need to define the buttons with name, index and more (GET ACTIONS). Second you need to define the actions which should be initiated if the user presses such a button. The action can simply be launching a transaction and forwarding the business object parameters to it. Or it could be used to simplify a whole process by using the buttons to call several function modules in a sequence automat automating ing the process in the background based on the selected item(s) in the POWER List. (see details and example for Met Metho hod d GET_ ACTIO ACTIONS NS and HANDLE_ACTION)


















SAP Best Practices

Not all of the methods described above need to be maintained to get a working POWER List. However, it is important to notice, that none of the standard feeder methods must be deleted, even if they are empty. Moreover you have to ensure that all standard feeder methods are activated before the POWER List can be used. Otherwise a shortdump shortdump is likely to occur occur during execution. execution.

3.3. 3. 3.3 3

Regi Re gister ster a POW POWER ER Lis Listt and make it vis visib ible le

After a feeder is developed, it needs to be made visible to the roles. Basically, this means we need to register the feeder under a specific APPLID, define a POWER List type and introduce it to the roles.

Creatin Crea ting g an APPLID for the POWER POWER Lis t

Use F irst of all, you need need to specify specify the the so called APP AP P LID LI D (Application (Application ID). This T his ID will later later be used in the role to specify the target (your feeder) which will then be shown as POWER List homepage in the the SAP S AP Net Weaver Weaver Business Client. The AP P LID LI D is more or less less just a name name to specify. specify.

Procedure 1. Access Acces s the the transaction choosing the the following navigat navigation ion option: option: Transaction Transaction cod e

FPB_MAINTAIN_HIER

2. On the Display View “Personalization Hierarchy”: Overview screen, choose Display <-> Change (Ctrl +F1). 3. In the dialog box Caution Table is cross client, choose OK. 4. F rom the menu bar choose New Entries. 5. In the grid Personalization Personalization Hierarchy, make the following entry: Fi el d n am e


Personalization Hierarchy

Specify an APP LID for the the POWE R Applica Applicattion




















SAP Best Practices

1. Access Acces s the the transaction choosing the the following navigat navigation ion option: option: Transaction Transaction cod e

POWL_TYPE

2. In the dialog box Caution Table is cross client, choose OK. 3. F rom the menu bar choose New Entries 4. On the View: Type Definition screen, make the following entry Fi el d n am e


Type

Specify an appropriate name as Feeder Type

Description

Specify an appropriate description

Feeder Class

Choose the the feeder class class via F4-help F 4-help A new feeder won’t be available in the dialog box until it is activated.

Sync. Call No Msg. Wrapping

This This che checkb ckbox can can be set set to enfo enforc rce e syn synchr chronou onous s query refr refre eshe shes. If the checkbox is set, no message wrapping takes place on refresh. (In case of errors during refresh, the system messages will be shown instead of the generic one)

5. Choose Save. 6. Specify a transport transport order in the upcoming upcoming dialog. dialog.




















SAP Best Practices

It might be useful to check the mappings that have been made so far. Tes Testt a POWER List List vi via a SAP Men Menu u describes an easy way to test the newly created POWER List using the Favorites of SAP S AP Menu. Basically Basically the POWE PO WER R List should work at this point; point; however, however, it will be empt empty, y, since there is no default query defined yet. 

3.3.4 3. 3.4

Create a Quer Query y fo forr a POW POWER ER Li st

Defi De fine ne the Query

Use Default queries queries are defined using the transaction transaction “P “P OWL_ OWL _ QU QUE ERY ”. Here you can define define a query query (QUERYID) and connect it to a POWER Lists type. Finally, you can set the query.


POWL_QUERY

2. F rom the menu bar choose New Entries. 3. On the Maintain Table Views: Initial screen, make the following entry:




















SAP Best Practices



Button Query Settings In the upcoming window, you can specify several attributes mapped to each single selection criteria.

7. Choose Save and specify a transport order in the upcoming dialogs boxes.

Role assignm assignm ent for the Query Query Type As with with the type, type, the the query needs needs to be introduced introduced to the the roles. Therefore the the APP AP P LID LI D and the QUE QU ERY ID get mapp mapped ed to each each other. other.


POWL_QUERYR

2. F rom the menu bar choose New Entries. 3. On the New Entries: Details of Added Entries screen, make the following entry: Fi el d n am e


Application

Choose Choose APP AP P LID define defined d in FPB_ MAINTAIN_HIER MAINTAIN_ HIER via via F4-help F4-help

Role

Optional field; specify only if a role dependent mapping is required




















SAP Best Practices

Prequisites Ensure that the Webdnpro service is activated. Normally the activation should have been done during system setup for using the Netweaver Busiess Client. P erform the the following steps steps in case the service is inactive: 1. Access Acces s the the transaction choosing the the following navigat navigation ion option: option: Transaction Transaction cod e

SICF

2. On the Maintain Service screen leave the default values as they are and press Execute (F8). 3. In the Virtual Hosts/ Services tree control locate the node sap/bc/webdynpro. Right click on the node and choose Activate Service from the context menu.

Procedure 1. Navigate to the initial screen of the SAP SA P Easy E asy Access Menu. 2. Do a right-click on Favorites and choose Add other objects from the context menu. 3. Choose Web Dynpro Application from the upcoming dialog box list. 4. On the Web Dynpro Application subcreen, make the following entries. Fi el d n am e





















SAP Best Practices

, OBN-navigation cannot be tested anyway, since the target transactions must be specifed for the specific roles.

3.3.5 3. 3.5

Connect in ing g a PO POWER WER Lis t to a Role

Prequisites Ensure that the Webdnpro service is activated. Normally the activation should have been done during system setup for using the Netweaver Busiess Client. Please use transaction SICF in case the service is inactive (as described in Test a POWER List via SAP Menu ).

Procedure 1. Access Acces s the the transaction transaction choosing one one of the the following navigat navigation ion options: options: SAP ECC menu Transaction Transaction cod e

Tools  Administration  User Maintenance  Role Administration  Roles

PFCG

2. On the Role Maintenance screen make the following entry: Fi el d n am e


Role

Specify the role to be maintained

3. Choose Change





















SAP Best Practices


Result The The POWER List List is avail vaila able as ne new node ode in the role role menu enu and and can can be test ested via via Execute from the context menu (right click). P lease lease remember remember to maintain maintain appropriate Authorizations Authorizations for for the new new entry entry as it is described described in the guide K53_How_to_Guide_EN_DE.doc.

In case the POWER List feeder uses OBN-navigation (method HANDLE_ACTION) and is supposed to call a target transaction, it is necessary to add it on the Menu tab (button Tran Transact sactio ion ns) of the Change Role screen. Here it it also possible to assign the Business Objectsmethod method to the specific transaction transaction and to map the the Business Business Object-parameters. Object-parameters.

Procedure




















SAP Best Practices

Fi el d n am e


Obj. Type

Select the Object Type to be used for OBN-navigation. That is the object specified in method HANDLE_ACTION of the feeder class.

Method

Select the Business Object-method to be used for OBN-navigation. That is the method specified in method HANDLE_ACTION of the feeder class

P lease see see Example for method HANDLE_ACTION for details. 13. Press P ress Enter. Enter. 14. In the upcomming upcomming popup Parameter Mapping make the following entries: Press the Insert Parameter

button and specify the parameter mapping.

Fi el d n am e


Transaction

Screen field of the transaction (can be found out e.g.via F1-help in the transaction transaction screen).



















SAP Best Practices


4 De Descr script ipt ion of the Fe Feede ederr Inte Interface rface 4.1 Description of the Feeder Interface IF_POWL_FEEDER 4.1.1 4.1. 1

Method Meth od GET_ACTIO GET_ACTIONS NS

Purpose Define buttons and their actions (Methods “GET_ACTIONS” & “HANDLE_ACTION”) By maintaining the two methods GET_ACTIONS and HANDLE_ACTION, you have a huge




















SAP Best Practices

PLACEMENT

Placement Toolbar ; (C – Context menu menu [not supported yet]) yet]) B – Toolbar

ENABLED

Flag: action enabled/ disabled

PLACEMENTINDX

Index of placement

IMAGESOURCE

P ath to an action action icon

TEXT

Action description text (e.g. button text)

TOOLTIP

Action tooltip

ADD_SEPARATOR ADD_SEPARATOR

Flag to add a seperator after the action item

ACT_CHOICES ACT_CHOICES

Action Choice




















SAP Best Practices

l st ru_acti ru_acti on_de _def - cardi cardi nal i t y = c_f eeder_acti on_sel _sel _r eq. l st r u_act _act i on_de on_deff - pl acem cement = c_f eed eeder _acti on_t ool bar . l st r u_act _act i on_d on_defef- enabl ed = c_t r ue. l st r u_act _act i on_d on_defef- pl acem cement i ndx = 2. l s t r u_ ac ac t i on_ de def - t ext = t ext - 002. l st ru_acti ru_acti on_de _def - add_sep _separator = ' ' . I NSERT l st r u_acti on_def _def I NTO TABLE l t ab_acti on_de _def . *

r el at ed ag agrr ee eem men entt s l st r u_acti on_d on_def ef - act i oni d = ' AGREEMENTS' . l st ru_acti ru_acti on_de _def - cardi cardi nal i t y = c_f eeder_acti on_sel _sel _r eq. l st r u_act _act i on_de on_deff - pl acem cement = c_f eed eeder _acti on_t ool bar . l st r u_act _act i on_d on_defef- enabl ed = c_t r ue. l st r u_act _act i on_d on_defef- pl acem cement i ndx = 3. l s t r u_ ac ac t i on_ de def - t ext = t ext - 009. I NSERT l st r u_acti on_def _def I NTO TABLE l t ab_acti on_de _def . e_act i ons_ ons_ chan changed ged = c_ t r ue. ct i _defs _defs l t ab ti

_d f





















SAP Best Practices


cons t ant s C_ BW_ I NFOB FOBJ _ GRP_VE P_ VEN NDOR t ype STRI STRI NG val ue ' 0GN_ VEND ENDOR__ 0CI 0CI _ GRP_ RP_ PAR PAR' . " #EC NOTEXT TEXT c onst ant s C_BW_ I NFOBJ FOBJ _ GEN_ EN_ VENDOR t ype STRI STRI NG val ue ' 0GN 0GN_ VENDOR' . " #EC NOTEXT const ant s C_OB _OBN_OP_L _OP_LAU AUNCHBW t ype STR STRII NG val ue ' l aunchbw aunchbw' . " #EC NOTEXT TEXT



















SAP Best Practices

I nser ser t l _t est est i nt o tabl tabl e e_co e_con nf _messag ssage. WHEN OTHERS OTHERS.. Ret ur n.




















SAP Best Practices


PARAM_TYPE

Display type for simple parameters I – Input field, C – Checkbox, D – dropdown list, T textline

SELOPT_TYPE

Criteria type for select options (in case KIND = S)



















SAP Best Practices


For labels or help texts like CRITTEXT, TOOLTIP etc. it is recommended to define text elements (language dependency) instead of using static literals.



















SAP Best Practices

l l l l l l

s _ se sel c r i t - qui c k ks s ea ear c h_ h_ c r i t = ' X' . s _s _s el el c r i t - dat a t yp ype = ' L I FNR' . s _s _s el el c r i t - r ef e f _ t a bl bl e = ' L F FA A1' . s _ se sel c r i t - r ef ef _ f i el d = ' L I FNR' . s_sel s_sel cri t - ddi c_shl c_shl p = ' KRED_C' _C' . s_sel s_sel cri t - al l ow_ad _admi n_cha _change = ' X' .


































































































































































































































SAP POWL Best Practice

Recommend Documents