Change Management

SAP Data

• A client has its own set of user master data,

application data, and customizing data
• Customizing adapts the SAP software to meet a
company’s individual business requirements by
setting up the business transactions the company
requires in the system
• The Repository consists of all system development
objects – programs, function modules, definition of
database tables, and so on.
• There are objects delivered by SAP as well as
developed by the customer in the Repository.
• The repository is in the database and independent of
the client
• All changes of customizing and developments are
recorded to transport to the next system

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 2

Change execution

Request for Change Change Execution

Requester Change Approver Change
Developer & IT Staff Tester Requester
Manager Manager

Create
Create Approve / Change
Process Handover Execute & document Test Confirm
Request for Reject Trans-
Request to Execution action Change Change Change
Change Request

Change Request
Notification Management supports
via all types of changes
Workflow
SAP and non-SAP Technical & non Technical
Changes Changes

System
IT Assets Admin Tasks
Landscapes

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 3

Dependency Check

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 4

Risk

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 5

Risk

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 6

Risk

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 7

Risk

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 8

Transport Object

You can use this request type to set up your own object lists and save them under a name of your choice.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 9

System Landscape

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 10

Extended Phased Transport Landscape

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 11

Summarization

• Too often, the measure of SAP Basis administration is simply how fast necessary changes can be imported into a company's production
systems. This may make sense from a business perspective, but who deals with the consequences that may arise from the poor quality of the
SAP change management process?
• SAP systems handle mission-critical and accounting-related business processes. Changes to SAP systems and SAP applications involve risks
that can bring a business to a halt. The processes of the SAP transport system are the key to governing the import of these changes into the
production systems.

• How to optimize the quality of SAP change management by way of well-defined workflows, processes, and automated checks and shows how
modern change management can effectively minimize the risk of system failures.
Optimize your SAP change & transport management processes,
Reduce the risk of system failures,
Maintain complete audit trails of all change activities.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 12

Change Management
Transport Overview and Import Method
 Agenda
Transport Strategy

1.Transport Overview
2.Import Method

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 14

SAP Standard System Landscape

Customers must customize R/3

to meet the needs of their
business flow AND may require
additional functionality created
with the ABAP Workbench

DEV QAS PRD

Quality
Development Assurance Production
System System Systems

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 15

Requirements of a System Landscape

Change Management
Define system roles within the system landscape
Define client roles for all clients within the system landscape
Record Customizing and development changes for distribution in the system landscape

Transport Management
Transport units of work ready for quality assurance testing (project management)
Schedule transports and establish a transport process for the timely delivery of changes
Ensure validation and sign-off of changes prior to import into a production system
Support non-standard changes such as emergency fixes and changes to the SAP-standard by
applying Support Packages

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 16

Transport Management Architecture

Change and Transport System (CTS)

Change and Transport Organizers
(CTO)
Transport
Workbench Customizing Transport Management
Organizer Organizer Organizer System (TMS)
SE09 SE10 SE01 STMS

Transport Tools
tp and R3trans

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 17

Centralized Transport Management

Concepts behind the TMS:

 Centralized configuration of Change and Transport System
(CTS) for all R/3 Systems Transport Domain
Established RFC communication links Domain Controller

 Centralized management of change requests and the import

process
View import queues and initiate imports from any R/3 System

 Transport strategy based on predefined transport routes

Transport routes
– Consolidation route
– Delivery route
Extended transport control

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 18

Structure of the Transport Management System

Transport Domain

Transport domain controller

transport directory

Backup transport domain

Transport Group controller

transport directory

Transport Group

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 19

Define Transport Process using TMS

• Consolidation route adds change requests to an

SAP import queue at the time of release
• Delivery route adds change requests to an import
Integration Consolidation Delivery
queue at the time of successful import
DEV QAS PRD • Standard transport layer required for
ZDEV ZDEV Customizing change requests
• Transport layers (like SAP and ZDEV) used by
development class for Repository objects

Delivery routes

Consolidation
routes

Standard transport layer

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 20

Transport Organizer & Transport Requests

SE80/SE37…. SE09

ABAP-Objects Task Transport Request

Automatic

Change
Recording
Reports,
Function Modules,
Dictionary Objects,
….

All workbench tools are tightly integrated with the SE09 functions.
All changes are automatically recorded within tasks.
A transport request is the container for transporting.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 21

Steps in Transport Process

Transport Domain
Transport Group

Development Quality Productio

Assurance n
Change Request

Task

2. Import
1. Release 3. Import
and export

