Kontakt

Ansicht
Dokumentation

RNCGET05 - IS-HCM: Retrieve Surgical Data From Partner Systems

RNCGET05 - IS-HCM: Retrieve Surgical Data From Partner Systems

rdisp/max_wprun_time - Maximum work process run time   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.
SAP E-Book

Description

This program retrieves surgical data from (selected) partner systems. You can specify either that batch input sessions should be generated, or that the data should be updated straight away. Transaction NP37 is used for this purpose.

If the 'Start update immediately' indicator is not set, the data is simply placed in a batch input session. It really only makes sense to use this mode for testing purposes.

In normal operation, the inbound data should be uploaded into the IS-H database as soon as possible. You do this by setting the 'Start update immediately' indicator. 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 you must check them manually (process with extended log and (then) correct error).

In the Alternative session name field, you can enter a batch input session name that is different than the standard name or the name defined 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 not defined 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, every evening) to transfer the collected surgical data from that day to the IS-H database.

SAP recommendations:

  1. You should name the corresponding background job in accordance with the ISH naming conventions, that is

    ISHCM_GET_SURGS_xxx

    where 'xxx' stands for the client in which the job was created. The job only runs/works for this client.
  2. Insert the SAPCDERR program as the first job step before RNCGET05. This transfers any pending receipt acknowledgements to partner systems and thereby avoids complications.
  3. Specify a "meaningful" repetition period. In general, we recommend that the surgical data be retrieved on a daily basis (for example, at 7.30 p.m.).

Requirements

  1. The SAP communication module must be installed correctly.
  2. In IS-HCM Customizing, you must specify the systems from which surgical data may be retrieved.
  3. The format must also be correct for the system in question.

Output

A short log with the number of messages retrieved from each partner system.

Any communication problems are also included in the log. Furthermore, a detailed description of most communication problems is provided in the system log.






Fill RESBD Structure from EBP Component Structure   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 2869 Date: 20240531 Time: 113617     sap01-206 ( 53 ms )