SAP SCM 5.

0 November 2007 English

Building Block B02 Connectivity
Building Block Configuration Guide

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany

SAP Best Practices

Building Block B02 Connectivity: Configuration Guide

Copyright
© Copyright 2007 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, Excel, 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, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. 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, Duet, PartnerEdge, 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

Page 2 of 62

SAP Best Practices

Building Block B02 Connectivity: Configuration Guide

Icons
Icon Meaning Caution Example Note or Tip Recommendation Syntax

Typographic Conventions
Type Style Example text Description 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 EXAMPLE TEXT Emphasized words or phrases in body text, titles of graphics and tables. 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. 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. Keys on the keyboard, for example, function keys (such as F2) or the ENTER key. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

Example text

EXAMPLE TEXT

Example text <Example text>

© SAP AG

Page 3 of 62

.............................................................1 SAP ECC..........................................................13 2...26 3.........1 Defining Client Administration............1 Connecting SAP SCM to the SAP BW system (SAP BW)...............................................................................5 Creating Business System Group (SAP SCM).....2 Defining a Logical System for SAP BW (SAP BW)............49 3..........1....................................................2 SAP XI with SAP ICH..... SAP SRM...................2 SAP SCM.....1 SAP ECC with SAP SCM...............................................................................................7 2..........................26 3..7 2..........4...8 2...................7 2.................................49 3........................................................................15 2.......9 2.........................................................................................................2...............2...........4........................................................................33 3.2 Defining Logical System (SAP ECC).....................................................4 Creating an RFC User (SAP BW).......................2 Configuring SAP Technical System in SLD (SAP XI)..................................................................................12 2....................................................2 Defining a Logical System for SAP SCM (SAP SCM).......5 SAP SCM with SAP BW..................................3 Assigning Logical System to Client (SAP ECC)...............3 Assigning Logical System to Client (SAP SCM)................5..........................................1.......30 3............................................................................................2...................25 3 Cross-Connectivity............................................................................40 3.............9 2................33 3.....................................................................15 2..........................................................................................................................1........................................4............4 Creating an RFC User (SAP SCM).....4..................20 2................................................................................23 2.........2 SAP ECC...............2....................................2 SAP ICH......................................2.............................................................59 3..3 SAP XI..............18 2................22 2............................................3...............1 Defining Client Administration (SAP ECC).4 Creating an RFC User (SAP ECC)......................................24 2.......................3 SAP XI with SAP ECC..............................................4 SAP BW...................................................................1...........6 2 Local Settings.................4 Connecting SAP BW with SAP ECC......1 Define Client Administration (SAP SCM)........1 SAP XI..........26 3........ SAP CRM..............1.............................3 Assigning Logical System to Client (SAP BW)............4.................2....................1 SAP XI............................................................................1 Installing Java Web Start for SAP XI........13 2.........................................................3...........1 SAP ECC.........................24 2....................................22 2.......................................60 © SAP AG Page 4 of 62 .................................................2....................................17 2................................................2 SAP SCM.......11 2.....................................................................5 Define RFCUSER as default (SAP BW).............11 2..............................18 2.................................3.................................60 3................2........................................................3..............................................................6 Assigning Logical System to Business System Group (SAP SCM)........SAP Best Practices Building Block B02 Connectivity: Configuration Guide Contents 1 Preparation...........................1.............3 Configuring SAP Business System in SLD (SAP XI).....................3....................57 3........................................................

.........2 Connecting SAP BW to the SAP SCM system (SAP SCM)...............61 3...............................6 Connecting SAP BW to a File System (SAP BW)............................SAP Best Practices Building Block B02 Connectivity: Configuration Guide 3.....5......62 © SAP AG Page 5 of 62 ....

To work with this configuration guide. © SAP AG Page 6 of 62 .SAP Best Practices Building Block B02 Connectivity: Configuration Guide Connectivity: Configuration Guide 1 Preparation This configuration guide provides the information you need to set up the configuration of this building block. 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 Page 7 of 62 . In the Change View “Clients”: Details screen. Save. activate the following settings: − − − 6. Procedure 1.1 Use This activity allows you to change Customizing settings and to start eCATT procedures.1 SAP ECC 2.1. 5. Confirm the warning message Caution: The table is cross client. Defining Client Administration (SAP ECC) Prerequisites You have logged on to the system in English to start with the installation. Select your SAP ECC client and choose Details. 3. 4. Automatic recording of changes Changes to Repository and cross-client Customizing allowed eCATT and CATT Allowed. The logon language must be English (EN) to ensure that you find all menu paths described in the documentation.SAP Best Practices Building Block B02 Connectivity: Configuration Guide 2 Local Settings 2. Choose Display → Change. choose one of the following navigation options: SAP ECC Menu Transaction code Tools  Administration  Administration  Client Administration  Client Maintenance SCC4 2. To carry out the activity. Go back to the SAP Easy Access Menu. 7.

Choose New Entries. 5. if necessary. Access the activity using one of the following navigation options: SAP ECC IMG menu SAP Customizing Implementation Guide → Integration with Other SAP. A transport request for Workbench appears.SAP Best Practices Building Block B02 Connectivity: Configuration Guide 2. If the logical system has already been created. Save your entries. Confirm the information message “Caution: The table is cross-client”. skip this activity. 2. if necessary. you must 1. Log. In the column Log.com Components → Advanced Planning and Optimization → Basic Settings for Setting Up the System Landscape → Name Logical System SPRO Transaction code 3. enter a description of the logical system. 4. 2. Select an existing request or create a new request. System <Logical system 2>. Name SAP R/3 System © SAP AG Page 8 of 62 . Logical systems are defined cross-client Procedure 1. <client number> is the number of the relevant client in your ECC system. A transport request for Customizing appears. 7. 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.System. 8. (for example DS7CLNT723) 6.2 Use Defining Logical System (SAP ECC) The purpose of this activity is to create a logical system for your SAP ECC System. This enables the systems to recognize the target system as an RFC destination. Assign the logical system for the SAP ECC System to a client. enter a name for the logical system you want to create. To enable communication between systems within your system landscape. Select an existing request or create a new request. In the Name column.1. Define the systems as logical systems.

select the newly created logical system of your SAP ECC client using the input help. enter RFCUSER. you have to create an RFC user in the SAP ECC System. 5.SAP Best Practices Building Block B02 Connectivity: Configuration Guide 2. Choose Display → Change. 4. 6. 7. Select your ECC client and choose Details.4 Use Creating an RFC User (SAP ECC) To enable communication between the SAP ECC back-end system and other SAP systems. 3. In the Maintain User screen. 3.3 Use Assigning Logical System to Client (SAP ECC) The purpose of this activity is to make an assignment for the logical system. Save and confirm the warning message Be careful when changing the logical system. The RFC user in the application client enables multiple RFC connections. Confirm the warning message Caution: The table is cross client. Choose Back twice. In field Logical System. enter the following data on the following tab pages: Address Tab Last Name Function Logon Data Tab User type Initial Password System BPLOGIN RFC User © SAP AG Page 9 of 62 . In the User field. 2. Choose Create. 4. Access the activity using one of the following navigation options: SAP ECC Menu Transaction code Tools → Administration → User Maintenance  Users SU01 2. Procedure 1. Skip this activity if a logical system is already assigned to your client. Procedure 1.1. Skip this activity if an RFC User has already been created.1. Access the activity using one of the following navigation options: SAP ECC Menu Transaction code Tools → Administration → Administration → Client Administration → Client Maintenance SCC4 2.

which gives him full authorization rights. Save your entries. If this authorization is not applicable to your project you can restrict the rights of this user according to SAP Note 0338537. The user RFCUSER has the profiles SAP_ALL and SAP_NEW assigned. © SAP AG Page 10 of 62 .SAP Best Practices Repeat Password Defaults Tab Logon Language Profiles Tab Profile Building Block B02 Connectivity: Configuration Guide BPLOGIN EN SAP_ALL SAP_NEW S_BI-WX_RFCA 5.

choose Display → Change and confirm the message The table is cross-client.2 SAP SCM This step describes the local settings required for the SAP SCM system – the full version. 3.2. Prerequisites You have logged on to the system in English to start with the installation. 5. In the view Change View "Clients": Details. which consists of the following components: • • • SAP APO SAP EM SAP ICH. 4. 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. 2.SAP Best Practices Building Block B02 Connectivity: Configuration Guide 2. © SAP AG Page 11 of 62 . Save and choose Back twice. Note that SAP ICH has not been tested as a standalone component (without SAP APO) by SAP Best Practices.1 Use Define Client Administration (SAP SCM) This activity enables you to change Customizing settings and start eCATT procedures. The logon language must be English (EN) to ensure that you find all menu paths described in the documentation. Choose Details. Procedure 1. In the view Display View "Clients": Overview. Select your SCM client. Access the activity choosing one of the following navigation options: SAP SCM menu Transaction code SAP menu → Tools → Administration → Administration → Client Administration → Client Maintenance SCC4 2. set the flags for − − − Automatic recording of changes Changes to Repository and cross-client Customizing allowed eCATT and CATT allowed 6.

