Introduction: Setting up (CUA) 
System distribution (ALE) requires that every system in a network be uniquely identified. This is what a "logical system" is for. In the R/3 System, a logical system is a client.
The following steps describe how to define each and every client in the central user administration as a logical system. You first have to create the logical systems. Then you assign each client to a corresponding logical system. Further activities related to defining central user administration can be found at the end of this section.

Always ensure that assignment is unique. One client must always be assigned to only one logical system.
Specifying Destination Parameters.

Use all capital letters for the destination definition.
The user you specify for logging on to the other system must have the authorization SAP_ALL. The name for this user should be clearly recognizable. This name will appear under Last changed by in the central system.
The distribution model is used to specify which applications communicate with each other in your distributed systems. The distribution model contains all of your company’s cross–system message flow information. The distribution model consists of several model views. In each model view, you can define related message flows. Each model view is maintained in a central system and distributed from there to the other systems.
For each model view, you can specify a descriptive short text, the validity period of the message flows in the view, as well as the view maintenance system. When a model view is created, the system in which the view is created is automatically specified as the maintenance system. If possible, designate one system as the central maintenance system for all model views. The names of the model views must be unique in the entire distributed environment within your company.
Do the following:


For information about partner profiles, see the IMG documentation (Cross-Application Components ® Distribution (ALE) ® Communication)