smartShift: The expert for fast, risk reduced, tool-based IT modernization.

smartTools Project Preparation

Prerequisites

Version:

1.7

Date:

03/02/2010

Document:

280784494.doc

smartShift GmbH | Willy-Brandt-Platz 6 | 68161 Mannheim, Germany

smartShift Inc | Pier 1 Bay 3 | San Francisco, CA 94111, USA

www.smartshiftgroup.com

[ smartTools Project Preparation - Prerequisites ]

Proprietary Notice
Restriction on user and Disclosure and Quotation Information Data
The information (data) contained in all sheets of this proposal or quotation constitutes a trade secret and/or
information that is commercial or financial and confidential or privileged. It is furnished to the addressee in
confidence with the understanding that it will not, without the permission of smartShift., be used or disclosed for
other than evaluation purposes; provided however, that in the event a contract is awarded on the basis of this
proposal or quotation, addressee shall have the right to use and disclose this information (data) to the extent
provided in the contract. This restriction does not limit addressees right to use or disclose this information (data) if
obtained from another source without restriction.
Copyright 2009 by smartShift.
Private and confidential. All Rights Reserved.

smartShift, 2009
Private and confidential
All rights reserved

Page 2 / 15

[ smartTools Project Preparation - Prerequisites ]

Table of Content
1
2

Introduction..............................................................................................4
Access to Customer systems................................................................5
2.1

2.1.1

VPN Connection...............................................................................................5

2.1.2

Onsite Internet Access......................................................................................5

2.1.3

Onsite Access to Client Network.......................................................................5

Access to SAP systems..........................................................................6

3.1

RFC Destination................................................................................................ 7

3.1.2

Authorization Requirements for Tool Users.......................................................8

Dialog User requirements for smartBridge configuration..................................9

3.2.2

Dialog User for Source System.........................................................................9

3.2.3

Dialog User for Target System........................................................................10

smartBridge Application Installation................................................................11

4.1.2

smartBridge Plug-In Installation......................................................................11

4.1.3

Namespaces to be analyzed...........................................................................11

Installation of smartShift Analyzer and smartShift Transformer..............................12

Technical Prerequisites........................................................................12
5.1

Source System Preparation...................................................................................12

5.1.1

Running the EU_INIT Job...............................................................................12

5.1.2

Running the EU_PUT and EU_REORG Jobs.................................................13

5.1.3

Monitoring Progress........................................................................................ 13

5.2

Installation of smartBridge......................................................................................10

4.1.1

4.2

Transport Requests................................................................................................ 10

smartTools for SAP Installation...........................................................10

4.1

Dialog Users............................................................................................................ 9

3.2.1

3.3

Tool Users................................................................................................................ 7

3.1.1
3.2

Access requirements................................................................................................ 5

Database Backups................................................................................................. 13

Appendix 1 - Minimum HW and SW requirements.............................14

6.1

Minimum HW Requirements..................................................................................14

6.2

Minimum SW Requirements..................................................................................14

Appendix 2 smartShift Tools Overview............................................15

smartShift, 2009
Private and confidential
All rights reserved

Page 3 / 15

[ smartTools Project Preparation - Prerequisites ]

1 Introduction
This document describes the technical prerequisites for an installation of smartShift Tools for
SAP: smartBridge, smartShift Analyzer and smartShift Transformer for SAP for the
conduction of analysis and transformation projects.
The image below shows all components and connections that need to be installed and setup. These are described in detail in the following chapters.
For a brief overview of the smartShift for SAP toolset, please refer to Appendix 2
smartShift Tools Overview.

* Access to customer network via VPN is the preferred access mode. Other options are available.

In order to install smartTools for SAP and perform ABAP source code analysis and
transformation, the following information is required before project start:

Contact Information

Access to Customer systems

Access to SAP systems

Release Information

smartShift, 2009
Private and confidential
All rights reserved

Page 4 / 15

[ smartTools Project Preparation - Prerequisites ]

User Login Data

Installation Data

2 Access to Customer systems

2.1

Access requirements

To be able to install and run smartShift tools for Analysis and Transformation, access to the
customer systems must be available and guaranteed.

VPN Connection
Onsite Internet access

Onsite access to customer network

Dedicated Workstation for running smartTools (optional)

Usually most of the tasks are performed offsite; therefore a VPN connection is required. For
all onsite activities, access to the Internet and customer network will be needed.
In case these accesses cannot be provided, the customer needs to provide a dedicated PC
to run the smartTools applications (please refer to appendix 1 for a list of minimum hardware
requirements).

