Creating an ODP ECC Source System

Operational Data Provisioning (ODP) provides a technical infrastructure to support data extraction and replication. For example, used to connect an SAP ECC system as the source system to a BW system. Communication is performed using remote function calls (RFC).

This article simply covers the creation of an ODP ECC source system within the SAP Business Warehouse (BW) system. I’ll produce follow-on articles that will cover the advantages and benefits of the ODP extractors from a data extraction and replication perspective.

The following are the steps to create an ODP ECC source system in a SAP Business warehouse system. Please note these steps need to be executed in all SAP BW systems across your landscape from Development to Production.

Open the BW Client.

Execute transaction SCC4 (Client Administration) and enter the following settings.

• Changes and transports for client specific objects = Changes without automatic recording.

• Cross-Client Object Changes = Changes to repository and cross client customizing allowed

Set system to modifiable

Execute transaction SE06 (Set Up Transport Organizer) and enter the following settings

• Global settings = Modifiable

• All Software components = Modifiable

• All Name Spaces = Modifiable

Create a new Logical Systems

Execute transaction BD54 (Maintaining Logical Systems) and enter a new logical system. The naming convention should be in aligned with the existing ECC system name. For example, if the existing ECC system is REDCLNT100 then the new source system name could be REDODPC100. For this step you need to create a new entry and enter the following in BD54.

• Log. System = REDODPC100

• Name = REDODPC100

Create RFC connections

Execute transaction SM59 (RFC Destinations (Display/Maintain)) to create a new standard RFC connection and a new dialog RFC connection. Under the ABAP Connections folder, create a new standard RFC connection with the following (using example name above):

        Header

• RFC Destination = REDODPC100

• Connection Type = 3 (ABAP Connection)

• Description = ODPC Connection to RED 600

  Technical Settings Tab

• Load Balancing = Yes

• Target System = RED

• Msg Server = Message server of RED (can get this from SM59 connection details for REDCLNT100).

• Group = server group (can get this from SM59 connection details for REDCLNT100).

• Save to Database as = Select Host and enter message server details above.

  Logon & Security

• Client = 100

• User = BIODPECC_RFC (can use existing RFC user from existing ECC connection or create a new one (clone of existing one) – for our scenario we created a new one to avoid issues with existing RFC user).

• Pwd = Password for above RFC user

  Under the ABAP Connections folder, create a new dialog RFC connection with the following (using example name above):

  Header

• RFC Destination = REDODPC100 _DIALOG

• Connection Type = 3 (ABAP Connection)

• Description = ODPC DIALOG Connection to RED 600

  Technical Settings Tab

• Load Balancing = Yes

• Target System = RED

• Msg Server = Message server of RED (can get this from SM59 connection details for REDCLNT100).

• Group = server group (can get this from SM59 connection details for REDCLNT100).

• Save to Database as = Select Host and enter message server details above.

  Logon & Security

• Client = 100

• User = BIODPECC_RFC (can use existing RFC user off existing ECC connection or create a new one (clone of existing one) – for our scenario we created a new one to avoid issues with existing RFC user).

• Pwd = Password for above RFC user

Create a new source system

Execute transaction RSA1 (Administrators workbench) to create a new source system. Select source system and ODP – SAP (Extractors) folder. On this folder right hand click and select create and enter the following parameters:

• Logical System Name = REDODPC100

• Source System Name = REDODPC100

  In the following window select the following:

• OPD Context = SAPI Data sources/extractors

• BW Background User: ALEREMOTE

• Password : ALEREMOTE Password.

  On the next screen, the system asks – “Do you want the generated content versions to be updated now or later”. Please choose now.

Conversion of logical system names

Execute transaction RSA1 (Administrators workbench) and select tools from the menu and the Select Conversion of logical system names option. Create a new entry with the following values:

• Original Source System = REDODPC100

• Target Source System = ODP source system for test system or production (depending on what system you’re currently executing these steps in).

Assignment of Source system to Source system ID

Execute transaction RSA1 (Administrators workbench) and select tools from the menu and the Assignment of Source system to Source system ID option. Create a new entry with the following values:

• Source system = REDODPC100

• Source system ID Text = ECC Client 100

• Source system ID = RB

Close the BW Client.

Execute transaction SCC4 (Client Administration) and enter the following settings.

• Changes and transports for client specific objects = No Changes allowed

• Cross-Client Object Changes = No Changes to Repository and Cross-Client Customizing allowed

Set system to not modifiable

Execute transaction SE06 (Set Up Transport Organizer) and enter the following settings

• Global settings = Not Modifiable

• All Software components = Not Modifiable

• All Name Spaces = Not Modifiable

You have just set up a new ODP ECC Source System connection within your BW system!!