Realtech Transports Guide August 22, 2014

Realtech Transports Guide

- ❖ Change Process Management(CPM)
❖ Transport Management(TM)

Table of Contents

Change Process Management(CPM) - Introduction ............................................................................................................ 2

Key CPM Workflow Activities for Change Requests containing Transports ..................................................................... 3
Allow SAP Transports (Automated) ................................................................................................................................. 3
Release SAP Change Request (CR Owner) ....................................................................................................................... 4
Approve for Transport to xTIER_xxx System (CR Owner or SE) .................................................................................... 5
Check Transports (CR Owner or Automated) .................................................................................................................. 5
Transport Check (Automated) .......................................................................................................................................... 5
Transport to xTIER_xxx System (CR Owner or SE) ......................................................................................................... 6
Request transport to xTIER_xxx (CR Owner or SE) ......................................................................................................... 6
Wait for Import Feedback (Automated)........................................................................................................................... 6
Confirm Import to xTIER_xxx (Automated) ..................................................................................................................... 7
Transport Information in CPM .............................................................................................................................................. 7
Transport Content and Status ........................................................................................................................................... 8
Transport Delivery ............................................................................................................................................................. 9
Transport Collisions ......................................................................................................................................................... 10
Transport Critical Objects ............................................................................................................................................... 12
Moving SAP Transports ....................................................................................................................................................... 13
Deleting/Removing Transports .......................................................................................................................................... 15
Transport Failures ............................................................................................................................................................... 17
Aborting CRs with Transports ............................................................................................................................................ 18
Transport Management(TM) .............................................................................................................................................. 19
Repeat Request Import Tool (RRI) ..................................................................................................................................... 28
System Refresh Cockpit(SRC) ............................................................................................................................................. 32
TM ICONS .............................................................................................................................................................................. 35
Realtech Transports Guide August 22, 2014

Change Process Management(CPM) - Introduction

Click on the link below to access the CPM Tool

[Link]

The CPM Tool will be utilized in place of existing processes/tools to run, manage, and track SAP change
processes from a single point of control.

CPM is a workflow based tool, therefore depending upon the workflow, which follows defined steps based
upon the Change Request Definitions (= templates) and the data populated in the Change Request.

The specific detail that is contained within the different pages of CPM are explained in detail later in this
document. The pages that are available to a user are based upon the activities that the user will be required to
perform and are established based upon the user’s security settings.

The officially supported browser for CPM is IE. Additionally only one session of CPM should be opened.

You must be on CORPNET to access this tool.

CPM Pages:

❖ Home
❖ Change Management
❖ Release Management
❖ Search
❖ My Profile
❖ Info
Realtech Transports Guide August 22, 2014

Key CPM Workflow Activities for Change Requests containing Transports

Below you will find activities that are a part of the Change Request process which are related to the processes
for transports. Above the activities you will see how the activity is processed. Some of the activities are
automated and others are performed by the CR Owner or SE Approver.

Allow SAP Transports (Automated)

Allow SAP Transports [New]
Description: Allow SAP Transport assignment

Upon Completion of this automated process the CR will be available in the selected SAP system for the
Configurator/Developer listed as a participant on the associated CR to attach the transports to.

➢ STEPS IN SAP FOR CREATING SAP TRANSPORT AND ASSIGNING CR

• CR must be Created, Activity Type “Transport”
• Activity – “Allow SAP Transports” must have completed successfully
• You must be listed in the associated CR as the Configurator/Developer Participant
o Logon to the designated SAP Development System
o Proceed to Create Transport
o Select the Change Request ID which corresponding to the change that is to be included in the
transport
o Complete the required fields
▪ The naming convention for transports has not changed. Please ensure to utilize the
proper naming convention when creating your transport.
Realtech Transports Guide August 22, 2014

If you are not assigned as a Configurator/Developer for any CRs, you will not be able to successfully create a transport.
You will receive the below message.

Release SAP Change Request (CR Owner)

