Overviewing Customization and Workbench Development Overview

Chapter 62: Overviewing Customization and Workbench Development

Contents
Overview ................................................................................................................................................................................621 ................................................................................................................................................................................621 Authorizations for Change Management ...................................................................................................................................621 ...................................................................................................................................621 The Customizing Organizer......................................................................................................................................................622 Organizer......................................................................................................................................................622 What is Customizing?........................................................................................................................................................................ 623 Workbench Organizer..............................................................................................................................................................623 Organizer ..............................................................................................................................................................623 Introduction to Workbench Tools ....................................................................................................................................................... 623 The Major Workbench Tools.............................................................................................................................................................. 624 Managing Clients ....................................................................................................................................................................624 ....................................................................................................................................................................624 Transporting (TP) ....................................................................................................................................................................626 ....................................................................................................................................................................626

Overview
The Implementation Guide (IMG) provides links to all customizing activities and all customizing activities must be performed directly from within in the IMG. Customizing objects are maintained using IMG customizing transactions. When a client is configured to automatically record changes, system settings are automatically saved to change requests. These change requests are managed by the Customizing Organizer. This topic provides background information on organizing and performing Customizing activities during the R/3 implementation process. Because of the integrated nature of SAP, customizing must be a managed process. SAP supports such project management by providing needed tools and authorizations. The ABAP/4 Development Workbench is SAP's graphical programming environment. The Workbench environment supports the creation of new ABAP/4 client/server applications by a development team. You can also use the Workbench to change existing SAP applications.

Authorizations for Change Management

Using authorizations, you can control whether a user can create, modify, or release change requests. Authorizations also exist for developers who need to change tasks.

1996 SAP Technology, Inc.

621

Overviewing Customization and Workbench Development The Customizing Organizer

SAP delivers sample profiles which contain authorizations for development and customizing users with different areas of responsibility: PROFILE S_A.SYSTEM S_A.CUSTOMIZ AUTHORIZATION ROLE (CR = Change Request, CTS = Correction & Transport System) S_CTS_ALL S_CTS_PROJEC SUPERUSER: System Administrator View Task & CR, Manage Tasks, Manage CR, initialize CTS PROJECT LEADER: Customizing (for all system setting activities) S_A.DEVELOP S_A.USER S_CTS_DEVELO S_CTS_APPLIC View Task & CR, Manage Tasks, Manage CR View Task & CR, Manage Tasks View Task & CR DEVELOPER END USER

The Customizing Organizer

The management of Customizing changes to an R/3 System is just as important as the changes themselves. SAP provides the needed tools for structured, project-based Customizing. This section explains how to use these tools to setup project teams for the purpose of recording, documenting, and distributing Customizing efforts. The Customizing Organizer and the Transport System are designed to work together. During normal customizing work: the project leader first defines a change request and tasks for all users involved. customizers can then create and modify objects, and these activities will be registered in the change request. after work has been completed, users must release their tasks. the change request can then be released from the source system for export. the transport to the target system takes place at the operating system level.

In general, customized table entries are automatically recorded by the Customizing Organizer. You can also use the Transport System to copy table entries to a request manually from one system to another. Customizing is the standard procedure used to adapt the functionality of the delivered SAP components to the requirements of your company. Customizing is required for all implementations of SAP R/3, used when enhancing an R/3 system, and used when undertaking a release upgrade. Customizing provides: the R/3 Procedure Model , the work breakdown structure for implementation and enhancement of the R/3 System the Implementation Guide (IMG), links to all customizing activities as well as project management, evaluation and documentation tools project management capabilities using change request management

622

1996 SAP Technology, Inc.

Overviewing Customization and Workbench Development Workbench Organizer

a link to the transport tool, enabling the transfer of changes from the development environment to a production environment system and release upgrades tasks

What is Customizing?
Customizing is a method which helps you in the following situations: when implementing the R/3 System when enhancing the R/3 System when undertaking a Release Upgrade and System Upgrade provides you with the R/3 Procedure Model, the work breakdown structure for implementation, and enhancement of the R/3 System provides you with tools for System configuration and the necessary documentation provides the Customizing Project which gives you Tools for management, processing and evaluation of your implementation or enhancement projects gives you configuration recommendations and tools to enable this helps you transfer the System configuration from the development environment into the Production environment gives you a set of tools for System Upgrades and Release Upgrades customizing does not help you to modify the standard SAP functions

Customizing also:

Workbench Organizer
Using the ABAP/4 Development Workbench, you are able to provide additional functionality to an R/3 System. This requires that all objects to be developed are managed, changes recorded, versions maintained, and objects transported to other systems within the system landscape. SAP provides both the tools and methodologies to support such development and they are explained in this section.

Introduction to Workbench Tools

Programmers can use the Workbench to: write ABAP/4 code design dialogs with a graphical editor create menus with a menu editor debug an application test an application for efficiency use pre-defined functions control access to objects under development create new or access pre-defined database information

1996 SAP Technology, Inc.

623

Overviewing Customization and Workbench Development Managing Clients

Because the Workbench is a graphical programming environment, you access the Workbench tools using pull-down menus, a toolbar, and your mouse.

The Major Workbench Tools

If you have not already done so, log on to the R/3 system. Then, choose Tools ABAP/4 Workbenchfrom the menu bar. The system displays the ABAP/4 Development Workbench screen. The Workbench tools you will work with most often appear in the toolbar: Tool: Object Browser ABAP/4 Dictionary Function: Traverse and edit hierarchical lists of development objects. Define and store data definitions. You can also store documentation, help information, data relationships, and other information. You use the Dictionary to generate database objects like tables and indices. The Dictionary is a central storage area for system-wide data definitions. Because definitions are centrally stored, they are available for use anywhere in any program throughout the system. Create new program code or edit existing code. Define and store library routines called function modules. The Function Library stores these modules centrally. You can use the library to write new modules and look up information on existing modules. Design the screens in an application's graphical user interface. Design the menus that appear in your interface

