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.

  1. Define the logical systems in the SAP Reference IMG under Cross-Application Components ® Distribution (ALE) ® Basic Settings ® Logical Systems ® Define Logical System. Choose Edit ® New entries. Enter a name and a description for the logical system you want to create.
  2. Always ensure that assignment is unique. One client must always be assigned to only one logical system.

     

  3. To assign a logical system to a client, choose Distribution (ALE) ® Basic Settings ® Logical Systems ® Assign Logical System to Client. Select a line and choose Goto ® Details. The system displays the detail screen.
    In the field Logical System, enter the name of the logical system you want to assign to the client. Then save your settings.
  4. To define RFC destinations for the logical system, choose Cross-Application Components ® Distribution (ALE) ® Communication ® Define RFC Destination.
    The remote function call is controlled by the RFC destination parameters.
    The name of the RFC destination should match the name of the corresponding logical system.
    Define a RFC destination for both transmission directions.
    First enter the RFC destination (for example, B20CLNT323) for the R/3 connection. For more information about the other parameters, see
    Specifying Destination Parameters.
  5. 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.

  6. Define the system environment in the SAP Reference IMG under Cross-Application Components ® Distribution (ALE) ® Maintain Distribution Model (Transaction BD64).

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:

  1. Distribute the system landscape by choosing Edit ® Model view ® Distribute. The system displays a dialog box in which the systems relevant for you are already selected. Normally, you can just confirm the selections.
  2. In Transaction BD64, generate the partner profiles for all dependent systems (choose Goto ® Partner profile ® Generate).
  3. For information about partner profiles, see the IMG documentation (Cross-Application Components ® Distribution (ALE) ® Communication)

  4. Generate the partner profiles in all dependent systems for the central system.
  5. Define the system landscape for central user administration in the SAP Reference IMG under Cross-Application Components ® Distribution (ALE) ® Standard ALE Business Processes ® Standard Business Processes ® Central User Administration® Select Model View for Central User Administration. Use the F4 help (possible entries) to choose the distribution model you require and then choose Save. When you save the distribution landscape, the information is automatically distributed to the dependent systems.
  6. Define field distribution under Set Distribution Parameters for Fields (Transaction SCUM). For more information, see Defining Fields to be Transferred.