IBM SAP Upgrade Explorer Tool _SUET_ v1.6.2 - Readme

Page 1 of 9 IBM Copyrighted Materials © Copyright IBM Corporation 2009

IBM SAP Upgrade Explorer Tool VVeerrssiioonn 11..66..22

Revisions

Version # Date Author Description

1.6.1 14-Aug-09 Nilay Ghosh Captures new features as mentioned in detail under the release notes section of this document.

1.6.2 27-Oct-09 Anjan Nandy Added Summary section regarding SUET tool can be executed on R3 system 4.6C ( support pack SAPKA46C38, SAPKB46C13) or higher version of R3 system only. Fixed problem of internal memory overflow to retrieve usage information of workflow. The usage of workflow is restricted by date range parameter. Added Authorization to run the tool in a system.

IBM SAP Upgrade Explorer Tool (SUET) v1.6.2


1. Summary The IBM SAP Upgrade Explorer Tool (SUET) is designed to produce Summary, Detail, and Estimation reports that assist IBM in accurately estimating a client’s SAP upgrade from SAP R/3 4.6C, 4.7(Enterprise), ECC 5.0 and ECC 6.0. All reports, transactions, and code is read-only. It should be installed in the Production system or in the Quality system via standard SAP transport mechanism. The reports may be useful for a SAP client; however, they were designed to be analyzed by IBM’s SAP Upgrade Factory. SUET works on both Unicode and non-Unicode systems. It is installed and un-installed via standard SAP transports. It should be installed in your Development system and transported via your standard SAP transport mechanism into your Production system. All reports, transactions, and code is read-only. To date, SUET has only been tested on R/3 4.6C, R/3 4.7 (Enterprise), ECC 5.0 and ECC 6.0. New versions of SUET are being developed with additional functionality. Please contact IBM for further information. All information, code, and documentation in SUET is copyrighted to IBM. SUET is free for use by IBM clients and IBM potential clients. SUET may not be copied, decompiled, reverse-engineered or used in part or in entirety in a non-specified manner without the written consent of IBM.

2. System Requirement

IBM SAP Upgrade Explorer Tool (SUET) runs on SAP R3 system 4.6 C support pack SAPKA46C38, SAPKB46C13 or higher. It is also recommended to close Microsoft Excel application before running the tool as it may sometime cause error while generating the report.

3. Release Notes for Version 1.6.2 This section describes the version specific features.

• Introduced Authorization to run the tool in a system. User should have role , ZIBM_SUET_EXECUTION, to execute the tool.

• Custom Development tab has been enhanced with the details (marked in blue) available as separate columns: A. Object Type B. Object Type Description C. Object Name D. Object Description E. Package F. Package Description G. Application H. Application Description I. Source System J. Object Version K. Created On L. Last Changed By M. Last Changed On N. Last Transport O. Last Transport Date P. Lines of Code



Q. Release Impact (Warning) – Determines the number of release specific syntax errors R. Unicode Impact (Error) – Determines the number of unicode specific syntax errors S. Obsolete Count (Warning) – Determines the number of obsolete syntax warnings T. Obsolete FM Count(Warning) - Determines the number of Obsolete FM used warnings U. Used – Value ‘X’ in this column denotes that the object has been used during the period

specified in the selection screen. This includes the object used as per ST03N statistics,programs inculded in batch job and also the linked objects with programs of ST03N statistics and batch job.

• Languages Installed tab has been enhanced with the details (marked in blue) available as separate columns: A. Language Key B. Language specifications C. Degree of Translation D. Lang. (ISO 639) E. Language F. Codepage – Captures the used codepages for installed languages in the system

• Summary Report tab has the information about system setting for “Statistical Data Retaintion”: One new Row has been added for Statistical Data Retained For Months

• SAP Version Info tab has been enhanced with the details (marked in blue) available as separate columns: A. Software Component B. SAP Release C. SAP SupportPackLevel D. Component Type E. Component Type Text – Captures the description of the component type F. Short Description of Software Component

• Custom Table details tab has been enhanced with the details (marked in blue) available as separate columns: A. Table Name B. Field Name C. Key ? D. Data Element E. Check Table F. Domain G. Data Type H. Length I. Decimal Pl J. Description K. Function Group

• Custom View details tab has been enhanced with the details (marked in blue) available as separate columns: A. View Name B. Field Name C. Data Element D. Domain E. Data Type F. Length G. Decimal Pl H. Description I. Function Group



