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 | OKCM_R2_DATATRANSFER | Data transfer from R/2 |
| Transaction Code | S_ALR_87000502 | IMG Activity: OKCM_R2_DATATRANSFER |
| Created on | 19981222 | |
| Customizing Attributes | OKCM_R2_DATATRANSFER | Data transfer from R/2 |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OKCM_R2_DATATRANSFER |
Target system maintenance in R/2
The target system to which the data should be sent is stored in the R/2 table T2420 in a parameter group. With the R/2 sender structure maintenance (table T242S), the target system is linked with the parameter group from table T2420.
Sender structure for transaction data in R/2
You maintain the sender structure in the R/2 system using table T242S (Transaction TM31). Tables T242I and T241S are automatically maintained at the same time and must exist in the current client.
The sender structure is also identified in the R/2 system with a sender program.
Sender structure for master data in R/2
- When maintaining the sender structure for master data records, you enter the:
- name of the sender program,
- target system (transfer method)
- language field name (any)
- sender field name (any)
- type and length of the sender field,
- name of the receiver field,
- length of the text field.
- The data records to be transferred must have the following structure:
Language field Sender field Text field
Example
A data record containing master data for company codes in English would, for example, look like this:
E001Company code 1
Collecting data from R/2
An R/2 sender program reads data and writes this data into the R/2 table DOUT. A system program (RSDRIVER with IMS or BS2000, or an assemler program) sends the data from table DOUT to the target system. The system program is automatically started, it logs onto the target system and transfers the data. As soon as the data has been transferred without an error message, it is deleted from DOUT.
You can display the status of the queue using transactions TMQD and TMQM.
If, in your R/2 - R/3 communication, the automatic sending of records from table DOUT is not supported (e.g. in DC system IMS), the sender records can be picked up by the R/3 system. This procedure is controlled by program RKCIMSST. The program requires a transfer method and a parameter group with the same name in table T2421. The parameter group, and therefore the transfer method, should begin with 'CP'.
You need to specify system control parameters 'GRPID' and 'DEST' for the parameter group in table T2420. For parameter 'GRPID', you enter the origin, e.g. CPBS1. For parameter 'DEST', you enter the LU (logical unit in R/2), in other words the value which you maintained in the R/2 system under system parameter value 'QDEST'. You should also note that the receiver routine in R/3 is called 'IMS_REC_AND_TRANS' for this type of communication. You enter it in the R/2 system under system parameter 'QMODU'. This is true for both master and transaction data.
If you have to collect data from R/2, you should set up the data transfer from R/2 so that different sender programs use different LUs.
Blocked data transfer from R/2 as of Release 5.0F
As of R/2 Release 5.0F, it is possible to set the parameters for data transfer from R/2 so that several logical data records are transferred to a physical record. Blocked data transfer has the advantage of considerably improving response times.
To set up data transfer, you need to make the following entries in R/2 in table T2420:
Group Abbr. Param.val. Parameter description
BLOCK MODE ON Block data transfer (ON/OFF)
BLOCK CPIC 16027 CPIC block size
BLOCK LUW 9999999 Number of transfer blocks for a LUW
LUW (Logical unit of work)
If anything other than ON is entered for BLOCKMODE, the data will not be transferred in block.
The greatest possible parameter value for BLOCK CPIC depends on the R/2 operating system and net configuration. The maximum size is 16027 bytes. If a greater number is entered, the maximum block size remains 16027 bytes. If the program RSDRIVER is used to send the data (with IMS and BS2000) the maximum size is 3900 bytes; this must also be entered.
The entry BLOCK LUW determines after how many physical records the queue is implicitly closed and reopened. In the R/2 operating system a LUW is not completed until the queue is closed. To prevent the LUWs becoming too big, you can limit the LUW block size with the entry BLOCK LUW.
In the log in R/3, this is indicated by the message 'Pause'. This is the same as the effect as when data is written in a queue from various program runs (variants). If the data transfer terminates and a part of the LUWs were transferred but another part were not, you can import the data in the transferred LUWs in the R/3 SAP-EIS menu under Tools -> Transfer log -> Edit and you can start the transfer again for the LUWs which were not transferred using R/2 transaction TMQD.
Business Attributes
| ASAP Roadmap ID | 254 | Transfer Data |
| 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 | OKCM_R2_DATATRANSFER | 0 | HLA0009491 | Data Collection |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
