SAP Note 91488 - SAP Support Services - Central preparatory note

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

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.

Tools

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.

Collectors and Monitors

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.

           Many services have a preparation phase during which SAP colleagues perform a brief review of the preparation steps. Where complex set ups are being used it can be useful to prepare a high level description which explains the relationship between logical and physical servers.
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

           customer system, or problems when using this connectionXX-SER-LIKEY     Problems regarding installation numbersBC-UPG-ADDON     Problems implementing addons (ST-PI or ST-A/PI)BC-UPG-OCS      Problems implementing support packagesBC-SMG-SYS       Problems related to transaction SMSYSV-SMG-SDD      Problems with the RTCCTOOL or SDCC toolSV-SMG-SER-EWA  EarlyWatch AlertSV-BO-REQ        Request for Remote ServicesSV-BO            General issues with Remote servicesBC-CCM-MON-OS    Problems with the OS collector (ST06)BC-CCM-MON-TUN   Problems with the performance collector (ST03)
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.

Appendix A
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

SAP Note 792941 - Maintenance of transaction SDCC or SDCCN

Symptom
You need to find out how SDCC or SDCCN are maintained for your basis release


Other terms
SDCC, SDCCN, EWA, Earlywatch Alert, SAP Solution Manager, Remote Service
Service Data Control Center


Reason and Prerequisites
You want to collect data for a service session.


Solution
From Spring 2005 a new version of the Service Data Control Center
will be available for basis releases 4.x and 6.x.  With this version
the old transaction SDCC will be replaced by transaction SDCCN.
Until SDCCN is generally released, please make sure that the latest
version of SDCC has been implemented.
This note explains how the Service Data Control Center can be maintained
for your basis release.

I. Service Data Control Center - Transaction SDCC

1. Basis releases 3.x
Basis Releases 3.0D/3.0F

Step 1:  Implement basis transport from Note 597323
         ( contains low SDCC version + function modules + RTCCTOOL)

Step 2:  Update SDCC to version 2.3 with transport from note 178631
Basis Releases 3.1 H + 3.1 I

Implement basis transport from Note 597323
( contains SDCC 2.3 + function modules + RTCCTOOL)

              No ST-PI was developed for basis release 3. x. All these systems must not refresh service definitions from SAPNet R3/Frontend ( OSS) anymore, as this will now cause shortdumps. They must therefore also implement note 712757.

2. Basis releases 4.x

a) Newest version of SDCC 2.4
Implement add on ST-PI 003C*
(contains newest version of SDCC 2.4 + function modules)

Strategy note for ST-PI: 539977
Support Packages for ST-PI: see note 539977

b) Systems without ST-PI must have at least SDCC version 2.3. The old basis transport (contains SDCC 2.3, function modules + RTCCTOOL) must be requested through a message as described in note 560630
They also must switch off Service Definition refreshes, as per note 713674.
Note that this version of SDCC is unable to collect many of the newer function modules.

3. Basis releases 6.x
In basis release 610 SDCC is maintained via basis support package, up until SP41. Ditto for basis release 620, SP45.
In addition  an add on ST-PI was provided,  which contains mostly function modules. The last ST-PI of this type for basis release 6.x was ST-PI 003C_6*. The last support package for ST-PI 003C_6* will be SP3.

II. Service Data Control Centre - Transaction SDCCN

4. Basis releases 3.x
    - not available

5. Basis releases 4.x
For basis releases 4.x  SDCCN is available from add on ST-PI 2005_1.
This contains SDCCN and some function modules. Corrections are contained in support packages for ST-PI.

6. Basis releases 6.x
For basis releases 6.x  SDCCN is available from add on ST-PI 2005_1.
This contains SDCCN and some function modules. Corrections are contained in support packages for ST-PI.

Note 539977 will remain the strategy note for ST-PI, it will advise you when new versions of ST-PI or new support packages for ST-PI become available. As per note 91488, we strongly recommend the use of RTCCTOOL (note 69455), as this tool will automatically advise you of the newest ST-PI versions. Never implement versions of ST-PI which have not been released for general use.

SAP Note 216952 - Service Data Control Center (SDCC) - FAQ

Symptom
For the planned execution of a service session you want to provide SAP with statistical data on the use of the R/3 System. For this purpose you want  to use the Service Data Control Center
(Transaction SDCC)
Operating instructions for SDCC are available in the attached document.
For questions regarding SDCCN please refer to note 763561.
Typical problems with SDCC are described below.


Other terms
RFC Download, EarlyWatch, GoingLive Check, Service, EarlyWatch Alert,
SDCC, Data Collection, Data Transfer, Solution Manager


