10 Posts

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.

In this blog it is explained how to do the very first steps with the tools of the MaxDB that are shipped with the ABAP Trial Version download.    In the download of the ABAP Trial Version there are two tools, one for database administration (Database Manager) and the other one for having a look at the tables and the execution of SQL statements (SQL Studio) on tables of interest. Both tools have a GUI as well as a CLI (Command Line Interface) - in this blog only the GUI is used. The database itself (MaxDB) is installed during the installation of the ABAP Trial Version, the tools however must be installed manually. You can find them in the directory 'maxdbtools' of the tree structure of the download. image After installing the tools you will find two new icons on your desktop. image Doubleclick on the Database Manager icon to start this tool.  image The Database Manager comes up with its entry screen.  At first you have to select the database you'd like to administrate. image Click on the 'Add' button. image The system will give you an overview of the databases that are on the selected machine (your PC). In my case, there is only the NSP database from my ABAP Trial Version. Select the database of your choice and press the 'OK' button. image Now the selected object will appear in the upper right window. Click on the Connection icon (red) to get connected to the database. image You have to enter the name of the database manager user for this database and his password. The user is set by the ABAP Trial Version installation to 'control'. The password is the one you entered during the installation process for the database. Press OK. image Since in my case the NSP database is not running, there are red balls at the database icons. Click on the online-icon (highlighted in red) in the menu bar to start the database. If the database is running, there will be a process 'kernel.exe' in the processes list of the task manager of your PC. In additon to that, a service 'MAXDB: NSP' will be started. image Now it's done - the database is up and running and we are connected with the Database Manager tool to it. The entry screen gives you an overview about the database size and the sessions that currently running. Yet you can have a closer look at the different items. For example, click on the 'Information' button on the left menu, a submenu will appear, and then select 'Data Area'. image Here you can see the physical locations where the data is stored. If more storage is needed you can add another volume (Configuration).  Since with the new ABAP Trial Version SP12 the online documentaion for the Database Manager is not available, you can get the information from here .  Click on the 'Tools' button in the menu bar and select 'SQL Studio' or just doubleclick on the 'SQL Studio' icon on your desktop. The SQL Studio will be started. Be sure that the database is running, if you come by way of the desktop item.   image Click on the key button on the left side of the button bar. image Enter the server name where your MaxDB is running, Database = 'NSP', User = 'SAPNSP', Password is the one you entered during the installation of the ABAP Trial Version for the database.  Press 'OK' button.  image This is the entry screen of the SQL Studio.  If you like to see for example which tables are in the ABAP Trial Version, just click on 'Tables' and scroll down. For example, searching for the structure of the SFLIGHT table that is well known from our demos, enter 'SFLIGHT' into the field below button bar and open up the tree beyond 'Tables (SFLIGHT)'.  image Here you can see all elements of table SFLIGHT. If you are eager to know what is inside the table, just go back to the dialog window and enter the open SQL statement 'select * from sflight'. image   If you'd like to have more information on that, click here .    For more Information about MaxDB, click here .     
In the New Blog Series: ABAP Trial Version for Newbies of this series we decribed how to get development objects out of the system. This blog focuses on how to get a transport into a system. In SP11/12 (SP = Service Pack) the transport system is preconfigured. That means you no longer have to distribute the transport environment with the transaction 'STMS'. The only thing that you have to do is to share the 'SAP' folder on the installation level. This was described at the beginning of the previous blog. image The two files for the RFC communication in the 'bin' directory are there - This was done as part of the preconfiguration. The output of the export from the last blog must be copied to the corresponding directory in the new installation. The 'cofiles' directory is for the header of the transport (beginning with 'K'), the 'data' directory is for the data of the transport (beginning with 'R'). Now we come to the actual import. Start the Transport Management System (transaction 'STMS') and click the truck icon in the menu bar. image This is the Import Overview. image Select the NSP queue with a double-click. image Open the context menu of 'Extras' and choose 'Other Requests >> Add'. A dialog box prompts you to specify a transport request. image Click the input help icon. image Select the request you'd like to import and choose 'Enter'. image Choose 'Enter'. image Choose 'Yes' image Select the transport request and click the small truck icon in the menu bar. image Enter '000' as the Target Client and leave the rest unchanged. Choose 'Enter'. image Click 'Yes'. image The import is now running. Click the 'Refresh' button in the menu bar to find out when the import is finished. Start the ABAP workbench and have a look for the migrated component 'Z_MY_QUIZ' from the package 'Z_MY_PACKAGE'. image Activate the new component. To make the new component run you have to create a Web Dynpro Application for it. Select the new component, open the context menu and choose 'Create' >> 'Web Dynpro Application'. Now you can run the migrated object. Open the 'Web Dynpro Applications' folder, select 'Z_MY_QUIZ', open the context menu and choose 'Test'. There are two forums where you can post your questions and ask for help in case of trouble. Software Downloadsfor general discussions about the trial versions ( interesting projects you are doing with it, wishes for the future,…) SAP NetWeaver Application Serverfor concrete problems with the installation
The last ABAP Trial Version for Newbies Part 7: Creating a Program and a Package - An Introduction to the SAP Change and Transport System was about the CTS (Change and Transport System), where you have got a brief overview of the transport mechanism on the ABAP Application Server. This blog explains what you have to do to get a package with your development objects out of a system. For our purposes, exporting a package means to get it out of the ABAP universe to the installation level.  Let's assume that you have created some programs or Web Dynpro components in the old (SP8) Trial Version and you want to upgrade the Trial Version to SP11. You use the transport system to save your programs and components and make them availiable in the new system.   You first need to set up the Transport System for the export.  On the installation level, the 'SAP' directory must be shared to the 'System' user. Open the MS Explorer, select the 'SAP' directory and choose 'Sharing and Security...' from the context menu. Select the 'Share this folder' option, and enter 'sapmnt' as the share name.  image Choose 'Permissions'.  Add a new user 'SYSTEM' with full control. image Choose 'Apply' and then 'OK'.  Now the changes on installation level are complete. To  set up the transport environment, you need to start the Transport Managment System (Transaction STMS). image   Choose 'System Overview' (red rectangle) and select 'CL5' from the table. Open the context menu, and choose 'Extras'. Then, choose 'Distribute and Activate Configuration'. imageimage Leave the distribution options as the default. Choose 'Enter'.   After you have successfully distributed the transport environment, there are two files in the 'bin' directory of the 'trans' tree on the installation level. These files are required by the RFC (Remote Function Call) to retrieve information about the receiver side. image The tree should look like this. Now the setup of transport system is complete.   In our example, we assume that there is a development object 'Z_MY_QUIZ' in an old Trial Version (SP8) that you need to migrate to the new Trial Version (SP11), since you can have only one ABAP Trial Version on your PC. This object is a copy of the 'WDT_QUIZ' Web Dynpro ABAP component in the Trial Version.       To export an object, it must belong to a package.  How to create a package is shown in the previous New Blog Series: ABAP Trial Version for Newbies in this series. The package for migration in this blog is 'Z_MY_PACKAGE'.   Let's assume that the object you want to migrate is created as a local object. (new users do not normally concern themselves with packages and workbench orders.)  You first need to reassign the object to a package. Go to the ABAP workbench (SE80) and select the component you want to reassign.  image This would be the right way to reassign the object, but be careful: there is a bug in the current version. Mime objects will not be written to the export. For that you need to copy the component to a new object that is related to a package.  image Choose ENTER. image The system prompts you with the workbench request to create the package. This request will comprise all the objects from the package, and will be the basis of the transport.   Choose ENTER. image SAVE.  There may be another dialog step - confirm this in the same way.   Now the package Z_MY_PACKAGE which contains all the objects in the Web Dynpro Component/Application Z_MY_QUIZ is linked to the workbench order NSPK900044. In the following steps, this order and the related tasks will be released.  Open the transport organizer (transaction SE09). You will find the virtual system 'CL5' as the destination of our transport.   image Select the correction (NSPK900045) for our workbench order, and click the truck icon in the menu bar. This releases the correction. A released correction cannot be changed. To release a workbench order, all the related corrections must be released first. After releasing the correction, an OK icon appears right to the correction.  image You process the workbench order in the same way. Place the cursor on the workbench order and click the truck icon in the menu bar. This starts the physical transport. image To find out when the transport is finished, you will have to refresh a couple of times. image Now the transport is complete. On the level of the intallation, there is data written to two files. The 'cofiles' directory contains the header information in a file beginning with 'K' followed by the workbench order number and ended with the system ID. image The transport data can be found in the 'data' directory beginning with 'R' followed by the workbench order number and ended with the system ID. image These two files can be copied to the corresponding directories in any other SAP system in order to be imported. This will be the topic of the next blog.  There are two forums where you can post your questions and ask for help in case of trouble. Software Downloadsfor general discussions about the trial versions ( interesting projects you are doing with it, wishes for the future,…) SAP NetWeaver Application Serverfor concrete problems with the installation 
In ABAP Trial Version for Newbies:  Part 2 ' Starting and Stopping the Application Server  ' of this blog series, you logged onto the Application Server as 'BCUSER'. From this starting point, this blog explains how to find the functionality you need.   image Item No.1 is a Command field for the 'Transaction Code'. This is a shortcut to the Transaction (functionality) you want to execute. Position the cursor in the field and press 'F1' to display the documentation.  This is a general feature of the Application Server for online help on input fields.  In ABAP Trial Version for Newbies:  Part 2 ' Starting and Stopping the Application Server  ' of this blog series you were asked to enter 'SE80' in this Command field, which takes you directly to the ABAP workbench. This works only in the logon screen, in all other screens you have to add '/' as the first character and a letter as described in the documentation. For example, if you add an 'o' (as in 'other') before the Transaction Code, a new window will be opened for that transaction. To the right of the Command field, there is an icon to display a history of commands used. Just click the icon and a pull down menu appears with all the transaction codes you entered so far.  Item No.2 are two buttons in the toolbar. The left button opens a new window, which is the same as '/o' in the Command field. The right button is for creating a shortcut on your desktop that will start the transaction you are currently in. You also can create a shortcut to any other transaction.   Item No. 3 is a folder for your Favorite transactions. Since it is not easy to remember all the Transaction Codes you can collect the ones you'd like to use more often in that folder. To make it more convenient for you, the folder displys the title of the transaction instead of the Transaction code. Click the folder icon to open the context menu. 'Insert transaction' adds a new item to your favorites. You can do the same thing by clicking 'Favorites' in the menu bar. If you are in a screen and you don't know the transaction code, just click the 'System' button in the menu bar and select 'Status'. A new dialog box will appear.   image This dialog box shows all the system information for your session. The transaction code used in the favorites folder can be found under 'Transaction'.   One useful hint: In the Favorites folder and in the SAP Menu you can display the Transaction Code in the beginning of each line (see screenshot below). For that, click on 'Extras' in the menu bar and select 'Settings' and check for 'Display technical names'.   Item No. 4 is a navigation tree to the different transactions. Just open up the SAP menu, click 'Tools', open the 'ABAP Workbench' folder, open 'Overview' folder, and then you'll find the 'Object Navigator' item. image Double-click that item, and the 'SE80' transaction is started.  Since the ABAP Trial Version is only the Application Server, there are no business-oriented transactions in the navigation tree. image There are three buttons in the middle of the toolbar, all for navigation purposes. They are highlighted when active.   The green button is the 'Back' button, which goes back to the previous screen.  The yellow button is the 'Exit' button that interrupts the transaction and takes you straight back to the entry screen.  The red button is the 'Cancel' button that stops the transaction, but will not always return you to the entry screen.   To close the session, just enter '/nex' in the Command field and press 'Enter' or the green 'OK' icon to the left of the toolbar. All open sessions will then be terminated without any dialog.   There are two forums where you can post your questions and ask for help in case of trouble. Software Downloadsfor general discussions about the trial versions ( interesting projects you are doing with it, wishes for the future,…) SAP NetWeaver Application Serverfor concrete problems with the installation 
In ABAP Trial Version for Newbies:  Part 1 ' Download and installation of the Trial Version ' of this blog series you successfully downloaded rar files from SDN, and you completed the installation process. At the end of the installation, you were asked whether you wanted to start the Application Server. In accordance with the governance described in the previous weblog, it would be a good idea to install the SAP GUI first. The SAP GUI should be installed before you proceed with Part 2.   Now you are prepared to start the Application Server with the SAPMMC. SAPMMC is a SAP snap-in for the Microsoft Management Console (MMC). SAPMMC allows you to administer all the SAP systems running on a particular machine. To start the SAPMMC in Windows, choose Start -> Programs -> SAP -> Start SAP Management Console, or click the meter icon on your desktop at any time. For our ABAP Trial Version with the system ID 'NSP' the MMC will look like this: image The left pane shows a tree with the elements of the NSP system consisting of the database and the Application Server.  The Application Server also provides information about the current system operation. Clicking the question mark will take you to the documentation that explains in detail the layout and context menu of the SAP System Manager Snap-In.  To start the NSP system, choose the NSP icon, go to the context menu and choose 'Start' or simply click on the triangle in the tool bar. The database is started first, and after a short while, green lights will indicate that the NSP is running. To check if the server has started completely select the  'ABAP WP Table' node in the left pane, which displays the workprocesses, the work horses of an ABAP system. Details about the workprocesses will be covered in a later blog. For the moment we just use the display to see that everything has started.   image If you want to start the system directly without the MMC you can also get to that point by choosing Start -> Programs -> SAP NetWeaver 2004 Trial Version -> NSP -> Start Application Server. This will not start SAPMMC, but it is easier, and if your are not interessted in system information, it might be sufficient for your needs.  Now it would be ok to log on to the system. To do this, start 'SAP Logon' (that is installed with the SAPGUI), click 'New Item' and double-click 'User Specified System' in the next dialog box. Enter the system parameters requested. The screenshot below shows the configuration for running an Application Server and SAP Logon on the same machine,which is our recommendation for the ABAP trial version. (If you prefer to install the GUI on another machine you have to make sure that the server PC is reachable via TCP/IP, has a valid IP address or DNS entry, that no firewall is blocking the GUI protocol etc.) image Click 'Finish' and a new entry for 'NSP' is displayed in the SAP Logon window. image Select 'NSP' and click 'Log On'. After a few seconds, the log-on screen appears. image The connection between your Application Server and SAP GUI is now up and running, - Congratulation !  The following users have been created in your NSP system by default:     - 'BCUSER' for the standard user (e.g. development)    - 'DDIC' for administration     - 'SAP*' for license purposes  There is a temporary 30 day license on every NSP system after installation, which can be extended by 90 days again and again (and will be described in another blog).  Use the 'BCUSER',with the password 'minisap' (as can be seen on the last screenshot) and press 'Enter' or click the green icon at the beginning of tool bar. The entry screen should look like the screenshot below. image Pressing the 'Help' button will open up a menu. The first entry is 'Application Help' which links directly to the SAP documentation for the subject you are currently working on. This is only available in the new ABAP Trial Version (SP11).  In the field that has the cursor, you can enter the so-called transaction code. This is a shortcut e.g. 'SE80' to start the development environment that takes you directly to the functionality you'd like to use.  Try it out and enjoy!  image This is the development environment (ABAP workbench) of the ABAP Application Server. Here you can find most of the tools for building business applications in ABAP. If you now open the 'Help' menu and select 'Application Help' a browser will appear and show you an overview of the functionality in the ABAP workbench. image When you have finished checking out the ABAP Trial Version, you can use the SAPMMC to stop the system. Select the NSP icon, go to the context menu and choose 'Stop' or just click the black rectangle in the tool bar, which will stop the Application Server but not the database.  Another way is to do this is: Click Start -> Programs -> SAP Netweaver 2004 Trial Version -> NSP -> Stop Application Server.  This will also stop the database.  In one of the next parts of this blog, we'll show you how easy it is to write a simple program in ABAP.  There are two forums where you can post your questions and ask for help in case of trouble. Software Downloadsfor general discussions about the trial versions ( interesting projects you are doing with it, wishes for the future,…) SAP NetWeaver Application Serverfor concrete problems with the installation 
If you're interested in the Trial Version and you like to download it, please check the system requirements first. If your PC doesn't meet the requirements the installation might fail or the performance will be very bad (which might reduce the fun to work with ABAP). The download consists of two rar-files SAPNW2004sABAPTrialSP11.part1.rar and SAPNW2004sABAPTrialSP11.part2.rar. These two file should be downloaded into same directory. Since both of them are bigger than 1 GB the download might take some time. To find out whether the downloads are complete you can check the file size (click on the file in the Explorer and choose 'Properties'): …part1.rar = 1.572.864.000 and …part2.rar = 1.189.536.491 If everything is alright so far you have to extract the files with an appropriate rar-tool (if there is none on your computer just google for 'rar tool download' and download and install it on your PC). Just click on the first one (…part1.rar) and after a little while your unpacked structure should look like:


