Creating an R/3 Source System - SAP BW

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

  • Creating a logical system for the R/3 client
  • Creating a logical system for the BW client
  • Naming background users
  • 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.

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,"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 clicksap-reference. IMG stands for IMplementation Guide.
IMplementation Guide.

Step 2. Click Clicknext to Define Logical System to execute the function.
Display IMG

Step 3. ClickClick 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.
Information

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,clicknew-entry.
Change view logical systems overview

Step 5. Return to Screen, and then clickClick next to Assign Client to Logical System to execute the function.
Display IMG

Step 6. Click Clickto continue.
Information

Step 7. Select client 200,and then click to view the client definition.
Change view clients overview

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.
Change view clients details
Restrictions

Result:
The logical system TC1_200 represents the system TC1 client 200.

Creating a Logical System for the BW Client:

Work Instructions:
Step 1. Log on to the BW system,and repeat Step 1 in Screen. Next,click Clicknext to Define Logical System to execute the function.
Customizing execute project

Step 2. Click Clickto continue.
Information

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.
Change view logical systems overview

Step 4. Return to Screen,and then click next to Assign Client to Logical System to execute the function.
Customizing Execute projects

Step 5. ClickClick to continue.
Information

Step 6. Select client 100,and then click to view the client details.
View the client details

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

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

Result:
The logical system BTC_100 represents system BTC client 100.

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,and clickClick next to Maintain proposal for users in the source system (ALE communication) to execute the function.
Customizing execute projects

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

Step 3. ClickClick next to Create background users for links to SAP Systems to execute the function.
Customizing Execute project

Step 4. Enter BWREMOTE and a password,and then clickClick to save the configuration.
create background user in the war

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

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,"BW Statistics."
Administrator work bench modelling

Step 2. Select the first option because TC1 is 4.6B,higher than 3.0D. ClickClick to continue.
Select source system type

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. ClickClick to continue.
create R/3 Source system

Step 4. ClickClick 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.
Information

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.
Sap R/3

Step 6. Clickcontinue.

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.
New source system connection

Result:
You have created a new source system TC1_200 in BW.
Administrator work bench modelling

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,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.
RFC destination

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):

  • 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.

IDOC STRUCTURE
IDOC STRUCTURE


All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

SAP BW Topics