Ansicht
Dokumentation
RNCGET06 - Retrieve Med. Service Data From Partner Systems
ABAP Short Reference CL_GUI_FRONTEND_SERVICES - Frontend ServicesThis documentation is copyright by SAP AG.
Description
This report retrieves the medical service data from (selected) partner systems. You can choose whether batch input sessions are generated or whether the data is updated straight away. The subsequent service entry function (transaction N1M0) is used for this purpose.
If the Start Update Immediately indicator is not set, the data is simply placed in a batch session. This mode is only sensible for tests.
In normal operation, the inbound data should be imported to the IS-H database as soon as possible. In this case, the data is updated straight away by means of a CALL TRANSACTION. A batch input session is only started if the data could not be updated. These sessions are indicated by the ending '_ERR' and must be checked manually (with extended log and (subsequent) troubleshooting).
The connection is established via the SAP communications module.
The report should run cyclically in the background to transfer (for example, every evening) the service data from that day to i.s.h.med.
SAP recommendations:
-
You should name the corresponding background job in accordance with the IS-H naming conventions, that is:
ISHCM_GET_MSERV_xxx
Where 'xxx' stands for the client in which the job was scheduled. The job only runs/works for this client. - Insert the SAPCDERR program as the first job step before RNCGET06. This transfers any pending receipt acknowledgements to partner systems and thereby avoids complications.
- Specify a "sensible" repetition period. In general, we recommend that medical service data be retrieved on a daily basis (for example, at 7.30 p.m.).
Integration
Prerequisites
- The SAP communications module must be installed correctly.
- In IS-HCM Customizing, you must specify the systems from which services may be retrieved.
- The format must also be correct for the system in question.
Features
Selection
The following selection criteria is available for controlling the execution of the report:
- Partner system(s)
- You enter the partner systems from which you transfer medical service data.
- Start Update Immediately
- If you check the Start Update Immediately indicator, the medical services are also updated, otherwise only batch input sessions are created.
- Deviating Session Name
- In this field you can enter a different name for the batch input session to that defined as standard or to your customizing entries. This entry is optional. In this case your customizing entries are used. If these also contain no name, the standard name ISHMSERV is used.
Standard Variants
Output
A short log indicating the number of messages retrieved from each partner system.
Any communications problems are also included in the log. More detailed information is also provided in the system log on almost every communications problem.
Activities
Example
Vendor Master (General Section) BAL_S_LOG - Application Log: Log header data
This documentation is copyright by SAP AG.
Length: 3440 Date: 20240520 Time: 084446 sap01-206 ( 63 ms )