HowToReadonlyvisiblefieldsinPOWL (1)

7/31/2019 HowToReadonlyvisiblefieldsinPOWL (1)

http://slidepdf.com/reader/full/howtoreadonlyvisiblefieldsinpowl-1 1/10

ow To...

ead only visible fields in POWLApplicable Releases:

SAP NetWeaver 7.01

SAP NetWeaver 7.11

rsion 1.0

rch 2008e 1 of 9

AP NetWeaver

ow-To Guide



opyright 2008 SAP AG. All rights reserved.art of this publication may be reproduced ormitted in any form or for any purpose without the

ess permission of SAP AG. The information containedn may be changed without prior notice.

e software products marketed by SAP AG and itsibutors contain proprietary software components of r software vendors.osoft, Windows, Outlook, and PowerPoint aretered trademarks of Microsoft Corporation.DB2, DB2 Universal Database, OS/2, Parallel

lex, MVS/ESA, AIX, S/390, AS/400, OS/390,400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,ligent Miner, WebSphere, Netfinity, Tivoli, Informix,S, POWER, POWER5, OpenPower and PowerPC are

emarks or registered trademarks of IBM Corporation.be, the Adobe logo, Acrobat, PostScript, and Readerither trademarks or registered trademarks of Adobe

ems Incorporated in the United States and/or othertries.le is a registered trademark of Oracle Corporation.X, X/Open, OSF/1, and Motif are registeredemarks of the Open Group.x, ICA, Program Neighborhood, MetaFrame,Frame, VideoFrame, and MultiWin are trademarks ortered trademarks of Citrix Systems, Inc.

ML, XML, XHTML and W3C are trademarks ortered trademarks of W3C®, World Wide Webortium, Massachusetts Institute of Technology.is a registered trademark of Sun Microsystems, Inc.Script is a registered trademark of Sun Microsystems,

used under license for technology invented andemented by Netscape.DB is a trademark of MySQL AB, Sweden.R/3, mySAP, mySAP.com, xApps, xApp, SAP

Weaver, and other SAP products and servicestioned herein as well as their respective logos areemarks or registered trademarks of SAP AG inmany and in several other countries all over the world.ther product and service names mentioned are theemarks of their respective companies. Data containedis document serves informational purposes only.onal product specifications may vary.e materials are subject to change without notice.e materials are provided by SAP AG and its affiliated

panies ("SAP Group") for informational purposes only,out representation or warranty of any kind, and SAPp shall not be liable for errors or omissions with

ect to the materials. The only warranties for SAPp products and services are those that are set forth inxpress warranty statements accompanying suchucts and services, if any. Nothing herein should betrued as constituting an additional warranty.e materials are provided “as is” without a warranty of

kind, either express or implied, including but noted to, the implied warranties of merchantability,ss for a particular purpose, or non-infringement.shall not be liable for damages of any kind includingout limitation direct, special, indirect, or consequentialages that may result from the use of these materials.does not warrant the accuracy or completeness of themation, text, graphics, links or other items containedn these materials. SAP has no control over themation that you may access through the use of hot

contained in these materials and does not endorseuse of third party web pages nor provide any warranty soever relating to third party web pages.NetWeaver “How-to” Guides are intended to simplify roduct implementation. While specific productres and procedures typically are explained in aical business context, it is not implied that thoseres and procedures are the only approach in solving afic business problem using SAP NetWeaver. Should

wish to receive additional information, clarification orort, please refer to SAP Consulting.software coding and/or code lines / strings (“Code”)ded in this documentation are only examples and arentended to be used in a productive systemonment. The Code is only intended better explain and

alize the syntax and phrasing rules of certain coding.

does not warrant the correctness and completeness of Code given herein, and SAP shall not be liable fors or damages caused by the usage of the Code, except

ch damages were caused by SAP intentionally orly negligent.aimere components of this product are based on Java™. Any change in these components may cause unpredictable

severe malfunctions and is therefore expressively ibited, as is any decompilation of these components.



Java™ Source Code delivered with this product is only used by SAP’s Support Services and may not befied or altered in any way.



pographic Conventionse Stylemple Textcriptionds or characters quoted the screen. These

ude field names, screens, pushbuttons labels,u names, menu paths,menu options.

ss-references to other umentationmple text

phasized words or ses in body text, graphic

s, and table titlesand directory names andpaths, messages,es of variables andmeters, source text, andes of installation,ade and database tools.r entry texts. These areds or characters that your in the system exactly asappear in the

umentation.able user entry. Angle

kets indicate that youace these words andracters with appropriatees to make entries in theem.s on the keyboard, for mple, F2 or ENTER.

nsncriptiontion

e or Importantmpleommendation or Tip

mple textmple text

xample>MPLE TEXT



ble of Contents

pose............................................................................................................................1pe ...............................................................................................................................1requisites....................................................................................................................2p-by-Step Procedure ..................................................................................................3

