b02_bb_configguide_en_de

SAP SCM 5.0

October 2006

English

Building Block B02 Connectivity

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Building Block Configuration Guide

SAP Best Practices Building Block B02 Connectivity: Configuration Guide

Copyright

© Copyright 2006 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AG of 62


Icons

Icon Meaning

Caution

Example

Note or Tip

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© SAP AG of 62


Contents

Connectivity: Configuration Guide............................................................................................6

1 Preparation........................................................................................................................ 6

2 Local Settings.................................................................................................................... 7

2.1 SAP ECC.................................................................................................................7

2.1.1 Defining Client Administration (SAP ECC)..........................................................7

2.1.2 Defining Logical System (SAP ECC)...................................................................8

2.1.3 Assigning Logical System to Client (SAP ECC)..................................................9

2.1.4 Creating an RFC User (SAP ECC)......................................................................9

2.2 SAP SCM..............................................................................................................11

2.2.1 Define Client Administration (SAP SCM)...........................................................11

2.2.2 Defining a Logical System for SAP SCM (SAP SCM).......................................12

2.2.3 Assigning Logical System to Client (SAP SCM)................................................13

2.2.4 Creating an RFC User (SAP SCM)....................................................................13

2.2.5 Creating Business System Group (SAP SCM)..................................................14

2.2.6 Assigning Logical System to Business System Group (SAP SCM)...................15

2.3 SAP XI................................................................................................................... 17

2.3.1 Installing Java Web Start for SAP XI.................................................................18

2.3.2 Configuring SAP Technical System in SLD (SAP XI)........................................18

2.3.3 Configuring SAP Business System in SLD (SAP XI).........................................20

2.4 SAP BW................................................................................................................. 22

2.4.1 Defining Client Administration...........................................................................22

2.4.2 Defining a Logical System for SAP BW (SAP BW)............................................23

2.4.3 Assigning Logical System to Client (SAP BW)..................................................24

2.4.4 Creating an RFC User (SAP BW)......................................................................24

2.4.5 Define RFCUSER as default (SAP BW)............................................................25

3 Cross-Connectivity...........................................................................................................26

3.1 SAP ECC with SAP SCM......................................................................................26

3.1.1 SAP ECC...........................................................................................................26

3.1.2 SAP SCM..........................................................................................................30

3.2 SAP XI with SAP ICH............................................................................................33

3.2.1 SAP XI...............................................................................................................33

3.2.2 SAP ICH............................................................................................................40

3.3 SAP XI with SAP ECC...........................................................................................49

3.3.1 SAP XI...............................................................................................................49

3.3.2 SAP ECC...........................................................................................................57

3.4 Connecting SAP BW with SAP ECC, SAP CRM, SAP SRM.................................59

3.5 SAP SCM with SAP BW........................................................................................60

© SAP AG of 62


3.5.1 Connecting SAP SCM to the SAP BW system (SAP BW).................................60

3.5.2 Connecting SAP BW to the SAP SCM system (SAP SCM)...............................61

3.6 Connecting SAP BW to a File System (SAP BW)..................................................62

© SAP AG of 62


Connectivity: Configuration Guide

1 PreparationThis configuration guide provides the information you need to set up the configuration of this building block.

To work with this configuration guide, we recommend that you log on to the system in English

Before you start installing this building block, refer to the Scenario Installation Guide of the SAP Best Practices scenario that you want to install.

© SAP AG of 62


2 Local Settings

2.1 SAP ECC

2.1.1 Defining Client Administration (SAP ECC)

UseThis activity allows you to change Customizing settings and to start eCATT procedures.

PrerequisitesYou have logged on to the system in English to start with the installation. The logon language must be English (EN) to ensure that you find all menu paths described in the documentation.

Procedure1. To carry out the activity, choose one of the following navigation options:

SAP ECC Menu Tools Administration Administration Client Administration Client Maintenance

Transaction code SCC4

2. Choose Display Change.

3. Confirm the warning message Caution: The table is cross client.

4. Select your SAP ECC client and choose Details.

5. In the Change View “Clients”: Details screen, activate the following settings:

Automatic recording of changes

Changes to Repository and cross-client Customizing allowed

eCATT and CATT Allowed.

6. Save.

7. Go back to the SAP Easy Access Menu.

© SAP AG of 62


2.1.2 Defining Logical System (SAP ECC)

UseThe purpose of this activity is to create a logical system for your SAP ECC System. To enable communication between systems within your system landscape, you must

1. Define the systems as logical systems.

2. Assign the logical system for the SAP ECC System to a client.

This enables the systems to recognize the target system as an RFC destination. If the logical system has already been created, skip this activity.

Logical systems are defined cross-client

Procedure1. Access the activity using one of the following navigation options:

SAP ECC IMG menu

SAP Customizing Implementation Guide Integration with Other mySAP.com Components Advanced Planning and Optimization Basic Settings for Setting Up the System Landscape Name Logical System

Transaction code SPRO

2. Confirm the information message “Caution: The table is cross-client”.

3. Choose New Entries.

4. In the column Log.System, enter a name for the logical system you want to create.

We recommend that you use the following naming convention:

<system ID>CLNT<client number> (for example: DS7CLNT712)

<system ID> is the ID number of your ECC system.

<client number> is the number of the relevant client in your ECC system.

5. In the Name column, enter a description of the logical system.

Log. System Name

<Logical system 2>, (for example DS7CLNT723) SAP R/3 System

6. Save your entries.

A transport request for Workbench appears.

7. Select an existing request or create a new request, if necessary.

A transport request for Customizing appears.


© SAP AG of 62


2.1.3 Assigning Logical System to Client (SAP ECC)

UseThe purpose of this activity is to make an assignment for the logical system. Skip this activity if a logical system is already assigned to your client.


SAP ECC Menu Tools Administration Administration Client Administration Client Maintenance



3. Confirm the warning message Caution: The table is cross client.

4. Select your ECC client and choose Details.

5. In field Logical System, select the newly created logical system of your SAP ECC client using the input help.

6. Save and confirm the warning message Be careful when changing the logical system.

7. Choose Back twice.

2.1.4 Creating an RFC User (SAP ECC)

UseTo enable communication between the SAP ECC back-end system and other SAP systems, you have to create an RFC user in the SAP ECC System.

The RFC user in the application client enables multiple RFC connections. Skip this activity if an RFC User has already been created.


SAP ECC Menu Tools Administration User Maintenance Users

Transaction code SU01

2. In the User field, enter RFCUSER.

3. Choose Create.

4. In the Maintain User screen, enter the following data on the following tab pages:

Address Tab

Last Name RFC User

Function

Logon Data Tab

User type System

Initial Password BPLOGIN

© SAP AG of 62


Repeat Password BPLOGIN

Defaults Tab

Logon Language EN

Profiles Tab

Profile SAP_ALL

SAP_NEW

S_BI-WX_RFCA


The user RFCUSER has the profiles SAP_ALL and SAP_NEW assigned, which gives him full authorization rights. If this authorization is not applicable to your project you can restrict the rights of this user according to SAP Note 0338537.

© SAP AG of 62


2.2 SAP SCMThis step describes the local settings required for the SAP SCM system – the full version, which consists of the following components:

SAP APO

SAP EM

SAP ICH.

Perform this step only once if you want to use only SAP APO or if you want to use the SAP ICH as part of a full version of the SAP SCM System.

Note that SAP ICH has not been tested as a standalone component (without SAP APO) by SAP Best Practices.