2.1.1

VPN Connection

For remote access to the client systems, VPN connections will need to be set up for all team
members. The following information needs to be available:
o

VPN Client software (Windows XP and Vista)

VPN Profiles/Certificates

Additional VPN Access hardware such as Tokens

VPN Account data (username and password)

If VPN timeouts are imposed, they need to be as sparse as possible. Please notify us if VPN
timeouts are in place!
The VPN logon procedure needs to be amenable to a machine and should not make the
presence of a human operator necessary.

2.1.2

Onsite Internet Access

While on site, the team requires internet access to allow exchanging data and information
using e-mail and other secure communication mechanisms (e.g. SFTP, etc.)
The team also needs to be able to host WebEx or GoToMeeting sessions in order to involve
our R&D team to resolve customer specific questions.

2.1.3

Onsite Access to Client Network

Our smartTools can run from any PC. If the analysis is performed onsite with smartShift
laptops, these need to have access to the customer network where the SAP Systems
reside.
These access requirements apply to all phases: Source Code Analysis, Source Code
Transformation and Source Code Upload.
During source code transformation, access to the target system (or a similar system at the
same release level) is required. At this point in time no changes will be made to any of the
systems.
For the source code upload it is necessary to have access to the actual target system.

smartShift, 2009
Private and confidential
All rights reserved

Page 5 / 15

[ smartTools Project Preparation - Prerequisites ]

3 Access to SAP systems

Access to the customer SAP systems needs to be set up for smartShift team to be able to
configure and run the tools appropriately.
Please note that there are two different options when using smartShift tools:
A. Analysis Only
B. Analysis and Transformation
This choice has direct impact on setup and configuration. Specifically, if option A is relevant,
any configuration (user creation, RFC destination, smartBridge customization) related to the
target system is not relevant and should be ignored.
The required connection data for each involved SAP system includes:

IP address or host name

SID (SAP System ID)

System number
Client number

Tool User name and password (see below)

Maximum allowed number of concurrent RFC connections

For the Solution Manager system (or other system where the smartBridge tool will be
installed), we need the customers Customer Number and Installation Number (provided by
SAP) in order to install the smartBridge Tool. See section 4 for details on information
necessary for product installation.
For the Analysis Only Option, two types of users are needed to be created in the source
system (e.g. system to be analyzed) Please see section 3.1 and 3.2:
-

1 Tool user in the Source System

(used by the tools for extraction and Analysis)

1-n Dialog user(s) in the Source System

(Used by smartShift to check/validate system. n=1-3 typically)

1 Tool user in the Solution Manager system

(used by the tools for extraction and Analysis)

1-n Dialog user(s) in the Solution Manager System

(Used by smartShift for Analysis and configuration. n=1-3 typically)

For the Analysis and Transformation Option, two types of users are needed to be created in
the source system (e.g. system to be analyzed) - Please see section 3.1 and 3.2:

The users described in the Analysis Only option above, AND:

1 Tool user in the Target system with developer key applied

(used by the tools for upload of transformed source code)

3-n Dialog users in the Target system with developer key applied
(Used by smartShift to validate and remediate the target system. n= 3 -7 typically)

smartShift, 2009
Private and confidential
All rights reserved

Page 6 / 15

[ smartTools Project Preparation - Prerequisites ]

Please note that the above data would need to be provided to smartShift.
It is important to note that both smartBridge and smartShift Analyzer need to be able to
access the source system at the same time.
Please note that on SAP 4.6c systems it is necessary to use upper case letters for
username and password.
Ports 33xx need to be opened in order to enable RFC connections.

3.1

Tool Users

In order to execute the source code analysis and transformation, dedicated tool users
(normal SAP Dialog users with special authorizations see chapter 3.1.2) need to be
created on each participating SAP system. The following setup is required:
-

Tool User on SAP system where smartBridge application is installed

Tool User on each source system to be analyzed

Tool User on each target system

Following naming conventions have been proven useful in previous projects for the setup
and maintenance of these users:
-

Tool User (x_y_smash), where:

o

x = s (source), t (target), sb (smartBridge) and

y is the system ID (e.g. EC1, R3D...)

So for a typical project setup with following three systems involved:

-

Solution Manager (System ID e.g. SMV)

Source System (System ID e.g. EDV)