Transport directory

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 22

Releae and Export

Import Queue
Transport
Task
Request
Release Release
EPDK9000H
DEV

Export
Pointer
Transport Directory

R3trans
data file

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 23

Performing Transports

After you release a change request using the Transport Organizer, the objects in the request are exported from the database and
stored in the transport directory. At the same time, the change request is marked for import into the target system by being
placed in the import queue of the target system. After the export log has been checked, the developer's or project manager's
work is initially finished.

The subsequent import into the target system is generally performed by the transport administrator. The import overview (STMS 
Overview  Imports) provides you with the following information on all SAP Systems in the transport domain:
 Number of requests ready for import
 Status of the import queue

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 24

Import Queues

The most important tools used to perform imports using TMS are the import queues that reflect the system-specific
import buffers at the operation system level.
The import queues display the requests that are to be imported, in the order of their release.

Import Queue
EPDK9000H

TP Target
System A
Import

Transport Directory

R3trans
data file

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 25

Transport Strategy

The Change and Transport System provides a range of functions that help you to choose a transport
strategy optimally suited to your requirements. There are three different transport strategies available:
 Queue-controlled mass transports
 Single transports
 Workflow-controlled transports
Transport Strategy is implemented by adjusting attributes of transport route.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 26

Transport Strategy in Details

Transports with Import Queues

Import queues can be used as a transition between development and administration. All changes released by developers can be seen immediately
by the administrator in the queues. Import queues are a particularly good way of automating transports in your system landscape. They can
significantly reduce the amount of work for system administrators responsible for a large number or transports; automation reduces the
administrator tasks mainly to monitoring and troubleshooting. You can choose between two procedures when you use import queues to perform
imports:
 You can import mass transport into your systems. This procedure imports all requests waiting for import in the queue. All requests are
imported into the target systems in the order they were exported. This minimizes the risk of errors in the target systems caused by requests
being imported in the wrong order, and the risk of objects being missing in the target system.

 You can import single transports into your systems. This procedure makes a selection of requests from the import queue and imports them
into the target system. The other requests remain in the import queue, where you can choose to import them later, or not at all. Single imports
are the most flexible method, however, they demand more administration.

Transport Workflow
The transport workflow provides a framework for transporting enhancements or new developments of existing business functions in a system
landscape. It provides a direct connection between development and transport administration. The transport workflow manages the transport
process, determines the user for each individual step automatically, and then displays an interface which they can use to perform the task directly.
It is an efficient method of transporting a selected number of requests into a group of transport targets, and uses clearly defined approval steps to
ensure the quality of your target systems.
However, the transport workflow can involve some risks, caused by the dependencies between transport requests:
 Import sequence
 Incompleteness

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 27

 Agenda
Transport Strategy

1.Transport Overview
2.Import Method

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 28

Fundamental Transport Principle

In a mechanism like that if you import the transport requests in the export order then the target system has to be
exactly the same as the source system.
 DB exports are only done at export time
 At change recording time only piece lists with the changed objects are written

At change recording
time only piece list
with the changed
objects are written
DE QAS
ChangeV
Request Piece List
A
B
Task C
D

A
B
Export Import A
B
C C
A
D R3 Trans D
B
C
DEV DB D Data File QAS DB
Transport Directory
DB exports are only
done at export time
© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 29
Import Queues

Import Queue: System QAS X Import Options

Individual requests ~ preliminary
Request for QAS: 6 / 12 import
one request
Number Request Owner Short text selected requests (Release 4.5)
Start import ~ import all
1 DEVK900032 KESTER condition table entire queue
filter on a client (Release 4.5)
2 DEVK900143 HAMM reports for FI filter on a project (Release 4.6)
3 DEVK900002 ROEHR IMG notes

4 DEVK900014 MCF sales org.

5 DEVK900085 MCF sales org.

6 DEVK900033 JAKOBI matchcodes

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 30

Import Requests

You can use three different methods in the TMS import queue to import requests into the target
system. The best method for you depends on your system landscape and your transport strategy.
In practice, you will find that a combination of these methods is the most effective way of working
with the TMS.
Before you import the requests from an import queue into an SAP System, ensure that no users
are working in this SAP System. Therefore, inform your users about the import times early on, for
example by creating a system message.To prevent change requests from still being placed in the
import queue shortly before the mass import, and perhaps being imported unintentionally, we
recommend closing the import queue before the import.
Import method
Import All
Single Import (Preliminary Import)
Import Subset
Import Project

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 31

