Show TOC

 Overview of the ABAP WorkbenchLocate this document in the navigation structure

Purpose

This section introduces you to the ABAP Workbench and the basic concepts you need to be familiar with before using it. The ABAP Workbench is a collection of tools you use to develop, test and run ABAP programs.

Integration

All tools in the ABAP Workbench are integrated. For example, when you edit a program in the ABAP Editor and want to open an object created with another tool, you just need to choose the object and the ABAP Workbench automatically launches the tool you need to edit that object.

To help you organize your application development in this integrated environment, SAP has developed the Object Navigator . It provides a tree-like hierarchy of development objects that makes it easier for you to navigate and edit the objects you need.

Note

We recommend that you use the Object Navigator as a starting point when you develop your applications. For this reason, this documentation is written from the perspective of an Object Navigator user.

Features

What are Development Objects and Packages?

When you work with the ABAP Workbench, you work with development objects and packages. Development objects are the individual parts of an ABAP application. Some examples of development objects are:

  • Programs: reports, transactions, and function modules
  • Program components: events, screens, menus, and function modules
  • Objects that programs can share: database fields, field definitions, and program messages.

A package is a container for objects that logically belong together. For example, all objects in an application belong to a single package. A package is also a type of development object. An example of a package is General Ledger Accounting .

Note

When you create a new object or change an existing object, the system asks you to assign the object to a package.

Where and How to Store Development Objects?

The SAP system stores development objects in the Repository, which is a part of the database. When you complete your work on a development object, you generate a runtime version of the object. Together with the object, this runtime version is stored in the Repository. An application consists of several runtime objects that are processed by the work processes in the SAP system.

Why to Divide Development from Production?

In a standard SAP installation, development and live operation take place in separate systems. You create new applications in the development system and transport them to the production system. Daily work takes place in the production system, which uses runtime versions created in the development system.

The division between production and development systems is recommended because changes to an existing ABAP application take immediate effect. To prevent disturbances in the daily workflow of the production system, all developments are carried out in development systems.

Why to use the Transport Organizer?

You use the Transport Organizer to move applications from the development system to the production system. The Transport Organizer also provides version control and tracking. For more information, see Package Concept and Transport Organizer .

See also:

Learning More