Assign the logical system for the SAP SCM system to a client. if necessary. 7. A transport request for Customizing appears. 2. if necessary. you must 1. Define the systems as logical systems. A transport request for Workbench appears. © SAP AG Page 12 of 62 . 4. 5. skip this activity.SAP Best Practices Building Block B02 Connectivity: Configuration Guide 2. In the column Name. Select an existing request or create a new request. In the column Log System. Save your entries. System <Logical system 2>. To define the logical system for your SAP SCM system.2. Log.2 Use Defining a Logical System for SAP SCM (SAP SCM) The purpose of this activity is to create a logical system for your SAP SCM system. To enable communication between systems within your system landscape. for example AS7CLNT001 Name SAP SCM system To designate logical systems. enter a name for the logical system that you want to create. Choose New entries. If the logical system has already been created. This enables the systems to recognize the target system as an RFC destination. Select an existing request or create a new request. 6. enter a description of the logical system. apply the naming convention <XXX>CLNT<NNN> where XXX is the system name and NNN is the client. choose one of the following navigation options: SAP SCM IMG menu SAP SCM-Implementation Guide → Integration with SAP Components → Integration via APO Core Interface (CIF) → Basic Settings for Creating the System Landscape → Name Logical Systems SPRO Transaction code 2. 3. Logical systems are defined cross-client Procedure 1.

In the Maintain User screen. Select your SCM client and choose Details. In the User field. SAP menu → Tools → Administration → Administration → Client Administration → Client Maintenance SCC4 2. Access the activity choosing one of the following navigation options: SAP SCM menu Transaction code 2. enter RFCUSER. Choose Display → Change. Confirm the warning message The table is cross client.3 Use Assigning Logical System to Client (SAP SCM) The purpose of this activity is to make a client assignment for the logical system. 5. 4. Procedure 1. Choose Back twice. Procedure 1. To carry out this activity. 3. 4. Save and confirm the warning message Be careful when changing the logical system. Skip this activity if a logical system is already assigned to your client. choose one of the following navigation options: SAP SCM IMG menu Transaction code SAP Menu → Tools → Administration → User Maintenance → Users SU01 2. enter the following data on the tab pages: Address Last Name Function RFCUSER © SAP AG Page 13 of 62 .SAP Best Practices Building Block B02 Connectivity: Configuration Guide 2. Enter the name of the logical system of your SAP SCM client. 6. The RFC user in the application client enables multiple RFC connections. 3.2. Skip this activity if an RFC User has already been created. you have to create an RFC user in the SAP SCM system.4 Use Creating an RFC User (SAP SCM) To enable communication between the SAP ECC backend system and the SAP SCM system. 7.2. Choose Create.

Save your entries and go back 6. enter XIAPPLUSER1. 5. In the User field. 8. you can restrict the rights of this user. enter the following data on the tab pages: Address Last Name Function XIAPPLUSER1 Logon data User type Password Profile Profiles Defaults Logon Language 9. If this authorization is not applicable to your project. 7. In the Maintain User screen. EN Leave blank System XIPASS © SAP AG Page 14 of 62 . Save your entries. Choose Create. the user RFCUSER has the profiles SAP_ALL and SAP_NEW which gives this user unrestricted authorization.SAP Best Practices Logon data User type Password Defaults Logon Language Profile Profiles Building Block B02 Connectivity: Configuration Guide System BPLOGIN EN SAP_ALL SAP_NEW S_BI-WHM_RFC S_BI-WX_RFC Here.

The SCM system must be assigned to one Business System Group only.2.6 Use Assigning Logical System to Business System Group (SAP SCM) In this activity. use one of the following navigation options: SAP SCM IMG Path SAP SCM – Implementation Guide  Integration with SAP Components → Integration via APO Core Interface (CIF) → Basic Settings for Creating the System Landscape → Maintain Business System Group SPRO Transaction code 2. we strongly recommend that you create a separate business system group (BSG) with a unique name for each ECC system (or each ECC client). you can skip this part. If you plan to connect more than one ECC system to the SCM system. It is important that you decide upon the total number of BSG before data replication takes place. After defining the business system group. you assign the logical system of your SAP SCM to the business system group. This way. Access the activity using one of the following navigation options: © SAP AG Page 15 of 62 . Decide now how many BSGs you will need. The purpose of business system groups is to maintain the data volumes and the processing of different business areas separate across different systems or different system clients. Choose New entries and enter the following data: Field name BusSystGrp Description 3. In a multi-system scenario. you assign the logical system of your SAP SCM and SAP ECC System to the business system group. User action and default values <Name of Business System Group > Enter a text description of the Business System Group 2.SAP Best Practices Building Block B02 Connectivity: Configuration Guide 2. economic. you can keep the data processing separate and avoid data inconsistencies between the systems. A business system group represents a unit within a company or organization that can be defined according to legal. If the SCM system is already assigned to a Business System Group. Procedure 1. Procedure 1.2. administrative or geographic factors. To maintain the business system group. the logical systems of all the systems involved must be assigned to a business system group to support synchronization of master data. you define a business system group.5 Use Creating Business System Group (SAP SCM) In this activity. Save your entries.

3.SAP Best Practices Building Block B02 Connectivity: Configuration Guide SAP SCM IMG Path SAP 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 SPRO Transaction code 2. © SAP AG Page 16 of 62 . With this setting. SCM <SCM System>CLNT<Client>. queue processing is controlled by the target system. if it is not set. In this case you have to set up the QIN (queue in) scheduler in the qRFC monitor in the target system. Save your entries. for example. choose New entries and enter the following data: Field name BusSystGrp Logical System User action and default values <Name of Business System Group >. To assign a logical system to your business system group. the source system is an SAP ECC system. Queues that are to be automatically processed by the target system must be registered in the QIN scheduler (Transaction SMQR). for example. for example 50 (SCM) Outbound Queue Strict (Terminate at Errors) Not Specified Queue Type: You should choose Inbound Queues if you are expecting large amounts of data during the transfer from the source system to the target system and you want to ensure that the target system is not overloaded. AS7CLNT001 Do not select SAP System Indicator (If this indicator is set. it is a legacy system) SAP Release Queue Type Error Handling in Target System Role Release of corresponding system.

Prerequisites SAP 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. this integration server should already be created in the SLD. The System Landscape Directory (SLD) provides a central repository which stores the information about all the installable and installed elements of your system landscape. Use In the Supplier Managed Inventory scenario. 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.3 SAP XI The 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. It is composed of the component repository and the landscape directory. This chapter describes the required activities in order to register the SAP ICH and SAP ECC respectively in the SLD. 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 Page 17 of 62 . In order to perform following steps. 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. 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.SAP Best Practices Building Block B02 Connectivity: Configuration Guide 2.

you can skip this step. you create the SAP technical system in the System Landscape Directory (SLD).SAP Best Practices Building Block B02 Connectivity: Configuration Guide 2. the client and instance number. which primarily describe the technical aspect of the system. there will be a message stating You need to install Java Web Start version x. Download and install the J2SE component. If the system prompts you for proxies during installation. Choose one of the following navigation options: SAP XI menu Transaction code User menu for <you name> → Exchange Infrastructure → Integration Builder SXMB_IFR This transaction launches the web browser for the XI. Procedure 1. Click on the link supplied and download the J2SE component. choose one of the following navigation options: SAP XI menu Transaction code User menu for <you name> → Exchange Infrastructure → Environment → Start SLD GUI in browser SLDHTMLGUI © SAP AG Page 18 of 62 . but not the J2EE component. 8. 5. 4. To carry out the activity. and execute. You need to perform these steps twice: Once for your SAP ICH system and once for your SAP ECC system. Ignore the Sun Java security warning stating It is highly recommended not to install and run this code.3. the Java Web Start application will be available on your local PC.2 Use Configuring SAP Technical System in SLD (SAP XI) In this activity. After the installation of J2SE. 3. You need to provide information such as the server name.3. 2. If you have installed Java Web Start. 7. If you do not have Java Web Start in your workstation. Log on to the SAP XI system to check whether Java Web Start has been installed. 6. select No proxies.x.1 Use Installing Java Web Start for SAP XI Before you can configure SAP Exchange Infrastructure (XI) to work with SAP Inventory Collaboration Hub (ICH) Java Web Start must be installed in your workstation. Choose Start. 2. Select No proxies. Procedure 1. Launch it and choose Files → Preferences → General.x.

