Development Class & Transport Request: Kaavian Systems 14-Sep-09

You might also like

Download as ppt, pdf, or txt
Download as ppt, pdf, or txt
You are on page 1of 13

DEVELOPMENT CLASS

&
TRANSPORT REQUEST

14-Sep-09

Kaavian Systems

Transport Request
A transport, copies objects from a source
system (Development System) to a target
system (Production System).
The objects are transported in two steps:
- 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

14-Sep-09

Kaavian Systems

Transport

14-Sep-09

Kaavian Systems

Transport

Development takes place in the Integration


System.
The changed objects are tested and verified
in the Consolidation System.
14-Sep-09

Kaavian Systems

Client Change Option

14-Sep-09

Kaavian Systems

There are five types of R/3 System changes


Customizing
Customer developments:
Enhancements
Modification
Advanced correction
14-Sep-09

Kaavian Systems

Releasing customizing change


requests

14-Sep-09

Kaavian Systems

Difference between WBO and CO

14-Sep-09

Kaavian Systems

Development Process

Development classes provide a logical separation of


repository objects
After you assign a development class to an object,
assign the object to a change request.
A task collects all the repository objects maintained
by a developer during a project.
14-Sep-09

Kaavian Systems

Development Classes
Development classes are used to collect
ABAP/4 Development Workbench objects
of the same type .
A transport layer is assigned when a
development class is created.
All development classes are defined in table
TDEVC.

14-Sep-09

Kaavian Systems

10

Completing a Development
Project

14-Sep-09

Kaavian Systems

11

Classifying Change Request and


Task

14-Sep-09

Kaavian Systems

12

THANK YOU

02-Sep-09

Kaavian Systems

You might also like