Reason and Prerequisites
While using the Service Data Control Center (SDCC) for preparation of a pending EarlyWatch, GoingLive check session, or similar, you have encountered  problems


Solution
************************************************************************
Do not import any transport files containing SDCC into systems with R/3 Releases 6* and higher, and/or systems where ST-PI has already been implemented.
************************************************************************

Below you will find a list of answers to question which are often raised in connection with the Service Data Control Center.

1. Q: Which version of the Service Data Control Center should I use, SDCC or SDCCN?

A: SDCCN is the newer version, this should be activated, especially in SAP Solution Manager systems where SDCCN controls the data collections for NON-ABAP satellite systems.
You can find information about SDCCN in SAP Note 763561. SDCC should only be used if it is not possible to activate SDCCN. SAP Note 792941 explains which formats have been used to deliver the Service Data Control Center for the different basis releases.

2. Basic use of SDCC

Q: How does one download a session with SDCC?

A: To use SDCC successfully it is important that the preparations described in note 91488 have been executed. the newest version of SDCC.

a) Call Transaction SDCC. You may be prompted with two pop-ups which ask if you would like to run a Service Preparation Check and/or if you would like to schedule the Automatic Session Manager (see below).
SERVICE PREPARATION CHECK:
This will take you to RTCCTOOL; a tool which lists which notes may yet have to be implemented to obtain the best possible data collection (see note 69455). Skipping this step by hitting the 'No' button means that you can perform a download, but you can not be sure that all necessary notes have been implemented. You may find errors in the data collection message log which could have been avoided.

ASM: This functionality should be scheduled as follows:
AUTOMATIC SESSION MANAGER (ASM)

The easiest method to use SDCC for service data collection and transfer is to use the Automatic Session Manager (ASM). The ASM is a periodic background job which you can trigger as follows:
I. Call Transaction SDCC.
II. In the menu, select 'Autom. Sess. Manager' -> Controls.
III. Enter the start date and time. Please choose a time when the load on the system is low. Please avoid times when other jobs start (i.e choose 00:17:47 rather than 00:00:00). Enter also the ASM period.
Please run the ASM daily.
IV. Select the pushbutton 'Schedule the ASM'.

Use of the ASM is strongly recommended.
EARLYWATCH ALERT SERVICE.
The ASM should be active for this service to be supported sufficiently. Please refer to note 91488 and note 207223 for further details on Earlywatch Alert.

a) A list display containing the session you would like to perform should appear after the first run of the ASM. If the session is not there, use 'Maintenance -> Refresh -> Session overview' to load it. If it still doesn't appear, check below for possible error sources. (questions 2 ff.).

b) If the session you plan to prepare has overall status 'green' it means that either the ASM or a member of the SAP Service Delivery Team have already completed the download for this session. If the status is not 'green' proceed by selecting the session in the list.

c) Then click on the button ' Download'. In the pop-up that appears you can choose to either schedule the download immediately, or at a time of your choice. This should only be necessary if the ASM is not set up.

d) If you have chosen to do the download immediately, a little red and white propeller icon appears while the download is running. You can follow it's progress in the main SDCC message log (Information -> Display message log ) or the session message log (double click on the relevant 'paper' icon at the right hand side of the session overview).

e) After the download is complete, the propeller icon disappears and is replaced (after a screen refresh) by a status light for data collection, data transfer and overall status. Mostly the transfer status is 'green'.The data collection status is occasionally yellow or red. This does not mean that data collection on customer systems has failed altogether (see below for details). In most cases the majority of data has been collected and may well be sufficient to perform a session.

3. SERVICE DEFINITION REFRESH
A regular service definition refresh from SAPNET R/3 Frontend (formerly OSS) is recommended for systems on basis release 4.x with ST-PI, and systems on basis release 6.x. You can refresh the service definitions by calling 'SDCC -> Maintenance -> Refresh ->  Service Definitions'.You should check in the main message log if  this was done successfully.
Systems on basis release 4.x without ST-PI MUST not refresh the Service Definitions from SAPNET R/3 Frontend after April 2004, as this will cause a shortdump.
Note 713674 must be implemented to prevent or repair this.
Also systems on basis release 3.x  MUST not refresh the Service Definitions from SAPNET R/3 Frontend after April 2004, as this will cause a shortdump.SDCC then probably can not be used anymore.
Note 712757 must be implemented to prevent or repair this.
Whenever in the following text a service definition refresh is recommended please check the above text for the appropriate action.

