Distributing Master Data From R/2 to R/3
Data is distributed between R/2 and R/3 Systems using the migration tools designed for data migration from R/2 to R/3. This is necessary because a rather complicated set of rules is required to map R/2 data structures to R/3 data structures.
These migration rules are used to control the distribution across an ALE server to an R/3 System. (The migration guide contains a comprehensive description of the migration tool.)
Thus 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 an R/3 System (the ALE server), whilst the second stage is the distribution of the data from the ALE server to one or more target R/3 Systems.
Distributing Data Between Coupled R/2 And R/3 Systems
The ALE server converts the data format and transfers the data between the host system and the R/3 instances.
Distributing Transaction Data From R/3 To R/2
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 and the data is transmitted to the ALE server via the port definition).
Firstly, perform the steps for normal inbound processing 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 data is imported in the R/2 System using 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 for data transfer between R/2 and R/3.