Ansicht
Dokumentation

RNCCHK01 - IS-HCM: Installation Check For Partner Systems

Addresses (Business Address Services)   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Description

This program checks whether the (selected) IS-H partner systems have been installed correctly. Communication with a partner system is not possible as long as error messages (red) are displayed here.

This is an important tool for installing partner systems.

Please also note the standard information messages that are not marked in red. These indicate potential consistency problems as well as unneccessary entries in Customizing that reduce system performance.

A cross-client check often provides useful information.

Customer message types that are not used throughout the entire SAP system should be removed, since these unnecessary structure entries place an additional load on the system. Remember that the message formatting program usually runs every 5 minutes. This constant importing/sorting out of unnecessary entries uses up memory and slows down the system.

This also applies to other unnecessary entries that are listed under the other check results. Caution: these are only meaningful if the program was started without a client restriction.

The following checks are performed:

• On a system basis, for each selected system:
  

• Is the system information corherent?:
  "External system" indicator set? "All in one" indicator set? If a code page is entered: does it exist? Are the TXCOM and script name conventions observed? Do the TXCOM entries exist? Are control entries present in the HCM for the existing TXCOM entries? Does a GET_RESP entry exist for every GET_TAB entry? Is the system blocked at present? Is direct dispatch active? If so, is an RFC destination specified? Does the specified RFC destination exist?
  

• Is the dispatch/receipt control information correct?
  Are the existing entries permitted? Is the message standard/version/format specified? Does this message format exist? Can it be used? Are the dispatch entries in the correct control system (with/without reference) based on events? Is there more than one receipt control entry for the same system and event?
  

• (Other) cross-system checks in the selected clients:
  

• Dispatch/receipt control
  Are there any dispatch/receipt control entries for non-existent systems? Or for impermissible events? Do records without a remote function name exist in synchronous dispatch control? Do the specified function modules exist? Is the same external function called more than once?
  

• Message formats:
  Do customer message types/segments exist that are not used anywhere in the system? Can the current message types/segments be used? Are there any (incoherent) HL7 conversion entries for system message types (owner code 'S*')? Does an HL7 message type with this owner code exist for every HL7 conversion entry?
  

• Number ranges:
  Have the HCM number ranges been created/are they coherent? Are there any HCM number ranges that are not required?
  

Requirements

None.

Output

• List of the selected/existing clients;

• All system-based check results;

• All other cross-system check results;

• List of all institutions with activated HCM dispatch.

Addresses (Business Address Services)   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 3751 Date: 20240531 Time: 114653     sap01-206 ( 71 ms )