Release SAP Change Request [New]
Description: Release Change Request in the development System. (Note: The SAP Task must first be released directly in SAP. The SAP
Change Request must be released from CPM.)

This step in the CPM Workflow releases the SAP Transport in the development system.

It will not complete successfully, unless all the assigned SAP tasks have been released in SAP:
Realtech Transports Guide August 22, 2014

Note: The Request Attribute ZRTC_TM_CHANGE_ID is the number of the CR that a transport is assigned to.

Approve for Transport to xTIER_xxx System (CR Owner or SE)

Approve for Transport to xTIER_xxx System [New]

This activity/step in the CPM Workflow is done prior to transporting to the next SAP System as indicated by the
template utilized. Before queuing the transport for import to the next system, there may be other required activities, such
as e.g. transport checks.

Note: Systems are marked as 2TIER in the Production System Landscape (Dev2 ➔ **U ➔ PROD) and 3TIER in the
Project System Landscape (Dev1 ➔ **G ➔ **T ➔ PROD).

Check Transports (CR Owner or Automated)

Check Transports [New]
Description: Check transports for critical objects

This step in the CPM Workflow will initiate built in checks for critical objects within the transports assigned to the
associated Change Request. The existing configuration checks for:
• Category 1: Index OR Number Range
• Category 2: House Bank
• Category 3: OBYC entries
• Category 4: LSMW
• Category 101: OSS note

If any of these objects are identified, the workflow will trigger the required approval process, and the CR will not be
available for import until all approvals have been granted.

Transport Check (Automated)

Transport Check [New]
Realtech Transports Guide August 22, 2014

Description: Checking for cat 4 - LSMW.

In addition to the “Check Transports” activity triggered before import to Test, the BreakFix template contains also
“Transport Check” for LSMW objects before import to Production. If LSMW objects are identified, the workflow will
trigger the required approval process, and the CR will not be available for import until all approvals have been granted.

Transport to xTIER_xxx System (CR Owner or SE)

Transport to xTIER_xxx System [New]
Description: Move CR to xTIER_xxx System in XXX landscape (*X).

This activity/step in the CPM Workflow will queue the transport to be included in the import batch job that will import
transports to the designated system in the landscape based upon the template that was utilized in creating the change
request.

Transports will be picked up by the automated job, which will be running every 15 minutes and will be imported to
the designated target system based upon the CR template and defined system.

Note: Systems are marked as 2TIER in the Production System Landscape (Dev2 ➔ **U ➔ PROD) and 3TIER in the
Project System Landscape (Dev1 ➔ **G ➔ **T ➔ PROD).

Request transport to xTIER_xxx (CR Owner or SE)

Request transport to xTIER_xxx [New]
Description: Email requesting transport to 3TIER_UAT system (*T) sent to SE.

This activity/step in the CPM Workflow will send an email to the SE Approver designated as a participant of the
associated Change Request.

Example Email:

Wait for Import Feedback (Automated)

Wait for Import Feedback [New]
Description: Wait for transport return code from xTIER_xxx system (*X).
Realtech Transports Guide August 22, 2014

This activity/step in the CPM Workflow update the CR to contain the details associated to the transport return
code. This will indicated whether or not the transport was successful, and will trigger email to the CR owner
(CR import successful OR Import errors).

Note: This activity may take up to 15 minutes, depending on the frequency of the scheduled transport jobs. If
needed, <Click> to refresh the screen to display the latest status.

Confirm Import to xTIER_xxx (Automated)

Confirm Import to 3TIER_UAT [New]
Description: Email confirmation of import to 3TIER_UAT

This activity/step in the CPM Workflow will send an email to the CR Owner to advise that the transport has
successfully imported.

Transport Information in CPM

Realtech Transports Guide August 22, 2014

In CPM, <Click> SAP Transport Management tab to view the details of the transports associated to the CR – each
detail area of this tab requires you to click on the specific area you would like to view.