4. Session data have not arrived in the Solution Manager system

Q: I have downloaded data from the satellite system without apparent errors, yet no download can be found in the Solution Manager.

A: Please ensure that you are using the current version of SDCC, at least version 2.3 (see note 91488). Please ensure also that the destination which connects the satellite system to the Solution Manager system is set up according to the instructions in the Solution Manager Installation Guide. Please ensure also that the user in this destination has been given the necessary authorisations (see the Installation Guide as well as note 546283).

5. Q: I have collected data for a session, but when I drill down in the download in the Service Data Viewer I get the error message No logical functional names found for current select'.
Has data been collected?

A: The Service Data Viewer in certain releases (see below) can  not display download data if the server name contains an '_' (underscore). Please check the SDCC message log for this  session. If there is no error message regarding the function module, the data was collected. In this case there should be no problem for the system were the session is performed. Another option is to rename the server, and collect data again when enough data has been accumulated under the new server name.

ST-PI 003D_4* , Support package 30 (610) and  20 (620 ) will contain the new Service Data Viewer 2.0, where this problem has been resolved.

The problem can occur in Release 4.X Solution Tools Plug-In  (Version A, B and C), Release 610 (Basis Support Package 23-29), Release 620 (Basis Support Package 8-19)

6. During a data collection an error message or a warning for a particular
function module appears in the SDCC session log.

Q: Where can I find more information about this?

A: For more information about problems with function modules please refer to note 781680.

7. Q: You try to use SDCC  but fail with a shortdump CONNE_ILLEGAL_TRANSPORT_VERS.

A: Systems on Basis Release 3.x and systems on Basis Release 4.x without ST-PI MUST NOT refresh their Service Definitions from SAPNET R/3 Frontend ( formerly OSS) anymore. If they do, the above shortdump occurs, SDCC can not be used anymore.

Systems on Basis Release 3.x :
Please advise the customer to implement note 712757

Systems on Basis Release 4.x without ST-PI
Please advise the customer to implement note 713674

8. Shortdump CONNE_IMPORT_WRONG_COMP_LENG (Error when attempting to IMPORT object "BDL_TABLE" )

Q: Either when trying to do a Service Definition Refresh (Maintenance -> Refresh -> Servive Definitions), when calling Transaction SDCC, or at the start of each ASM run I get a short dump.

A: Please get the newest version of SDCC implemented, at least version 2.3. The service definitions should be  maintained as described in Question 2 of this note, (SERVICE DEFINITION REFRESH)

9. Faulty initialization of SDCC for R/3 release 4.6D

Q: When I run SDCC on a 4.6D system I get error messages like "RFC dest. CSD : does not exist" and plenty of type 'D' messages in the SDCC Message Log.

A: Please implement the newest version of SDCC, at least version 2.3.

10. "No valid service" in SDCC Message Log

Q: "No valid service" appears in SDCC Message Log during report BDLCOLL. Data collections fails because of this error.

A: It is likely that the service definition tables are not filled. Please ensure that the newest version of SDCC is implemented, at least version 2.3. The service definitions should be  maintained as described in Question 2 of this note, (SERVICE DEFINITION REFRESH)

11. No authorization to perform a 'Service Definition Refresh' (R/3 >=4.6B)

Q: When I try to use 'Maintenance ->Refresh -> Service Definitions' I am prompted with the message ' You do not have customizing permission', and the refresh is not carried out.

A: Please note that Service Definitions may only be refreshed on systems with basis release 4.x with ST-PI, and basis release 6.x. For all other systems please switch off the service definition refreshes as described in notes 712757 or 713674, as appropriate.

For systems where service definition refreshes are allowed please ensure that your user has the profile 'S_SDCC_ADMIN'. Alternatively use transaction SE38 and call report BDLTRA (/BDL/TRA if SDCC has been implemented by ST-PI, see note 91488).

12. Error in RFC destination of SDCC (CSD_PETER) - 4.6B customers only

Q: How can I fix the faulty RFC destination?

A: Please implement the newest SDCC version, at least version 2.3. Before changing the SDCC version, please fix the destination as described in note 209203.

13. Problems with systems on Basis Rel 3.0D

Q: On this system calling SDCC results in syntax errors being displayed.

A: Please implement SDCC version 2.3, and maintain the Service definitions as described in note 712757.

14. No authorization to call SDCC (R/3 release >= 4.6B)

Q: How can I get the missing authorization to call SDCC?

A: If your user contains the profile SAP_ALL, you should have no problems. If you do not have SAP_ALL, please add S_SDCC_ADMIN into the profile list for your user.