2.2.1 Define Client Administration (SAP SCM)

UseThis activity enables you to change Customizing settings and start eCATT procedures.

PrerequisitesYou have logged on to the system in English to start with the installation. The logon language must be English (EN) to ensure that you find all menu paths described in the documentation.

Procedure1. Access the activity choosing one of the following navigation options:

SAP SCM menu SAP menu Tools Administration Administration Client Administration Client Maintenance


2. In the view Display View "Clients": Overview, choose Display Change and confirm the message The table is cross-client.

3. Select your SCM client.

4. Choose Details.

5. In the view Change View "Clients": Details, set the flags for


Changes to Repository and cross-client Customizing allowed

eCATT and CATT allowed

6. Save and choose Back twice.

© SAP AG of 62


2.2.2 Defining a Logical System for SAP SCM (SAP SCM)

UseThe purpose of this activity is to create a logical system for your SAP SCM system. To enable communication between systems within your system landscape, you must

1. Define the systems as logical systems.

2. Assign the logical system for the SAP SCM system to a client.

This enables the systems to recognize the target system as an RFC destination. If the logical system has already been created, skip this activity.


Procedure1. To define the logical system for your SAP SCM system, choose one of the following

navigation options:

SAP SCM IMG menu

mySAP SCM-Implementation Guide Integration with SAP Components Integration via APO Core Interface (CIF) Basic Settings for Creating the System Landscape Name Logical Systems


1. Choose New entries.

2. In the column Log System, enter a name for the logical system that you want to create.

3. In the column Name, enter a description of the logical system.

Log. System Name

<Logical system 2>, for example AS7CLNT001 SAP SCM system

To designate logical systems, apply the naming convention

<XXX>CLNT<NNN>

where XXX is the system name

and NNN is the client.






© SAP AG of 62


2.2.3 Assigning Logical System to Client (SAP SCM)

UseThe purpose of this activity is to make a client assignment for the logical system. Skip this activity if a logical system is already assigned to your client.

Procedure1. Access the activity choosing one of the following navigation options:

SAP SCM menu SAP menu Tools Administration Administration Client Administration Client Maintenance



3. Confirm the warning message The table is cross client.

4. Select your SCM client and choose Details.

5. Enter the name of the logical system of your SAP SCM client.

6. Save and confirm the warning message Be careful when changing the logical system.

7. Choose Back twice.

2.2.4 Creating an RFC User (SAP SCM)

UseTo enable communication between the SAP ECC backend system and the SAP SCM system, you have to create an RFC user in the SAP SCM system. The RFC user in the application client enables multiple RFC connections. Skip this activity if an RFC User has already been created.

Procedure1. To carry out this activity, choose one of the following navigation options:

SAP SCM IMG menu

SAP Menu Tools Administration User Maintenance Users


1. In the User field, enter RFCUSER.

2. Choose Create.

3. In the Maintain User screen, enter the following data on the tab pages:

Address

Last Name RFCUSER

Function

© SAP AG of 62


Logon data

User type System

Password BPLOGIN

Defaults

Logon Language EN

Profile

Profiles SAP_ALL

SAP_NEW

S_BI-WHM_RFC

S_BI-WX_RFC

1. Save your entries and go back

2. In the User field, enter XIAPPLUSER1.

3. Choose Create.

4. In the Maintain User screen, enter the following data on the tab pages:

Address

Last Name XIAPPLUSER1

Function

Logon data

User type System

Password XIPASS

Profile

Profiles Leave blank

Defaults

Logon Language EN


2.2.5 Creating Business System Group (SAP SCM)

UseIn this activity, you define a business system group. The purpose of business system groups is to maintain the data volumes and the processing of different business areas separate

© SAP AG of 62


across different systems or different system clients. A business system group represents a unit within a company or organization that can be defined according to legal, economic, administrative or geographic factors. After defining the business system group, you assign the logical system of your SAP SCM and SAP ECC System to the business system group.

If you plan to connect more than one ECC system to the SCM system, we strongly recommend that you create a separate business system group (BSG) with a unique name for each ECC system (or each ECC client). This way, you can keep the data processing separate and avoid data inconsistencies between the systems. Decide now how many BSGs you will need. It is important that you decide upon the total number of BSG before data replication takes place.

Procedure1. To maintain the business system group, use one of the following navigation options:

SAP SCM IMG Path mySAP SCM – Implementation Guide Integration with SAP Components Integration via APO Core Interface (CIF) Basic Settings for Creating the System Landscape Maintain Business System Group


2. Choose New entries and enter the following data:

Field name User action and default values

BusSystGrp <Name of Business System Group >

Description Enter a text description of the Business System Group


2.2.6 Assigning Logical System to Business System Group (SAP SCM)

UseIn this activity, you assign the logical system of your SAP SCM to the business system group. In a multi-system scenario, the logical systems of all the systems involved must be assigned to a business system group to support synchronization of master data.

The SCM system must be assigned to one Business System Group only. If the SCM system is already assigned to a Business System Group, you can skip this part.


SAP SCM IMG Path mySAP SCM – Implementation Guide Integration with SAP Components Integration via APO Core Interface (CIF) Basic Settings for Creating the System Landscape Assign Logical System and Queue Type


© SAP AG of 62


2. To assign a logical system to your business system group, choose New entries and enter the following data:


BusSystGrp <Name of Business System Group >, for example, SCM

Logical System <SCM System>CLNT<Client>, for example, AS7CLNT001

R/3 Flag (If this indicator is set, the source system is an R/3 System, if it is not set, it is a legacy system)

Do not select

SAP Release Release of corresponding system, for example 50 (SCM)

Queue Type Outbound Queue

Error Handling in Target System Strict (Terminate at Errors)

Role Not Specified


© SAP AG of 62


2.3 SAP XIThe following settings are carried out on the prerequisite that the installation of the SAP XI system has been completed and the post-installation activities of the SAP XI installation guide have been performed, which means that the SAP XI system has been registered in the System Landscape Directory (SLD) as the Integration Server.

The System Landscape Directory (SLD) provides a central repository which stores the information about all the installable and installed elements of your system landscape. It is composed of the component repository and the landscape directory. The component repository includes a description of all SAP components whereas the landscape directory includes a complete description of the actually installed SAP system landscape.

UseIn the Supplier Managed Inventory scenario, there are three systems involved in the inventory collaboration:

SAP ICH (as part of the SAP SCM system)

SAP XI

SAP ECC

During the installation of the SAP XI, this integration server should already be created in the SLD. This chapter describes the required activities in order to register the SAP ICH and SAP ECC respectively in the SLD.

When you enter values in the fields of the SLD, make sure you comply with the uppercase and lowercase spelling as described in this guide.

PrerequisitesSAP Best Practices for SCM do not deliver any additional roles for configuring the XI system because you can use the standard roles delivered by SAP. In order to perform following steps, you need to assign the following composite roles to your user (in the roles tab of user maintenance)

SAP_XI_Administrator

SAP_XI_Configurator

SAP_XI_Display_User

© SAP AG of 62


2.3.1 Installing Java Web Start for SAP XI

UseBefore you can configure SAP Exchange Infrastructure (XI) to work with SAP Inventory Collaboration Hub (ICH) Java Web Start must be installed in your workstation. If you have installed Java Web Start, you can skip this step.

Procedure 1. Log on to the SAP XI system to check whether Java Web Start has been installed.

2. Choose one of the following navigation options:

SAP XI menu User menu for <you name> Exchange Infrastructure Integration Builder

