Information Request for SAP Project Proposal · 2020. 4. 1. · transaction DB02 screenshots. See Capturing Data Growth History on page 9 for details. To understand how data is being

[email protected] | http://www.smartShiftTech.com v20200327 COPYRIGHT © 2020 SMARTSHIFT TECHNOLOGIES. ALL RIGHTS RESERVED.

Information Request for SAP Project Proposal

Contents

Overview of Information Request........................................................................................... 1

System Details ....................................................................................................................... 1

Technical Information ............................................................................................................. 1

Gathering System Details ........................................................................................................ 2

Obtaining a Count of Custom Objects ................................................................................... 2

Identifying database table schema ........................................................................................ 4

Capturing Data Growth History .............................................................................................. 9

Capturing Data Usage ............................................................................................................ 9

Collecting Technical Information ......................................................................................... 11

Requirements for Current SAP Systems ............................................................................. 11

Requirements for Older SAP Systems ................................................................................ 11

mailto:[email protected]

http://www.smartshifttech.com/

smartShift Technologies Information Request for SAP Project Proposal

[email protected] | http://www.smartShiftTech.com/ COPYRIGHT © 2020 SMARTSHIFT TECHNOLOGIES. ALL RIGHTS RESERVED.

1

Overview of Information Request

As part of our initial customer engagement, smartShift requests information contained in your

SAP systems (as outlined in this document) to gain a better understanding of your environment.

Providing this information allows us to prepare a more accurate proposal for your SAP project.

System Details

smartShift requires basic information for your SAP systems as outlined below:

To obtain a count of custom objects (a.k.a., ‘Z’ objects), we request you provide information

from table TADIR. See Obtaining a Count of Custom Objects on page 2 for details.

To identify tables being used and their footprint, we request you execute RSTABLESIZE

and provide us with the report. See Identifying database table schema on page 4 for details.

To understand how data has been growing in your systems, we request you provide

transaction DB02 screenshots. See Capturing Data Growth History on page 9 for details.

To understand how data is being used in your systems, we request you provide one of the

following options depending on what you have available on your systems:

a. ST03N transaction data (from your ECC system) with collection time range of ideally

> 1 year – Good option

b. UPL logs (from your Solution Manager system) – Better option

c. SCMON transaction (from your Solution Manager system) – Best option

See Capturing Data Usage on page 9 for details.

Technical Information

smartShift also requires technical information that will depend on the state of your SAP systems.

If your systems are running current versions (up-to-date), we request you provide:

a. SAP Readiness Check 2.0

b. DBACOCKPIT transaction screen shots

OR, if your systems are running older SAP versions and you cannot provide SAP Readiness

Check 2.0, we request you provide:

a. Early Watch Report (for each SAP system in scope)

b. HANA sizing Report

c. ST06 OS information screen shots

See Collecting Technical Information on page 11 for details.





2

Gathering System Details

smartShift requires basic information for your SAP systems such as a count of custom objects,

table schema, data growth pattern and overall usage analysis. Customers must perform each of

the procedures outlined in this section to gather system details.

Obtaining a Count of Custom Objects

Pre-assessment of your SAP systems requires that we obtain a scoping level count of main

objects. This information can be collected via a simple ABAP query (TADIR), as shown below.

Usage analysis details for your systems can be generated in the form of data files from either

ST03N transactions (for ECC) or UPL/SCMON logs (for Solution Manager).

Data provided in your usage analysis must span a reporting period of at least one year to

include critical functions that take place monthly, quarterly and annually (e.g., financial closings).

To execute TADIR:

1. List the #entries from table TADIR with Z*, Y* or ‘Customer Namespace’* as prefixes,

excluding $TMP, deleted and generated objects and filtering for object types PROG,

FUGR, CLAS = #main objects.

2. Optional. Dump table TADIR with Z*, Y* or ‘Customer Namespace’* as prefixes,

excluding $TMP, deleted and generated objects. Share object list as an MS Excel file.

In OBJECT field – Add PROG,

FUGR, CLAS filters to list Object

Types in standard package

In OBJ_NAME field – Add Z*, Y*,

/<CustomNameSpace>/*

Exclude:

• Local Objects

• Generated Objects

• Deleted Objects

Click Number of Entries button to

determine Object Count





3





4

In this screen… (John, we didn’t get to replacing this screen. What do you want to say here?)

Identifying database table schema

ECC systems contain a standard SAP program – RSTABLESIZE – that smartShift relies upon

during its pre-assessment to learn which database tables are being used by your system. This

program does not extract any business data, nor does it extract data from your tables. It simply

reports on the number of records found and the approximate size of each table in your system.

Keep in mind that this program does NOT change any data in your system.

smartShift recommends that your system administrator execute this program as a background

job, writing its output to a spool file which can then be downloaded, zipped and sent to your

smartShift Account Representative to fulfill this database requirement.

Runtime of this program varies significantly as it depends on your system size and how well the

database has been maintained. We have seen this program run from 30 minutes to 48 hours.

Please allow the program to complete execution as it will not harm your system.

If you have any questions about running this program or how smartShift uses information in the

generated report, contact your smartShift Account Representative.





5

To execute RSTABLESIZE:

1. Execute transaction SE38/SA38 or SE80 and execute program RSTABLESIZE.

2. Specify execution parameters.





6

3. Execute program as background job.





7

4. Use transaction SM37 to ensure job is running (and to monitor job).

5. When job is complete, call spool, select list and export/download results.





8

6. Zip and send results to your smartShift Account Representative.





9

Capturing Data Growth History

To understand how data has been growing in your system, we request you provide transaction

DB02 screen shots as shown below.

[Insert Screens]

Capturing Data Usage

To understand how data is being used in your system (a.k.a., ‘Usage Analysis’), we request you

provide screen shots as shown below.

Sample ST03N transaction data (with collection time range of ideally > 1 year) from your ECC system:

[Insert screens]





10

Sample UPL logs (from your Solution Manager system):

[Insert screens]

Sample SCMON transaction (also from your Solution Manager system):

[Insert screens]





11

Collecting Technical Information

smartShift also requires technical information that will depend on the state of your SAP systems.

Technical information can be provided in the form of transaction results, reports or screen shots.

Requirements for Current SAP Systems

• SAP Readiness Check 2.0. Instructions for generating: www.sap.com/readinesscheck

• DBACOCKPIT database transaction screen shots (samples shown on page 12)

Requirements for Older SAP Systems

• Early Watch reports for each SAP system in scope for your transformation

• Indication of whether each SAP system has been Unicode-Enabled

• HANA Sizing Report. Instructions for running this report (requires login):

/SDF/HDB_SIZING report (https://launchpad.support.sap.com/#/notes/1872170)

• ST06 operating system information screen shots (samples shown on page 13).



http://www.sap.com/readinesscheck

https://www.google.com/url?q=https://launchpad.support.sap.com/%23/notes/1872170&sa=D&source=hangouts&ust=1579897715863000&usg=AFQjCNGtUfzRjgBEKF7zkcD2bwNVqxIxWg



12

Sample DBACOCKPIT database transaction screen shots:





13

Sample ST06 operating system information screen shots:



Documents

Information Request for SAP Project Proposal · 2020. 4. 1. · transaction DB02 screenshots. See Capturing Data Growth History on page 9 for details. To understand how data is being