Setting Up the System Infrastructure and Data Transfer 

Possible Uses

Because data is distributed between systems, it is necessary to identify each system within a network. The logical system is used for this purpose.

Various applications that run on a common database are grouped together in a logical system. This applies to both the source and target system.

You can assign a logical system to a client in client maintenance in the R/3 System. From SAP APO release level 3.0A, APO differentiates between different clients.

For further information, see ALE Implementation and Administration

Do not use the same name for more than one logical system.

If data from different logical systems reference the same objects in SAP APO, there are two courses of action:

  1. Define a business system group (BSG) It integrates different physical systems to a superordinate logical unit (the settings for Business System Group are carried out using the following path: APO Implementation Guide ® Advanced Planner and Optimizer (APO) ® Basis Settings ® Integration ® Business System Group ® Maintain Business System Group).

    2. It is recommended that you assign the APO System to the same BSG to which the logical system or R/3 instance(s) that contain the master data server belong. Only then can preliminary maintenance of the master data be carried out in APO.

  2. Set up mapping structures, which means maintaining/activating user enhancements. For further information, see Customer Exits.

In order to be able to uniquely refer to identical keys from different business system groups in APO, the primary key is supplemented by the business system group key. The following graphic illustrates an example of this scenario.

In a multi-system environment into which APO is to be integrated, there are two logical systems (LS1 and LS3) in different business system groups (BSG 1 and BSG 2). As Material 1 is used as the name for two different products (‘screw’ in LS1 and ‘hammer’ in LS3), this conflict must be solved when integrating APO. It is possible, using a Customer Exit, to write a company-specific convention that will correct this situation and guarantee clarity.

Prerequisites

At least one R/3 and one APO System must be successfully installed.

If the R/3 system was previously active as a stand-alone system, it is possible that the (system) distribution (ALE) is not sufficiently maintained. Check whether your R/3 system ALE is active, and maintain the logical system in R/3 Customizing accordingly.

Process Flow

You must make various settings both for APO and for the APO Core Interface in R/3 before the actual data transfer between R/3 and SAP APO can be started. To set up the system, follow the steps in the Checklist for Setting Up the System Infrastructure

Result

After completing the individual Customizing steps to set up an integrated system infrastructure, your next step is to trigger the data transfer itself.

For further information, see Data Transfer