Transaction code SXMB_IFR

This transaction launches the web browser for the XI. If you do not have Java Web Start in your workstation, there will be a message stating You need to install Java Web Start version x.x.x.

3. Click on the link supplied and download the J2SE component, and execute.

Download and install the J2SE component, but not the J2EE component.

4. If the system prompts you for proxies during installation, select No proxies.

After the installation of J2SE, the Java Web Start application will be available on your local PC.

5. Launch it and choose Files Preferences General.

6. Select No proxies.

7. Ignore the Sun Java security warning stating It is highly recommended not to install and run this code.

8. Choose Start.

2.3.2 Configuring SAP Technical System in SLD (SAP XI)

UseIn this activity, you create the SAP technical system in the System Landscape Directory (SLD). You need to provide information such as the server name, the client and instance number, which primarily describe the technical aspect of the system.

You need to perform these steps twice: Once for your SAP ICH system and once for your SAP ECC system.

Procedure 1. To carry out the activity, choose one of the following navigation options:

SAP XI menu User menu for <you name> Exchange Infrastructure Environment Start SLD GUI in browser

Transaction code SLDHTMLGUI

© SAP AG of 62


2. In the logon pop-up enter again your user name and password and choose OK.

3. The SAP System Landscape Directory page will be opened in your default browser.

4. Choose the link Technical Systems.

5. On the SLD Technical System Browser page, choose New Technical System….

6. On the SLD Technical System Wizard – Technical System Type page, select Technical System Type – Web AS ABAP and choose Next.

7. On the SLD Technical System Wizard – System Details page, make the following entries:

Field name Description R/O/C User action and values

Note

Web as ABAP Name (SID)

SAP system name

R Specify the SAP system name, for example, AS7

–

Installation Number

Installation number of your SAP system

R Specify the SAP system installation number, for example, 0120007965

–

Database Host Name

The name of database server

R Specify the name of the server, for example, PWDF0155

–

To check the installation number and host name of your system, choose System Status… from the menu bar of your SAP system.

8. Choose Next.

9. On the SLD Technical System Wizard – Message Server and Central Application Server page, make the following entries:


Note

Host Name Name of the message server


–

Message Server Port

The TCP port number that this message server uses to listen for load-balanced SAP login request

R Specify the message server port, for example, 3600

Usually 3600+Instance Number

Logon Groups

Name of Logon Groups

R Specify the name of Logon Group, for example, PUBLIC

–

Host Name Name of the central application server


–

Instance Number

Instance number R Specify the instance number, for example, 21

–

Ask your system administrator for the relevant information.

© SAP AG of 62


10. Choose Next,

11. The SLD Technical System Wizard – Additional Application Server (optional) page appears.

If you have several application servers, enter them on this page.

12. Choose Next

13. On the SLD Technical System Wizard – Client page, make the following entries:

Field name Description R/O/C User action and values Note

Client Number

Client number R Specify the name of the client, for example, 001

–

Logical System Name

The logical name assigned to this client

R Specify the logical system, for example, AS7CLNT001

–

14. Choose Next

15. On the SLD Technical System Wizard – Software Product And Components page, choose the following value:


Note

Available Products

Available products R Choose the SAP system from the list box, for example, SAP SCM 4.1

–

16. Choose Add, the page is refreshed and the installed components are displayed.

17. Keep the default value and choose Finish to leave the SLD Technical System Browser page.

18. Repeat steps 4 to step 21 to register your SAP ECC system.

Result The SAP technical system is registered in the System Landscape Directory.

2.3.3 Configuring SAP Business System in SLD (SAP XI)

UseBusiness systems are logical systems that serve as senders or receivers within the SAP Exchange Infrastructure. A business system is associated with the technical SAP system.In this activity, you create a new SAP business system and assign it to the SAP technical system you created in the previous step.

PrerequisitesThe SAP technical system has been created.

© SAP AG of 62



SAP XI menu User menu for <you name> Exchange Infrastructure Environment Start SLD GUI in browser

Transaction code SLDHTMLGUI

2. In the logon dialog box, enter again your user name and password and choose OK.

The SAP System Landscape Directory page will be opened in your default browser.

3. Choose the link Business Systems.

4. On the SLD Business Landscape page, choose New Business System

5. On the SLD Business System Wizard – Technical System Type page, select Web AS ABAP and choose Next

6. On the SLD Business System Wizard – Select System page, make the following entry:


System The SAP system you created

R Choose the SAP system from the list box, for example, AS7 on PWDF0155

–

7. The page is refreshed and all existing clients of this system are listed in the Client box. Choose the client you will use, for example, 001 of AS7 and choose Next.

8. On the SLD Business System Wizard – Name page, make the following entry:


Name The name of the SAP Business System

R Specify the name, for example, AS7CLNT001

--

9. Choose Next

10. On the SLD Business System Wizard – Installed Products page, make sure that the product is selected and then choose Next.

11. On the SLD Business System Wizard – Integration page, make the following entries:


Business System Role

System role R Choose the role Application System

–

Related Integration Server

The integration server

R Choose the server, for example, XIB

–

12. Choose Finish to quit to the SLD XI Landscape page.

13. Repeat steps 4 to step 12 to register your SAP ECC system.

ResultThe SAP Business System is created and assigned to a SAP Technical System that is already registered in the SLD.

© SAP AG of 62


2.4 SAP BW

If you are using the SAP BW component as part of an SCM system for an SAP Best Practices for SCM business scenario, you can omit this section, because the configuration steps under Local Settings SAP SCM are the same as for SAP BW and have been completed at this stage.

However, if you are using SAP BW as a standalone system, you have to do the following activities.

2.4.1 Defining Client Administration

UseThis activity defines changes and transports of the client-dependent and client-independent objects. It also allows CATT processes to be started.

Procedure1. To perform this activity, choose one of the following navigation options:


1. Switch to Change mode.

2. Select your client.

3. Choose details.

4. In field Currency, enter EUR.

5. In field Client Role, enter Customizing.

6. Check the settings for changes and transport of client-specific objects and client-independent object changes.

If you want to use the settings made by BC-Sets or manually in other systems, “Automatic recording of changes” and “Changes to Repository object and cross-client Customizing allowed” is required.

7. In the Restrictions, when starting CATT and eCATT area, enter X eCATT and CATT allowed.

This entry must be made. Otherwise, activities using CATT procedures cannot be used for the installation.

ResultClient administration has been defined to support the installation using SAP Best Practices.

© SAP AG of 62


2.4.2 Defining a Logical System for SAP BW (SAP BW)

UseIn this step, you define the logical systems in your distributed system.

PrerequisitesLogical systems are defined cross-client. Therefore, cross-client customizing must be allowed in your client (this can be checked in transaction SCC4).


SAP BW IMG menu SAP Reference IMG BW Customizing Implementation Guide Business Information Warehouse Links to other Systems General Connection Settings Define Logical System


2. A dialog box informs you that the table is cross-client. Choose Continue.

3. On the Change View “Logical Systems”: Overview screen, choose New entries.

4. On the New Entries: Overview of Added Entries screen enter the following data:


Log. System

Technical Name of the Logical System

Enter a name for the logical BW system you want to create

–

Name Textual Description of the Logical System

Enter a clear description for the logical BW system

–

5. Choose Save.

If a transport request for workbench and customizing is displayed choose existing requests or create new requests.

ResultYou have created a logical system name for your SAP BW client.

© SAP AG of 62