15. Q: ASM schedules several SASM_<sessionnr>_COLL_TRANS  jobs for
one session. The jobs interrupt each other, in the SDCC message log you find the error  > collect/transfer jobs for session already active

A: The background job AUTO_SESSION_MANAGER carries out multiple scheduling of sessions.  The job does not query the complete time window asking whether a SASM_*_COLL_TRANS job already exists.
Please refer to the solution in note 624427.

16. RFC breakdown just after the ASM has started

Q: In the SDCC message log the entry " Maximale Anzahl von CPIC-Clients erreiched " oder " Maximum number of CPIC-clients reached " appears. How can this be fixed?

A: There can be several reasons for this:

a) If it happens during the run of the Automatic Session Manager: The default starting time for the ASM was 22:00:00 for SDCC up to version 2.0. So, if the starting time is not changed before the ASM is started, it will attempt a Service Definition Refresh through an RFC call to OSS every day shortly after 22:00. If too many customers attempt such a call at the same time, there can be an overload on OSS. To avoid this, please delete the next ASM job, using 'Autom. Sess. Manager -> Controls (leads you to sm37), and reschedule it at another time. Please choose a time when there is little load on the system.
NOTE: Service definitions should be only be refreshed from OSS where appropriate, as described in Question 2 of this note, (SERVICE DEFINITION REFRESH)

b) Otherwise, the logon group for the RFC destination SAPOSS may not be used properly. To force the system to use it, go into 'SDCC->Maintenance->Customizing->General' and

• if the input box for 'Logon group' is empty, fill in 'EWA'.

• if the input box for 'Logon group' already contains 'EWA', and the box for 'RFC destination' contains SAPOSS, replace SAPOSS with SAPNET_RFC.

17. RFC destination SAPOSS works, it's copy SAPNET_RFC does not work

Q: I get connection errors in SM59 RFC destination SAPNET_RFC. Therefore data transfer to SAP or service definition refreshes fail.

A: Please note that only systems on basis release 4.x with ST-PI and systems on basis release 3.x  may refresh service definitions from SAPNET R/3 Frontend (OSS). For all other systems please check Question 2 of this note, (SERVICE DEFINITION REFRESH)

SAPNET_RFC is a copy of SAPOSS which uses load balancing through logon group EWA. It is created automatically by SDCC. If, however, SAPOSS is changed ( for example, if the 'Message Server' string there is changed, or because the entries 'Technical parameters' in transaction OSS1 were updated) it is necessary to adjust SAPNET_RFC. You can do this by simply deleting SAPNET_RFC. A fresh copy of SAPOSS will be created when SDCC tries to connect to SAP. If this does not work, and you get an error of type "hostname ... unknown/CPI-C error CM_PRODUCT_SPECIFIC_ERROR" you should refer to note 316221 for advice.

18. Submitting the data collection or transfer background job fails

Q: When going through the standard procedure of collecting or transmitting data, an error message 'error during JOB_CLOSE, see SYSLOG' appears, and no job is submitted.

A: Both the collection of session data and its transfer to the SAP Service System are done through class C background work processes. Usually the customer system looks for any free background work process on any server and starts the collections and/or transfer jobs there. Problems can occur when:

• the 'Background server' parameter in 'Maintenance -> Remote Environment -> Default destinations' is not empty but set to a server that doesn't exist anymore, contains no background work processes, whose background work processes have been removed, or whose background work processes do not permit class C background jobs.

• on the entire system all background work processes are in use.

• the user under which the background work process is scheduled does not have authorization to do so (the user EARLYWATCH can have this problem). If the background work processes you tried to start (Session -> Display -> Coll./trans. jobs) are in status 'SCHEDULED' and you try to release them, you'll get an error message.

19. Run of AUTO_SESSION_MANAGER failed ( in R/3 rel 4.*)

Q: During run of ASM following error message is shown in job log
(SM37):
"Variant &0000000000000 does not exist"

A: Go to transaction sm37, select job AUTO_SESSION_MANAGER. Select the next future job ( there should be only one). Go into change mode (Job -> Change). Then press button 'Steps'. Select program name (BDLATRUN or /BDL/ATRUN with ST-PI) and go to Change mode. Change field entry "Parameters" from  &0000000000000 to 'Space' and save. Subsequent ASM jobs should be executed without the paramater, and run through.

20. Oracle error 1039 and/or 942 appear in the SYSLOG during execution of a SDCC download

