Creating an R/3 Source System

Creating an R 3 Source System

A high-level procedure for creating an R/3 source system involves the following steps:

  1. Creating a logical system for the R/3 client
  2. Creating a logical system for the BW client
  3. Naming background users
  4. Creating the R/3 source system in BW

Note

Some activities were carried out before the screens shown in this chapter were captured. Here we can only check their status.

 

10.1.1 Creating a Logical System for the R/3 Client

A client is a subset of the data in the SAP database. It belongs to a legally and organizationally independent function group. When a user logs on to an SAP system, he or she actually logs on to a particular client as specified in the logon screen. In Section 11.3, "Creating a Characteristic in BW," we will see how the client is defined at the database level.

A logical system identifies a client in an SAP system. SAP systems, whether R/3 or BW, communicate with one another using logical systems instead of clients. An R/3 system can have client 100, and a BW system can also have client 100. Logical systems allow us to distinguish between these two clients although both are numbered 100.

The following procedure shows how to create a logical system.

Work Instructions

Step 1. Log on to the R/3 source system, run transaction SPRO, and then click graphics/sapreferenceimg.gif. IMG stands for IMplementation Guide.

 

 

SCREEN 10.1

graphics/10fig01.gif

Step 2. Click graphics/clock.gif next to Define Logical System to execute the function.

 

 

SCREEN 10.2

graphics/10fig02.gif

Step 3. Click graphics/continue.gif to continue.

 

 

Note

In either an R/3 or BW SAP system, some data are client dependent; other data are client independent. Client-independent data are also called cross-client data. The data about the logical system definition is client independent.

SCREEN 10.3

graphics/10fig03.gif

Step 4. We see a logical system named as TC1_200. We will soon find out that it represents system TC1 and client 200. TC1 is the R/3 system ID.

 

 

Note

To create a new logical system name, click graphics/newentries.gif.

SCREEN 10.4

graphics/10fig04.gif

Step 5. Return to Screen 10.2, and then click graphics/clock.gif next to Assign Client to Logical System to execute the function.

 

 

SCREEN 10.5

graphics/10fig05.gif

Step 6. Click graphics/continue.gif to continue.

 

 

SCREEN 10.6

graphics/10fig06.gif

Step 7. Select client 200, and then click graphics/detail.gif to view the client definition.

 

 

SCREEN 10.7

graphics/10fig07.gif

Step 8. Note that logical system TC1_200 is assigned to client 200.

 

 

Note

The Changes to Repository and cross-client Customizing allowed option in the Client-independent object changes block must be selected. The procedure of turning system TC1 client 200 into a source system in BW will create a background user and set up RFC (Remote Function Call) related configurations in R/3 and BW.

Tip

If system TC1 client 200 is a production client, we can switch off this option after creating the source system in BW.

SCREEN 10.8

graphics/10fig08.gif

Result

The logical system TC1_200 represents the system TC1 client 200.

10.1.2 Creating a Logical System for the BW Client

Work Instructions

Step 1. Log on to the BW system, and repeat Step 1 in Screen 10.1. Next, click graphics/clock.gif next to Define Logical System to execute the function.

 

 

SCREEN 10.9

graphics/10fig09.gif

Step 2. Click graphics/continue.gif to continue.

 

 

SCREEN 10.10

graphics/10fig10.gif

Step 3. The logical system BTC_100 is already created. We will find out soon that it represents system BTC client 100. BTC is the BW system ID.

 

 

SCREEN 10.11

graphics/10fig11.gif

Step 4. Return to Screen 10.9, and then click graphics/clock.gif next to Assign Client to Logical System to execute the function.

 

 

SCREEN 10.12

graphics/10fig12.gif

Step 5. Click graphics/continue.gif to continue.

 

 

SCREEN 10.13

graphics/10fig13.gif

Step 6. Select client 100, and then click graphics/detail.gif to view the client details.

 

 

SCREEN 10.14

graphics/10fig14.gif

Step 7. Note that the logical system BTC_100 is assigned to client 100.

 

 

Note

For the same reason mentioned in conjunction with Screen 10.8, the Changes to Repository and cross-client Customizing allowed option in the Client-independent object changes block must be selected.

SCREEN 10.15

graphics/10fig15.gif

Result

The logical system BTC_100 represents system BTC client 100.