The rar-tool creates a structure that you can see in the right side of the Explorer window. In the DOC directory you can find all HTML stuff related to the installer. The image is the installation itself. There are two database tools in the maxdbtools directory. And the SAPGUI directory contains a Compact SAP Logon 7.10 that you should use as User Interface. To start the ABAP server installation click on 'start.htm' and follow the dialog steps.


Be sure to check the system requirements. It is also important that there are no remnants of an older Trial Version or Sneak Preview installation left on your PC.
The Installation can be started from the Installation page by clicking on the word 'Installer'.
Be aware that the installation of an SAP system is typically a pretty complex task, with installing a database, starting it, filling it with a huge amount of data, configuring the network connection, starting the system and doing lots of configuration steps. Therefore the installation guide of a real SAP system consists literally of hundreds of pages for experienced administrators. All this is hidden in this trial version as good as possible but nevertheless it is done under the hood. So it might be a good idea to leave the installation alone and not to work heavily on the PC during the installation.


This window shows you the real beginning of the installation process. The only information you have to provide during the installation is the target directory and you have to define the master password for the database. (the users of the ABAP trial server itself and their passwords are predefined)
The installation typically takes between half an hour and two hours dependent on your hardware. Therefore you have to be patient especially at 16% and 43%. Don’t worry if the installation seems to make no progress for a while at these points. As long as the hard disk is turning everything is ok. If you cancel the installation process manually you might leave the system in an indefinite state which may cause trouble with a new installation.