Q: While the SDCC report BDLCOLL is running Oracle error 1039 and/or 942 appears in the SYSLOG (Datenbankfehler 1039, Datenbankfehler 942). What should be done?

A: These errors occur when the function module SQL_CACHE_ANALYSIS_READ is called. This module calls a kernel C routine which make EXPLAINs on SQL statements. The kernel routine returns the error codes.

This SYSLOG entry causes no disruption for the Service. It also causes no short-dumps. Therefore it can be ignored. PLease see also note 200463.
.

21. Data collection gets stuck

Q: What should I do when a data collection is going on for a long time (hours), or simply stops without the 'Data collection completed' entry in the SDCC Message Log?

A: Data collection can take very long when, for example, the system consists of many servers, or the system performance is poor. However, it is possible that some of the function modules called by SDCC lead to errors, very long loop times etc. These errors can occur in a variety of circumstances which need to be examined on a case by case basis. They often indicate some general problems in the system, or in some of the function modules called. If they are not contained in the scenarios outlined below you should seek specialist advice by opening a message in component SV-SMG-SDD.

a)SDCC batch jobs fails. Typically the SYSLOG (SM21) contains an error message of type
"F61 K TemSe input/output to unopened file".

In SM37 (SDCC -> Session -> Display -> Coll./trans.) I get the error "Error occurred when reading job log JOBLGX...X"  when I try to look at the job log.

Please refer to Note 21661. Further information is, if required, in Note 48400. If the problem is a full file system, please refer to Note 16513.

b) If the system has R/3 release 3.0D have a look in transaction ST22. Look for short dumps 'CALL_FUNCTION_PARM_MISSING' for the user who is running SDCC. If the error analysis shows that the error occured while calling function 'DDIF_NAMETAB_GET', parameter "X031L_TAB", the situation is as follows:
The version of the DDIC function module 'DDIF_NAMETAB_GET' is not up to date.  For old R/3 releases in function 'DDIF_NAMETAB_GET' (it is used to get DDIC information) the 'optional' flag is not set for tables parameter "X031L_TAB".

Solution:  Set the tables parameter "X031L_TAB" of function 'DDIF_NAMETAB_GET' optional and generate the function. After that  you can run transaction SDCC as normal.

c) For AS400 systems data collection stops, and in the SYSLOG (SM21) an entry appears "DB error -901 at DEL access to ...".

Solution: A DB patch is required. The customer should seek specialist AS400 advice through a message in component BC-DB-DB4.

22. RFC destination not found in SDCC

Q: When trying to transfer data in SDCC the following messages appear.

   -  No data transfer possible: destination info not found

   -  No RFC destination found: transfer not possible

  in the SDCC Message Log and the data are not transferred.

A: Please check if the RFC destination has been accepted by SDCC.
Highlight the session, then do 'Maintenance -> Remote Environment -> Custom target dest.' If no target destination is implemented, you can do it in this screen for this single session.

If you need a general solution for future sessions please do 'Maintenance-> Remote environment -> Default target destination'. Here you have to change the current destinations to any different destination and save. After this you have to reimplement the original destination once again. Please check again if the RFC destination has now been accepted ( check as described above). If this does not work, please open a message in component SV-SMG-SDD.

23. RFC errors

Q: I tried to refresh the 'Service definitions' and/or the 'Session overview' but I am prompted with errors 'Session update via RFC failed' (SD-140) and/or 'Service definition update via RFC failed' (SD-141).

or

Data collection was successful, but data transfer failed (RFC problems)

NOTE: Service definitions should be only be refreshed from OSS where appropriate, as described in Question 2 of this note, (SERVICE DEFINITION REFRESH)

A: Ideally the system should have a working RFC connection from each of its servers to the SAP Service System. You can check whether this is the case by using Transaction SM59 -> R/3 destinations, then choosing SAPOSS and doing 'Test -> Authorisation'. From SDCC version 1.7 on, a tool for checking RFC destination SAPOSS is available through Information -> Service prep. check -> Status of RFC dest. (from outside SDCC it can be called through Transaction SE38 -> BDLPING(or /BDL/PING,if SDCC was implemented with ST-PI))

A list with SAP instances is displayed, and for each instance it is
shown whether

a) there are background work processes on the instance (key functions of SDCC run as background jobs!)

b) whether the RFC connections to SAPOSS/SAPNET_RFC are working.
(Please note that this only checks if a 'ping ' can be exchanged,  not the authorization of the user sending it. Please check Question 29 for information on how to maintain the destinations.)

What you need is an instance where both these requirements are rated 'green'; the server assigned to that instance can be used by SDCC.