Target System (System ID e.g. TDV)

The following three users need to be created:

-

sb_SMV_smash on the solution manager

s_EDV_smash on the source system

t_TMV_smash on the target system.

3.1.1

RFC Destination

It is necessary to create ABAP Type RFC Destinations in the system where smartBridge is
installed to the Source and Target SAP systems.
These RFC destinations will need to use the corresponding tool users above:
In Solution Manager (or wherever smartBridge is installed) create 2 ABAP RFC destinations
(Transaction SM59): 1 to the source system, the other to the target system.
In the connection to the source, use user s_y_smash In the connection to the target, use
user t_y_smash.
Please make sure that the name of the RFC Destinations to Source and Target systems
follows the pattern:
<SID>CLNT<MAND>, where SID is the 3 digit system ID, and MAND is the three digit client
number.
If a different name is used, it MUST NOT exceed 10 characters.

smartShift, 2009
Private and confidential
All rights reserved

Page 7 / 15

[ smartTools Project Preparation - Prerequisites ]

3.1.2

Authorization Requirements for Tool Users

The Tool Users need to have at least the following profile.

Auth. Object

Auth.
Field

Value

S_RFC

ACTVT

16

yes

yes

yes

RFC_NAME

/LCOM/*

yes

yes

yes

FUGR

yes

yes

yes

RFC1

yes

yes

yes

SVRW

yes

yes

SCCA

yes

yes

SCTS

yes

yes

SCTS_ATTRIBUTES

yes

yes

SDIF

yes

yes

SDIFRUNTIME

yes

yes

SDTX

yes

yes

SEUEXIST

yes

yes

SIFP

yes

yes

SLOG

yes

yes

STMG

yes

yes

STR8

yes

yes

STR9

yes

yes

STRD

yes

yes

SWY_DB

yes

yes

SYST

yes

yes

yes

yes

SZAD

yes

yes

TRWB_REQUESTS

yes

yes

SUNI

yes

yes

yes

yes

SYSU

RFC_TYPE
S_ADMI_FCD

FUGR

User *
sb_y_smash

yes

yes

User **
s_y_smash

User ***
t_y_smash

yes

S_CTS_ADMI

CTS_ADMFCT

yes

S_CTS_LANG

CTS_LANFKT

yes

S_DATASET

ACTVT

yes

FILENAME

yes

PROGRAM

yes

ACTVT

yes

DEVCLASS

yes

OBJNAME

yes

OBJTYPE

yes

P_GROUP

yes

ACTVT

yes

TTYPE

yes

S_DEVELOP

S_TRANSPORT

S_TABU_CLI

CLIIDMAINT

S_TABU_DIS

DICBERCLS

smartShift, 2009
Private and confidential
All rights reserved

Yes
&NC&

yes

yes

SS

yes

yes

SZ01

yes

yes

Z_OM

yes

yes

Page 8 / 15

[ smartTools Project Preparation - Prerequisites ]

Auth. Object

Auth.
Field

ACTVT

Value

User *
sb_y_smash

User **
s_y_smash

User ***
t_y_smash

SC

yes

yes

02

yes

yes

03

yes

yes

*
sb_y_smash = Tool User on Solution Manger
** s_y_smash = Tool User on Source System
*** t_y_smash = Tool User on Target System
Please note, that the user created on the target system (t_y_smash) is also used for the
automated source code upload and therefore needs a developer key assigned.

3.2

Dialog Users

Dialog users are needed to be created in order to:

-

Configure the smartBridge application on Solution Manager or NW

Have developer access on the target and source systems to be able to troubleshoot
and make remaining manual fixes on the objects.

3.2.1

Dialog User requirements for smartBridge configuration

The dialog user to configure smartBridge should be able to invoke the following
transactions:
-

All transactions in the /LCOM/ namespace. Minimum requirement:

o
o
o
o
o

/LCOM/REGISTER Object Manager Registration

/LCOM/ZO48 Customizing Configurator
/LCOM/ZO41 Repository Snapshot
/LCOM/ZO42 Create Object Work List
/LCOM/ZO43 Process Object Work List

SE38 Execute program /LCOM/OBJECT_LIST_SELECT

SM59 - Maintain RFC Destinations (<SID>CLNT<Client #> for all involved SAP
systems).

SM30 - Maintain View V_TBDLS to maintain logical systems with the same name
as the defined RFC Destinations

If access to SM59 and SM30 transactions is not possible or allowed, the smartShift team will
guide the customers Basis team in performing the required configuration steps.

3.2.2

Dialog User for Source System

The smartShift team will need to have at least 1 user account in the source system in order
to validate and trouble-shoot any issues found in the source system.

Access to transactions:
o

SE11

SE16

SE37

SE38

SE80

smartShift, 2009
Private and confidential
All rights reserved

Page 9 / 15

[ smartTools Project Preparation - Prerequisites ]

3.2.3

SLIN

SCI (Authority object S_COV_ADM Activity 03)

SCID

ST22

Dialog User for Target System

The smartShift team might be required to perform agreed upon manual changes on the
transformed and uploaded objects. Therefore additional Dialog user accounts with
developer level access will be required. The accounts need to have development keys
applied to them. These accounts need to meet the following minimum requirements:
-

3.3

Access to transactions:
o

SE09

SE11

SE16

SE37

SE38

SE80

UCCHECK

SLIN

SCI (Authority object S_COV_ADM Activity 03)

SCID

ST22

Individual developer keys for each of the relevant systems

Transport Requests

In order to ensure a clean separation of code changes that are initiated by the tool, a set of
transport requests needs to be created and assigned both for the developers as well as for
the smartTool.
Whenever code is transported from the smartTool to the target system, it will be done under
the assigned transport request, thus allowing both better overview and management of the
transports.

4 smartTools for SAP Installation

4.1

Installation of smartBridge

The smartBridge consists of two components:

-

the smartBridge application installed on a Solution Manager or Netweaver 2004s

system (or greater)

the corresponding plug-ins for each of the source and target systems

When installing the application or the Plug-Ins, all objects imported into any system are
developed in a dedicated development namespace (/LCOM/). Therefore there will be no
impact whatsoever for the customer systems.

smartShift, 2009
Private and confidential
All rights reserved

Page 10 / 15

[ smartTools Project Preparation - Prerequisites ]

4.1.1

smartBridge Application Installation

The smartBridge application needs to be installed on a Solution Manager 4.0 (latest Patch
recommended). In case there is no Solution Manager available, the smartBridge application
requires at least a Netweaver 2004s base system.
4.1.1.1

License Key

In order to run the smartBridge application a license key is required.

The license key can only be generated with the support of smartShift. In order to obtain a
valid license following information is needed:
Information

Format

SAP Customer Number

Desired validity period of license

From date to start date

SAP Installation number

0000000000

SID of system

XXX

System number

00

Host name

XXXXXXXXXXXXXXXXXXXXXXX

The requested information to create the license key needs to be from the system
where the actual smartBridge application is installed. The information can be
acquired using the transaction SLICENSE.
Based on this information, smartShift will generate a license key which will be delivered in
raw format (digitally signed) to the Customer.
4.1.1.2

smartBridge Installation Bundle

The smartBridge application package will be delivered in transports that need to be installed
on the Solution Manager machine or an NW2004s base system. Please follow the
instructions and the sequence the transports have to be installed.
The application installation can proceed in parallel, even without a license key. The key will
be required in order to complete the registration and configuration steps.

4.1.2

smartBridge Plug-In Installation

The smartBridge plug-in will work with the following system landscape:

Release 4.6 (requires minimum 4.6c Patch 46)

Release 4.7

Release 7.0

Depending on which systems the customer wants to run the analysis, separate Plug-Ins are
available for installation.

4.1.3

Namespaces to be analyzed

The smartBridge considers per default the standard namespaces Z* and Y*. Additional
namespaces need to be specified sepparately.
Within each namespace definition, the current delivered system may consider up to 120
predefined object types. Per request different object types can be considered during the
analysis.
Please note: if a new object type is needed, please let us know so we can implement and
enable that.

smartShift, 2009
Private and confidential
All rights reserved

Page 11 / 15

[ smartTools Project Preparation - Prerequisites ]

4.2

Installation of smartShift Analyzer and smartShift Transformer

The smartShift Analyzer and smartShift Transformer for SAP can be used in one of the
following ways:
i.

Over a remote, local network or VPN connection, from a smartShift laptop with preinstalled smartTools
Over a customer network connection, from a local/customer workstation (PC), where
the smartShift Tools for SAP will be installed.

ii.

In case (i) both smartShift Analyzer and smartShift Transformer will already be installed.
Only the connectivity needs to be set up and tested as defined in the previous chapters.
In case (ii), the installation of the smartShift Analyzer and smartShift Transformer is
performed by a smartShift resource. Administration rights on the local/customer PC will be
required.

5 Technical Prerequisites
5.1

Source System Preparation

The proper extraction of source code via smartBridge requires that the source system be
properly indexed from a technical viewpoint. In order to do so, a number of batch jobs are
provided by SAP to ensure consistency:

EU_INIT

EU_PUT

EU_REORG

5.1.1

Running the EU_INIT Job

You must execute the EU_INIT job in full prior to operating the Extractor. The EU_INIT job
rebuilds the indices, and can require from 8 to 24 hours to complete, depending on the size
of custom objects, system bandwidth, etc. The EU_INIT job submits the SAPRSEUI
program, which in turn indexes all customer-defined programs.
Optionally, SAPRSEUI may be executed as a background job. The following parameters
are REQUIRED in order to properly execute the program:
Program Name = *
Development Class = *
Selection Type = CLIENT
This will ensure all Customer development objects are Indexed.
Important: The SAPRSEUI job may fail if it encounters syntax errors within a program. If
this occurs, re-start the job; it will start at the next program. You should do this as often as
necessary until the job completes.

smartShift, 2009
Private and confidential
All rights reserved

Page 12 / 15

[ smartTools Project Preparation - Prerequisites ]

5.1.2

Running the EU_PUT and EU_REORG Jobs

You must also ensure that the EU_PUT and EU_REORG jobs, which update the indices for
the ABAP workbench, are running regularly. Please refer to SAP OSS note 18023 for more
details.
5.1.3

Monitoring Progress

You can check the progress of each in job log in SM37. The EU_INIT job writes a log entry
at every 1000 objects using the object key as a reference.
The basic jobs EU_PUT and EU_REORG should also be running regularly.
Please see SAP OSS note 18023 for more details.

5.2

Database Backups

To ensure maximum flexibility and quick turnaround during the iteration, it is required that
database backup and restore mechanism is available and used during the transformation
phase. This ensures, that the different versions of the modified code do not unnecessarily
accumulate and thus posing additional load to the database storage. It also ensures that
each transport is clean and builds on the original version.

smartShift, 2009
Private and confidential
All rights reserved

Page 13 / 15

[ smartTools Project Preparation - Prerequisites ]

6 Appendix 1 - Minimum HW and SW requirements

6.1

6.2

Minimum HW Requirements
-

Windows XPsp2 or later

Min. 2GB Memory

Min. 2GB available local disc space

Dual Core Processor

CD / DVD Drive

USB

LAN

Minimum SW Requirements

Administrative rights are needed in order to install software.

The following will be installed if not already available.
- Java JDK 6 (latest version http://java.sun.com)
PostgreSQL 8.X
- Customer needs to have SAPs Java Connector 2.1.8 available (if not already
installed). Further details can be found under http://service.sap.com/connectors
- Archiving Tool (e.g. WinZip, WinRAR, 7-zip)
- UTF-8 capable editor

smartShift, 2009
Private and confidential
All rights reserved

Page 14 / 15

[ smartTools Project Preparation - Prerequisites ]

7 Appendix 2 smartShift Tools Overview

The following graph provides an overview of the smartShift source code analysis and source
code transformation and the involved tool set:

smartBridge is based on plug-in technology and consists of two components: the

smartBridge application installed on a Solution Manager or a Netweaver 2004s base system
and the smartBridge plug-in, residing in the SAP system during the analysis. The plug-in
identifies all the sources on an object level that are relevant to be analyzed when performing
an upgrade and/or Unicode project.
The sources are downloaded by the smartShift Analyzer for SAP (a component outside the
SAP system), where the actual analysis is performed on a source code level. The rulebased engine is preconfigured to detect all known violations and recommends solutions.
Through a configurable table, smartShift is able to simulate the expected outcome. A built-in
code viewer allows immediate comparison with the original ABAP sources to assess the
expected results of the conversion. The tool-based modifications in the ABAP code are
categorized to evaluate the level of automation that can be achieved during an upgrade
and/or Unicode project. Various reports and statistics are generated to provide a detailed
view of the effort to perform the changes in the coding to be compliant with SAP coding
standards.
Based on the source code analysis smartShift Transformer for SAP automates the entire
process of converting the in-house extensions and enhancements according to the
requirements of the customer.

smartShift, 2009
Private and confidential
All rights reserved

Page 15 / 15