POWL: Infoset Generation with Web Dynpro ABAP Applies to: WebDynpro ABAP Developer. For more information, visit the Web Dynpro ABAP homepage. Summary: This document explains how to create an Infoset, generate the structure and create the Query for the Infoset. Author: Avik Saha Company: IBM India Pvt. Ltd. Created on: 1 January 2010 Author Bio Avik Saha is an SAP NetWeaver Portal Consultant at IBM India Pvt. Ltd. in Kolkata, India 2010 SAP AG 1
Table of Contents Prerequisites... 3 What is POWL (Personal Object Work List)?... 3 What is an Infoset?... 3 Infoset creation using SAP tools... 4 Related Content... 8 Disclaimer and Liability Notice... 9 2010 SAP AG 2
Prerequisites You are using the SAP ERP 6.0 Enhancement Package 03 and you have access to the SAP NetWeaver Business Client. What is POWL (Personal Object Work List)? The POWL is basically a framework that can list business objects and allows specific activities (actions) based on these business objects. This is an individual list generated by query that provides an overview of the user's working environment by presenting one or more list of objects, as a set from which the user can select items to work on. POWLs are most suited to assignments that are not part of a workflow. What is an Infoset? The InfoSet is what is responsible for the retrieval of the data from the ALV (ABAP List Viewer) reports. The technical basis for the new, so-called streamlined reporting is the InfoSet Query and its underlying InfoSet. Infoset can be created in two possible ways: Creating and generating an InfoSet based on an existing ABAP List Viewer (ALV) report. This is supported by SAP tools specifically designed to generate InfoSet and InfoSet Query. Manually create a new InfoSet and InfoSet Query based on existing information for all non-alv reports. Here we only see the creation of Infosets for ALV reports using SAP tools. 2010 SAP AG 3
Infoset creation using SAP tools Step 1: Go to the transaction SQ_REPORT_INFOSET Step 2: Give an Infoset name for the ALV report and click Create button. Step 3: Provide the following any one for which you are creating the Infoset. It may be the Transaction Code or Report Program or the Data source. Provide the Structure name which will be generated as table structure into database. 2010 SAP AG 4
Step 4: Below screen will come. Click on Execute button to run the report. Step 5: After executing the report with proper selection criteria and coming back to the Maintain Report Infoset screen you can see like below. On the right hand side at New structure area, all the column fields of report output are visible. Here you can also delete the fields whichever you do not need in your structure. Then click on Generate Structure button. 2010 SAP AG 5
Step 6: Save it into a package at next prompt by clicking on the button. At the time of structure generation it will ask for the transport request where you transport your objects. If any existing request is there, choose that one and click on the button. Otherwise create a new request using the button and select that one and click on the button. Step 7: Then go to Infoset tab and click on Generate Infoset button. Step 8: Repeat the same task as Step 6. 2010 SAP AG 6
Step 9: Then go to Queries tab and generate query with proper user group and query id. Click on the Generate Query button. After Query generation the screen looks like below. 2010 SAP AG 7
Then you can run the query by right clicking and execute. Related Content http://wiki.sdn.sap.com/wiki/display/wdabap/main http://help.sap.com/saphelp_srm70/helpdata/en/80/c8cbf89a394eaaa59767d0faf958d3/content.htm 2010 SAP AG 8
Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document. 2010 SAP AG 9