Description
This report retrieves the medical service data from (selected) partnersystems. You can choose whether batch input sessions are generated orwhether the data is updated straight away. Transaction N1M0 is used forthis purpose.
If the 'Start Update Immediately' indicator is not set, the data issimply placed in a batch session. This mode is actually only meaningfulfor 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 'ISHMSERV'.
The connection is established via the SAP R/3 communications module.
The report should run cyclically in the background to transfer (forexample, every evening) the service data from that day to i.s.h.med.
SAP recommendations:
RESET N1
You should name the corresponding background job in accordance with theIS-H naming conventions, that is:
ISHCM_GET_MSERV_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 RNCGET06. Thistransfers any pending receipt acknowledgements to partner systems andthereby avoids complications.
Specify a "meaningful" repetition period. In general, we recommend thatmedical service data be retrieved on a daily basis (for example, at 7.30p.m.).

Precondition
RESET N1
The SAP communications 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 indicating the number of messages retrieved from eachpartner system.
Any communications problems are also included in the log. More detailedinformation is also provided in the system log on almost everycommunications problem.