Migration tools are used to distribute data between R/2 and more recent SAP systems. These tools are necessary because a rather complicated set of rules is required to map R/2 data structures to newer SAP data structures.
These migration rules are used to control the distribution across an ALE server to a more recent SAP system. (The migration guide contains further details.)
The distribution process can be broken down into two stages. The first stage consists of a permanent migration of the objects to be distributed from an R/2 system to a more recent SAP system (the ALE server), whilst the second stage is the distribution of the data from the ALE server to one or more target SAP systems.
Distributing Data Between Coupled R/2 and SAP Systems
The ALE server converts the data format and transfers the data between the host system and the SAP instances.
When distributing data in the reverse direction, the data to be sent to the R/2 system is addressed to the R/2 system (the R/2 system is specified as the logical system). The data is first transferred to the ALE server via the port specification.
Firstly, carry out the normal inbound processing steps in the ALE server.
A comparison between the target logical system and your logical system shows that the inbound IDoc has to be sent to the R/2 System:
· The new port is determined.
· The IDoc is placed in the outbox.
· The dispatch function module is called. It transmits data to R/2 via CPI-C.
· The R/2 System recognizes the data as an inbound IDoc.
· An application module posts the IDoc in R/2.
The data is imported into the R/2 System via appropriate interfaces. These could be batch input interfaces. Alternatively, if an application has an adequate number of EDI interfaces in both directions (usually the case for document data), then these may be used for the distribution.
R/2 System Release 5.0F or later is required for the EDI communication between R/2 and newer SAP systems.