Transport Content and Status

Contains the below details associated to the transports
• Transports that have been assigned to the CR
• Owner
• Source System
• Status
• TM Status
▪ Registered
▪ Removed
• TM Workflow details
• Objects in the Request
▪ Program ID
▪ Object ID
▪ Object Name
▪ Dev Package
▪ Application Component
▪ Application Description
▪ List of Transport Requests which contain the object
• Application Content of the Request
▪ Dev Package
▪ Application Component
▪ Application Description
Realtech Transports Guide August 22, 2014

<Click> to view Object for the transport request:

<Click> to view transport requests that contain the objects. (This list will be inclusive only of those that have been
transported via the Realtech Process.)

<Click> to view the application content associated with the transports:

Transport Delivery
Contains the below details associated to the transports
Realtech Transports Guide August 22, 2014

• Transport #
• Systems Transported To
• Import Date
• Import Time
• Status
o OK – Transport successfully imported
o Open – Transport not yet transported to system listed
o Error – Import was not successful

Transport Collisions
Collisions
• Contains the below details associated to the transports:

If there are potential collisions/dependencies identified, review the dependencies and mitigate any potential impact by
for example releasing and moving the dependent transports if needed. If ok, click on the “Ignore Collision” check box
and proceed with the transport to the test system.

***If you do not mitigate the issues and/or do not click on the “Ignore Collision” check box, you will not be able to
proceed with the import to the test system.
Realtech Transports Guide August 22, 2014
Realtech Transports Guide August 22, 2014

Transport Critical Objects

Critical Objects
• Contains the below details associated to the transports
o Lists Critical Objects that are located in a transport
o Additional approvals for Critical Objects are required and included as a part of the workflow
process.

Critical Check Approvers

▪ (Category 1) Index OR Number Range Basis
▪ (Category 2) House Bank FIMM
▪ (Category 3) OBYC Application Support Leads
▪ (Category 101) OSS Note Basis
▪ (Category 4) LSMW saplsmwapprovers

Critical Objects need to be reviewed by the CR Owner if found and the “checkbox” to acknowledge the critical objects
must be checked to avoid errors in moving the transport.

The CPM Workflow step “Check Transports” or “Transport check” will trigger a built in check for critical objects
within the transports assigned to the associated Change Request. If any of these objects are identified, the workflow will
trigger the required approval process, and the CR will not be available for import until all approvals have been granted
and the checkbox checked.

Verify and Fix Critical Object Errors: Check Ignore:

Realtech Transports Guide August 22, 2014

Moving SAP Transports

Transports will be picked up by the automated job, which will be running every 15 minutes, and will be
imported to the designated target system based upon the template and system utilized.

All transports that belong to a CR will be moved together to the target system, when the CR is moved for the
first time.

For subsequent moves (i.e. if the CR is sent back to development to add more TRs), when approved again for
the target system - the additional TRs will be moved together (in one queue, one transport buffer).

If there is a situation where “break point” is needed between TRs that belong to the same CR (for whatever
reason – manual activity in between, technical reason to import in different buffers, etc.), then it would be best
to assign the TRs to different CRs in advance so that the “break” can be controlled by the person approving the
CR for import to the system. If there is such requirement it should be documented in the CR (in the “Special
Instructions to CAB/BASIS” field), because it will be needed for building the production buffer and specifying
the break points. In addition, the release specific CR templates include a “Stop Point Transport” field. Enter
the break point transport in this field, in case the release to production must be split.
Realtech Transports Guide August 22, 2014

The process that needs to be followed when there are transport dependencies for transports contained in
multiple CRs is listed below:
• The CRs should be approved for transport in order of dependencies.
• The TRs for all CRs approved for a system will move together when the import job runs (in one
buffer, one queue).
• If a “break point” is needed between CRs – the person approving the CR for the target system
can control when the 1st CR after the break point can be approved (i.e. approve after the first
group has been imported and if there is manual activity the manual activity was performed).
• In addition, the release specific CR templates include a “Stop Point Transport” field. Enter the
break point transport in this field, in case the release to production must be split.
Realtech Transports Guide August 22, 2014