2.4.3 Assigning Logical System to Client (SAP BW)



2. In the view Display View "Clients": Overview, choose Change Display.

3. Confirm the message.

4. Select your BW client.

5. Choose Details.

6. In the view Change View "Clients": Details, insert your BW system in the Logical system field, for example, BS7CLNT100.

7. Set the flags for


Allow CATT processes to be started

The logon language to run the CATT procedures must be English (EN). The install user has to logon in English.

8. Save the entries and go back.

2.4.4 Creating an RFC User (SAP BW)

Procedure1. To carry out the activity, choose one of the following navigation options

SAP BW menu Tools Administration User Maintenance Users


2. On the User Maintenance: Initial Screen, enter the following data:

Field Entry

User RFCUSER

3. Choose Create.

4. On the Maintain User screen, choose Address and enter the following data:

Field Entry

Last Name RFCUSER

Function Default-User for RFC connection

5. Choose Logon data and enter the following data:

Field Entry

Password LOGIN

User type System

6. Choose Profiles and enter the following data:

© SAP AG of 62


Field Entry

Profiles SAP_ALL , SAP_NEW and S_BI-WHM_RFC

7. Choose Save.

Do not change the password of this user, as it is used in RFC connections.

2.4.5 Define RFCUSER as default (SAP BW)

ProcedureTo carry out the activity, choose one of the following navigation options

Transaction code RSA1

1. On the Administrator Workbench: Modeling screen choose Settings Global Settings.

2. On the Global Settings/Customizing dialog box choose Glob. Settings.

3. On the “RSADMINA Maintenance View” screen, choose Display Change.

4. Enter RFCUSER in the BW User ALE field.

© SAP AG of 62


3 Cross-ConnectivityThis chapter describes all settings that are necessary to connect the components of the mySAP ERP landscape with each other that are relevant for an SCM solution. The settings for each combination of two components to be connected are described in a separate structure node. The separate structure nodes make it possible to identify the activities required to connect certain components with each other.

3.1 SAP ECC with SAP SCM

3.1.1 SAP ECC

3.1.1.1 Creating a Logical System for SAP SCM (SAP ECC)

UseTo enable communication between your SAP SCM and your SAP ECC systems, you need to define logical systems for both systems in your ECC System.

Procedure1. To define the two required logical systems for your system, open the transaction using:

SAP ECC IMG

menu

SAP Customizing Implementation Guide Integration with Other mySAP.com Components Advanced Planning and Optimization Basic Settings for Setting Up the System Landscape Name Logical System


2. Confirm the information message that appears.




Log. System Name

<Logical system 1>, for example AS7CLNT001 SAP SCM system

To designate logical systems, apply the naming convention

<XXX>CLNT<NNN>

where XXX is the system name

and NNN is the client.


7. A transport request for Workbench appears.Select an existing request or create new request, if necessary.

© SAP AG of 62


8. A transport request for Customizing appears. Select an existing request or create a new request, if necessary.

9. Go back twice.

3.1.1.2 Connecting SAP SCM (SAP ECC)

UseCommunication between the systems is based on the RFC interface, where Remote Function Calls (RFCs) manage the communication process, parameter transfer and error handling between different systems. To set up these functions in your systems, you need to define RFC destinations in your system landscape.

Procedure1. To define an RFC destination in the SAP ECC System, open the transaction:

SAP ECC IMG menu SAP Customizing Implementation Guide Integration with Other mySAP.com Components Advanced Planning and Optimization Basic Settings for Setting Up the System Landscape Set Up RFC Destination

Transaction code SM59

2. In the Configuration of RFC Connections screen, choose Create.

3. Make the following entries:


RFC destination <SAP SCM system name>CLNT<client>

for example AS7CLNT001

Connection type 3 (Connection to ABAP system)

Description

Description SAP SCM system

4. Choose Enter.

5. Move to the Technical Settings tab and make the following entries:

Technical settings

Balance Load No

Target host <SAP SCM target host name>, for example pwdf0421

System number <SAP SCM target system number>, for example 74

Save as Host name (select)

One option of finding the host name is to go through the SAP Logon, select Groups and enter the name of your system. The target host will appear in the field Message Server. After having selected the system, click on “Add and Logon”. In the next screen the system number appears.

6. Move to the Logon/Security tab and make the following entries:

© SAP AG of 62



Trusted system No (default)

SNC Inactive (default)

Logon

Language EN

Client <SAP SCM target client>, for example 001

User RFCUSER

Password BPLOGIN (password you have chosen in user

maintenance)

Current user Deselect (default)

7. Choose the tab MDMP & Unicode and select the Unicode flag under Comunication Type with Target System.

This step is only required when you are using a UNICODE system.

8. Save your RFC destination

9. Choose Test connection to verify that the connection to the SCM system has been established.

10. Go back.

3.1.1.3 Maintaining Systems and their Types and Releases (SAP ECC)

UseThe purpose of this activity is to specify details of your SAP SCM system for the SAP SCM Core Interface.


SAP ECC menu SAP Easy Access Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Settings APO Releases

Transaction code NDV2

2. Confirm the information message “Caution: The table is cross-client”.

3. Choose New Entries and enter the following data:

© SAP AG of 62



Log. System <SCM System>CLNT<Client>, for example “AS7CLNT001”

Syst. Type SAP_APO

Release Release of your SAP SCM system, for example “50”


3.1.1.4 Maintaining the Target System (SAP ECC)

UseThe purpose of this activity is to enter your SAP SCM system as the target system of your SAP ECC System for the SAP SCM Core Interface.


SAP ECC menu Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Environment Current Settings Set Target System and Queue Type

Transaction code CFC1

2. In the Change View “Target System, Operation Mode and Queue Type...” screen, choose New Entries and enter the logical system name for your SAP SCM system (for example AS7CLNT001) and choose the queue type Outbound Queues.

3. Save your entry.

4. A transport request for Customizing appears.Select an existing request or create a new request, if necessary.

5. Go back.

© SAP AG of 62


3.1.2 SAP SCM

3.1.2.1 Defining a Logical System for SAP ECC (SAP SCM)

UseThe purpose of this activity is to create a logical system for your SAP ECC System in SAP SCM. This enables the systems to recognize the target system as an RFC destination. If the logical system has already been created, skip this activity.


PrerequisitesTo enable communication between systems within your system landscape, you must have

Defined a logical system in SAP SCM and SAP ECC.

Assigned the logical system to the corresponding client in SAP SCM and SAP ECC.

Procedure1. To define the logical system for your SAP ECC System, open the transaction using:

SAP SCM IMG menu

mySAP SCM - Implementation Guide Integration with SAP Components Integration via SAP Core Interface (CIF) Basic Settings for Creating the System Landscape Name Logical Systems





Log. System Name

<Logical system 2>, for example KD6CLNT416 SAP ECC System

The name of the logical system in SAP ECC can be displayed using transaction SCC4 in the SAP ECC system.



5. Select an existing request or create new request, if necessary.



© SAP AG of 62


3.1.2.2 Maintaining the RFC Connection to ECC (SAP SCM)

UseCommunication between the systems is based on the RFC interface.

The RFC connection enables data to be exchanged between systems.

Procedure1. To define RFC connections, open the following transaction:

SAP SCM IMG menu

mySAP SCM – Implementation Guide Integration with SAP Components Integration via SAP Core Interface (CIF) Basic Settings for Creating the System Landscape Set Up RFC Destination


2. On the Display and maintain RFC destinations screen, choose Create.



