Programme SAP RNCGET02 - IS-HCM: Retrieve Diagnoses From Partner Systems

Description
This report retrieves diagnosis data from (selected) partner systems.You can choose whether batch input sessions are generated or whether thedata is updated straight away. Transaction NP61 is used for thispurpose.
If the 'Start update immediately' indicator is not set, the data issimply placed in a batch input session. This mode is acutally onlymeaningful for tests.
In normal operation, the inbound data should be imported to the IS-Hdatabase as soon as possible. This is done by setting the 'Start updateimmediately' indicator. In this case, the data is updated straight awayby means of a CALL TRANSACTION. A batch input session is only started ifthe data could not be updated. These sessions are indicated by theending '_ERR' and must be checked manually (with extended log and(subsequent) troubleshooting).
You can enter a batch input session name other than the standard name orthe name defined in Customizing in the 'Alternative session name'parameter. This entry is not mandatory. If you do not enter analternative name, the name set in Customizing is used. If you have notspecified a name here, the system uses the standard name 'ISH_DIAGS'.
The connection is established via the SAP communication module.
The report should run cyclically in the background to transfer (forexample every hour) the diagnoses that have been performed to the IS-Hdatabase.
SAP recommendations:
RESET N1
You should name the corresponding background job in accordance with theISH naming conventsion, that is:
ISHCM_GET_DIAGS_xxx
Where 'xxx' stands for the client in which the job was scheduled. Thejob only runs/works for this client.
Insert the SAPCDERR program as the first job step before RNCGET02. Thistransfers any pending receipt acknowledgements to partner systems andthereby avoids complications.
Specify a "meaningful" repetition period. In general, we recommend thatdiagnoses be retrieved on a daily basis (for example, at 7.30 p.m.).
This recommendation applies as long as diagnoses are only kept in theIS-H database for statistical or documentation purposes.
If i.s.h.med is being used, it may be more expedient to have the partnersystem tranfer the diagnoses immediately when they are available. Forthis purpose, RNCGET00 is called by the external system.
Irrespective of the above, it may be more meaningful to simply "collect"the diagnoses on an hourly (daily?) basis.

Precondition
RESET N1
The SAP communication module must be installed correctly.
In IS-HCM Customizing, you must specify the systems from which diagnosisdata may be retrieved.
The format must also be correct for the system in question.

Output
A short log containing the number of messages retrieved from eachpartner system. Any communication problems are also included in the log.

369346IS-H RNCGET02 diagnosis key 2 is not transferred