Case 1: Some servers have functional SAPOSS RFC destinations

If a working SAPOSS RFC destination exists in one server (but not in others) and this server contains background work processes, this server can be explicity set in 'Maintenance -> Customizing -> General' under 'Background server' for use by SDCC. This makes sure that the SDCC core data collection and transfer processes can run and that the 'Session Overview Refresh' that is triggered by the ASM is working.

In terms of doing a Service Definition Refresh, or a Session Overview Refresh (which run on dialog work processes), you have to switch to a usable server with Transaction SM51.

NOTE: Service definitions should be only be refreshed from OSS where appropriate, as described in Question 2 of this note, (SERVICE DEFINITION REFRESH)

If a working RFC destination exists in one server but this server does not contain background work processes, you can call report BDLSEND (/BDL/SEND where SDCC is implemented by ST-PI) with SE38 on the functional server and transmit data manually. In the input screen for BDLSEND (or /BDL/SEND...) you usually only need to fill the fields SESSNR (with .Sess. num..), MANDANT (with the .Ext..) and DEST (with the RFC Destination   in 'Maintenance -> Customizing -> General'). However, this should only be done as an exception! For the normal use of the Earlywatch Alert a sufficient number of background work processes should be set up.

Case 2: No server has a functional SAPOSS RFC destination

If the system has no working SAPOSS RFC destination it can have a number of reasons (see Note 33135, Appendix A):

I. Error ' service sapdp99 unknown' or 'error opening an RFC connection'occurs
The services file may not be maintained correctly.

(i) Add the entry sapdp99    3299/tcp  in the 'services' file of the customer system which is usually UNIX: /etc/service , NT:
<windir>\system32\drivers\etc\services. (If it is not already there; here 3299 is the port number and tcp is the protocol)
This method should be preferred to option ii).

(ii) Alternatively you can change from 'sapdp99' to '3299' directly in SAPOSS.

After this you can proceed as in case 1.

II. If there is a saprouter or firewall problem (route permission denied)

The file saprouttab is not correct, refer to note 30289. If all efforts fail, please open a message (component BC-MID-RFC).

24. Dedicated background server can't be set in SDCC

Q: After entering the dedicated background server in SDCC -> Maintenance-> Remote Environment -> Default Target Destinations, and leaving the window with the OK Button the server name is automatically changed into capital letters. This makes processing of the download in the background impossible. In some cases warnings in SDCC log appear : "ASM: SASM_Z0000000xx_COLL_TRANS failed". The reason for this warning is that the job SASM_Z0000000xx_COLL_TRANS is scheduled without a start date and time due to the badly implemented background server.
What can be done?

A: Please implement the latest SDCC version, at least SDCC 2.3 (see note91488). If the problem persists, please open a message in component SV-SMG-SDD.

25. Getting kicked out of SDCC immediately after calling it

Q: After calling SDCC a pop up shows up : " YOU ARE NOT AUTHORIZED TO LOG ON TO TARGET SYSTEM" or "KEINE BERECHTIGUNG ZUR ANMELDUNG AM ZIELSYSTEM" before throwing me out. What should I do?

A: The RFC destinations SAPOSS or SAPNET_RFC are not properly maintained, most likely because the user or password are not maintained correctly.You will find information about how to maintain these destinations correctly in the next question.

26. SAPOSS, SAPNET_RFC, SAPNET_RTCC are not properly maintained

Q: These destinations look unusual in SM59; is there a template I can check them against?

A: SAPOSS is configured automatically on the basis of data in OSS1.
If SAPOSS isn´t working, please make sure that the entries for 'Technical settings' in OSS1 are correct. Refer to Notes 33135 and 30289 for more information on OSS1. To ensure SAPOSS is maintained with 'load distribution' set to 'yes', please follow note 766505.
SAPNET_RFC and SAPNET_RTCC are copies of SAPOSS. They get created automatically when the tools SDCC (SAPNET_RFC) and RTCCTOOL ( SAPNET_RTCC) connect to OSS the first time. They get created with 'Loadbalancing' switched on. This makes the entry in the field 'Target Host' appear very short - please note that the full string as described below can only be maintained if 'Loadbalancing' is set to 'No'.

Please note that after an update of SAPOSS via TA OSS1 the client may change to 000 - please update this manually to 001.
Also, after an update of SAPOSS via TA OSS1 SAPNET_RFC and SAPNET_RTCC do NOT get updated automatically. The easiest way to ensure they are updated correctly is to delete both destinations, and then start a connection to OSS from the tools ( SAPNET_RFC: SDCC -> Maintenance -> Refresh -> Service Overview. SAPNET_RTCC: SE38 -> RTCCTOOL)