On the SLD Technical System Wizard – Message Server and Central Application Server page. for example. AS7 Specify the SAP system installation number. for example. select Technical System Type – Web AS ABAP and choose Next. Choose the link Technical Systems. PWDF0155 Specify the instance number. for example. for example. In the logon pop-up enter again your user name and password and choose OK. 3. 21 – R – Instance Number R – Ask your system administrator for the relevant information. © SAP AG Page 19 of 62 . 9. 8. 5. make the following entries: Field name Web as ABAP Name (SID) Installation Number Database Host Name Description SAP system name Installation number of your SAP system The name of database server R/O/C R R User action and values Specify the SAP system name. The SAP System Landscape Directory page will be opened in your default browser. PUBLIC Specify the name of the server. On the SLD Technical System Wizard – System Details page. 7. for example. make the following entries: Field name Host Name Description Name of the message server The TCP port number that this message server uses to listen for load-balanced SAP login request Name of Logon Groups Name of the central application server Instance number R/O/C R User action and values Specify the name of the server. for example. On the SLD Technical System Browser page. choose System → Status… from the menu bar of your SAP system. choose New Technical System…. Choose Next. 6. On the SLD Technical System Wizard – Technical System Type page. 4. for example. PWDF0155 Specify the message server port. PWDF0155 Note – – R – To check the installation number and host name of your system. for example. 0120007965 Specify the name of the server. 3600 Note – Message Server Port R Usually 3600+Instance Number Logon Groups Host Name R Specify the name of Logon Group.SAP Best Practices Building Block B02 Connectivity: Configuration Guide 2.

Prerequisites The SAP technical system has been created. for example. make the following entries: Field name Client Number Logical System Name 14.3 Use Configuring SAP Business System in SLD (SAP XI) Business systems are logical systems that serve as senders or receivers within the SAP Exchange Infrastructure. Repeat steps 4 to step 21 to register your SAP ECC system.1 Note – Description Client number The logical name assigned to this client R/O/C R R User action and values Specify the name of the client. the page is refreshed and the installed components are displayed. for example.SAP Best Practices 10. for example. 2. On the SLD Technical System Wizard – Software Product And Components page. Building Block B02 Connectivity: Configuration Guide 11. A business system is associated with the technical SAP system. 12. Keep the default value and choose Finish to leave the SLD Technical System Browser page. Choose Next 15.3. 001 Specify the logical system. Choose Next 13. choose the following value: Field name Available Products Description Available products R/O/C R User action and values Choose the SAP system from the list box. Choose Add. If you have several application servers. 18. Choose Next. 17. AS7CLNT001 Note – – 16. you create a new SAP business system and assign it to the SAP technical system you created in the previous step. © SAP AG Page 20 of 62 . enter them on this page. On the SLD Technical System Wizard – Client page. SAP SCM 4. Result The SAP technical system is registered in the System Landscape Directory. In this activity. The SLD Technical System Wizard – Additional Application Server (optional) page appears.

choose one of the following navigation options: SAP XI menu Transaction code User menu for <you name> → Exchange Infrastructure Environment → Start SLD GUI in browser SLDHTMLGUI 2. 11. make the following entry: Field name Name Description The name of the SAP Business System R/O/C R User action and values Specify the name. The SAP System Landscape Directory page will be opened in your default browser. In the logon dialog box. 3. Choose Next 10. Result The SAP Business System is created and assigned to a SAP Technical System that is already registered in the SLD. Repeat steps 4 to step 12 to register your SAP ECC system. XIB Note – – 12. make the following entry: Field name System Description The SAP system you created R/O/C R User action and values Choose the SAP system from the list box. for example.SAP Best Practices Building Block B02 Connectivity: Configuration Guide Procedure 1. Choose the link Business Systems. 8. Choose Finish to quit to the SLD XI Landscape page. choose New Business System 5. On the SLD Business System Wizard – Installed Products page. On the SLD Business System Wizard – Name page. On the SLD Business System Wizard – Select System page. The page is refreshed and all existing clients of this system are listed in the Client box. make the following entries: Field name Business System Role Related Integration Server Description System role The integration server R/O/C R R User action and values Choose the role Application System Choose the server. for example. 001 of AS7 and choose Next. On the SLD Business System Wizard – Technical System Type page. On the SLD Business Landscape page. select Web AS ABAP and choose Next 6. make sure that the product is selected and then choose Next. Choose the client you will use. © SAP AG Page 21 of 62 . for example. 4. 13. AS7CLNT001 Note -- 9. To carry out the activity. enter again your user name and password and choose OK. for example. AS7 on PWDF0155 Note – 7. On the SLD Business System Wizard – Integration page.

SAP Best Practices

Building Block B02 Connectivity: Configuration Guide

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 Use

Defining Client Administration

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

Procedure
1. To perform this activity, choose one of the following navigation options: Transaction code 2. Switch to Change mode. 3. Select your client. 4. Choose details. 5. In field Currency, enter EUR. 6. In field Client Role, enter Customizing. 7. Check the settings for changes and transport of client-specific objects and clientindependent 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 crossclient Customizing allowed” is required. 8. 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. SCC4

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

© SAP AG

Page 22 of 62

SAP Best Practices

Building Block B02 Connectivity: Configuration Guide

2.4.2 Use

Defining a Logical System for SAP BW (SAP BW)

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

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

Procedure
1. To carry out the activity, choose one of the following navigation options: SAP BW IMG menu SAP Reference IMG  BW Customizing Implementation Guide  Business Information Warehouse  Links to other Systems  General Connection Settings  Define Logical System SPRO

Transaction code

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: Field name Log. System Name Description Technical Name of the Logical System Textual Description of the Logical System R/O/C User action and values Enter a name for the logical BW system you want to create Enter a clear description for the logical BW system Note –

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

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

© SAP AG

Page 23 of 62

SAP Best Practices

Building Block B02 Connectivity: Configuration Guide

2.4.3

Assigning Logical System to Client (SAP BW)

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

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 − − Automatic recording of changes 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)

Procedure
1. To carry out the activity, choose one of the following navigation options SAP BW menu Transaction code Field User 3. Choose Create. 4. On the Maintain User screen, choose Address and enter the following data: Field Last Name Function Field Password User type Entry RFCUSER Default-User for RFC connection Entry LOGIN System Tools  Administration  User Maintenance  Users SU01 Entry RFCUSER

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

5. Choose Logon data and enter the following data:

© SAP AG

Page 24 of 62

Entry SAP_ALL . SAP_NEW and S_BI-WHM_RFC 2. Choose Profiles and enter the following data: Field Profiles 7. choose one of the following navigation options Transaction code RSA1 1.5 Define RFCUSER as default (SAP BW) Procedure To carry out the activity. Choose Save.4. Enter RFCUSER in the BW User ALE field. 2. Settings. Do not change the password of this user. On the “RSADMINA Maintenance View” screen. as it is used in RFC connections. On the Administrator Workbench: Modeling screen choose Settings  Global Settings. choose Display  Change. 3. 4. © SAP AG Page 25 of 62 .SAP Best Practices Building Block B02 Connectivity: Configuration Guide 6. On the Global Settings/Customizing dialog box choose Glob.

Confirm the information message that appears. you need to define logical systems for both systems in your ECC System. open the transaction using: SAP ECC IMG menu SAP Customizing Implementation Guide → Integration with Other SAP. 4. 3.1 3.1 Use To enable communication between your SAP SCM and your SAP ECC systems. 5. A transport request for Workbench appears. 3. System <Logical system 1>. if necessary. In the column Log System. A transport request for Customizing appears. 7.1.1. Select an existing request or create new request. Choose New entries. © SAP AG Page 26 of 62 . if necessary. In the column Name. Log. 8. Select an existing request or create a new request. enter a description of the logical system.1 SAP ECC with SAP SCM 3.1. SAP ECC Creating a Logical System for SAP SCM (SAP ECC) Procedure 1. enter a name for the logical system that you want to create. XXX is the system name and NNN is the client.com Components → Advanced Planning and Optimization → Basic Settings for Setting Up the System Landscape → Name Logical System SPRO Transaction code 2. Save your entries. To define the two required logical systems for your system. The separate structure nodes make it possible to identify the activities required to connect certain components with each other. for example AS7CLNT001 Name SAP SCM system To designate logical systems.SAP Best Practices Building Block B02 Connectivity: Configuration Guide 3 Cross-Connectivity This chapter describes all settings that are necessary to connect the components of the SAP ERP landscape with each other that are relevant for an SCM solution. apply the naming convention <XXX>CLNT<NNN> where 6. The settings for each combination of two components to be connected are described in a separate structure node.

