Hierarchy

⤷

⤷

IMG Activity
ID | OLIS_KOPP4B | Define settings in the R/3 System |
Transaction Code | S_ALR_87000857 | IMG Activity: OLIS_KOPP4B |
Created on | 19981222 | |
Customizing Attributes | OLIS_KOPP4B | Define settings in the R/3 System |
Customizing Activity | OLIS_KOPP4B | Define settings in the R/3 System |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | OLIS_KOPP4B |
The following tables must be maintained in R/3:
- T242I
This table contains sender information and can be maintained with using the transaction SM30 (View Maintenance).
Note
With older Releases, import the table entries by using the OSS note 0027768.
- T242S
Here, you maintain the sender structures (or programs for data collection from R/2) for the master data texts. The procedure is the same in both cases.
This table can be called up from the implementation guides for the Logistics Information System (LIS).
Note
A detailed description of Maintain the sender structures can be found in the implementation guides for SAP EIS (Executive Information System).
- T2421
Maintain the parameter groups in the system control parameters.
After a sender program has collected data from R/2, they are then written into the file DOUT (queue file). As soon as this data has been transferred without an error message into the R/3 system, they are deleted from the DOUT file.
If you want to work with the DC system IMS, you cannot automatically send the sender data records from the file DOUT. In this case, the sender data records must be "retrieved" with the program RKCIMSST from the DOUT file.
In addition, you must specify a paramter group in this table. Using this parameter group will identify the target of the data.
You maintain table T2421 by using transaction SM31.
- T2420
You only have to maintain this table if you want to work in R/2 with an IMS system.
Maintain the system control parameters GRPID and DEST for the parameter groups which are given in the table T2421. For parameter GRPID specify the origin of the data as the parameter value, and for the parameter DEST, the LU (Logical Unit) in R/2.
Maintain table T2420 also using transaction SM31.
Recommendation
If the data must be "retrieved" from R/2, you should organize the data transfer from the R/2 system in such a way that the various sender programs use a variety of LUs.
Business Attributes
ASAP Roadmap ID | 255 | Create Interfaces |
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 | OLIS_KOPP4B | 0 | HLA0006426 | Data Collection |
SIMG | OLIS_KOPP4B | 1 | O HLA0001547 | |
SIMG | OLIS_KOPP4B | 2 | O HLA0001552 | |
SIMG | OLIS_KOPP4B | 3 | O HLA0009760 |
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 |
KCDM | L - Logical transport object | OKX6 | LIS1 | LIS: Sender structures for R2/R3 connection |
History
Last changed by/on | SAP | 19981222 |
SAP Release Created in |