Symptom
You need to prepare one of your systems for which a SAP Support Service has been scheduled.
Other terms
SAP Support Services, Safeguarding, Solution Management Optimization Services, Empowering, SMO, SMA, Standard Support
SDCC, RTCCTOOL, ASM, ST14, SQLR, ST-PI, ST-A/PI, SQL Trace, ABAP Trace,
SAP Solution Manager, Service Preparation
SAP GoingLive Check, SAP GoingLive Functional Upgrade Check, SAP OS/DB Migration Service, SAP Codepage Conversion Check, SAP EarlyWatch Alert, SAP EarlyWatch Service, SAP Solution Management Assessment
SAP Business Process Performance Optimization, SAP Customer Program Optimization, SAP Remote Performance Optimization, SAP SQL Statement Optimization, SAP Business Process Management, SAP Interface Management, SAP Data Management, SAP System Administration, SAP Upgrade Assessment, Technical Integration Check, Feasibility Check
Reason and Prerequisites
SAP recommends to execute SAP Support Service Sessions in SAP Solution Manager. To enable the delivery of the planned SAP Support Service session you wish to prepare your managed SAP System and your SAP Solution Manager system accordingly. This note provides you with a central overview of the preparation steps required for ABAP stacks.
Appendix A provides an overview of SAP Notes with recommendations specific to products such as BW, SCM etc.
Appendix B provides an overview of SAP Notes with further recommendations, specific to service types.
Solution
Services
An overview of support offerings and related service types can be accessed via service.sap.com/supportofferings.
SAP Solution Manager
SAP Note 1170668 gives an overview over the role of SAP Solution Manager in Remote Service Delivery.SAP Note 1172939 describes which technical prerequisites must be met to ensure the service delivery readiness of your SAP Solution Manager system.
Managed systems
To ensure that SAP can deliver a service for each SAP System that you wish to analyze, the prerequisites listed below must be met.
Timing
To ensure that sufficient data for a meaningful analysis is available on the day of the session, the preparation steps listed below should be checked ca 4-6 weeks before the agreed session date. This ensures that any problems can be discovered and resolved in such a way that sufficient data will be available on the day of the session.
Questionnaires, Quick Sizer
For some service sessions questionnaires need to be filled in. Part of the analysis for such sessions is based on the information in the questionnaires, therefore it is important that these are filled in accurately. They should be returned ideally 1-2 weeks prior to the agreed session date so that any open questions can be adressed prior to the start of the actual service session.
The Quick Sizer is a web based tool designed to assist with the sizing of SAP Business Suite. It has been developed by SAP in close cooperation with all platform partners and is free of cost.
For some sessions a Quick Sizer project is needed to contribute to the planned analysis. As with the questionnaires the project should be created and filled ideally 1-2 weeks prior to the session so that any open questions can be addressed in good time before the session starts.
For more information see service.sap.com/quicksizer.
Where questionnaires or Quick Sizer projects are needed for a session you will be advised of this when you arrange the session date.
EarlyWatch Alert
EarlyWatch Alert is required for delivery of all run phase remote services, such as EarlyWatch Check, GoingLive Verification etc.
It is a free service for the preventative monitoring of the performance of SAP Systems which automatically and regularly collects data on your SAP system. As it provides you with continuous service reports it considerably reduces the risk of system bottlenecks or failures.
You should activate EarlyWatch Alert for all productive SAP systems, to be processed in your own SAP Solution Manager system.
A Best Practice document on how to set this up can be found in the SAP Service Marketplace at service.sap.com/solutionmanagerbp.
For further information please review the information provided at service.sap.com/EWA as well as SAP Note 1257308.
Common steps in ABAP stacks
Connections
If hardware is shared between several SAP systems or a form of virtualization is used please inform the person delivering the session as this can affect the analysis.
Recommendations given in the service will depend on the description of the exact hardware setup.
SV-SMG-MAI-APR The colleagues in this component can release the required download basket in in SAP Service Marketplace, if a SAP Solution Manager system (and so Maintenance Optimizer) are temporarily unavailable, and software is urgently needed.
Overview of SAP Notes with recommendations specific to Products:
SAP Note 320903 Supply Chain Management ( SCM)SAP Note 160777 Business Information Warehouse (BW)SAP Note 1258585 SAP Customer Relationship ManagementSAP Note 1295142 SAP Remote Services for SAP SRMSAP Note 617604 SAP Remote Services for SAP PI/XISAP Note 1498779 Preparing Java-based systems for Support ServicesSAP Note 1251022 SAP Remote Services for MDM: Technical Prep...SAP Note 738676 Non ABAP components
Appendix B
Overview of SAP Notes with recommendations specific to Services:
SAP Note 1329189 GoingLive Check for SolutionsSAP Note 1320620 Prerequisites for GoingLive Check for SolutionsSAP Note 696478 SAP Security Optimization: Preparation & additional infoSAP Note 1323405 Technical Preparation of a GO, BPPO and IV serviceSAP Note 1159758 Data Volume Management: Central Preparation NoteSAP Note 1306163 SAP Downtime Assessment PrerequisitesSAP Note 1077981 SAP Upgrade Assessment Preparation NoteSAP Note 1274306 SAP Solution Transition Assessment - PreparationSAP Note 1320940 Prerequisites for CQC service: BPA and BPMSAP Note 1318148 SAP Custom Code Change Impact Analysis - PreparationSAP Note 1330674 SAP Custom Code Maintainability CheckSAP Note 1074808 SAP Change and Transport Analysis Session: RequirementsSAP Note 1041351 FAQ - Solution Manager Preparation Service (SMPS)SAP Note 350011 GoingLive Service - Preparations for BPS Benchmark CheckSAP Note 1149742 SAP CQC Going Live Support
Appendix CSAP Note 352081 Additional service-relevant functions for MaxDBSAP Note 145316 DB2-z/OS: Preparations for SAP Support Services
You need to prepare one of your systems for which a SAP Support Service has been scheduled.
Other terms
SAP Support Services, Safeguarding, Solution Management Optimization Services, Empowering, SMO, SMA, Standard Support
SDCC, RTCCTOOL, ASM, ST14, SQLR, ST-PI, ST-A/PI, SQL Trace, ABAP Trace,
SAP Solution Manager, Service Preparation
SAP GoingLive Check, SAP GoingLive Functional Upgrade Check, SAP OS/DB Migration Service, SAP Codepage Conversion Check, SAP EarlyWatch Alert, SAP EarlyWatch Service, SAP Solution Management Assessment
SAP Business Process Performance Optimization, SAP Customer Program Optimization, SAP Remote Performance Optimization, SAP SQL Statement Optimization, SAP Business Process Management, SAP Interface Management, SAP Data Management, SAP System Administration, SAP Upgrade Assessment, Technical Integration Check, Feasibility Check
Reason and Prerequisites
SAP recommends to execute SAP Support Service Sessions in SAP Solution Manager. To enable the delivery of the planned SAP Support Service session you wish to prepare your managed SAP System and your SAP Solution Manager system accordingly. This note provides you with a central overview of the preparation steps required for ABAP stacks.
Appendix A provides an overview of SAP Notes with recommendations specific to products such as BW, SCM etc.
Appendix B provides an overview of SAP Notes with further recommendations, specific to service types.
Solution
Services
An overview of support offerings and related service types can be accessed via service.sap.com/supportofferings.
SAP Solution Manager
SAP Note 1170668 gives an overview over the role of SAP Solution Manager in Remote Service Delivery.SAP Note 1172939 describes which technical prerequisites must be met to ensure the service delivery readiness of your SAP Solution Manager system.
Managed systems
To ensure that SAP can deliver a service for each SAP System that you wish to analyze, the prerequisites listed below must be met.
Timing
To ensure that sufficient data for a meaningful analysis is available on the day of the session, the preparation steps listed below should be checked ca 4-6 weeks before the agreed session date. This ensures that any problems can be discovered and resolved in such a way that sufficient data will be available on the day of the session.
Questionnaires, Quick Sizer
For some service sessions questionnaires need to be filled in. Part of the analysis for such sessions is based on the information in the questionnaires, therefore it is important that these are filled in accurately. They should be returned ideally 1-2 weeks prior to the agreed session date so that any open questions can be adressed prior to the start of the actual service session.
The Quick Sizer is a web based tool designed to assist with the sizing of SAP Business Suite. It has been developed by SAP in close cooperation with all platform partners and is free of cost.
For some sessions a Quick Sizer project is needed to contribute to the planned analysis. As with the questionnaires the project should be created and filled ideally 1-2 weeks prior to the session so that any open questions can be addressed in good time before the session starts.
For more information see service.sap.com/quicksizer.
Where questionnaires or Quick Sizer projects are needed for a session you will be advised of this when you arrange the session date.
EarlyWatch Alert
EarlyWatch Alert is required for delivery of all run phase remote services, such as EarlyWatch Check, GoingLive Verification etc.
It is a free service for the preventative monitoring of the performance of SAP Systems which automatically and regularly collects data on your SAP system. As it provides you with continuous service reports it considerably reduces the risk of system bottlenecks or failures.
You should activate EarlyWatch Alert for all productive SAP systems, to be processed in your own SAP Solution Manager system.
A Best Practice document on how to set this up can be found in the SAP Service Marketplace at service.sap.com/solutionmanagerbp.
For further information please review the information provided at service.sap.com/EWA as well as SAP Note 1257308.
Common steps in ABAP stacks
Connections
- 1. Access to your ABAP system
Access often is already needed during the preparation phase of the session. Please ensure that a connection of the type R/3 support is available, ideally ca 4-6 weeks before the session date.
SAP Note 812732 provides more information about this connection type.
Logon information can be securely stored as per SAP Note 508140.
Access to systems is greatly simplified where the Line Opener Program ( LOP ) is used, as this allows access without extra interaction with a contact person at customer side.
More details on connection types and the use and advantages of LOP be found at service.sap.com/serviceconnection.
If more assistance is needed a message can be opened in component XX-SER-NET-HTL.
Access from your ABAP system to SAP
To be able to use RTCCTOOL, and to some extent also SDCCN, a connection to SAP is necessary. Please ensure that destination SAPOSS is checked and configured, ideally ca 4-6 weeks before the session date.
SAP Note 33135 provides information about how to maintain SAPOSS, via transaction OSS1. If more assistance is needed a message can be opened in component XX-SER-NET.
From your ABAP system to your SAP Solution Manager
To ensure that SDCCN in the managed system can communicate with your SAP Solution Manager, the *BACK destination must be maintained in SDCCN, and must test ok in SM59.
If more assistance is needed a message can be opened in SV-SMG-SYS.
- 2. Installation number
Installation number and system ID are the key for all service administration, both at SAP and in a customer SAP Solution Manager.
It is therefore vital that this information is up to date in both the managed system itself, as well as in the SAP Solution Manager.
Any change must be reflected in System Landscape ( SMSY ) in the connected SAP Solution Manager, as well as the corresponding logical components and solutions.
Changes should be updated as soon as possible in all areas.
Updated Solutions also need to be transferred to SAP quickly, so that administration relevant information regarding your solution is updated.
This information will be needed, as already ordered services have to be adjusted to reflect the new installation numbers.
If service sessions have been agreed already, contacts at SAP should be advised of a new installation number as soon as possible, as the necessary adjustments have to be made manually.
This will ensure that service plans can be updated correctly in the customer SAP Solution Manager.
If you need help implementing the installation number / license key inside a system, you can open a message in XX-SER-LIKEY.
If you need help updating informatin in SMSY in your SAP Solution Manager you can open a message in SV-SMG-SYS.
- 3. ST-PI and support packages Addon ST-PI and the corresponding
support packages contain the Service Data Control Center (SDCCN) which
controls the collection and transfer of data analysed during a service session.
They also contain various function modules needed for data collection.
Additionally they contain reports which are executed by function modules during
data collection. Details regarding the content can be found in SAP Note
539977 .
Please note that only SDCCN should be used for data collection, rather than SDCC (older version). All developments since 2005 have been made for SDCCN only. Only SDCCN can make full use of the changes contained in ST-PI and the support packages. SAP Note 763561 contains answers to frequently asked questions as well as a guide on the functionalities.
If you need help regarding SDCCN you can open a message in component SV-SMG-SDD.
- 4. ST-A/PI
Addon ST-A/PI contains data collectors which contribute to data collections with SDCCN. It also contains additional functionalities for separately analysing and gathering application based data, as well as various trace tools.
Another important feature is report RTCCTOOL.
This can be run either directly or from within SDCCN, and gives you an overview over many of the steps and tools needed to prepare a system for a session.
It provides a rating depending on whether a step still needs to be addressed or executed, and provides details on what needs to be done.
Using RTCCTOOL can therefore save time when working through the preparation steps.
More details about ST-A/PI can be found in SAP Note 69455.
- 5. Performance Collector
In order to provide data for peformance analysis in service sessions, the performance collector must run, and must store data correctly. The data for each instance must be stored in folder 'week' in ST03.
The following SAP Notes assist in starting the setup of the performance collector:SAP Note 12103 Contents of the TCOLL table [ releases < 640]SAP Note 970449 Contents of TCOLL table in SAP_BASIS 640SAP Note 966631 Contents of TCOLL table in SAP_BASIS 710SAP Note 966309 Contents of table TCOLL in SAP_BASIS 700
If more assistance is needed a message can be opened in BC-CCM-MON-TUN.
Further information on service relevant settings can also be found in SAP Note 144864.
- 6. Hardware utilization
A number of SAP services require information about the hardware utilization of each system in the landscape. To enable a meaningful analysis it is important that the monitoring and recording of this data is set up correctly. Most services need ca 2 weeks worth of data.
Ensure that data for all servers is being collected and can be viewed in ST06N, or ST06 -> Detailed analysis -> Compare recent days. This is required also for servers without SAP instance (e.g. standalone servers, Java).
Ideally this should be carefully reviewed 4-6 weeks prior to the agreed session date. Where problems exist this ensures that they can be recognised and fixed, in time to then still record the required amount of data correctly. If assistance is needed a message can be opened in BC-CCM-MON-OS.
Where the OS Collector is used please bear in mind the following :
- a) The OS collector version should be kept up to date. You can find the
newest version following SAP Note 19227.
- b) If you need to monitor a non SAP system (Java, standalone database) you
can find more information in SAP Note 450741.
- c) Where agents and/or connections are used to monitor and record data
please ensure that they are set up correctly, and that the set up is reflected
in transactions OS07 and AL15.
- d) If you are using IBM Logical Partitions with SPLPARS you need to take
extra steps to configure monitoring correctly. Please refer to SAP Notes
895816 and then 994025 for more information.
If hardware is shared between several SAP systems or a form of virtualization is used please inform the person delivering the session as this can affect the analysis.
Recommendations given in the service will depend on the description of the exact hardware setup.
- 7. Database Monitor
The Database Monitor provides a snapshot of databuffer, cache quality, SQL cache catalog, I/O activity and other values used for the analysis of database performance. As of SAP NetWeaver 7.0 SPS 13, a new platform-independent tool called DBA Cockpit (transaction DBACOCKPIT) is available for all supported databases. This tool replaces many of the old database monitors and transactions.
Should there be any issues with these tools (e.g. no data, negative values), a customer message under component BC-DB-<DB type>-CCM should be created (example: BC-DB-ORA-CCM).
To ensure the counters have enough information for analysis (1 full working day) a restart of the database just before the agreed session date should be avoided.
If the required information is not available, we will not be able to perform a detailed database analysis.
For further details please refer to the following SAP Notes:
In case you use central monitoring system (CEN) for databases: SAP Note 1068204 New monitor template for database monitoring.
Up to SAP Basis 4.6D only: SAP Note 73945 Missing statistical data in database monitor.
- 8. Central Performance History (CPH)
SAP Services are evaluating data from various sources. One source is the central performance history of the CCMS. In order to activate the collection of this data for the SAP Services, please proceed as described in SAP Note 1373735.
- 9. Traces
To enable the safe use of SQL Traces please ensure that the requirements described in SAP Note 1076804 and SAP Note 1132350 are met.
- 10. To enable the safe use of ABAP Traces please ensure that the
requirements described in SAP Note 981919 are met.
- 11. Profile parameters
In order to activate the recording of the required performance data, you need to set the ABAP instance profile parameters as follows:
stat/level = 1
rsdb/staton = 1
For an Oracle database system, you need to set the following parameter in configuration file "init<SID>.ora":
timed_statistics = true
For an Informix database system, you need to set the following parameter in configuration file "/informix/<SID>/etc/onconfig.<dbhost>.<sid>":
WSTATS = 1
- 12. Data Protection
When an SAP Support Service session is executed, no data is changed; data is only displayed according to the user's authorizations, so that service related system analyses can be carried out. Detailed information on data protection in connection with remote connections is available in SAP Note 46902.
Where SAP employees come into contact with customers' personal/secret data these employees are bound to secrecy by §5 according to the German Data Protection Act. More information can be found in SAP Note 35493.
- 13. Authorizations
To execute a service session, SAP requires users who are equipped with suitable authorization profiles.
A user RSDUSER has been constructed, which is described in SAP Note 1405975. The SAP Note also describes which products and session types RSDUSER can be used for.
- 14. In case of Queries
If you have any questions or experience any difficulties during the service preparation, create a customer message under the relevant component.
XX-SER-NET-HTL Setting up the connection from SAP to the
SV-SMG-MAI-APR The colleagues in this component can release the required download basket in in SAP Service Marketplace, if a SAP Solution Manager system (and so Maintenance Optimizer) are temporarily unavailable, and software is urgently needed.
- 15. Service Reports in Service Messages
When a session is completed the service consultant uploads the report so it is available in a service message in the SAP Service Marketplace.
An SUser can be nominated to be the main recipient for a service message if this SUser is based in the customer number which owns the analysed system. A feedback form is provided in the service message containing the session results. To be able to fill in the feedback an SUser must have the authorisation ACCESS_SERVICE_MESSAGES for the customer number of the analysed system. If you experience problems accessing a report for a session please inform the service consultant. He can open an internal message, following the information in internal SAP Note 975252.
Overview of SAP Notes with recommendations specific to Products:
SAP Note 320903 Supply Chain Management ( SCM)SAP Note 160777 Business Information Warehouse (BW)SAP Note 1258585 SAP Customer Relationship ManagementSAP Note 1295142 SAP Remote Services for SAP SRMSAP Note 617604 SAP Remote Services for SAP PI/XISAP Note 1498779 Preparing Java-based systems for Support ServicesSAP Note 1251022 SAP Remote Services for MDM: Technical Prep...SAP Note 738676 Non ABAP components
Appendix B
Overview of SAP Notes with recommendations specific to Services:
SAP Note 1329189 GoingLive Check for SolutionsSAP Note 1320620 Prerequisites for GoingLive Check for SolutionsSAP Note 696478 SAP Security Optimization: Preparation & additional infoSAP Note 1323405 Technical Preparation of a GO, BPPO and IV serviceSAP Note 1159758 Data Volume Management: Central Preparation NoteSAP Note 1306163 SAP Downtime Assessment PrerequisitesSAP Note 1077981 SAP Upgrade Assessment Preparation NoteSAP Note 1274306 SAP Solution Transition Assessment - PreparationSAP Note 1320940 Prerequisites for CQC service: BPA and BPMSAP Note 1318148 SAP Custom Code Change Impact Analysis - PreparationSAP Note 1330674 SAP Custom Code Maintainability CheckSAP Note 1074808 SAP Change and Transport Analysis Session: RequirementsSAP Note 1041351 FAQ - Solution Manager Preparation Service (SMPS)SAP Note 350011 GoingLive Service - Preparations for BPS Benchmark CheckSAP Note 1149742 SAP CQC Going Live Support
Appendix CSAP Note 352081 Additional service-relevant functions for MaxDBSAP Note 145316 DB2-z/OS: Preparations for SAP Support Services
No comments:
Post a Comment