RFC destination <SAP ECC System name>CLNT<client>

for example KD6CLNT416

Connection type 3 (Connection to SAP ECC System)

Description

Description SAP ECC System

4. Choose Enter.

5. On the Technical Settings tab page make the following entries:

Technical settings

Balance Load No

Target host <SAP ECC target host name>, for example pwdf0421

System number <SAP ECC target system number>, for example 74

Save as Host name (select)

One option of finding the host name is to go through the SAP Logon screen, select Groups and enter the name of your system. The target host will appear in the field Message Server. After having selected the system, click on “Add and Logon”. In the next screen the system number appears

6. Move to the Logon/Security tab and make the following entries:


Trusted system No (default)

SNC Inactive (default)

© SAP AG of 62


Logon

Language EN

Client <SAP ECC target client>, for example 446

User RFCUSER

Password BPLOGIN (password you have chosen in user

maintenance)

Current user Deselect (default)




9. Choose Test Connection to verify that the connection to the ECC system has been established.

10. Go back.

3.1.2.3 Assigning Logical System to Business System Group (SAP SCM)

UseIn this activity, you assign the logical system of your SAP ECC to the business system group. In a multi-system scenario, the logical systems of all the systems involved must be assigned to a business system group to support synchronization of master data.

Procedure1. To assign a logical system to your business system group, open the IMG activity in SAP

SCM as follows:

SAP SCM IMG menu mySAP SCM – Implementation Guide Integration with SAP Components Integration via SAP Core Interface Basic Settings for Creating the System Landscape Assign Logical System and Queue Type


2. Choose New entries and enter the following data:


BusSystGrp <Name of Business System Group >, for example, SCM

Logical System <Logical System of your SAP ECC System>, for example, DS7CLNT723

© SAP AG of 62



SAP System Indicator x

SAP Release Release of corresponding system, for example 600

Queue Type Outbound Queue

Error Handling in Target System

Strict (Terminate at Errors)

Role Not Specified


3.2 SAP XI with SAP ICHThis section describes the settings required for connecting the SAP XI system to the SAP ICH component (of the SAP SCM system)

Note that SAP ICH has not been tested as a standalone component (but only as part of an SAP SCM system) by SAP Best Practices.

3.2.1 SAP XI

3.2.1.1 Maintaining the J2EE Parameters (SAP XI)

PrerequisitesThe configuration user must have the authorization to login the integration server. In order to maintain J2EE parameters, the following composite roles must have already been assigned to the configuration user:

SAP_J2EE_ADMIN

SAP_XI_ADMINISTRATOR

SAP_XI_CONFIGURATOR

UseThe business systems use two registered programs to retrieve the information of the SLD. In this activity, you register these programs in the J2EE engine of your Integration Server, so that the connection with the business system can be established.

Note that this activity is carried out on your operation system (OS) level. To access the system on the OS level, usually a special authorization is required. In the following procedure we assume that the OS is a Windows system.

© SAP AG of 62


Procedure1. From the window system, choose Start Program Accessories Communications

Remote Desktop Connection

2. In the Remote Desktop Connection screen, enter the following data:

Field name Description User action and value

Computer Host name or IP address of XI system Enter the Host name or IP

address. for example, pwdf2268

3. Choose Connect, on the Log on to Window screen, enter the following data:

Field name

Description R/O/C User action and values Note

User User ID R Enter the user name. for example, I029514

The user ID will be used to access the integration server and run the J2EE applications at the server

Password Password R Ask your administrator and specify it here

4. Choose OK and log o to the Integration Server

5. Start the J2EE Engine Visual Administrator either locally by choosing J2EE Engine Administrator Shortcut or on your Integration Server by executing the file go.bat from within the directory: .../usr/sap/<systemid>/DVEBMGS<instance_number>/j2ee/admin.

6. Choose Connect, on the Login screen, enter the following data:

Field name

Description R/O/C User action and values Note

User User ID R The user name. for example, J2EE_ADMIN is defaulted from the login profile

The user ID will be used to access setting at OS level in XI system


7. Choose Cluster Server Services JCo RFC Provider, under the RFC destination specify the following data:


Program ID Program name

R Enter the program name LCRSAPRFC_AS7

The program name follows the syntax as LCRSAPRFC_<System ID>

Gateway Host

Gateway host

R Enter the gateway host, for example, pwdf2268

This is your Integration Server host

Gateway Service

Gateway service

R Enter the service, for example, sapgw64

This is the gateway service from your Integration Server

Number of process

Number of process

R Specify the number of the process, for example, 3

© SAP AG of 62


To find out the gateway host and service on your integration server host, call transaction SMGW, choose: Goto Parameters Display, and search for the entries for gateway hostname and gateway service attributes.

8. Under the Repository specify the following data:


Application Server

Application server

R Enter the server name, for example, pwdf2268


System number

System number

R Enter the system number, for example, 64

This is the system number of your Integration Server

Client Client number

R Enter the client, for example, 100

User User R Enter the user name SAPJSF


Only Unicode system is supported as of XI 7.0. To verify whether your business system is a Unicode or Non-unicode system, you can follow the menu path in your business system: System Status…to check the field Unicode System.

9. Choose Set.

10. Under the RFC destination specify the following data for the program SAPSLDAPI:



R Enter the program name SAPSLDAPI_AS7

The program name follows the syntax as SAPSLDAPI_<System ID>

Gateway Host

Gateway host

R Enter the gateway host, for example, pwdf0764


Gateway Service

Gateway service

R Enter the service, for example, sapgw64

This is the gateway service from your Integration Server

Number of process

Number of process

R Specify the number of the process, for example, 3

11. Under the Repository specify the following data:


Application Server

Application server

R Enter the server name, for example, pwdf0764


© SAP AG of 62



System number

System number

R Enter the system number, for example, 64

This is the system number of your Integration Server

Client Client number

R Enter the client, for example, 100

User User R Enter the user name SAPJSF


To verify whether your business system is a Unicode or Non-Unicode system, you can follow the menu path in your business system: System Status…to check the field Unicode System.

12. Choose Set.

13. Quit the program.

3.2.1.2 Defining HTTP Destination for Business System (SAP XI)

UseIn this activity you create the HTTP destination for the business system (the SAP ICH in our case). This HTTP destination is assigned to the End Point you create later.


SAP XI menu SAP menu Tools Administration Network RFC Destinations


2. On the Display and maintain RFC destinations screen choose Create.

3. On the RFC Destination screen, enter the following data:


Note

RFC Destination

The HTTP destination

R Enter the name, for example, AS7CLNT001

Connection type

Connection type R Choose the type H

© SAP AG of 62



Note

Description Description R Enter the description for the RFC destination, for example, SAP ICH

4. Choose Enter, confirm the pop-up message.

5. On the RFC Destination <your RFC ID> screen, enter the following data:


Target host Target host R Specify the host name, for example, PWDF0155

Service No. Service number

R Specify the service number, for example, 50021

The service no. is the HTTP port number.

PathPrefix Path prefix R Enter the prefix, for example, /sap/xi/engine/engine_as7_001/?type=receiver

If you have created an alias for your business system, you need to add it into the prefix. For the Best Practices configuration, the alias engine_as7_001 is used

To find out the number of the HTTP port (service number), call transaction SMICM and then choose Go to Service in your SAP ICH and look up the port protocol =”HTTP”.

6. Choose the Logon/Security tab, confirm the warning message and enter the following logon data:


Language Logon language