figuration settings ...............................................................................................3nges in feeder class............................................................................................4



urposeently, when a personal object worklist or POWL is accessed from the SAP Netweaver Portal or Netweaver Business Client, the contents of all fields contained in the feeder class are read. Thisinvolve complex selection procedures accessing several data sources in order to select all fieldsntially required for display. For the end user, this long selection is perceived as poor systemormance since it may take some time for the results of the POWL query to be displayed. If only aset of the fields is initially visible to the end user, then the large initial selection is a waste of em resources.user can already personalize which fields he or she wishes to see in the POWL by setting up a number ews that use ABAP List Viewer or ALV to determine which columns are displayed in each view

tings). Instead of selecting and filling all fields in the feeder class at run time, applications thatect to do large and complex selections at run time can now implement a logic whereby only thes selected for display in the chosen ALV view are read at run time. This results in faster ormance in the eyes of the end user. When the user switches to a view that contains differents, a new selection will take place to access the fields required for that view. This will lead to moreshes, as data is read on demand.

UTION

oon as a new field is added to the list of visible fields, a refresh will be triggered.refore, this feature needs to be used with care. If the visible fields in the work listnge very often, it is recommended not to make use of this feature as it couldsen the performance.

copewill provide applications using the POWL with an option to improve performance when largebers of fields are being selected via the feeder class. Note that the implementation of this feature is

onal for applications using the POWL. There is no need for existing applications that do notcipate performance issues for long selections to change their applications.

portant

performance benefit is not inherent in the framework itself, but will be achieved byapplication developers working with this function.requirement does not handle so-called lazy loading. If the view contains more fields thanbe shown on the screen and the user has to scroll right to see some of the fields, the feeder classstill read all visible fields rather than reselecting on each scrolling action. Either the applicationt consider splitting “wide” lists into separate views for delivery to the customer, or the/administrator at the customer site can split “wide” lists into separate views. Similarly, if the resultse query contain more lines than can be shown on the screen and the user has to scroll down tothe remainder of the list, the feeder class will still read all the lines rather than reselecting on eache down action. There will be no “tree” logic, where the top nodes of a hierarchy are presented touser and then the objects of the next node of the hierarchy are read when the user clicks on thee.



rerequisitesapplication has implemented a feeder class, and the necessary customizing. Moremation about developing the feeder class can be found ats://bis.wdf.sap.corp/twiki/pub/Applications/POWL/POWLHow_to_Guide.pdf



tep-by-Step Procedureonfiguration settings

mplement the logic to read only visible fields in ‘get_objects’ method of e feeder class.rder to use this feature the following steps need to be performed.

1

onfiguration settingse the implementation of this feature is optional, it is provided via configuration possibility. This can

chieved by following the steps given below.tart transaction SE80 and enter the Web Dynpro Component POWL_UI_COMP.ght click on node POWL_UI_COMP or 'Component Configurations' nfiguration.nter 'POWL_UI_COMP' into the field component name and choose a name for your iguration.ick tCreate.lick the Component-Defined tab (in an SAP ERP EhP3 system the tab’s name is Explicit Configuration).

The Web Dynpro Configuration editor will open..



ick Save, to save the configuration.o back to SE80 and select the node Web Dynpro ApplicationsRight clickte/change configurationn the Application Configuration editor, enter the following

• Application = POWL

• Configuration : {your choice}Click Create

13. In the table, under the Configuration column, enter the name of the previously created

omponent configuration.lication Configuration settings for ‘Read Visible Fields only’

Click Save, to save your configuration

2

hanges in feeder classrder to improve the performance you need to implement the logic to read only visible fields in_objects’ method of the feeder class. This can be achieved by following the steps given below.

tart transaction SE24 and enter the name of your feeder class.

Double click ‘get_objects’ method.importing parameter ‘I_VISIBLE_FIELDS’ which contains the list of visible fields on

e ALV at any given point in time, will display

6. Choose typeSpecific from the drop down menu of the ADD button.

7. Select the node TYPE_SPECIFIC . Choose the corresponding POWL Type fromthe input help in field Type. Select the ‘ReadVisibleColumns ’ checkbox .

create/change

Now you can create the application configuration

15. In SE80, above the object tree, click Refresh to display your configurations.

16 Right click and select Test or addi the URL Parameter 'sap-wd-configId={YOUR_CONFIGID}' to test the configuration.

Click on Change.



itional importing parameter to get the list of visible columns in ‘get_objects’ methodsing this importing parameter you can write the logic to fetch only the visible set of fields frome database in order to improve the performance.Save and activate your class.

ample

example for this implementation can be found in package ‘POWL_TEST’. The example feeder ss is ‘CL_POWL_VISIBLE_COLUMNS_TEST’.

HowToReadonlyvisiblefieldsinPOWL (1)

Documents

Transcript of HowToReadonlyvisiblefieldsinPOWL (1)