Transport Management System
Dr. Thomas Brodkorb Dr. Hans-Jrgen Hennrich
SAP AG
SAP AG 1998
N8 SAPTechEd 98, Karlsruhe (Brodkorb, Hennrich) / 1
Contents
z Introduction to TMS z Demonstration of TMS Release 4.5 z New Features in TMS Release 4.6 z Future Developments
SAP AG 1998
N8 SAPTechEd 98, Karlsruhe (Brodkorb, Hennrich) / 2
Introduction to TMS
SAP AG 1998
N8 SAPTechEd 98, Karlsruhe (Brodkorb, Hennrich) / 3
Transport Management System
A reminder of the purpose of the Change and Transport System:
T To control all changes
to Workbench objects and Customizing
T To transport all changed objects
from the development system to the production system(s)
As of Release 4.0, the Transport Management System supports the administrator in all transport tasks
SAP AG 1998
N8 SAPTechEd 98, Karlsruhe (Brodkorb, Hennrich) / 4
Architecture and Terms
Change and Transport System (CTS)
Change and Transport Organizer (CTO)
Workbench Organizer (SE09) Customizing Organizer (SE10) Transport Organizer (SE01)
Transport Management System (TMS)
Transport Tools (low level programs: tp, R3trans)
SAP AG 1998
N8 SAPTechEd 98, Karlsruhe (Brodkorb, Hennrich) / 5
TMS Functions
R/3 user interface for all administrative tasks concerning CTS
T T T T
Transport Management System
Global maintenance of transport configuration Perform imports (hiding tp and R3trans) Monitor import queues (buffers) Transports in distributed R/3 system landscapes (multiple transport directories)
Monitoring tools
T Investigate problems in the Change and Transport System
SAP AG 1998
N8 SAPTechEd 98, Karlsruhe (Brodkorb, Hennrich) / 6
TMS Terms
transport domain A transport domain B
transport group 3 transport group 1
transport group 2
transport domain controller
SAP AG 1998
N8 SAPTechEd 98, Karlsruhe (Brodkorb, Hennrich) / 7
Demonstration of TMS Release 4.5
SAP AG 1998
N8 SAPTechEd 98, Karlsruhe (Brodkorb, Hennrich) / 8
Demonstration of TMS Release 4.5
z z z z
Transport domain setup Maintaining the transport profile Organizing the system landscape Working with import queues
SAP AG 1998
N8 SAPTechEd 98, Karlsruhe (Brodkorb, Hennrich) / 9
Transport Domain Setup
z z z
By starting TMS for the first time:
T The first system is declared as domain controller T Further systems request participation in the domain
(by sending their address data)
On the controller, the administrator accepts these systems (by sending the configuration data of all other systems) Consequences:
T User TMSADM is generated in each system T RFC destinations are generated for connections between every
pair of systems
T Transport profile(s) are generated in each transport group
SAP AG 1998
N8 SAPTechEd 98, Karlsruhe (Brodkorb, Hennrich) / 10
Maintaining the Transport Profile
z z z z z
As of Release 4.5, the transport tool configuration is generated during the domain setup Parameters necessary for establishing the database connection are taken from the R/3 profile Settings from TPPARAM may be copied into the new transport tool configuration Further maintenance of the transport tool configuration is done on the domain controller Transport profiles TP_<domain>.PFL are generated in each transport group
SAP AG 1998
N8 SAPTechEd 98, Karlsruhe (Brodkorb, Hennrich) / 11
Organizing the System Landscape
z z
New optional features as of Release 4.5 Client-specific transport routes
T Client-specific default transport
layer
User Hennrich? Import to client 015 and 020 User Brodkorb? Import to client 010 All imports to client 020 must be delivered to client 025
T Client-specific consolidation
routes
... ...
z z
T Client-specific delivery routes
Target groups Improved import control
SAP AG 1998
N8 SAPTechEd 98, Karlsruhe (Brodkorb, Hennrich) / 12
Extended Transport Route Configuration
Client-specific consolidation routes
ZDV1 GR_QA
Client-specific delivery routes QAS
010 015 020
DEV
ZDV1 020: ZDV2
PRD
015 017 025
ZDV2
Client-specific default layer
Target group
User Hennrich? Import to client 015 and 020 User Brodkorb? Import to client 010 All imports to client 020 should be delivered to client 025
... ...
SAP AG 1998
N8 SAPTechEd 98, Karlsruhe (Brodkorb, Hennrich) / 13
Working with Import Queues
z z z z
Choose a subset of all pending requests on a per client basis Choose a subset of all pending requests by manual selection Use this subset to
T Import requests T Forward requests to another system or client T ...
Scanner for critical objects
T Critical objects can be defined for each system T Import queues can be scanned for these objects
SAP AG 1998
N8 SAPTechEd 98, Karlsruhe (Brodkorb, Hennrich) / 14
New Features in TMS Release 4.6
SAP AG 1998
N8 SAPTechEd 98, Karlsruhe (Brodkorb, Hennrich) / 15
New Features in TMS Release 4.6
z z z z z
Managing transports in projects Advanced quality assurance Import scheduler Import tracking CTO - TMS workflow
SAP AG 1998
N8 SAPTechEd 98, Karlsruhe (Brodkorb, Hennrich) / 16
Managing Requests in a Project
z z
Transport requests will be assigned to a project
T Customizing requests are assigned to IMG projects
automatically
All selections within CTS can be made by projects
T T T T
Searching for transport requests Displaying import queues Importing transport requests ...
SAP AG 1998
N8 SAPTechEd 98, Karlsruhe (Brodkorb, Hennrich) / 17
Advanced Quality Assurance
z z z
You can assign a system as a QA system Forwarding into the production system is done inactively All requests have to be approved in the QA system
DE VK904711 D E V K 9 04 7 12 DE VK904713
PR1 PR2
P R1 D E V K 9 0 4 71 1 D E V K 9 0 4 71 2 D E V K 9 0 4 71 3 P R2 D E V K 904711 D E V K 904712 D E V K 904713
DEV
QAS
Q AS D E V K 904711 D E V K 904712 D E V K 904713
SAP AG 1998
N8 SAPTechEd 98, Karlsruhe (Brodkorb, Hennrich) / 18
Import Scheduler
You can schedule the import of transport requests
T Imports may be started at a given time or after an event T Imports are performed using R/3 background processing T Imports of all pending requests in a system may be scheduled
periodically
Global maintenance and monitoring
T Imports may be scheduled from any system in the transport
domain
T Batch queues of all systems in a transport domain may be
monitored from any system in the domain
SAP AG 1998
N8 SAPTechEd 98, Karlsruhe (Brodkorb, Hennrich) / 19
Import Tracking
z z z
Complete history of exports and imports
T Performed on a per client basis T Performed on any time period T Performed on user or project basis
Troubleshooting in the event of inconsistencies
T Check correct import sequence T Check completeness of transports T Compare transport history between systems/clients
Interface to tracking database available
SAP AG 1998
N8 SAPTechEd 98, Karlsruhe (Brodkorb, Hennrich) / 20
CTO - TMS Workflow
z z z z
Workflow between developer and administrator for
T transports into systems outside the predefined transport routes T transports outside the regular transport schedule
Several transport requests may be imported into several target systems using one transport proposal TMS workflow inbox is accessible from any system within the domain Automatic logging of transport proposal history
SAP AG 1998
N8 SAPTechEd 98, Karlsruhe (Brodkorb, Hennrich) / 21
Future Development
SAP AG 1998
N8 SAPTechEd 98, Karlsruhe (Brodkorb, Hennrich) / 22
Integration of Transport Tasks
z z
Integration of all transport tasks using R/3 workflow A particular aspect of this integration is that responsibilities and tasks will become project-specific
Our vision is that every transport administrator and/or quality manager will find his every day work in the integrated TMS workflow inbox.
SAP AG 1998
N8 SAPTechEd 98, Karlsruhe (Brodkorb, Hennrich) / 23
Summary
SAP AG 1998
N8 SAPTechEd 98, Karlsruhe (Brodkorb, Hennrich) / 24
Summary
With the new features in TMS you can
T T T T T T T
Manage transport profiles Extend transport control on clients Organize transports with project systems Integrate quality assurance processes Schedule transport jobs Track down imports Apply workflow to manage transports
SAP AG 1998
N8 SAPTechEd 98, Karlsruhe (Brodkorb, Hennrich) / 25
