Fritz MosonyiFritz Mosonyi SAP Upgrade Analysis – Procedures and Results

11/25/2008 by Fritz Mosonyi

In reply to numerous inquiries, I would like to take the opportunity to describe, in greater detail, the SAP Upgrade analysis using IntelliCorp LiveCompare.

Analysis Procedure

We usually establish an upgrade analysis as a small-scale project in which the customer receives specific, clearly defined reports. The typical project has a duration of under two weeks, while the time required by our consultants is no more than four days, with an additional half-day to three days for work done internally at the customer’s location.

The “project” consists of three phases

  • Phase 1: Definition and clarification of the content. Using sample reports and the customer’s requirements, every single report (including its contents and usefulness) is thoroughly discussed and defined
  • Phase 2: The analysis is performed
  • Phase 3: A concluding presentation, followed by a discussion of the results with project management

Analysis Results

I should again emphasize that the analysis can be performed before the actual input takes place.
The following list of reports is provided for example purposes and in actual situations, is nearly always tailored to the customer’s needs.

Degree of Utilization

Utilization ratio analysis is conducted according to application areas, transactions and request frequency.

Used/Obsolete Transactions

This report shows all the currently used transactions that either no longer exist on the target release or that SAP has deemed obsolete.

Unused Custom Code

This contains a list of all in-house developments executable by the end user; or, in other words, the transactions and programs that have not been used.

Standard Transactions Used

This contains all the standard transactions used, and it indicates the changes in their “dynpros.” This is a direct reference to the changes to be expected from a test or the end user’s perspective. (Dynpros are the definitions of the screen masks in the SAP GUI).

User Location Analysis

Usage analysis is based on the user’s location. Also included is data such as the division and personnel department.

Impacted Profiles and Authorizations

This report contains a list of all the profiles used, providing a comparison of the associated objects in the source and target systems.

Customized and Used Standard IDocs

An analysis of the used IDocs is performed in order to determine which IDocs must be adjusted according to the input.

New SAP Transactions

This contains all new SAP transactions along with a description, the development class and module affiliation.

RFC – Remote Function Calls

The SAP workload records outside access via RFC, in addition to normal user interaction. These logs are direct indicators to external interfaces. The resulting report compares the retrieved function modules between the two systems.

Custom Code Impact

The Custom Code Impact Report indicates all the relevant changes that have been made to the SAP standard objects used for in-house development.

UNICODE Syntax Check

This provides a complete syntax check of the in-house developments. The procedure and result are very similar to those of UCCHECK, but this check can also be performed on SAP releases 46c and down (!) while UCCHECK is available only after the upgrade. This is an essential report if you are using an SAP release less than 4.7 and must perform a Unicode conversion simultaneously with the upgrade (because you are using MDMP, for example).

Interface Programs Impact

To generate this report, all the in-house developments are browsed according to “call transaction” requests. The parameter, meaning the accessed transaction, is then compared between the two systems.

ABAP Impact

This scan contains a series of ABAP statements that could cause problems for upgrades from 46c and below to 4.7 and above.

BAPI

Using the ABAP impact scan result, all “BAPI*” call function locations are further processed in order to generate this report. The found and accessed BAPIs are compared between the two systems with respect to their coding.

About the author:
Fritz Mosonyi is a senior consultant and division head for SAP tools at SPP Vienna, a beteo partner.

Sphere: Related Content

No TweetBacks yet. (Be the first to Tweet this post)