• A new column (marked in blue) has been added to Transaction Statistics and Program Statistics tab to capture the number of times the objects are been executed during the period specified in the selection screen: L. Type M. Name N. Count

• A new column (marked in blue) has been added to standard workflow and custom workflow tab to capture the number of times the workflow object has been used: A. Obj Type B. Object ID C. Description D. Usage Count ( As per given date range of work flow in input screen)

• Two new rows has been added to Hardware Platform tab to capture allocated database size and available free space.

• A new tab named User Info has been added to capture the following details about SAP clients and users in each of them: A. Client B. Client Name C. User Name D. User Type E. User Type Description

• A new tab named Scheduled Jobs With Cust Prog has been added to capture the following details of scheduled job that has Custom programs associated: A. Scheduled job name B. Program name C. Variant

• A new tab named Gateway Connections has been added to capture the following details: A. Connection Numb B. Logical Unit C. Transaction pro D. Gateway User E. Connection Status F. Symbolic Destin ation G. Conversation ID H. Client Log I. Fast/slow Connection J. Work Process Number K. General Counter L. CPIC Return Value M. CPIC Return Value N. Last Reqest Time O. Gateway Fill By

• A new tab named Server Info has been added to capture the following details: D. Server Type E. Server Name F. Host

• A new tab named Run Info has been added to capture the details of the system details and selection screen parameters



• In earlier version module pool programs which are not to transaction code were not being captured in the Prog in Appl tab. The bug is now fixed and the same information is now being captured in the Custom Development tab. As it was not needed anymore, the Prog in Appl is now removed.

4. Installation Process Ensure that you have authorization for certain transactions (CG3Z, STMS) for executing the steps mentioned below. 1) Upload the files workbench and customizing transports to the application server using

transaction CG3Z in Binary mode. The Datafile should be uploaded to '/usr/sap/trans/data/' and the Cofile should be uploaded to '/usr/sap/trans/cofiles/' . First import workbench request and after that import customizing request.

• Datafile name for workbench request is R903540.ERP and cofile name is K903540.ERP

• Datafile name for customizing request is R903468.ERP and cofile name is K903468.ERP

2) Do the following: a. Go to transaction STMS

b. Click on c. Double click on the row containing the target SAP server d. Click on the “Add” option in menu path - Extras> Other Requests. The following screen will

appear as a popup. Enter the transport name & target client and hit enter. For Workbench request this will be ERPK903540. For customizing request this will be ERPK903468.

e. Click on the “Yes” button on the popup that appears. The transport request number ERPK903540 will appear in the Import Queue. Once this transport is imported successfully, a green light will appear beside the transport.

f. Click on the row containing the transport and click on the button in the tool bar. g. A popup window like the below would appear. Enter the target client, select the options

shown below and click on the button. Click on the “Yes” button if a confirmation popup

appears. A sign will appear next to the transport if it is successfully imported. h. Import options (Choose Target Client according to the client in which the transport is

desired to be imported)



After import of the tool create the role, ZIBM_SUET_EXECUTION, as below. Ensure that you have authorization for certain transactions (PFCG, SU01) for executing the steps.

1) Go to the transaction PFCG and go to menu Role=>Upload .



2) Continue for the information screen appears and select the file, ZIBM_SUET_EXECUTION.SAP, that is distributed along with the installer.

3) Press Ok to load the role in the system.



4) Go to the transaction SU01 to assign the role to the user who will execute SUET tool.

5. Un-installation Process

Just like installer, IBM SUET is uninstalled using the Transport Management System. Please get in touch with a basis consultant to use the files K903531.ERP (cofile) and R903531.ERP (data file) which are included in this package. The transport request for uninstall is ERPK903531. If the tool is transported to multiple systems then this transport must be imported to all the systems to uninstall IBM SUET Tool. Unassign the role, ZIBM_SUET_EXECUTION, from the user in SU01 transaction. After that delete the role from system in PFCG transaction.

6. Issue related to import of tool 1. As per SAP note – 330267, if import is returning with return code 16 and message (“unknown dynpro format. Please contact SAP support”, then it is required to upgrage “R3trans” as per notes 330267. Since the screen format was changed in Release 6.10 so updated “R3trans” program is required to import new screen format.

7. User Guidance

For step by step execution guidance, refer to the powerpoint presentation distributed as part of this documentation.

Documents

IBM SAP Upgrade Explorer Tool _SUET_ v1.6.2 - Readme