Deleting/Removing Transports
At time it may be necessary to remove a TR assigned to a Change Request. The process depends on various factors such
as the state of the CR and the associated transports. Here are some scenarios:

▪ The transport that I need to remove has not been released yet. ➔ In this scenario, you can reassign the TR to another
CR or delete the TR from the CR.
▪ On the “SAP Transport Management” tab, click on “Assignment”:

▪ Select the new CR from the dropdown and click “Reassign” or click on “Remove” to remove the TR completely.

Notes:
1) If you delete the TR, you will no longer be able to attach it to another CR in CPM, which means you will
no longer be able to use the TR to move your changes. Remember to back out any changes that will not
be rolled out from the development system.

2) If you reassign it, ensure that you are selecting a CR created with the correct template and corresponding
SAP system.

▪ The transport that I need to remove has already been released. It is the only TR associated with the CR or all the other
TRs associated with this CR must be canceled as well. ➔ In this scenario, authorized users (SE Level 3, Release
Management, Basis) can abort the CR by clicking on “Abort Change Request Workflow” icon. If you are not an
authorized user, please work with your L3 or the Release Management team to get a CR aborted.

Notes:
1) A TR reverting the initial changes may be required before the original CR is closed.
2) After aborting the CR, the TRs will be removed from the TM workflow and it will not be possible to reuse them
later to move the changes to any systems.

▪ The transport that I need to remove has already been released. Not all TRs associated with my CR need to be
canceled. ➔ In this scenario, it is currently not possible to delete the transport, but this option should be available
before the end of the pilot. In the meantime, you will need to create a new CR and attach new TRs for those changes
that you want to keep. The new CR will need to go through all the approvals and transports of a brand new CR again.
The original CR will then need to be aborted in the same way as described in the previous scenario.
Notes:
1) A TR reverting the initial changes may be required before the original CR is closed.
Realtech Transports Guide August 22, 2014

2) After aborting the CR, the TRs will be removed from the TM workflow and it will not be possible to reuse them
later to move the changes to any systems.

In case a TR must be pulled from going to Production on a short notice (e.g. due to problems with Dry Run), the TR may
be manually removed from the TM queue by Basis. This TR will no longer be available for future deployment, so if the
change is still desired, a new TR and a new CR will need to be created and go through all the approvals of a brand new
CR.
Realtech Transports Guide August 22, 2014

Transport Failures
Transport Error can occur for example in case of a dependent object moved without ensuing all dependent
objects in the same or preceding CR, or due to technical issues in the target system. Such errors can be
mitigated by re-importing the TR outside of the CPM workflow. Refer to the Repeat Request Import Tool (RRI)
section of this document for more details.

If the re-import does not resolve the issue, you may need to create a new transport to replace the original one.
In such case, select “Errors or Additional Changes Required” step in the Open Activities, so that you can go
back to the “Allow SAP Transports” stage and assign additional transport(s) in order to address the import
error.
Realtech Transports Guide August 22, 2014

Aborting CRs with Transports

When you abort a CR, all the assigned TRs get removed from Transport Management. There is no way to re-
process any CR after it was aborted.

Notes:
• A TR reverting the initial changes may be required before the original CR is closed.
• After aborting the CR, the TRs will be removed from the TM workflow and it will not be possible to
reuse them later to move the changes to any systems.
• Not all users will have authorization to abort CRs. You may need to work with an SE L3, Release
Manager or a Basis resource in order to abort a CR.
Realtech Transports Guide August 22, 2014

Transport Management(TM)
Tool enabling automation of the SAP transport process.

• The Transport Management(TM) tool in conjunction with the Change Process Management (CPM) tool
will replace the existing custom ZCCT for moving transports in the SAP Landscape.
• Transport Management is accessed from Solution Manager SMP system.
• Jobs will be scheduled every 15 minutes for transporting to **U, **G and **T SCM systems during the Pilot
Phase.

