RT - Full User Guide PDF

Rev-Trac Guide
1. Rev-Trac logo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Documentation inclusion library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1 Sample panel and sample table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2 Request details fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3 In-flight parallel check report screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.4 Rev-Trac enforcement popup - Refresh lock check button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.5 How to save searches for reuse later . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.6 How to retrieve saved searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3. Safety User Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.1 Rev-Trac enforcement popup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.1.1 Rev-Trac enforcement if locking of SAP configuration is enforced at table name level . . . . . . . . . . . . . . . . 16
3.1.2 Rev-Trac enforcement if locking of SAP configuration is enforced at table key level . . . . . . . . . . . . . . . . . . 17
3.1.3 Rev-Trac enforcement if Rev-Trac locking system is in advice-only mode . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.1.4 Rev-Trac enforcement if cross project locking is configured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.2 Parallel development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.2.1 How to allow parallel development when locking of SAP configuration is enforced at table name level . . . 24
3.2.2 How to allow parallel development when locking of SAP configuration is enforced at table key level . . . . . 26
3.2.3 How to disallow parallel development that has been approved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.2.4 How to display approved and disallowed parallel development requests . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.2.5 How to notify relevant parties when parallel development requests are submitted . . . . . . . . . . . . . . . . . . . 29
3.2.6 Parallel Development Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.2.7 How to approve and reject parallel development requests via the workbench . . . . . . . . . . . . . . . . . . . . . . . 31
3.2.8 How to redirect parallel development requests via the workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.2.9 How to view requests to which selected object is currently locked via the workbench . . . . . . . . . . . . . . . . . 35
3.2.10 How to display approved parallel development requests via the workbench . . . . . . . . . . . . . . . . . . . . . . . 37
3.2.11 In-flight parallel check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.2.12 How to perform in-flight parallel checks via Parallel Development Workbench . . . . . . . . . . . . . . . . . . . . . 41
3.2.13 How to perform an in-flight parallel check on a request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.2.14 How to view the in-flight parallel check report in Rev-Trac Web GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.3 Transport dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3.3.1 How to view and manage transport dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
3.3.2 How to view and define request dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
3.3.3 How to display transport dependencies reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3.4 Overtake and Overwrite Protection System (OOPS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
3.4.1 OOPS Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
3.4.2 How to respond when potential OOPS conflicts are found in the OOPS report . . . . . . . . . . . . . . . . . . . . . . 63
3.4.3 How to notify request owners regarding OOPS conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
3.4.4 How to perform OOPS check on a Rev-Trac request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
3.4.5 How to perform OOPS check on transports in the Rev-Trac Migration Workbench . . . . . . . . . . . . . . . . . . . 67
3.4.6 How to perform OOPS check on transports in the Rev-Trac migration queue . . . . . . . . . . . . . . . . . . . . . . . 68
3.4.7 How to perform OOPS check on multiple Rev-Trac requests in background mode . . . . . . . . . . . . . . . . . . . 69
3.4.8 How to display historical OOPS report in Web GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
3.4.9 How to display historical OOPS reports and responses to OOPS alerts in SAP GUI . . . . . . . . . . . . . . . . . 72
3.5 Peripheral Object Dependency System (PODS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
3.5.1 How to perform PODS check in Web GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
3.6 Change Impact Scoring System (CISS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
3.6.1 How to perform CISS check in Web GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
4. Basic User Guide for Web GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
4.1 How to log into Rev-Trac Web GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
4.2 Web GUI dashboards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4.2.1 How to create a dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
4.2.2 How to edit a dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.3 How to create new requests (Web GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
4.4 How to search requests (Web GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
4.5 How to display requests (Web GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
4.6 How to change request details fields including protected fields (Web GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
4.7 How to display change history log of a request (Web GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
4.8 Mobile approval (Web GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
4.9 How to sign a request (Web GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
4.10 How to display the approvals history of a request (Web GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
4.11 How to add, change and remove references (Web GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
4.12 How to add, change and remove attachments (Web GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
4.13 How to add comments (Web GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
4.14 How to display migration and deployment queues (Web GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
4.15 How to display xReports (Web GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
4.16 How to delete a request (Web GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
5. Basic User Guide for SAP GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
5.1 How to access Rev-Trac from your SAP systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
5.2 How to create new requests (SAP GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
5.3 How to search and display requests (SAP GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
5.4 How to change request details fields including status and protected fields (SAP GUI) . . . . . . . . . . . . . . . . . . . . . 127
5.5 How to display change history log of a request (SAP GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
5.6 How to sign a request (SAP GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
5.7 How to display approvals history of a request (SAP GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
5.8 How to add special approvers (SAP GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
5.9 How to pre-select approvers (SAP GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
5.10 How to add, change, remove and launch references (SAP GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
5.11 How to add, change, remove and display attachments (SAP GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
5.12 How to add a note to a request’s history log (SAP GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
5.13 How to delete a Rev-Trac request (SAP GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Rev-Trac Guide
Rev-Trac logo
4
Rev-Trac Guide
Documentation inclusion library

This library contains screenshots that are used in the documentations. Use the screenshots provided here in your documentations.
Replace old screenshots and insert new ones here to help to keep screenshots up-to-date in all documentations.
5
Rev-Trac Guide
Sample panel and sample table

Type title here
Use this panel colour scheme for all documentations
Fields Description
Field 1 test test test test test test test test test test
Field 2
6
Rev-Trac Guide
Request details fields
Field Description
Title Type the title of the request.

(Mandatory) This title will appear on many Rev-Trac screens and reports, and by default will be included in the texts of transports
created under Rev-Trac control and associated with this request.
Project Type or select from the pull-down list the Rev-Trac project within which request will be managed.
(Mandatory) The project you choose may help determine this request's approval process and migration path.
Note: There is no connection between a Rev-Trac project and a project defined in the SAP Project System (PS)
module.
Request Type or select from the pull-down list a Rev-Trac request type. This field is mandatory.
type The request type you choose may also help determine this request's approval process and migration path.
(Mandatory)
Team Type or select from the pull-down list a Rev-Trac team that is commissioning the work.
Position holders within this team may be responsible for approving certain stages of the work.
Module Type or select from the pull-down list the main SAP module to be affected by the work.
The field is only used for reporting purposes only.
Project Type or select from the pull-down list the release within the Rev-Trac Project.
release Rev-Trac project release relates to SAP changes released in subprojects or clusters, which may be known as phases,
rollouts or waves.
Owner Type or select from the pull-down list the SAP ID of the person responsible for overseeing the work.
The request owner may be responsible for giving some approvals and deleting the request. The requests belonging to
the owner will appear in the Owner tab on the Rev-Trac Console.
Programmer Type or select from the pull-down list the SAP ID of the person responsible for doing programming work for the change.
The programmer may be responsible for giving some approvals. The requests belonging to the programmer will appear
in the Programmer tab on the Rev-Trac Console.
Customizer Type or select from the pull-down list the SAP ID of the person responsible for doing customizing work for the change.
The customizer may be responsible for giving some approvals.
Note: The Customizer field is only available in a specific version of request details screen. If you require this field,
please consult your Rev-Trac administrator.
Actor Type or select from the pull-down list the SAP ID of the person who is responsible to act on the request.
The Actor will receive a workflow message whenever this request is saved, and has to act on the request. The requests
belonging to the actor will appear in the Actor tab on the Rev-Trac Console.
User status This is a supplementary status flag not updated by Rev-Trac and does not affect any Rev-Trac behavior.
Type or select from the pull-down list a user status defined by your organisation.
Class The request class determines whether fewer or more approvals (or different approvals) are required for this request
than otherwise would be.
Type or select from the pull-down list a Rev-Trac request class.
Priority Type a priority defined by your organisation.

For example, you may use the decimal point system to prioritise one request from another i.e. a request with Priority of
3.2 is seen as less important than a request with Priority of 3.1.1.
Test date Type the date when changes associated with a Rev-Trac request are expected to be in the Test (or QA) system.
7
Rev-Trac Guide
Production Type the date when changes associated with a Rev-Trac request are expected to be in the Production system.
date
Estimated Type an estimate of the total number of days required to perform all the work associated with the request.
Taken Type the number of days so far taken to perform the work.
Remaining Type an estimate of the number of days currently required to complete outstanding aspects of the work.
Keywords Type a search term to be used to search for this request via Rev-Trac Workbench selection screen in SAP GUI.
SAP Type the release of SAP that work will be done in.
Release It may be relevant to alter the default if, for example, you are planning a system upgrade in the near future.
8
Rev-Trac Guide
In-flight parallel check report screen
New feature in Rev-Trac 8.1.0

Two new columns; Release request flag and Clone request flag have been added to the In-flight parallel check report.
In the illustration below, 3279 is marked as the release request and 3409 is marked as the clone request.
9
Rev-Trac Guide
Rev-Trac enforcement popup - Refresh lock check button
In Rev-Trac 7.3.0 (SPS03), a new button called Refresh lock check is added to the Rev-Trac enforcement popup.
When you try to save a change to a request that is different from the locked request, click the Refresh lock check button to update the
lock check result with the request you attempt to save to. You can select Continue to save the change to the request if the lock check
result displays locking mode is in advice-only or there is no locked object (means locking is turned off).
10
Rev-Trac Guide
How to save searches for reuse later

At the search selection screen, click on
and select Save this search.
To create a new saved search
1. Select Save as.

2. The Save new search window is displayed. See illustration below.
3. Give the search a name.

4. Select Public or Private sharing mode and click the Save button.
5. The name of the search is displayed at the top of the screen.
To change the current saved search
1. Make sure the Saved search : <current saved search> window is displayed. See illustration below.
2.
11
Rev-Trac Guide
2. To replace the saved search with the new search criteria you have chosen:
a. Click the Save button. The new search criteria is saved under the same saved search name.
3. To rename or change the access level of the saved search:
a. Make the necessary changes and click the Save button.
b. The new name of the search is displayed at the top of the screen.
12
Rev-Trac Guide
How to retrieve saved searches

1. At the search selection screen, click on
. A list of options and recently used saved searches are displayed (see illustration below).
2. Select a recently used saved search, if suitable, otherwise, select View saved searches. The Saved searches dialog is
displayed with Name as the default search term and contains as the default operator.
3. Leave the input field blank to retrieve a list of all saved searches or type a search value.
4. Alternatively, select a more suitable search term and operator from the dropdown lists. To further narrow your search, click the Ad
d group button and use the All or Any boolean operator.
5. Click the Search button. A list of saved searches is displayed.
6. Select a suitable saved search and click the OK button.
7. Click the Search button again. A search result is displayed.
13
Rev-Trac Guide
Safety User Guide
Introduction
Use this guide to help you prevent transport-related accidents by utilising the following functionalities:
Rev-Trac locking system

Parallel development
Transport dependencies
Overtake and Overwrite Protection System (OOPS)
Change Impact Scoring System (CISS)
Peripheral Object Dependency System (PODS)
Before you proceed, ensure you have been set up as a Rev-Trac user and have suitable SAP user profile.
14
Rev-Trac Guide
Rev-Trac enforcement popup

If Rev-Trac enforcement is enabled, the Rev-Trac enforcement popup is displayed whenever a developer tries to save a change to an
object or table data that is already locked to a Rev-Trac request.
Messages and buttons that appear on the Rev-Trac enforcement popup depend on whether locking of SAP configuration is enforced at
table name or table key level.
There are four scenarios in which different enforcement screen will appear:
Rev-Trac enforcement if locking of SAP configuration is enforced at table name level

Rev-Trac enforcement if locking of SAP configuration is enforced at table key level
Rev-Trac enforcement if Rev-Trac locking system is in advice-only mode
Rev-Trac enforcement if cross project locking is configured
15
Rev-Trac Guide
Rev-Trac enforcement if locking of SAP configuration is enforced at table name level
If an item is already locked to one or more Rev-Trac requests, the enforcement popup will display the name of the item and the Rev-Trac
requests to which the item is locked.
In the example below, the enforcement popup window shows LIMU REPS Z_TC_1415_2 was locked to Rev-Trac request 2652.
The developer should ensure that the Generate the transport from Rev-Trac request number radio button is selected and select Conti
nue to save the change to request number 2652.
Otherwise, a parallel development has to be requested and allowed.
16
Rev-Trac Guide
Rev-Trac enforcement if locking of SAP configuration is enforced at table key level
If locking is enforced at table key level, the Locked Request(s) button is displayed in the enforcement popup (see illustration below).
To identify what items are locked, and to which Rev-Trac requests, click the Locked Request(s) button and the RSC - Locked object
details screen displays what items are locked and to which requests. In the example below, the LIMU REPS Z_TC_1415_2 object is
locked to Rev-Trac request 2652 and carried in transport DEVK907484.
To save the change, the developer selects the line on the report that lists request 2652 (highlighted in green), and then clicks the Select
Rev-Trac request button from the toolbar. The field in the enforcement popup will be filled with 2652. The developer should ensure that
the Generate the transport from Rev-Trac request number radio button is selected and then select the Continue button to save the
change to request 2652.
17
Rev-Trac Guide
Otherwise, a parallel development has to be requested and allowed.
18
Rev-Trac Guide
Rev-Trac enforcement if Rev-Trac locking system is in advice-only mode
When the Rev-Trac locking system is in advice-only mode, you will see ADVICE ONLY texts in the Rev-Trac enforcement pop-up window
(see illustration below), RSC - Locked object details screen or Lock advice screen.
The developer is free to save the change on any Rev-Trac request: the locking message, in effect, merely serves to show which other
Rev-Trac requests touch the same object or SAP configuration, and are currently in progress.
19
Rev-Trac Guide
Rev-Trac enforcement if cross project locking is configured
As of Rev-Trac 7.3.0 (SPS03), a new feature called cross project locking is introduced. If cross project locking is configured, the Cross
Project Lock button will appear on the Rev-Trac enforcement screen (see the illustrations below). You have the option to save your
change to a request other than the identified locked request.
Cross project locking is configured and locking of SAP configuration is at table key level
Cross project locking is configured and locking of SAP configuration is at table name level
Click the Cross Project Lock button to display the projects from where you can select an appropriate request to save your changes to
(see illustration below).
20
Rev-Trac Guide
The cross project lock report lists projects that are configured in cross project locking
21
Rev-Trac Guide
Parallel development
Overview
While Rev-Trac locking system is enforced, changes made to a locked ABAP Workbench object or SAP configuration, must be assigned
to the same Rev-Trac request that holds the lock. If this is not feasible, the developer can submit a request for parallel development of the
object or table data in another Rev-Trac request.
It is best practice to seek the agreement of all interested parties of the locked item before allowing parallel development for it. Only when
the request for parallel development is approved, the developer is able to save the change to another Rev-Trac request.
For example, the 'RSC – Locked object details' screen below shows that table data /RSC/C_DEMO_CUST that is locked to Rev-Trac
request 500460019, is now allowed parallel development on request 5004600265.
To save changes to request 5004600265, the developer selects request 5004600265, and then clicks the Select Rev-Trac request butto
n from the toolbar.
Parallel Development Workbench
The Parallel Development Workbench (SAP GUI) was introduced in Rev-Trac 7.2 to facilitate better parallel development control and
visibility.
Later, the workbench was also launched in Web GUI v8.0.0.
22
Rev-Trac Guide
The workbench provides the following functions:
Active parallel development report lists requests that have been approved for parallel development.
Parallel development request queue allows authorised managers to approve, reject or redirect Rev-Trac requests that
developers have submitted for parallel development.
In-flight parallel changes (check) report lists Rev-Trac requests and transports to which ABAP Workbench objects are locked.
Ability to configure cross project locking. For configuration details, please refer to OOPS, Locking system, sensitive objects
and whitelists from Documentation > Administrator Guides via Rev-Trac support portal.
Note: From Rev-Trac 8 SPS00 onwards, accessing the workbench will require authorisation value PD_001 to be assigned to authorisation
object Y/RSC/CE04 (Tools / Utilities).
23
Rev-Trac Guide
How to allow parallel development when locking of SAP configuration is enforced at table name level
Prerequisite
Before allowing parallel development for a locked item in an additional Rev-Trac request, the additional request must already exist.
Steps
Perform one of the methods below.
METHOD 1: IF THE 'LOCKED TO THESE REQUESTS <REV-TRAC REQUEST N> <REV-TRAC REQUEST N+1>' MESSAGE WAS DISPLAYED DURING REV-TRAC
ENFORCEMENT.
1. From Rev-Trac Console, go to menu path Administration > System log. The 'RSC - Display Rev-Trac system log' screen is
displayed.
2. Tick the Show parallel devel. Messages? checkbox.
3. To view the locking message Rev-Trac has previously displayed for locked item(s), type 34 in the Message number field.
Complete other selection fields as needed.
4. Select Execute from the toolbar. A list of locking messages is displayed.
5. Select one or more log entries that refer to the locked item(s) for which you want to allow parallel development.
6. Select Allow parallel dev. from the toolbar. An information dialog is displayed with the 'Please select the execute button on
the following screen' message.
7. Select Continue. The 'RSC - Parallel development' screen is displayed. Check that:
The Allow parallel development radio button is selected.
The Lock keys area displays details of the item(s) for which you may now allow parallel development in an additional
request.
8. In the Rev-Trac Request field, type or select the number of the Rev-Trac request where you intend to allow parallel development
(see example below). Note: Make sure it is not the Rev-Trac request to which the item(s) is currently locked.
9. Click the Execute button from the toolbar. A list of object(s) or table data for which parallel development has been allowed in the
selected Rev-Trac request, is displayed.
METHOD 2: IF NO 'LOCKED' MESSAGE WAS DISPLAYED DURING REV-TRAC ENFORCEMENT
1. From Rev-Trac Console, go to menu path Request Management > Tools > Develop in parallel. The 'RSC - Parallel development'
screen is displayed.
2. Select the Allow parallel development radio button.
3. In the Rev-Trac Request field, type or select the number of the Rev-Trac request where you intend to allow parallel development.
4.
24
Rev-Trac Guide
4. In the Lock keys area, create one or more entries by completing the following fields to identify the object(s) or table data for which
you want to allow parallel development:
Field Description
Program ID The program ID of the object or data for which parallel development is to be allowed.
Example: R3TR
Object type The object type of the object or data.

Example: CDAT
Object Name The object name of the object or data.

Example: /RSC/C_DEMO_SYST
5. Click the Execute button from the toolbar. A list of object(s) or table data for which parallel development has been allowed in the
25
Rev-Trac Guide
How to allow parallel development when locking of SAP configuration is enforced at table key level
Rev-Trac 7 SPS02 onwards

From Rev-Trac SPS02 onwards, authorised managers can approve or reject parallel development requests that have been submitted to
the parallel development queue, via the Parallel Development Workbench.
Before Rev-Trac 7 SPS02

Follow the steps below to allow parallel development in an additional Rev-Trac request if you are not using Parallel Development
Workbench. Before you proceed, please ensure the additional request already exists.
STEPS
1. From the Rev-Trac Console, go to menu path Administration > System log. The 'RSC - Display Rev-Trac system log' screen is
displayed.
2. Tick the Show parallel devel. Messages? checkbox.
3. To view the locking message Rev-Trac has previously displayed for the locked item, type 34 in the Message number field.
Complete other selection fields as needed.
4. Select Execute from the toolbar. A list of locking messages is displayed.
5. Select one or more log entries that refer to the locked item(s) for which you want to allow parallel development.
6. Select Allow parallel dev. from the toolbar. An information dialog is displayed with the 'Please select the execute button on
7. Select Continue. The 'RSC - Parallel development' screen is displayed. Check that:
The Allow parallel development radio button is selected.
The Lock keys area displays details of the item(s) for which you may now allow parallel development in an additional
request.
8. In the Rev-Trac Request field, type or select the number of the Rev-Trac request where you intend to allow parallel
development. Note: Make sure it is not the Rev-Trac request to which the item(s) is currently locked.
9. If you are allowing parallel development of SAP configuration settings, you may perform the steps below to identify the actual
configuration table keys involved:
a. Select the relevant Lock keys entry.
b. Click the Show table keys button.
10. Click the Execute button on the toolbar. A list of object(s) or table data for which parallel development has been allowed in the
26
Rev-Trac Guide
How to disallow parallel development that has been approved
Note
You can disallow the parallel development only if the transport containing the object(s) or table data has not been added into the
parallel development request.
Steps
1. From Rev-Trac Console, select Administration > System log. The 'RSC - Display Rev-Trac system log' screen is displayed.
2. To view approved parallel development messages, type 37 in the Message number field. Complete other selection fields as
needed.
3. Select the Show parallel devel. Messages? checkbox.
4. Select Execute from the toolbar. A list of allowed parallel development messages is displayed.
5. Select one or more log entries that correspond to the object(s) or table data for which you want to disallow parallel development.
6. Select Disallow par'l dev. from the toolbar. An information dialog is displayed with the 'Please select the execute button on
7. Click the Continue button. The 'RSC - Parallel development' screen is displayed. Check that:
The Disallow parallel development radio button is selected.
The Lock keys area displays details of the object(s) or table data for which parallel development permission is to be
disallowed.
8. In the Rev-Trac request field, type or select the Rev-Trac request for which parallel development is to be disallowed.
9. Click the Continue button on the toolbar. A list of object(s) or table data for which parallel development has been disallowed in
the selected Rev-Trac request, is displayed.
27
Rev-Trac Guide
How to display approved and disallowed parallel development requests
From Rev-Trac 7 SPS02 onwards, you will be able to view parallel development requests that are approved via the Parallel
Development Workbench.
However, you will still need to follow the procedure below to view parallel requests that are disallowed.
For installation prior to Rev-Trac 7 SPS02, please follow the procedure below to view approved and disallowed parallel requests.
Steps
1. From Rec-Trac Console, go to menu path Administration > System log. The 'RSC - Display Rev-Trac system log' screen is
displayed.
2. Look for the following message numbers (see example below).
Message 37 for allowed parallel development.
Message 38 for disallowed parallel development.
28
Rev-Trac Guide
How to notify relevant parties when parallel development requests are submitted
In Rev-Trac 8 SPS00, a new Rev-Trac customer exit is introduced to enable the relevant parties to be notified when parallel
developments are requested. After a parallel development request is successfully submitted, an email is sent to the user nominated in
the customer exit.
This article describes how to set up the customer exit.
Steps
1. From Rev-Trac Console, go to menu path Configuration > Global > Advanced. The 'Display View "Over-rides": Overview' screen
is displayed.
2. Switch to Change mode and press Enter. The 'Change View "Over-rides" Overview' screen is displayed.
3. Select New Entries from the toolbar.
4. Complete the following fields. XXX is the SAP user ID.
Over-ride Parameter Sub Parameter 1 Sub Parameter 2 Value
CUSTOMER_EXIT 031 USER=XXX ON
5. Save your changes.
29
Rev-Trac Guide
Parallel Development Workbench
The Parallel Development Workbench (SAP GUI) was introduced in Rev-Trac 7.2 to facilitate better parallel development control and
visibility.
Later, the workbench was also launched in Web GUI v8.0.0.
The workbench provides the following functions:
Active parallel development report lists requests that have been approved for parallel development.
Parallel development request queue allows authorised managers to approve, reject or redirect Rev-Trac requests that
developers have submitted for parallel development.
In-flight parallel changes (check) report lists Rev-Trac requests and transports to which ABAP Workbench objects are locked.
Ability to configure cross project locking. For configuration details, please refer to OOPS, Locking system, sensitive objects
and whitelists from Documentation > Administrator Guides via Rev-Trac support portal.
Note: From Rev-Trac 8 SPS00 onwards, accessing the workbench will require authorisation value PD_001 to be assigned to authorisation
object Y/RSC/CE04 (Tools / Utilities).
30
Rev-Trac Guide
How to approve and reject parallel development requests via the workbench
This page describes the steps to approve and reject requests that have been submitted for parallel development and added to the parallel
development queue.
If approval is successful
Message 'Parallel development allowed in Rev-Trac request <n> for object <object name>' is displayed in the approvals
history of the request.
The request(s) is removed from the queue.
Workflow messages are emailed to the developers who requested for the parallel development and manager who approved
the request(s). The title of the email contains 'Parallel development allowed in Rev-Trac <n>'.
If rejection is successful
Message 'Parallel development rejected in Rev-Trac request <n> for object <object name>' is displayed in the approvals
history of the request.
The rejected request(s) is removed from the queue.
Workflow messages are emailed to the developers who requested for the parallel development and the manager who
rejected the request(s). The title of the email contains 'Parallel development rejected in Rev-Trac <n>'.
Web GUI
STEPS
1. At your dashboard, click on PD workbench from the left toolbar and select Parallel development request queue.
2. Complete the appropriate selection fields or use the default values.
3. Click the Search button.The queue is displayed.
4. Select one or more requests and scroll to the bottom of the queue (see illustration below).
5. To approve, select Approve selected and click on Approve at the confirmation dialog.
6.
31
Rev-Trac Guide
6. To reject, select Reject selected and click on Reject at the confirmation dialog.
SAP GUI
STEPS
1. Use transaction /RSC/OPW1 or from Rev-Trac Console, go to menu path Request Management > Tools > Parallel Dev
Workbench. The Active parallel development report selection screen is displayed by default.
2. Click the Parallel development request queue tab.
3. Complete the appropriate selection fields or use the default values.
4. Click the Display button.The queue is displayed (see iilustration below).
5. Select one or more requests.

6. Click the Approve button from the toolbar to approve or Reject button to reject.
32
Rev-Trac Guide
How to redirect parallel development requests via the workbench
Web GUI
STEPS
1. At your dashboard, click on PD workbench from the left toolbar and select Parallel development request queue.
2. Complete the appropriate selection fields or keep the default value.
4. Select a request.
5. Click the Actions button at the end of the request and select Redirect (see illustration below). The Redirect parallel
development request dialog is displayed.
6. Type or select an existing Rev-Trac request to be the new parallel request and select Redirect. See illustration below.
SAP GUI
STEPS
3. Complete the appropriate selection fields or keep the default value.
4. Click the Display button.The queue is displayed.
5. Select one or more requests to be moved and click the Redirect button from the toolbar. The Redirect parallel development dia
log appears.
6. Type or select an existing request to be the new parallel request and select Continue (see illustration below).
33
Rev-Trac Guide
If redirect is successful
Message 'Parallel development allowed in redirect Rev-Trac request <n> for object <object ID>' is displayed in a popup
window.
The selected request(s) are removed from the parallel development request queue.
Workflow messages are emailed to the relevant parties below. The title of the email contains 'Parallel development redirected
to Rev-Trac <n> from <original request n>'.
The release request owner of which the redirect request is attached to.
The developer who requested for parallel development.
The manager who redirected (and approved) the parallel development request.
The redirect Rev-Trac request will now carry the object(s).
The activities are recorded in the Rev-Trac system log which can be retrieved from the Rev-Trac Console via menu path
Administration > System log.
34
Rev-Trac Guide
How to view requests to which selected object is currently locked via the workbench
Web GUI
STEPS
1. At your dashboard, click on PD workbench from the left toolbar and select Parallel development requests queue.
2. Complete the appropriate selection fields or keep the default values.
4. Select the request from the queue and click the Actions button at the end of the line item. See illustration below.
5. Select the Show locked requests option. The Locked Rev-Trac requests are displayed, as shown in the illustration below.
6. Click on the request number to display the request details.
SAP GUI
STEPS
Workbench.
4.
35
Rev-Trac Guide
4. Click the Display button.The queue is displayed (see illustration below).
5. Select a locked object entry and click the Show lock list button from the toolbar. The request to which the object is locked is
displayed in Rev-Trac Workbench.
36
Rev-Trac Guide
How to display approved parallel development requests via the workbench
Web GUI
STEPS
1. At your dashboard, click on PD workbench from the left toolbar and select Active parallel development report.
2. In Rev-Trac 8 SPS00, a new check box called Show historic parallel developments has been added to the selection screen of
the report so that requests which are not in lock-holding statuses are only displayed if this check box is selected. Leaving the
check box unselected (by default) will exclude requests in statuses that do not hold locks.
4. Click the Search button.A list of approved parallel development requests is displayed (see illustration below).
SAP GUI
STEPS
3. Click the Display button. A list of approved parallel development requests is displayed (see illustration below).
37
Rev-Trac Guide
Created by, Created date and Created time refer to the developer who requested for the parallel development.
38
Rev-Trac Guide
In-flight parallel check

The in-flight parallel check functionality has been introduced and enhanced in the following versions:
From Rev-Trac 7 SPS03, the Parallel development report by object report introduced in Rev-Trac 7.2.0 (SPS02) has been
enhanced and renamed to In-flight parallel check report.
You can generate the report based on the following selection criteria:
An ABAP object
One or more transports
A Rev-Trac request
Ignore status lock option
This option allows you to choose whether the report should include, objects that are not currently locked
(meaning Locked Mode = 1 via menu path Rev-Trac Console > Configuration > Process > Strategies >
Status).
You can also execute an in-flight parallel check on a Rev-Trac request from the Rev-Trac Workbench and Release
Management Workbench. Note: In this case, objects that are currently locked due to Rev-Trac status lock configuration
will not be listed.
From Web GUI 7.3.3, you can only view historical in-flight parallel check reports which were executed in SAP GUI.
The in-flight parallel check report could display a list of locked objects which were also contained in other requests. These other
requests were also shown, however it was not obvious which of these requests were Change requests and which were Release
requests. In Rev-Trac 8 SPS00, improvement has been made so that Release Requests are highlighted in green in the report.
From Web GUI 8.0.0, you can also execute in-flight parallel check on a request from the request screen and generate In-flight
parallel changes reports (this is the equivalent of the In-flight parallel check report in SAP GUI) from the Parallel Development
Workbench.
The check will list Rev-Trac requests and transports to which ABAP Workbench objects are locked (see illustration below).

39
Rev-Trac Guide
40
Rev-Trac Guide
How to perform in-flight parallel checks via Parallel Development Workbench
Web GUI
STEPS
1. At your dashboard, click on PD workbench from the left toolbar and select In-flight parallel changes report. The Search
in-flight parallel changes dialog is displayed.
2. Select one of the following search mode and complete the relevant selection fields:
By object – to report on selected ABAP workbench or configuration objects
By transports(s) – to report on selected transports
Continue to click on the transports you want to select and it will be added to the input field.
By request – to report on a single request
3. To apply report filters, click the Add button next to Changes filter. The In-flight parallel changes filter dialog is displayed.
a. Select and complete the appropriate selection criteria.
i. Set Ignore status lock equals True if you want the report to include, objects that are not currently locked
(meaning Locked Mode = 1 via menu path Rev-Trac Console > Configuration > Process > Strategies > Status).
ii. Set Ignore releases equals True (only available from Rev-Trac 8.1.0) to exclude Release requests from the
report.
iii. Set Ignore clone requests (only available from Rev-Trac 8.1.0) to exclude clone requests from the report.
b. Click OK to accept the report filters or Cancel if you decided not to apply any filters.
The Add button changes to Edit (this indicates report filters have been entered).
To cancel all report filters, click on Clear.
4. Click the Search button. The results is displayed.
Example
The illustration below shows a report with the following specifications:
Search mode: By request

Changes filter: Ignore status lock equals True
SAP GUI
STEPS
1.
41
Rev-Trac Guide
Workbench.
2. Click the In-flight parallel check report tab. The report selection fields are displayed.
3. Select one of the following radio buttons and complete the relevant selection fields:
Select Object – to report on selected ABAP workbench or configuration objects
Select transports(s) – to report on selected transports
Select Rev-Trac request – to report on a single request
4. If desired, select the following filters in the Filter in flight parallel changes section.
Ignore Rev-Trac Status Lock Configuration
To include, objects that are not currently locked (meaning Locked Mode = 1 via menu path Rev-Trac Console >
Configuration > Process > Stategies > Status).
Ignore Release requests (only available from Rev-Trac 8.1.0)
To exclude Release requests from the report.
Ignore clone requests (only available from Rev-Trac 8.1.0)
To exclude clone requests from the report.
5. Click the Display button at the bottom of the screen.
6. If you have chosen options other than Select Rev-Trac request, the report will be displayed (see illustration below).
7. If you have chosen the Select Rev-Trac request option, the ‘Run inflight parallel check report in background mode’ popup
window is displayed.
Select No to run the report in the foreground or Yes for background.
If you have chosen to run the report in the foreground, the report will be displayed (see illustration below).
If you have chosen to run the report in background mode, you will also receive a workflow email with the title ‘In-flight
parallel check report completed in Rev-Trac <number>’.
To display the in-flight parallel check report that was run in background mode:
1. Display the request tree in Rev-Trac Workbench.

2. Expand the Approvals node and click on the message I328 ‘Inflight
parallel check report completed’ that matches the date and time the
in-flight parallel check report background job was submitted. The report
will be displayed (see illustration below).

42
Rev-Trac Guide
43
Rev-Trac Guide
How to perform an in-flight parallel check on a request

This page describes the steps to perform an in-flight parallel check for the particular request while you are querying the request.
If you need to perform a check using other selection criteria, please refer to How to perform in-flight parallel checks via Parallel
Development Workbench.
Web GUI
The tool is accessible only from the request screen when you click on the request number anywhere in Web GUI.
STEPS
1. At the request screen, click the Safety Checks button from the Utilities section and select In-flight parallel check.
2. The check is submitted as a background job and the information is displayed (see illustration below).
3. Click OK to return to the request screen.

4. Select Approvals tab to view the check report. If you need help, please refer to How to view the in-flight parallel check report
in Rev-Trac Web GUI.
Tips
Depending on the system performance and amount of data, the batch job may take a while to complete.
Reports generated in background jobs are always retrievable in the future via the Approvals tab.
SAP GUI
The tool is accessible from Rev-Trac Workbench and Release Management Workbench.
STEPS
1. To perform the check from Rev-Trac Workbench:

a. From Rev-Trac Console, type the request number in the Request field and click the icon beside it. The Rev-Trac request
tree is displayed.
b. Select the request number and select In-flight parallel check from the toolbar. The Run inflight parallel check report
in background mode pop-up window is displayed.
2. To perform the check from Release Management Workbench:
a. From the Rev-Trac Console, go to menu path Request Management > Release Management > Release Management
44
Rev-Trac Guide
2.
a.
Workbench.
b. Type or select a project from the dropdown list and click the Execute icon from the toolbar.
c. Switch to Change mode.
d. Select a Release request and select In-flight parallel check from the toolbar. The Run inflight parallel check report in
background mode pop-up window is displayed.
3. Select No to run the report in the foreground or Yes for background.
a. If you have chosen to run the report in the foreground, the report will be displayed (see illustration below).
b. If you have chosen to run the report in background mode, you will also receive a workflow email with the title ‘In-flight
parallel check report completed in Rev-Trac <number>’.
To display the in-flight parallel check report that was run in background mode:
1. Display the request tree in Rev-Trac Workbench.

2. Expand the Approvals node and click on the message I328 ‘Inflight parallel check report completed’ that matches the date and time the
in-flight parallel check report background job was submitted. The report will be displayed (see illustration below).

45
Rev-Trac Guide
How to view the in-flight parallel check report in Rev-Trac Web GUI
Steps
1. Display the approvals history of the request.
2. Search for the ‘Inflight parallel check report completed’ message.
If the message cannot be found, click the Reload button from Actions of the toolbar (on the top left of the screen).
3. Click the View button to display the in-flight report (see illustration below).
46
Rev-Trac Guide
Transport dependencies
Overview
Rev-Trac uses the concept of transport dependency to ensure that pre-requisite transports are imported into their target systems or
equivalent systems before dependent transports can be migrated to the same systems, or equivalent systems.
The dependencies can only be applied to transports attached to Rev-Trac requests.
The transports involved do not have to be attached to the same request, or even relate to the same landscape.
Transport dependencies can be useful if, for example:
Related changes (such as changes to DDIC data elements and program changes that reference these) need to be migrated in a
specific sequence.
Related changes in different landscapes (i.e. R/3 and BW) need to be synchronised.
You can define transport dependencies at two different levels:
Transport level
Transport level dependency is referred to as Transport dependency. It explicitly defines one transport as a pre-requisite of
another transport to ensure the pre-requisite transport must have been migrated before the dependent transport can be
migrated to the same systems.
Request level
Request level dependency is referred to as Request dependency. It defines one request as a pre-requisite of another
request to ensure all transports / xDeploy packages of the pre-requisite request must have been migrated / deployed before
any transport / xDeploy package of the dependent request can be migrated / deployed to the same systems (for xDeploy
information, please refer to the xDeploy Administrator and User Guide).
For example, if Rev-Trac request 156 is defined as the pre-requisite request for Rev-Trac request 289, this would mean that
all transports on request 156 would have had to be imported into the target systems or equivalent systems before any
transport on request 289 can be migrated. Transports of request 156 will precede the transports of request 289 in the
Rev-Trac migration queue.
All additions and deletions of request dependencies will be reported in the request change log.
If both transport and request dependencies are defined for the same transport, the transport dependency will take precedence over the
request dependency for the same transport, in the Rev-Trac migration queue. This means that the queue is first sequenced to satisfy the
request dependency and sequenced again to satisfy the transport dependency.
The Unsatisfied dependencies report
A transport dependency checking routine will validate if all applicable dependencies are satisfied when a user tries to approve a migration
status. A migration status, if approved, will trigger migration activity such as releasing or queuing a transport. If an unsatisfied dependency
is found, a report (see example below) will be displayed and the approval may or may not be allowed.
The report will display details of all applicable unsatisfied dependencies. The example above shows a pre-requisite transport has not been
imported.
Transport dependencies reports
47
Rev-Trac Guide
Transport dependencies reports are also available to list defined transport and request dependencies.
48
Rev-Trac Guide
How to view and manage transport dependencies
The following steps describe how to view and manage a transport dependency between a transport and its pre-requisite transport. For this
purpose, the transport is referred to as transport A and its pre-requisite, transport B.
Web GUI
STEPS
Display the request for which you want to create the transport dependency.
To define a dependency:
1. At the request details screen, click the Edit button to switch to change mode and select the Technical tab. The request technical
2. Click the Actions button of transport A and select Edit dependencies (see illustration below).
3. The Edit transport dependencies dialog is displayed.

4. Click the + Add button to specify transport B (pre-requisite) for transport A. The Add transport dependency dialog is displayed.
5. In the Source field, type or select the source system from the dropdown list. In the Number field, type the transport number. If
you do not know the transport number, type a search term (part of the transport number or title) and select the number from the
dropdown list.
6. Click the Add button. Transport B will appear as the pre-requisite for transport A (see illustration below).
49
Rev-Trac Guide
7. To specify another dependency, repeat from step 4 to 6.

8. Click the OK button to close the Edit transport dependencies dialog.
9. Select Save to save your changes. Rev-Trac will perform a validation on the proposed dependencies.
a. If error occurs, the changes will not be saved and you will be advised what is causing the error.
b. If no error occurs, the screen will change to display mode. The dependency relationship will be created. At the request
technical screen, you will see a dependency icon displayed in the Status column (see illustration below).
To view the transport's dependencies:
1. At the request technical screen, click the dependency icon (in the Status column) of the transport. The View transport
dependencies dialog is displayed as illustrated below.
a. Alternatively, click the Actions button of the transport with a dependency icon and select View dependencies.
Tips
If the transport dependencies view is not up-to-date, click on the Actions button of the request and select Reload.
50
Rev-Trac Guide
To remove a dependency:
1. At the request technical screen, click the Edit button to switch to change mode.
2. Click the dependency icon (in the Status column) of the transport. The Edit transport dependencies dialog is displayed.
a. Alternatively, click the Actions button of the transport with a dependency icon and select Edit dependencies.
3. Click the Delete button at the end of the dependency to be removed and select Delete at the confirmation popup.
4. Click the OK button to close the Edit transport dependencies dialog.
5. Select Save to save your changes.
SAP GUI
STEPS
1. Display the request for which you want to create the transport dependency, on the Rev-Trac Workbench.
2. Expand the Transports node and double-click transport A. The Display transport details dialog is displayed.
3. Click the Change button at the bottom of the dialog and click the Dependencies button. The Dependencies dialog is displayed
(see illustration below).
51
Rev-Trac Guide
4. Click the Add button on the Pre-requisites section to define transport B (pre-requisite) for transport A.
a. If a request dependency has been defined for the request of transport B, the Rev-Trac Dependency validation dialog
may pop-up to display the validation result of the proposed dependency (see illustration below).
b. Select Yes to continue.
5. The Please choose an entity type dialog is displayed.

6. Double-click the T (CTS Transport) option. The Dependency details dialog is displayed.
7. In the Transport source system field, select the source system of transport B.
8. Type transport B number in the Transport field and press Enter.
9. Select Continue. If no error was found, transport B will appear in the Pre-requisites list.
10. Select Continue. The Change transport details dialog is displayed.
11. Select Save to save your changes. At the Rev-Trac Workbench screen, you will see a dependency icon displayed on the left of
transport A (see illustration below).
52
Rev-Trac Guide
To view the transport's dependencies:
1. Display the request you want to view, on the Rev-Trac Workbench.

2. Expand the Transports node and double-click the transport with the dependency icon. The Display transport details dialog is
displayed.
3. Click the Dependencies button. The Dependencies dialog is displayed.
1. Display the request whose transport dependency you want to remove, on the Rev-Trac Workbench.
2. Expand the Transports node and double-click transport A. The Display transport details dialog is displayed.
3. Click the Change button at the bottom of the dialog and click the Dependencies button. The Dependencies dialog is displayed.
4. Select the transport dependency to be deleted and click the Delete button. The dependency will be removed from the Pre-requisi
tes list.
5. Select Continue. The Change transport details dialog is displayed.
53
Rev-Trac Guide
How to view and define request dependencies
The following steps describe how to view and define a request dependency between a request and its pre-requisite request. For this
purpose, the request is referred to as request 1 and its pre-requisite request is referred to as request 2.
While you are defining a pre-requisite for a request, Rev-Trac will perform a validation on the proposed dependency. The result can
contain warning or error messages. If an error is found, the dependency will not be created. Possible warnings and errors are as
follow:
Warnings
Pre-requisite request has no transport.
One identical transport is found on a request and its pre-requisite request.
Errors
Dependency is not allowed if more than one identical transports are found on a request and its pre-requisite request.
Dependency is not allowed between requests that contain transport source systems belonging to different
landscapes unless the systems are defined in the equivalent system group.
You cannot define a request as the pre-requisite to itself.
You cannot define an existing pre-requisite request as a pre-requisite request again.
You cannot define the depended-on-by request as a pre-requisite request.
Web GUI
STEPS
1. Display the request for which you want to create a dependency.

2. At the request detail screen, click the Edit button to switch to change mode and click the Actions button.
3. Select Edit dependencies (see illustration below) to display the Edit request dependencies dialog .
4. Click the + Add button. The Add dependency dialog is displayed.

5. Leave the Type field as Rev-Trac Request, the default value. In the Value field, type the request number of the pre-requisite
(known as request 2). If you do not know the request number, type a search term (part of the request number or title) and select
the request from the dropdown list.
6. Click the Add button. Rev-Trac will perform a validation on the proposed dependency. If no error occurs, request 2 will appear as
the pre-requisite for request 1. See illustration below.
54
Rev-Trac Guide
6.
7. To add another pre-requisite, repeat from step 3 to 6.

8. Click the OK button to close the Edit request dependencies dialog.
9. Select Save to save your changes to the request.
To view the request's dependencies:
1. Display the request for which you want to view.

2. At the request detail screen, click the Actions button.
3. Select View dependencies. The View request dependencies dialog is displayed as illustrated below.
Tips
If the request dependencies view is not up-to-date, click on the Actions button of the request and select Reload.
55
Rev-Trac Guide
1. Display the request for which you want to remove a dependency.

2. At the request detail screen, click the Edit button to switch to change mode.
3. Click the Actions button and select Edit dependencies. The Edit request dependencies dialog is displayed.
4. Click the Delete button at the end of the dependency to be removed and select Delete at the confirmation popup.
5. Click the OK button to close the Edit request dependencies dialog.
6. Select Save to save your changes to the request.
SAP GUI
STEPS
1. Display the request for which you want to create a dependency, on the Rev-Trac Workbench.
2. Double-click the request number and switch to Change mode.
3. Go to menu path Request > Dependencies. The Dependencies dialog is displayed. You will see all existing pre-requisites and
dependants of the request (see illustration below).
56
3.
Rev-Trac Guide
4. Click the Add button on the Pre-requisites section to define request 2 (pre-requisite) for request 1. The Dependency details dial
og is displayed.
5. In the Rev-Trac Request field, type or select the pre-requisite request from the dropdown list and press Enter. If the Rev-Trac
Dependency validation pop-up appears to display the validation result of the proposed dependency, read the results and close
the pop-up.
6. Select Continue. If no error was found, request 2 will appear in the Pre-requisites list.
7. Repeat step 4 to 6 to add more pre-requisite requests.
8. Select Continue to return to the request details screen.
9. Select Save to save your changes. At the Rev-Trac Workbench screen, you will see a dependency icon displayed on the left of
the request as illustrated below.
To view the request dependencies:
1. Display the request you want to view, on the Rev-Trac Workbench screen.
2. Double-click the request number with the dependency icon. The Display request details dialog is displayed.
3. Go to menu path Request > Dependencies. The Dependencies dialog is displayed. You will see all the existing pre-requisites
and dependants of the request.
1. Display the request whose dependency you want to remove, on the Rev-Trac Workbench screen.
2. Double-click the request number and switch to Change mode.
3. Go to menu path Request > Dependencies. The Dependencies dialog is displayed. You will see all existing pre-requisites and
dependants of the request (see illustration below).
4. Select the dependency to be deleted and click the Delete button. The dependency will be removed from the Pre-requisites list.
5. Select Continue to return to the request details screen.
6.
57
Rev-Trac Guide
58
Rev-Trac Guide
How to display transport dependencies reports
Steps
1. From Rev-Trac Console, go to menu path Migration > Reports > Dependencies. The 'RSC – Dependencies report' selection
2. Select an option from the Pre-requisite type pull-down selection list.
R for request level transport dependency reports.
T for transport level transport dependency reports.
3. Execute the report. The dependencies reports are displayed (see illustration below).
59
Rev-Trac Guide
Overtake and Overwrite Protection System (OOPS)
Overview
Transports containing changes to ABAP workbench objects and SAP configuration data (table data) should be migrated to their
destinations in the same order in which they were released.
Rev-Trac Overtake and Overwrite Protection System, also referred to as OOPS, performs checks to detect any object and data
overtaking and overwriting before transports are actually imported into their destinations, and reports the result in an OOPS report.
Rev-Trac provides two types of OOPS checks:
Automatic OOPS checks

Ad hoc OOPS checks
Automatic OOPS checks
OOPS can automatically check for potential overtakes and overwrites when:
A migration status of a request is approved. A migration status is a status, if approved, will trigger migration activity such as
releasing a transport or adding a transport to the Rev-Trac migration queue.
A transport is manually added to the Rev-Trac migration queue, from the Rev-Trac Migration Workbench.
A transport is manually migrated immediately to the target group, from the Rev-Trac Migration Workbench.
Rev-Trac does not perform automatic OOPS checks when:
Rev-Trac batch migration utility migrates items in the Rev-Trac migration queue to their destinations.
Transports are migrated using the TP command or STMS transaction.
Tips
You can first perform manual OOPS checks on the transports using the Rev-Trac Workbench or Rev-Trac Migration
Workbench, and then perform the actual migration using TP command or STMS transaction.
Ad hoc OOPS checks
When performing an ad hoc OOPS check, Rev-Trac will calculate the next migration/deployment status defined on the request and use
the systems defined on the target group definition for this migration/deployment status as the destination systems for the OOPS check.
Prior to Rev-Trac 7.3.0 (SPS03), ad hoc OOPS checks could only be performed in the foreground via Rev-Trac Workbench, Migration
Workbench and migration queue. From Rev-Trac 7.3.0 (SPS03) onwards, ad hoc OOPS check can also be performed on multiple
Rev-Trac requests in background mode.
Ad hoc checks can be performed on:
Transports displayed on the Rev-Trac Migration Workbench.

Transports present in the Rev-Trac Migration queue.
A single Rev-Trac request in the Rev-Trac Workbench.
Multiple Rev-Trac requests in batch mode.
60
Rev-Trac Guide
OOPS Report
When you approve a Rev-Trac request into a status that will trigger an automatic migration of the request's transports, OOPS checks
whether the proposed migration is safe.
If the proposed migration might be unsafe, potential overtakes and overwrites are reported in the OOPS Report (see illustration below).
OOPS can detect several different types of potentially unsafe migrations, including:
An Overwrite
An Overtake
A Foreign overwrite
If you see an OOPS Report with the above messages, you should proceed with the migration only if you are confident you understand
why you are getting this warning, and you are completely sure that it is safe to proceed with the migration despite the warning. Otherwise,
contact your Rev-Trac administrator for advice.
Will overtake message
For example, assume that transport DEVK01 contains an early version of an ABAP program, and transport DEVK02 contains a later
version of the same program.
DEVK01 was migrated to QA1 system in June. When a user attempts to migrate DEVK02 to QA1 in November, Rev-Trac OOPS reports
that DEVK02 will overtake DEVK01, when DEVK01 has already gone to QA1.
This could be due to the possible scenarios:
The earlier version of the ABAP program is no longer present in QA1 because the system was refreshed from another system or
the system was imperfectly restored. You can check if the objects carried by transport DEVK01 are still present in QA1 using
transaction SE01.
While the transport DEVK01 was imported into QA1, the migration did not succeed.
The Rev-Trac migration monitor job may not be scheduled in QA1. If this is the case, Rev-Trac might be unaware of DEVK01's
presence in that system.
Will overwrite foreign message
If you want to migrate ZZ_SOME_OBJECT to a target system, and if Rev-Trac detects that the most recent change to
ZZ_SOME_OBJECT in the target system is in a transport that is not also present in the system from which ZZ_SOME_OBJECT is about
to be migrated, OOPS will report a Will overwrite foreign message.
61
Rev-Trac Guide
This migration is potentially unsafe, as Rev-Trac is unable to determine which version of ZZ_SOME_OBJECT is the earlier. It is even
possible that the object about to be migrated, and the object with the same name in the target system, and two different objects that
happen to share the same name, in which case proceeding with the migration could lead to very unfortunate consequences.
62
Rev-Trac Guide
How to respond when potential OOPS conflicts are found in the OOPS report
Steps
1. Click on the Back button from the toolbar of the OOPS report. The 'Rev-Trac OOPS Alert ' dialog will appear (see illustration
below).
2. Select Continue if you are completely sure that it is safe to proceed with the migration, otherwise, select Stop.
3. After the user's response, OOPS will log the OOPS message and user response in the Rev-Trac request's Approvals node (see
illustration below).
63
Rev-Trac Guide
How to notify request owners regarding OOPS conflicts
New feature from Rev-Trac 8 SPS01
In Rev-Trac 8 SPS01, a new Rev-Trac customer exit is introduced to send workflow messages to the owners of requests causing
OOPS conflicts. The customer exit will be triggered when the user nominated in the customer exit selects the continue button in the R
ev-Trac OOPS Alert popup.
This article describes how to set up the customer exit.
Steps
1. From Rev-Trac Console, go to menu path Configuration > Global > Advanced. The 'Display View "Over-rides": Overview' screen
is displayed.
2. Switch to Change mode and press Enter. The 'Change View "Over-rides" Overview' screen is displayed.
3. Select New Entries from the toolbar.
4. Complete the following fields. XXX is the SAP user ID of the user.
Over-ride Parameter Sub Parameter 1 Sub Parameter 2 Value
CUSTOMER_EXIT 032 USER=XXX ON
64
Rev-Trac Guide
How to perform OOPS check on a Rev-Trac request
From Rev-Trac 7.1.0 (SPS01) onwards, ad hoc OOPS check is allowed on a request currently in a migration status and the user will
be prompted to either stop the check or continue to check the next migration status of the request. This feature was not available
previously.
Note
Check that all transports attached to the request are released.
Web GUI
STEPS
1. Display the request.

2. Click the Safety Checks button from the Utilities section and select OOPS check.
3. An OOPS report is displayed. The example below shows there are conflicts found.
4.
65
Rev-Trac Guide
4. You can filter the OOPS report by selecting one of the four filters:
Select All (by default) to show all OOPS messages.
Select Overtake to show only Will Overtake messages
Select Overwrite to show only Will Overwrite messages
Select Foreign to show only Will Overwrite Foreign messages
5. Select OK. The OOPS report can later be retrieved from the Approvals node of the request.
SAP GUI
STEPS
1. From Rev-Trac Console, enter the Rev-Trac request number into the Request field and click the button beside it.The request is
displayed in the Rev-Trac Workbench.
2. Select the Rev-Trac request number and select OOPS check from the toolbar.
The 'Ad Hoc OOPS check for request <Rev-Trac request number> (status <Status>) -> F1' message will pop up.
3. Select Continue. One of the following results will occur.
a. If any transport attached to the request is unreleased state, the following error will appear and the check will not
proceed.
Error message
Transport SIDK9##### has not been released - (May be still releasing)
Please release all transports for OOPS checking (E446)
b. If potential overtakes or overwrites are found, the OOPS report will appear.
i. OOPS will log the message below in the Approvals node of the request as displayed on the Rev-Trac
Workbench.
ii. Click on this entry to display the OOPS report.
OOPS message
DD.MM.YYYY HH:MM:SS I623:OOPS Conflicts found via Ad Hoc OOPS check. <User name>
66
Rev-Trac Guide
How to perform OOPS check on transports in the Rev-Trac Migration Workbench
You can use this method to check if migrating a particular transport or transports in a given sequence will result in an overtake or overwrite
without actually migrating the transport(s).
Steps
Populate the Rev-Trac Migration Workbench with relevant transports.
Tips
There are several ways to populate the workbench. These include:
Manually typing in the transports.

Pasting in a list of transports from the clipboard.
Selecting transports from a filtered list of transports on Rev-Trac requests.
Importing transports from a Rev-Trac transport list.
Importing transports from an external text file.
Select Oops check from the toolbar.
If potential overtakes or overwrites are found, the OOPS report will appear.
67
Rev-Trac Guide
How to perform OOPS check on transports in the Rev-Trac migration queue
Steps
1. Use one of the following methods to display the queue:
a. From the Rev-Trac Console, go to menu path Migration > Migration queue > Manage / view queue.
b. From the Rev-Trac Console, click on the buttons on the Queue Statistics area to display the queue items (see illustration
below). It shows user P Dann has 0 items added to the queue and the queue currently has 3 items in total.
i. Click the top button to display only items added to the queue by the logged in user.
ii. Click the lower button (Total) to display all items currently in the queue.
2. Display the Rev-Trac migration queue and then go to menu path Queue > OOPS check.
68
Rev-Trac Guide
How to perform OOPS check on multiple Rev-Trac requests in background mode
This function is only available from Rev-Trac 7.3.0 (SPS03) onwards
Steps
From Rev-Trac Console, go to transaction /n/rsc/op03. The 'RSC – Ad hoc OOPS report submit' selection screen is displayed.
Complete the following fields:
Field Description
Rev-Trac request This is a mandatory field. Select the multiple selection icon beside the entry field and type the Rev-Trac
requests to be checked.
Name of spool Use the given spool name or type a new one.
request
Jobname Use the given job name, which is ADHOC_BACKGROUND_OOPS.
Select the Execute button from the toolbar. The job will be submitted to perform the OOPS checks in the background.
Use transaction SM37 to view the outcome of the job.
Select the finished job and perform any step below:
Select Job log from the toolbar. The Job log overview is displayed, listing all Rev-Trac requests for which ad hoc OOPS checks
have been performed.
Select Spool from the toolbar. A spool request is displayed.
Select the spool request and click Display from the toolbar.
The OOPS report is displayed, listing potential overtakes and overwrites of the transports carried by the checked
Rev-Trac requests.
69
Rev-Trac Guide
How to display historical OOPS report in Web GUI
Rev-Trac master system must be running version 7.3.1 or later to support this function, otherwise, you will get an error message.
Steps
2. Select the Approvals tab.
3. Click the Show History button, if necessary.
4. Search for the ‘OOPS Conflict found’ message and click the View button to display the OOPS report (see iilustrations below).
70
Rev-Trac Guide
If you are a licensed Rev-Trac Insights (Salt) user, you can select the View comparison link to compare the object versions with Salt
Match Box app.
From Rev-Trac Web GUI 7.3.3 onwards, the following features have been introduced:
Next to the objects where comparison can be made, you may see a green tick to indicate the objects are identical or a red
alert icon to indicate the objects are different. This can help assess OOPS messages for false positives.
You can filter the OOPS report by selecting one of the four filters:
Select All (by default) to show all OOPS messages.
Select Overtake to show only Will Overtake messages
Select Overwrite to show only Will Overwrite messages
Select Foreign to show only Will Overwrite Foreign messages
71
Rev-Trac Guide
How to display historical OOPS reports and responses to OOPS alerts in SAP GUI
Historical OOPS messages and user responses can be retrieved using the following methods:
If the Rev-Trac request number is known, expand the Approvals node of the Rev-Trac request in the Rev-Trac Workbench. Go
to How to retrieve OOPS messages and user responses from the Rev-Trac Workbench.
If the Rev-Trac request number is unknown or no Rev-Trac request is related, search the Rev-Trac system log. Go to How to
retrieve OOPS messages and user responses from the Rev-Trac system log.
How to retrieve OOPS messages and user responses from the Rev-Trac Workbench
STEPS
1. Display the request in Rev-Trac Workbench.

2. Expand the Approvals node. OOPS messages and user responses are displayed (see iilustration below).
3. Click on Message logged area where the message contains ‘OOPS Conflicts found’.
4. The original OOPS report will be displayed.
How to retrieve OOPS messages and user responses from the Rev-Trac system log
STEPS
From the Rev-Trac Console, select Administration > System log. The ‘RSC - Display Rev-Trac system log’ screen is displayed.
Complete some or all of the following fields.
Field Description
Date Date of the OOPS check.
Time Time of the OOPS check.
User ID SAP user ID of the user who triggered the OOPS check.
Message To search for OOPS messages in systems from RevTrac 6.0 SPS02 and onwards, type the following message
number numbers:
595 for 'OOPS conflicts found before import' via automatic OOPS checks
623 for 'OOPS conflicts found via Ad Hoc OOPS checks'
592 for 'Stop button selected'
593 for 'Continue button selected'
To search for OOPS messages in systems prior to RevTrac 6.0 SPS02, type the following message numbers:
454 for 'OOPS conflicts found before import'

475 for 'Stop button selected' messages
476 for 'Ignore button selected' messages
Rev-Trac The Rev-Trac requests containing the transports that were checked
request
Select Program > Execute. The selected Rev-Trac system log entries are displayed.
To display the original OOPS report for an ‘OOPS conflict found’ message, click the page icon to the right of the logged user ID as shown
in the illustration below.
72
Rev-Trac Guide
73
Rev-Trac Guide
Peripheral Object Dependency System (PODS)

The PODS check tool was introduced in Web GUI 7.1.0 to allow you to analyse each workbench object in the transports of the enquired
request, if they have referenced objects and so, if the required versions are found in the target systems.
The check is automatically triggered during the approval of a request migration status to determine if the transports proposed for migration
have any object dependency issues.
For instructions on how to manually execute a PODS check, please refer to How to perform PODS check in Web GUI
74
Rev-Trac Guide
How to perform PODS check in Web GUI
Steps
1. Click on Safety Checks under Utilities from the dashboard or request screen and select PODS check.
2. If you are performing the check from the dashboard, the Run PODS check dialog is displayed.
a. Select a request and migration status from the dropdown lists.
b. Click the Run button. The PODS check results are displayed (see illustration below).
3. If you are performing the check from the request screen, the request and migration status are pre-selected in the Run PODS
check dialog and the check results are displayed immediately (see illustration below).
4. The results also display counts per overall result. You can select any combination of filters to help you focus on a particular result.
For example, the illustration below shows the filtered results when Queued and In selection are selected.
Explanation
Source
The source system of a transport of the enquired request.
Dependency
75
Rev-Trac Guide
A dependency is an object that is referenced by an object contained in a transport of the enquired request; both
objects come from the same source system.
The same dependency may appear multiple times if the transports originated from different source systems.
Click the dependency object to drill-down to Version Vault (see illustration below) so you can quickly view the object
source code. This is applicable only to licensed Rev-Trac Insights users.
Type
The type of object, i.e. program, function module, structure, screen, etc.
Minimum required version
The minimum required version of the dependency, which exists in the source system, to be analysed against the
target system.
The information in this column is taken from SAP Version Management of the dependency.
The numbers, other than 0, beside the transport number, indicate versions released in chronological order; 0 is the
current active version and 1 is the oldest/original released version. Please see illustration below.
76
Rev-Trac Guide
At the start of the result, this value is pre-selected and is determined by matching the timestamps of the transports
with those of the dependency versions.
If required, you can select a different version from the dropdown list and the tool will immediately recalculate the
result.
Overall result
The following results are possible. You can use tooltips to view the explanation of each result.
The minimum required version is found in the target system. However there are two possible findings:
The minimum required version is identical to the current active version in the target system.
The minimum required version is found in the dependency's history and the current active version matches a more
recent version in the source system.
77
Rev-Trac Guide
The minimum required version is missing from the target system.
The minimum required version is found in the dependency's history in the target system, however the current active
version does not match any version in the source system.
The minimum required version is not found in the target system.

The current active version of the dependency in the target system matches a version in the source system, which is
newer than the chosen minimum required version.
The minimum required version is not found in the target system, however it is currently in the Rev-Trac migration
queue en route to the target system.
The minimum required version is not found in the target system, however it is included in the transports attached to
the request being analysed.
The system is not configured as a target system for the transport. This may occur when source-specific migration
applies.
The result cannot be computed due to unexpected errors with one or more target systems, which usually rarely
occurs.
Target systems
A separate column will appear for each applicable target system.

When the result is overwritten or overtaken, you can click here to quickly view the object source code difference
between the two systems in Salt Match Box, as shown in Figure: Link to Salt Match Box from PODS check
results. This is applicable only to licensed Rev-Trac Insights users.
78
Rev-Trac Guide
Figure: Link to Salt Match Box from PODS check results
79
Rev-Trac Guide
Change Impact Scoring System (CISS)

CISS check has been introduced in Web GUI v7.3.5 to facilitate change impact analysis.
The CISS check determines which other objects will be impacted by a proposed migration of the transports carried by a request and
provides a score for each impacted object to indicate the importance based on usage statistics and relative position in the impact graph.
An impacted object (parent) is an object, which directly references an object found in the transports (child) of the request. The impacted
objects for object A are typically the objects that are found as a result of performing 'where-used' on object B in SAP GUI.
The CISS check tool is more enhanced in terms of checking the impacts recursively rather than just giving the immediate impacts. The
impacted objects are determined recursively until the total number of unique impacts touched recursively by a change reaches a limit (100
for now).
The CISS check tool is particularly useful to determine whether any change to a particular object (or a set of objects) is impacting other
objects. A typical scenario would be to check if a change to a function module is impacting any report or transaction that could potentially
be used (or is being used) in the production system. If there is an impact, all the impacted objects can be included in the next test cycle to
check for regression.
The check is automatically triggered during the approval of a request migration status. For instructions on how to manually execute a
CISS check, please refer to How to perform CISS check in Web GUI.
80
Rev-Trac Guide
How to perform CISS check in Web GUI
Steps
1. Click on Safety Checks under Utilities from the dashboard or request screen and select CISS check.
2. If you are performing the check from the dashboard, select a request from the dropdown list for the Request field in the Run
CISS check dialog.
a. Click the Run button. The CISS check results is displayed (see illustration below).
3. If you are performing the check from the request screen, the request is pre-selected for the Request field in the Run CISS check
dialog and the check results is displayed immediately (see illustration below).
Explanation
The following table explains what each column means.
Column Description
Source The source system of the impacted objects.
Impacted An impacted object (parent) is an object, which directly references an object found in the transports (child).
object The impacted objects are determined recursively until the total number of unique impacts touched recursively for a change
reaches a limit (100 for now).
Type The type of object, i.e. program, function module, structure, screen, etc.
Usage The SAP usage that can be obtained from SAP transaction ST03N.
Users The user statistics that can be obtained from SAP transaction ST03N.
81
Rev-Trac Guide
Score The standard score (z-score in Statistics) is calculated for each of the following factor, for each impact and then, combined
to produce the final score.
The score increases when SAP usage and user statistics increase. If an impact does not have a score (which is true
for most of the impacts) from the SAP statistics, it is given the average score (0).
The score increases when number of changes that are directly impacting the object increases.
The score decreases when the number of levels deep of the impact increases.
The results are sorted by the score.

By default, only callable types (reports, programs and function modules) are displayed.
The results can be filtered by source and callable types (reports, programs and function modules).
Once the analysis is run on a particular request, the result is cached for 6 hours from the last run and any further run displays the cached
result. It is clearly displayed at the top of the results, whether it is a cached result and it can be reloaded by clicking the Reload button.
82
Rev-Trac Guide
Basic User Guide for Web GUI
Introduction
Use this guide to help you perform common tasks with Rev-Trac requests via Rev-Trac Web GUI, such as creating new requests and
attaching supporting documentation, updating and signing the requests.
83
Rev-Trac Guide
How to log into Rev-Trac Web GUI
From Rev-Trac Web GUI 7.3.0 onwards, the following enhancements have been made:
Access to Rev-Trac Web GUI is available from the Rev-Trac master system's Rev-Trac Console in SAP GUI.
Log in to the Rev-Trac master system is available via monitored systems i.e. QA and PROD.
You can log in to Rev-Trac Web GUI via:
Rev-Trac Console in SAP GUI

Attached hyperlink
URL
Steps
1. To log in via Rev-Trac Console in SAP GUI, select Launch the Rev-Trac web GUI from the Rev-Trac Console toolbar. The Log
in screen is displayed.
2. To log in via attached hyperlink, click on the link attached, i.e. from a workflow email, and you will be directed to the Log in scree
n.
3. If you know the Rev-Trac Web GUI URL, you can go to the URL in your browser. The Log in screen is displayed.
4. Below is an illustration of the Web GUI log in screen.
84
Rev-Trac Guide
5. Select the SAP system to log into.

6. If SSO is enabled, select Log in using single sign-on.
7. If you are not using SSO, enter your SAP user id and password and click the Log in button.
85
Rev-Trac Guide
Web GUI dashboards

The Web GUI dashboard has been significantly enhanced from version 8.0.0 onwards.
This page provides an overview of what the current version offers compared to previous versions.
From Web GUI 8.0.0 onwards
The current version comes with a left toolbar that provides access to the following functionalities.
Please click on the links for instructions.
Search
Create
Agile workbench
Release workbench
Parallel development (PD) workbench
Reports
Propagation report
Migration and deployment log
xReports
Safety checks
PODS check
CISS check
Queues
Migration and Deployment queue
Rev-Trac Insights (Salt)
In addition, it comes with a standard dashboard and also allows you to create your own dashboards for the Rev-Trac master system.
The standard dashboard provides quick access to your favourite list of requests, and, visual summary and statistics comprising:
Open requests in value chart

New requests grouped by request type in line chart (this chart can be changed using different Date range)
Open requests by project in pie chart
86
Rev-Trac Guide
Open requests by request type in table chart

Open requests by team and request status in bar chart
You can double-click on the charts to drill-down to the underlying requests.
You can also create custom dashboards that can only be privately viewed or publicly shared. To create a new dashboard, refer to How to
create a dashboard.
To go to dashboards other than the standard dashboard, click the pulldown button and select the dashboard of your choice.
The dashboard you created will be listed under Owned by me and those shared by others will be listed under Public. See illustration
below.
To return to the dashboard from other pages , click on the Rev-Trac logo at the top left corner.
Before Web GUI 8.0.0
The dashboard in the prior versions provides access to the following functionalities and features. Please click on the link for instructions.
87
Rev-Trac Guide
Work in progress
This section provides quick access to work-in-progress requests. Selection criteria for these requests are:
Status excluding NEW (new request), COMP (complete) and DELT (deleted).
The logged in user is either the owner, programmer, customizer or actor.
Favourites
This section provides quick access to requests marked as favourite.
Search for requests
Create new requests
Integrity Hub
PODS check
CISS check
Reports
Propagation report
Migration and deployment log
xReports
Utilities
Migration and Deployment queue
Salt
To go to Salt, click on
at the top right corner and select Access Salt.

For instructions on how to use Salt, please refer to Rev-Trac Insights User Guide.
To return to the dashboard from other pages , click on the Rev-Trac logo at the top left corner.
88
Rev-Trac Guide
How to create a dashboard
You can create a dashboard from scratch or copy from an existing dashboard.
Steps
To create a dashboard from scratch:
1. Click the + Add button. The Add dashboard dialog is displayed, as shown below.
2. Type the name of the dashboard and select Public or Private access level.
3. Save your new dashboard. The new dashboard is displayed with two items (by default): My work in progress and New
Requests by Type.
4. To customise the dashboard, please refer to How to edit a dashboard.
To copy a dashboard from an existing one:
1. Select the dashboard to be copied from.

2. If you are copying from a dashboard that you previously created, click the pulldown arrow next to Edit and select Copy from the
dropdown option (see illustration below).
3. If you are copying from a dashboard that was not created by you, click the Copy button (see illustration below).
89
Rev-Trac Guide
3.
4. Type a new name for the dashboard or change the access level.
5. Save your dashboard. The new dashboard is displayed with all the items copied from the original dashboard.
6. To customise the dashboard, please refer to How to edit a dashboard.
90
Rev-Trac Guide
How to edit a dashboard
Steps
1. You can only modify dashboards that are created by you.
2. Click on Edit. The Edit dashboard dialog is displayed.
3. Type a new name for the dashboard or change the access level.
5. To add more items to the dashboard:
a. Select Add item. The Add item dialog is displayed.
b. Select Chart or List type. Currently, all items on the dashboard are derived from requests.
c. Type a name for the item.
d. If you selected a Chart item, select from the following Chart type : area, bar, gauge, line, pie, table, matrix or value. For
example, see illustration below. Note: The matrix chart type has only been introduced in Rev-Trac Web GUI 8.0.1.
i. Select a term for the Group by field.

ii. The groups are limited to the top 5 (by default), but you can select a smaller number of groups.
iii. Select a saved search from the dropdown list or leave the field blank.
iv. Click on Save.
e. If you selected a List item, for example, see illustration below.
91
Rev-Trac Guide
i. Select a saved search from the dropdown list or leave the field blank.
ii. Click on Save.
6. To modify or delete an existing item on the dashboard:
a. Click on
of the item.
b. To modify the item, select Edit. The Edit item dialog is displayed.
i. Make your changes and select Save.
c. To delete the item, select Delete. A warning is displayed.
i. Read the warning and click on Delete.
92
Rev-Trac Guide
How to create new requests (Web GUI)
Steps
1. Click the Create… button from the dashboard.

2. Complete the Title field and other relevant fields in the Details tab.
Field Description

(Mandatory) This title will appear on many Rev-Trac screens and reports, and by default will be included in the texts of
transports created under Rev-Trac control and associated with this request.
Note: There is no connection between a Rev-Trac project and a project defined in the SAP Project System
(PS) module.
(Mandatory)
release Rev-Trac project release relates to SAP changes released in subprojects or clusters, which may be known as
phases, rollouts or waves.
The request owner may be responsible for giving some approvals and deleting the request. The requests
belonging to the owner will appear in the Owner tab on the Rev-Trac Console.
Programmer Type or select from the pull-down list the SAP ID of the person responsible for doing programming work for the
change.
The programmer may be responsible for giving some approvals. The requests belonging to the programmer will
appear in the Programmer tab on the Rev-Trac Console.
Customizer Type or select from the pull-down list the SAP ID of the person responsible for doing customizing work for the
change.
Note: The Customizer field is only available in a specific version of request details screen. If you require this
field, please consult your Rev-Trac administrator.
The Actor will receive a workflow message whenever this request is saved, and has to act on the request. The
requests belonging to the actor will appear in the Actor tab on the Rev-Trac Console.
Class The request class determines whether fewer or more approvals (or different approvals) are required for this
request than otherwise would be.
93
Rev-Trac Guide

For example, you may use the decimal point system to prioritise one request from another i.e. a request with
Priority of 3.2 is seen as less important than a request with Priority of 3.1.1.
Test date Type the date when changes associated with a Rev-Trac request are expected to be in the Test (or QA)
system.
date
Keywords Type a search term to be used to search for this request via Rev-Trac Workbench selection screen in SAP
GUI.
3. Complete the following additional information as required:

a. Comments
i. Click on Add button under Comments to add relevant notes to help others working on the request. Note: Comme
nts cannot be deleted after the request is saved.
New feature from v8.1.0

You can trigger an email to be sent to a Rev-Trac user by typing '@<user ID>' as part of the comment.
Below are two examples.
Example 1: You want to notify Joe ($$JBLOKE) to update team information.
Example 2: You want to notify John ($$JWAYNE) and Joe ($$JBLOKE) to attach some documentations to
94
Rev-Trac Guide
the request.
b. Attachments
i. Select Attachments tab and add as attachments specifications, SAP Notes or reviews that contain useful
information to help others working on the request.
c. References
i. Select References tab and add as references OSS note, a Help Desk record, online resources and other
objects.
4. Select Save from the toolbar to save your changes and return to Display mode.
5. If you select Cancel from the toolbar, you can choose:
a. Don't save to return to Display mode without saving.
b. Cancel to return to current screen and mode without saving.
95
Rev-Trac Guide
How to search requests (Web GUI)

You can search requests using the following three methods:
Using search box

Using Search... from the dashboard
Using saved searches
From Web GUI v7.3.0 onwards:
You can save your searches for reuse later.

Rev-Trac performs smart searching using your input at the search box. If an exact match is found, the request details screen
is displayed. If an exact match is not found, a list of search result is displayed.
Using search box
Steps
1. If you know the request number, type the number in the
search box at the top right corner of the screen and press Enter.
2. If the request exists, the request details screen is displayed.
3. If you do not know the request number, type a text of the title or significant digits of the number and press Enter.
a. Rev-Trac performs a smart search using your input. If an exact match is found, the request details screen is displayed.
b. Otherwise, a list of search result is displayed.
c. If you still do not find the request you want, try Using Search... from the dashboard option, as described below.
Using Search... from the dashboard
Steps
1. Click on Search... from the dashboard.
2. The default search term and operator are set to Title and contains.
3. Select and type your own search terms and operators.
96
Rev-Trac Guide
Tips
Use wildcard * and/or + with search operators under Patterns only.
Do not use quotation marks such as "" or ''.
For date/time search, you can choose to enter only the date or if necessary, turn on the time selection to enter the
time.
4. Click the + button to add another search term and the – button to remove a search term. See illustration below.
5. To further narrow your search, click the Add group button and use the All or Any boolean operator. See illustration below.
97
5.
Rev-Trac Guide
6. Click the Search button. A search result is displayed.

7. To return to the default search term, click the Reset button.
To save the search criteria for reuse later

At the search selection screen, click on
and select Save this search.
To create a new saved search
1. Select Save as.

2. The Save new search window is displayed. See illustration below.
98
Rev-Trac Guide
3. Give the search a name.

4. Select Public or Private sharing mode and click the Save button.
5. The name of the search is displayed at the top of the screen.
To change the current saved search
1. Make sure the Saved search : <current saved search> window is displayed. See illustration below.
2. To replace the saved search with the new search criteria you have chosen:
a. Click the Save button. The new search criteria is saved under the same saved search name.
3. To rename or change the access level of the saved search:
a. Make the necessary changes and click the Save button.
b. The new name of the search is displayed at the top of the screen.
Using saved searches
Steps
1. At the search selection screen, click on
. A list of options and recently used saved searches are displayed (see illustration below).
99
Rev-Trac Guide
1.
2. Select a recently used saved search, if suitable, otherwise, select View saved searches. The Saved searches dialog is
displayed with Name as the default search term and contains as the default operator.
3. Leave the input field blank to retrieve a list of all saved searches or type a search value.
4. Alternatively, select a more suitable search term and operator from the dropdown lists. To further narrow your search, click the Ad
d group button and use the All or Any boolean operator.
5. Click the Search button. A list of saved searches is displayed.
6. Select a suitable saved search and click the OK button.
7. Click the Search button again. A search result is displayed.
New feature from 8.1.0

The Saved searches result list displays a new column called References as illustrated in the following example.
The References column displays, if any, the total number of agile boards and dashboards referencing the saved searches. Click on
the number to reveal the boards.
Agile boards and dashboards that are viewable by currently logged in users are shown as clickable links. A private agile board or
dashboard owned by another user is displayed as "Private” in grey, only to indicate there is an existing reference to the saved search.
100
Rev-Trac Guide
How to display requests (Web GUI)

There are three ways to display a request:
Click on the request number from the dashboard (if available).

Type a text or significant digits of a request number in the search box
at the top right corner of every screen and Rev-Trac will perform a smart search. Smart search is available from Web GUI v7.3.0
onwards.
If an exact match is not found, a list of search result will be displayed. Click on the request number from the search
result.
Select Search... from the dashboard. Click on the request number from the search result.
Tips
The request details is displayed by default. Click on Actions from the left toolbar and select Reload, to clear the cache and load the
latest request details.
101
Rev-Trac Guide
How to change request details fields including protected fields (Web GUI)
Changing unprotected fields will not affect the status of the request.
On the contrary, your organisation may decide to set up a rule such that if the content of a particular request field changes (i.e.
Rev-Trac project, request type, etc.), the status of the request should change automatically.
If changing a particular field may automatically change the status of the request, the field is protected until you open the field for input.
Steps

2. The Details tab is displayed by default. Click the Edit button to switch to Change mode.
3. Change the relevant input fields.
4. To change protected fields:
a. Click on Actions from the left toolbar and select Unlock protected fields….A Warning message will pop up.
b. Select Continue to proceed.
c. The protected fields are now unprotected and you can proceed to change their values.
i. If you intend to change both the Project and Request type, change the Project first. This ensures the correct list
of options is available in the Request type field.
ii. To be able to select an appropriate status for the request other than what is configured, you may need the
appropriate authorisation.
102
Rev-Trac Guide
How to display change history log of a request (Web GUI)
Steps

2. From the toolbar, click the Actions button and select Reload.
3. Click the Reports button from the Utilities section and select Change log.
The Change log records changes that have occurred to the request since it was first created. Changes are grouped under
heading related to the type of change recorded (see illustration below).
4. Select the heading to expand the details of the changes.
103
Rev-Trac Guide
Mobile approval (Web GUI)
Steps
1. If you are responsible to sign a request, you will receive a workflow email as shown in the illustration below.
2. If you are logged in, click on the hyperlink in your workflow email and you will be directed to the relevant request, otherwise, you
will need to log in first.
To approve the request:

From version 8.0.0 onwards, a status bar is always displayed under the title of the request. It shows (see illustration below):
Current status (green)

Next status in the approval path (blue)
Remaining statuses in the strategy (grey)
1. To approve the next status, click on the status (in blue) at the status bar.
2. If there is more than one approval type to be signed off, the Choose approval type dialog is displayed (as shown below).
a. Select the approval type and click the Approve button. The request screen is displayed again.
104
Rev-Trac Guide
3. Otherwise, click the Approve button at the Approve request status dialog.
4. If the approval process is complete, the status bar is updated with the latest changes.
To reject the request:

1. Select Workflow from the left toolbar. The approval information is displayed.
2. Click the Reject button. The Reject request status dialog is displayed.
3. You may need to type the reason for rejection (if configured). See illustration below.
4.
105
Rev-Trac Guide
4. Select Reject and the status is set to the reject status that is configured in the strategy (as shown below).
106
Rev-Trac Guide
How to sign a request (Web GUI)

The most common reason for signing a request is to approve its next status. In some cases, you may also sign a request to reject it. When
a status is rejected, the status will change to the reject status that is configured in the strategy.
Note
Only specified personnel in the approval rules are authorised to sign the request. Rev-Trac typically sends you a workflow email for
each request you are responsible for signing.
You may be eligible to sign a request for any of the following reasons:
Your name appears in a request field (i.e. as Owner, Programmer or Customizer).

You hold a position in a team whose name appears in the Team field of the request.
You hold a position in a team that is named explicitly in the strategy used to manage the request.
You are defined in Rev-Trac as a stand-in position holder (i.e. as standin ABAP/4 development team leader).
You are nominated as a delegate for approval purposes.
Steps
1. If you are responsible to sign a request, you will receive a workflow email as shown in the illustration below.
2. If you are logged in, click on the hyperlink in your workflow email and you will be directed to the relevant request, otherwise, you
will need to log in first.
To approve the request:

From version 8.0.0 onwards, a status bar is always displayed under the title of the request. It shows (see illustration below):
Current status (green)

Next status in the approval path (blue)
Remaining statuses in the strategy (grey)
1. To approve the next status, click on the status (in blue) at the status bar.
2.
107
Rev-Trac Guide
2. If there is more than one approval type to be signed off, the Choose approval type dialog is displayed (as shown below).
a. Select the approval type and click the Approve button. The request screen is displayed again.
3. Otherwise, click the Approve button at the Approve request status dialog.
4. If the approval process is complete, the status bar is updated with the latest changes.
To reject the request:

1. Select Workflow from the left toolbar. The approval information is displayed.
2. Click the Reject button. The Reject request status dialog is displayed.
3. You may need to type the reason for rejection (if configured). See illustration below.
108
Rev-Trac Guide
4. Select Reject and the status is set to the reject status that is configured in the strategy (as shown below).
109
Rev-Trac Guide
How to display the approvals history of a request (Web GUI)
Steps

2. From the left toolbar, click the Actions button and select Reload.
3. Select the Workflow tab.
4. Click on the Show history button, if necessary, to expand the approvals history.
110
Rev-Trac Guide
How to add, change and remove references (Web GUI)

Rev-Trac allows references to other records, information sources or objects, to be added to a request.
There are two types of reference allowed:
Simple references are usually static documents relevant to the request such as design specifications, notes or records.
Smart references are references, which are not static documents, such as Rev-Trac requests, LAN files or web URLs, and
provide the following features. You may be able to launch the smart references, i.e. open the files, load the websites and display
the requests, by double-clicking the references.
Steps
The References tab may display the following information:
References
The list shows what the request refers to. Note: References are not restricted to Rev-Trac requests only.
Referenced by
The list shows the requests that refer to the request.
Shared references
The list shows the requests that share one or more requests that are also referred to by this request. This feature is
only available from Web GUI v8.0.0 onwards.
2. Click on the Edit button to switch to change mode and select the References tab.
3. To add a reference to the request:
a. Click the +Add… button.
b. Select the reference type from the dropdown list.
c. Type the value of the reference i.e. number, URL, etc. and a description for the reference. Note: If the reference type is
RT (Rev-Trac Request), ensure you type a valid and existing request number. (In the future, enhancement will be made
to provide a selection list of valid request number).
d. Click the Add button.
4. To change or remove a reference:
a. Click on
at the line item.

b. Select Edit to change or Delete… to remove the reference.
111
Rev-Trac Guide
How to add, change and remove attachments (Web GUI)

You can attach to a request, useful information such as functional and technical specification documents, test results, screenshots, SAP
Notes, email messages or spreadsheets for use by others working on the request.
The attachments can be readily available from your storage or files that you create on-the-fly, based on templates stored within Rev-Trac.
Tips
You can use a template as a base for an attachment but only if the template has already been stored in Rev-Trac.
Rev-Trac compresses attachments before storing them internally in a table in the SAP database. Once attached to a request, it can be:
Edited using the native application

Deleted
Exported as a file
Copied into another Rev-Trac request
Steps

2. Select the Attachments tab and click the Edit button to switch to Change mode.
3. To add an attachment to the request:
a. Click the +Add… button.
b. Select the attachment type from the dropdown list.
c. Choose a file from the file browser and type a description for the attachment.
d. Click the Add button.
4. To change or remove an attachment:
a. Click on
at the line item.

b. Select Edit to change or Delete to remove the attachment.
112
Rev-Trac Guide
How to add comments (Web GUI)
Steps

2. You can add a comment using one of the following methods.
3. In Display mode. Note: This method does not allow you to delete your comment after it is added.
a. Click on + Add button in Comments panel.
b. Type your texts in the input box and select Add at the bottom of the window (Note: You will not be able to delete the
comment after Add is selected.)
4. In Change mode. Note: This method allows you to delete your comment before you click on Save from the toolbar.
a. Select Edit from the toolbar to switch to Change mode.
b. Type your texts in the input box and select Add at the bottom of the window.
c. If you need to change the comment, click on Delete button at the bottom of the comment.
d. If you are happy with the comment, select Save from the toolbar. The request screen switches back to Display mode and
you will not be able to delete any existing comment.
New feature from v8.1.0

You can trigger an email to be sent to a Rev-Trac user by typing '@<user ID>' as part of the comment.
Below are two examples.
Example 2: You want to notify John ($$JWAYNE) and Joe ($$JBLOKE) to attach some documentations to the request.
113
Rev-Trac Guide
How to display migration and deployment queues (Web GUI)
Web GUI
Steps
Follow the instructions below to display a queue for a particular request or selected requests.
To display a queue for a particular request:

2. Select Queues from the left toolbar.
3. To display the migration queue, select Migration queue. The Migration queue for the particular request is displayed (see
4. To display the deployment queue, select Deployment queue. The Deployment queue for the particular request is displayed (see
114
Rev-Trac Guide
To display a queue for selected requests:
1. From the dashboard, select Queues from the left toolbar.

2. To display the migration queue, select Migration queue.
a. Complete your search criteria and select Search. See illustration below.
3. To display the deployment queue, select Deployment queue.

a. Complete your search criteria and select Search. See illustration below.
115
Rev-Trac Guide
116
Rev-Trac Guide
How to display xReports (Web GUI)
Steps
From your dashboard, click the Reports button from the Utilities section and select xReports.
xReports users are automatically logged in to xReports, as shown in the illustration below.
117
Rev-Trac Guide
How to delete a request (Web GUI)
Deleting a request changes the status of the Rev-Trac request to DELT (Deleted).
Once deleted, its status can never be changed.
Deleting a request does not:
Physically remove the request from the system.

Exempt transports attached to the request from overtake checking by the Rev-Trac Overtake and Overwrite Protection
System (OOPS). If you want to prevent OOPS from displaying overtake warnings relating to transports attached to the
deleted Rev-Trac request, ask your Rev-Trac administrator to quarantine the transports (remove their data files from your
transport directory).
Note: Only a Rev-Trac administrator or the request owner (whose name appears in the Owner field of the request details and who is
not necessarily the person who created the request) can delete the request.
Steps

2. Click on Actions from the side toolbar and select Delete.
3. A Warning is displayed. Select Yes to proceed with deletion.
4. The Status field is changed to Deleted.
118
Rev-Trac Guide
Basic User Guide for SAP GUI
Introduction
Use this guide to help you perform common tasks with Rev-Trac requests via Rev-Trac SAP GUI, such as creating new requests and
attaching supporting documentation, updating and signing the requests.
119
Rev-Trac Guide
How to access Rev-Trac from your SAP systems

Rev-Trac is typically installed in multiple systems in your landscape. One of these systems (often, but not always, a development system)
functions as the Rev-Trac master system, which co-ordinates and controls Rev-Trac related processes on the other systems.
Steps
After logging into your SAP system, type transaction /n/rsc/rt. You will see different screens, depending on which Rev-Trac systems you
have logged into.
Rev-Trac master system

If you are logged into the Rev-Trac master system, the Rev-Trac Console is displayed immediately (see illustration below).
SAP system other than the Rev-Trac master

If you are logged into an SAP system other than the Rev-Trac master, the 'Rev-Trac Monitored System' screen is displayed.
To display the Rev-Trac Console on the Rev-Trac master, click the Click this button to log onto the Rev-Trac master system
(non-administrative) button (see illustration below).
120
Rev-Trac Guide
121
Rev-Trac Guide
How to create new requests (SAP GUI)
Steps
1. If the 'Rev-Trac – Add a workbench transport to a request' dialog box is currently displayed, select the Create a new Rev-Trac
request and generate transport radio button. The 'Create request details' screen is displayed.
2. Otherwise, type transaction /n/rsc/rt and then press Enter. The Rev-Trac Console screen is displayed.
a. Click the Create request button. The 'Create request details' screen is displayed.
3. Complete some or all of the following standard Rev-Trac request fields. You can click the Help icon or press F1 to display more
information on the field.
Field Description

(Mandatory) This title will appear on many Rev-Trac screens and reports, and by default will be included in the texts of
transports created under Rev-Trac control and associated with this request.
Note: There is no connection between a Rev-Trac project and a project defined in the SAP Project System
(PS) module.
(Mandatory)
release Rev-Trac project release relates to SAP changes released in subprojects or clusters, which may be known as
phases, rollouts or waves.
The request owner may be responsible for giving some approvals and deleting the request. The requests
belonging to the owner will appear in the Owner tab on the Rev-Trac Console.
Programmer Type or select from the pull-down list the SAP ID of the person responsible for doing programming work for the
change.
The programmer may be responsible for giving some approvals. The requests belonging to the programmer will
appear in the Programmer tab on the Rev-Trac Console.
Customizer Type or select from the pull-down list the SAP ID of the person responsible for doing customizing work for the
change.
Note: The Customizer field is only available in a specific version of request details screen. If you require this
field, please consult your Rev-Trac administrator.
The Actor will receive a workflow message whenever this request is saved, and has to act on the request. The
requests belonging to the actor will appear in the Actor tab on the Rev-Trac Console.
122
Rev-Trac Guide
Class The request class determines whether fewer or more approvals (or different approvals) are required for this
request than otherwise would be.

For example, you may use the decimal point system to prioritise one request from another i.e. a request with
Priority of 3.2 is seen as less important than a request with Priority of 3.1.1.
Test date Type the date when changes associated with a Rev-Trac request are expected to be in the Test (or QA)
system.
date
Keywords Type a search term to be used to search for this request via Rev-Trac Workbench selection screen in SAP
GUI.
4. If you are required to complete custom Rev-Trac request fields on top of the standard fields above, you may need to perform one
of the following steps:
a. If the custom fields are added as tabs in the request detail screen, select the tabs and complete the relevant fields.
b. If the custom fields are not added as tabs in the request detail screen, go to menu path Request > Custom fields. At the
'Custom fields' dialog, complete the relevant fields required and then select Continue.
5. If necessary, you may want to proceed to add the following items to the request:
a. References
i. Add as references OSS note, a Help Desk record, online resources and other objects.
b. Special approvers (deprecated from Rev-Trac 8 SPS01)
i. Nominate a special approver, for example, a tester with special expertise who you want to review and approve
this request at a later time
c. Attachments
i. Add as attachments specifications, SAP Notes or reviews that contain useful information for others working on
the request.
d. History Log
i. Enter any brief note you want others working on this request to see.
ii. Rev-Trac automatically appends your name and the current date and time to each log entry.
iii. Log entries cannot subsequently be changed or deleted after the request is saved.

You can trigger an email to be sent to a Rev-Trac user by typing '@<user ID>' in the History Log area. Note
: Make sure the user's email is defined via menu path Configuration > Process > Organisation > Users.
See the following examples.
Example 2: You want to notify John ($$JWAYNE) and Joe ($$JBLOKE) to attach some documentations to
the request.
123
Rev-Trac Guide
6. Select Save to save the request. The new Rev-Trac request number will be displayed in the Request field on the Rev-Trac
Console screen.
7. If the 'Transport linking' dialog box is displayed, do one of the following below:
a. To save the request without adding a transport or further transport, click the No button. The Rev-Trac Console screen is
displayed. The number of the saved request is displayed in the Request field.
b. To add a new or existing transport to the request, click the Yes button and follow the instructions in the How to add new
or existing transports to a request page.
124
Rev-Trac Guide
How to search and display requests (SAP GUI)

You can search requests using the following two methods:
Via Rev-Trac Console. This method is useful if you want to find Rev-Trac requests quickly.
Using search parameters
Via Rev-Trac Console
Steps
1. From the Rev-Trac Console, select the tab (i.e. Owner, Programmer, Actor, Signatory, All) that corresponds to the subset of
requests you are interested in. For example, to identify all requests for which you are the next signatory, select the Signatory tab.
2. Immediately beneath your name, select the Subtotal or Total button. The Executive matrix screen lists a summary of the
requests you have selected.
In the example below, the Signatory tab for 014 User has a total of 3 Rev-Trac requests that require signing off.
The Executive matrix (see example below) lists a summary of the requests you selected.
3. Do one of the following:

a.
125
Rev-Trac Guide
3.
a. To list on the Rev-Trac Workbench all or some of the requests you selected in the previous step, select the appropriate
number in the Executive matrix. The selected requests are displayed on the Rev-Trac Workbench screen.
b. To display the Executive matrix sorted by different criteria, select Other Matrix from the toolbar and then select the new
criteria.
c. To display the report graphically, select Graph matrix from the toolbar. The SAP Business Graphics screen is displayed.
Using search parameters
This method is useful if you want to find the requests that match particular search criteria, include particular references or transports, or
whose attachments include particular terms, via the Rev-Trac Workbench.
Steps
1. At the Rev-Trac Console, click the Rev-Trac Workbench button. The Rev-Trac Workbench selection screen is displayed.
2. Do one or more of the following:
a. To select requests by one or more request header attributes (i.e. project, request type, status), complete the relevant
fields in the General selections area.
b. To select requests by the contents of custom Rev-Trac request fields, select Custom Selections from the toolbar and
then complete the relevant fields in the Custom Fields area.
c. To select requests that include particular references (i.e. a reference to a particular SAP Note or help desk reference
number) click the References button and then complete the appropriate search criteria.
d. To select requests that contain particular transports, click the Transports button and then complete the appropriate
search criteria.
e. To select requests whose History Log or attachments contain one or more terms, click the Attachments button and then
complete the appropriate search criteria.
f. To select requests for which you are a stand-in approver, enter your own SAP user ID in the User id field, and select Sta
ndin Signatory in the Select only requests for these users area.
g. To select requests to which transports are attached that contain particular objects or data, click the Objects button and
then complete the Object category, Object type and Object name fields in the Object selections area.
h. To display the selected requests initially in an executive matrix view rather than a list, select Matrix view in the Start
options area.
i. To display requests showing their first or second reference number, rather than their request number, select Reference
number 1 or Reference number 2 in the Number display options area.
3. Select Execute from the toolbar to display the search result.
4. At Rev-Trac Workbench, do one of the following:
a. To display the request details, double-click the request number. The 'Display request details' screen appears.
b. To display the request's approval history, attachments, references, transports or other associations, click the + icon at the
left. An expanded view of the request is displayed.
126
Rev-Trac Guide
How to change request details fields including status and protected fields (SAP GUI)
Note
Changing unprotected fields will not affect the status of the request.
On the contrary, your organisation may decide to set up a rule such that if the content of a particular request field changes (i.e.
Rev-Trac project, request type, etc.), the status of the request should change automatically.
If changing a particular field may automatically change the status of the Rev-Trac request, the field is protected until you open the
field for input.
Steps
1. Display the Rev-Trac request on the Rev-Trac Workbench.

2. Double-click the request number. The 'Display request details' screen is displayed.
3. Switch to Change mode.
4. Change the relevant input fields.
5. To change the status of the request:
Any Rev-Trac user may set the status of a request backward. Only a Rev-Trac administrator may set the status of a request
forward.
a. Go to menu path Request > Change status. The Status field is opened for input.
b. Select a suitable status from the list.
c. Save your changes. The Rev-Trac Workbench is displayed and the manual change is logged in the request's Approvals
history showing who made the change, and when.
6. To change protected fields:
a. Go to menu path Request > Change more fields. The 'Automatic status change' dialog box is displayed to inform you that
changing the field value will also change the status of the request.
b. To proceed with the change, click the Continue button.
c. The protected fields are now unprotected and you can proceed to change their values.
d. If you intend to change both the Project and Req type, change the Project first. This ensures the correct list of options is
available in the Req type field.
e. If you need to select an appropriate status for the request, go to menu path Request > Change status.
i. Select a suitable status from the list. Note: If you do not have the appropriate authorisation, you may have to
skip this step.
127
Rev-Trac Guide
How to display change history log of a request (SAP GUI)
Steps

2. Select the request and select Change log from the toolbar. The 'Change documents' screen is displayed.
3. The screen summarises changes that have occurred to the request since it was first created. Changes are grouped under
heading related to the type of change recorded (see illustration below).
128
Rev-Trac Guide
How to sign a request (SAP GUI)

The most common reason for signing a request is to approve its next status. In some cases, you may also sign a request to reject it. When
a status is rejected, the status will revert to the previous status.
Note
Only specified personnel in the approval rules are authorised to sign the request. Rev-Trac typically sends you a workflow email for
each request you are responsible for signing.
You may be eligible to sign a request for any of the following reasons:
Your name appears in a request field (i.e. as Owner, Programmer or Customizer).

You hold a position in a team whose name appears in the Team field of the request.
You hold a position in a team that is named explicitly in the strategy used to manage the request.
You are defined in Rev-Trac as a stand-in position holder (i.e. as standin ABAP/4 development team leader).
You are nominated as a delegate for approval purposes.
Steps
1. If you receive a workflow email that requests you to sign a request, display the Rev-Trac request on the Rev-Trac Workbench.
2. If you did not receive a workflow email, at the Rev-Trac Console, select the Signatory tab to quickly identify the requests for
which you are the next signatory (see iilustration below).
a. Click on the Total button to display the 'Executive Matrix' screen (see illustration below).
129
Rev-Trac Guide
b. Click on a number to display the request tree. For example, click on '2' under the New status (see illustration above). The
request tree is displayed.
3. Expand the request tree to display the Approvals node.
4. Expand the Approvals node and the node that has the Next approval label (see illustration below).
5. Select the approval type, for example, Functional.
Sometimes multiple types of approval (for example, both Functional and Technical) are required.
6. If there is more than one person eligible to sign the status, the 'Please select the appropriate signatory' dialog box is
displayed. Select your name or role.
If the status you are about to approve will result in an automatic migration activity, the details of the migration will also be
displayed under 'Migration activity detail' heading on the "Please select the appropriate signatory" dialog (see illustration
below).
130
Rev-Trac Guide
7. The 'Sign a document' screen is displayed. Review the request details.

8. To proceed, do one of the following:
a. To approve the status, type your SAP password in the open field on the Signoff area and click the Sign document butto
n (see illustration below).
b. If a Reject button is displayed and you want to reject the request, type your SAP password in the open field on the Signo
ff area and click the Reject button. The status will revert to the previous status.
c. If the one-click approval feature has been implemented and you are one of the allowed approver and you are logged on,
you can simply click the Sign button without having to type your password (see illustration below).
131
Rev-Trac Guide
How to display approvals history of a request (SAP GUI)
Steps

2. Expand the request tree to display the Approvals node.
3. Expand the Approvals node and the subsequent status nodes, which are displayed in yellow background (see illustration below).
132
Rev-Trac Guide
How to add special approvers (SAP GUI)
Steps

2. If the Special approvers button is displayed, click on the button, otherwise switch to Change mode.
3. Go to menu path Request > Special approvers. The 'Special approvers' dialog is displayed.
4. Double-click a value from the dropdown list and complete the Text field.
5. Add as many special approvers as needed.
6. Click the Okay button. The newly added special approvers are displayed on the Special approvers button.
133
Rev-Trac Guide
How to pre-select approvers (SAP GUI)

The list of approvers for a Rev-Trac status is based on the number of individuals who match the Rev-Trac Team and Rev-Trac Position
selection criteria for approving the status. Rev-Trac Pre-select approvers functionality can be used to restrict the list of approvers for a
Rev-Trac request status to one or more individuals who hold particular positions within a given team.
Steps

2. Select the Rev-Trac request number and go to menu path Request > Pre-Select approvers > Change. The current Rev-Trac
organisation structure will be displayed (see illustration below).
3. Select one or more approvers in each of the teams for which you want to restrict the number of approvers by clicking the icon
beside the approver’s name. In the example above, Bruce Dunlop will be the only approver displayed where ABAP development
team member sign off is required. There are no Pre-selected approvers for the other teams such as Basis, therefore sign offs by
134
Rev-Trac Guide
3.
other teams would be unaffected.

5. To display preselected approvers go to menu path Request > Pre-Select approvers > Display. The current Rev-Trac organisation
structure will be displayed (see illustration above) and any preselected approvers will be highlighted.
135
Rev-Trac Guide
How to add, change, remove and launch references (SAP GUI)

Rev-Trac allows references to other records, information sources or objects, to be added to a Rev-Trac request.
There are two types of reference allowed:
Simple references
Smart references
Simple references are usually static documents relevant to the Rev-Trac request such as design specifications, notes or records.
Smart references are references, which are not static documents, such as Rev-Trac requests, LAN files or web URLs, and provide the
following features:
Depending on the type of smart references, Rev-Trac will validate the existence of the reference, i.e. files.
You may be able to launch the smart references, i.e. open the files, load the websites and display the requests, by double-clicking
the references from the Rev-Trac Workbench.
Steps

2. Double click the request to display the request details screen.
To add a reference:
1. If you see the References tab, click the tab. Otherwise, go to menu path Request > References.
2. Click the Create button at the bottom of the references list.
3. Double click the reference type from the reference type list and complete the following fields:
Field Description
Reference Type or click the Select button to select a reference.

Tips: The acceptable entry in this field depends upon the reference type. For example, an
SAP Note number, a Rev-Trac request number or a PDF file.
Reference description Type a description of the reference content.
4. Select Continue and save the changes. The Rev-Trac Workbench will be displayed.
To change or remove an reference:

1. To change a reference, select the reference and click the Change button at the bottom of the references list.
a. You can only change the Reference description.
2. To remove a reference, select the reference and click the Delete button at the bottom of the references list.
3. Select Continue and save your changes.
To launch a smart reference:

1. Select the reference and click the Launch button at the bottom of the references list.
2. Alternatively, you can launch the reference from the Rev-Trac request tree.
a. If there is a reference linked to the request, the References node will appear on the request tree (see illustration below).
136
a.
Rev-Trac Guide
b. Click the References node to view the references that are linked to the request.
Note
Sometimes you may see multiple References nodes, which represent different Reference groups. This is because
the Rev-Trac administrator has configured to associate one or more Reference types to a Reference group.
137
Rev-Trac Guide
How to add, change, remove and display attachments (SAP GUI)

You can attach to a Rev-Trac request, useful information such as functional and technical specification documents, test results,
screenshots, SAP Notes, email messages or spreadsheets for use by others working on the request.
The attachments can be readily available from your storage or files that you create on-the-fly, based on templates stored within Rev-Trac.
Tips
You can use a template as a base for an attachment only if the template has already been stored in Rev-Trac.
Rev-Trac compresses attachments before storing them internally in a table in the SAP database. Once attached to a Rev-Trac request, it
can be:
Edited using the native application

Deleted
Exported as a file
Copied into another Rev-Trac request
Steps
Display the Rev-Trac request on the Rev-Trac Workbench.
To add an attachment:
1. Select the request number and go to menu path Attachments > Create. The 'Create attachment: Header' dialog box is displayed.
2. Complete the following fields:
Field Description
Type Type or select an attachment type from the dropdown list.
Title Type the title of the attachment.
3. To attach a PC file, select PC File.

a. Select Save at the bottom right of the dialog box to display a file selection dialog box.
b. Select the file and then click Open.
4. To create an attachment using SAPscript, select SAP WP.
a. Select Save at the bottom right of the dialog box to display the SAPscript editor.
b. Create your document, select Save and then Back from the toolbar.
5. To create an attachment based on a template (i.e. a model Microsoft Word document or a preformatted SAPscript document),
select Template.
a. Select Save at the bottom right of the dialog box.
b. If more than one template file of this type is loaded into the system, select a template from the list when you are
prompted.
c. The appropriate application (i.e. Microsoft Word or the SAPscript editor) is launched and opens the template file. Change
the template file as required, then save it without renaming it and close the file.
The new attachment will be added to the Attachment nodes in the request tree in the Rev-Trac Workbench.
To change or remove an attachment:

1. Select the request number and go to menu path Attachments > Change. The 'Attachments listing' dialog box is displayed.
2. Select the relevant attachment.
3. To change the attachment, select Change attachment from the dialog's toolbar.
a. If the file is a PC-based file (i.e. a Microsoft Word document or Microsoft Excel spreadsheet), Rev-Trac opens the file
using the set default application.
b. Make necessary edits and save the file.
c. Note: If the 'Launch PC application instructions' dialog is displayed in the foreground, do not click Continue on this dialog
138
Rev-Trac Guide
3.
c.
until you have edited and saved the file.
d. Select Continue from the dialog's toolbar.
e. If the file is a SAPscript document, the SAPscript editor opens the document for editing.
f. Change the file and then save it without renaming it.
g. Select Back from the toolbar. The Rev-Trac Workbench is displayed.
4. To remove an attachment, select Delete attachment from the dialog's toolbar and select Continue.
a. At the 'Attachments listing' dialog box, select Cancel from the dialog's toolbar. The Rev-Trac Workbench is displayed.
To display an attachment:
1. Select the request number and go to menu path Attachments > Display. The 'Attachments listing' dialog box is displayed.
2. Select the relevant attachment and select Display attachment from the dialog's toolbar.
3. If the file is a PC-based file (i.e. a Microsoft Word document or Microsoft Excel spreadsheet), Rev-Trac opens the file using the
set default application.
a. Close the file and select Continue from the dialog's toolbar.
4. If the file is a SAPscript document, it will be displayed using the SAPscript editor.
a. Close the file and select Back from the toolbar.
5. At the 'Attachments listing' dialog box, select Cancel from the dialog's toolbar. The Rev-Trac Workbench is displayed.
139
Rev-Trac Guide
How to add a note to a request’s history log (SAP GUI)
Steps

2. Double-click the request number. The 'Display request details' screen is displayed.
Note
Once the note is added, no deletion or changes are allowed.
4. Do one of the following. Note: Rev-Trac automatically adds your name and a date stamp to your note. There is no need to add
this information manually.
a. Type your note in the History Log area.

You can trigger an email to be sent to a Rev-Trac user by typing '@<user ID>' in the History Log area. Note: Make
sure the user's email is defined via menu path Configuration > Process > Organisation > Users.
See the following examples.
Example 2: You want to notify John ($$JWAYNE) and Joe ($$JBLOKE) to attach some documentations to the
request.
b. Copy to the Windows clipboard the text you want to insert, place your cursor in the History Log area, then select Edit >
Paste clipboard.
Tips
To add more extensive documentation, you can add an attachment to the request.
140
Rev-Trac Guide
How to delete a Rev-Trac request (SAP GUI)
Note
Only a Rev-Trac administrator or the request owner (whose name appears in the Owner field of the request details and who is not
necessarily the person who created the request) can delete the request.
Deleting a request changes the status of the Rev-Trac request to DELT (Deleted).
A deleted request continues to be displayed on the Rev-Trac Workbench.
Once deleted, its status can never be changed.
Deleting a request does not:
Physically remove the request from the system.

Exempt transports attached to the request from overtake checking by the Rev-Trac Overtake and Overwrite Protection
System (OOPS). If you want to prevent OOPS from displaying overtake warnings relating to transports attached to the
deleted Rev-Trac request, ask your Rev-Trac administrator to quarantine the transports (remove their data files from your
transport directory).
Steps

2. Select the request number and go to menu path Request > Delete request. The 'Sign a document' screen is displayed.
3. Type your SAP password in the open field and click the Sign document button.
4. If the one-click approval feature has been implemented and you are one of the allowed approver and you are logged on, you can
simply click the Sign button without having to type your password. A message box is displayed to confirm that the status of the
request has been changed to 'Deleted'.
141

RT - Full User Guide PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

RT - Full User Guide PDF

Загружено:

Авторское право:

Доступные форматы

Rev-Trac Guide

Documentation inclusion library

Sample panel and sample table

Request details fields

Title Type the title of the request.

The customizer may be responsible for giving some approvals.

Priority Type a priority defined by your organisation.

In-flight parallel check report screen

New feature in Rev-Trac 8.1.0

Rev-Trac enforcement popup - Refresh lock check button

How to save searches for reuse later

and select Save this search.

To create a new saved search

1. Select Save as.

3. Give the search a name.

To change the current saved search

How to retrieve saved searches

Safety User Guide

Rev-Trac locking system

Rev-Trac enforcement popup

Rev-Trac enforcement if locking of SAP configuration is enforced at table name level

Rev-Trac enforcement if locking of SAP configuration is enforced at table name level

Otherwise, a parallel development has to be requested and allowed.

Rev-Trac enforcement if locking of SAP configuration is enforced at table key level

Otherwise, a parallel development has to be requested and allowed.

Rev-Trac enforcement if Rev-Trac locking system is in advice-only mode

Rev-Trac enforcement if cross project locking is configured

Parallel Development Workbench

Later, the workbench was also launched in Web GUI v8.0.0.

The workbench provides the following functions:

METHOD 2: IF NO 'LOCKED' MESSAGE WAS DISPLAYED DURING REV-TRAC ENFORCEMENT

Object type The object type of the object or data.

Object Name The object name of the object or data.

Rev-Trac 7 SPS02 onwards

Before Rev-Trac 7 SPS02

How to disallow parallel development that has been approved

How to display approved and disallowed parallel development requests

This article describes how to set up the customer exit.

Over-ride Parameter Sub Parameter 1 Sub Parameter 2 Value

CUSTOMER_EXIT 031 USER=XXX ON

5. Save your changes.

Parallel Development Workbench

Later, the workbench was also launched in Web GUI v8.0.0.

The workbench provides the following functions:

5. Select one or more requests.

How to redirect parallel development requests via the workbench

4. Click the Display button.The queue is displayed (see illustration below).

How to display approved parallel development requests via the workbench

In-flight parallel check

New feature in Rev-Trac 8.1.0

How to perform in-flight parallel checks via Parallel Development Workbench

Search mode: By request

1. Display the request tree in Rev-Trac Workbench.

New feature in Rev-Trac 8.1.0

How to perform an in-flight parallel check on a request

3. Click OK to return to the request screen.

1. To perform the check from Rev-Trac Workbench:

1. Display the request tree in Rev-Trac Workbench.

New feature in Rev-Trac 8.1.0

The dependencies can only be applied to transports attached to Rev-Trac requests.

Transport dependencies can be useful if, for example:

You can define transport dependencies at two different levels:

The Unsatisfied dependencies report