SAP ABAP IMG Activity SIMG_CFMENUNMO4SM54 (Maintain Technical Connections (Table TXCOM))

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_CFMENUNMO4SM54	Maintain Technical Connections (Table TXCOM)
Transaction Code	S_KK4_74000211	IMG Activity: SIMG_CFMENUNMO4SM54
Created on	19990816
Customizing Attributes	SIMG_CFMENUNMO4SM54	Maintain Technical Connections (Table TXCOM)
Customizing Activity	SIMG_CFMENUNMO4SM54	Maintain Technical Connections (Table TXCOM)

Document

Document Class	SIMG	Hypertext: Object Class - Class to which a document belongs.
Document Name	SIMG_CFMENUNMO4SM54

Use

In this IMG activity, you specify technical connection names and define their attributes.

Activities

Specify a name for the communication to the partner system in the Dest. (destination) field (refer to the naming conventions below).
Enter the network name of the partner host in the LU (logical unit) field.
Enter the name of the partner program on the non-SAP system side in the TP (transaction program) field. This is usually a command file. If operating system-related file extensions are stipulated (.CMD for OS/2 or Windows NT, for example), you have to adhere to these conventions here. For OS/400 you have to enter the complete IFS path for the executable configuration program here (not the actual HCM transceiver program, but /QSYS.LIB/R331IOPT.LIB/AS4GETRSP.PGM, for example).
With multi-client operation, ensure that the same transaction program is never called by the same partner system from two different clients. This could result in data being transferred into the wrong client.
The communications type (Log field) is "E". This indicates that the partner is a C program and is started via Remote Shell.
The Gateway Host field specifies the host on which the SAP gateway was started.
The Gateway Service field specifies the TCP/IP service via which the gateway expects connection logins (e.g. sapgw00).

You are not obligated to specify these gateway entries (refer to the F1 field help).

Conventions

The first seven characters of the (technical) TXCOM destination name must form a unique identification. In particular, this name must comprise at least seven characters. The system requires the eighth character as control information for a number of communication processes:

The eighth character of the TXCOM destination name must be "1" for connections to the SAP communication module PUT_TAB. Your transaction protocol should start with PUT_TAB (or put_tab).
The eighth character of the TXCOM destination name must be "2" for connections to the SAP communication module GET_TAB. Your transaction protocol must start with GET_TAB (or get_tab).
The eighth character of the TXCOM destination name must be "3" for connections to the SAP communication module GET_RESP. Your transaction protocol must start with GET_RESP or get_resp.
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" or "HCM".

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_CFMENUNMO4SM54	0	I010004207	Communication

Maintenance Objects

Maintenance object type

Customizing Object

Assigned objects
Customizing Object	Object Type	Transaction Code	Sub-object	Do not Summarize	Skip Subset Dialog Box	Description for multiple selections
SNC_SM54	T - Individual transaction object	SM54	1			Maintain TXCOM

History

Last changed by/on	SAP	20021206
SAP Release Created in

Object Hierarchy

Used by

Advertise Links