SAP ABAP IMG Activity SIMG_ISHCM_GD_INST (Instructions for Installing HCM Transceiver)
BBPCRM (Software Component) BBPCRM
   CRM (Application Component) Customer Relationship Management
     CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       NBAS (Package) Appl. development Hospital System master data, catalogs
IMG Activity
ID SIMG_ISHCM_GD_INST Instructions for Installing HCM Transceiver  
Transaction Code S_KK4_74000434   IMG Activity: SIMG_ISHCM_GD_INST 
Created on 19990816    
Customizing Attributes SIMG_ISHCM_GD_INST   Instructions for Installing HCM Transceiver 
Customizing Activity    
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_ISHCM_GD_INST    

IS-HCM - Instructions for Installing HCM Transceiver
Status: IS-H Release 4.61, March 2000

This document describes how to install the HCM transceiver as part of SAP Healthcare Industry-Specific Components for Hospitals (IS-H). For details on how the HCM transceiver functions, refer to IS-HCM Function Description. Knowledge of how the transceiver operates is a prerequisite for installation.

  1. Platforms supported

    A special IS-HCM version of the SAP Communication Module (communication module, transceiver for communication with external programs) is required for IS-HCM communication. SAP calls this product the "HCM transceiver". This product should not be confused with the "standard" transceiver that may exist for other platforms.

    SAP currently provides the transceiver software for the following platforms (available under /specific/ish/HCM on sapservX):

    ALPHAOSF    for DEC Alpha OSF/1 3.2,

    HP    for HP UX 9.0x,

    LINUXINTEL    for Red Hat Linux 6.0 on Intel,

    OS2    for OS/2 Warp 3.0,

    OS400    for IBM OS/400 as of V3R7 on AS/400,

    RM600    for SNI Reliant 5.41 on RM400/600,

    RS6000    for IBM AIX 3.2.5,

    SUN    for SUN 5.4,

    WNTINTEL    for MS Windows NT 3.5, 4.0 on Intel,

    WNTALPHA    for MS Windows NT 3.5, 4.0 on Alpha.

To be able to use the transceiver software under OS/2, you need to have installed TCP/IP Version 2.1 (or higher).
For information on the prerequisites to be satisfied for using the transceiver software under Linux, please see SAP Note 171356.

Transceiver modules may not be available for older versions of operating systems running on otherwise supported platforms. It is also possible that the software no longer executes with newer versions of operating systems.

If a suitable transceiver module is not available for the operating system of the host on which your subsystem is running, you need not forgo the functionality of the HCM transceiver. In such cases, the following work around is possible:

You simply need to have a computer running one of the above supported operating systems in your network. This can also be an SAP server. You can install the transceiver module on this computer. The transceiver and scripts reside on this (superordinate or central) host. NFS (Network File System) functionality should be used to define shared directories for transferring data from the "transceiver host" to the external partner systems involved (via 'mounts' or 'links'). The installation then continues as described below.

  1. Shipment of HCM transceiver software

    The transceiver software for the common platforms is shipped with the IS-H Release CD. For technical reasons this is not possible for the AS/400 programs. You can also fetch the transceiver software programs directly from sapservX at a later date.

    The programs are located
    on sapservX in the directory


    These program are non-compressed and are grouped by platform. This directory also contains the template scripts that serve as a reference for concrete customer installation. Please note that the executable programs must be transported in binary mode.

    Particularities with OS/400 programs:

    The programs for AS/400 are stored in the format *SAVF. To fetch the *SAVF from sapservX and to decompress the programs, please proceed as follows:

    • Create the savefile ISHCM in the library QGPL using
    • Fetch the transceiver programs from sapservX
      ftp sapservX
      user ftp ftp
      cd /specific/ish/HCM/os400/
      get ISHCM QGPL/ISHCM (replace
    • Import the objects into your AS/400 system. Specify the key library for the parameter RSTLIB.
      SAVF(QGPL/ISHCM) RSTLIB(<key library>)

      The IS-H Release CD (not with maintenance levels) contains a separate HCM directory

      /<CD directory>/HCM.

      The programs with template scripts are compressed in an HCM.CAR file in platform-specific subdirectories under this directory (the OS/400 programs cannot be shipped in this manner). Please refer to the READ.ME file.

      To decompress the programs, proceed as follows:

    • Mount the CD (see IS-H or SAP Upgrade Guide);
    • Make a tmp directory your current working directory using 'cd';
    • Decompress the file using 'SAPCAR -xvf /<CD-Verzeichnis>/HCM/<Plattform>/HCM.SAR'

      Example (for WNTINTEL platform):

      >cd /usr/tmp

      >SAPCAR -xvf /sapcd/HCM/WNTINTEL/HCM.SAR

      The decompressed programs and scripts are now located in the tmp directory.

  2. Prerequisites for installation

    You first have to have installed IS-H on the SAP system side. At least one SAP gateway must be running (a separate gateway is usually started on each SAP application server).

    It must be possible to reach the partner system computer from the SAP gateway computer (if these are not the same computers). This requires the host name of the partner system computer to be entered in /etc/hosts file on the SAP gateway computer. To identify the name of the host, run the hostname or uname -a command.

    The host name of the SAP gateway host must be entered in the local /etc/hosts file on the partner system side (if these are not the same computers). Furthermore, the SAP gateway service entry sappgw[xx] (e.g. sapgw00) is required in the local file /etc/services.

    The following requirements must be satisfied for calling the remote shell from the SAP gateway computer if the SAP gateway is not running on the partner system host:

    • The user under whose ID the SAP gateway is running (e.g. c41adm) must exist.
    • The .rhosts file must exist in the home directory of the c41adm users. This file must contain at least the host name of the SAP gateway computer.
    • Since the remote shell command differs in relation to the platform (remsh, rsh, etc.), it can be set accordingly using the SAP gateway profile parameter gw/remsh (e.g. gw/remsh=/usr/ucb/remsh). The SAP default setting is remsh.

      A separate SAP gateway is required fir MS Windows and IBM/400. The remote shell is not used in this case. As such the prerequisites for the remote shell do not need to be satisfied.

  3. Install the executables

    The executable programs must be installed in the partner system in such a way that they can be executed remotely. This requires the SAP gateway to be authorized and enabled to start the transceiver scripts (and in so doing to start the transceiver programs indirectly). For cases where several partner systems are connected to the same computer, the same executables are always started even though system-specific scripts are used. This is why it is practical to install these programs centrally and grant all users concerned the authorization to execute them (e.g. in /usr/bin).

    Please refer to the particularities for the OS/400 version.

    Copy the corresponding platform programs into the appropriate directory. The programs should be copied as follows:

put_tab.<systemname>     copy tp -> PUT_TAB1

get_tab.<systemname>     copy to -> GET_TAB1

get_resp.<systemname>     copy to -> GET_RESP1

send_tab.<systemname>     copy to -> SEND_TAB1 *

* install SEND_TAB1 only if it is required and supported. This is currently not the case with Windows NT and OS/400.

The transceiver programs must be in the search path. If necessary, the .cshrc file must be modified (by the SAP admin. user).

Particularities with Windows NT

  • The NT transceivers must be executed on the same NT computer on which the SAP NT gateway is running. This is because, in contrast to Unix computers, NT computers cannot be accessed from the SAP system via remote shell. This usually means that you have to install an extra gateway on the NT PC. This st
Business Attributes
ASAP Roadmap ID 306   Establish System Administration 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG SIMG_ISHCM_GD_INST 0 I010004232 Communication with Systems Inside the Hospital 
Maintenance Objects
Maintenance object type    
Last changed by/on SAP  19990816 
SAP Release Created in