O Enter the language id, for example, EN

Client Client R Enter the client, for example, 001

User User R Enter the user, for example, XIAPPLUSER1

Password Password R Enter the password, for example, XIPASS

7. Choose Save and go back.

3.2.1.3 Defining Services and Communication Channels for SAP ICH (SAP XI)

UseTo prepare the configuration of the business scenario, you must do the following:

© SAP AG of 62


Define the involved business systems as services (business system services) in the Integration Directory. Only then can you address the business systems as senders or receivers of messages.

Define communication channels for outbound message processing for all relevant receiver business systems. You must define a communication channel for all communication types that you want to use and all potential receiver systems.

With this activity, you define a service (business system service) for the business system (the SAP ICH in our case). The communication channels for the involved business system are created automatically as well.


SAP XI menu User menu for <you name> Exchange Infrastructure: Integration Builder Start Integration Builder


2. The SAP Exchange Infrastructure page will be opened in your default browser.

3. Choose the link Integration Directory.

4. The Java Web Start program is started.

5. Enter the following data on the Configuration: Integration Builder (<Your integration server>) screen:


Note

User User ID R Enter the logon user You can use your standard XI user and password

Password Password R Enter the password

Language Language O Choose the logon language, for example, English

The screen can be started in German; the sequence of the fields is arranged as the sequence in the above table.

© SAP AG of 62


6. On the Configuration: Integration Builder (<your system>) page, select Environment -> Clear SLD Cache to update the SLD data.

7. Confirm the system prompt with Enter.

8. In the navigation area, on the Objects tab page, position the cursor on the Service without Party node.

9. In the context menu, choose Assign Business System to call the wizard for assigning business systems.

10. Choose Continue. And on next screen, leave field Party blank, choose Continue again

11. On the next screen, select your SAP ICH business system (for example, AS7CLNT001) by selecting the corresponding checkboxes.

12. Make sure that the Create Communication Channels Automatically checkbox is selected. In this case, the receiver communication channels for the selected business systems are created automatically.

13. Choose Finish.

14. Read the Information Message and choose Close.

15. In the navigation area, under Service Without Party Business System <SID>CLNT<Client> Communication Channel, right click the communication channel GeneratedReceiverChannel_XI.

16. In the context menu, choose Open.

17. Choose Switch between display and edit mode to switch to change mode

18. On the Edit Configuration Parameters screen, in the Parameters tab, check and specify the following data:


Adapter Type Adapter type R XI

Transport Protocol

Transport Protocol

R HTTP 1.0

Message Protocol

Message Protocol

R XI 3.0

Adapter Engine

End point type

R Make sure that the value Integration Server is selected

Addressing Type

Addressing type

R Choose the value HTTP Destination

HTTP Destination

HTTP destination

R Enter your HTTP Destination for the business system, for example, AS7CLNT001

Use the HTTP Destination you defined in the previous step

19. Choose Save to save your data.

20. In the navigation area, select the Change Lists tab page.

21. If more than one change lists appears, expand the change lists and check which one the communication channels are assigned to.

22. Delete the communication channels that are not required one by one.

© SAP AG of 62


For the Business System SAP ICH, the following communication channels are not required:

GeneratedReceiverChannel_HTTP

GeneratedReceiverChannel_IDoc

GeneratedReceiverChannel_RFC.

To delete an object in a change list, you must first open it (double-click), Then choose Communication Channel Delete in the menu bar of the object editor.

23. Right click the change list with the communication channels and choose Activate in the context menu.

24. Go back to the Objects tab.

25. In the navigation area, under Service Without Party Business System <SID>CLNT<Client> Communication Channel, check that the only available communication channel is GeneratedReceiverChannel_XI.

26. Choose menu Object Exit to quit the program.

3.2.2 SAP ICH

3.2.2.1 Assign XI Administrator Role to Configuration User

UseIn order to do carry out the following configuration steps in SAP ICH, you must have assigned the SAP standard role SAP_XI_ADMINISTRATOR to your user or another configuration user.

Procedure1. Access transaction SU01 and enter the name of the user in charge of the subsequent

configuration activities. Choose Change.

2. On the Roles tab page, enter the role SAP_XI_ADMINISTRATOR in the Roles column and choose Save.

3. Log off and log on again.

ResultThe user role is now displayed and can be used for the following configuration activities.

3.2.2.2 Creating the HTTP Destination for XI (SAP ICH)

Use In this activity, you create an HTTP destination for your integration server (SAP XI), which will be assigned in the role of the SAP ICH system.


SAP menu SAP menu Tools Administration Network RFC Destinations

© SAP AG of 62






RFC Destination The HTTP destination

R Enter the name, for example, XIBCLNT100

Connection type Connection type R Choose the type H

Description Description R Enter the description for the RFC destination, for example, XI HUB

4. Choose Enter to confirm the op-up message.




Service No. Service number

R Specify the service number, for example, 50064

PathPrefix Path in the HTTP service tree of the SAP Web AS

R Enter the prefix, for example, /sap/xi/engine/?type=entry

1. If the system displays the Query String Not Allowed message, ignore it.

2. To find out the number of the HTTP port (service number), call transaction SMICM and then choose Goto Service in your Integration Server (SAP XI).

6. Choose the Logon/Security tab, confirm the warning message and enter the following logon data:





User User R Enter the user, for example, XIAPPLUSER



3.2.2.3 Defining System Role for ICH (SAP ICH)

Use

© SAP AG of 62


You need to configure the role of your SAP ICH system as a business system which uses the Integration Engine to connect to the integration server. The Integration Engine is the runtime environment of the exchange infrastructure. It controls the messaging process (receiving, processing, and forwarding) to and from the central integration server.


SAP menu User menu for <you name> Exchange Infrastructure: Administration Integration Engine - Administration

Transaction code SXMB_ADM

2. On the Integration Engine: Administration screen choose Integration Engine Configuration and then, choose Execute Function.

3. On the Integration Engine Configuration Data screen, choose menu path Edit → Change Global Configuration Data.

4. On the same screen, enter the following data:


Role of Business System

System role R Choose the role Application System

Corresponding Integ. Server

Name of the integration server

R Enter the HTTP destination of the integration server, for example, dest://XIBCLNT100

Be careful of the syntax of the HTTP destination

You can also directly maintain the HTTP address of the Integration Server. However, the syntax used above is more secure than the explicit URL.


3.2.2.4 Activating HTTP Service (SAP ICH)

Use For the Integration Engine to be able to receive XML messages using HTTP, you have to activate an HTTP service. The HTTP services are deactivated by default. After every change you have to activate them again.


SAP Menu User menu for <you name> Exchange Infrastructure Environment HTTP Service Hierarchy Maintenance

Transaction code SICF

© SAP AG of 62


2. On the Maintain service screen go to default_host sap xi engine

3. Right click on the engine node and choose Activate Service from the context menu.

4. Select engine, and choose Create Host/Service.

5. Confirm the message for the namespace with Enter.

6. On the Create a Service Element screen, enter the following data:


Name of service element to be created:

Service name R Enter the new name, for example, engine_as7_001

Type of Service Node To Be Created:

Service type R Choose the type Reference to an existing service

7. Choose Input (Enter) and enter the following data:


Description Description O Enter the description of the service, for example, ICH service

8. Choose the Alias Trgt tab page and go to default_host sap xi engine. Double click on the engine and choose Save.

9. Confirm the warning pop up “Do you really want to save?”

10. Assign a proper package name, for example, $TMP.