Often ( but not always - systems with 2 saprouters can be different) the parameters of a working SAPOSS or SAPNET_RFC destination (where Load balancing is set to 'No' ) are set up like this:

• Target host: /H/X1/S/sapdp99/H/X2/S/sapdp99/H/oss001
  with
  X1 = customer saprouter IP address
  X2 = IP address of sapservX
  
  possible entries for sapservX:
  sapserv1 (194.117.106.129) Internet VPN connection
  sapserv2 (194.39.131.34)  Internet SNC connection
  sapserv3 (147.204.2.5)    for customers connected to Germany.
  sapserv4 (204.79.199.2)    for customers in Americas.
  sapserv5 (194.39.138.2)    for customers connected to Japan.
  sapserv6 (194.39.139.16)  for Australia and New Zealand customers.
  sapserv7 (194.39.134.35)   for Asia customers.
  

SAPOSS and SAPNET_RFC

• System number = 01

• Client = 001

• User = OSS_RFC

• Password = CPIC

SAPNET_RTCC

• Client = 001

• User = ST14_RTCC

• Password gets set automatically when the destination is created. In case of problems with the password please delete SAPNET_RTCC and recreate it.

27. Data transfer job aborts with a short dump TSV_NEW_PAGE_ALLOC_FAILED

Q: When I collect and transfer data for a download the SDCC message log shows that data collection is ok, but ends with 'Data transfer started'. Additionally a short dump TSV_NEW_PAGE_ALLOC_FAILED is created ( see ST22) and the transfer job is aborted.

A: In table BDLCUST (/BDL/CUST where SDCC has been implemented via ST-PI) the entry for SENDSTYL has to be changed from SINGLE_RFC to MULTIPLE_RFC. You can do this in SE38, with report BDLSETUP (/BDL/SETUP where SDCC has been implemented by ST-PI), using KEY : SENDSTYL and VALUE: MULTIPLE_RFC. Then delete the data collection from the download viewer and redo the complete download. For more details, especially regarding ADDON data see note 312834.

28. RFC related errors

Q1: While collecting data the message log shows the following error:
   -  <function name> : no matching interface found
   -  BDL_GET_DDIC_INFO exception 2 wrong_function_parameter

A: On systems with more than one server each server should have the same entry in the 'services' file for the message server. Change  the entry 'sapms<SID>' of the 'services' file on all servers of the system to the identical value '36xx/tcp' (xx is a two digit number), The 'services' file is usually
UNIX: /etc/service ,
NT: <windir>\system32\drivers\etc\services.

Q2: ST22 shows ABAP runtime errors ´RFC_NO_AUTHORITY´ for the user that executed SDCC. User ´...´ has no RFC authorization for function group
´BDL...´.

A: The user authorizations have to be adjusted accordingly.

29. Transport errors ( ONLY relevant if SDCC was implemented by note 560630 - NEVER if it was implemented with ST-PI)

Q: Implementing transport SAPKVSDB* ended with RC8, and the following message: BDLFUVER2 table class is 'L'. Entries must not be replaced.

A: Please re-implement the transport with unconditional mode u168. Please be careful NEVER to implement any transport containing SDCC into a system where ST-PI has already been implemented, or in a system with R/3 release 6*.

30. For security or infrastructure reasons the system does not exchange RFC calls with the outside world.

Q: The system cannot use RFC to communicate with the SAP Service System. As a result

• the session overview cannot be loaded into the system, so that the session list remains empty

• collected data can't be transferred