To define an RFC destination in the SAP ECC System. choose Create.1. 3. To set up these functions in your systems. Move to the Technical Settings tab and make the following entries: Technical settings Balance Load Target host System number Save as No <SAP SCM target host name>. Building Block B02 Connectivity: Configuration Guide 3. 6.SAP Best Practices 9. open the transaction: SAP ECC IMG menu SAP Customizing Implementation Guide → Integration with Other SAP. select Groups and enter the name of your system. Procedure 1. where Remote Function Calls (RFCs) manage the communication process. In the Configuration of RFC Connections screen.com Components → Advanced Planning and Optimization → Basic Settings for Setting Up the System Landscape → Set Up RFC Destination SM59 Transaction code 2. parameter transfer and error handling between different systems.1. click on “Add and Logon”. Make the following entries: Field name RFC destination User action and default values <SAP SCM system name>CLNT<client> for example AS7CLNT001 Connection type Description Description 4. you need to define RFC destinations in your system landscape. The target host will appear in the field Message Server. for example 74 Host name (select) SAP SCM system 3 (Connection to ABAP system) One option of finding the host name is to go through the SAP Logon.2 Use Connecting SAP SCM (SAP ECC) Communication between the systems is based on the RFC interface. for example pwdf0421 <SAP SCM target system number>. Choose Enter. Go back twice. Move to the Logon/Security tab and make the following entries: Field name Trusted system SNC User action and default values No (default) Inactive (default) © SAP AG Page 27 of 62 . After having selected the system. In the next screen the system number appears. 5.

This step is only required when you are using a UNICODE system. User action and default values <SCM System>CLNT<Client>. Choose Test connection to verify that the connection to the SCM system has been established. To carry out the activity. Save your entries. 3. Confirm the information message “Caution: The table is cross-client”. choose one of the following navigation options: SAP ECC menu SAP Easy Access → Logistics → Central Functions → Supply Chain Planning Interface → Core Interface Advanced Planner and Optimizer → Settings → APO Releases NDV2 Transaction code 2. 8. Type Release 4. 10. Choose the tab MDMP & Unicode and select the Unicode flag under Comunication Type with Target System.3 Use Maintaining Systems and their Types and Releases (SAP ECC) The purpose of this activity is to specify details of your SAP SCM system for the SAP SCM Core Interface. for example “AS7CLNT001” SAP_APO Release of your SAP SCM system.1. System Syst. Procedure 1. 3. Go back.SAP Best Practices Logon Language Client User Password Building Block B02 Connectivity: Configuration Guide EN <SAP SCM target client>.1. Choose New Entries and enter the following data: Field name Log. for example “50” © SAP AG Page 28 of 62 . for example 001 RFCUSER BPLOGIN (password you have chosen in user maintenance) Current user Deselect (default) 7. Save your RFC destination 9.

1. if necessary. 5.SAP Best Practices Building Block B02 Connectivity: Configuration Guide 3.4 Use Maintaining the Target System (SAP ECC) The 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. To carry out the activity.. In the Change View “Target System. Go back. choose New Entries and enter the logical system name for your SAP SCM system (for example AS7CLNT001) and choose the queue type Outbound Queues.” screen.1. Save your entry. © SAP AG Page 29 of 62 . Operation Mode and Queue Type. A transport request for Customizing appears. 3. Select an existing request or create a new request. choose one of the following navigation options: 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 CFC1 Transaction code 2.. Procedure 1. 4.

you must have • • Defined a logical system in SAP SCM and SAP ECC. 8.SAP Best Practices Building Block B02 Connectivity: Configuration Guide 3. Select an existing request or create a new request. 4. Save your entries. In the column Name. for example KD6CLNT416 Name SAP ECC System The name of the logical system in SAP ECC can be displayed using transaction SCC4 in the SAP ECC system.1. 10. If the logical system has already been created. enter a name for the logical system that you want to create. Choose New entries.Implementation Guide → Integration with SAP Components → Integration via SAP Core Interface (CIF) → Basic Settings for Creating the System Landscape → Name Logical Systems SPRO Transaction code 2. skip this activity. open the transaction using: SAP SCM IMG menu SAP SCM . Logical systems are defined cross-client Prerequisites To enable communication between systems within your system landscape.2 3.1. 9. A transport request for Workbench appears. enter a description of the logical system. This enables the systems to recognize the target system as an RFC destination. 3.1 Use SAP SCM Defining a Logical System for SAP ECC (SAP SCM) The purpose of this activity is to create a logical system for your SAP ECC System in SAP SCM. if necessary. Assigned the logical system to the corresponding client in SAP SCM and SAP ECC. Procedure 1.2. To define the logical system for your SAP ECC System. A transport request for Customizing appears. if necessary. Log. Select an existing request or create new request. In the column Log System. © SAP AG Page 30 of 62 . System <Logical system 2>.

click on “Add and Logon”. choose Create. On the Technical Settings tab page make the following entries: Technical settings Balance Load Target host System number Save as No <SAP ECC target host name>. Make the following entries: Field name RFC destination User action and default values <SAP ECC System name>CLNT<client> for example KD6CLNT416 Connection type Description Description 4.1.2 Use Maintaining the RFC Connection to ECC (SAP SCM) Communication between the systems is based on the RFC interface. for example 74 Host name (select) SAP ECC System 3 (Connection to SAP ECC System) One option of finding the host name is to go through the SAP Logon screen. The RFC connection enables data to be exchanged between systems. Choose Enter. select Groups and enter the name of your system. To define RFC connections.SAP Best Practices Building Block B02 Connectivity: Configuration Guide 3. Move to the Logon/Security tab and make the following entries: Field name Trusted system SNC User action and default values No (default) Inactive (default) © SAP AG Page 31 of 62 . In the next screen the system number appears 6. On the Display and maintain RFC destinations screen. for example pwdf0421 <SAP ECC target system number>. Procedure 1.2. open the following transaction: SAP SCM IMG menu SAP SCM – Implementation Guide → Integration with SAP Components → Integration via SAP Core Interface (CIF) → Basic Settings for Creating the System Landscape → Set Up RFC Destination SM59 Transaction code 2. 3. The target host will appear in the field Message Server. After having selected the system. 5.

3 Use Assigning Logical System to Business System Group (SAP SCM) In this activity. Choose New entries and enter the following data: Field name BusSystGrp Logical System SAP System Indicator User action and default values <Name of Business System Group >. 10.1. 3.SAP Best Practices Logon Language Client User Password EN Building Block B02 Connectivity: Configuration Guide <SAP ECC target client>.2. for example 446 RFCUSER BPLOGIN (password you have chosen in user maintenance) Current user Deselect (default) 7. for example. In a multi-system scenario. 8. Procedure 1. Go back. 9. for example. DS7CLNT723 x © SAP AG Page 32 of 62 . Choose Test Connection to verify that the connection to the ECC system has been established. you assign the logical system of your SAP ECC to the business system group. SCM <Logical System of your SAP ECC System>. Save your entries. the logical systems of all the systems involved must be assigned to a business system group to support synchronization of master data. To assign a logical system to your business system group. open the IMG activity in SAP SCM as follows: SAP SCM IMG menu SAP 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 Transaction code SPRO 2. This step is only required when you are using a UNICODE system. Choose the tab MDMP & Unicode and select the Unicode flag under Comunication Type with Target System.

1 3. Note that this activity is carried out on your operation system (OS) level.2. Procedure 1. 3.1. enter the following data: © SAP AG Page 33 of 62 . Save your entries. the following composite roles must have already been assigned to the configuration user: • • • SAP_J2EE_ADMIN SAP_XI_ADMINISTRATOR SAP_XI_CONFIGURATOR Use The business systems use two registered programs to retrieve the information of the SLD. you register these programs in the J2EE engine of your Integration Server. In the Remote Desktop Connection screen. for example 600 Outbound Queue Strict (Terminate at Errors) Not Specified 3. In order to maintain J2EE parameters. In the following procedure we assume that the OS is a Windows system. usually a special authorization is required. In this activity.SAP Best Practices Field name SAP Release Queue Type Error Handling in Target System Role 3. Building Block B02 Connectivity: Configuration Guide User action and default values Release of corresponding system. choose Start → Program → Accessories → Communications → Remote Desktop Connection 2.1 SAP XI Maintaining the J2EE Parameters (SAP XI) Prerequisites The configuration user must have the authorization to login the integration server. From the window system. so that the connection with the business system can be established. To access the system on the OS level.2 SAP XI with SAP ICH This 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.2.

