Ansicht
Dokumentation

RNCGET04 - IS-HCM: Retrieve OU-Related Services from Partner Systems

RNCGET04 - IS-HCM: Retrieve OU-Related Services from Partner Systems

CPI1466 during Backup   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.
SAP E-Book

Description

This report retrieves the data for organizational-unit-related services from (selected) partner systems. You can choose whether batch input sessions are generated or whether the data is updated straight away. Transaction NL04 is used for this purpose.

If the 'Start update immediately' indicator is not set, the data is simply placed in a batch input session. This mode is actually only meaningful for tests.

In normal operation, the inbound data should be imported to the IS-H database as soon as possible. This is done 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 must be checked manually (with extended log and (subsequent) troubleshooting).

You can enter a batch input session name other than the standard name or the name defined in Customizing in the 'Alternative session name' parameter. This entry is not mandatory. If you do not enter an alternative name, the name set in Customizing is used. If you have not specified a name here, the system uses the standard name 'ISH_OUSRV'.

The connection is established via the SAP commuication module.

The report should run cyclically in the background (for example, every evening) to transfer the services performed 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_OUSRV_xxx

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

Requirements

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

Output

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






BAL Application Log Documentation   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 2712 Date: 20240531 Time: 173410     sap01-206 ( 53 ms )