Description
The RNCSND01 report is the message dispatch program. It reads themessages that are ready for dispatch from the table NC02 and attempts tosend them to their recipients. The connection is established via the SAPcommunication module. Messages that were successfully delivered arelogged in the table NC00. Messages that could not be delivered remain inthe table NC02.
All of the exsiting messages that are ready for dispatch for theselected system are processed. If you do not specify a system name, themessages from every system are dispatched.
Messages only remain in the NC02 table if an error has occurred. In thiscase, the program outputs the number of messages that could not bedelivered in the dipatch log.
RNCSND01 should be installed as a cyclical background process as soon asthe IS-HCM is used. This is the only way to ensure constant orderprocessing.
SAP recommendations:
RESET N1
Schedule RNCSND01 as the second step in a background job with the name
ISHCM_DISPATCH_xxx
RNCBLD00 should be defined as the first step.
'xxx' stands for the client in which the job was scheduled. The job willonly run/work for this client.
Enter a "meaningful" repetition period. SAP recommends that you formatand send messages every six minutes. If the interval is too small, thesystem will be overloaded unnecessarily by the background processes. Ifthe interval is too large, it may take too long for the messages toreach the recipient. The best compromise is usually based on practicalexperience with the application in question.
If you create separate jobs to format and dispatch messages, they shouldbe defined in such a way that one job starts in the middle of theinterval of the other job (see example below). By doing so, you canoptimize their interaction and rule out time losses due to blockingproblems (see below) to a large extent.
In this case, you should define the job names as ISHCM_BUILDER_xxx
and ISHCM_SENDER_xxx. For performance reasons, SAP recommendsthe DISPATCH variant with two steps in one job.

Precondition
RESET N1
The SAP communication module must be installed correctly.
In IS-HCM Customizing, you must define which systems are informed andhow.
The message formatting and dispatch programs must not runsimultaneously. This is also prevented by the programs themselves. Thisblocking problem must be taken into account when you define the starttimes for separate jobs.

Output
A short log containing the number of messages dispatched. The log alsoindicates whether ceratin messages could not be delivered.

Example
RESET N1
One job:
ISHCM_DISPATCH_xxx first starts at 08:00 a.m., then at six-minuteintervals, that is at 08:06, 08:12, 08:18, and so on.
Separate jobs:
ISHCM_BUILDER_xxx first starts at 08:00 a.m., then at six-minuteintervals, that is at 08:06, 08:12, 08:18, and so on.
ISHCM_SENDER_xxx first starts at 08:03 a.m., then at six-minuteintervals, that is at 08:09, 08:15, 08:21, and so on.