Note: The final job frequency for the global rollout is still TBD.

Transaction /n/RTC/TM to start Transport Management from SMP (Solution Manager Production)

• This displays the main window of Transport Management.

• Monitor
• History
Realtech Transports Guide August 22, 2014

Display System Queue

• Utilize Drop Down to Select System Queue

Transport finished successfully

Transport finished with Errors

Selection

• Provides the ability to search via filter critera

TM Attributes
Realtech Transports Guide August 22, 2014

• Shows Details of a transport

• Request / Package
• Short description
• Project
• Destination

Critical Objects

• Transport includes Critical Objects

• Details of Critical Objects can be seen in the details below

Tracking Information
Realtech Transports Guide August 22, 2014

Request Lifecycle

Import Protocol

Show Collision Objects

• Shows details with regards to any Collisions Found within a transport

Notes

Choose Layout

• Provides the ability to modify the layout of the displayed details

Realtech Transports Guide August 22, 2014

Scheduler

Provides the timing of the Batch Jobs that are processing the import of the transport(s)

Transport Details can be viewed by double clicking on a transport request

Request Header

• Transport Header Level Details

o Transport #
o Transport Name
o Reference Date/Time
o Change Date/Time
o Owner
o Source Client
o Transport Type
• Customizing Request
• Workbench Request
Realtech Transports Guide August 22, 2014

Approvals

• Transport Approval Details

o Transport Import Levels
o Transport Approver
Realtech Transports Guide August 22, 2014

Import Information

• Details regarding transport import levels, date and time

Critical Objects

• Details of Critical Objects located in a transport

Realtech Transports Guide August 22, 2014

Attributes

• Contains SAP and TM transport Attribute information

Return Code Forecast

• Transports can be scanned in order to locate additional information with regards to

errors/potential errors

Scan Transports

• Click Scan Transport to generate the Return Code Forecast Findings

• Details can be viewed by clicking on the individual line items

Explain Transports

❖ Will provide further details with regards to transport dependencies

• Click on to see details

Realtech Transports Guide August 22, 2014

Transport Details can also still be viewed in SAP Systems via SE01
Realtech Transports Guide August 22, 2014

Repeat Request Import Tool (RRI)

The purpose of the Repeat Request Import Tool (RRI) is to enable re-import of transport requests to a specified system
without Basis Team’s assistance. This may be required in case of an import error.

The tool only provides access to transport requests for the selected system which:

a) have been imported into that system at least one time before
b) are in the appropriate status (available for transport into the next transport level)

➢ The tool is started through transaction /N/RTC/TM_CU_MS_RRI in SMP:

• Enter your “Target System” and “Change Request ID” of CR with the transport(s), the “CPM Project”, or
transport(s) that you need to reimport and execute the report. Available CRs and transports will be
displayed together with collision and critical check information:

CR Area TR Area

Collisions Critical Object Check

• Double-click on the desired CR to show the TRs and transport details.

• Select the desired transport(s) that you want to import, and click on the Repeat Import icon to
reimport the transport(s) to the selected system. Confirm “Yes” to re-import the selected TRs.
Realtech Transports Guide August 22, 2014

Change Request Area

• TM Project: Assigned TM Project

• CPM Project: Assigned CPM Project
• Change ID: Change Request ID
• Short Text: Name of the Change Request
• Status: Status of the Change Request:
No import yet (should not appear, see condition a)

Highest return code of all transports of the change request

• Populates the other areas with the data belonging to the selected change request(s). To achieve
the same for a single change request, the user can optionally just double-click a record in the grid.
• Refresh Change Request Approval Grid
Realtech Transports Guide August 22, 2014

Transport Request Area

Transport Request: Transport Request Number

