Transport Execution Analysis_report.pdf

(1)

SERVICE REPORT

SAP

®

Guided Self Service

Transport Execution Analysis

SAP System ID

PE1

SAP Product

SAP ERP

Release

6.00 DB System

ORACLE

Customer

Processed on SAP Solution Manager Service Center Release EHP 1 for NetWeaver 7.0 Telephone

Service Tool 701_2010_1 SP3 Fax

Date of Session 16.07.2010 Session No. 0000000000000 Date of Report 20.08.2010 Installation No. 0000000000

(2)

1 Table of Contents

1 TABLE OF CONTENTS ... 2 SERVICE SUMMARY ... 4 1.1SUMMARY ...4 1.2ACTION PLAN ...5 1.3SYSTEM HISTORY ...6

1.4SYSTEM SIZE INDICATORS ...6

1.5CHANGE MANAGEMENT INDICATORS ...6

1.6KEY PERFORMANCE INDICATORS...6

2 CUSTOM CODE MAINTAINABILITY ... 8

2.1MODIFIED OBJECTS IN THE SYSTEM ...8

2.2CUSTOMER OBJECTS IN THE SYSTEM ...9

2.3USAGE STATISTICS ... 10

2.3.1 Top 20 Transactions by Dialog and Background Steps ... 10

2.3.2 Number of Transactions and Reports in Use ... 10

3 SAP SOFTWARE MAINTENANCE ... 12

3.1AGE OF SUPPORT PACKAGES ... 12

3.2CONSISTENCY OF SAPSUPPORT PACKAGES ... 13

3.2.1 Import History ... 13

3.3SAPNOTES ... 14

3.4CONSISTENCY OF SAPNOTES ... 15

3.5BUSINESS FUNCTIONS ... 20

3.6CONSISTENCY OF BUSINESS FUNCTIONS ... 20

4 SYSTEM LANDSCAPE AND TMS SETTINGS ... 22

4.1USAGE OF THE SAPTRANSPORT MANAGEMENT SYSTEM ... 22

4.2TRANSPORT ROUTES ... 22

4.3TRANSPORT MANAGEMENT TOOLS ... 22

4.4CLIENT STRATEGY ... 23

4.4.1 Clients in Development System... 23

4.4.2 Clients in Quality Assurance System ... 24

4.4.3 Clients in Production System... 24

4.5SYSTEM CHANGE OPTIONS ... 24

4.5.1 System Change Options - Current Values ... 24

4.5.2 Change Option Log ... 25

5 TRANSPORTS ... 27

5.1NUMBER OF TRANSPORT REQUESTS IN THE ANALYSIS PERIOD ... 27

5.2NUMBER OF OBJECTS IN TRANSPORT REQUESTS ... 27

5.3RELEASE CYCLES ... 28

5.4SOURCE SYSTEMS OF TRANSPORT REQUESTS ... 29

5.5TRANSPORT REQUESTS IN PRODUCTION ... 29

5.6MOST FREQUENTLY CHANGED OBJECTS IN THE ANALYSIS PERIOD ... 30

5.7IMPORT ERRORS ... 31

(3)

Table of Contents

5.7.2 Most Frequent Transport Errors ... 32

5.8TIME PROFILES FOR IMPORTS ... 35

5.8.1 Imports per Weekday ... 36

5.8.2 Imports per Month ... 37

6 TESTING AND RUNTIME ERRORS ... 38

6.1TESTING TIME ... 38

6.2REFRESH OF THE QUALITY ASSURANCE SYSTEM ... 39

6.3NUMBER OF RUNTIME ERRORS PER DAY ... 39

6.4TYPE OF RUNTIME ERRORS ... 40

7 TRANSPORT LANDSCAPE CONSISTENCY ... 41

7.1TRANSPORT TRACKING ... 41

7.1.1 Requests Deleted from the Queue of QAS ... 41

7.2OPEN TRANSPORT REQUESTS IN DEVELOPMENT ... 42

7.3PARKED TRANSPORT REQUESTS ... 42

7.4TRANSPORT SEQUENCE VIOLATIONS ... 43

8 APPENDIX ... 45

8.1BEST PRACTICES IN TRANSPORT MANAGEMENT ... 45

8.1.1 Release Management ... 45

8.1.2 CTS projects... 45

8.1.3 Preliminary Transports ... 45

8.1.4 Transports of Copies ... 45

8.1.5 Critical Object Approval ... 45

8.2SOFTWARE CHANGE MANAGEMENT FEATURES IN SAPSOLUTION MANAGER ... 45

8.2.1 Change Request Management... 45

8.2.2 Quality Gate Management ... 46

8.2.3 Enhanced Change and Transport System (CTS+) ... 46

(4)

Service Summary

During this Transport Execution Analysis service, we detected

severe problems that may cause you to lose business. We

recommend that you take corrective action immediately. If you

would like further information, create a customer message in

component SV-BO.

(Note: All recommendations provided in this report are based on our general experience only. We advise you to test our recommendations before using them in your production system.)

OVERVIEW OF RATINGS

Rating Check Performed

Custom Code Maintainability SAP Software Maintenance

System Landscape and TMS Settings Transports

Testing and Runtime Errors Transport Landscape Consistency

1.1 Summary

The Transport Execution Analysis service was performed for your production system PE1 with development system DE1 and quality assurance system QE1. Transport requests from 01.01.2010 to 30.06.2010 were analyzed. The purpose of this session was to check the general status of your system PE1 with regard to change management and also to make recommendations for further improving stability.

This report was rated RED due to the following factors that could impact the stability and availability of the production system:

- There are SAP notes with an inconsistent implementation status in your DEV, QAS and PRD system. - Some transport requests have been deleted from the import queues.

- The Support Package level is not up to date.

- The client change options have not been set up correctly.

- Transport requests are imported continuously into production. No release or maintenance cycles are in place. - We have detected several transport sequence errors in the analysis period.

We have also identified some areas of concern that must be addressed as soon as possible: - There is a large number of modified SAP standard objects in the system.

- There is a large number of customer objects in the system. - Some objects have been changed frequently in production.

- Many transport requests spend less than one day in the quality assurance system.

- The production system was not copied to the quality assurance system within the last 12 months.

These issues and additional minor issues are explained in this report. Some of the subsections could be rated RED even if the main section was rated YELLOW; this indicates that although the check is critical, it might not impact the overall stability and availability of the system. A short description of the main actions and recommended SAP services is provided in the Action Plan below.

(5)

Service Summary

1.2 Action Plan

Number Priority Issue Recommended action When to do See

section 1 Very

High

There are SAP notes with an inconsistent implementation status in your DEV, QAS and PRD system.

Check the SAP notes with an inconsistent implementation status. Download and implement the latest versions in DEV and transport them to all systems in the landscape.

Immediately 3.3

2 Very High

Some transport requests have been deleted from the import queues.

Do not delete transport requests from the import queues. If a transport request contains an error, it should be backed out by a correction transport. Both transport requests should then be imported together into production.

Ongoing 7.1.1

3 High The Support Package level is not up to date.

