|
Satellites on Separate SAP System |
|
RFC_DEST
This constant is used to establish an RFC connection to another R/3 system (remote system) for the supplementary tables /KERN/IPPSAT01 till /KERN/IPPSAT49. Allevo then accesses data in the remote system while reading and writing these tables.
Background: this feature may be used especially for personnel planning in case that data protection regulations do not permit personal data, even if protected, to be saved on the source system.
An additional SAP transport provided by Kern AG is required to import tables in the remote system (18 satellites are by default included there). Via additional transport, a maximum of up to 49 satellites may be accessed in the remote system.
The following steps
are necessary to establish the connection:
· An RFC destination (type ABAP connection) must be created for transaction SM59 in the source system (the system where Allevo is started).
· The RFC destination ID entered for RFC_DEST in column Value from.
·
A 49-digit combination
of the numbers 0 and 1 must be entered in column Value to.
Digits 1 to 49 specify which table will be activated.
0 stands for reading
from the source system;
1 refers to reading from the remote system via RFC.
The combination 001 would therefore mean that only data of the table /KERN/IPPSAT03
are stored in the remote system
(installation possible via
Sat.Assistent).
· The table structure should preferably be the same in both systems (remote and local, i.e. same appends). Completely identical structures, however, are no longer necessary: in current SAP versions, it is sufficient to use the same field names. When accessing, SAP itself checks for name equivalence (possibly, not all fields will be filled/read, the RFC access, however, will not be interrupted).
After these installation steps, Allevo stores all satellite data in the remote system (and reads from there as well).
|
Note: |
Constant RFC_DEST must always be entered in the so called * layout. Entries in named Allevo layouts will be ignored: regarding the remote mode, a satellite table is thus treated the same way in all layouts. Only one remote system can be addressed, which means, the tables cannot be distributed across several remote systems (controlled by the setting for *-Layout). The RFC user must at least hold the Allevo planner authorization in the remote system (group ZIPP_PLA for authorization object S_PROGRAM). |
Provided that these steps are taken, data of the satellite table will be read from the remote system and also stored there. There are no data stored in the source system.
New from version 2.8
Support of a maximum of 49 satellites in the remote system.
New from version 3.3
The used RFC user must have the Allevo planner authorization in the remote system.