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 | ISH_EIS_RFC | Data Transfer Beyond System Limits via RFC for EC-EIS |
| Transaction Code | S_KK4_74000436 | IMG Activity: ISH_EIS_RFC |
| Created on | 19990816 | |
| Customizing Attributes | ISH_EIS_RFC | Data Transfer Beyond System Limits via RFC |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | ISH_EIS_RFC |
To be able to transfer data from the IS-H system into EC-EIS running on another system via RFC, you must perform the preparatory tasks relating to EC-EIS settings described in this IMG activity.
Requirements
- Compare and, if necessary, synchronize the DDIC structures in the source and target systems
Both systems must contain the same version of the sender structure RNEISTRANS as well as the included structures RNEISand RNEISHEADER.
You can compare the structures in the two systems as follows: From the SAP Easy Access menu, choose Tools -> ABAP Workbench -> Development -> ABAP Dictionary. Here choose Utilities -> Versions -> Version Management -> REMOTE Compare. You can list the mismatching fields by choosing List -> Delta Display.
If the structures are not contained in the target system, transport these from the IS-H source system using the Transport Organizer Tools (transaction code SE03).
The system subsequently remaps enhanced existing aspects in the database.
Caution: If the structures are not identical, the field contents of characteristics and key figures are filled incorrectly, or with initial values when data is transferred. An automatic consistency check beyond system boundaries is not possible.
- Create the RNUEIS sender structure for the RNEISTRANS data structure in the target system
Create a sender structure with the name RNUEIS, in the same way as in the source system, and enter the DDIC structure at item 1. You do this by choosing Accounting -> Enterprise Controlling -> EIS -> Environment -> Configuration Menu -> Data Transfer -> Transaction Data -> Sender Structure. Double keys must be permitted and you have to specify the target aspect.
- Generate an RFC function module in the target system
Create an RFC function module for the sender structure you have just created. To accommodate data transfer, it must be possible to call this function module from the source system. You generate such an RFC function module by choosing Environment -> Generate RFC.
- Create transfer rules for the RNUEIS data structure in the target system
You must also maintain transfer rules for the RNUEIS data structure in the target system. For further information about how to do this, see Make Settings in EC-EIS.
Important Note:
The data in the target system can only be overwritten during data transfer beyond system boundaries if you set the Overwrite indicator in the definition of the transfer rules for the basic key figures. Since the generated report that deletes the aspect data cannot be automatically called beyond system boundaries, to be on the safe side, delete the data pertaining to the periods and the institution to be transferred from the aspect using a function of EC-EIS, before starting data transfer.
- Set up SAP system destinations for the connection of source and target systems
In the source system, expand the ABAP Connections node in the hierarchical list of RFC destinations by choosing Tools -> Administration -> Administration -> Network -> RFC Destinations.
Check if a connection is already established between your source and target system in the list displayed. You can then specify the name of this connection as the RFC target system in the RNUEIS program, to start data transfer beyond system boundaries.
If no connection exists, establish a new connection. To do this, proceed as described in Maintaining Remote Destinations (to access this documentation, choose Help -> Application Help).
Data transfer with background processing requires the logon data including the password of the user who schedules data transfer to run as a background job to be entered in the source system.
Business Attributes
| ASAP Roadmap ID | 207 | Establish Reporting |
| 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 | ISH_EIS_RFC | 0 | I041002011 | Integration with Executive Information System |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20010724 |
| SAP Release Created in |
