Transport Execution Analysis_report.pdf
Short Description
Download Transport Execution Analysis_report.pdf...
Description
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 Release Service Tool
SAP Solution Manager EHP 1 for NetWeaver 7.0 701_2010_1 SP3
Date of Session Date of Report Author
16.07.2010 20.08.2010 John Doe
Service Center Telephone Fax
Session No. Installation No. Customer No.
0000000000000 0000000000 0000000000
Table of Contents
1 Table of Contents 1 TABLE OF CONTENTS ........................................................................................................................................ 2 SERVICE SUMMARY ............................................................................................................................................... 4
1.1 SUMMARY .........................................................................................................................................4 1.2 ACTION PLAN ....................................................................................................................................5 1.3 SYSTEM HISTORY ..............................................................................................................................6 1.4 SYSTEM SIZE INDICATORS .................................................................................................................6 1.5 CHANGE MANAGEMENT INDICATORS...................................................................................................6 1.6 KEY PERFORMANCE INDICATORS........................................................................................................6 2 CUSTOM CODE MAINTAINABILITY .................................................................................................................... 8
2.1 MODIFIED OBJECTS IN THE SYSTEM ...................................................................................................8 2.2 CUSTOMER OBJECTS IN THE SYSTEM .................................................................................................9 2.3 USAGE 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.1 AGE OF SUPPORT PACKAGES .......................................................................................................... 12 3.2 CONSISTENCY OF SAP SUPPORT PACKAGES ................................................................................... 13 3.2.1 Import History ....................................................................................................................................... 13
3.3 SAP NOTES ................................................................................................................................... 14 3.4 CONSISTENCY OF SAP NOTES........................................................................................................ 15 3.5 BUSINESS FUNCTIONS .................................................................................................................... 20 3.6 CONSISTENCY OF BUSINESS FUNCTIONS ......................................................................................... 20 4 SYSTEM LANDSCAPE AND TMS SETTINGS ................................................................................................... 22
4.1 USAGE OF THE SAP TRANSPORT MANAGEMENT SYSTEM ................................................................. 22 4.2 TRANSPORT ROUTES...................................................................................................................... 22 4.3 TRANSPORT MANAGEMENT TOOLS .................................................................................................. 22 4.4 CLIENT 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.5 SYSTEM CHANGE OPTIONS ............................................................................................................. 24 4.5.1 System Change Options - Current Values ............................................................................................ 24 4.5.2 Change Option Log .............................................................................................................................. 25 5 TRANSPORTS .................................................................................................................................................... 27
5.1 NUMBER OF TRANSPORT REQUESTS IN THE ANALYSIS PERIOD ......................................................... 27 5.2 NUMBER OF OBJECTS IN TRANSPORT REQUESTS............................................................................. 27 5.3 RELEASE CYCLES .......................................................................................................................... 28 5.4 SOURCE SYSTEMS OF TRANSPORT REQUESTS ................................................................................ 29 5.5 TRANSPORT REQUESTS IN PRODUCTION ......................................................................................... 29 5.6 MOST FREQUENTLY CHANGED OBJECTS IN THE ANALYSIS PERIOD ................................................... 30 5.7 IMPORT ERRORS ............................................................................................................................ 31 5.7.1 Transport Error Resolution Time........................................................................................................... 32 SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
2
Table of Contents 5.7.2 Most Frequent Transport Errors ........................................................................................................... 32
5.8 TIME 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.1 TESTING TIME ................................................................................................................................ 38 6.2 REFRESH OF THE QUALITY ASSURANCE SYSTEM ............................................................................. 39 6.3 NUMBER OF RUNTIME ERRORS PER DAY ......................................................................................... 39 6.4 TYPE OF RUNTIME ERRORS ............................................................................................................ 40 7 TRANSPORT LANDSCAPE CONSISTENCY .................................................................................................... 41
7.1 TRANSPORT TRACKING ................................................................................................................... 41 7.1.1 Requests Deleted from the Queue of QAS .......................................................................................... 41
7.2 OPEN TRANSPORT REQUESTS IN DEVELOPMENT ............................................................................. 42 7.3 PARKED TRANSPORT REQUESTS ..................................................................................................... 42 7.4 TRANSPORT SEQUENCE VIOLATIONS ............................................................................................... 43 8 APPENDIX........................................................................................................................................................... 45
8.1 BEST 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.2 SOFTWARE CHANGE MANAGEMENT FEATURES IN SAP SOLUTION 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 8.2.4 SAP Test Workbench............................................................................................................................ 46
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
3
Service Summary
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. If you have any questions or comments concerning this report, do not hesitate to contact us.
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
4
Service Summary
1.2 Action Plan Number Priority Issue 1 Very High
2 Very High
3 High
4 High
5 High
6 High
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.
7 Medium There is a large number of modified SAP standard objects in the system. 8 Medium There is a large number of customer objects in the system. 10 Medium Some objects have been changed frequently in production. 11 Medium Many transport requests spend less than one day in the quality assurance system. 12 Medium The production system was not copied to the quality assurance system within the last 12 months.
Recommended action
When to do
See section
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
Do not delete transport requests from the Ongoing 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. Import Support Package stacks at least Next few once a year. months
7.1.1
Change the client change options according to our recommendations.
Immediately
4.4
Transport requests should be bundled in release and maintenance cycles. See the detailed explanations in chapter 5.3.
Next few months
5.3
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. Check if SAP Enhancement options can be used instead of modifying the SAP standard.
Next few weeks 7.4
Next implementation project
2.1
Check if new business requirements can be fulfilled within the SAP Standard or in future SAP Releases before you start a custom development project. Improve the development specifications and introduce mandatory testing procedures in order to avoid continuous adjustments of objects in production. Introduce mandatory testing procedures. Make sure that changes are tested sufficiently before they are moved into production.
Next implementation project
2.2
Refresh the quality assurance system regularly by copying the production system.
Next few months
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
3.1
Next few weeks 5.6
Next few weeks 6.1
6.2
5
Service Summary
1.3 System History SYSTEM HISTORY Step
Target Release
1. Installation 2. System Copy PE1 -> QE1
700
Date 28.06.2007 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) Transactions and Reports in Use (last month)
1288 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 Customizing Requests since System Installation Customer Objects Modified Objects Average Number of Transport Requests per Month
10770 6988 6454 356 227
Owners of Transport Requests Errors during Transport in Production in Analysis Period Average Number of ABAP Dumps per Day (data only available for a shorter period) Transport Sequence Violations in Analysis Period
17 27 102
Transports in Analysis Period Problem Indicators
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 Transports in Production Transports with short transition time Amount of Emergency Changes
Total number of transport requests imported in production
1361
Transports created in production Transports with a transition time from DEV to PRD shorter than 1 day. Ratio between emergency changes and transport requests imported into Production in the last six month. Total number of objects in workbench requests
2 461
Number of failed object changes due to technical transport errors Number of objects which were overwritten by older version Number of objects with 4 or more versions in analysis period
27 10 16
Ratio between failed changes and Imported Objects in Workbench Requests
1.54%
Total number of objects in workbench requests Import errors Transport sequence errors Frequently changed object versions Amount of Failed Changes
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
34.02% 3432
6
Service Summary
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
7
Custom Code Maintainability
2 Custom Code Maintainability
This chapter was rated YELLOW. The reason for this rating can be found in the overview section below:
OVERVIEW OF RATINGS Rating
Check Performed 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
FI-LOC SD-MD-CM CO-PC-ACT SD-SLS LO-MD-MM SD-MD-MM MM-PUR PP-SFC LO-MD-BOM CO-OM-CCA MM-IM CO-PA FI PP-BD-RTG FIN-FSCM-TRM-TM SD-BIL CO-PC-PCP CA-FIM-FMA EC-PCA-BS FI-AR-AR
Localization Conditions Actual Costing/Material Ledger Sales Material Master Material Maintenance Purchasing Production Orders Bills of Material Cost Center Accounting Inventory Management Profitability Analysis Financial Accounting Routing Transaction Manager Billing Product Cost Planning Financial Mathematics Basic Settings Basic Functions
SAP Guided Self Service - Transport Execution Analysis,
Coding 21 47 13 12 1 9 0 4 2 2 1 2 2 1 5 3 2 1 0 0
16.07.2010
Data Dictionary Text Others Sum 54 4 20 1 7 0 6 3 5 0 4 2 3 5 0 2 1 3 0 4
1 0 4 0 1 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0
7 0 0 2 3 0 2 0 0 4 0 2 1 0 0 0 1 0 4 0
83 51 37 15 12 9 8 7 7 6 6 6 6 6 5 5 4 4 4 4 8
Custom Code Maintainability Application Component
Description
Coding
Other Total
Data Dictionary Text Others Sum
27 155
39 163
0 7
5 31
71 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
ZDES ZLF Z_141 ZKFBC ZPROC $TMP Z001 ZLF_TMP Total
Class DES Fiscal book ABAP - 141 Class ZKFBC PROC Temporary Objects (never transported!) Customer development class Temporary
2247 423 391 63 5 1 2 1 3133
Data Dictionary Others Sum 1626 841 232 123 0 1 2 0 2825
385 4258 54 1318 35 658 20 206 0 5 2 4 0 4 0 1 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. When new functional requirements are introduced, there should be procedures in place to check whether these requirements can be fulfilled by current or planned SAP standard functionality. Customer coding should only be allowed in unavoidable cases and after a restrictive approval step. SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
9
Custom Code Maintainability
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 20 TRANSACTIONS BY DIALOG AND BACKGROUND STEPS Transaction / Report
Description
# Steps
SE11_OLD CNV_CDMC SE37 CMOD SM37 ST22 SESSION_MANAGER SE01 ST13 ST14 SE19 SE09 STMS SU01 DSA SE18 SE61 SE24 SEU_INT SE16
ABAP/4 Dictionary Maintenance Custom Develop. Management Cockpit ABAP Function Modules Enhancements Overview of job selection ABAP dump analysis Session Manager Menu Tree Display Transport Organizer (Extended) Analysis&Monitoring tool collection Application Analysis Business Add-Ins: Implementations Transport Organizer Transport Management System User Maintenance Service Session Workbench Business Add-Ins: Definitions R/3 Documentation Class Builder Object Navigator Data Browser
2454 2219 1648 881 815 597 450 425 274 274 180 161 158 142 128 116 116 101 77 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 Transactions and reports in customer namerange Transactions and reports with namespace prefix: /* Sum
62 0 0 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 SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
10
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.
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
11
SAP Software Maintenance
3 SAP Software Maintenance
This chapter was rated RED. The reason for this rating can be found in the overview section below:
OVERVIEW OF RATINGS 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 EA-APPL EA-DFPS EA-FINSERV EA-GLTRADE EA-HR EA-IPPE EA-PS EA-RETAIL ECC-DIMP ERECRUIT FI-CA FI-CAX FINBASIS INSURANCE IS-CWM IS-H IS-M IS-OIL IS-PS-CA IS-UT LCAPPS LSOFE PI_BASIS SAP_ABA SAP_AP SAP_APPL
400 600 600 600 600 600 400 600 600 600 600 600 600 600 600 600 600 600 600 600 600 2005_700 600 2005_1_700 700 700 600
0006 0008 0008 0008 0008 0020 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0006 0006 0006 0006 0006 0003 0006 0011 0011 0008 0008
SAPK-40006INCPRXRPM SAPKGPAD08 SAPKGPDD08 SAPKGPFD08 SAPKGPGD08 SAPKGPHD20 SAPKGPID08 SAPKGPPD08 SAPKGPRD08 SAPK-60008INECCDIMP SAPK-60008INERECRUIT SAPK-60008INFICA SAPK-60008INFICAX SAPK-60008INFINBASIS SAPK-60008ININSURANC SAPK-60008INISCWM SAPK-60006INISH SAPK-60006INISM SAPK-60006INISOIL SAPK-60006INISPSCA SAPK-60006INISUT SAPKIBHD03 SAPK-60006INLSOFE SAPKIPYJ7B SAPKA70011 SAPKNA7008 SAPKH60008
18.09.2006 02.02.2007 02.02.2007 02.02.2007 02.02.2007 13.08.2007 02.02.2007 02.02.2007 02.02.2007 26.02.2007 31.01.2007 02.02.2007 05.02.2007 02.02.2007 02.02.2007 05.02.2007 28.08.2006 28.08.2006 28.08.2006 28.08.2006 28.08.2006 26.07.2006 22.08.2006 10.01.2007 11.01.2007 18.01.2007 02.02.2007
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
12
SAP Software Maintenance Component
Release
Level
Highest SP Implemented
Shipping Date
SAP_BASIS SAP_BW SAP_HR SEM-BW ST-A/PI ST-PI WFMCORE
700 700 600 600 01M_ECC600 2008_1_700 200
0011 0012 0020 0008 0000 0002 0006
SAPKB70011 SAPKW70012 SAPKE60020 SAPKGS6008 SAPKITAR7E SAPKITLRD2 SAPK-20006INWFMCORE
24.01.2007 11.01.2007 13.08.2007 02.02.2007 24.03.2010 13.04.2010 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 The table below shows when the last Support Packages were imported into the DEV, QAS, and PRD systems.
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
13
SAP Software Maintenance SUPPORT PACKAGE STACK IMPORT IN THE TRANSPORT LANDSCAPE Component
Release
Level Support Packages
Import in DEV
Import in QAS
Import in PRD
CPRXRPM
400
06.10.2006
29.06.2007
29.06.2007
EA-APPL EA-DFPS EA-FINSERV EAGLTRADE EA-HR EA-IPPE EA-PS EA-RETAIL ECC-DIMP ERECRUIT
600 600 600 600
0006 SAPK40006INCPRXRPM 0008 SAPKGPAD08 0008 SAPKGPDD08 0008 SAPKGPFD08 0008 SAPKGPGD08
03.04.2007 07.01.2008 03.04.2007 02.06.2007
28.06.2007 07.01.2008 28.06.2007 28.06.2007
28.06.2007 07.01.2008 28.06.2007 28.06.2007
600 400 600 600 600 600
0020 0008 0008 0008 0008 0008
16.01.2008 03.04.2007 19.12.2007 19.12.2007 03.04.2007 02.06.2007
17.01.2008 28.06.2007 28.06.2007 28.06.2007 28.06.2007 28.06.2007
17.01.2008 28.06.2007 28.06.2007 28.06.2007 28.06.2007 28.06.2007
FI-CA FI-CAX FINBASIS INSURANCE
600 600 600 600
0008 0008 0008 0008
19.12.2007 19.12.2007 03.04.2007 19.12.2007
28.06.2007 28.06.2007 28.06.2007 28.06.2007
28.06.2007 28.06.2007 28.06.2007 28.06.2007
IS-CWM IS-H IS-M IS-OIL IS-PS-CA IS-UT LCAPPS LSOFE PI_BASIS SAP_ABA SAP_AP SAP_APPL SAP_BASIS SAP_BW SAP_HR SEM-BW ST-A/PI ST-PI WFMCORE
600 600 600 600 600 600 2005_700 600 2005_1_700 700 700 600 700 700 600 600 01M_ECC600 2008_1_700 200
0008 0006 0006 0006 0006 0006 0003 0006 0011 0011 0008 0008 0011 0012 0020 0008 0000 0002 0006
19.12.2007 07.01.2008 06.10.2006 19.12.2007 06.10.2006 19.12.2007 06.10.2006 04.04.2007 13.03.2007 13.03.2007 03.04.2007 03.04.2007 13.03.2007 03.04.2007 16.01.2008 05.04.2007 09.06.2010 09.06.2010 19.12.2007
28.06.2007 07.01.2008 28.06.2007 28.06.2007 28.06.2007 28.06.2007 29.06.2007 28.06.2007 27.06.2007 27.06.2007 27.06.2007 27.06.2007 27.06.2007 27.06.2007 17.01.2008 28.06.2007 09.06.2010 09.06.2010 29.06.2007
28.06.2007 07.01.2008 28.06.2007 28.06.2007 28.06.2007 28.06.2007 29.06.2007 28.06.2007 27.06.2007 27.06.2007 27.06.2007 27.06.2007 27.06.2007 27.06.2007 17.01.2008 28.06.2007 09.06.2010 09.06.2010 29.06.2007
SAPKGPHD20 SAPKGPID08 SAPKGPPD08 SAPKGPRD08 SAPK-60008INECCDIMP SAPK60008INERECRUIT SAPK-60008INFICA SAPK-60008INFICAX SAPK-60008INFINBASIS SAPK60008ININSURANC SAPK-60008INISCWM SAPK-60006INISH SAPK-60006INISM SAPK-60006INISOIL SAPK-60006INISPSCA SAPK-60006INISUT SAPKIBHD03 SAPK-60006INLSOFE SAPKIPYJ7B SAPKA70011 SAPKNA7008 SAPKH60008 SAPKB70011 SAPKW70012 SAPKE60020 SAPKGS6008 SAPKITAR7E SAPKITLRD2 SAPK20006INWFMCORE
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. SAP NOTE ASSISTANT Components
Number of notes implemented with SAP Note Assistant
CO LO XX SAP Guided Self Service - Transport Execution Analysis,
141 65 34 16.07.2010
14
SAP Software Maintenance Components
Number of notes implemented with SAP Note Assistant
PP BC FIN CA FI MM IS SV LE QM SD PS SRM EC AC
28 17 16 14 12 9 7 6 3 2 2 1 1 1 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 SAP NOTES SAP Note Implementation Status in DEV Implementation Status in QAS Implementation Status in PRD 36353 115899 140573 156239 170819 198519
Obsolete version implemented Completely implemented Obsolete version implemented Completely implemented Obsolete version implemented Completely implemented
Completely implemented
Completely implemented
Completely implemented
Completely implemented
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
15
SAP Software Maintenance SAP Note Implementation Status in DEV Implementation Status in QAS Implementation Status in PRD 211324 352375 355404 362135 377501 386340 390738 631266 658090 698122 735130 736873 738631 804722 805007 807001 884639 885207 936820 944823 980213 986184 998194 998195 1003894 1005433 1009219 1009374 1012685 1013462 1014419 1014617 1015050 1019060 1022677 1026604 1031438 1031612 1032524 1032547 1035372 1036862 1036943 1037070 1037869 1039984 1040061 1040798 1040800 1043129 1043688 1045412 1047606 1050478
Obsolete version implemented Completely implemented Obsolete version implemented Completely implemented Obsolete version implemented Obsolete version implemented Completely implemented Obsolete version implemented Completely implemented Completely implemented
Completely implemented
Completely implemented
Completely implemented
Completely implemented
Completely implemented Completely implemented
Completely implemented Completely implemented
Obsolete version implemented Completely implemented Completely implemented Completely implemented Completely implemented Obsolete version implemented Completely implemented Obsolete version implemented Obsolete version implemented Completely implemented Can be implemented Completely implemented Completely implemented Can be implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented
Completely implemented
Completely implemented Completely implemented
Can be implemented
Can be implemented
Completely implemented
Completely implemented
Completely implemented Completely implemented Completely implemented Incompletely implemented Completely implemented Completely implemented Completely implemented
Completely implemented Completely implemented Can be implemented Incompletely implemented Can be implemented Completely implemented
Completely implemented Completely implemented
Completely implemented Completely implemented Completely implemented Obsolete version implemented Completely implemented Cannot be implemented Cannot be implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Obsolete version implemented Completely implemented Completely implemented Completely implemented
Completely implemented Obsolete version implemented
Obsolete version implemented
Completely implemented Completely implemented
Completely implemented Completely implemented
Completely implemented Completely implemented
Completely implemented Completely implemented Completely implemented
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
Completely implemented 16
SAP Software Maintenance SAP Note Implementation Status in DEV Implementation Status in QAS Implementation Status in PRD 1051004 1051182 1052572 1052715 1053589 1053626 1054262 1058003 1058676 1059507 1059521 1061510 1061568 1062251 1062468 1062551 1063485 1065008 1065334 1066221 1068615 1069018 1069919 1070077 1070261 1073259 1074689 1075585 1076222 1076667 1078079 1079826 1083806 1084237 1084779 1086064 1086813 1087424 1087442 1088394 1090279 1092028 1093252 1094041 1094320 1095074 1111190 1113127 1114348 1114474 1115352 1118145 1119516 1120852
Completely implemented Obsolete version implemented Completely implemented Completely implemented
Completely implemented Completely implemented
Completely implemented
Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Obsolete version implemented Completely implemented Completely implemented Incompletely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented
Completely implemented
Completely implemented
Completely implemented Completely implemented
Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented
Completely implemented
Completely implemented Completely implemented
Completely implemented Completely implemented Completely implemented Completely implemented
Completely implemented Completely implemented
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
17
SAP Software Maintenance SAP Note Implementation Status in DEV Implementation Status in QAS Implementation Status in PRD 1121070 1121103 1122294 1124075 1124408 1133739 1136770 1136823 1138969 1142067 1143177 1144194 1145148 1145736 1145960 1146690 1146914 1149356 1150220 1150843 1151112 1151557 1152263 1153533 1153873 1153874 1154029 1155424 1156116 1156332 1158063 1159009 1160107 1160226 1161347 1161951 1162232 1162512 1163104 1164283 1165155 1167546 1168010 1168073 1174791 1174946 1175538 1175933 1177258 1180402 1223773 1224499 1225078 1228028
Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented
Completely implemented Completely implemented
Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Obsolete version implemented
Obsolete version implemented
Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented
Completely implemented Completely implemented Completely implemented
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
18
SAP Software Maintenance SAP Note Implementation Status in DEV Implementation Status in QAS Implementation Status in PRD 1232490 1237796 1238765 1238910 1239541 1239958 1244881 1248153 1249431 1251471 1256135 1257933 1260002 1260868 1264422 1270744 1271688 1278444 1280545 1295856 1302928 1305640 1310801 1329090 1330776 1331356 1336105 1342183 1346037 1355614 1356215 1361038 1362972 1363371 1366176 1369659 1388729 1399942 1402735 1421254 1422843 1431823
Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Completely implemented Obsolete version implemented
Completely implemented Completely implemented
Completely implemented
Can be implemented Can be implemented Completely implemented
Can be implemented Can be 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. Recommendation Use the SAP Note Assistant (transaction SNOTE) to check and resolve the SAP Notes with an inconsistent
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
19
SAP Software Maintenance 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 IS_AD_MPN
Discrete Indus. - Mill Products A&D Manufacturer Part Number
ACTIVATED ENTERPRISE EXTENSIONS Business Function
Description
EA-FIN EA-FS EA-ICM EA-ISE EA-PLM EA-TRV
Financials Extension Financial Services Incentive & Commission Mgmt Industry-Spec. Sales Enhancement PLM Extension Travel Management Extension
ACTIVATED ENTERPRISE BUSINESS FUNCTIONS Business Function
Description
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 Business Function
Activated in DEV
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
Activated in QAS
20
SAP Software Maintenance Business Function
Activated in DEV
Activated in QAS
Total number of inconsistent Business Functions: 0. Evaluation All Business Functions have the same activation state in your landscape. No inconsistencies exist.
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
21
System Landscape and TMS Settings
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:
OVERVIEW OF RATINGS Rating
Check Performed 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 Quality Gate Management Quality Approval Procedure 3rd party Transport Tool
No No Yes No
Part of SAP Solution Manager Part of SAP Solution Manager Part of SAP Transport Management System Vendor:
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
22
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
000
SAP reference
SAP AG
001
Customizing
066
SAP reference
Auslieferungsmandant R11 EarlyWatch
100
Customizing
Customizing
Customizing in this client cannot be changed Customizing in this client cannot be changed Customizing in this client cannot be changed Changes are recorded in transport request
110
Training/Education Sandbox
120
Test
ABAP
130
Test
Tests
Client-independent object Changes
No changes to Repository and cross-client Customizing objs No changes to Repository and cross-client Customizing objs No changes to Repository and cross-client Customizing objs Changes to Repository and cross-client Customizing allowed No automatic recording of Changes to Repository and changes for transport cross-client Customizing allowed No automatic recording of Changes to Repository and changes for transport cross-client Customizing allowed Customizing in this client No changes to Repository and cannot be changed cross-client Customizing objs
Evaluation The client change options allow changes in more than one client. The clients which are open in DEV: 100 110 120. Recommendation SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
23
System Landscape and TMS Settings 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
Client-independent object Changes
000
SAP AG
Customizing in this client cannot be changed Changes are recorded in transport request No automatic recording of changes for transport Customizing in this client cannot be changed
No changes to Repository and cross-client Customizing objs Changes to Repository and crossclient Customizing allowed No changes to cross-client Customizing objects No changes to Repository and cross-client Customizing objs
001 066 700
SAP reference Customizing SAP reference Test
Auslieferungsmandant R11 EarlyWatch Tests
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
Client-independent object Changes
000
SAP AG
Customizing in this client cannot be changed Changes are recorded in transport request No automatic recording of changes for transport Customizing in this client cannot be changed
No changes to Repository and cross-client Customizing objs Changes to Repository and crossclient Customizing allowed No changes to cross-client Customizing objects No changes to Repository and cross-client Customizing objs
001 066 700
SAP reference Customizing SAP reference Production
Auslieferungsmandant R11 EarlyWatch Production
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 components and namespaces/name ranges available in your production system are allowed to be modified.
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
24
System Landscape and TMS Settings SYSTEM CHANGE OPTIONS Software Component
Change Option
ABA_PLUS CPRXRPM EA-APPL EA-DFPS EA-FINSERV EA-GLTRADE EA-HR EA-IPPE EA-PS EA-RETAIL ECC-DIMP ERECRUIT FI-CA FI-CAX FINBASIS HOME INSURANCE IS-CWM IS-H IS-M IS-OIL IS-PS-CA IS-UT LCAPPS LOCAL LSOFE PI PI_BASIS SAP_ABA SAP_AP SAP_APPL SAP_BASIS SAP_BW SAP_HR SEM-BW ST-A/PI ST-PI WFMCORE
Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable Not Modifiable; Not Enhanceable 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 30.06.2010 05.07.2010 06.07.2010
BASIS BASIS ADMIN123 ADMIN123
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
25
System Landscape and TMS Settings "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 systemspecific 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.
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
26
Transports
5 Transports
A YELLOW rating was set for this section . The reason for this rating can be found in the overview section below:
OVERVIEW OF RATINGS Rating
Check Performed 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 Customizing Request Transport of Copies Sum
814 544 1 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 Average Number of Objects in Customizing Requests Average Number of Objects in Transports of Copies Average Number of Objects in Transport Requests
4.22 1.46 220.00 3.28
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
27
Transports 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 DE1K944738 DE1K944795 DE1K945070 DE1K943335 DE1K944249 DE1K947204 DE1K944167 DE1K945714 DE1K945859 ...
K T K K K K K K K K
BOERR REREBOB BASIS PANDELO BASIS BASIS BASIS EMERAL PANDELO PANDELO
20100323 20100415 20100303 20100505 20100401 20100125 20100618 20100304 20100505 20100505
Integration Project 109283 Project 198453 Integration Project 109283 Integration Project 109283 DB Monitor SAP Note 1477783 Project 198453 SAP Note 1343607 SAP Note 1343607 SAP Note 1477783
1404 220 121 77 42 36 33 29 28 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: http://help.sap.com/saphelp_nw04/helpdata/en/03/dcb6b6048711d3b42a00609419f767/frameset.htm
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
28
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 DE1 F7P PE1
Number of transports
Date of first import
Date of last import
1357 2 2
04.01.2010 23.03.2010 09.06.2010
30.06.2010 18.05.2010 30.06.2010
Evaluation Almost all transport requests come from the development system. This is the recommended procedure.
5.5 Transport Requests in Production In this check, we analyzed the change requests that were created directly in Production within the analysis period.
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
29
Transports REQUESTS DIRECTLY CREATED IN Request
Type
User
PE1K900028 PE1K900030 Sum
Workbench Request Workbench Request 2
PULMER BASIS
Date Short Text 09.06.2010 Emergency Correction - PULMER 30.06.2010 Bug Fixing ZREORG
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 = * 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
LIMU REPS ZSURMM037 LIMU REPS ZFIXFI014 LIMU REPS ZQLRCS002 LIMU FUNC ZVENSD021 LIMU REPS ZYCRR161_141 LIMU REPS ZVERSD054 LIMU REPS ZVERSD040 LIMU REPS LZENNPP292F01 LIMU REPS ZVERSD021 LIMU REPS ZVERSD038 LIMU REPS ZSUPMM002 LIMU REPS ZRM06LBEW LIMU REPS ZJ_1BNFPR_SF LIMU REPS LZVENSD029F01 ... Total number of frequent changes
ZDES ZDES ZDES ZDES ZDES ZDES ZDES ZDES ZDES ZDES ZDES ZDES ZDES ZDES
No. of Changes 8 7 6 6 5 5 5 5 5 4 4 4 4 4 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 wellcommunicated 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. Transport requests must be tested before they are exported from the development system. In the case of SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
30
Transports customizing changes, this can be achieved using an additional test client in the development system. Transport requests can then be transferred to this client using transaction SCC1. In the case of workbench requests, you can use transports of copies to send objects to the test system. You only release the original transport request if the test is successful. Only the original transport request is sent to production. The test transports are not sent to production.
5.7 Import Errors We analyzed the import errors in the analysis period. If the same error occurred several times (for example, if the import was repeated several times), this was only counted as one error. If an import error was resolved within one hour it was not counted. The overall return code of a transport is the maximum return code of the different transport steps. Return codes of less than 0008 are warnings only and can usually be ignored. NUMBER OF TRANSPORTS WITH IMPORT ERRORS Indicator
Value
Number of transport requests with import errors Total number of transport requests Amount of transport requests with import errors
27 1359 1.99%
Evaluation The number of transport errors in the production system in the analysis period was low. This shows that imports are tested sufficiently in the quality assurance system and that the quality assurance system is operating correctly. The following table lists the biggest transport requests with import errors. BIGGEST TRANSPORT REQUESTS WITH IMPORT ERRORS Transport DE1K944738 DE1K944738 DE1K945714 DE1K946661 DE1K938121
Date
Errorneous Objects
All Objects in Request
15.04.2010 15.04.2010 05.05.2010 24.05.2010 10.05.2010
1 1 3 1 1
220 220 28 9 7
The following table lists the number of errors by return code. NUMBER OF ERRORS BY RETURN CODE Return Code
Meaning
No of Errors
0008
Individual objects could not be transported successfully. You need to analyze and correct the errors. Examples of import errors: - Original object was not overwritten - Repaired object was not overwritten - An object could not be activated because a dependent object was missing from the system
27
The following table shows the transport steps in which the errors occurred. NUMBER OF ERRORS BY TRANSPORT STEP Transport Step
Char. Description
Activation
A
Generation Main Import XPRAs
G I R
No of Errors
Runtime descriptions (nametabs) are written inactively, but the steps required for activation are initiated during this phase. Generation of imported objects Import of all data including table entries. Post-import methods are required activities (such as the execution of an ABAP program) that rely on transported data.
4 18 1 4
Background Take the following steps to prevent transport errors: SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
31
Transports - Ensure that the development, quality assurance, and production systems are synchronized. This allows you to detect syntax errors in the development system before you release transport requests. Transaction SREPO allows you to compare the repository in different systems. See SAP Note 1368474 for more details on the transaction SREPO. - Use transports of copies to send objects from the development system to the quality assurance system. If the transport of copies results in a transport error, you can fix the original transport request in the development system before it is released. Only the original transport request is sent to the production system. - Most transport errors are caused by missing dependent transport requests, for example, if a table is imported but a required data element is not yet available. These types of errors can be avoided if you bundle transport requests into releases and import all transport requests simultaneously using the “Import ALL” or “Import Project ALL” procedure. - The custom development management cockpit in SAP Solution Manager includes a new feature, “CTS Analysis” as of release 7.1, which enables you to check the dependent objects for a list of transport requests. If dependent objects are different in the production system, or if they are missing, a warning is issued. You can prevent most transport errors using this tool.
5.7.1 Transport Error Resolution Time We calculated the error resolution time for each transport error. This is the time difference between the first import with a return code of 0008 or higher and the first import with a return code of 0006 or lower. Transport errors can sometimes be fixed by other transports. In such cases, a transport resolution time cannot be calculated. TRANSPORT RESOLUTION TIME Transport Resolution Time
No of transports In %
Within six hours Unresolved Transport Errors
5 16.13% 26 83.87%
Evaluation
5.7.2 Most Frequent Transport Errors In this section, we analyzed the most frequent transport errors.
5.7.2.1 && Occurrences: 19 Message Class: PU Upgrade and Transport Log Messages Message Number: 164 && Step: Generation Example: DE1K944079 Short text: The type 'ZDSD_TIPO_ESTRAT' is unknown. Database COMMIT executed Long Text: CAUSE: SYSTEM_RESPONSE: WHAT_TO_DO: Read the long text for the preceding log line.
5.7.2.2 Program &: Syntax error in line & Occurrences: 12 Message Class: PU Upgrade and Transport Log Messages Message Number: 161 Program &: Syntax error in line & Step: Generation Example: DE1K944857 Short text: Program ZVERSD037: Syntax error in line 000031 The Dictionary structure or table 'ZVERSD037_LISTA1' is either not active or does not exist. Long Text: CAUSE: Program &V1& contains a syntax error in line &V2&. The error text is displayed in a log line. SYSTEM_RESPONSE: The specified program is not executed. WHAT_TO_DO: If the log line with the error text is not yet visible, expand the log with Expand or Expand all. To analyze the error in more detail, check the program in transaction SE38 with the function Program -> Check. SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
32
Transports The faulty part of the program is displayed in the program editor. Note: A program may be faulty in the transport target system, despite functioning correctly in the source system. The reason for this is the different environment (missing or different INCLUDE programs or Data Dictionary objects) that the program encounters in the target system. Check whether the error can be corrected by transporting dependent objects.
5.7.2.3 Program &, Include &: Syntax error in line & Occurrences: 7 Message Class: PU Upgrade and Transport Log Messages Message Number: 163 Program &, Include &: Syntax error in line & Step: Generation Example: DE1K944079 Short text: Program SAPLZCONPA002, Include LZCONPA002$01: Syntax error in line 000012 The type 'ZDSD_TIPO_ESTRAT' is unknown. Long Text: CAUSE: Program &V1& has a syntax error in line &V3& of INCLUDE program &V2&. The error text is displayed in a log line. SYSTEM_RESPONSE: The specified program is not executed. WHAT_TO_DO: If the log line with the error text is not yet visible, expand the log with Expand or Expand all. To analyze the error in more detail, check the program in transaction SE38 with the function Program -> Check. The faulty part of the program is displayed in the program editor. Note A program may be faulty in the transport target system, despite functioning correctly in the source system. The reason for this is the different environment (missing or different INCLUDE programs or Data Dictionary objects) that the program encounters in the target system). Check whether the error can be corrected by transporting dependent objects.
5.7.2.4 Field &: Component type or domain used not active or does no Occurrences: 7 Message Class: DT Table activation (incl. indexes) Message Number: 242 Field &: Component type or domain used not active or does not exist Step: Activation Example: DE1K945070 Short text: Field LIST_IND: Component type or domain used not active or does not exist Field TPEXP_ORIGE: Component type or domain used not active or does not exist Long Text: CAUSE: The corresponding row type for a field or the underlying domain for for a data element is not active in the Dictionary or does not exist. SYSTEM_RESPONSE: WHAT_TO_DO: Go to the type maintenance or domain maintenance screen and activate the object or create the object and activate it.
5.7.2.5 Nametab for table & cannot be generated Occurrences: 7 Message Class: DT Table activation (incl. indexes) Message Number: 005 Nametab for table & cannot be generated Step: Activation Example: DE1K945070 Short text: Nametab for table ZENRPP103_LISTA cannot be generated Table ZENRPP103_LISTA was not activated Long Text: CAUSE: The runtime object (nametab) of the table could not be generated. SYSTEM_RESPONSE: WHAT_TO_DO: Details about the error can be found in the log. Possibly try again to activate the table.
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
33
Transports
5.7.2.6 $ $ could not be activated Occurrences: 7 Message Class: DO Dictionary: Mass activation of domains and data elements Message Number: 519 $ $ could not be activated Step: Activation Example: DE1K945070 Short text: Aj.p/pes. ZTEN_PERFPROC could not be activated (E- Tabela ZTEN_PERFPROC n#o # tabela de banco de dados => inapropriada como m#todo sel. ) Long Text:
5.7.2.7 &1 &2 in pl.version &3 does not exist -> activation not poss Occurrences: 3 Message Class: 5W Messages for PD (Particularly Workflow) Message Number: 613 &1 &2 in pl.version &3 does not exist -> activation not possible Step: XPRAs Example: DE1K945354 Short text: S 50001701 in pl.version 01 does not exist -> activation not possible No activation of relationship to object S 50001775 in pl.version 50001775 (cl.700) Long Text:
5.7.2.8 No activation of relationship to object &1 &2 in pl.version Occurrences: 3 Message Class: 5W Messages for PD (Particularly Workflow) Message Number: 612 No activation of relationship to object &1 &2 in pl.version &2 (cl.&4) Step: XPRAs Example: DE1K945354 Short text: No activation of relationship to object S 50001701 in pl.version 50001701 (cl.700) S 50001701 in pl.version 01 does not exist -> activation not possible Long Text: CAUSE: The system has transported a relationship to the specified object of an object currently being activated. However, the relationship cannot be activated. The problem is usually caused by the related object not being available in the target system. SYSTEM_RESPONSE: The object is transported correctly but without the specified relationship. WHAT_TO_DO: Make sure that the related object is available in the target system, or that it is included in the same transport request as the current object, before you repeat the transport. If the related object is not required or must not be available in the target system, no further action is required on your part.
5.7.2.9 Base table & of the lock object is not active Occurrences: 1 Message Class: DI Dictionary messages: Indexes Message Number: 751 Base table & of the lock object is not active Step: Activation Example: DE1K945714 Short text: Base table ZTEN_EXPCOCKPIT of the lock object is not active Lock object EZTEN_EXPCOCKPIT not activated Long Text: CAUSE: The lock object uses a table as base table which is not active in the ABAP/4 Dictionary. SYSTEM_RESPONSE: The action was cancelled. WHAT_TO_DO: Either ensure that the corresponding table is active in the ABAP/4 Dictionary or remove the table from the list of base tables of the lock object.
5.7.2.10 Table & is not a database table => not suitable as selection Occurrences: 1 Message Class: DH DD: Messages for search helps Message Number: 118 Table & is not a database table => not suitable as selection method Step: Activation Example: DE1K945070 Short text: Table ZTEN_PERFPROC is not a database table => not suitable as selection method SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
34
Transports Search help ZTEN_PERFPROC was not activated Long Text: CAUSE: Table &V1& is assigned as selection method for the elementary search help in question. Table category &V2& of this table, however, indicates that it is not a database table. The table is therefore not suitable as the selection method of a search help. SYSTEM_RESPONSE: INCLUDE DDDOC_CANCEL WHAT_TO_DO: Enter a database table or a view as selection method for the search help. INCLUDE DDDOC_SHLP_HANDLE OBJECT DOKU ID TX
5.8 Time Profiles for Imports There are different import strategies. For example, you can import transports into production continuously, once a week on Fridays, or only in the evening (when there is no load on the system). The following data helps you determine whether your strategy has been executed. The first diagram shows the average workload each day. The second diagram shows the number of imports in one day over the last six months.
Evaluation No daily import window is defined. Transports are imported continuously throughout the day. SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
35
Transports
Recommendation Schedule an import window for a time at which system usage is low to minimize the impact of the transports on productive users. If transports are moved to production at times of high or moderate system usage, normal business activities may be disrupted. If transports are imported at times of high system usage, this causes an immediate change to the dictionary, repository or even customizing objects, impacting transactions that are being used at a certain point in time. This could lead to transactions terminating suddenly with short dumps or, in the worst case, a system breakdown.
5.8.1 Imports per Weekday
Evaluation Transports are imported every day of the week. Recommendation Within your release management strategy, define one day of the week on which system usage is low and requests can be imported to the systems. Transports should be classified as emergency and nonemergency transports. Emergency transports are those that could resolve critical issues for production operations. The scope of daily transports should be limited to the resolution of critical production issues. For non-emergency transport requests, you should determine a day and time when system usage is low and they can be imported to the production system.
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
36
Transports
5.8.2 Imports per Month
Evaluation Transports were imported in every month of the analysis period. Recommendation Release cycles should be scheduled for project and non-project transports. All project transports should be imported in a maintenance window that can occur quarterly or throughout the duration of the project. Nonproject transports (maintenance and emergency transports) should be imported on a weekly or monthly basis for maintenance. Only emergency corrections should be considered for daily import.
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
37
Testing and Runtime Errors
6 Testing and Runtime Errors
This chapter is rated YELLOW. The reason for this rating can be found in the overview section below:
OVERVIEW OF RATINGS Rating
Check Performed Testing Time Refresh of the Quality Assurance System Number of Runtime Errors per Day
6.1 Testing Time We analyzed the times at which transports were exported from the development system and imported to the productive system. The time difference represents the time spent in the quality assurance system, that is, the time allocated for testing. The table below provides an overview of transports exported from the DEV system and imported into the PRD system over the last six months, categorized according to the time spent in the QA system before being transported into production. We always count the time of the last import. TESTING TIME Time spent in Quality Assurance System
Number of transports
Transport requests in %
1 197 265 329 222 239
0,1 15,7 21,1 26,3 17,7 19,1
Longer than one quarter Longer than one month Longer than one week Longer than one day Shorter than one day Shorter than one hour
Evaluation Many requests spend less than one day in the quality assurance system. These transport requests cannot be tested sufficiently. Recommendation Introduce mandatory testing procedures. Only changes that are tested sufficiently should be imported into production. The faster a transport request takes to transition from development to production indicates that the amount of testing is minimal. This makes the production system vulnerable to untested changes and may also result in production downtimes. Background Introduce segregation of duties. This means that the developer and the tester should be different people. Each change should be tested either by the requestor or by a separate testing organization. This forces the developer to document the change so that it can be tested by another person. The SAP testing methodology foresees different test types: unit test, integration test, and user acceptance test. In addition, critical changes require a regression test of the most critical business processes. This is only possible if changes are bundled in releases.
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
38
Testing and Runtime Errors
6.2 Refresh of the Quality Assurance System In this check, we analyzed the last time at which the production system was copied to the quality assurance system. Evaluation The production system was not copied to the quality assurance system within the last 12 months. Recommendation Refresh the quality assurance system regularly by copying the production system. This increases the value of testing results due to the availability of quality transactional data. It also helps to identify potential issues prior to the import into production. This is relevant to both production support and new functional development. Background A system copy from the production system to the quality assurance system synchronizes the software configuration between the two systems. Furthermore, it provides current test data in the quality assurance environment. If you only want to provide test data, you can use the SAP Test Data Migration Server. It allows you to copy a reduced set of production data to the test systems. For more information, see http://www.sap.com/tdms.
6.3 Number of Runtime Errors per Day In this check, we analyzed the runtime errors in your productive system. We checked the period for which data was available and calculated the average number of ABAP dumps each day.
Average number of dumps each day: 102 Evaluation The average number of ABAP dumps per day is relatively high. Recommendation The number of runtime errors is an important indicator for the quality and stability of your productive system. Reduce the number of runtime errors by performing root cause analysis and assign respective teams based on the type of dumps. The section “Type of Runtime Errors” gives more details regarding the different areas where the short dumps have occurred most frequently. Make sure that during the regular testing cycles (production support or project) the systems for unit and integration testing are monitored closely for runtime errors. By actively monitoring these testing environments, many of the runtime errors can be mitigated before the changes move into the production system.
Background Dumps are reorganized by reorganization program RSSNAPDL. By default, this job runs every day and deletes all short dumps that are older than 28 days (as of basis release 7.00). For more information, see SAP Note 11838.
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
39
Testing and Runtime Errors
6.4 Type of Runtime Errors In the following table, we categorized the ABAP dumps. TOP 10 ABAP DUMPS Error
Number Description
TIME_OUT CALL_FUNCTION_SEND_ERROR RAISE_EXCEPTION RFC_ATTACH_GUI_FAILED MESSAGE_TYPE_X
885 159 104 53 53
TSV_TNEW_PAGE_ALLOC_FAILED
50
MEMORY_PGFREE_FAILED SYSTEM_CANCELED SAPSQL_ARRAY_INSERT_DUPREC
43 35 34
LIST_TOO_MANY_LPROS
28
Time limit exceeded. &ZD (I/O error) Exception condition "&P1" raised. Start 'sapgui' failed. The current application triggered a termination with a short dump. No more storage space available for extending an internal table. Error when releasing a block in the SAP paging The program &AP was terminated manually. The ABAP/4 Open SQL array insert results in duplicate database records.records in the data base. No further list processing possible.
Category User Others Appl Others Appl IT IT IT Appl
Appl
Evaluation In the table above, we classified the Runtime Errors into different categories. This helps identify the root causes. For example, runtime errors of type “Appl” typically arise due to poor code in the system. Recommendation The number of runtime errors is an important indicator for the quality and stability of your productive system. Monitor the number of ABAP dumps regularly. Reduce the number of runtime errors by identifying the root causes. The categories for the errors and the recommended action are explained below: - Appl - Runtime errors due to poor coding. These can be avoided by appropriate testing procedures. All transports need to be tested thoroughly in the quality system to ensure that runtime errors are resolved prior to the import into production system. You should also develop a comprehensive testing strategy based on the E2E Integration Testing functionality of Solution Manager. Examine the link below for more details on E2E Integration Testing: http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000725177&_SCENARIO=01100035870 000000202&. - Transport - The runtime errors are caused by imports at a time of high system activity. Schedule a daily import window at times of low system usage in order to minimize the impact of the transports on productive users. If transports are moved into production at times of high or moderate system usage, normal business activities may be disrupted. For more information, see the “Time Profiles for Imports” section. - IT - Technical system problems such as database and operating system. These errors indicate problems in system administration. Schedule a CQC for Business Process Performance Optimization service and Remote Performance Optimization for analysis of response times and optimal usage of hardware resources. - User – These could be caused by incorrect end-user handling of an application, such as entering incorrect selection criteria. This indicates that adequate end user training has not been done. Proper documentation of business processes for end users and class room trainings is required in order to overcome end-user handling. - Auth – These could be caused due to missing authorizations. Identify the root cause for the missing authorizations and design an efficient security strategy to overcome these issues. You could also leverage the CQC for Security Optimization to analyze and improve security in your SAP environment. The explanation for the other categories is as below: - RFC - Dumps in Remote Function Calls. - Others - Could not be assigned to one of the above groups.
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
40
Transport Landscape Consistency
7 Transport Landscape Consistency
This chapter is rated RED. The reason for this rating can be found in the overview section below:
OVERVIEW OF RATINGS Rating
Check Performed Transport Tracking Open Transport Requests in Development Parked Transport Requests Transport Sequence Violations
7.1 Transport Tracking In this check, we analyzed the number of transport requests that were imported to or exported from DEV during the analysis period and that have already been imported into PRD, as well as the number of transport requests that are still in transition. System
Number of Requests (analysis period)
Requests not in PRD
1834 0 1359
531 0
DEV (DE1) QAS (QE1) PRD (PE1) NUMBER OF REQUESTS IN PRD BUT NOT IN DEV Category
Number
Requests in PRD but not in DEV
2
7.1.1 Requests Deleted from the Queue of QAS In this table, we checked how many transport requests were deleted from the QAS import queue in the last six months. To do so, we counted the transport requests that were exported or imported into DEV but that exist neither in QAS nor in the QAS import queue. The results are valid only if there is no transport system between DEV and QAS and no external tool is used to manage the import queues. Number Reason 498 Requests deleted from the import queue of QAS Evaluation Many transport requests have been deleted from the import queue of QAS. This indicates that all transport requests exported from the development system have not been imported into the quality system. Recommendation Transport requests should not be deleted from the import queues. If they contain errors, these errors should be fixed with a follow-up transport. Both transport requests should then be imported together to the next system of the transport landscape. You can check the canceled transport requests in the system in which the data was collected. They are listed in the table /SDF/CMO_T_46Q.
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
41
Transport Landscape Consistency
7.2 Open Transport Requests in Development In this check, we analyzed the open transport requests in the development system. AGE OF OPEN TRANSPORT REQUESTS IN DEVELOPMENT Age
Number of Requests
Newer than 6 months
9
Evaluation The number of old open transport requests is moderate. You do not have a lot of temporary or incomplete development tasks. The number of open transport requests in the development system indicate the number of ongoing changes. You can also consider the number of objects in the transport requests. For this purpose, we have listed the ten largest open transport requests: BIGGEST OPEN TRANSPORT REQUESTS IN DEVELOPMENT Request
Type
User
Date
Short Text
No. of Objects
DE1K947068 DE1K947403 DE1K946642 DE1K945017 DE1K908745 DE1K944731 DE1K945755 DE1K947582 DE1K943902
K K K K K K K K K
BASIS PULMER BELUGA PULMER BELUGA HECOS BASIS BASIS PULMER
20100609 20100623 20100520 20100309 20100309 20100218 20100412 20100630 20100104
Bug Fixing ZREORG DDIC Elements for ZREORG DB Monitor Ext. Legal Changes Adjustment SP06 Revision Test SD_P_9182734 Verification -> SD_P_9182734 SD_P_9182734_v3
22 17 9 7 3 3 3 3 2
7.3 Parked Transport Requests In this check, we analyzed whether there are old entries in the import queues of QAS and PRD. Old buffer entries can result in problems. AGE OF BUFFER ENTRIES IN QAS Age
Number of Requests
AGE OF BUFFER ENTRIES IN PRD Age
Number of Requests
Evaluation There are only a few or no transport requests in the import queues that are older than six months. It is good practice to forward transport requests quickly to QAS and PRD. Background Transports that are parked in the import buffer of QAS and PRD cause inconsistencies within the transport landscape. Changes should be quickly forwarded from DEV to QAS and PRD in order to keep the transport landscape consistent. If transport requests are parked for a long time in the import buffers of QAS or PRD before they are imported, they SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
42
Transport Landscape Consistency might not work anymore because the context in which they were developed might have changed in the meantime. Furthermore, the risk of overtake and bypassing situations increases if transport requests stay in the import buffer for a long time. Finally, a large import buffer in production with many old transport requests represents a major risk for the production system. If these are imported accidentally, the system will be aborted and must be restored. Transports that were applied accidentally are one of the main reasons for system restores. Transport Strategy The TMS setting “Transport Strategy” takes effect when transport requests are cleaned up from the import queues. This setting can be found in transaction STMS -> Overview -> Transport Routes. In the Transport Route diagram, click one of the systems. The following settings are possible: Mass Transports By default, import option "Leave transport request in queue for later import" is activated. This import option causes requests that have been imported as single transports to be imported to the correct order during the next global request import. This option is useful if you have to make preliminary imports for individual requests. This prevents older objects from being imported during the next regular import of all the requests (referred to as a sequence violations problem). Single Transports By default, import option "Leave transport request in queue for later import" is deactivated. If you supply a system with single transports only, this option is not useful since the requests remain in the queue after the import and have to be manually deleted from the import queue. The toolbar in the import queue changes according to the requirements of the single import strategy (for example, it contains a selection function). In the import queue display, the "Start Import" function is only available if you have selected one or more projects using the filter function. This prevents you from accidentally importing all the requests in the queue. Note: If "Change Request Management" is active, select the "Single transports" option. Workflow-Controlled Transports Transport proposals are created automatically when requests are exported. The import options correspond to those for single transports. Imports become linked to the processing of transport proposals in the TMS work list. A warning appears in the import queue if you try to perform transports without using the transport workflow.
7.4 Transport Sequence Violations All transport requests must be imported into QAS and PRD in the same order in which they were exported from DEV. If sequence violations occur, outdated object versions may be reactivated in PRD. We analyzed the current sequence violations for all transport requests that were imported into PRD over the last six months. We only compared transports containing the same objects. We counted the overtakers and bypassed transports, along with the objects that were overwritten by older versions in the last six months. Example Time System 1 | T1 | T2 V T3
System 2 T2 T3 T1 transports with Import Queues -> Single Transports: http://help.sap.com/saphelp_nw04/helpdata/en/54/b3fc377cb5be5ae10000009b38f842/frameset.htm.
8.1.2 CTS projects Transport requests are bundled in CTS projects. This ensures that all transport requests that logically belong together are imported together and in the correct sequence into production.
8.1.3 Preliminary Transports Urgent corrections are sent to production as preliminary transports. They are imported again into production with the next regular import to ensure the correct transport sequence.
8.1.4 Transports of Copies Changes are sent from the development system to the test system by means of transport copies. Only if the test was successful, is the original transport request then exported. This significantly reduces the number of transport requests, and thus, the number of object versions in the production environment.
8.1.5 Critical Object Approval Critical objects that often caused problems in the past can be maintained in a table. If these objects are changed, special approval is required before the corresponding transport request can be imported into the test system.
8.2 Software Change Management Features in SAP Solution Manager Business and IT departments put forward change requests, which in turn lead to the need to make software changes to SAP and non-SAP solutions. To manage these change requests during the design, build, and test phase, SAP customers can make use of the following SAP Solution Manager capabilities.
8.2.1 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, phase transitions, and managing the transports of changed SAP objects between the SAP systems involved. You have a high degree of freedom to adjust the design of the change process to your individual needs. Change Request Management incorporates our 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.
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
45
Appendix
8.2.2 Quality Gate Management Quality Gate Management is an easy-to-setup function in SAP Solution Manager that provides governance support when dealing with SAP 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 a system landscape, for example, the development landscape to the subsequent system landscape based on the integrated SAP Transport Management system. QGM enables you to document why a quality gate is 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 to the chain of system landscapes. This results in an improved quality management process when compared to processes that are still managed by MS Excel or on paper, which is still the case in several companies.
8.2.3 Enhanced Change and Transport System (CTS+) With the availability of multiple development workbenches supporting multiple development languages including ABAP, Java, C++, and .NET, the need for advanced transport mechanisms increased. CTS+ allows you to transport objects from various development workbenches between SAP system landscapes. You benefit from an increased quality when transporting non-ABAP objects, which results in faster stabilization of the SAP system landscapes involved.
8.2.4 SAP Test Workbench As the central platform for test management, the Test Workbench delivers all major functions to handle every aspect of test management for SAP-centric solutions, using either its own tools or those of integrated partner solutions. Organizing tests with the Test Workbench improves the quality of changes and reduces the number of emergency changes.
SAP Guided Self Service - Transport Execution Analysis,
16.07.2010
46
View more...
Comments