Stat: Status of the Transport Request:
Request is not subject of reapplication as it belongs to the checked
change request but the target system is not part of the request’s TM
destination
Request is already ready for import
Request is not in a proper TM workflow state

Return code of the last import

Request not imported since last system refresh

Short Text: Short Text of the Transport Request

Export Date: Export Date of the Transport Request
Export Time: Export Time of the Transport Request
Return Code: Return Code of the re-imported Transport Request
Import Date: Date of the last import
Import Time: Time of the last import
TM Project: Assigned TM Project
CPM Project: CPM Project of the corresponding Change Request
Change ID: Corresponding Change Request ID

This area displays the transport requests for the checked change requests in the change request approval area. By
double-clicking a transport request, the user is forwarded into its object list. By double-clicking into the ‘Return Code’
field, the user is forwarded to the import logs for that request:

Collision Check Area

TM Project: TM Project of the colliding Transport Request

CPM Project: CPM Project of the colliding Change Request
Change ID: Change Request ID of the colliding Transport Request
Transport Request: Colliding Transport Request Number
Transport Level: Current Transport Level of the colliding Transport Request
Status: Current Status of the colliding Transport Request

Note: The area only displays colliding requests, which would be overtaken if the checked change request will be re-
imported.
Realtech Transports Guide August 22, 2014

Critical Object Check Area

Transport Request: Transport Request Number of the critical finding

PgID: Program ID of the found critical object
Object: Object Type of the found critical object
Object Name: Object Name of the found critical object
Category: Category of the found critical object
TM Project: TM Project of the Transport Request
CPM Project: CPM Project of the corresponding Change Request
Change ID: Corresponding Change Request ID

Reimport Transports:

Select the desired transport(s) that you want to import, and click on the Repeat Import icon to reimport the
transport(s) to the selected system. Confirm “Yes” to re-import the selected TRs.
Realtech Transports Guide August 22, 2014

System Refresh Cockpit(SRC)

The purpose of the System Refresh Cockpit (SRC) is to enable re-import of transports requests to a specified system
without Basis Team’s assistance after system refreshes.

The tool is started through transaction /N/RTC/TM_CU_MS_SRC in SMP

• Enter your “Refreshed System” and the “Change Request ID” of CR with the transport(s) or the “CPM
Project”, or TM Project that you need to reimport and execute the report.
✓ Available CRs and transports will be displayed together with collision and critical check information:
Realtech Transports Guide August 22, 2014

• Double-click on the CR to show the TRs and transport details.

Select the Change Requests that need to be re-imported.

<Click> on

<Click> on
Realtech Transports Guide August 22, 2014

Columns:

TM Project: Assigned TM Project

CPM Project: Assigned CPM Project (Attribut ‘projectname’ in CPM)

Change ID: Change Request ID

Short Text: Name of the Change Request

Org. Approver: User, who has initially approved the change request in CPM

Status: Status of the Change Request:

Change Request not completely approved yet

Change Request completely approved

Change Request re-imported with RC=0, 4, >=8

CR Approver: User, who has approved for re-application

Date: Date of the CR Approval for re-application

Time: Time of the CR Approval for re-application

Tool specific Toolbar buttons:

Refresh Change Request Approval Grid

Populates the other areas with the data belonging to the selected change request(s). To achieve
the same for a single change request, the user can optionally just double-click a record in the
grid.

Approval button for the selected change request(s). The button is only displayed for users,
assigned to the defined role for CR Approvers in table /RTC/TM_CU_MS_AP.

Please note: An App Type approval can only be executed if the CR Approval has already been executed.
When a change request has been approved and further approvals are needed, due to critical
object findings, users, representing this additional approval types are notified via email.
Realtech Transports Guide August 22, 2014

TM ICONS
Full Screen On/Off
Package View
Selection
Display System Queue
TM Attributes
Export
Return Code Forecast
Tracking Information

Request Lifecycle
Import Protocol

Show Collision Objects

Notes
Choose Layout
Scheduler

Package Administration