SAP ABAP IMG Activity SIMG_CFMENUOKCMOKCD (Maintain transfer method)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ KC (Package) Cost Accounting Controlling EIS
IMG Activity
ID SIMG_CFMENUOKCMOKCD Maintain transfer method  
Transaction Code S_ALR_87000150   IMG Activity: SIMG_CFMENUOKCMOKCD 
Created on 19981222    
Customizing Attributes SIMG_CFMENUOKCMOKCD   Maintain transfer method 
Customizing Activity SIMG_CFMENUOKCMOKCD   Maintain transfer method 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUOKCMOKCD    

During the data transfer from one system to another, you must differentiate between the source system and target system. The source system contains the operative data which is selected from a sender program and transferred to the target system. There are three possible ways of starting the sender program:

  • You can start the sender program from the target system using program RKCSUB00.
  • You can start the sender program from the source system online.
  • You can schedule the sender program for background processing from the source system.

Depending on whether you are in the target or source system and how you wish to start the data transfer, you must maintain the transfer method differently.

  • You must maintain the transfer method in the source system. This involves maintaining section 'Target system' where you enter with which user and client the source system should log onto the target system and section 'Queue' where you define a queue name and enter driver program RKCDRIVE.
  • You should create a transfer method in the target system which has the same name as the transfer method in the source system. If you start the sender program in the source system, you only need to enter a transfer method in the target system. You do not need to make entries in sections 'Target system' and 'Queue'.
  • If you start the sender program from the target system using program RKCSUB00, you need to enter how the target system is to log onto the source system. You do this in the target system when you enter the transfer method on the selection screen of RKCSUB00.

Using different transfer methods, you can differentiate between data transfer logs of transfers from various source systems or clients in a source system. The transfer paths must match in the source and target systems. There must be a transfer path of the same name in the target system to match the transfer path in a source system. This is how a data transfer is identified from the source system in the target system.

Prerequisites

The user you enter in the target system must exist in the relevant system as a CPIC user.

You must have maintained the symbolic destination from the main SAP menu under Tools -> Administration -> Administration -> Network -> TXCOM Maintenance.

Action

Create a queue System -> Services -> Queue. This step is not necessary in an R/2 source system. The data to be transferred is written in the queue. In addition, a leading record containing information about the sender program and closing record are written. The queue should be type 'A' as should the start mode. You can choose other modes, however, in that case you need to make sure that the queue data is transferred periodically. To do this, you schedule jobs for program RKCDRIVE.

  • Queue driver program RKCDRIVE
  • Program SAPFKCIM
  • Form RECEIVE_AND_TRANSFER

Maintain the transfer paths.

You can access several examples.

Special transfer methods

Certain transfer methods have been predefined:

  • Transfer method 'FILE' is used to import data from a file.
  • Transfer method 'SELEC' is used to summarize an aspect.
  • Transfer method 'LOCAL' is used for data transfers using ABAP/4 query within one system.

Further notes

For more information on maintaining Table TXCOM see, Help -> SAP Library -> Basis -> System administration -> R/3 Network configuration -> SAP communication: Configuration.
Transport Settings

Business Attributes
ASAP Roadmap ID 255   Create Interfaces 
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_CFMENUOKCMOKCD 0 HLA0009491 Data Collection 
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_T242Y V - View SM30 9999999999 Transfer parameters 
History
Last changed by/on SAP  19981222 
SAP Release Created in