Entering content frameComponent documentation Web Transaction Tutorial Locate the document in its SAP Library structure

Purpose

This documentation is a step-by-step introduction to developing screen-based Internet applications that are driven by the Internet Transaction Server (ITS) and enable users to run R/3 dialog transactions from any Web browser. These applications – known as Internet Application Components (IACs) or Web transactions – are developed using the Web Transactions implementation model.

You develop Web transactions both inside and outside the R/3 System:

The SAP@Web Studio is a PC tool for creating, changing and managing all the files required by the ITS to run R/3 transactions as Web transactions from a Web browser. When you have created and tested the application, you can source-control all the files in the R/3 System by checking them into the R/3 Repository and assigning them to a change request, just like any other development object.

The ITS files required to run a Web transaction include a service description and HTML templates (one for each screen in the R/3 transaction).

To enhance the performance and appearance of your Web transaction, you may also include language resource files to keep HTML templates language-independent and Multipurpose Internet Mail Extension (MIME) files, which contain graphic, image and video elements.

At runtime, the ITS interfaces between the Web server and the R/3 System to control dialog processing. On each screen change (PBO), the R/3 System sends all data for display on the new screen to the ITS. The ITS merges this data with the relevant HTML template and passes the finished HTML page to the Web server.

When the Internet user enters data on this page, the Web server returns the data to the ITS, which in turn passes it back to R/3. The R/3 System receives this data, merges it with the relevant ABAP fields and triggers PAI processing.

What the Web Transaction Tutorial Covers

This tutorial is designed to be read as a continuous document. It covers all the steps you have to take if you want to convert R/3 dialog transactions to Web transactions based on the Web Transactions implementation model and use the SAP@Web Studio as development environment.

Due to the inevitable differences between running a transaction from the SAP GUI and running a transaction from a Web browser, this means modifying the ABAP code of the underlying R/3 transaction, and the HTMLBusiness code generated for each R/3 screen.

Further Information

What the Web Transaction Tutorial Does Not Cover

This tutorial does not teach you how to create dialog transactions in R/3. It assumes that you are familiar with ABAP programming techniques, and that you know how to use the various programming tools available in the ABAP Workbench.

Further Information

For detailed information about ABAP programming techniques and ABAP Workbench tools, click on the relevant link below.

If the links do not work from your current location, and you are outside the R/3 System, log on to the latest release and follow the directions for the documentation you want to view.

In the R/3 System, see under Help ® SAP Library ® Basis Components ® ABAP Programming and Runtime Environment (BC-ABA) ® BC – ABAP Programming

In the R/3 System, see under Help ® SAP Library ® Basis Components ® ABAP Workbench (BC-DWB) ® BC – ABAP Workbench Tools

In the R/3 System, see under Help ® SAP Library ® Basis Components ® ABAP Workbench (BC-DWB) ® BC – ABAP Workbench Tutorial

In the R/3 System, see under Help ® SAP Library ® Cross-Application Components ® Business Framework Architecture (CA-BFA)

Leaving content frame