Description
This program retrieves surgical data from (selected) partner systems.You can specify either that batch input sessions should be generated, orthat the data should be updated straight away. Transaction NP37 is usedfor this purpose.
If the 'Start update immediately' indicator is not set, the data issimply placed in a batch input session. It really only makes sense touse this mode for testing purposes.
In normal operation, the inbound data should be uploaded into the IS-Hdatabase as soon as possible. You do this 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 you must check them manually (process with extendedlog and (then) correct error).
In the Alternative session name field, you can enter a batchinput session name that is different than the standard name or the namedefined in Customizing. You do not have to enter a name in this field.If you do not, the name defined in Customizing is used. If you have notdefined a name in Customizing, the system uses the standard name'ISH_SURGS'.
The connection is established via the SAP communication module.
The program should run cyclically in the background (for example, everyevening) to transfer the collected surgical data from that day to theIS-H database.
SAP recommendations:
RESET N1
You should name the corresponding background job in accordance with theISH naming conventions, that is
ISHCM_GET_SURGS_xxx
where 'xxx' stands for the client in which the job was created. The jobonly runs/works for this client.
Insert the SAPCDERR program as the first job step before RNCGET05. Thistransfers any pending receipt acknowledgements to partner systems andthereby avoids complications.
Specify a "meaningful" repetition period. In general, we recommend thatthe surgical data be retrieved on a daily basis (for example, at 7.30p.m.).

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

Output
A short log with the number of messages retrieved from each partnersystem.
Any communication problems are also included in the log. Furthermore, adetailed description of most communication problems is provided in thesystem log.