Show TOC

Process documentationImplementation of a Simple Customer-Specific Reporting Service


This section explains the essential steps for creating a simple example reporting service with either a list or a form GUIBB as input for the backend report, and one document (PDF, office document, url) display.

Note Note

End of the note.

You can find information on how to implement more complex scenarios in section Detailed Configuration.


  1. Analyze the reporting scenario that you want to implement. You need to be familiar with what you are trying to achieve. This step is especially of importance if you want to reuse a report based on Web Dynpro for Java that you used in the Business Package for Employee Self-Service (up to and including 1.41).

  2. Create a feeder class for your application and implement the 2 essential methods, GET_DEFINITION and GET_DATA.

  3. Complete the Methods of Your Feeder Class to bring it to life, in particular the GET_DATA method where you add the code for calling your report.

  4. Create your Web Dynpro application and determine it as an Overview Page Floorplan (OVP).

  5. Create the OVP configuration, into which you insert the screen elements in the next steps.

  6. Create the initial screen, into which you embed a reuse component for PERNR selection.

  7. Create the main screen, into which you embed a form GUIBB or list GUIBB for the user to make selections. You also embed here the reuse UIBB which takes care of outputting the document result (PDF, XLS, etc.) of your backend report.

After you have completed the implementation steps, test your application.