Currently Being Moderated

This blog is about how to get the sample solutions and the data generator of the Enterprise Sales Model into your local Netweaver 2004s ABAP Trial Version. These are the essential parts of the hands-on session for Web Dynpro ABAP held at TechEd2007. Have a look at the download where you'll find 3 transports and the documentation (CD255.doc) for the exercises.


You can find a brief introduction to how to get transports in and out of the ABAP Trial Version in ABAP Trial Version for Newbies: Part 8 ' Exporting development objects from SP8 ' and ABAP Trial Version for Newbies: Part 9 ' Importing a transport into SP11/12 ' of the New Blog Series: ABAP Trial Version for Newbies about the ABAP Trial Version. Download the all object and unzip the transports. Share the SAP folder on installation level (see ABAP Trial Version for Newbies: Part 8 ' Exporting development objects from SP8 ' , the first two screenshots at the beginning). Copy the R / K - to the files from the transports to the appropriate folder in the transport system (see below).    

Start the ABAP Trial Version and log on to the system. Open the transport managment system with transaction 'STMS' .

Click the 'truck' icon in the menu bar to go to the import queue.


Select the 'NSP' queue and open menu 'Extras >> Other Requests >> Add'.

Click the input help. Three requests are displayed. It is necessary to import the objects in the following order:

  1. Y7AK068639
  2. BCEK179792
  3. NWRK900015


Select 'Y7AK068639' and press the 'OK' button.


Press the 'Enter' button. 


Press 'Yes'. 

Select the import request and click the small 'truck' icon. 


Enter the Target Client '000', leave the rest unchanged and press the 'OK' button.

Now the import is started. This is indicated by the 'truck' icon on the right hand side. The import can take a couple of minutes. Click on the 'Refresh' button to find out when the import is finished. Then the 'truck' icon is replaced by the 'OK' icon (see below).


After this request has been completed, the other two transports must be imported into the system in exactly the same way before. Open menu 'Extras'>> Other Requests >> Add' and proceed in the same way you did with Y7AK068639. 


Finally the Import Queue should look like the screeshot above. You can safely ignore the yellow triangle with request BCEK179792.

The next step is to create test data for the TechEd exercises. Start Transaction S_NWDEMO_DG.


Leave all items default and press the 'OK' button. Now the data generator creates the data records for the Enterprise Sales Model. This may take a few minutes. A dialog box is displayed when data generation is finished. 

Each Web Dynpro application has ist own HTTP service handler in the ABAP server, which is the entry point to the application and is accessed by the browser. To test a Web Dynpro application, the application's HTTP service has to be active. But for security reasons the HTTP services for freshly imported Web functionality, like Web Dynpro applications are switched off by default. Therefore we have to actively activate the HTTP services for the new Web Dynpro examples in our system.
Start transaction 'SICF'.


Click the 'OK' icon.

Open the tree 'sap/bc/webdynpro/sap'. At the end, you will find the services for your sample solutions beginning with 'zwd_00_bpartner....' .

Select the five services, go to the context menu and click 'Activate Service'.

Now all the preparations for the Web Dynpro ABAP training is done. Have a look at the documentation for the exercises and have fun working with the development environment of Web Dynpro ABAP.

To get an overview on Web Dynpro ABAP first, check out the recorded session CD214 Web Dynpro ABAP Overview

The last exercise (ZWD_00_BPARTNER_SO_INVPDF) requires an Adobe Document Server (ADS) running on a Java engine. For that reason, it will not work properly if the ADS is not available. In a later blog, we will show how to set up the ADS.