When the installation is finished the system will ask you how you to proceed. If you have already a SAP Logon on your PC you just can click on 'Next' which will start the Application Server and the SAP Management Console for monitoring purposes. If you don't have the SAP Logon yet on your PC, it would be a good idea to uncheck the check-boxes and install the GUI first. For that you have to go to the SAPNW2004sABAPTrialSP11 directory and open SAPGUI folder.


By doubleclicking on 'SapGuiSetup.exe' you will start the installation of the Compact SAP Logon 7.10. In the dialog you are guided through some information pop-ups and finally you come to the window with the product selection. Just click on the 'Select all' that will check the check-box for you and then choose 'Next' and finish the installation.


image There will be a new icon for SAP Logon on your desktop now. After the installation of the SAP Logon a reboot might be required.

In the next edition of 'ABAP Trial Version for Newbies' it is shown how to start the Application Server and how to logon with the SAP GUI to the system.

There are two forums where you can post your questions and ask for help in case of trouble.

Software Downloadsfor general discussions about the trial versions ( interesting projects you are doing with it, wishes for the future,…)

SAP NetWeaver Application Serverfor concrete problems with the installation

With the new build of the SAP NetWeaver 2004s ABAP Trial Version (SP11), we in SAP NetWeaver Product Management are eager to introduce, through a series of blogs, SAP ABAP technology to those with limited ABAP experience. While the Trial Version allows developers who are new to SAP to start learning ABAP it can also serve more experienced ABAP developers as a sandbox for more ambitous development experiments or to learn basic administrative tasks. In any case what you should have is a basic understanding of IT, and experience in at least one programming language. The blog series will start with easy - but essential - topics such as starting and stopping the SAP NW ABAP Application server from the management console. They'll lead you to the development environment, where you can check out how easy and convenient it is to write applications in ABAP. Of course, the blogs cannot replace a solid training in ABAP technology, but it can serve as an appetizer before you delve deeper. With every blog, your knowledge of SAP technology will improve. And finally, you will have an overview of what's going on in the ABAP application server. Feel free to make a suggestion for the topic you are interested in.