3 R © SAP AG Page 34 of 62 .. I029514 Note 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 Connect. for example. Choose OK and log o to the Integration Server 5.bat from within the directory: ./usr/sap/<systemid>/DVEBMGS<instance_number>/j2ee/admin. under the RFC destination specify the following data: Field name Program ID Description Program name R/O/C R User action and values Enter the program name LCRSAPRFC_AS7 Note The program name follows the syntax as LCRSAPRFC_<System ID> This is your Integration Server host This is the gateway service from your Integration Server Gateway Host Gateway Service Number of process Gateway host Gateway service Number of process R R Enter the gateway host.. Choose Connect. enter the following data: Field name User Description User ID R/O/C R User action and values Enter the user name. Choose Cluster → Server Services → JCo RFC Provider. for example. sapgw64 Specify the number of the process. 6. J2EE_ADMIN is defaulted from the login profile Ask your administrator and specify it here Note The user ID will be used to access setting at OS level in XI system Password Password R 7. for example. for example. Start the J2EE Engine Visual Administrator either locally by choosing J2EE Engine Administrator Shortcut or on your Integration Server by executing the file go. pwdf2268 Host name or IP address of XI system Enter the Host name or IP 3.SAP Best Practices Field name Computer Building Block B02 Connectivity: Configuration Guide Description User action and value address. pwdf2268 Enter the service. on the Log on to Window screen. for example. on the Login screen. enter the following data: Field name User Description User ID R/O/C R User action and values The user name. for example.

for example. for example. pwdf0764 Note This is your Integration Server host © SAP AG Page 35 of 62 . 10. 8. choose: Goto → Parameters → Display. you can follow the menu path in your business system: System → Status…to check the field Unicode System. sapgw64 R Number of process Number of process R Specify the number of the process. 64 Enter the client. 100 Enter the user name SAPJSF Ask your administrator and specify it here Note This is your Integration Server host This is the system number of your Integration Server R R R R Only Unicode system is supported as of XI 7. Under the Repository specify the following data: Field name Application Server Description Application server R/O/C R User action and values Enter the server name. for example. Choose Set. pwdf0764 Enter the service. Under the RFC destination specify the following data for the program SAPSLDAPI: Field name Program ID Description Program name R/O/C R User action and values Enter the program name SAPSLDAPI_AS7 Note The program name follows the syntax as SAPSLDAPI_< System ID> This is your Integration Server host This is the gateway service from your Integration Server Gateway Host Gateway Service Gateway host Gateway service R Enter the gateway host. 3 11. and search for the entries for gateway hostname and gateway service attributes. To verify whether your business system is a Unicode or Non-unicode system. pwdf2268 Enter the system number.0. for example. for example. 9.SAP Best Practices Building Block B02 Connectivity: Configuration Guide To find out the gateway host and service on your integration server host. for example. for example. Under the Repository specify the following data: Field name Application Server System number Client User Password Description Application server System number Client number User Password R/O/C R User action and values Enter the server name. call transaction SMGW.

for example. Procedure 1. enter the following data: Field name RFC Destination Connection type Description The HTTP destination Connection type R/O/C R R User action and values Enter the name. Choose Set. 12. 3. choose one of the following navigation options: SAP XI menu Transaction code SAP menu → Tools → Administration → Network → RFC Destinations SM59 2. This HTTP destination is assigned to the End Point you create later. AS7CLNT001 Choose the type H Note © SAP AG Page 36 of 62 . To carry out the activity. 13. On the Display and maintain RFC destinations screen choose Create. Quit the program.1.2 Defining HTTP Destination for Business System (SAP XI) Use In this activity you create the HTTP destination for the business system (the SAP ICH in our case). 64 Note This is the system number of your Integration Server Client User Password Client number User Password R R R Enter the client. you can follow the menu path in your business system: System → Status…to check the field Unicode System. 100 Enter the user name SAPJSF Ask your administrator and specify it here To verify whether your business system is a Unicode or Non-Unicode system. On the RFC Destination screen. for example. 3.SAP Best Practices Field name System number Building Block B02 Connectivity: Configuration Guide Description System number R/O/C R User action and values Enter the system number.2. for example.

Description Target host Service number Path prefix R/O/C R R User action and values Specify the host name. for example. SAP ICH Note 4. 001 Enter the user. EN Enter the client. for example. /sap/xi/engine/engi ne_as7_001/? type=receiver The service no. for example. If you have created an alias for your business system. PWDF0155 Specify the service number. for example. for example.1. confirm the pop-up message. On the RFC Destination <your RFC ID> screen.3 Use Defining Services and Communication Channels for SAP ICH (SAP XI) To prepare the configuration of the business scenario. for example. confirm the warning message and enter the following logon data: Field name Language Client User Password Description Logon language Client User Password R/O/C O R R R User action and values Enter the language id. Choose Save and go back. you need to add it into the prefix. for example.2.SAP Best Practices Field name Description Building Block B02 Connectivity: Configuration Guide Description Description R/O/C R User action and values Enter the description for the RFC destination. 5. is the HTTP port number. Choose Enter. Choose the Logon/Security tab. the alias engine_as7_001 is used Note PathPrefix R To find out the number of the HTTP port (service number). you must do the following: © SAP AG Page 37 of 62 . for example. XIPASS Note 7. XIAPPLUSER1 Enter the password. 6. call transaction SMICM and then choose Go to → Service in your SAP ICH and look up the port protocol =”HTTP”. 50021 Enter the prefix. enter the following data: Field name Target host Service No. For the Best Practices configuration. 3.

You must define a communication channel for all communication types that you want to use and all potential receiver systems. 5. Enter the following data on the Configuration: Integration Builder (<Your integration server>) screen: Field name User Description User ID R/O/C R User action and values Enter the logon user Note You can use your standard XI user and password Password Language Password Language R O Enter the password Choose the logon language. Procedure 1. the sequence of the fields is arranged as the sequence in the above table. With this activity. 3. The Java Web Start program is started. The SAP Exchange Infrastructure page will be opened in your default browser. 4. To carry out the activity. © SAP AG Page 38 of 62 . you define a service (business system service) for the business system (the SAP ICH in our case). choose one of the following navigation options: SAP XI menu Transaction code User menu for <you name> → Exchange Infrastructure: Integration Builder → Start Integration Builder SXMB_IFR 2. for example. English The screen can be started in German. Choose the link Integration Directory. Only then can you address the business systems as senders or receivers of messages.SAP Best Practices • • Building Block B02 Connectivity: Configuration Guide Define the involved business systems as services (business system services) in the Integration Directory. The communication channels for the involved business system are created automatically as well. Define communication channels for outbound message processing for all relevant receiver business systems.

Confirm the system prompt with Enter. If more than one change lists appears.0 XI 3. 21. 9. on the Objects tab page. expand the change lists and check which one the communication channels are assigned to. In the context menu. Choose Continue. 15. check and specify the following data: Field name Adapter Type Transport Protocol Message Protocol Adapter Engine Addressing Type HTTP Destination Description Adapter type Transport Protocol Message Protocol End point type Addressing type HTTP destination R/O/C R R R R User action and values XI HTTP 1. under Service Without Party→ Business System →<SID>CLNT<Client> → Communication Channel. 13. Make sure that the Create Communication Channels Automatically checkbox is selected. 10. Choose Save to save your data. choose Assign Business System to call the wizard for assigning business systems. In the navigation area. Choose Finish. for example.0 Make sure that the value Integration Server is selected Choose the value HTTP Destination Enter your HTTP Destination for the business system.SAP Best Practices Building Block B02 Connectivity: Configuration Guide 6. choose Continue again 11. 17. On the next screen. right click the communication channel GeneratedReceiverChannel_XI. in the Parameters tab. And on next screen. select your SAP ICH business system (for example. In the navigation area. In the navigation area. 7. leave field Party blank. On the Edit Configuration Parameters screen. 12. 16. 20. select Environment -> Clear SLD Cache to update the SLD data. In this case. 22. AS7CLNT001 Use the HTTP Destination you defined in the previous step Note R R 19. 14. position the cursor on the Service without Party node. choose Open. Read the Information Message and choose Close. AS7CLNT001) by selecting the corresponding checkboxes. the receiver communication channels for the selected business systems are created automatically. select the Change Lists tab page. In the context menu. © SAP AG Page 39 of 62 . Delete the communication channels that are not required one by one. On the Configuration: Integration Builder (<your system>) page. Choose Switch between display and edit mode to switch to change mode 18. 8.