11. Choose Cancel and go back to the Maintain service screen.

12. Select the alias you just created, right click on the node and choose Activate Link to activate it from the context menu.

13. Choose Back to quit the transaction.

3.2.2.5 Registering Queues (SAP ICH)

Use In this activity you register the queues used by the Integration Engine.


SAP Menu User menu for <you name> Exchange Infrastructure: Administration Integration Engine - Administration

Transaction code SXMB_ADM

© SAP AG of 62


2. On the Integration Engine: Administration screen choose Manage Queues

3. On the Manage Queues screen, keep the default values and choose Register Queues.

4. You will see the message Registration Complete on the status bar.

5. Choose Back to quit the transaction.

© SAP AG of 62


3.2.2.6 Maintaining HTTP Address of SLD Server (SAP ICH)

Use Business systems with an Integration Engine require a connection to the SLD server to obtain their name from the SLD. In this activity you define the SLD access data in your business system, the data consists of the host and port of the SLD as well as a user and password (XIAPPLUSER and XIPASS).


SAP Menu User menu for <you name> Exchange Infrastructure: Administration SLD API Customizing

Transaction code SLDAPICUST

2. On the Maintain SLD Access Data screen choose Display <-> Change and enter the following data:


Alias Alias O Enter the alias, for example, XIB_100

x

Prim. Primary SLD R Mark this checkbox

Host Name Host name R Enter the host name, for example, pwdf2268

Port Port number of the SLD

R Enter the port number, for example, 56400

User User id R Enter the user, for example, XIAPPLUSER

Password Password R Choose the button and enter the password, for example, XIPASS

The host name here must be identical to the name you maintain in the SLD. To find this host name, you can follow the menu path in your Integration Server (SAP XI): User menu for <you name> Exchange Infrastructure Environment Start SLD GUI in Browser Administration Details, choose Server tab; To find the port number for the SLD, you can choose Browser tab on the same page, use the port number after the host name, for example, Host: pwdf2268:56400.


© SAP AG of 62


3.2.2.7 Creating SLD Connection to XI (SAP ICH)

Use In this activity you create the RFC destinations LCRSAPRFC and SAPSLDAPI, which are used for the SLD connection.

PrerequisitesYou have registered the programs in the J2EE engine of your Integration Server.


SAP Menu SAP menu Tools Administration Network RFC Destinations




Field name R/O/C User action and values Note

RFC Destination

R Enter the name LCRSAPRFC This is a fixed name

Connection type

R Choose the type T

Description R Enter the description for the RFC destination, for example, SLD Connection LCRSAPRFC

14. Choose Enter.

15. On the RFC Destination <your RFC ID> screen, choose Technical Settings tab and enter the following data:


Activation type

Activation type

R Choose the type Registered Server Program


R Enter the program name, for example, LCRSAPRFC_AS7

This is the program id you register in the J2EE engine of your Integration Server, it uses the syntax LCRSAPRFC_<System ID>

CPI-C Timeout

Default Gateway Value

R Mark this checkbox

Gateway host

Gateway server

R Specify the host name, for example, pwdf2268

Gateway service

Gateway service

R Enter the gateway service, for example, sapgw64

© SAP AG of 62


To find out the value of the gateway host and service, call the transaction SMGW and choose Goto Parameters Display in your Integration Server (SAP XI), search the entries for the gateway hostname and gateway service attributes.



17. Choose Save.

18. Repeat the step 3 to step 6 to create the RFC destination for the program SAPSLDAPI, using the following data:


RFC Destination

The RFC destination

R Enter the name SAPSLDAPI

This is a fixed name

Connection type

Connection type

R Choose the type T

Description Description R Enter the description for the RFC destination, for example, SLD Connection SAPSLDAPI

Activation type

Activation type

R Choose the type Registered Server Program


R Enter the program name, for example, SAPSLDAPI_AS7

This is the program id you register in the J2EE engine of your Integration Server, it uses the syntax SAPSLDAPI_<System ID>

CPI-C Timeout

Default Gateway Value

R Mark this checkbox

Gateway host

Gateway server

R Specify the host name, for example, pwdf2268

Gateway service

Gateway service

R Enter the gateway service, for example, sapgw64


© SAP AG of 62


You can use the transaction code SLDCHECK at the business system to check whether the business system can connect to the SLD server after you finish the configuration of the SLD connection.

© SAP AG of 62


3.3 SAP XI with SAP ECC

3.3.1 SAP XI

3.3.1.1 Creating the RFC Destination (SAP XI)

UseIn this activity, you create a RFC Destination from your Integration Server to the SAP ECC system.


SAP XI IMG menu SAP Customizing Implementation Guide SAP NetWeaver SAP Web Application Server IDoc Interface/Application Link Enabling (ALE) Communication Create RFC Connections





RFC Destination

The RFC destination

R Enter the name, for example, KD6CLNT416

Connection type

Connection type R Choose the type 3

Description Description R Enter the description for the RFC destination, for example, Automotive OEM

4. Choose Enter.



Target host Target host R Specify the host name, for example, ld0059

System number.

System number R Specify the system number, for example, 19

6. Choose the Logon/Security tab and enter the following logon data:





© SAP AG of 62



User User R Enter the user, for example, RFCUSER

Make sure that the user id is identical to that already created in your ECC system

Password Password R Enter the password, for example, BPLOGIN

Make sure that the password is identical to that in your ECC system




3.3.1.2 Assigning Port for SAP ECC (SAP XI)

UseIn this activity you assign an IDoc Adapter Port (RFC Destination) to the SAP ECC system, which sends the IDoc to the Integration Server.


SAP XI IMG menu User menu for <your name> Exchange Infrastructure: Configuration Port Maintenance in IDoc Adapter

Transaction code IDX1

2. On the Port Maintenance in IDoc Adapter screen choose Create.

3. Enter the following data on the right side of the screen:


Port Port R Enter the port name, for example, SAPKD6

Using SAP+<your system name>

Client Client R Enter the client number, for example, 416

Description Description R Enter the description, for example, KD6CLNT416

RFC Destination

RFC destination

R Choose the RFC destination, for example, KD6CLNT416

This the SAP ECC system which sends the IDoc into the Integration Server

© SAP AG of 62


3.3.1.3 Loading IDoc Meta Data (SAP XI)

UseIn this activity, you load the Meta Data of the relevant IDoc types from your ECC system into the integration server.


SAP XI IMG menu User menu for <your name> Exchange Infrastructure: Configuration Meta Data Display in IDoc Adapter

Transaction code IDX2

2. On the Metadata Overview for IDoc Adapter screen choose Create.

3. On the Reload a type description screen, enter the following data:


IDoc Type R Enter the IDoc type, for example, PROACT01

Source Port R Enter the port number, for example, SAPKD6

This is the port you assigned to the IDoc Adaptor

4. Choose Continue to load the data.

5. Repeat the step 3 to step 4 and with the following data:


IDoc Type R Enter the IDoc type, for example, DELFOR01





IDoc Type R Enter the IDoc type, for example, DELVRY03





IDoc Type R Enter the IDoc type, for example, ORDERS05





IDoc Type R Enter the IDoc type, for example, ORDERS03

© SAP AG of 62







IDoc Type R Enter the IDoc type, for example, DELVRY05





IDoc Type R Enter the IDoc type, for example, DELFOR02





IDoc Type R Enter the IDoc type, for example, PORDCR102





IDoc Type R Enter the IDoc type, for example, PORDCH02