Part 1 ' Download and installation of the Trial Version '

Part 2 ' Starting and Stopping the Application Server ' 

Part 3 ' Why and How the Server Matters to You as a Developer: Server Architecture and Work Processes ' 

Part 4 ' Many Developers On One Central Server - How Does It Work ' 

Part 5 ' Navigation in the Application Server ' 

Part 6 ' A first Hello-World-Program ' 

Part 7 ' Creating a Program and a Package - An Introduction to the SAP Change and Transport System ' 

Part 8 ' Exporting development objects from SP8' 

Part 9 ' Importing a transport into SP11 ' 

Part 10 ' A First Little Business Program '

Part 11 ' Getting More Familiar With the ABAP Dictionary '

Part 12 ' Debugging in ABAP '

Part 13 ' Get Your Program up to Speed ' 

Part 14 ' The Foundation of an Application - Creating the Database Tables '

Part 15 ' How to Dynamically Create Test Data for Our Database Table '

Part 16 ' MaxDB: Database Manager and SQL Studio '   

Part 17 ' Your first ABAP Object

Part 18 ' Starting with Web Dynpro for ABAP '


There are two forums where you can post your questions and ask for help in case of trouble.


Trials, Previews & Other Downloads for general discussions about the trial versions ( interesting projects you are doing with it, wishes for the future,…) Web AS Preview Installation for concrete problems with the installation.