Import Support Package stacks at least once a year.

Next few months

3.1

4 High The client change options have not been set up correctly.

Change the client change options according to our recommendations.

Immediately 4.4

5 High Transport requests are imported continuously into production. No release or maintenance cycles are in place.

Transport requests should be bundled in release and maintenance cycles. See the detailed explanations in chapter 5.3.

Next few months

5.3

6 High We have detected several transport sequence errors in the analysis period.

Analyze the transport sequence errors and try to avoid them in the future. All transport requests should be imported in the same sequence as they were exported from the development system. Make sure by organizational means that the transports are released and transported in the right sequence. Transports should only be released by lead developers and after a stringent approval process.

Next few weeks 7.4

7 Medium There is a large number of modified SAP standard objects in the system.

Check if SAP Enhancement options can be used instead of modifying the SAP standard.

2.1

8 Medium There is a large number of customer objects in the system.

Check if new business requirements can be fulfilled within the SAP Standard or in future SAP Releases before you start a custom development project.

2.2

10 Medium Some objects have been changed frequently in production.

Improve the development specifications and introduce mandatory testing procedures in order to avoid continuous adjustments of objects in production.

Next few weeks 5.6

11 Medium Many transport requests spend less than one day in the quality assurance system.

Introduce mandatory testing procedures. Make sure that changes are tested sufficiently before they are moved into production.

Next few weeks 6.1

12 Medium The production system was not copied to the quality assurance system

Refresh the quality assurance system regularly by copying the production system.

Next few months

(6)

1.3 System History

SYSTEM HISTORY

Step Target Release Date

1. Installation 28.06.2007

2. System Copy PE1 -> QE1 700 23.07.2009

1.4 System Size Indicators

The following performance indicators show the system size and performance. The data was extracted on 16.07.2010 and contains statistics for the last complete month.

Indicators Value

Logged on Users (last month) 1288

Transactions and Reports in Use (last month) 3164

1.5 Change Management Indicators

The table shows the relevant change management indicators that were calculated during this service session.

Area Indicator Value

System Modification Level Workbench Requests since System Installation 10770 Customizing Requests since System Installation 6988

Customer Objects 6454

Modified Objects 356

Transports in Analysis Period

Average Number of Transport Requests per Month 227

Owners of Transport Requests 17

Problem Indicators Errors during Transport in Production in Analysis Period 27 Average Number of ABAP Dumps per Day (data only available for a shorter period)

102 Transport Sequence Violations in Analysis Period 12

1.6 Key Performance Indicators

The table shows the Emergency Changes and Failed Changes during the analysis period.

KPI Description Value

Transport requests in analysis period

Total number of transport requests imported in production 1361

Transports in Production Transports created in production 2

Transports with short transition time

Transports with a transition time from DEV to PRD shorter than 1 day.

461 Amount of Emergency Changes Ratio between emergency changes and transport requests imported

into Production in the last six month.

34.02% Total number of objects in

workbench requests

Total number of objects in workbench requests 3432 Import errors Number of failed object changes due to technical transport errors 27 Transport sequence errors Number of objects which were overwritten by older version 10 Frequently changed object

versions

Number of objects with 4 or more versions in analysis period 16 Amount of Failed Changes Ratio between failed changes and Imported Objects in Workbench

Requests

(7)

(8)

2 Custom Code Maintainability

This chapter was rated YELLOW. The reason for this rating can be found in

the overview section below:

Modified Objects in the System Customer Objects in the System Usage Statistics

2.1 Modified Objects in the System

We have counted the number of modified objects in your systems. These are changes to SAP standard objects. We count on sub-object level. If for example three function modules within one function group are modified we count three objects. Modifications that are caused by implementing an SAP Note with the Note Assistant and translations are not listed. Also modified objects in the customer or partner name range are not listed. We have introduced the following object types:

- Coding: programs, includes, function modules, etc

- Data Dictionary: Tables, structures, indexes, data elements, domains, … - Text: Messages, documentation, report texts, …

- Other: All other object types

The following table lists the modifications by application component and by object type. COMPONENTS WITH MOST MODIFICATIONS

Application Component Description Coding Data Dictionary Text Others Sum

FI-LOC Localization 21 54 1 7 83

SD-MD-CM Conditions 47 4 0 0 51

CO-PC-ACT Actual Costing/Material Ledger 13 20 4 0 37

SD-SLS Sales 12 1 0 2 15

LO-MD-MM Material Master 1 7 1 3 12

SD-MD-MM Material Maintenance 9 0 0 0 9

MM-PUR Purchasing 0 6 0 2 8

PP-SFC Production Orders 4 3 0 0 7

LO-MD-BOM Bills of Material 2 5 0 0 7

CO-OM-CCA Cost Center Accounting 2 0 0 4 6

MM-IM Inventory Management 1 4 1 0 6

CO-PA Profitability Analysis 2 2 0 2 6

FI Financial Accounting 2 3 0 1 6

PP-BD-RTG Routing 1 5 0 0 6

FIN-FSCM-TRM-TM Transaction Manager 5 0 0 0 5

SD-BIL Billing 3 2 0 0 5

CO-PC-PCP Product Cost Planning 2 1 0 1 4

CA-FIM-FMA Financial Mathematics 1 3 0 0 4

EC-PCA-BS Basic Settings 0 0 0 4 4

(9)

Custom Code Maintainability

Application Component Description Coding Data Dictionary Text Others Sum

Other 27 39 0 5 71

Total 155 163 7 31 356

Evaluation

There is a significant number of modified objects in the system. A high number of modifications could cause a lot of effort for adjustment when upgrading or applying Support Packages. Therefore, it is a good practice to avoid modifying standard SAP code.

Recommendation

A significant number of modifications causes high costs for continuous software maintenance and requires a significant amount of adjustment effort during solution transition events such as an upgrade or Support Package implementation. Therefore, the number of modifications should be limited. Analyze the existing objects and check whether they are still used. During the solution transition event in particular, an analysis should be carried out to determine whether modifications or customer objects can be replaced by SAP standard functionality. In some cases, they can be avoided by using SAP's standard enhancement technology. New modifications or customer objects should only be allowed in unavoidable cases and after a restrictive approval step.

Before modifying the system, you should investigate whether customizing and personalization or implementing user exits and Business Add-Ins (BAdIs) can fulfill your requirements.

2.2 Customer Objects in the System

We have counted all objects in the customer name range. We count on main-object level. For example one function group with three function modules is counted as one customer object.

We have introduced the following object types: - Coding: transactions, programs, function groups, ... - Data Dictionary: Tables, data elements, domains, ... - Other: All other object types

The following table lists the number of objects per development class and object type. CUSTOMER OBJECTS

Development Class Description Coding Data Dictionary Others Sum

ZDES Class DES 2247 1626 385 4258

ZLF Fiscal book 423 841 54 1318

Z_141 ABAP - 141 391 232 35 658

ZKFBC Class ZKFBC 63 123 20 206

ZPROC PROC 5 0 0 5

$TMP Temporary Objects (never transported!) 1 1 2 4