Import All

Import of All Requests in an Import Queue (Mass Transport Strategy)

When you import all the requests from an import queue, they are imported in the order in which they are placed in the
queue. Each import step is performed for all requests. First, all the Dictionary objects in the requests are imported, then
all the Dictionary objects are activated, and then the main import is performed for all requests.
If you use this method to export all your requests from your development system into your quality assurance and
production systems, then you are assured of keeping the Customizing and Workbench objects in your systems
synchronized. However, this method is less suitable if you develop in different projects at the same time, test them in
the QA system, and then import the projects into your production system at different times. This applies especially to
the production system.
Problem with Import All
Nobody can do a proper assessment of a complete queue and a complete import all. It is danger to perform Import all in
reality. Never endanger the productive system!

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 32

Single Import (Preliminary Import)

Single Import for Individual Requests (Single Transport Strategy)

TMS also allows you to import individual selected requests from the import queue. The requests you choose are
imported in the order in which they are placed in the import queue. Import steps are done for each request separately
Importing single requests can either be
 an exception, if you usually use mass transports
 or the rule if you usually use single transports.
Problem with Single Import
Import steps are done for each request separately which caused generation problem (object dependence) and
performance problems. For this reason, this method is obsolete.
To minimize the risks associated with single import, the request remains in the import queue after the import and is re-
imported the next time the entire import queue is imported. This guarantees that export and import sequence are
always the same. This is defined by the option Leave Transport request in queue for later import, which is initially
marked.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 33

Import Subset

Single Import for Subset (Single Transport Strategy)

Similar to Single Import, transport requests to be imported are defined manually from the import queue; but import is
technically done in import all style (each import step for all requests). The order of the import steps corresponds to an
import of all requests. The requests you choose are imported in the order in which they are placed in the import queue.

Problem with Import Subset

Technically Import Subset is fine, but if there are dependencies between different changes distributed by different
import subsets then the customer is running into problems.

Dependent change B
DE QAS is not synchronously
imported
Change AV
Import Subset (Change A)
Change A

Change B

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 34

Import Project

Project (CTS Project) Controlled Transports

If you are working on several different development projects at the same time, you cannot always
estimate which of the projects will go live at which time. If your development projects do not overlap,
or only overlap a little, you can use projects to control transports, and then use different transport
schedules for different projects.
Project are bundling single transport requests and/or changes with respect with their business
context.

Changes within same

DEV QAS business context are
transported synchronously
Project A Import Project (A) Project A
Change A Change A

Change B Change B

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 35

Import Options
Import Option Depends on Import Method Chosen

Select All Requests for Later Import

The requests remain in the import queue after the import and can be imported, for example, into another client. This is only useful if you have
not switched on extended transport control, but you want to provide several clients with requests.
Leave Transport Request in Queue for Later Import
This causes these requests to be imported again in the correct order with the next import of all the requests. This option is useful if you have
to make preliminary imports for individual requests. This prevents older objects from being imported at the next regular import of all the requests
(over shooter problem). However, if you provide a system only with individual transports (e.g. ChaRM variant SAP1), this option is not useful
since the requests remain in the queue after the import and have to be manually deleted from the import queue.
Import Transport Request Again
The transport control program also imports the transport request if it already has been completely imported.
Overwrite Originals
The transport control program also imports objects if the objects are the originals in the target system. The object directory entry determines
the SAP System where the original version of an object is located.
Overwrite Objects in Unconfirmed Repairs
The transport control program also imports objects if they were repaired in the target system and the repair is not yet confirmed.
Ignore Non-Permitted Transport Type
The transport control program imports the transport request if this transport type was excluded by particular settings in the transport profile.
 Ignore Non-Permitted Table Class
The transport control program imports data records of a table even
if the delivery class of the table does not permit the data records to be
imported.
 Ignore Predecessor Relationships
You can choose this option if you want to import all the requests for
one or several projects, but additional requests from other projects
exist for which there are dependencies. This option is switched off by
default, which means the predecessor's relationships are checked
before the import. The import only occurs if the predecessor's
relationships will not be damaged.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 36

 Appendix

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 37

More Information in IMG about
TMS in Change Management

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 38

Transport Methodology and CTS Configuration
for Change Management

TMS Setup
Import Single
CTC=1
Client Transport Routes
Inter domain link between SAP Solution Manger and Managed Systems

CTS Setup
Project assignment mandatory
CTS Status Switches used for locking TMS and WBO functionality

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 39