If you start the ABAP Workbench (transaction SE80) and the appearence is like the picture below with some areas left blank (red frame) then the problem might be caused by an upgrade of the MS Internet Explorer to release 7.00. The combination of SAP GUI for Windows 6.40 and the MS IE 7.00 requires at least patchlevel 20 on the SAP GUI.
There are also some other functionalities e.g. 'online help' effected by that issue.


To find out what patchlevel your GUI is running just click on the SAP GUI icon and open ' properties '. For our ABAP Trial Version community we provide a patch that can be downloaded from SDN. This patch is an exe-file that has to be executed on the machine your SAP GUI for Windows 6.40 is installed. After running this file the patchlevel of SAP GUI will be 23.

With the release of SAP NetWeaver 2004s, ABAP developers can now take advantage of Web Dynpro’s revolutionary approach to develop web-based user interfaces (UIs).  What makes Web Dynpro so different to the current UI technologies? Well, Web Dynpro uses declarative programming techniques – you design your application and the framework generates meta data in XML format which is then translated into ABAP classes. Tools support you to design the UI layout with immediate data binding to contexts, and mapping of contexts to other components and models. OK, let's not get carried away with too much Web Dynpro terminology – the bottom line is, this approach reduces your coding work substantially. Don’t worry - you’ll still be able to write ABAP since you can extend the application by writing your own action handlers and methods. Web Dynpro is based on the Model View Controller (MVC) design paradigm which is widely accepted as the best UI architecture for all complexity levels. The Web Dynpro tools are integrated into the ABAP Development Workbench allowing seamless integration with the latest ABAP features – new editor, new debugger, and enhancement framework plus all the existing SE80 features. There are also plenty of new-need features along the way for you and the end-users. It’s a snap to provide value help for users and to integrate Adobe Forms. Users can personalize your application by hiding or renaming fields. This Web Dynpro service is provided out of the box - no implementation necessary. Want to have your Web Dynpro application in a SAP NetWeaver Portal? Well, guess what - there’s an iView template waiting for you.  Join the session to see ABAP Web Dynpro firsthand and make a new development experience in the hands-on exercises and see for yourself - Web Dynpro for ABAP rocks.

At TechEd Las Vegas, Amsterdam and Bangalore we'll have hands-on sessions for novices and experts. So watch out for:

CD 154 Web Dynpro for ABAP Part 1 - the basics
Prerequisite: You must be familiar with object-orientated ABAP programming
Las Vegas, Amsterdam, Bangalore
CD 264 Web Dynpro for ABAP Part 2 - advanced topics
Prerequisite: You must have attended CD 154
Las Vegas, Amsterdam, Bangalore