SAP ABAP IMG Activity SIMG_ISHCM_GD_RECV (Explain Message Receipt Customizing)
Hierarchy
☛ 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_RECV Explain Message Receipt Customizing  
Transaction Code S_KK4_74000162   IMG Activity: SIMG_ISHCM_GD_RECV 
Created on 19990816    
Customizing Attributes SIMG_ISHCM_GD_RECV   Explain Message Receipt Customizing 
Customizing Activity SIMG_ISHCM_GD_RECV   Explain Message Receipt Customizing 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_ISHCM_GD_RECV    

IS-HCM Customizing - Data Transfer from Subsystems

This documentation describes how a non-SAP system is connected to IS-HCM - from the perspective of the IS-H System - in order to transfer data to the IS-H System. It basically comprises a list of the necessary Customizing steps

  1. Install the HCM transceiver on the non-SAP system

    The HCM transceiver is a program package that is used by SAP. It has to be installed in the local area network in such a way that it can be accessed from the SAP gateway. Usually the transceiver is installed on the computer on which the application to be connected is also running.

    Should the application use a computer for which SAP cannot (yet) provide a transceiver, an alternative solution has to be found. However, it is important that the transceiver is capable of storing the transfer files in a file system for which both communication partners have write access (here the communications partner on the IS-H side is the SAP gateway).

    Caution: when you transfer executable files via FTP, you always have to use binary mode! When transferring all other files (shell scripts, documentation), please use ASCII mode.

    Regarding the actual installation: the connection is established via the SAP gateway. This necessitates that the gateway user (usually <sid>adm with system Id <sid>) has access to this host (freely definable password).

    The file .rhosts should be created in the $HOME directory of the gateway user on this host. In this file you specify from which host the SAP gateway will establish the connection. Consequently, there is no need to make an entry in the hosts.equiv file. For more information on this procedure, please refer to the documentation on hosts.equiv in your UNIX manual.

    Should the partner system be put in the position of itself taking the initiatve of transferring data (program send_tab), a correct sideinfo file must be created. In this case, prior agreement must be made as regards which SAP user(s) are to be used for such communication connections. The type of authorization must also be given careful consideration. Two alternatives are open to you: either create a standard user (per system) and store the users and password in the SEND_TAB script, or have each individual user log on. Note, however, that this second variant is not suitable for automated background processing.

    If you are installing the transceiver yourself, please proceed as described in the Installation instructions for the SAP CPIC transceiver module for communication with subsystems. You will find this documentation under Installation Instructions for the Transceiver.

    The characteristics peculiar to IS-H must be taken into account when installing the transceiver. These are documented under IS-HCM Specifications for the SAP Communication Module.

  2. Maintain number range ISH_NCI0 (TNKRS)

    Unique numbers are required for inbound messages. You have to set up their number ranges. You do this in the IMG activity Define number range.

  3. Create partner system in the SAP System (TXCOM)

    The SAP System has to know the technical data for the partner system. You make this declaration in the IMG activity Maintain TXCOM.

Note

To facilitate the creation of a new partner system, you can also use report RNCUTL19. Please refer to the program documentation.

  1. Maintain system and system attributes (TN02S)

    In this step you specify the logical systems and their attributes. This involves maintaining the corresponding system attributes for a logical system name. This name then represents the partner designation within the IS-H System.

    Attention: On no account make changes to (other) existing entries. Always contact the system administrator before deleting entries. In particular, systems of the type R3 or R2 are essential for productive IS-H operation even when no HCM connections are used.

  2. Check installation (program RNCCHK01)

    You should now execute the installation check. Please take note of any warnings or error messages issued.

  3. Set up receipt control (TNCI1)

    You now have to specify the events about which IS-H is to be informed by the partner system and how.

    IS-H basically supports the automatic receipt of particular messages triggered by corresponding events. These receipt options are supplied with the standard version and may not be modified.

    The only type of receipt control, i.e. who is to receive which message when, is receipt control without reference.

  4. List settings - extended check (program RNCLST01)

    Here you should generate a list of the settings for this system. Please take note of any warnings or error messages issued.

    You can archive a hardcopy of this list in order to track subsequent changes to settings.

  5. Test data transfer

    At this point you can and should test whether the specifications you have made do in fact result in correct data transfer.

    To do this, you basically have to trigger the main event by branching to the corresponding application on the partner system side.

