Workbench Organizer & Transport System SAP recommends three types of systems for implementation purpose Development System

m Test System Production System Though number of systems used by an organization depends upon many factors such as size of implementation, budget etc. However even in the smallest installation, a second system is a must. Development system Development system is the system where the actual development takes place. Normally the development is carried out for objects and these objects are original for these systems. Test system Also known as quality assurance system and are used to test the objects. You can test objects on development system also, but on Test System the object is tested against real data. When the tests are validated the development objects are transported to the production system. Production System The production system is where the end user enters real business data and where the actual business runs. No development takes place in this system. You need to transfer the object from test system to production system. The overall flow of objects can be understood in the following diagram:

DEVELOPMEN SYSTEM

TEST SYSTEM

PRODUCTION SYSTEM

Developer creates the objects in the development system, these objects are transported to the Test system to test them against the real data and when validated, these objects are transported to the Production System. To transport these objects from one system to another, ABAP/4 development work bench provides the tool called Work bench organizer which is also used to manage activities that are important in the overall development environment. Example, for these activities are.

 The management and control of new development requests. Modification of objects Version management In a distributed environment, workbench Organizer transports the development object between different SAP systems. In the following example, the objects are transported from the development system to production system. E.g., between development and Production System

Type Users: Developers, Consultant

Production System End Users

Develop System: New Development

No development hhhjhjh

Workbench Organizer
The most puzzling topic of R3 system is intended to help functions for system development.

Concepts of workbench
Development objects: Workbench records and controls change to existing development objects as well as new objects. A development object is an object created in R/3 system. (Program, Screens, Function modules.) Dictionary objects: Tables, Domains, Match code objects, Data Elements.

The workbench is fully integrated into the ABAP/4 development workbench. Development Classes: A Development class classifies the objects belonging to the same development project. When a user creates a object in R/3 system, the object needs to be stored in a particular development class. The development class are objects themselves. In R/3 system you can store objects. In local object i.e. object is stored in $tmp class and cannot be transported from one system to another. User can assign his own development class and can be transported. Transport System

Developers are in charge of creating or correcting data objects and will create change request, which can be for individual object or common request for a project. When the change request is released the system performs transport R/3 administrator is the person who sets up the transport system. This group works both at the R/3 application level and at the operating system level, using transport control (tp) program.

Change Request A Change request is a list in the system, which mainly contains the object to be transported. It also contains the transport type, the request category and the target system. When the change request is created either manually or automatically, the system assigns a number to it automatically. This number is known as change request number. The format of this number is normally <SID>K<Number> E.g., DD1K<900002> Where DD1 is System Identification Number (SID) K is keyword The number is automatically generated by system and starts with 900001. The change request records all modifications made to development object. When the changes are made and the change task (will be discussed) has been released, the change request can be released. SEO9 transaction Or Tools -> ABAP/4 W.B -> overview -> W.B. organizer Will display and check all the change requests.

Tasks
A task in the workbench organizer is an activity in which user either creates an object or modifies the same. In workbench organizer, task can be either development or repair task. A task is related to single user while change request contains tasks belonging to different users. You cannot transport task as such, but as a part of request. Each task is associated with task number, which is similar to change request number. Usually, when a development work starts, a system administrator or project manager creates a change request to define tasks for all users involved in the project. Later, user starts modifying objects or create new object. Once user finishes his task, they must release them. A change

request can be released for transporting, only when all tasks under the same change request are released. Objects included in task become locked against other development work on the same object. Version Management ABAP/4 workbench and the organizer provide a version management for all the objects in the system. With version management user can compare current version object and object with the previous version. To display the version for a object, Locate your object through the change request number of workbench organizer. Click on the object and from menu. Or Utilities display version. It displays what has been modified and who did it. Version management is important for developers also as it allows user to compare previous programs with the current one.

Transport
A transport means the process of moving something from one place to another. In R/3 system this something means change request. To transport the objects you need to create the change request. It can be done with the help of workbench organizer. Transport System and workbench organizer are closely linked to each other. An object original is a development object that has been created in the system in which you are working. DD1 PP1 Zsus001 (Development System) Zsus001 (Production System)

Suppose you transport object Zsus001 to another system, Zsus001 is object original for system DD1. If anyone tries to modify the program, he will be making repair to it, provided he has access key for the same. R/3 system offers this security measure to ensure that development object remain consistent for all system, thus preventing parallel work on the same objects. Correction of objects and development of objects can be only in original system. The difference between Repair and Correction is as follows:

If you modify an object in a system in which it is created, you are making Correction to it. If you modify an object in a system in which it was not created, then you are making Repair task.

Releasing Tasks and Request When new development or correction is complete, developer must release their task and request. To release a task: Find a task from the Workbench initial screen. Position the cursor over the task. Click on the release button A request is released by either system Administrator or Project Managers, once all the tasks are released