Z001 Customer development class 2 2 0 4

ZLF_TMP Temporary 1 0 0 1

Total 3133 2825 496 6454

Evaluation

There is a significant number of objects in the customer name range. This shows that you often develop your own applications instead of using the SAP standard functionality. A large number of customer objects could cause a lot of effort for adjustment when upgrading or importing Support Packages. It is a good practice to customize SAP standard functionality instead of making customer-specific developments. Recommendation

A significant number of custom-developed objects causes high costs for continuous software maintenance and a lot of effort for adjustment during solution transition events, such as upgrade or Support Package implementation. Therefore, the number of custom-developed objects should be limited. Analyze the existing objects and check whether they are still used. During a solution transition event in particular, an analysis should be carried out to determine whether modifications or customer objects can be replaced by SAP standard functionality. In some cases, they can be avoided by using SAP's standard enhancement technology.

(10)

Background:

You can use of the Custom Development Management Cockpit in order to analyze your custom code in more detail. This tool is part of the SAP Solution Manager Enterprise Edition. Check SAP notes 1243233 - Information about Custom Development Management Cockpit and 1244713 - Installation of Custom Development

Management Cockpit for further details.

2.3 Usage Statistics

2.3.1 Top 20 Transactions by Dialog and Background Steps

The following table shows the transactions that have been used most frequently during the last month. TOP 20TRANSACTIONS BY DIALOG AND BACKGROUND STEPS

Transaction / Report Description # Steps

SE11_OLD ABAP/4 Dictionary Maintenance 2454

CNV_CDMC Custom Develop. Management Cockpit 2219

SE37 ABAP Function Modules 1648

CMOD Enhancements 881

SM37 Overview of job selection 815

ST22 ABAP dump analysis 597

SESSION_MANAGER Session Manager Menu Tree Display 450

SE01 Transport Organizer (Extended) 425

ST13 Analysis&Monitoring tool collection 274

ST14 Application Analysis 274

SE19 Business Add-Ins: Implementations 180

SE09 Transport Organizer 161

STMS Transport Management System 158

SU01 User Maintenance 142

DSA Service Session Workbench 128

SE18 Business Add-Ins: Definitions 116

SE61 R/3 Documentation 116

SE24 Class Builder 101

SEU_INT Object Navigator 77

SE16 Data Browser 75

Evaluation

This table shows the transactions and reports that are used most frequently. Standard test cases that cover these transactions should be available. However, you should also consider other transactions that are not used as often, since these could be highly critical for your business.

You can generate the list in transaction ST03, under workload expand “Total”, then determine the time frame for which the analysis needs to be carried out (daily, weekly, or monthly). Once you have selected the frequency, the number of dialog steps can be seen by clicking “Transaction Profile” under “Analysis Views.”

2.3.2 Number of Transactions and Reports in Use

The following table shows the number of separate transactions and reports that have been used in one week. NUMBER OF TRANSACTIONS AND REPORTS IN USE

Item Number

Transactions and reports in SAP namerange 62

Transactions and reports in customer namerange 0