• a Service Definition Refresh can't be performed
  
  Is there a way out of this?
  
  A: Yes. The data can be sent to sapservX, the Service Engineer performing the session then creates an IT/IBC message to get the data transferred to the system he performs the session in. Please note that the Service Engineer will have to give you the session number as it is
  defined at SAP.
  
  a) Call Session -> Create -> Internal Session. A window appears.
  
  In the field 'Session number' any number (that has not been used before) can be typed in.
  
  In the field #Session type# the relevant session type has to be selected. Then push the green check icon at the bottom of the window.
  
  b) The newly created session should now appear in the session overview.
  
  c) Highlight that session.
  
  d) Click on the 'Download' button. A window appears. In this window de-select(!) the 'Transfer  ...' field and click on the 'Start task(s) immediately' button.
  
  e) Now watch the Message Log with Information -> Display Message Log until the 'Data collection completed' entry comes up.
  
  f) Once this is done, please do the following:
  Highlight the session, then do:
  'Session -> Process -> Export data to file'
  A window comes up.
  
  At the bottom of it you see two pairs of session numbers. On the left side is the imaginary number the you made  up; on the right hand side the session number as it is defined for this session at SAP must be entered.
  For the 'Destination extension' use '000' (three zeros) and click the green check icon. At the bottom of the screen and in the message log a file path will appear. This file path indicates the location of the file that contains the session data.
  
  g) Now the file has to be transported to the SAP system:
  Please contact the Service Engineer performing the session. He will provide a link ( via SAPMats)  to which you can upload the file.The process will then be continued internally; the Service Engineer can use note 588128 for information on how to continue the process.
  
  Please note that from this point on it takes 24 hrs to get the data into the correct system at SAP, so the process must be started in good time before the session.
  
  Please note also that this method is not primarily meant for customers with 'bad' lines. In case of such a line, please try to solve the problem first by reducing the RFC packet size using 'Maintenance ->
  Customizing -> General -> Block size for one RFC'
  
  i) Concerning the Service Definition Refresh:
  Please follow note 727998, which explains how to completely replace the service definitions for all possible combinations, with the relevant transport.

SAP Note 309711 - SAP Servicetools Update: Online help (Part II)

(Continued from part I)

4. ABOUT AUTOMATED FTP

When starting RTCCTOOL, an FTP availibility check is performed. If sapserv3-7 canot be reached, the options for automated FTP in the
'Get files # select method' screen of the ST assistent are disabled ('not possible on this server').
In this case you should try once more to run RTCCTOOL on the server where your SAProuter is running (FTP has to use the SAP Remote Connection). If it still does not work, we do not recommend to try further. Instead, please choose one of the other three option for manual FTP. If you use a separate computer for FTP to sapserv3-7, you can download the FTP commands as a text file.

Longrunning FTP check
If RTCCTOOL takes some minutes after start until the list of recommended notes&transports comes up, This is most likely caused by an unsuccessful FTP availibility check (by RFC ping). In this case, choose 'Settings', expand the 'Further FTP options' and set the 'FTP on/off' option explicitely to 'off'.
In some rare cases, the FTP check does not come back at all. It the RTCCTOOL runs already longer than half an hour, you should cancel the program. Then start RTCCTOOL once more. The program should recognize the previous failure 'Last FTP check did not run through'. Choose 'Yes' to disable the FTP check.

5. MODIFICATION INFO IN (VERY) OLD SERVICETOOL TRANSPORTS

More than 2 year before some servicetool transports occasionally have contained some modification info (SMODILOG), i.e. FUGR SQLD/OCSI/SSQ0. During upgrade or during import of certain basis supportpackages (see note 195189), these objects may pop up for modification adjustment.
As a solution or in order to prevent this, we recommend to run report /SSF/RTCCSMOD before a planned upgrade without input parameters. This report clears modification only for TCC Servicetool objects.

6. ABOUT RTCCTOOL RECOMMENDATIONS

Q: Shortened procedure for customers using an internet VPN/SNC
  connection to sapserv1 or sapserv2
A: This connection type does not allow FTP access to the sapserv file
   system. The most important servicetools are available as addons
  from SAP Services Marketplace http://service.sap.com/supporttools
  (addons ST-PI and ST-A/PI) and can be implemented.
   Further recommendations regarding transports from Sapserv3-7
  cannot be implemented. Skip these recommendations and set them
  manually to green in RTCCTOOL.

Q: List of recommended notes
A: RTCCTOOL automatically checks for addons&transports
  from the following notes:
   Note 116095 (ST-PI Addons with basis tools, includes the download
                tool SDCC (note 178631), the SQL traceinterpreter SQLR)
   Note 69455 (ST-A/PI Addons with Servicetools for Applications
              include ST14 application monitor & RTCCTOOL)
  Note 7312 (New Earlywatch user / client 066)
  Note 207223 (Activation of SAP EarlyWatch Alert)
   Note 36637 (Database monitor for MS SQL Server Release 6.5)
  Note 139945 (Database monitor for MS SQL Server Release 7.0)
   Note 84060 (Database monitor for Informix)
  Note 101217 (Correction transports for DB2/390)
   Note 124268 (Explain function for DB6)
   and others

Affected Releases

Software Component Release From Release To Release And subsequent SAP_APPL 30 30D 31I   SAP_APPL 40 40A 40B   SAP_APPL 45 45A 45B   SAP_APPL 46 46A 46B   SAP_APPL 46C 46C 46C   SAP_BASIS 46 46D 46D