choose one of the following navigation options: SAP menu SAP menu → Tools → Administration → Network → RFC Destinations © SAP AG Page 40 of 62 .2. Result The user role is now displayed and can be used for the following configuration activities. you must have assigned the SAP standard role SAP_XI_ADMINISTRATOR to your user or another configuration user. under Service Without Party→ Business System →<SID>CLNT<Client> → Communication Channel. which will be assigned in the role of the SAP ICH system. 3. Right click the change list with the communication channels and choose Activate in the context menu. To carry out the activity.1 Use SAP ICH Assign XI Administrator Role to Configuration User In order to do carry out the following configuration steps in SAP ICH. In the navigation area. the following communication channels are not required: • • • GeneratedReceiverChannel_HTTP GeneratedReceiverChannel_IDoc GeneratedReceiverChannel_RFC.2. 24.SAP Best Practices Building Block B02 Connectivity: Configuration Guide For the Business System SAP ICH. 26. you must first open it (double-click). Access transaction SU01 and enter the name of the user in charge of the subsequent configuration activities.2.2 3. you create an HTTP destination for your integration server (SAP XI). To delete an object in a change list. Choose menu Object → Exit to quit the program. Procedure 1. Choose Change. 2. On the Roles tab page. Procedure 1. Then choose Communication Channel → Delete in the menu bar of the object editor. 3. 25.2 Use Creating the HTTP Destination for XI (SAP ICH) In this activity. enter the role SAP_XI_ADMINISTRATOR in the Roles column and choose Save. check that the only available communication channel is GeneratedReceiverChannel_XI. Log off and log on again. 3.2. Go back to the Objects tab.2. 23.

for example. 50064 Enter the prefix. ignore it. XI HUB Note 4. choose Create. To find out the number of the HTTP port (service number). XIAPPLUSER Enter the password. On the RFC Destination screen. 5. for example. Choose Save and go back. EN Enter the client. PWDF2268 Specify the service number. for example. PathPrefix Description Target host Service number Path in the HTTP service tree of the SAP Web AS R/O/C R R R User action and values Specify the host name. for example. 3. XIBCLNT100 Choose the type H Enter the description for the RFC destination. 100 Enter the user.SAP Best Practices Transaction code Building Block B02 Connectivity: Configuration Guide SM59 2. 3. for example.2. call transaction SMICM and then choose Goto → Service in your Integration Server (SAP XI). 6. enter the following data: Field name Target host Service No. for example.3 Use © SAP AG Defining System Role for ICH (SAP ICH) Page 41 of 62 . If the system displays the Query String Not Allowed message. for example. for example. Choose the Logon/Security tab. /sap/xi/engine/?type=entry Note 1. confirm the warning message and enter the following logon data: Field name Language Client User Password Description Logon language Client User Password R/O/C O R R R User action and values Enter the language id. Choose Enter to confirm the op-up message. enter the following data: Field name RFC Destination Connection type Description Description The HTTP destination Connection type Description R/O/C R R R User action and values Enter the name. for example. 2. XIPASS Note 7. On the RFC Destination <your RFC ID> screen. On the Display and maintain RFC destinations screen.2.

