FAQ Service Data Control Center (SDCC)
Service Data Control Center is used for the purpose of planned execution of a service session you want to provide SAP with statistical data on the use of the R/3 System.
Below you will find a list of question which are often raised in connection with the Service Data Control Center.
1. Q: Which version of the Service Data Control Center should be used, 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.
SDCC should only be used if it is not possible to activate SDCCN.
2.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( version 2.3 at least) . Please also ensure 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 and the user in this destination has been given the necessary authorisations also.
3. 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)
4. 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.
5. 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. T
6. 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.
7.Q: ASM schedules several SASM__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.
8.Q: RFC breakdown just after the ASM has started 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.
9. 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.
10.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.
11.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.
12.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.
13.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.
14.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.
15.Q: SAPOSS, SAPNET_RFC, SAPNET_RTCC are not properly maintained.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. To ensure SAPOSS is maintained with 'load distribution' set to 'yes'.
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
X1 = customer saprouter IP address
X2 = IP address of sapservX
possible entries for sapservX:
sapserv1 (188.8.131.52) Internet VPN connection
sapserv2 (184.108.40.206) Internet SNC connection
sapserv3 (220.127.116.11) for customers connected to Germany.
sapserv4 (18.104.22.168) for customers in Americas.
sapserv5 (22.214.171.124) for customers connected to Japan.
sapserv6 (126.96.36.199) for Australia and New Zealand customers.
sapserv7 (188.8.131.52) for Asia customers.
SAPOSS and SAPNET_RFC
System number = 01
Client = 001
User = OSS_RFC
Password = CPIC
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.
16.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.