FAQ Service Data Control Center (SDCCN)
Below you will find some questions which are often raised in connection with transaction SDCCN (Service Data Control Center).
1. Q: What authorisations are needed to work with SDCCN?
A: The following authorisations exist:
Profile (in Basis rel 40*-46D)
- S_SDCC_READN Read authorization
- S_SDCC_SERVN Collect and send data
- S_SDCC_ADM_N Admin authorization
Roles (as of Basis Release 6.10)
- SAP_SDCCN_DIS Read authorization
- SAP_SDCCN_EXE Collect and send data
- SAP_SDCCN_ALL Admin authorization
When assigning the roles for the first time please ensure that they contain the corresponding profile.
2. Q: I want to activate SDCCN - do I have to deactivate SDCC?
A: Yes. If you have used the old transaction SDCC this must be deactivated prior to the activation of SDCCN.
To do this please delete any future background jobs connected with SDCC:
AUTO_SESSION_MANAGER, SESS* , SASM*
Then you can. locally activate SDCCN via 'Utilites -> Activate'.SDCCN in a satellite system can also be activated from a connected SAP Solution Manager system.
3.Q: What is the minimum set up needed for SDCCN?
A: To ensure that SDCCN can continuously monitor your systems for sessions created in connected SAP Solution Manager systems as well as sessions ordered from SAP a number of prerequisites must be met.
SDCCN must be activated as described in the documentation.
After a succesful activation the customizing in Goto -> Settings -> Task specific settings is filled with the SAP proposed default values.
In Goto -> Settings -> Task Processor you should see that the Task Processor job is 'active'.
Two tasks should have been created:
Service Preparation Check
This is an interactive Task which you can start by clicking on it. This leads you to RTCCTOOL, which gives you an overview of tools and notes needed for the correct preparation of any service session. More information about RTCCTOOL is in note 69455. Note 91488 documents the various preparations for a service session. The Service Preparation Check is a periodic task, i.e when the original task has been executed, the next task of the same type is scheduled as per the customizing in the 'Task specific settings'.
Maintenance package
The maintenance package is a periodic task, which should run every day. It consists of 3 'housekeeping' tasks, which each get executed when necessary. The frequency of the individual tasks is based on the customizing in the 'Task specific settings'.
- Session refresh
The session refresh which is triggered by a maintenance task checks all destinations known in the list of RFC destinations
(Goto -> Settings -> Task specific settings -> RFC destinations)
Destinations from SM59 can be added to this list manually.
- Service definition refresh
The service definition refresh is also based on the above list of destinations. It uses either the destination for which the 'Master' flag has been set, or if this flag has not been set, SDCC_OSS.
- Delete data
This task is executed as per the customizing in the task specific setting.
When the Task Processor is active, and Service Preparation Task and Maintenance Task have been created succesfully, no further tasks are needed. For control purposes individual tasks can be created, but these should generally created with mode 'runs once'.
The old transaction SDCC should now be locked.
4. Q: SDCCN is activated, but SDCC can still be called. How can SDCC be locked?
A: Most likely you have activated SDCCN when the system was on basis release 4.x, and then upgraded to basis release 6.x This has to do with the change of the namespace for the old SDCC , from /BDL/* on basis release 4.x to BDL*. When SDCCN was activated on 4.x SDCC was locked via table /BDL/CUST. In 6.x the relevant table is called BDLCUST and does not yet have the lock entry.
It must be created manually, with report BDLSETUP:
KEY = LOCKED
VALUE = X
Delete = unchecked
5. Q: When trying to create a task in SDCCN an error message appears: ' No action possible '. Why can the task not be created?
A: SDCCN has not yet been initialised correctly, and so the customizing for the tasks has not been filled yet.
SDCCN can be initialised locally by following these steps:
Ensure that the task processor job is deactivated, via
SDCCN -> Goto -> Settings -> Task processor
Then initialise the tool via SDCCN ->Utilities -> Activate.
If the initialisation was succesful you should get the following messages:
Local initialisation of new Service Data Control Center
Activation successful
Destination to SAP created
AUTO_SESSION_MANAGER descheduled
Settings filled
Service Data Control Manager tasks created
Task processor scheduled
Jobname /BDL/TASK_PROCESSOR
6.. Q: A task in SDCCN appears 'active' in the 'To do' tab, but the corresponding back ground job /BDL/TASK_PROCESSOR* has been cancelled.The apparently 'active' task cannot be cancelled.
A: At the moment only a workaround can be offered:
Highlight the task -> right click -> select 'Start now'.
The icon should change to 'match stick' while the task searches for a free background job. Now you must immediately delete the task (if you wait, the task will actually be re-started).
7. Q: Testing a destination to SAP in SM59 returns error message " service 'sapdp99' unknown " or " error opening an RFC connection ". How can this be fixed?
A: The services file may not be maintained correctly. There are several options:
a) Add the entry sapdp99 3299/tcp in the 'services' file of the customer system. This is usually:
UNIX: /etc/service , NT: <windir>system32driversetcservices.
( 3299 is the port number and tcp is the protocol)
This method should be preferred to option b).
b) (ii) Alternatively you can change from 'sapdp99' to '3299' directly in the destination.
If this information is not sufficient to fix the problem please open a message in component XX-SER-NET.
8. Q: Can I force the Task Processor background job to run on a particular instance?
A: Yes, provided the below conditions apply.
To execute a Task Processor job succesfully an instance has to fulfill two conditions
a background process of class 'C' has to be available
the connection to the target system has to be functional from this instance.
To identify which instances can be used to succesfully run the Task Processor background job you can follow this path:
SDCCN -> Goto -> Settings -> Task Processor -> Job settings -> Check hosts. Select the destination you wish to check against -> Confirm
The check will bring back a list of instances.For each you can see if a 'ping' was succesful, and if background processes exist.
At the bottom of the list instances which meet both prerequisites are listed.
In SDCCN -> Goto -> Settings -> Task Processor -> Job settings -> Target host you can use the F4 help to choose a host which fullfills the above prerequisites.
Deactivate the Task Processor. Maintain the target host as described above. Reactivate the Task Processor.
All future tasks will be executed on the maintained target host.
9. Q: In the log for the task 'Service Preparation Check' I find errors about a failed attempt to connect to SAP. What should be done?
A: Destination SAPNET_RTCC is used by RTCCTOOL, which executes the 'Service Preparation Check'.
SAPNET_RTCC gets created automatically when RTCCTOOL connect to OSS the first time.
After an update of SAPOSS via TA OSS1 SAPNET_RTCC does NOT get updated automatically. The easiest way to ensure it is updated correctly is to delete the destination and then to recreate it via:
SAPNET_RTCC: SE38 -> RTCCTOOL or executing a task 'Service Preparation Check' .
10. Q: A task was not processed at the time it was scheduled for. Why?
A: How close to the scheduled time a task can be processed depends on the frequency of the 'Task processor'. The Task processor can only process tasks in the past. If, for example,the Task processor is scheduled to run only once a day, at 21:14, all the tasks in the to do list , which are in the past, will be processed after 21:14. The sequence in which they are processed is determined by the time they are scheduled for; the task scheduled for the earliest time is processed first.
11. Q: Job /BDL/TASK_PROCESSOR is cancelled. In SM37 the job log has entries similar to this:
Job started
Step 001 started (program /BDL/TASK_SCHEDULER, variant &0000000000000, user ID <user name> )
Variant &0000000000000 does not exist
Job cancelled
How can this be resolved?
A: Deactivate and then reactivate /BDL/TASK_PROCESSOR as follows:
Logon to the productive client.
SDCCN->GoTo->Settings->Task Processor->Change settings->Deactivate.
Enter Change Modus again -> Set Defaults->Activate.