SAP ABAP IMG Activity SIMG_CFMENUNMO4ONC6 (Maintain System Attributes)
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_CFMENUNMO4ONC6 Maintain System Attributes  
Transaction Code S_KK4_74000212   IMG Activity: SIMG_CFMENUNMO4ONC6 
Created on 19990816    
Customizing Attributes SIMG_CFMENUNMO4ONC6   Maintain System Attributes 
Customizing Activity SIMG_CFMENUNMO4ONC6   Maintain System Attributes 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUNMO4ONC6    

In this IMG activity, you specify the logical systems and define their attributes.

Caution

Under no circumstances modify existing (other) entries. Always contact the system administrator before deleting entries. In particular, systems of the type "R3" or "R2" are essential for IS-H production operation even if no HCM connections are used.

Recommendation

To simplify the creation of a new partner system you can also use the HCM Precustomizing report (RNCUTL19). Please read the report documentation.

Activities

  1. For the logical system name, use an explicit short description for the partner system under which the system is known in your healthcare facility. This name is then always used to designate the partner system within IS-H.
  2. The system names are valid for all clients. This means that the technical specifications (in particular the assignment to the TXCOM entries) also apply to all clients. You should keep this in mind should your system operate with several clients at the same time. Create separate systems with separate attributes (in particular, TXCOM names) for each client. This avoids data being transferred into the wrong client.
  3. The system type "ST" is - from SAP's perspective - a non-SAP system. Enter a "1" here accordingly.
  4. If the application release is of importance, you should enter it in the Release field.
  5. When you define a new partner system, you always have to flag the External System checkbox in order to enable communication.
  6. You can also block systems here. If you set the blocking indicator, the blocked system is considered by IS-H as excluded from the communication process. Consequently, no messages are generated or dispatched for this system, and messages can no longer be retrieved from this system. This does not, however, prevent the partner system from delivering messages to the IS-H system.
    This indicator is intended to disable a partner system temporarily, without having to shut down complete HCM data communication or the usual data retrieval procedures.
  7. Enter the technical communication name of this logical system from table TXCOM in the XCOM Name field.
  8. Convention: The first seven characters of the (technical) TXCOM name must form a unique identification. In particular, the TXCOM name must contain at least seven characters. The system requires the eighth character as control information for a number of communication processes.
    It is also recommended to use a TXCOM name with a recognizable link to the IS-H system. This provides a clearer picture should your table contain many TXCOM entries. Enter names that start with "ISH", "HCM" when maintaining the TXCOM table.
  9. Here you can also make default settings with regard to the communication standard (name, version) and agreed special characters used for the exchange of messages with this system. However, these specifications only apply if alternative agreements have not been made for the individual case.
  10. Flagging the All in One checkbox stipulates that all messages from the IS-H system are written to a single file (NTISH.dat) on the partner system side. This is the default setting. If you do not set this indicator, the messages are grouped according to message type and placed in separate files (all admission records in NT011.dat, transfers in NT012.dat, discharges in NT013.dat, patient merges in NT018.dat). This, however, is only supported up to and including IS-H Release 4.03.

As of IS-H Release 4.61, the Patient Events indicator lets you stipulate whether patient events are also to be transmitted from the IS-H system to partner systems. If you do not set this indicator, system behavior is the same as prior to the introduction of this option, and patient events are suppressed. If you set this indicator, patient events that occur are transmitted to the partner system. The following patient events are transmitted:

  • EVT_ANLEGEN_PAT
  • EVT_ANLEGEN_PAT_K
  • EVT_ANLEGEN_PAT_N
  • EVT_CHANGED_PAT
  • EVT_CHANGED_PAT_K
  • EVT_CHANGED_PAT_N

  1. If a character set other than that used in the SAP system is required on the partner system side, you can make a corresponding specification to initiate character set conversion. However, this is seldom necessary. You should specify the required character set here only if you experience problems with different character sets.

Special cases:

  • If you want to communicate between an ASCII system (SAP System on an ASCII host) and an EBCDIC host (non-SAP system), you must specify the EBCDIC character set (SAP character set no. 500) here. If the SAP System and non-SAP system are both running on AS/400 hosts (EBCDIC systems), character set conversion is not required.
  • If the HCM transceiver is on an EBCDIC host, you must always transmit the application data also in EBCDIC. This also means you must provide data you want to transmit to the SAP System in EBCDIC.
    The following applies to the EBCDIC transceiver:
    • Conversion is not allowed from EBCDIC-SAP System or to EBCDIC-SAP System. If you specify a conversion here, the programs are no longer capable of processing the data in an expedient manner. If the files to be transmitted to the SAP system are not provided in EBCDIC, this operation terminates. Depending on the application data, this may also result in different error situations.
    • You must specify character set 500 from an ASCII-SAP system.
    • If you require a file in a character set other than EBCDIC, you must use an external conversion program to convert the file after it has been successfully transmitted. For transmission from the EBCDIC transceiver to the SAP system, you must use an external program to convert the file from other character sets to EBCDIC before initiating the transmission.

Business Attributes
ASAP Roadmap ID 205    
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   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_CFMENUNMO4ONC6 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
V_TN02S V - View ONC6 1 IS-H Systems and System Attributes 
History
Last changed by/on SAP  19990816 
SAP Release Created in