Tip

Create a corresponding test file with the correct format in the transfer directory of the subsystem.

The programs

  • RNCGET01 Retrieve Case-Related Services From Partner Systems
  • RNCGET02 Retrieve Diagnoses From Partner Systems
  • RNCGET04 Retrieve OU-Related Services From Partner Systems
  • RNCGET05 Retrieve Surgical Data From Partner Systems

    take charge of data transfer. Start the corresponding program (for instance, via Utilities).

    Specify the name of the partner system on the selection screen. To avoid inserting the test data into the database synchronously, you may have to deselect Start update immediately.

    On successful completion, the programs list a transfer log. While processing is underway, the system issues information on any errors which occur. Take note of this information, but then choose ENTER in order to resume processing. Processing is complete only when the transfer log is displayed.

    In cases of successful transfer ("All data retrieved") at least one batch input session is created. You have to check this (search for this session in batch input processing).

    Providing you have kept to the name conventions, you can search specifically for sessions whose name begins with ISH_* (overview). The sessions are in the Sessions still to be processed.

    If a session is not created, please check through the steps you have just performed.

    You now have to check whether the data in the session is properly formatted. To do this, position the cursor in the corresponding line and choose F8=Session. You can then display all screen data and check that it is correct.

    Should you discover errors, always start by checking whether the supplied data format of the non-SAP system matches that specified in table TNCI1.

  1. Set up periodic formatting/dispatch

    This is essentially the task of the system administrator. He/she is also responsible for reorganizing the job log file. Reorganization may need to be frequent if automatic data transfer is active (see explanation below).

    Before going ahead with your settings, first check that corresponding jobs do not already exist. To do this, branch to the job overview. Here search for jobs whose name starts with ISHCM* regardless of user names. Any jobs you may find must be examined closely. Check whether they have been configured correctly and completely.

    If you do not find any ISHCM* jobs, you have to define/create background jobs. In doing so, it is essential to respect the IS-H naming conventions.

  2. Delete old HCM receipt logs periodically (NCI0)

    The use of automatic data transfer means that messages are received on an ongoing basis. The date/time of dispatch and the messages themselves(!) are recorded in log file NCI0.

    Inevitably an ever increasing number of successfully received messages are appended to file NCI0. This results in extensive disk space requirements. Finally, receipt can fail due to the database storage constraints.

    The background jobs themselves write many logs which in turn require storage space.

    To ensure smooth operation, you should set up background job ISHCM_CLEAR_PROTOCOLS_xxx. This ensures the orderly deletion of old logs.

Business Attributes
ASAP Roadmap ID 104    
Mandatory / Optional 3   Nonrequired 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_RECV 0 I010004207 Communication 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
IMGDUMMY D - Dummy object ONC5 3 Perform Installation Check 
IMGDUMMY D - Dummy object ONCE 3 Create List of Partner System Settings 
IMGDUMMY D - Dummy object SM35 2 Process Batch Input 
IMGDUMMY D - Dummy object SM36 3 Define/Create Background Jobs 
IMGDUMMY D - Dummy object SM37 3 Overview of Background Jobs 
SNC_SM54 T - Individual transaction object SM54 3 Maintain TXCOM 
TNKRS T - Individual transaction object ONCN N_ONCN_3 Maintain Number Ranges 
V_TNCI1 V - View SM30 2 Maintain Receipt Control Without Dependency 
History
Last changed by/on SAP  20021206 
SAP Release Created in