Import Subset vs. Import Project

 Urgent Corrections are transported individually and thus no dependency to other corrections.
 They are imported by the transport method import subset and stay in the transport buffer after
import.
 Urgent Corrections are propagated into other systems at the end of phases in the Maintenance
Cycle together with the Normal Corrections by the transport method import project.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 40

References

 Transport Management System (BC-CTS-TMS)

 Managing SAP System Landscapes with Transport Management System.ppt

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 41

RCA Survival Kit
Import Processes

RCA Project 2008

Steps During Import all ABAP Dictionary data is imported inactively
Log file: <SourceSID>H<number>.<targetSID>
transport tool: R3trans
Runtime descriptions (nametabs) are written inactively
1 ABAP Dictionary Import Log file: <SourceSID>A<number>.<targetSID>
transport tool: RDDMASGL
After activation and running logical checks for the new dictionary structures, the distribution program
2 ABAP Dictionary Activation decides what actions are required to bring the new objects into the running system.
Log file: DS<date>.<targetSID>
transport tool: RDDGENBB
3 Distribution If necessary, changes are made to table structures
Log file: N<date>.<targetSID>
transport tool: RDDGENBB
4 Structure Conversion The new ABAP runtime objects are put into the active runtime environment, database structures are
adjusted if necessary.
Log file: P<date>.<targetSID>
5 Move Nametabs transport tool: pgmvntab
All data is imported.
Log file: <SourceSID>I<number>.<targetSID>
6 Main Import transport tool: R3trans
Enqueue objects such as search helps that were not previously activated are activated in this separate
step after the main import. They are used immediately in the running system.
7 Activ &Conv of Enqueue Obj. Logfile: <SourceSID>M<number>.<targetSID>
transport tool: RDDGENBB
Import of application-defined objects (ADOs): These objects include forms, styles, and printer definitions.
8 Import of ADOs Log file: <SourceSID>D<number>.<targetSID>
transport tool: RDDIC1L
Versions of repository objects are only created if transport parameter vers_at_import is active. However, the
9 Versioning import process does modify the object's version counter, which is incremented for all repository objects during
import.
Log file: <SourceSID>V<number>.<targetSID>
10 Execute User defined (XPRAs)
transport tool: RDDVERSL
XPRAs are objects that can be used to start reports in the target system. The XPRA object has the same
name as the report.
11 Generate reports and screens
Log file: <SourceSID>R<number>.<targetSID>
transport tool: RDDEXECL
During this step, you can resume normal business activities in the system.
Log file: <SourceSID>G<number>.<targetSID>
transport tool: RDDIC03L
© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 43
TP Processing Sequence

 tp collectively processes each import step for all requests before proceeding with
the next import step
 tp does NOT process all import steps for only a single request before proceeding to
the the next request

1st 2nd 3rd

TASK DDIC | ACTIV | MAIN I | | | | VERS F | XPRA | GENERA | UMODE

------------------------------------------------------------------------------------------------------------------------------------------------------------
DEVK900048 1 | | 1 | | | | 13 | | |
DEVK900057 | | 23 | | | | 23 | | 23 |
DEVK900053 | | 1 | | | | 5 | | |
DEVK900069 1 | 1 | 1 | | | | 1 | | 1 |
DEVK900078 | | 1 | | | | 197 | | |
DEVK900083 | | 1 | | | | 25 | | 23 |
DEVK900087 | | 1 | | | | 5 | | |
DEVK900092 1 | 1 | 1 | | | | 1 | | 1 |

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 44

Import Process: tp and the import buffer

The first step of an import process is the tp call, triggered

by starting an import through TMS or by a ‘tp import’
command at operating system level.

R3trans tp Buffer file Log files

OS
tp reads the buffer file that includes all the necessary
steps for the specific request.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 45

Import Process: Tp and the import buffer

 The first step of an import process is the tp call, triggered by starting an import through TMS or
by a ‘tp import’ command at operating system level.
 To ensure that all transport requests stored in the buffer begin the import process automatically,
each time a ‘tp import’ call is made, a ‘tp setstopmark’ is executed.
 After the steps of the import process are completed, the command ‘tp delstopmark’ is performed
automatically, and a ‘tp cleanbuffer’ deletes the transport requests from the import buffer.
 After all involved tools have finished their work, tp exits to the operating system level and writes
a return code to the appropriate log file for the activity. For example, ‘tp import’ and ‘tp
setstopmark’ commands are recorded in the ULOG file.
 Note: The command 'tp import' is reentrant. If an error occurs during import, after you eliminate