Transactions and reports with namespace prefix: /* 0

Sum 62

Evaluation

A small number of transactions and reports is in use. This means that a narrow scope of functionality is used in the system. This number is an indicator of the effort of a regression test. For Software Change

(11)

Custom Code Maintainability

Management, this means that all changes are working on a limited set of objects. If there is a large number of changes, there is an increased risk of inconsistencies and dependencies between different transport requests.

(12)

3 SAP Software Maintenance

This chapter was rated RED. The reason for this rating can be found in the

overview section below:

Rating Check Performed Age of Support Packages

Consistency of SAP Support Packages Consistency of SAP Notes

Business Functions

Consistency of Business Functions

3.1 Age of Support Packages

The table below shows the Support Packages applied in your productive system. SUPPORT PACKAGE LEVEL

Component Release Level Highest SP Implemented Shipping Date

CPRXRPM 400 0006 SAPK-40006INCPRXRPM 18.09.2006 EA-APPL 600 0008 SAPKGPAD08 02.02.2007 EA-DFPS 600 0008 SAPKGPDD08 02.02.2007 EA-FINSERV 600 0008 SAPKGPFD08 02.02.2007 EA-GLTRADE 600 0008 SAPKGPGD08 02.02.2007 EA-HR 600 0020 SAPKGPHD20 13.08.2007 EA-IPPE 400 0008 SAPKGPID08 02.02.2007 EA-PS 600 0008 SAPKGPPD08 02.02.2007 EA-RETAIL 600 0008 SAPKGPRD08 02.02.2007 ECC-DIMP 600 0008 SAPK-60008INECCDIMP 26.02.2007 ERECRUIT 600 0008 SAPK-60008INERECRUIT 31.01.2007 FI-CA 600 0008 SAPK-60008INFICA 02.02.2007 FI-CAX 600 0008 SAPK-60008INFICAX 05.02.2007 FINBASIS 600 0008 SAPK-60008INFINBASIS 02.02.2007 INSURANCE 600 0008 SAPK-60008ININSURANC 02.02.2007 IS-CWM 600 0008 SAPK-60008INISCWM 05.02.2007 IS-H 600 0006 SAPK-60006INISH 28.08.2006 IS-M 600 0006 SAPK-60006INISM 28.08.2006 IS-OIL 600 0006 SAPK-60006INISOIL 28.08.2006 IS-PS-CA 600 0006 SAPK-60006INISPSCA 28.08.2006 IS-UT 600 0006 SAPK-60006INISUT 28.08.2006 LCAPPS 2005_700 0003 SAPKIBHD03 26.07.2006 LSOFE 600 0006 SAPK-60006INLSOFE 22.08.2006 PI_BASIS 2005_1_700 0011 SAPKIPYJ7B 10.01.2007 SAP_ABA 700 0011 SAPKA70011 11.01.2007 SAP_AP 700 0008 SAPKNA7008 18.01.2007 SAP_APPL 600 0008 SAPKH60008 02.02.2007

(13)

SAP Software Maintenance

Component Release Level Highest SP Implemented Shipping Date

SAP_BASIS 700 0011 SAPKB70011 24.01.2007

SAP_BW 700 0012 SAPKW70012 11.01.2007

SAP_HR 600 0020 SAPKE60020 13.08.2007

SEM-BW 600 0008 SAPKGS6008 02.02.2007

ST-A/PI 01M_ECC600 0000 SAPKITAR7E 24.03.2010

ST-PI 2008_1_700 0002 SAPKITLRD2 13.04.2010

WFMCORE 200 0006 SAPK-20006INWFMCORE 24.08.2006

Evaluation

The Support Package level for all software components is older than three years. For the component SAP_APPL the latest Support Package level is 8, which has been available since 02.02.2007 and for the components SAP_ABA and SAP_BASIS the latest Support Package level 11 is available since 01.2007. Recommendation

Support Package stacks should be imported at least once a year since outdated Support Packages result in higher maintenance overhead and require more emergency transports moving across the landscape. Schedule a Support Package stack import within the next few months as part your scheduled maintenance activities.

Background

Support Packages should be imported at least once each year. Importing Support Packages provides the following benefits:

- There is a proactive solution to problems that have already been solved for other customers. - Supportability is easier:

* Support Packages might be required to solve a problem. Especially in non-ABAP systems, single corrections with the SAP Note Assistant are not possible.

* Troubleshooting is easier on a current Support Package level since the number of possible root causes is reduced.

* Implementation of an SAP Note often requires the implementation of many dependent SAP Notes if the Support Package level is out of date.

- Support Packages contain the latest legal changes.

- Support Packages are required for implementing Enhancement Packages (new functionality).

3.2 Consistency of SAP Support Packages

The table below shows the software components with a different support package level in your transport landscape.

SUPPORT PACKAGE LEVEL IN THE TRANSPORT LANDSCAPE

Component Release Level in DEV Level in QAS Level in PRD

SAP_BASIS 700 0014 0011 0011

Evaluation

The development system has a higher Support Package level than the production system. This can be due to an ongoing Support Package implementation project.

Recommendation

Import the missing versions and Support Packages to ensure a consistent landscape. Generally, all Support Packages should first be imported in the development system. All systems in the landscape should have uniform components and Support Package levels. Inconsistent components will pose a risk of transport errors, increased maintenance windows, and increased risk of production downtime due to an inability to properly test notes and changes in a production-like environment.

3.2.1 Import History

(14)

SUPPORT PACKAGE STACK IMPORT IN THE TRANSPORT LANDSCAPE

Component Release Level Support Packages Import in DEV Import in QAS Import in PRD CPRXRPM 400 0006 SAPK-40006INCPRXRPM 06.10.2006 29.06.2007 29.06.2007 EA-APPL 600 0008 SAPKGPAD08 03.04.2007 28.06.2007 28.06.2007 EA-DFPS 600 0008 SAPKGPDD08 07.01.2008 07.01.2008 07.01.2008 EA-FINSERV 600 0008 SAPKGPFD08 03.04.2007 28.06.2007 28.06.2007 EA-GLTRADE 600 0008 SAPKGPGD08 02.06.2007 28.06.2007 28.06.2007 EA-HR 600 0020 SAPKGPHD20 16.01.2008 17.01.2008 17.01.2008 EA-IPPE 400 0008 SAPKGPID08 03.04.2007 28.06.2007 28.06.2007 EA-PS 600 0008 SAPKGPPD08 19.12.2007 28.06.2007 28.06.2007 EA-RETAIL 600 0008 SAPKGPRD08 19.12.2007 28.06.2007 28.06.2007 ECC-DIMP 600 0008 SAPK-60008INECCDIMP 03.04.2007 28.06.2007 28.06.2007 ERECRUIT 600 0008 SAPK-60008INERECRUIT 02.06.2007 28.06.2007 28.06.2007 FI-CA 600 0008 SAPK-60008INFICA 19.12.2007 28.06.2007 28.06.2007 FI-CAX 600 0008 SAPK-60008INFICAX 19.12.2007 28.06.2007 28.06.2007 FINBASIS 600 0008 SAPK-60008INFINBASIS 03.04.2007 28.06.2007 28.06.2007 INSURANCE 600 0008 SAPK-60008ININSURANC 19.12.2007 28.06.2007 28.06.2007 IS-CWM 600 0008 SAPK-60008INISCWM 19.12.2007 28.06.2007 28.06.2007 IS-H 600 0006 SAPK-60006INISH 07.01.2008 07.01.2008 07.01.2008 IS-M 600 0006 SAPK-60006INISM 06.10.2006 28.06.2007 28.06.2007 IS-OIL 600 0006 SAPK-60006INISOIL 19.12.2007 28.06.2007 28.06.2007 IS-PS-CA 600 0006 SAPK-60006INISPSCA 06.10.2006 28.06.2007 28.06.2007 IS-UT 600 0006 SAPK-60006INISUT 19.12.2007 28.06.2007 28.06.2007 LCAPPS 2005_700 0003 SAPKIBHD03 06.10.2006 29.06.2007 29.06.2007 LSOFE 600 0006 SAPK-60006INLSOFE 04.04.2007 28.06.2007 28.06.2007 PI_BASIS 2005_1_700 0011 SAPKIPYJ7B 13.03.2007 27.06.2007 27.06.2007 SAP_ABA 700 0011 SAPKA70011 13.03.2007 27.06.2007 27.06.2007 SAP_AP 700 0008 SAPKNA7008 03.04.2007 27.06.2007 27.06.2007 SAP_APPL 600 0008 SAPKH60008 03.04.2007 27.06.2007 27.06.2007 SAP_BASIS 700 0011 SAPKB70011 13.03.2007 27.06.2007 27.06.2007 SAP_BW 700 0012 SAPKW70012 03.04.2007 27.06.2007 27.06.2007 SAP_HR 600 0020 SAPKE60020 16.01.2008 17.01.2008 17.01.2008 SEM-BW 600 0008 SAPKGS6008 05.04.2007 28.06.2007 28.06.2007

ST-A/PI 01M_ECC600 0000 SAPKITAR7E 09.06.2010 09.06.2010 09.06.2010 ST-PI 2008_1_700 0002 SAPKITLRD2 09.06.2010 09.06.2010 09.06.2010

WFMCORE 200 0006

SAPK-20006INWFMCORE

19.12.2007 29.06.2007 29.06.2007

Background

Support Packages should be first applied in the development system, and after appropriate testing transitioned across the landscape. This will give opportunity to resolve issues before moving into production.

For business critical systems it might make sense to import the support packages first in a sandbox system and test the impact on the core business processes there.

3.3 SAP Notes

The table below shows the number of SAP Notes implemented with SAP Note Assistant by component. SAPNOTE ASSISTANT

Components Number of notes implemented with SAP Note Assistant

CO 141

LO 65

(15)

Components Number of notes implemented with SAP Note Assistant

PP 28 BC 17 FIN 16 CA 14 FI 12 MM 9 IS 7 SV 6 LE 3 QM 2 SD 2 PS 1 SRM 1 EC 1 AC 1 Evaluation

360 SAP Notes are applied in your production system with the implementation status “Completely Implemented”.

Background

The SAP Note Assistant is a powerful tool used to implement specific SAP Notes rapidly. The SAP Note Assistant makes it easy to install specific corrections to SAP components. It also recognizes any dependencies of SAP Notes, Support Packages, and modifications that have already been implemented, which helps ensure that you implement all the appropriate fixes for your SAP component. These capabilities make the SAP Note Assistant a useful complement to our support services. For more information, see SAP Note 560756 - Note Assistant Version 1.2: Important notes.

SAP HotNews and SAP TopNotes

SAP HotNews are priority 1 ("very high") SAP Notes that explain how to solve or avoid problems that can cause the SAP system to shut down or lose data. If you are affected by these problems, ensure that you are aware of these SAP Notes.

SAP TopNotes are the most important SAP Notes for a component or subcomponent regarding customer support messages that have been closed successfully. The 10 most successful SAP Notes are selected on a monthly basis using a semi-automatic process, which is described in SAP Note 557703 - FAQ: TopNotes.

You can display and subscribe to SAP HotNews and SAP TopNotes for your area using the "/notes" quick link in SAP Service Marketplace. The joint SAP HotNews and SAP TopNotes personalization interface enables you to create several filters based on the applications you have implemented (for example, SAP R/3 or SAP CRM). Filter maintenance allows you to select the products (for example, SAP R/3), product version (for example, SAP R/3 4.6C), software components (for example, SAP Basis 4.6C), and Support Packages you have implemented. As a result, you see only the SAP HotNews that are relevant to you.

You can also have your SAP HotNews sent to you by e-mail in the SAP Service Marketplace Newsletter. To receive these e-mails, subscribe to the SAP Service Newsletter with the subject "News for Administrator (incl. SAP HotNews)" by making the relevant settings in SAP Service Marketplace under "My Profile." You will be informed automatically as soon as there is a new SAP HotNews that matches your settings.

3.4 Consistency of SAP Notes

In this check, we analyzed the consistency of SAP Notes. The following list contains all SAP Notes that have an inconsistent implementation status in one system or that are not implemented in all systems of the transport landscape.

INCONSISTENT SAPNOTES

SAP Note Implementation Status in DEV Implementation Status in QAS Implementation Status in PRD 36353 Obsolete version implemented Completely implemented Completely implemented 115899 Completely implemented

140573 Obsolete version implemented 156239 Completely implemented

(16)

SAP Note Implementation Status in DEV Implementation Status in QAS Implementation Status in PRD 211324 Obsolete version implemented Completely implemented Completely implemented 352375 Completely implemented

355404 Obsolete version implemented Completely implemented Completely implemented 362135 Completely implemented

377501 Obsolete version implemented Completely implemented Completely implemented 386340 Obsolete version implemented Completely implemented Completely implemented 390738 Completely implemented

631266 Obsolete version implemented 658090 Completely implemented 698122 Completely implemented

735130 Completely implemented

805007 Completely implemented Can be implemented Can be implemented 807001 Completely implemented

936820 Obsolete version implemented Completely implemented Completely implemented 944823 Obsolete version implemented Completely implemented Completely implemented 980213 Completely implemented Completely implemented Can be implemented 986184 Can be implemented Incompletely implemented Incompletely implemented 998194 Completely implemented Completely implemented

998195 Completely implemented Completely implemented Can be implemented 1003894 Can be implemented Completely implemented Completely implemented 1005433 Completely implemented

1009219 Completely implemented 1009374 Completely implemented 1012685 Completely implemented

1013462 Completely implemented Completely implemented

1015050 Completely implemented Completely implemented 1019060 Completely implemented

1022677 Obsolete version implemented Obsolete version implemented Obsolete version implemented 1026604 Completely implemented

1031438 Cannot be implemented Completely implemented Completely implemented 1031612 Cannot be implemented Completely implemented Completely implemented 1032524 Completely implemented

1032547 Completely implemented 1035372 Completely implemented 1036862 Completely implemented 1036943 Completely implemented

1040798 Completely implemented 1040800 Completely implemented 1043129 Obsolete version implemented

1047606 Completely implemented Completely implemented

(17)

SAP Note Implementation Status in DEV Implementation Status in QAS Implementation Status in PRD 1051004 Completely implemented Completely implemented

1058003 Completely implemented 1058676 Completely implemented 1059507 Completely implemented

1062251 Completely implemented Completely implemented 1062468 Completely implemented Completely implemented 1062551 Completely implemented

1063485 Completely implemented 1065008 Completely implemented

1065334 Completely implemented Completely implemented 1066221 Completely implemented Completely implemented 1068615 Completely implemented Completely implemented 1069018 Completely implemented Completely implemented 1069919 Completely implemented Completely implemented 1070077 Completely implemented Completely implemented 1070261 Completely implemented Completely implemented 1073259 Completely implemented Completely implemented 1074689 Completely implemented

1076667 Completely implemented 1078079 Incompletely implemented

1079826 Completely implemented Completely implemented 1083806 Completely implemented Completely implemented 1084237 Completely implemented 1084779 Completely implemented 1086064 Completely implemented 1086813 Completely implemented 1087424 Completely implemented 1087442 Completely implemented 1088394 Completely implemented

1090279 Completely implemented Completely implemented 1092028 Completely implemented Completely implemented 1093252 Completely implemented Completely implemented 1094041 Completely implemented Completely implemented 1094320 Completely implemented

(18)

SAP Note Implementation Status in DEV Implementation Status in QAS Implementation Status in PRD 1121070 Completely implemented

1122294 Completely implemented Completely implemented 1124075 Completely implemented Completely implemented 1124408 Completely implemented 1133739 Completely implemented 1136770 Completely implemented 1136823 Completely implemented 1138969 Completely implemented 1142067 Completely implemented 1143177 Completely implemented

1146914 Completely implemented Completely implemented 1149356 Completely implemented Completely implemented 1150220 Completely implemented Completely implemented 1150843 Completely implemented Completely implemented 1151112 Completely implemented Completely implemented 1151557 Completely implemented

1155424 Completely implemented Completely implemented 1156116 Completely implemented Completely implemented

1156332 Completely implemented Obsolete version implemented Obsolete version implemented 1158063 Completely implemented

1161347 Completely implemented Completely implemented 1161951 Completely implemented Completely implemented 1162232 Completely implemented Completely implemented 1162512 Completely implemented Completely implemented 1163104 Completely implemented Completely implemented 1164283 Completely implemented Completely implemented 1165155 Completely implemented Completely implemented 1167546 Completely implemented

1168010 Completely implemented Completely implemented 1168073 Completely implemented Completely implemented 1174791 Completely implemented Completely implemented 1174946 Completely implemented Completely implemented 1175538 Completely implemented Completely implemented 1175933 Completely implemented

(19)

SAP Note Implementation Status in DEV Implementation Status in QAS Implementation Status in PRD 1232490 Completely implemented

1251471 Completely implemented Can be implemented Can be implemented 1256135 Completely implemented Can be implemented Can be implemented 1257933 Completely implemented Completely implemented

1260002 Completely implemented 1260868 Completely implemented 1264422 Completely implemented 1270744 Completely implemented 1271688 Completely implemented 1278444 Completely implemented 1280545 Completely implemented 1295856 Completely implemented 1302928 Completely implemented 1305640 Completely implemented 1310801 Completely implemented 1329090 Completely implemented 1330776 Completely implemented 1331356 Completely implemented 1336105 Completely implemented 1342183 Completely implemented 1346037 Completely implemented 1355614 Completely implemented 1356215 Completely implemented 1361038 Completely implemented 1362972 Completely implemented 1363371 Completely implemented 1366176 Completely implemented 1369659 Completely implemented 1388729 Completely implemented 1399942 Completely implemented 1402735 Completely implemented 1421254 Completely implemented 1422843 Completely implemented

1431823 Obsolete version implemented Completely implemented Completely implemented Total number of inconsistent SAP Notes: 210.

Evaluation

We identified that there are many SAP Notes in an inconsistent implementation status across the transport landscape. Inconsistent application of SAP Notes could result in production downtime. As a result of these inconsistencies, the status of an object in one system may be higher or lower when compared with another system in the landscape. This could cause failed transports and unpredictable test results. For example, if an SAP Note is not completely implemented in development and quality systems but has been completely implemented in production, any changes to that object in development and quality will not be valid for production.

(20)

implementation status. Download and implement the latest versions again in DEV and transport them to all systems in the transport landscape.

3.5 Business Functions

As part of our ongoing commitment to deliver innovation without disruption, the methodology for delivering new functionality has changed significantly. SAP Enhancement Packages, in combination with the Switch Framework, allows you to implement new functionality selectively. Only software components that are required for a certain functionality need to be enhanced. In addition, new functionality is deactivated by default. Individual business functions can be activated selectively. As a result, customers can isolate the impact of software updates and bring new functionality online faster through shortened testing cycles.

The following tables contain an overview the use of Business Functions in your productive system. ACTIVATED BUSINESS FUNCTION SET

Business Function Set Description

DIMP Discrete Industries / Mill Prod.

ACTIVATED BUSINESS FUNCTIONS IN THE BUSINESS FUNCTION SET

Business Function Description

DIMP_SDUD Discrete Indus. - Mill Products

IS_AD_MPN A&D Manufacturer Part Number

ACTIVATED ENTERPRISE EXTENSIONS

EA-FIN Financials Extension

EA-FS Financial Services

EA-ICM Incentive & Commission Mgmt

EA-ISE Industry-Spec. Sales Enhancement

EA-PLM PLM Extension

EA-TRV Travel Management Extension

ACTIVATED ENTERPRISE BUSINESS FUNCTIONS

Evaluation

Business Functions are activated in your productive system. You are using SAP technology for accelerated innovation enablement.

Background

Familiarize yourself with the Enhancement Package technology and the Switch Framework. For more information on Enhancement Packages for ERP, see http://service.sap.com/erp-ehp. In addition, we provide the Accelerated Innovation Enablement service as part of Enterprise Support. Please see SAP Note 1300402 for more details.

3.6 Consistency of Business Functions

In this check, we analyzed whether the same business functions are activated in your development, test, and production systems.

BUSINESS FUNCTIONS WITH INCONSISTENT ACTIVATION STATE

(21)

Business Function Activated in DEV Activated in QAS

Total number of inconsistent Business Functions: 0. Evaluation

(22)

4 System Landscape and TMS Settings

This chapter has a RED rating. The reason for this rating can be found in the

overview section below:

Usage of the SAP Transport Management System Transport Routes

Transport Management Tools Client Strategy

System Change Options

4.1 Usage of the SAP Transport Management System

In this check, we analyzed whether transports are executed using the Transport Management System or direct tp calls are executed at operating system level, for example, using scripts or external tools.

Evaluation

Almost all imports are triggered from the TMS. This adheres to SAP recommendations.

4.2 Transport Routes

In this check, we analyzed how the transport routes are configured in TMS.

Evaluation

There is a 1:1 relationship between the development and production systems. The transport routes comply with SAP's Best Practices.

4.3 Transport Management Tools

In this check, we analyzed whether you are using a tool to control your transports in addition to the SAP Transport Management System.

TRANSPORT MANAGEMENT TOOLS

Tool Used Remark

Change Request Management No Part of SAP Solution Manager Quality Gate Management No Part of SAP Solution Manager

Quality Approval Procedure Yes Part of SAP Transport Management System

(23)

System Landscape and TMS Settings Evaluation

According to the information we derived from your system, the Quality Approval procedure is activated in your TMS.

Change Request Management

Change Request Management in SAP Solution Manager supports the entire change process from the definition of change objects, collaboration between various roles involved in managing the change, and phase transitions, to management of the transports of the changed SAP objects between the SAP systems involved. You have a high degree of freedom to adapt the design of the change process to your individual needs, Change Request

Management incorporates SAP’s Best Practices in transport management, which are described above. In addition, it provides a cross-system object lock, which is an extended locking mechanism for Customizing and workbench objects. If you work with two development systems for the same production system, the retrofit functionality of Change Request Management helps you to keep both systems in sync.

Quality Gate Management

Quality Gate Management is an easy-to-set-up capability of SAP Solution Manager that provides governance support when dealing with transports in the context of phase changes. Two managers in the role of a quality manager and quality steering board member can demand quality gates during phase changes before moving transports from one system landscape, such as the development landscape, to the subsequent system landscape based on the integrated SAP Transport Management System. QGM allows you to document the reasons why a quality gate can or cannot be passed. In addition, all relevant documents such as change requests, requirement specifications, or test status reports can be attached to provide the necessary background information for quality gates. As an additional feature, the quality manager can group multiple transports and control their release and import in the chain of system landscapes. You benefit from a better managed quality management process, which at many companies, is still paper based or controlled using MS Excel.

Quality Assurance Procedure

The TMS Quality Assurance approval procedure increases the quality and the availability of the production system by letting you approve requests in the quality assurance system before delivering them to subsequent systems. When you activate QA approval procedure, change requests are only forwarded to the delivery system if all the QA approval steps have been processed for the request in the QA system and the request has been approved. When configuring the QA system, you can determine how many QA approval steps have to be processed for each request. If one check for an approval step is not successful, the entire request cannot be approved.

You can only import completely approved requests into the delivery systems. Rejected request are not imported into the delivery systems of the QA system.

4.4 Client Strategy

4.4.1 Clients in Development System

Client Client Role Description Changes transport for Client Specific Objects

Client-independent object Changes

000 SAP reference SAP AG Customizing in this client cannot be changed

No changes to Repository and cross-client Customizing objs 001 Customizing Auslieferungsmandant

R11

Customizing in this client cannot be changed

No changes to Repository and cross-client Customizing objs 066 SAP reference EarlyWatch Customizing in this client

cannot be changed

No changes to Repository and cross-client Customizing objs 100 Customizing Customizing Changes are recorded in

transport request

Changes to Repository and cross-client Customizing allowed

110 Training/Education Sandbox No automatic recording of changes for transport

120 Test ABAP No automatic recording of

changes for transport

130 Test Tests Customizing in this client

cannot be changed

No changes to Repository and cross-client Customizing objs

Evaluation

(24)

Cross-client and repository changes should be allowed in one client only. You should lock down all clients in which no transport requests are created. For more information about the impact of making changes in multiple clients/systems, refer to the background information at the end of the “Change Option Log” section.

4.4.2 Clients in Quality Assurance System

Client Client Role Description Changes transport for

Client Specific Objects

000 SAP reference

SAP AG Customizing in this client cannot be changed

R11

Changes are recorded in transport request

Changes to Repository and cross-client Customizing allowed 066 SAP

reference

EarlyWatch No automatic recording of changes for transport

No changes to cross-client Customizing objects

700 Test Tests Customizing in this client

cannot be changed

No changes to Repository and cross-client Customizing objs Evaluation

The client change options allow changes in one or more clients of the quality assurance system. The clients which are opened in QAS: 001.

Recommendation

Make sure that all clients are locked against any changes. SAP Best Practices state that all clients should be locked against changes in the quality assurance system. All changes should be made in the

development system and moved across the landscape via transport requests. For more information about the impact of making changes in multiple clients/systems, refer to the background information at the end of the “Change Option Log” section.

4.4.3 Clients in Production System

Client Client Role Description Changes transport for Client Specific Objects

000 SAP reference

SAP AG Customizing in this client cannot be changed

R11

Changes are recorded in transport request

Changes to Repository and cross-client Customizing allowed 066 SAP

reference

EarlyWatch No automatic recording of changes for transport

No changes to cross-client Customizing objects 700 Production Production Customizing in this client

cannot be changed

No changes to Repository and cross-client Customizing objs

Evaluation

The client change options allow changes in one or more clients of the production system. The clients which are opened in PRD: 001.

Recommendation

Secure all clients in the production system to ensure that no changes can be made without proper testing in the production support landscape.

For more information about the impact of making changes in the production system, refer to the background information at the end of the “Change Option Log” section.

4.5 System Change Options

4.5.1 System Change Options - Current Values

The purpose of this check is to verify whether objects are allowed to be changed directly in the production system. Change options control whether repository objects and cross-client Customizing objects in the software

(25)

System Landscape and TMS Settings SYSTEM CHANGE OPTIONS

Software Component Change Option

ABA_PLUS Not Modifiable; Not Enhanceable

CPRXRPM Not Modifiable; Not Enhanceable

EA-APPL Not Modifiable; Not Enhanceable

EA-DFPS Not Modifiable; Not Enhanceable

EA-FINSERV Not Modifiable; Not Enhanceable

EA-GLTRADE Not Modifiable; Not Enhanceable

EA-HR Not Modifiable; Not Enhanceable

EA-IPPE Not Modifiable; Not Enhanceable

EA-PS Not Modifiable; Not Enhanceable

EA-RETAIL Not Modifiable; Not Enhanceable

ECC-DIMP Not Modifiable; Not Enhanceable

ERECRUIT Not Modifiable; Not Enhanceable

FI-CA Not Modifiable; Not Enhanceable

FI-CAX Not Modifiable; Not Enhanceable

FINBASIS Not Modifiable; Not Enhanceable

HOME Not Modifiable; Not Enhanceable

INSURANCE Not Modifiable; Not Enhanceable

IS-CWM Not Modifiable; Not Enhanceable

IS-H Not Modifiable; Not Enhanceable

IS-M Not Modifiable; Not Enhanceable

IS-OIL Not Modifiable; Not Enhanceable

IS-PS-CA Not Modifiable; Not Enhanceable

IS-UT Not Modifiable; Not Enhanceable

LCAPPS Not Modifiable; Not Enhanceable

LOCAL Not Modifiable; Not Enhanceable

LSOFE Not Modifiable; Not Enhanceable

PI Not Modifiable; Not Enhanceable

PI_BASIS Not Modifiable; Not Enhanceable

SAP_ABA Not Modifiable; Not Enhanceable

SAP_AP Not Modifiable; Not Enhanceable

SAP_APPL Not Modifiable; Not Enhanceable

SAP_BASIS Not Modifiable; Not Enhanceable

SAP_BW Not Modifiable; Not Enhanceable

SAP_HR Not Modifiable; Not Enhanceable

SEM-BW Not Modifiable; Not Enhanceable

ST-A/PI Not Modifiable; Not Enhanceable

ST-PI Not Modifiable; Not Enhanceable

WFMCORE Not Modifiable; Not Enhanceable

Evaluation

No software components can be changed. This adheres to SAP Best Practices.

4.5.2 Change Option Log

The SAP system logs every switch to the new change option settings.

The table below shows the log for your system change option settings over the last six months: CHANGE OPTION LOG

"Not modifiable" -> "Modifiable" User (First Entry)

09.06.2010 BASIS

(26)

"Not modifiable" -> "Modifiable" User (First Entry)

15.07.2010 ADMIN123

Evaluation

The system change options were set to "modifiable" less than six times in the last six months.

IMPORTANT NOTES

Topic Note Number

Customizing: Current settings 77430

Background

Allowing changes to be made directly in the production system without sufficient testing in the quality assurance system carries a high risk. It may jeopardize performance, the stability of the production system, and the integrity of data. In the worst case scenario, it may cause unscheduled production downtime.

In addition, if you allow changes to be made directly in the production system, the development, quality assurance, and production systems are no longer synchronized with regard to development and customizing changes. This means that reliable testing is not possible in your transport landscape. If you have defined emergency or system-specific settings, you can change these for a short period of time.

Some tables that must be changed on a regular basis during production operation (for example, currency

exchange rates and tax values) are affected by the client control settings. SAP Note 77430 - Customizing: Current settings - explains how to allow changes to specific tables without having to change the client settings.

(27)

Transports

5 Transports

A YELLOW rating was set for this section . The reason for this rating can be

found in the overview section below:

Number of Objects in Transport Requests Release Cycles

Source Systems of Transport Requests Transport Requests in Production

Most Frequently Changed Objects in the Analysis Period Import Errors

Time Profiles for Imports

5.1 Number of Transport Requests in the Analysis Period

In this check, we counted the number of transports in the last six months. We took into account transports of type Customizing, Workbench, Transports of Copies, and Relocation Transports.

TRANSPORTS INTO PRODUCTION IN THE PERIOD

Request Category Number

Workbench and Relocation Request 814

Customizing Request 544

Transport of Copies 1

Sum 1359

Evaluation

The average number of transport requests per month is relatively high. This indicates that new functionality is implemented in addition to regular maintenance.

Recommendation

A high number of transport requests is only acceptable if implementation projects are going on. If this is not the case the number of transport requests should be kept small in order to ensure maximum stability of the system.

5.2 Number of Objects in Transport Requests

In this check, we counted the average number of objects in transport requests in the analysis period. AVERAGE NUMBER OF OBJECTS IN TRANSPORT REQUESTS

Request Category Number

Average Number of Objects in Workbench and Relocation Requests 4.22

Average Number of Objects in Customizing Requests 1.46

(28)

Evaluation

The average number of objects in transport requests is high. Changes should be bundled in large transport requests to avoid large numbers of dependencies between different transport requests. Furthermore, changes can be imported to the production system much quicker if the number of transport requests is low. The following table shows the ten biggest transport requests which contain the most objects in the analysis period: BIGGEST TRANSPORT REQUESTS IN THE ANALYSIS PERIOD

Request Type User Date Short Text No. of Objects

F7PK906036 K BOERR 20100323 Integration Project 109283 1404

DE1K944738 T REREBOB 20100415 Project 198453 220

DE1K944795 K BASIS 20100303 Integration Project 109283 121 DE1K945070 K PANDELO 20100505 Integration Project 109283 77

DE1K943335 K BASIS 20100401 DB Monitor 42

DE1K944249 K BASIS 20100125 SAP Note 1477783 36

DE1K947204 K BASIS 20100618 Project 198453 33

DE1K944167 K EMERAL 20100304 SAP Note 1343607 29

DE1K945714 K PANDELO 20100505 SAP Note 1343607 28

DE1K945859 K PANDELO 20100505 SAP Note 1477783 26

...

5.3 Release Cycles

Different options and strategies exist for transporting changes to the production system and for the associated quality assurance process. These range from a permanent flow of changes to strict release management (bundling of changes in larger packages – releases – that are transported and checked for quality as one entity). In this check, we analyzed the number of transport requests per day over the last six months.

Evaluation

There are some days on which a moderate number of transport requests were imported to production, but most of the transports were imported on a few of days within the analysis period. This indicates that release cycles exist but have not been defined clearly to manage changes within the landscape. Recommendation

We recommend that you deliver transports to production in release cycles. This enables you to perform integration and regression tests in the quality assurance system. One way of using release cycles is to group transport requests by CTS project. CTS projects are used by SAP’s transport tools (Change Request Management and Quality Gate Management) in SAP Solution Manager.

For more information about working with projects, see the online help documentation at:

(29)

Transports Change Categories

To provide the business with maximum flexibility and minimize the cost and risk of operating the production system, change requests should be grouped into different categories that must be realized with differing frequencies.

The following are typical change categories:

- Major Changes consist of larger amounts of new functionalities (invasive changes). A Major Release is tested intensively (sufficient time and dedicated test systems). Typical examples of major changes are completely new functionalities, changes that require system outage, changes to global objects with a high impact, changes that require end user training, and so on.

- Minor Changes involve minor enhancements and fixes only (non-invasive changes). A limited amount of regression testing is required for minor changes. Examples need to be provided (for example, shift plans, factory calendar, read-only reports, SAPscript forms, storage locations, and so on).

- Emergency Corrections should involve priority 1 changes only and are imported immediately (once regression tests are complete). Emergency changes should only be made if a critical business process no longer works. SAP Note 67739 explains the priority given to problem messages sent to SAP by customers. The criteria for the category “very high” can be taken as the criteria for emergency changes.

- Standard Changes are changes made repeatedly and whose impact is 100% clear (for example, changing authorizations, exchange rates, and so on). Change categories ensure that the correct testing approach is applied to each change. They also allow non-critical changes to be realized as quickly and flexibly as possible. It is crucial to have clear change definitions, including examples and a stringent approval process, from the outset.

Advantages of bundling changes in releases

We recommend that transports to the production system take place in cycles. This has the following benefits: - The frequency of changes to production is dramatically reduced. This guarantees stability phases between the release deliveries with a low number of daily changes.

- Common regression and integration testing for several projects can be carried out in one run. This reduces costs and risk.

- The documentation and rollout of new functionalities to end users can be controlled. If changes are deployed continuously, end users will be confused by frequently changed functionalities.

- Administrative effort is reduced for controlling and approving single transports. All transports of a release move from one phase to another at a single point in time by means of automated import procedures.

- Error corrections and bugfixing of new functionality is limited to the post GoLive phase of a release. During that time, resources from the support department can be scheduled and blocked for this task. If new functionality is delivered continuously to production, bugfixing requests are submitted unplanned and at all times. Support resources must be removed from other projects at short notice.

- The risk of transport sequence errors and forgotten transports is high if changes are imported to production continuously. For more information about the risks of the "Import single" strategy, see the TMS documentation under: Transport Strategy in the CTS -> transports with Import Queues -> Single Transports:

http://help.sap.com/saphelp_nw04/helpdata/en/54/b3fc377cb5be5ae10000009b38f842/frameset.htm

5.4 Source Systems of Transport Requests

The following check provides information about the different source systems that have been used over the last 6 months to create transport requests for your productive system.

All transport requests should be created in the same development system.

If you have more than one source system with many transport requests, we recommend that you review the reasons for this.

If you have systems that have only been used temporarily (for example, for project purposes), the time window between the dates of the first and last imports should correspond to the project duration. For the analysis, we considered all the "Customizing", "Workbench", "Relocation", and "Transport of Copies" transport requests that were made to your productive system over the last six months. This includes imports and exports.

TABLE OF DIFFERENT SOURCE SYSTEMS

Source Systems Number of transports Date of first import Date of last import

DE1 1357 04.01.2010 30.06.2010

F7P 2 23.03.2010 18.05.2010

PE1 2 09.06.2010 30.06.2010

Evaluation

Almost all transport requests come from the development system. This is the recommended procedure.

(30)

REQUESTS DIRECTLY CREATED IN

Request Type User Date Short Text

PE1K900028 Workbench Request PULMER 09.06.2010 Emergency Correction - PULMER PE1K900030 Workbench Request BASIS 30.06.2010 Bug Fixing ZREORG

Sum 2

Evaluation

Only a small number of transport requests were created in Production directly. Recommendation

The requests created in the production system directly are listed above. Find out why these requests were created in the production system. For a list of all requests, see table E070 in transaction SE16. On the selection screen, specify TRKORR = <SID>* and limit the selection to the last six months.

Background

You should check for all open transport requests in your system and release them if no longer required. Open transport requests allow changes to be made in the production system directly. They may also lock development objects, which can trigger in transport errors in the future.

If you make changes in the production system directly, make sure that the same changes are distributed to all other systems in your system landscape.

5.6 Most Frequently Changed Objects in the Analysis Period

In this section, we analyzed repository, data dictionary, and BW objects that were changed most frequently in the analysis period.

MOST FREQUENTLY CHANGED OBJECTS

Object Development Class No. of Changes

LIMU REPS ZSURMM037 ZDES 8

LIMU REPS ZFIXFI014 ZDES 7

LIMU REPS ZQLRCS002 ZDES 6

LIMU FUNC ZVENSD021 ZDES 6

LIMU REPS ZYCRR161_141 ZDES 5

LIMU REPS ZVERSD054 ZDES 5

LIMU REPS LZENNPP292F01 ZDES 5

LIMU REPS ZSUPMM002 ZDES 4

LIMU REPS ZRM06LBEW ZDES 4

LIMU REPS ZJ_1BNFPR_SF ZDES 4

LIMU REPS LZVENSD029F01 ZDES 4

...

Total number of frequent changes 16

Evaluation

Some of the objects are changed frequently. This indicates that the business requirements were not well understood when the development was initiated. A large number of changes to a single object also indicates that the testing effort in the quality system is insufficient and does not correspond to the business requirements.

Recommendation

Improve the description of the development requirements. The requirements must be clear and well-communicated between the business and development departments before development starts. Ideally, a tool should be in place to record all change requests. The changes should be discussed in a Change Advisory Board before being forwarded to the development department. SAP Solution Manager provides a workflow for managing the entire Change Request Management process.

Compliance with the development specifications must be validated during the testing phases of the project to help reduce the number of object repairs transported to production. Initial and corrective transports for an object should be imported to production at the same time.