the syntax used above is more secure than the explicit URL. choose one of the following navigation options: SAP Menu Transaction code User menu for <you name> → Exchange Infrastructure Environment → HTTP Service Hierarchy Maintenance SICF © SAP AG Page 42 of 62 . After every change you have to activate them again. On the same screen. and forwarding) to and from the central integration server. Procedure 1.4 Use Activating HTTP Service (SAP ICH) For the Integration Engine to be able to receive XML messages using HTTP.Administration SXMB_ADM 2. 3. Choose Save and go back. It controls the messaging process (receiving. On the Integration Engine: Administration screen choose Integration Engine Configuration and then. for example. The HTTP services are deactivated by default. Procedure 1. choose Execute Function. 5. processing. On the Integration Engine Configuration Data screen. you have to activate an HTTP service.2. The Integration Engine is the runtime environment of the exchange infrastructure. dest://XIBCLNT100 Be careful of the syntax of the HTTP destination Note Name of the integration server R You can also directly maintain the HTTP address of the Integration Server.SAP Best Practices Building Block B02 Connectivity: Configuration Guide 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. enter the following data: Field name Role of Business System Correspondin g Integ. To carry out the activity. 3. To carry out the activity. 4. choose one of the following navigation options: SAP menu Transaction code User menu for <you name> → Exchange Infrastructure: Administration → Integration Engine . choose menu path Edit → Change Global Configuration Data. However.2. Server Description System role R/O/C R User action and values Choose the role Application System Enter the HTTP destination of the integration server.

4.SAP Best Practices Building Block B02 Connectivity: Configuration Guide 2.2. for example. Select engine. Confirm the warning pop up “Do you really want to save?” 10. Select the alias you just created. right click on the node and choose Activate Link to activate it from the context menu. choose one of the following navigation options: SAP Menu Transaction code User menu for <you name> → Exchange Infrastructure: Administration → Integration Engine . Choose the Alias Trgt tab page and go to default_host → sap → xi → engine. 12. 3.2. Double click on the engine and choose Save. Confirm the message for the namespace with Enter. engine_as7_001 Choose the type Reference to an existing service Note Service type R 7. Choose Back to quit the transaction. Choose Input (Enter) and enter the following data: Field name Description Description Description R/O/C O User action and values Enter the description of the service.Administration SXMB_ADM © SAP AG Page 43 of 62 . To carry out the activity. 9. 13. 11. On the Create a Service Element screen. ICH service Note 8. Right click on the engine node and choose Activate Service from the context menu. Procedure 1. and choose Create Host/Service. for example.5 Use Registering Queues (SAP ICH) In this activity you register the queues used by the Integration Engine. $TMP. for example. Assign a proper package name. On the Maintain service screen go to default_host → sap → xi → engine 3. enter the following data: Field name Name of service element to be created: Type of Service Node To Be Created: Description Service name R/O/C R User action and values Enter the new name. Choose Cancel and go back to the Maintain service screen. 6. 5.

© SAP AG Page 44 of 62 . 4. On the Integration Engine: Administration screen choose Manage Queues 3.SAP Best Practices Building Block B02 Connectivity: Configuration Guide 2. On the Manage Queues screen. 5. You will see the message Registration Complete on the status bar. keep the default values and choose Register Queues. Choose Back to quit the transaction.

you can choose Browser tab on the same page. the data consists of the host and port of the SLD as well as a user and password (XIAPPLUSER and XIPASS). choose one of the following navigation options: SAP Menu Transaction code User menu for <you name> → Exchange Infrastructure: Administration → SLD API Customizing SLDAPICUST 2. choose Server tab. On the Maintain SLD Access Data screen choose Display <-> Change and enter the following data: Field name Alias Prim. Choose Save and go back. To find the port number for the SLD. for example.2.6 Use Maintaining HTTP Address of SLD Server (SAP ICH) Business systems with an Integration Engine require a connection to the SLD server to obtain their name from the SLD. for example. Host Name Port User Password Description Alias Primary SLD Host name Port number of the SLD User id Password R/O/C O R R R R R User action and values Enter the alias. 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. Procedure 1. for example. use the port number after the host name. for example. for example. pwdf2268 Enter the port number.2. To carry out the activity. 56400 Enter the user. In this activity you define the SLD access data in your business system. Host: pwdf2268:56400. To find this host name.SAP Best Practices Building Block B02 Connectivity: Configuration Guide 3. for example. XIPASS Note x The host name here must be identical to the name you maintain in the SLD. 3. XIAPPLUSER Choose the button and enter the password. © SAP AG Page 45 of 62 . XIB_100 Mark this checkbox Enter the host 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> Note R CPI-C Timeout Gateway host Gateway service Default Gateway Value Gateway server Gateway service R Mark this checkbox R R Specify the host name. for example. To carry out the activity. Prerequisites You have registered the programs in the J2EE engine of your Integration Server. which are used for the SLD connection. choose Create. sapgw64 © SAP AG Page 46 of 62 . for example. enter the following data: Field name RFC Destination Connection type Description R/O/C R R R User action and values Enter the name LCRSAPRFC Choose the type T Enter the description for the RFC destination. for example. On the Display and maintain RFC destinations screen. choose Technical Settings tab and enter the following data: Field name Activation type Program ID Description Activation type Program name R/O/C R User action and values Choose the type Registered Server Program Enter the program name.SAP Best Practices Building Block B02 Connectivity: Configuration Guide 3. On the RFC Destination screen. On the RFC Destination <your RFC ID> screen. Procedure 11.2. 13. pwdf2268 Enter the gateway service.2. choose one of the following navigation options: SAP Menu Transaction code SAP menu → Tools → Administration → Network → RFC Destinations SM59 12. SLD Connection LCRSAPRFC Note This is a fixed name 14.7 Use Creating SLD Connection to XI (SAP ICH) In this activity you create the RFC destinations LCRSAPRFC and SAPSLDAPI. Choose Enter. 15.

18. 16. for example. call the transaction SMGW and choose Goto → Parameters → Display in your Integration Server (SAP XI). Repeat the step 3 to step 6 to create the RFC destination for the program SAPSLDAPI. using the following data: Field name RFC Destination Connection type Description Description The RFC destination Connection type Description R/O/C R R R User action and values Enter the name SAPSLDAPI Choose the type T Enter the description for the RFC destination. Choose Save.SAP Best Practices Building Block B02 Connectivity: Configuration Guide To find out the value of the gateway host and service. This step is only required when you are using a UNICODE system. Choose the tab MDMP & Unicode and select the Unicode flag under Comunication Type with Target System. © SAP AG Page 47 of 62 . for example. search the entries for the gateway hostname and gateway service attributes. SLD Connection SAPSLDAPI Choose the type Registered Server Program Enter the program name. for example. it uses the syntax SAPSLDAPI_<System ID> Note This is a fixed name Activation type Program ID Activation type Program name R R CPI-C Timeout Gateway host Gateway service Default Gateway Value Gateway server Gateway service R Mark this checkbox R R Specify the host name. sapgw64 19. 17. for example. pwdf2268 Enter the gateway service. Choose Save and go back. SAPSLDAPI_AS7 This is the program id you register in the J2EE engine of your Integration Server.

© SAP AG Page 48 of 62 .SAP Best Practices Building Block B02 Connectivity: Configuration Guide 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.

3. On the RFC Destination screen. for example. for example. enter the following data: Field name Target host System number. On the RFC Destination <your RFC ID> screen. for example. 5. for example.3. for example. Description Target host System number R/O/C R R User action and values Specify the host name. To carry out the activity. 19 Note 6. you create a RFC Destination from your Integration Server to the SAP ECC system.3. KD6CLNT416 Choose the type 3 Enter the description for the RFC destination. Choose the Logon/Security tab and enter the following logon data: Field name Language Client Description Logon language Client R/O/C O R User action and values Enter the language id.1 3.1. Choose Enter. EN Enter the client. SAP XI Creating the RFC Destination (SAP XI) Procedure 1. enter the following data: Field name RFC Destination Connection type Description Description The RFC destination Connection type Description R/O/C R R R User action and values Enter the name.3 SAP XI with SAP ECC 3. for example. Automotive OEM Note 4. ld0059 Specify the system number. 416 Note © SAP AG Page 49 of 62 .SAP Best Practices Building Block B02 Connectivity: Configuration Guide 3.1 Use In this activity. choose one of the following navigation options: SAP XI IMG menu SAP Customizing Implementation Guide  SAP NetWeaver  SAP Web Application Server  IDoc Interface/Application Link Enabling (ALE)  Communication → Create RFC Connections SM59 Transaction code 2. On the Display and maintain RFC destinations screen choose Create.

for example. for example. for example. KD6CLNT416 This the SAP ECC system which sends the IDoc into the Integration Server Note Using SAP+<your system name> © SAP AG Page 50 of 62 . This step is only required when you are using a UNICODE system. for example. 3.1. Procedure 1. choose one of the following navigation options: SAP XI IMG menu Transaction code User menu for <your name> → Exchange Infrastructure: Configuration → Port Maintenance in IDoc Adapter IDX1 2. Choose Save and go back. 8. which sends the IDoc to the Integration Server.2 Use Assigning Port for SAP ECC (SAP XI) In this activity you assign an IDoc Adapter Port (RFC Destination) to the SAP ECC system.SAP Best Practices Field name User Description User Building Block B02 Connectivity: Configuration Guide R/O/C R User action and values Enter the user. KD6CLNT416 Choose the RFC destination. RFCUSER Note Make sure that the user id is identical to that already created in your ECC system Make sure that the password is identical to that in your ECC system Password Password R Enter the password. Choose the tab MDMP & Unicode and select the Unicode flag under Comunication Type with Target System.3. 416 Enter the description. for example. Enter the following data on the right side of the screen: Field name Port Client Description RFC Destination Description Port Client Description RFC destination R/O/C R R R R User action and values Enter the port name. for example. On the Port Maintenance in IDoc Adapter screen choose Create. 3. SAPKD6 Enter the client number. BPLOGIN 7. To carry out the activity.

Go back. Choose Save to save your entries. 5. © SAP AG Page 51 of 62 .SAP Best Practices Building Block B02 Connectivity: Configuration Guide 4.

choose one of the following navigation options: SAP XI IMG menu Transaction code User menu for <your name> → Exchange Infrastructure: Configuration → Meta Data Display in IDoc Adapter IDX2 2. for example. Repeat the step 3 to step 4 and with the following data: Field name IDoc Type R/O/C R User action and values Enter the IDoc type. SAPKD6 This is the port you assigned to the IDoc Adaptor Note 7. SAPKD6 This is the port you assigned to the IDoc Adaptor Note 8. for example. for example.3. PROACT01 Enter the port number. SAPKD6 This is the port you assigned to the IDoc Adaptor Note 4. enter the following data: Field name IDoc Type Source Port R/O/C R R User action and values Enter the IDoc type. Repeat the step 3 to step 4 and with the following data: Field name IDoc Type Source Port R/O/C R R User action and values Enter the IDoc type. ORDERS05 Enter the port number.3 Use Loading IDoc Meta Data (SAP XI) In this activity. for example. 5. ORDERS03 Note © SAP AG Page 52 of 62 . for example. To carry out the activity. On the Reload a type description screen. Procedure 1. Repeat the step 3 to step 4 and with the following data: Field name IDoc Type Source Port R/O/C R R User action and values Enter the IDoc type. DELVRY03 Enter the port number. Choose Continue to load the data. DELFOR01 Enter the port number. for example. for example. Repeat the step 3 to step 4 and with the following data: Field name IDoc Type Source Port R/O/C R R User action and values Enter the IDoc type. 3. for example. for example.SAP Best Practices Building Block B02 Connectivity: Configuration Guide 3. SAPKD6 This is the port you assigned to the IDoc Adaptor Note 6. you load the Meta Data of the relevant IDoc types from your ECC system into the integration server.1. On the Metadata Overview for IDoc Adapter screen choose Create.

DELFOR02 Enter the port number. SAPKD6 This is the port you assigned to the IDoc Adaptor Note 11. SAPKD6 Note This is the port you assigned to the IDoc Adaptor 9. Repeat the step 3 to step 4 and with the following data: Field name IDoc Type Source Port 13. SAPKD6 This is the port you assigned to the IDoc Adaptor Note © SAP AG Page 53 of 62 . for example. PORDCR102 Enter the port number. for example. SAPKD6 This is the port you assigned to the IDoc Adaptor Note 12. Go back. for example.SAP Best Practices Field name Source Port R/O/C R Building Block B02 Connectivity: Configuration Guide User action and values Enter the port number. R/O/C R R User action and values Enter the IDoc type. Repeat the step 3 to step 4 and with the following data: Field name IDoc Type Source Port R/O/C R R User action and values Enter the IDoc type. DELVRY05 Enter the port number. Repeat the step 3 to step 4 and with the following data: Field name IDoc Type Source Port R/O/C R R User action and values Enter the IDoc type. for example. for example. PORDCH02 Enter the port number. SAPKD6 This is the port you assigned to the IDoc Adaptor Note 10. for example. Repeat the step 3 to step 4 and with the following data: Field name IDoc Type Source Port R/O/C R R User action and values Enter the IDoc type. for example. for example. for example.

choose Continue again 11. 7. 6. Choose Continue. Read the Information Message and choose Close. Choose Finish 14. on the Objects tab page. In the context menu. leave field Party blank.SAP Best Practices Building Block B02 Connectivity: Configuration Guide 3. Choose the link Integration Directory. 3. please be noticed that the sequence of the fields is arranged as the sequence in the above table.3. In the navigation area. 9. you define a service (business system service) for the business system (the SAP ECC in our case). 13. 5. choose one of the following navigation options: SAP XI menu Transaction code User menu for <you name> → Exchange Infrastructure: Integration Builder → Start Integration Builder SXMB_IFR The SAP Exchange Infrastructure page is opened in your default browser. In this case. for example. KD6CLNT416) by using the corresponding checkboxes. Enter the following data on the Configuration: Integration Builder: (<Your integration server>) screen: Field name User Password Language Description User ID Password Language R/O/C R R O User action and values Enter the logon user Enter the password Choose the logon language. On the Configuration: Integration Builder (<your system>) page. © SAP AG Page 54 of 62 .4 Use Defining Services and Communication Channels for SAP ECC (SAP XI) In this activity. 4. 10. Procedure 1. position the cursor on the Service without Party node. English Note Ask the administrator for the user id and password The screen might be started in German. The communication channels for the involved business system are created automatically as well. select Environment  Clear SLD Cache to update the SLD data. On next screen. 2. 12. select your SAP ECC business system (for example. On the next screen.1. choose Assign Business System to call the wizard for assigning business systems. the receiver communication channels for the selected business systems are created automatically. in this case. Confirm the pop-up window with Enter. Make sure that the Create Communication Channels Automatically checkbox is selected. The Java Web Start program is started. 8. To carry out the activity.

in the Parameters tab.0 or Higher Enter the port. expand the change lists and check which lists the communication channels are assigned to. KD6CLNT416 Choose the version of your ECC system. SAP Release 4. If more than one change lists appears. 16. select the Change Lists tab page. On the Edit Configuration Parameters screen. right click the communication channel GeneratedReceiverChannel_IDoc. In the navigation area. In the context menu. 22. check and specify the following data: Field name Adapter Type Transport Protocol Message Protocol Adapter Engine RFC destination Interface Version Port R/O/C R R R R R User action and values IDoc IDoc IDoc Integration Server Enter the RFC destination for your ECC system. 17. Choose Switch between display and edit mode to switch to change mode 18. GeneratedReceiverChannel_XI and GeneratedReceiverChannel_RFC are not required. Choose Save to save your data. choose Open. Delete the communication channels that are not required one by one. 20. For the Business System SAP ECC. for example. SAPKD6 Note R R 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. under Service Without Party→ Business System →<SID>CLNT<Client> → Communication Channel. for example. 21. © SAP AG Page 55 of 62 . 700 19. for example.SAP Best Practices Building Block B02 Connectivity: Configuration Guide 15. for example. In the navigation area. the Communication Channels GeneratedReceiverChannel_HTTP.

24. In the navigation area. Go back to the Objects tab. 23. Right click the change list with the communication channels and choose Activate in the context menu. under Service Without Party→ Business System →<SID>CLNT<Client> → Communication Channel. Then choose Communication Channel → Delete in the menu bar of the object editor. 26. © SAP AG Page 56 of 62 . Choose menu Object → Exit to quit the program. you must first open it (double-click). check that only the communication channel GeneratedReceiverChannel_IDoc is available. 25.SAP Best Practices Building Block B02 Connectivity: Configuration Guide To delete an object in a change list.

2 3. for example. for example. for example. Description Target host System number R/O/C R R User action and values Specify the host name. for example. XIBCLNT100 Choose the type 3 Enter the description for the RFC destination. EN Enter the client.3. Choose the Logon/Security tab and enter the following logon data: Field name Language Client User Password Description Logon language Client User Password R/O/C O R R R User action and values Enter the language id. enter the following data: Field name RFC Destination Connection type Description R/O/C R User action and values Enter the name. On the Display and maintain RFC destinations screen choose Create. To carry out the activity.SAP Best Practices Building Block B02 Connectivity: Configuration Guide 3. 5. XI Hub Note Ensure the name is identical to the name of the logical system created in the previous step R R 4. for example. Procedure 1. for example. for example. XIPASS Note © SAP AG Page 57 of 62 . On the RFC Destination <your RFC ID> screen. 64 Note 6. for example. XIAPPLUSER1 Enter the password. you create a RFC Destination from your SAP ECC system to the Integration Server. On the RFC Destination screen. 3.1 Use SAP ECC Creating the RFC Destination (SAP ECC) In this activity.3. PWDF2268 Specify the system number. Choose Enter.2. enter the following data: Field name Target host System number. 100 Enter the user. choose one of the following navigation options: 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 SM59 Transaction code 2.

SAP Best Practices Building Block B02 Connectivity: Configuration Guide 7. Choose the tab MDMP & Unicode and select the Unicode flag under Comunication Type with Target System. 8. This step is only required when you are using a UNICODE system. Choose Save and go back © SAP AG Page 58 of 62 .

SAP CRM or SAP SRM system source RFCUSER LOGIN RFCUSER (can not be changed in this activity) LOGIN RSA1 Password for source system Background user in BW Password for BW user 9. Log on to the Source System with your administrator user.0E (Automatic Creation). 7. Make the following entries: Field Target computer (server) System ID System number Background system user in Entry Server of the SAP ECC. SAP CRM or SAP SRM system System number of the SAP ECC. 10.4 Connecting SAP BW with SAP ECC. Choose Create. © SAP AG Page 59 of 62 . Choose Source systems. Choose Modeling. 4. SAP CRM. 8. If you receive the error “No entry for BW_User in table RSADMIN”. 5. Choose the correct client. 6. SAP SRM Procedure 1. On the dialog box New Source System Connection choose Continue. 3. To carry out the activity. Choose the Context menu (right mouse click). SAP CRM or Sap SRM system System ID of the SAP ECC. choose one of the following navigation options in the SAP BW system: Transaction code 2. Select SAP System from Release 3.SAP Best Practices Building Block B02 Connectivity: Configuration Guide 3. 11. On the Replicate Metadata dialog box. refer to SAP note 410952. choose Only Activate. On the dialog box Please log on as an administrator in the following screen choose Continue. Select Source systems in the window on the right. 12.

© SAP AG Page 60 of 62 . On the dialog box. Select SAP Business Information Warehouse.1 Connecting SAP SCM to the SAP BW system (SAP BW) Procedure 1. select the relevant items in the substructure. Choose Create. 4. choose one of the following navigation options in the SAP BW system: Transaction code 2. choose Continue. 7. Choose the Context menu (right mouse click). Make the following entries: Field Target computer (server) System ID System number Background system user in Entry Server of the SAP SCM system System ID of the SAP SCM system System number of the SAP SCM system source RFCUSER BPLOGIN RFCUSER (can not be changed in this activity) BPLOGIN RSA1 Password for source system Background user in BW Password for BW user 9. 11. 5. Choose Source systems.5. Select Source systems in the window on the right. 8. In the New Source System Connection dialog box. In the following screen choose Continue. log on as an administrator. choose Only Activate.SAP Best Practices Building Block B02 Connectivity: Configuration Guide 3. 13. Choose Modeling. 6. In the Replicate Metadata dialog box. Log on to the source system with your administrator user. 12. 3. 3. To carry out the activity. 10.5 SAP SCM with SAP BW For information on this section. Choose the correct client.

Carry out the activity in the SAP SCM system. Select Source systems in the window on the right. Log on to the source system with your administrator user. Select SAP Business Information Warehouse. 10. Transaction code 2. 5. 11. On the Check RFC destination dialog box. Choose the correct client.SAP Best Practices Building Block B02 Connectivity: Configuration Guide 3. Choose Source systems.2 Connecting SAP BW to the SAP SCM system (SAP SCM) Procedure 1. Choose Modeling. 6. Choose Create. On the dialog box Please log on as an administrator in the following screen. 7. Choose the Context menu (right mouse click). © SAP AG Page 61 of 62 . 8. Make the following entries: Field Available destination Background system user in Entry Destination of your SAP BW system source RFCUSER BPLOGIN RFCUSER (can not be changed in this activity) BPLOGIN RSA1 Password for source system Background user in BW Password for BW user 9. 3. 4. choose Continue.5. choose Use.

User action and values for example. EXCEL for example.6 Connecting SAP BW to a File System (SAP BW) Procedure SA BW menu From the SAP Menu in the BW system. 2. Choose Modeling. select Source Systems and right-click on it to display the context menu.. Manual Meta Data. 3. In the right screen area. Choose Back. Field name File System. Data Using File.SAP Best Practices Building Block B02 Connectivity: Configuration Guide 3. 7. Choose Enter. Excel File User action and values X RSA1 © SAP AG Page 62 of 62 . Field name Logical source system Source system name 6. 5.. choose: BW-Administration  Administrator Workbench Transaction code 1. Choose Enter. 4. Choose Create. Choose Source Systems.