Scribd
Upload
7 views3 pages

TMS 1

Transport management in SAP ABAP systems involves data movement strategies, change requests, and the use of the transport control program for exporting and importing data. It distinguishes between client-specific and cross-client data, with various types of requests and transport routes for managing changes across development, quality, and production systems. The repository serves as a central store for all ABAP objects, and specific transaction codes are used for managing transport requests and imports.

Uploaded by

Rajesh BS
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
7 views3 pages

TMS 1

Transport management in SAP ABAP systems involves data movement strategies, change requests, and the use of the transport control program for exporting and importing data. It distinguishes between client-specific and cross-client data, with various types of requests and transport routes for managing changes across development, quality, and production systems. The repository serves as a central store for all ABAP objects, and specific transaction codes are used for managing transport requests and imports.

Uploaded by

Rajesh BS
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Transport management in SAP ABAP systems includes concepts such as the data movement strategy

b/w the three system landscapes. Data packaging of ABAP source code changes and configuration
changes in the form of change requests or transport requests. Exporting and importing the transport
requests using the sap transport control program(tp).

During the installation of the SAP development system, a central transport directory referred to as
usr/sap/sid/trans is created.

The data can be exported and imported using this as a central data area at the file system.

The host is saptranshost.

The sap transport request is exported in development to quality system database using transport
program(tp).

All tasks should be released before releasing the change request. Releasing (exporting)the change
request will create a data file and control file at os level.

The name convention of transport request is <SID>k9 followed by 5 digit. Eg: DEVk900045.

Task should be released first and then the change request is released, after the status should be
changed modifiable to released.

All the data should be stored in common or central transport directory.

Transport program is a kernel executable, and it helps in coordinating all activities associated with
the export and import of transport requests.

Data file name is R900045.dev, It contains actual data

Cofile name is K900045.dev, It contains change request data

When the transport is released, the Tp executes an export command and writes a data file and a
cofile in the central transport directory at the os level.

When the transport control program(tp) starts the import, it calls the kernel executable R3trans,
connects to the DB, and performs the needed DB updates. It also starts an event triggered ABAP
program called RDDIMPDP at the SAP application level. And it starts some background jobs and
stored in TRBAT and TRJOB tables. RDD* jobs execute all the conversion and activation steps of the
ABAP program and tables in the repository. Scheduled (RDDNEWPP).

Client-specific data

It is data affecting only one client, such as user master and application data.

1.User master data – such as parameters, authorization, user groups,


2.Customizing data – such as organizational units, assignments, and document types
3. Application data – such as business transaction data, and material master data

Cross-client data
It is data affecting the whole system environment, such as cross-client Customizing data and all
Repository objects.
Smart forms, all dictionary objects data and repository objects data like programs, functions
modules, tables etc.

Repository
The repository is where objects are accessed using the ABAP Workbench. The repository is a
cross-client store containing all dictionary objects (tables, data elements, and domains) and
all ABAP programs, menus, and screens. If we develop or change any repository object in one
client, an SAP system uses the same form of the object in every other client.

TYPES OF REQUESTS
⚫ Workbench Request: Workbench requests are cross-client. It essentially means that the
changes done in one client are automatically reflected in all other clients.
Eg: repository objects (tcode, table, transections, report, etc)

⚫ Customizing Request: Customizing requests are client specific. The changes will not be
reflected in other clients.

⚫ Transport of Copies: Transport of copies allows you to transport objects to any specified SAP
System. It allows you to move the original location of objects to a target system.

TYPES OF TRANSPORT ROUTES


Consolidate Route--- Connection b/w Development and Quality System

Delivery Route--- Connection b/w Quality and Production system.

TYPES OF TRANSPORT LAYER


SAP Layer
Z<sid> Layer

All Workbench requests can be displayed, changed, released using transaction code SE09
Customizing Request display SE10
the transport administrator starts imports by using transaction code STMS.
------------------------------------------------------------------------------------------------------------

● Client-specific data = client dependent = customizing request = Z<SID>Layer(100)


● Cross-client Customizing data = client independent = workbench = SAP Layer(000,100,200)

You might also like