10.1.3 Naming Background Users

TC1_200 and BTC_100 communicate with each other through system users. For our example, we will name ALEREMOTE as the user in system TC1 client 200 and BWREMOTE as the user in system BTC client 100.

Work Instructions

Step 1. Return to Screen 10.12, and click graphics/clock.gif next to Maintain proposal for users in the source system (ALE communication) to execute the function.

 

 

SCREEN 10.16

graphics/10fig16.gif

Step 2. ALEREMOTE is the default name. Accept it and return to the previous screen.

 

 

SCREEN 10.17

graphics/10fig17.gif

Step 3. Click graphics/clock.gif next to Create background users for links to SAP Systems to execute the function.

 

 

SCREEN 10.18

graphics/10fig18.gif

Step 4. Enter BWREMOTE and a password, and then click graphics/continue.gif to save the configuration.

 

 

SCREEN 10.19

graphics/10fig19.gif

Result

Two system users are named. You will create them next.

10.1.4 Creating an R/3 Source System in BW

Now we are ready to create TC1_200 as an R/3 source system in BTC.

Work Instructions

Step 1. From the BTC BW Administrator Workbench, click Source systems in the left panel. In the right panel, right-click Source systems, and then select Create….

 

 

Note

A BW system can serve itself as a source system. We will see how this process works in Section 13.1, "BW Statistics."

SCREEN 10.20

graphics/10fig20.gif

Step 2. Select the first option because TC1 is 4.6B, higher than 3.0D. Click graphics/continue.gif to continue.

 

 

SCREEN 10.21

graphics/10fig21.gif

Step 3. Enter the application server host name of the R/3 source system, its system ID and system number, and the passwords for ALEREMOTE and BWREMOTE. Click graphics/continue.gif to continue.

 

 

SCREEN 10.22

graphics/10fig22.gif

Step 4. Click graphics/continue.gif to continue.

 

 

Note

BW will check the authorizations in the next screen. We need sufficient authorizations so that we can create the users ALEREMOTE and BWREMOTE and configure the system settings. We will see the result in Screen 10.27.

SCREEN 10.23

graphics/10fig23.gif

Step 5. Enter the user ID and password, and log on to TC1 client 200.

 

 

Note

This step is necessary to verify that we have the authorization needed to access the R/3 source system.

SCREEN 10.24

graphics/10fig24.gif

Step 6. Click graphics/continue1.gif.

 

 

Note

This message notes that ALEREMOTE had been created prior to this step. Also, this message indicates that the password and authorization profile we set up earlier must be correct.

SCREEN 10.25

graphics/10fig25.gif

Result

You have created a new source system TC1_200 in BW (Screen 10.26).

SCREEN 10.26

graphics/10fig26.gif

Note

This procedure would create the ALEREMOTE user in system TC1 client 200 and the BWREMOTE user in system BTC client 100, both with appropriate authorization, if they did not exist. It would also create two RFC (Remote Function Call) destinations, one in system TC1 and the other in system BTC.

To check the RFC destination information in BTC, run transaction SM59. In Screen 10.27, we see that the RFC destination TC1_200 contains the necessary information for user ALEREMOTE to log on to system TC1 client 200, such as the host machine name bobhpd04 and the SAP system number 04.

TC1_200 and BTC_100 locate each other by using the RFC destinations and log on to each other as the ALEREMOTE and BWREMOTE users.

SCREEN 10.27

graphics/10fig27.gif

With RFC destinations, the following settings were also created:

  • IDoc partner profiles
  • IDoc port definitions
  • IDoc types
  • IDoc segments

IDoc (Intermediate Document) is a template that SAP systems use to exchange data with one another and with outside systems. An IDoc consists of three types of records (Figure 10.2):

  • The Control Record contains administration information, such as the sender and the recipient. It uniquely identifies an IDoc.
  • The Data Records contain segments and their administration information, such as the parent segment to which they are attached. The segments hold real data.
  • The Status Records contain all of the processing status information.

Figure 10.2. IDOC STRUCTURE

graphics/10fig01b.gif



SAP Bw. A Step-By-Step Guide
Sap Bw: a Step By Step Guide for Bw 2.0
ISBN: B000LZM8CM
EAN: N/A
Year: 2002
Pages: 106
Flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net