13. Go back.

© SAP AG of 62


3.3.1.4 Defining Services and Communication Channels for SAP ECC (SAP XI)

UseIn this activity, you define a service (business system service) for the business system (the SAP ECC in our case). The communication channels for the involved business system are created automatically as well.


SAP XI menu User menu for <you name> Exchange Infrastructure: Integration Builder Start Integration Builder


The SAP Exchange Infrastructure page is opened in your default browser.

2. Choose the link Integration Directory.

3. The Java Web Start program is started.

4. Enter the following data on the Configuration: Integration Builder: (<Your integration server>) screen:


User User ID R Enter the logon user Ask the administrator for the user id and password

Password Password R Enter the password

Language Language O Choose the logon language, for example, English

The screen might be started in German, in this case, please be noticed that the sequence of the fields is arranged as the sequence in the above table.

5. On the Configuration: Integration Builder (<your system>) page, select Environment Clear SLD Cache to update the SLD data.

6. Confirm the pop-up window with Enter.

7. In the navigation area, on the Objects tab page, position the cursor on the Service without Party node.

8. In the context menu, choose Assign Business System to call the wizard for assigning business systems.

9. Choose Continue.

10. On next screen, leave field Party blank, choose Continue again

11. On the next screen, select your SAP ECC business system (for example, KD6CLNT416) by using the corresponding checkboxes.

12. Make sure that the Create Communication Channels Automatically checkbox is selected. In this case, the receiver communication channels for the selected business systems are created automatically.

13. Choose Finish

14. Read the Information Message and choose Close.

© SAP AG of 62


15. In the navigation area, under Service Without Party Business System <SID>CLNT<Client> Communication Channel, right click the communication channel GeneratedReceiverChannel_IDoc.

16. In the context menu, choose Open.

17. Choose Switch between display and edit mode to switch to change mode

18. On the Edit Configuration Parameters screen, in the Parameters tab, check and specify the following data:


Adapter Type

R IDoc

Transport Protocol

R IDoc

Message Protocol

R IDoc

Adapter Engine

R Integration Server

RFC destination

R Enter the RFC destination for your ECC system, for example, KD6CLNT416

Interface Version

R Choose the version of your ECC system, for example, SAP Release 4.0 or Higher

Port R Enter the port, for example, SAPKD6 This is the port you have defined for your ECC system in SAP XI

SAP Release

R Enter the release number for your Web Application Server, for example, 700

19. Choose Save to save your data.

20. In the navigation area, select the Change Lists tab page.

21. If more than one change lists appears, expand the change lists and check which lists the communication channels are assigned to.

22. Delete the communication channels that are not required one by one.

For the Business System SAP ECC, the Communication Channels GeneratedReceiverChannel_HTTP, GeneratedReceiverChannel_XI and GeneratedReceiverChannel_RFC are not required.

© SAP AG of 62


To delete an object in a change list, you must first open it (double-click), Then choose Communication Channel Delete in the menu bar of the object editor.

23. Right click the change list with the communication channels and choose Activate in the context menu.

24. Go back to the Objects tab.

25. In the navigation area, under Service Without Party Business System <SID>CLNT<Client> Communication Channel, check that only the communication channel GeneratedReceiverChannel_IDoc is available.

26. Choose menu Object Exit to quit the program.

© SAP AG of 62


3.3.2 SAP ECC

3.3.2.1 Creating the RFC Destination (SAP ECC)

UseIn this activity, you create a RFC Destination from your SAP ECC system to the Integration Server.


SAP ECC IMG menu

SAP Customizing Implementation Guide SAP Web Application Server Application Link Enabling (ALE) Sending and Receiving Systems Systems in Network Define Target Systems for RFC calls





RFC Destination

R Enter the name, for example, XIBCLNT100

Ensure the name is identical to the name of the logical system created in the previous step

Connection type

R Choose the type 3

Description R Enter the description for the RFC destination, for example, XI Hub

4. Choose Enter.




System number.

System number R Specify the system number, for example, 64

6. Choose the Logon/Security tab and enter the following logon data:





User User R Enter the user, for example, XIAPPLUSER1


© SAP AG of 62


3.4 Connecting SAP BW with SAP ECC, SAP CRM, SAP SRM

Procedure1. To carry out the activity, choose one of the following navigation options in the SAP BW

system:


2. Choose Modeling.

3. Choose Source systems.

4. Select Source systems in the window on the right.

5. Choose the Context menu (right mouse click).

6. Choose Create.

7. Select SAP System from Release 3.0E (Automatic Creation).


Field Entry

Target computer (server) Server of the SAP ECC, SAP CRM or Sap SRM system

System ID System ID of the SAP ECC, SAP CRM or SAP SRM system

System number System number of the SAP ECC, SAP CRM or SAP SRM system

Background user in source system

RFCUSER

Password for source system LOGIN

Background user in BW RFCUSER (can not be changed in this activity)

Password for BW user LOGIN

9. On the dialog box Please log on as an administrator in the following screen choose Continue.

10. Log on to the Source System with your administrator user. Choose the correct client.

11. On the dialog box New Source System Connection choose Continue.

12. On the Replicate Metadata dialog box, choose Only Activate.

If you receive the error “No entry for BW_User in table RSADMIN”, refer to SAP note 410952.

© SAP AG of 62


3.5 SAP SCM with SAP BWFor information on this section, select the relevant items in the substructure.

3.5.1 Connecting SAP SCM to the SAP BW system (SAP BW)

Procedure1. To carry out the activity, choose one of the following navigation options in the SAP BW

system:


2. Choose Modeling.




6. Choose Create.

7. Select SAP Business Information Warehouse.


Field Entry

Target computer (server) Server of the SAP SCM system

System ID System ID of the SAP SCM system

System number System number of the SAP SCM system


RFCUSER

Password for source system BPLOGIN


Password for BW user BPLOGIN

9. On the dialog box, log on as an administrator.

10. In the following screen choose Continue.

11. Log on to the source system with your administrator user. Choose the correct client.

12. In the New Source System Connection dialog box, choose Continue.

13. In the Replicate Metadata dialog box, choose Only Activate.

© SAP AG of 62


3.5.2 Connecting SAP BW to the SAP SCM system (SAP SCM)

Procedure1. Carry out the activity in the SAP SCM system.


2. Choose Modeling.




6. Choose Create.

7. Select SAP Business Information Warehouse.


Field Entry

Available destination Destination of your SAP BW system


RFCUSER

Password for source system BPLOGIN


Password for BW user BPLOGIN

9. On the dialog box Please log on as an administrator in the following screen, choose Continue.

10. Log on to the source system with your administrator user. Choose the correct client.

11. On the Check RFC destination dialog box, choose Use.

© SAP AG of 62


3.6 Connecting SAP BW to a File System (SAP BW)

ProcedureSA BW menu From the SAP Menu in the BW system, choose:

BW-Administration Administrator Workbench


1. Choose Modeling.

2. Choose Source Systems.

3. In the right screen area, select Source Systems and right-click on it to display the context menu.

4. Choose Create.

Field name User action and values

File System, Manual Meta Data, Data Using File... X

5. Choose Enter.

Field name User action and values

Logical source system for example, EXCEL

Source system name for example, Excel File

6. Choose Enter.

7. Choose Back.

© SAP AG of 62

b02_bb_configguide_en_de

Documents

sap products

sap scm

sap netweaver

sap group products

client sap ecc

express permission of

logical system sap ecc

rfc user sap ecc