This documentation is a step-by-step introduction to developing screen-independent Internet applications that are driven by the Internet Transaction Server (ITS), access data in the R/3 System (or any other external system) and can run from any Web browser.

This implementation model allows you to develop Internet applications that consist of linked HTML pages, which you can populate with data retrieved from the R/3 System (or any other external system). The pages can offer a range of application functions, and are generated by following hyperlinks or processing HTML forms. The dialog flow is determined on the client side by the user, who can navigate freely between pages.

Since the dialog flow is not fixed in advance, much depends on what the user decides to do. This contrasts with the dialog flow in other business scenarios, where the business application can put restrictions on how users can navigate.

The following graphic illustrates the basic concept:

You should consider using this implementation model for applications that offer many application functions on one page, and the dialog flow is not fixed in advance.

Such applications have simple point-and-click user interfaces, limited manual data input, and reduced data formatting requirements. They are often used in e-commerce scenarios.

To develop applications that use flow files where the business logic is implemented in module calls from the R/3 System, you need to install the following components:

• The ITS

• The SAP@Web Studio

• The R/3 System

Like all other implementation models, there is a clear separation between business logic and presentation aspects. In this case, defining the dialog flow is also a separate task.

• You implement a set of modules that comprise the business logic in the R/3 System (or other external system).

• You implement the presentation and the dialog flow in the SAP@Web Studio.

• The presentation determines the look and feel of each application.

• The dialog flow determines which template is displayed when, depending on what the user decides to do next.

When you have defined the business logic in R/3, created all the files required by the ITS to drive the application in the SAP@Web Studio, you can source-control the files by checking them into the R/3 Repository. Users can run the application from any Web browser.

This tutorial is designed to be read as a continuous document. It covers the steps you have to take if you want to develop screen-independent Internet applications that are driven by the ITS, based on flow logic and use the SAP@Web Studio as development environment. The tutorial refers to a specific example application.

For a full description of the flow logic implementation model, including a list of flow logic syntax elements and their usage, see:

For further information about other ITS implementation models, see:

This tutorial does not teach you how to create remote-enabled function modules or BAPIs. 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 of the R/3 System.

For further information about ABAP programming techniques, ABAP Workbench tools, and BAPI programming, 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.