the error condition and restart tp, tp finds the correct point to restart.
 By default, tp aborts if one import phase receives a return code larger than 8. The TPPARAM
parameter stoponerror defines what return code value should cause tp to abort.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 46

Import Process: r3trans

1 Step1: Dictionary Import

3 Step3: Main Import

TRBAT TRJOB

DB

DB
1 3

R3trans tp Buffer file Log files

For each import step, tp passes information

OS from the buffer file to R3trans.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 47

Import Process: R3trans

 During the import process, tp reads the command file that includes all the necessary steps for
the specific request and calls R3trans at the operating system level through a forc() for Unix
systems, a CreateProcess() for Windows NT, or a spawn() for AS/400 environments.
 For each import step, tp passes a control file to the transport subdirectory tmp for use by
R3trans. R3trans reads the corresponding data files in the transport subdirectory data and
connects directly to the database to perform inserts or updates to the included objects.
AfterR3trans finishes performing inserts or updates, it passes an exit code to tp.
 For each transport action, R3trans writes a log file in transport subdirectory tmp. After R3trans
completes its work, tp moves this log file to the transport subdirectory log.
 During the import process, R3trans is called by the import steps ABAP dictionary import (for the
import of ABAP dictionary definitions), and main import (for the import of table contents).

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 48

Import Process: tp/ABAP communication I
other import steps

RDDIMPDP

SAP system

TRBAT TRJOB
trigger

DB
insert

R3trans tp Buffer file Log files

read

OS
© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 49
Import Process: tp/ABAP communication I

 For every transport request, tp writes an entry in table TRBAT. The import function currently being
performed for the request is represented by a character. For a list of TRBAT function codes, see
the Appendix.
 In the example below, there are 3 change requests waiting for DDIC activation in the table TRBAT.
tp inserts a header entry to tell RDDIMPDP to start processing. Some activities that are
independent of transport requests, such as distribution and structure conversion, only have a
header entry in TRBAT. Return code 9999 indicates that the step is waiting to be performed. For
the header entry, tp inserts a B (for "begin") as return code.
 To trigger the transport daemon RDDIMPDP in R/3, tp uses the operating system level tool sapevt.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 50

Import Process: tp/ABAP communication II

Other import steps

Start RDD* jobs

RDDIMPDP DDIC
Conversion Generation …
Activation
SAP system

Insert job nr.

write status

Checks & TRBAT TRJOB

write tables
DB

R3trans tp Buffer file Log files

OS
© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 51
Import Process: tp/ABAP communication II

 When RDDIMPDP is started, it checks the table TRBAT to find out if there is an action
to be performed such as mass activation, distribution, or table conversion. It sets the
header entry to R (for "run"), and starts the appropriate RDD* program as a
background task, reschedules itself, and exits. The activated program (in this
example, the mass activator) sets the status of the first entry in TRBAT to active
(return code 8888):
 Each of the required background tasks receives a job number generated by R/3
background processing. This job number and the step ID are inserted into table
TRJOB by the RDD* jobs.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 52

Import Process: tp/ABAP communication III

Other import steps

Start RDD* jobs

RDDIMPDP DDIC
Conversion Generation …
Activation
SAP system
Checks tables Delete entries
write status
TRBAT TRJOB

restart
DB
Delete entries Write logs
monitor

R3trans tp Buffer file Log files

OS

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Restart failed Internal 53
Import Process: tp/ABAP communication III

 The background tasks write their return codes in TRBAT and delete the corresponding entry in TRJOB.
Return codes of 12 or less indicate that the step is finished. In TRBAT, the column TIMESTMP contains
the finishing time. When all the necessary actions are performed for all transport requests, the header
entry is set to F (for "finished") by the RDD* jobs.
 All the background jobs log the steps they perform either in the database or in transport subdirectory
TMP.
 tp monitors the entries in TRBAT and TRJOB. When the header entry in TRBAT is set to F and TRJOB is
empty, tp copies the logs of the completed steps from directory tmp to log and deletes the corresponding
TRBAT entries.
 If problems are detected by tp when monitoring TRBAT and TRJOB, tp re-triggers RDDIMPDP through
sapevt. RDDIMPDP automatically recognizes if a previous step is still active or was aborted by checking
TRJOB and TRBAT. If a step was aborted, RDDIMPDP restarts this step. Two background work processes
must be available.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 54

Appendix: TRBAT Function Codes

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Internal 55