ABAP/4 Editor Function Library

Screen Painter Menu Painter

Managing Clients
Customizing maintenance has been linked to the Workbench Organizerand transport system with the Customizing Organizer As a result, all changes to customizing settings can be recorded in change requests. . The numerous changes made to parameters during a customizing project no longer need to be remembered and subsequently assigned to transport. The system records the work carried out by a person or team and registers it for transport. The transport of customizing settings to another system is prepared and you only need to release the transport. The same applies when you transfer a client to another client in the same system. The system also assists you with a tool for Copying clients. However, it is not always desirable to record every single change made to the system. That is why many systems have a test, training, or demo client in addition to the production client. In extreme cases, this could even result in unintentional transport that could destroy the target client. Role of the client: indicates whether the client is a production, test, training, demo or customizing client. Extent of record-keeping: Record-keeping can be set for each client individually. As in the system change option of the Workbench Organizer, all changes can also be forbidden here.

When you link a selected client to the transport system, this only affects changes to client-dependent customizing settings and not client-independent settings. A record is always kept of client-independent changes and modifications of Repository objects (programs, screens, and so forth).

624

1996 SAP Technology, Inc.

Overviewing Customization and Workbench Development Managing Clients

Customizing requests (request category CUST) may only include client-specific objects, whereas system requests (category SYST) may contain any objects. If you set your client to record transports, mainly customizing requests are generated. This ensures that the results of a customizing project can be transported to the target client of another system without affecting other clients there. Once in production, the customer's system landscape is in a state of maintenance. All changes to either customizing or repository objects should be distributed using change requests and the Transport System. The client copy and client transport tools should no longer be used. Once in maintenance, all development should still take place in the development client using the Workbench Organizer and the Customizing Organizer to record all changes. All objects are collected either in customizing requests (client-dependent data) or in transportable change requests (client-dependent and client-independent data). These changes are distributed using a client copy according to the change request to clients within the same R/3 System. To transport customizing settings and repository objects, the Transport System provides the following functions: Client copy change request The log of client-dependent customizing settings can be saved to a customizing change request. A client copy copies only the settings defined in the change request to another client within the same R/3 System. Customizing change request The log of client-dependent customizing settings can be saved to a customizing change request. This change request can be transported (exported and then imported) into one or more clients in another R/3 System. Transportable change request Client-independent customizing settings and repository objects are collected in transportable change requests. The list of table entries and repository objects can then be transported (exported and then imported) into another R/3 System. Once in production, the customer's system landscape is in a state of maintenance. All changes to either customizing or repository objects should be distributed using change requests and the Transport System. The client copy and client transport tools should no longer be used. Once in maintenance, all development should still take place in the development client using the Workbench Organizer and the Customizing Organizer to record all changes. All objects are collected either in customizing requests (client-dependent data) or in transportable change requests (clientdependent and client-independent data). These changes are distributed using a client copy according to the change request to clients within the same R/3 System. Downstream systems receive these change requests from the Transport System.

1996 SAP Technology, Inc.

625

Overviewing Customization and Workbench Development Transporting (TP)

Transporting (TP)
System Landscape Transport Path (logical)
Integration Consolidation Delivery

Development

Quality Assurance

Production

To facilitate the synchronization of multiple R/3 Systems, SAP provides transport capabilities. Transporting is simply the movement of changes that originate in the development environment to downstream systems. In addition to the common system names, SAP has provided more technical transporting terms for a standard system landscape. Development takes place in the integration system. The integration system is used to integrate additional functionality into the SAP standard software and adapt the existing functionality to your specific requirements through customizing. Therefore, the integration system assumes the role of development. Once the developments are stable, they are transported from the integration system into the consolidation system. Here, extensive and final testing occurs. The changed objects are tested and verified in the consolidation system. This system is commonly known as the quality assurance system. After testing, all development and customizing transports that enter the consolidation system are also transported to one or more delivery systems. The production system is a delivery system.

System Landscape Transport Path (physical)

Integration Consolidation Delivery

Development
Export

Quality Assurance
Import

Production
Import

Common Transport Directory

Physically, changed objects in a three-system landscape are transported in three steps:

626

1996 SAP Technology, Inc.

Overviewing Customization and Workbench Development Transporting (TP)

First, all the objects for a change request to be released are exported from the source systems database to a file in the common transport directory. Second, the objects are imported into the target system's database. Third, once testing and verification take place, the objects may then be imported into any defined delivery systems.

In order to take advantage of all transport capabilities, all systems within the system landscape must share a common transport directory. This directory contains all released changed request and exported data as well as log files that indicate the success of every export and import. For further details refer to R/3 System Administration Made Easy Overviewing R/3 System and Roles (Ch. 15) Introducing R/3 System Architecture (Ch. 1) Transporting SAP Objects at the OS Level (Ch. 66) R/3 Basis Knowledge Products Software Logistics CD Reference Implementation Customizing Reference Implementation Workbench Development Technical Implementation Implementation Coordinate Customizing Technical Implementation Implementation Coordinate Development R/3 System Online Help Implementation Tools Implementation Guide Basis Components ABAP/4 Development Workbench Workbench Organizer Basis Courses Workbench Organizer, Transport System & Upgrade (BC325)

1996 SAP Technology, Inc.

627