How to configure SAP XI/PI to use the standard SAP communication APIs (Idoc, Bapi, Rfc, Enterprise Services) from

external systems
How to create the necessary certifiable XI Content with the XI Integration Builder
SAP Integration & Certification Center, icc@sap.com Updated version for XI/PI 7.0 February 2009

Contents
1 2 3 4 5 6 7 8 9 10 11 12 Introduction ..................................................................................................................2 First steps......................................................................................................................2 Add your system into the System Landscape Directory .................................................4 Establish the connection between the SAP systems .......................................................6 Transfer your Software Component into the Integration Repository ..............................7 XI Content for asynchronous IDOC Outbound..............................................................8 XI Content for asynchronous IDOC Inbound .............................................................. 18 XI Content for synchronous RFC/BAPI Inbound ........................................................ 27 XI Content for synchronous RFC/BAPI Outbound...................................................... 37 XI Content to invoke Web Services / SAP Enterprise Services.................................... 47 How to import/configure your XI Content in a target XI system.................................. 58 Files needed for Certification ...................................................................................... 59

How to configure SAP XI/PI to use the standard SAP communication APIs (idoc, bapi, rfc, ES) from external systems ____________________________________________________________________________________________

1 Introduction
Purpose of this document This document describes how the SAP Exchange Infrastructure (XI/PI) 3.0 or 7.0 can be configured, so that external systems can communicate with a backend SAP system (e.g. SAP R/3 Enterprise) using the standard SAP XI adapter “HTTP” with XML communication. On the other side, the integration of XI with the backend SAP system is done with IDOCs or RFC modules (BAPIs). You could also integrate with the latest SAP systems using SAP Enterprise Services (see chapter 10). Throughout the document we will always use the term “XI”.

SAP Backend System

RFC

Rfc Adapter

SAP XI
http Adapter

http/ XML

3rd party system

IDOC

Idoc adapter

The configuration of XI will lead to certifiable XI Content, that can be extracted and again imported into the customers XI system. Related Documents A lot of help can be found in the Online Help of SAP: http://help.sap.com/ Documentation SAP NetWeaver Process Integration SAP Exchange Infrastructure. You should at least read the basics of XI provided there (Overview Basics). You can also find some sample scenarios using XI (Overview Demo Examples).

Certification Requirements It’s possible to certify an integration scenario with an SAP backend system using XI. To do that it’s necessary that the 3rd party system integrates with XI via one of the standard SAP adapters or a certified 3rd party adapter. XI Content Certification This tutorial lists all the steps that are necessary to get certifiable XI Content. But sure, you should also check the NW-XI-CNT certification test catalog. Please ask your local ICC to get further details about this (icc@sap.com or icc-americas@sap.com) or check the ICC SDN page (http://www.sdn.sap.com/irj/sdn/icc):

2 First steps
This tutorial is designed for the test environment provided by the SAP Integration and Certification Center (ICC). It consists of the SAP XI 7.0 system NX7 and the SAP R/3 enterprise backend system CE8. To include other XI systems or SAP backend systems further configuration might be necessary. You can get access to this test environment through our Remote Access Kit (RAC). For more information regarding RAC you should contact your local ICC or check the here: http://www.sdn.sap.com/irj/sdn/saprac The XI system is hosted on pwdf6425.dmzwdf.sap.corp, the internet address is iccpi7.sap.com. To use the XI system you need to install Java WebStart on your PC. You can get this as part of the J2SE platform provided by SUN. After the installation you should start Java WebStart manually and configure it correctly, so that it can access the internet (also check chapter 2.1). You should be able to execute the sample applications located on http://java.sun.com/products/javawebstart/apps/remoteApps.html.

2/59

How to configure SAP XI/PI to use the standard SAP communication APIs (idoc, bapi, rfc, ES) from external systems ____________________________________________________________________________________________

Now start the XI system NX7 and log on. After the logon, you should activate the user menu (ctrl-F10) to find all the necessary programs to configure, use and monitor the XI system. As a first check you should start the Integration Builder (“Start Integration Builder” or choose the following link: http://iccpi7.sap.com/rep/start/index.jsp) that opens in a separate browser window. Please check, if you can start all the four tools IntegrationRepository, IntegrationDirectory, SystemLandscapeDirectory and RuntimeWorkbench. The two Integration tools are based on Java WebStart and perhaps you have to start them several times before all the necessary classes are loaded completely into the WebStart-cache (see following chapter).

2.1

Connecting to NX7 system through a proxy server

The Integration Builder of the NX7 system can be reached directly from a web browser. If you need a proxy server for your internet connection, you should configure your browser accordingly. Also the Java Web Start tool must be configured. You can use the Java Web Start Preferences panel to view or edit the proxy configuration. Launch the Application Manager, either by clicking on the icon on the desktop (Microsoft Windows), or type ./javaws in the Java Web Start installation directory, and then select Edit/Preferences. If you are in an environment where access to the Web is through a proxy server, you are encouraged to use the Java Web Start Preferences panel to check that these are set-up correctly. The first time you start the two XI Web Start Applications (Integration Repository or Integration Directory), the necessary classes are loaded from iccxi.sap.com into the Java Web Start Cache. Especially if you have to connect through a proxy server, this can take quite long. To avoid any authentication problems, you should also add the following line to your hosts file (on windows platforms: \windows\system32\drivers\etc\hosts): 155.56.49.19 pwdf6425 pwdf6425.dmzwdf.sap.corp iccpi7.sap.com

Now everything should be in place to start all the applications contained in the SAP XI Integration Builder.

2.2

Prerequisites if you want to do IDOC communication

For IDOC communication you also need ALE customizing in the SAP Backend System, and the description of this customizing is not part of this tutorial. ALE communication with IDOCs is implemented as communication between Logical Systems. In the following chapters, we assume that we have the following Logical Systems defined in the SAP Backend System “CE8”: Central Logical System of CE8, client 850: CE8CLNT850 Logical System created for the external system: CC_CRM

3/59

How to configure SAP XI/PI to use the standard SAP communication APIs (idoc, bapi, rfc, ES) from external systems ____________________________________________________________________________________________

3 Add your system into the System Landscape Directory
All our XI configuration objects will be created in the range of the external product that consists of one or more Software Component Versions. At first we need to add information about this 3rd party product into the System Landscape Directory (SLD). The name of the external business system will be CC_CRM.

IMPORTANT NOTE: Please neither use the sample objects mentioned below in your scenario, nor change the sample Integration Scenarios or Configuration Scenarios. Always create your own objects!! Additionally, most of the sample objects here have the prefix “CC”. This is just ICC related and does not reflect a special naming convention. You don’t have to use the same prefix

Now open the SLD. Edit the Software Catalog: In section “Software Catalog”, choose ”Products“ Click “New Product Version Enter the appropriate data into the three fields Vendor: e.g. ccvendor.com Name: e.g. ccCRM Version: e.g. 1.0 Then enter Software Unit name ccCRM. Now add a Software Component Name: e.g. CCVENDOR_CRM Version: e.g. 1.0 Click “Home” to go back The above information is part of your XI Content and must be named in the same way for all your customers. Therefore you have to export it from the SLD and provide this exported file for your customers to import into their SLD. To export, go to section “Software Catalog” / “Products” again, search your product from the list and select it, then simply press the “Export”-button. This exports the Product and all attached Software Components into one single zip-file. This zip-file is part of the XI content package and is required to submit for the certification. The information for Product, Product Version, Software Component and Software Component Version are also important for the PPMS data sheet and will be entered into SAP’s internal PPMS system. Please find further details about that in the XI Content certification catalog, chapter 4.

4/59

How to configure SAP XI/PI to use the standard SAP communication APIs (idoc, bapi, rfc, ES) from external systems ____________________________________________________________________________________________

Now create the “Technical System” and the “Business System”; these are customer specific and therefore not part of the static XI Content.

Create Technical System: Click on “Technical Systems”, then choose “New Technical System” Choose “Third Party”, press “Next” Enter some sample details System: e.g. ccCRM_system Host: your host name, e.g. P105077 Now choose the product created in the step before, e.g. ccCRM and the attached Software Components, and press “Finish”. Click “Home” to go back

Create Business System CC_CRM: Click on “Business Systems”, then choose “New Business System” Choose “Third Party”, press “Next” Choose the technical system created in the step before, e.g. ccCRM_system For IDOC communication, we should enter the Logical System as defined in the SAP Backend System for the external system, so in our sample it’s CC_CRM. Enter the name “CC_CRM”, then press “Next” two times Choose Integration Server “SAP_NX7_800” Click “Finish”, then “Home” to go back

Check the available Business Systems: Click on “Business Systems”. Now you should be able to find the two Business Systems necessary for our communication scenario: The SAP backend system SAP_CE8 Your external system CC_CRM

5/59

and with transaction SM59. Then you have to log on to NX7.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. create a port named as the Logical System Name of your ALE customizing in the CE8 system. create a new RFC destination that points to the XI system: RFC destination: Connection type: Documentation: Target Host: System Number: CC_DEST_NX7 3 My Destination PWDF6425 (will then be automatically replaced by something) 10 Change to the Logon Tab and provide your logon details for the XI system. so we need a connection between the two systems: 4. ES) from external systems ____________________________________________________________________________________________ 4 Establish the connection between the SAP systems In the following chapters we want to send messages from the CE8 to XI and vice versa. 4. Don’t change this port. bapi. Integration Server. So check that the following port is available. In our case. rfc. The port name must be SAP<ID_of_SAP_backend_system>. Both should be successful. you also don’t need an additional port! Port: SAPCE8 Client: 850 RFC Destination: CC_DEST_CE8 6/59 . if you want to make IDOC communication. Check R/3 destination: With transaction SM59. you can find an ABAP destination CC_DEST_CE8 that connects to the CE8 system. Create port: With transaction IDX1. Try the connection and try the remote logon. It’s not necessary to change that or create a new R/3 destination. Port: CC_CRM Client: 850 Description: A valuable Text RFC Destination: CC_DEST_CE8 Check port: NX7 also needs one port to query IDOC metadata from the sending SAP system CE8.2 Connect the XI system NX7 with the CE8 system You only need to make changes here. this name is CC_CRM.1 Connect the CE8 system with the XI system NX7 Create R/3 destination in CE8: Log on to CE8 system.

0 of ccvendor.com. So now open the Integration Builder. from there jump into the Integration Repository. together with a meaningful namespace. Now you should find new objects under your Software Component Version. bapi. then doubleclick the Software Component Version CCVENDOR_CRM. 1. Choose “Import of RFC … permitted” and enter the system details: o o System: Client: CE8 850 “Transfer from Go into the first line of the “Namespaces”-section and enter a namespace for your Integration Scenario: http://ccvendor.) belong to an Integration Scenario that lies in your Software Component Version created previously in the SLD. This Software Component must be created first in the Integration Repository. 7/59 . Use the first icon to switch into the “change”-mode. rightclick on your change list and choose “Activate”. Choose your Software Component Version created in 3: CCVENDOR_CRM Click “Import”.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc.com/xi/crm_demo Save. Import your product from SLD: In the Integration Repository Menu. ES) from external systems ____________________________________________________________________________________________ 5 Transfer your Software Component into the Integration Repository All the static XI configuration objects (message definitions. Now jump to the chapter that is relevant for you (6. So before you leave. 8 or 9) and finish the XI Content Development. you should make sure to jump to the “Change Lists”-Tab. rfc. then exit Add the Namespace: Open the Software Component. mappings etc. 7. Important: Every change in the Integration Repository must be committed in a second step. choose “Tools” System Landscape Directory” “Import Software Component Versions”.

then “Continue”. We also don’t need any mapping. Import MATMAS01 message data: Since the external system already understands the MATMAS01 message format. rfc. bapi. 6. The scenario is as follows: Outbound MATMAS01: CE8CLNT850 CC_CRM Into the port of your ALE customizing you have to enter the R/3 destination to the SAP XI system created in 4. Open your Software Component Version CCVENDOR_CRM. from there jump into the Integration Repository. You can find the complete configuration in our XI system.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. We only focus on the XI customizing. 1. we only need to import one message type into the XI system. not the ALE customizing in the CE8. 8/59 .2 Create the Repository Content for the IDOC Outbound Scenario Open the Integration Builder. Important: Every change in the Integration Repository must be committed in a second step. As a prerequisite you should have completed chapters 3-5. in our case it’s MATMAS. ES) from external systems ____________________________________________________________________________________________ 6 XI Content for asynchronous IDOC Outbound In the following chapter we will configure the XI system. 6. prepare the ALE customizing so that MATMAS01-IDOCs can be sent to the logical system CC_CRM. then “Close” after the successful import. In our case this is CE8CLNT850.com “Imported Objects” Rightclick on “IDOCs” and choose “Import” Enter data: Application Server: cpce801 System Number: 75 your CE8-user and password Choose the IDOCs you want to import. so that we can send MATMAS01 IDOCs from the CE8 system through XI to the external system CC_CRM using the SAP tRFC communication protocol.0 of ccvendor. We can import the message type into our Software Component Version. so it should be easy to copy it using different external systems and IDOCs. So before you leave.1. You also need to know the central logical system of the client (the sender system). This name must match with the logical system name of the external Business System created in chapter 3. you should make sure to jump to the “Change Lists”-Tab.1 Check the customizing in the SAP backend system Prepare ALE customizing: In the CE8 system. Choose “Finish”.MATMAS01. rightclick on your change list and choose “Activate”.

Since we already know. bapi. rfc. Press here to add documentation 1. Choose “Adapter Type” = “HTTP” by using the F4-Help-icon. ES) from external systems ____________________________________________________________________________________________ Create Communication Channel Templates: The communication channels serve as the technical endpoints to the connected systems. we can create the templates for these endpoints now. Save. choose “New” Enter a name for the external http receiver: idoc_outbound_HTTPreceiver and enter a meaningful description. that the SAP sender is connected via IDOC and the receiving external system is connected via http. Press here to show the documentation panel 9/59 . we only need a receiver communication channel: Open your namespace “Adapter Objects” and rightclick on “Comm Channel Templates”. you should always add a meaningful text in the field “Description” and also provide some further documentation. the details of the connection are usually defined later during the configuration and are therefore not part of the static XI Content. save. This makes the configuration of the integration scenario later easier.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. by clicking on in the menu of the XI Content object: 2. For IDOC outbound. then choose “Receiver”-type. That’s it. Don’t forget the descriptions and the documentation! For all objects.

since from the view of our Software Component “CCVENDOR_CRM” SAP is the Partner Software Component. title = ccCRM. The text “Insert Application Component” should appear. Save. Create a graphical representation of the SAP system by rightclicking into the first grey column. then “Close” You can now find a window with the details of the action. bapi. rfc. ES) from external systems ____________________________________________________________________________________________ Create the Integration Scenario: Open your namespace “Integration Scenarios…” and rightclick on “Integration Scenarios”. choose this one. of ccvendor. switch to the change mode here. created previously in the SLD) Role – Name = External_CRM_System Choose “Apply” Don’t forget to enter some documentation of your Integration Scenario. From the SAP_System we want to send the MATMAS message. Create action to send the MATMAS01 from the SAP_System Still in the edit mode of your Integration Scenario. so we need to add a line to the “Outbound Interfaces”.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. title = SAP R/3 ENTERPRISE 47X110 Role – Name = SAP_System Choose “Apply” Create a graphical representation of the external system by rightclicking into the second grey column. Choose “Insert Application Component”. Enter a meaningful description and documentation 10/59 . click on the +-icon and choose ObjectType = IDOC Click on the 7th icon of the table (“Display input help”) and choose the MATMAS01 from your Software Component CCVENDOR_CRM. It’s no bad idea to describe the scenario quite detailed here. choose “New” Enter a name and description: IS_ReceiveMaterialMaster and choose “Create”. 10. o o o Application Component Type = Product Version. o o o Application Component Type = Product Version. rightclick into the SAP_System column and choose “Create Action” On the next popup we have to choose “External”. In the outbound-table. Enter the name “SendMatmas” and press “Finish”.com (our external product.

since the External_CRM_System contains our own Software Component CCVENDOR_CRM. Enter the name “ReceiveMatmas” and press “Finish”. rightclick and choose “Create Connection …”.MATMAS01” are marked. In the inbound-table. make sure that both checkboxes “MATMAS. ES) from external systems ____________________________________________________________________________________________ Save and close the created action Create action to receive the MATMAS01 in the External_CRM_System Still in the edit mode of your Integration Scenario. we need to add a line to the “Inbound Interfaces”. click on the +-icon and choose ObjectType = IDOC Click on the 7th icon of the table (“Display input help”) and choose the MATMAS01 from your Software Component CCVENDOR_CRM. it’s necessary that the receiving action is “below” the sending action. To get an asynchronous IDOC-connection. You can also see that the communication is asynchronous: 11/59 . rfc. Make sure to move the “ReceiveMatmas”-box accordingly: Rightclick the action “SendMatmas” and choose “Define as Start Action”. check the location of the two created actions. Enter a meaningful description and documentation Save and close the created action Create connection for message flow between the previously created actions Still in the edit mode of your Integration Scenario. then “Close” You can now find a window with the details of the action. Since we want to receive a message. In the following popup.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. Rightclick the action “ReceiveMatmas” and choose “Define as End Action” Mark both actions by holding the shift-key. switch to the change mode here. bapi. rightclick into the External_CRM_System column and choose “Create Action” On the next popup we have to choose “Internal”.

ES) from external systems ____________________________________________________________________________________________ Go to the “Assign Comm Channel Template” tab and assign the previously created template idoc_outbound_receiver in the receiver part. For a better overview. You can use the F4-help-icon in the “Name”-field to find the channel template in our Software Component CCVENDOR_CRM. Leave the sender part empty. rfc. you should add them directly into the already defined Integration Scenario. That’s it. If there are further communication steps involved in your scenario (other IDOCs or RFCs). With these simple steps you have created the certifiable content for the IDOC outbound scenario completely. You should only receive warning messages like: “Check Result for Object IS_ReceiveMaterialMaster Component View IS_ReceiveMaterialMaster: Connection from Action to send Material Master from SAP to Action to receive Material Master from SAP has no mapping” Activate all your changes (check chapter 5 about how to activate). bapi. in our tutorial we will generate a separate Integration Scenario for each communication method.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. as we don’t need to create a communication channel there: Choose apply then save the Integration Scenario Check the consistency of the scenario by choosing “Component View” “Check Configurability”. 12/59 .

we want to configure our Integration Scenario in the XI Integration Directory. we want to test the communication. it’s not necessary to export the Integration Directory Content. Note: When you are ready for a certification test drive. Open the Integration Builder. you can export the content so that it can be easily implemented at your customers site. Choose “Tools” “Transfer Integration Scenario from the Integration Repository” and use the F4-help-icon to find your Integration Scenario IS_ReceiveMaterialMaster in your Software Component Version. After that. 6. So we will also check. Just choose “Tools Export Design Objects”. we copy the Integration Scenario created in the XI Integration Repository into a Configuration Scenario. Since the system landscape is different for each customer. Click “Finish” and “Close”. bapi. 13/59 . so that you can find it later easily. These services are the physically existent Business Systems “CC_CRM” and “SAP_CE8” that we have created in the System Landscape Directory in chapter 3. select the Software Component Version “CCVENDOR_CRM. This automatically starts the: Integration Scenario Configurator: In this step we have to assign Services to our two Application Components “SAP_System” and “External _CRM_System” of our Integration Scenario. For certifiable XI Content it must be possible. So before you leave. ES) from external systems ____________________________________________________________________________________________ Export the Repository Content: After you have finished the creation of all the XI Content Objects.g. into CS_ccReceiveMaterialMaster (“CS” is ConfiguationScenario). rightclick on your change list and choose “Activate”. if this works as expected. you should clear the SLD cache with “Environment” Cache”.3 Create the Configuration Scenario in the XI Integration Directory In the next step. e. 1. You can also add your company name or initials as a prefix. Clear SLD cache: To have a consistent start. you should make sure to jump to the “Change Lists”-Tab. so that it fits into our existing landscape with an external HTTP server and the CE8 SAP system.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. Important: Every change in the Integration Directory must be committed in a second step. to configure it automatically with the Integration Scenario Configurator. please provide us the export path with the name of your XI content and the exported SLD content zip file (see chapter 3). rfc. “Clear SLD Data Import the Integration Scenario: In the first step. from there jump into the Integration Directory. Click “Continue” The scenario is copied into a Configuration Scenario and you should change the name.0” and export the objects that belong to your content that should be certified (usually “all objects of your Software Component Version”).

If it’s available. then choose it. then “Close” If not yet assigned. then it has been already created. use the arrow icons on the top to choose the Communication Step you want to configure. o Click on “Assign”. click into the field “Communication Channel” for the Receiver Business System on the very right. rfc. Assign Services: This is where we have to assign the Business Systems: o o In the popup. bapi. Click on the “Create”-icon of the table below (4th icon) and choose 2 times “Continue” Look for your Business System CC_CRM. Configure Connections: This is where we have to assign the Communication Channels: o In the popup. click on the “+”-icon of the table below and choose the F4-Help to find the Business System CC_CRM. ES) from external systems ____________________________________________________________________________________________ We can start directly with step 2: 2. o o o o Now use the arrow icons on the top to choose Role = External_CRM_System. If it’s not available here. click “Cancel”. 3. use the arrow icons on the top to choose Role = SAP_System. Then click the “Create”-icon (3rd icon) to start the Communication Channel Wizard. deselect the “Create Communication Channels Automatically” (Important!) and choose “Finish”.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. Since we only have one step in our Integration Scenario. Click on the “+”-icon of the table below and choose the F4-Help to find the Business System SAP_CE8. this is chosen automatically. o o 14/59 . In the table below.

o Finish the configuration of the connections by pressing “Apply”. now we need to configure the connection between the external http IDOC receiver and XI. ES) from external systems ____________________________________________________________________________________________ o Press “continue”. so that it does not collide with other configuration objects. 6. Go on with the configuration steps and generate the new configuration. Generate: Generate all the needed agreements automatically and finish the wizard: o o o o Change the general settings to “Generation” (no simulation).How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. rfc. bapi. Quickly check the log. Switch into the edit mode and enter the following data: o Target host: Host of http server o Service number: Port of http server o Path: Path of http service To access the internet: o Proxy Host: 155. Close the log without saving. 4. If you have later changed the Integration Scenario in the XI Integration Repository and you want to update the existing Configuration Scenario. and then press “continue”. Close the Integration Scenario Configurator and choose “Apply”. then you can also start the Integration Scenario Configurator manually: Open your Configuration Scenario with a double click Switch to the Edit Mode Choose “Configuration Scenario” “Integration Scenario Configurator” To update the scenario. then make sure that our template idoc_outbound_receiver is chosen. choose “Settings” “Integration Scenario from the Integration Repository” “Update”. Finish Configuration in XI Integration Directory: Add the connection details into the previously created Receiver Communication Channel: Open CS_ccReceiveMaterialMaster Service Without Party Business System CC_CRM CommChannel idoc_outbound_receiver. press “Start”. after that click “finish” and then “close”. if there are any errors.4 Finish the configuration manually With the wizard we have already created all the needed XI objects.68.229 o Proxy Port: 8080 o Authentication data if necessary 15/59 . Now give the Communication Channel a new unique name.56.

choose transaction BD10 Enter Material (e. 6. Send MATMAS01 IDOC: In the CE8 system.g. bapi. CC_CRM) Execute with F8 16/59 .g. T-22212) and your logical system (e. rfc. save and activate all the changes done before. ES) from external systems ____________________________________________________________________________________________ To finish the configuration in XI Integration Directory.5 Check the IDOC communication That’s it! Now you should be able to send MATMAS01 IDOCs from the SAP backend system to the external IDOC server via http.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc.

open “Monitoring” “Integration Engine Monitoring” Open the Monitor for processed XML Messages Enter appropriate selection criteria.0 content-type: text/xml content-length: 25524 connection: close accept: */* user-agent: SAP Web Application Server (1. 17/59 . e. charset=utf-8 Content-Length: 0 Congratulations! You have successfully created certifiable content and tested the communication.1 200 Ok Content-Type: text/xml. rfc.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. bapi. Please make sure to read more information on the configuration in chapters 11 and 12. Now all you have to do is fill out the Technical Profile questionnaire and complete the Configuration Guide document.0" encoding="UTF-8" ?> <MATMAS01> […] </MATMAS01> The unique message ID (GUID) can be found in the http header: msgguid=F0D38FDC18C5BA4E977FC5DEE169F3EE Sample Response: HTTP/1.0. With a doubleclick on the line you can inspect the details. ES) from external systems ____________________________________________________________________________________________ Check message in Integration Server Monitoring In NX7 system. Then you are ready for a certification test drive.g. Sample Request from SAP: POST /?msgguid=F0D38FDC18C5BA4E977FC5DEE169F3EE&service=SAP_CE8&namespace=urn%3asapcom%3adocument%3asap%3aidoc%3amessages&interface=MATMAS%2eMATMAS01&qos=EO HTTP/1. Receiver-Service = CC_CRM and execute with F8 Check the status of your message.640) host: P105077:123 accept-encoding: gzip <?xml version="1.

18/59 . For IDOC inbound. then “Close” after the successful import. The scenario is as follows: Inbound ALEREQ01: CC_CRM CE8CLNT850 7.0 of ccvendor. 1. So before you leave. We import the message type into our Software Component Version.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. bapi. the details of the connection are usually defined later during the configuration and are therefore not part of the static XI Content. Open your Software Component Version CCVENDOR_CRM. then “Continue”. You can find the complete configuration in our XI system.ALEREQ01. prepare the ALE customizing so that ALEREQ01-IDOCs can be received from the logical system CC_CRM. so that we can send MATFET messages from the external system CC_CRM to the CE8 system through XI using the SAP IDOC and HTTP Adapter. 7. we only need a receiver communication channel: Open your namespace “Adapter Objects” and rightclick on “Comm Channel Templates”. Choose “Finish”. save. from there jump into the Integration Repository. so it should be easy to copy it using different external systems and IDOCs. Since we already know. that the SAP receiver is connected via IDOC and the sending external system is connected via http. in our case it’s MATFET. This makes the configuration of the integration scenario later easier. Important: Every change in the Integration Repository must be committed in a second step. That’s it. In our case this is CE8CLNT850. You also need to know the central logical system of the server (the receiving SAP system). we can create the templates for these endpoints now. We only focus on the XI customizing. you should make sure to jump to the “Change Lists”-Tab. we only need to import one message type into the XI system. These messages are sent to SAP using the IDOC type ALEREQ01.2 Create the Repository Objects for the IDOC Inbound Scenario Open the Integration Builder. Import ALEREQ01 message data: Since the external system already understands the ALEREQ01 message format. Create Communication Channel Templates: The communication channels serve as the technical endpoints to the connected systems. ES) from external systems ____________________________________________________________________________________________ 7 XI Content for asynchronous IDOC Inbound In the following chapter we will configure the XI system. not the ALE customizing in the CE8.1 Check the customizing in the SAP backend system Prepare ALE customizing: In the CE8 system.com “Imported Objects” Rightclick on “IDOCs” and choose “Import” Enter data: Application Server: cpce801 System Number: 75 your CE8-user and password Choose the IDOCs you want to import. As a prerequisite you should have completed chapters 3-5. Save. rfc. then choose “Receiver”-type. rightclick on your change list and choose “Activate”. choose “New” Enter a name for the IDOC receiver: idoc_inbound_receiver and enter a meaningful description. Choose “Adapter Type” = “Idoc”. This name must match with the logical system name of the external Business System created in chapter 3. We also don’t need any mapping.

by clicking on in the menu of the XI Content object: 2. choose “New” Enter a name and description: IS_SendMaterialRequest and choose “Create”. you should always add a meaningful text in the field “Description” and also provide some further documentation. Create a graphical representation of the SAP system by rightclicking into the first grey column. rfc. o o o Application Component Type = Product Version. bapi.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. choose this one. Press here to show the documentation panel Create the Integration Scenario: Open your namespace “Integration Scenarios…” and rightclick on “Integration Scenarios”. Press here to add documentation 1. title = SAP R/3 ENTERPRISE 47X110 Role – Name = SAP_System Choose “Apply” 19/59 . ES) from external systems ____________________________________________________________________________________________ Don’t forget the descriptions and the documentation! For all objects. The text “Insert Application Component” should appear.

com (our external product. o o o Application Component Type = Product Version. title = ccCRM. Enter the name “SendMatfet” and press “Finish”. click on the +-icon and choose ObjectType = IDOC Click on the 7th icon of the table (“Display input help”) and choose the ALEREQ01 from your Software Component CCVENDOR_CRM. created previously in the SLD) Role – Name = External_CRM_System Choose “Apply” Don’t forget to enter some documentation of your Integration Scenario. 10. In the outbound-table. Enter a meaningful description and documentation Save and close the created action 20/59 . Save. rightclick into the External_CRM_System column and choose “Create Action” On the next popup we have to choose “Internal”. since the External_CRM_System contains our own Software Component CCVENDOR_CRM. of ccvendor. we need to add a line to the “Outbound Interfaces”. It’s no bad idea to describe the scenario quite detailed here. switch to the change mode here. then “Close” You can now find a window with the details of the action. Choose “Insert Application Component”.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. rfc. Since we want to send a message. ES) from external systems ____________________________________________________________________________________________ Create a graphical representation of the external system by rightclicking into the second grey column. bapi. Create action to send the MATFET message from the External_CRM_System Still in the edit mode of your Integration Scenario.

so we need to add a line to the “Inbound Interfaces”. rightclick and choose “Create Connection …”. then “Close” You can now find a window with the details of the action. In the SAP_System. as End Action” Mark both actions by holding the shift-key. switch to the change mode here. it’s necessary that the receiving action is “below” the sending action. make sure that both checkboxes “MATFET. click on the +-icon and choose ObjectType = IDOC Click on the 7th icon (“Display input help”) and choose the ALEREQ01 from your Software Component CCVENDOR_CRM. To get an asynchronous IDOC-connection. Make sure to move the “ReceiveMatfet”-box accordingly: Rightclick the action “SendMatfet” and choose “Define as Start Action”. rightclick into the SAP_System column and choose “Create Action” On the next popup we have to choose “External”.ALEREQ01” are marked. since from the view of our Software Component “CCVENDOR_CRM” SAP is the Partner Software Component. In the following popup. bapi. In the inbound-table. rfc. Enter the name “ReceiveMatfet” and press “Finish”. we want to receive the MATFET message.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. Rightclick the action “ReceiveMatfet” and choose “Def. check the location of the two created actions. ES) from external systems ____________________________________________________________________________________________ Create action to receive the MATFET message in the SAP_System Still in the edit mode of your Integration Scenario. You can also see that the communication is asynchronous: 21/59 . Enter a meaningful description and documentation Save and close the created action Create connection for message flow between the previously created actions Still in the edit mode of your Integration Scenario.

You should only receive warning messages like: “Check Result for Object IS_SendMaterialRequest Component View IS_SendMaterialRequest: Connection from Action to request Material Master Data from SAP to Action to receive the Material Master Request has no mapping” Activate all your changes (check chapter 5 about how to activate). For a better overview. That’s it. 22/59 . Leave the sender part empty. rfc. ES) from external systems ____________________________________________________________________________________________ Go to the “Assign Comm Channel Template” tab and assign the previously created template idoc_inbound_receiver in the receiver part.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. you should add them directly into the already defined Integration Scenario. in our tutorial we will generate a separate Integration Scenario for each communication method. You can use the F4-help-icon in the “Name”-field to find the channel template in our Software Component CCVENDOR_CRM. as we don’t need to create a communication channel there: Choose apply then save the Integration Scenario Check the consistency of the scenario by choosing “Component View” “Check Configurability”. If there are further communication steps involved in your scenario (other IDOCs or RFCs). With these simple steps you have created the certifiable content for the IDOC inbound scenario completely. bapi.

so that you can find it later easily. For certifiable XI Content it must be possible. Open the Integration Builder. We can start directly with step 2: 2. if this works as expected. Clear SLD cache: To have a consistent start. So before you leave.3 Create the Configuration Scenario in XI Integration Directory In the next step. bapi. ES) from external systems ____________________________________________________________________________________________ Export the Repository Content: After you have finished the creation of all the XI Content Objects. After that. to configure it automatically with the Integration Scenario Configurator. So we will also check. you should make sure to jump to the “Change Lists”-Tab.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. 7. we copy the Integration Scenario created in the XI Integration Repository into a Configuration Scenario. we want to test the communication. These services are the physically existent Business Systems “CC_CRM” and “SAP_CE8” that we have created in the System Landscape Directory in chapter 3. Click “Finish” and “Close”. 1. you should clear the SLD cache with “Environment” Cache”. You can also add your company name or initials as a prefix. Important: Every change in the Integration Directory must be committed in a second step. it’s not necessary to export the Integration Directory Content. Note: When you are ready for a certification test drive. from there jump into the Integration Directory. you can export the content so that it can be easily implemented at your customers site. Click “Continue” The scenario is copied into a Configuration Scenario and you should change the name. Just choose “Tools Export Design Objects”. e. into CS_ccSendMaterialRequest (“CS” is ConfiguationScenario). rightclick on your change list and choose “Activate”.g. so that it fits into our existing landscape with an external IDOC client and the CE8 SAP system. “Clear SLD Data Import the Integration Scenario: In the first step. This automatically starts the: Integration Scenario Configurator: In this step we have to assign Services to our two Application Components “SAP_System” and “External _CRM_System” of our Integration Scenario. rfc.0” and export the objects that belong to your content that should be certified (usually “all objects of your Software Component Version”). Assign Services: This is where we have to assign the Business Systems: o o In the popup. please provide us the export path with the name of your XI content and the exported SLD content zip file (see chapter 3). Choose “Tools” “Transfer Integration Scenario from the Integration Repository” and use the F4-help-icon to find your Integration Scenario IS_SendMaterialRequest in your Software Component Version. Click on the “+”-icon of the table below and choose the F4-Help to find the Business System SAP_CE8. 23/59 . select the Software Component Version “CCVENDOR_CRM. use the arrow icons on the top to choose Role = SAP_System. we want to configure our Integration Scenario in the XI Integration Directory. Since the system landscape is different for each customer.

click “Cancel”. 24/59 . then choose it. Click on the “Create”-icon of the table below (4th icon) and choose 2 times “Continue” Look for your Business System CC_CRM. If it’s available. If it’s not available here. ES) from external systems ____________________________________________________________________________________________ o o o o Now use the arrow icons on the top to choose Role = External_CRM_System. Then click the “Create”-icon (3rd icon) to start the Communication Channel Wizard. this is chosen automatically. bapi. so that it does not collide with other configuration objects. after that click “finish” and then “close”. 3. In the table below. then make sure that our template idoc_inbound_receiver is chosen. then “Close” If not yet assigned. and then press “continue”. click into the field “Communication Channel” for the Receiver Business System on the very right. o o o o Finish the configuration of the connections by pressing “Apply”. deselect the “Create Communication Channels Automatically” (Important!) and choose “Finish”. Since we only have one step in our Integration Scenario. use the arrow icons on the top to choose the Communication Step you want to configure. rfc. Configure Connections: This is where we have to assign the Communication Channels: o In the popup. o Click on “Assign”. then it has been already created. Press “continue”. click on the “+”-icon of the table below and choose the F4-Help to find the Business System CC_CRM. Now give the Communication Channel a new unique name.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc.

Generate: Generate all the needed agreements automatically and finish the wizard: o o o o Change the general settings to “Generation” (no simulation).2. 7. To finish the configuration in XI Integration Directory. then you can also start the Integration Scenario Configurator manually: Open your Configuration Scenario with a double click Switch to the Edit Mode Choose “Configuration Scenario” “Integration Scenario Configurator” To update the scenario. Close the log without saving. After that. press “Start”. CC_CRM. Close the Integration Scenario Configurator and choose “Apply”. Port: Here you have to enter your own created port according chapter 4. so we can enter this name: CC_DEST_CE8. 25/59 . save and activate all the changes done before.e.0 or Higher (CE8 is Enterprise 4. now we need to configure the connection between XI and the SAP Backend System CE8 in the communication channel. i. Go on with the configuration steps and generate the new configuration. Finish Configuration in XI Integration Directory: Add the connection details into the previously created Receiver Communication Channel: Open CS_ccSendMaterialRequest Service Without Party Business System SAP_CE8 CommChannel idoc_inbound_receiver. Switch into the edit mode and enter the following data: RFC Destination: We already have an RFC Destination pointing to CE8 system (check chapter 4).How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. If you have later changed the Integration Scenario in the XI Integration Repository and you want to update the existing Configuration Scenario. Quickly check the log. rfc. the external http IDOC client can be started and send messages to XI. bapi.7) SAP Release: 470. Interface Version: Release 4.4 Finish the configuration manually With the wizard we have already created all the needed XI objects. ES) from external systems ____________________________________________________________________________________________ 4. choose “Settings” “Integration Scenario from the Integration Repository” “Update”. if there are any errors.

How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. it generates a MATMAS message and sends that back through the XI system to your external HTTP server. bapi. then the SAP system will process the MATFET message. rfc. Post the request to iccpi7. charset=utf-8 Host: localhost Authorization: Basic <your user and password in BASE64 encoding> Accept: */* <?xml version="1.5 Check the IDOC communication That’s it! Now you should be able to send MATFET messages from an external HTTP client to the SAP backend system. The information about service.0" encoding="UTF-8" ?> <ALEREQ01> <IDOC BEGIN="1"> <E1ALER1 SEGMENT="1"> <MESTYP>MATMAS</MESTYP> <MESTYP40>MATMAS</MESTYP40> <E1ALEQ1 SEGMENT="1"> <OBJVALUE>MATNR</OBJVALUE> <SIGN>I</SIGN> <OPTION>EQ</OPTION> <LOW>P-101</LOW> </E1ALEQ1> </E1ALER1> </IDOC> </ALEREQ0 Congratulations! You have successfully created certifiable content and tested the communication. With a doubleclick on the flag you can inspect the details. Now all you have to do is fill out the Technical Profile questionnaire and complete the Configuration Guide document. If you have also implemented chapter 6. Sample Request: Below you can see the path to post the request to. choose “Goto” “Services” Find the http port number.com Check message in Integration Server Monitoring In NX7 system. Sender part: It’s not necessary to fill the IDOC Control Record EDI_DC40. Then you are ready for a certification test drive. ES) from external systems ____________________________________________________________________________________________ 7. POST /sap/xi/adapter_plain?service=CC_CRM&namespace=urn%3asapcom%3adocument%3asap%3aidoc%3amessages&interface=MATFET%2eALEREQ01&qos=EO HTTP/1.0 Content-type: text/xml. This is done by XI according to the configuration in the Integration Directory. namespace and interface can be taken from the matching Interface Determination. go to the ICM Monitor (transaction SMICM) In the menu. open “Monitoring” “Integration Engine Monitoring” Open the Monitor for processed XML Messages Enter appropriate selection criteria and execute with F8 Check the status of your message. Get the port number for http-requests In the NX7 system. Please make sure to read more information on the configuration in chapters 11 and 12. and if the requested material can be found.sap. 26/59 . for NX7 system this is 80.

so it should be easy to copy it using different external systems and modules. 8. Create Communication Channel Templates: The communication channels serve as the technical endpoints to the connected systems. Receiver communication channel. rightclick on your change list and choose “Activate”. bapi. Open your Software Component Version CCVENDOR_CRM. rfc. You can find the complete configuration in our XI system. so that we can query customer details from the SAP system using the RFC module (BAPI) BAPI_CUSTOMER_GETDETAIL. To send the message to XI. we will use the SAP HTTP Adapter.1 Create the Repository Objects for the RFC Inbound Scenario Open the Integration Builder. you should make sure to jump to the “Change Lists”-Tab. That’s it. this makes the configuration of the integration scenario later easier. ES) from external systems ____________________________________________________________________________________________ 8 XI Content for synchronous RFC/BAPI Inbound In the following chapter we will configure the XI system. then “Continue”. save. in our case it’s BAPI_CUSTOMER_GETDETAIL. the details of the connection are usually defined later during the configuration and are therefore not part of the static XI Content. we only need to import one message into the XI system. Choose “Adapter Type” = “RFC”. choose “New” Enter a name for the RFC receiver: rfc_inbound_receiver and enter a meaningful description.0 of ccvendor. 27/59 . Import BAPI_CUSTOMER_GETDETAIL metadata: Since the external system already understands the BAPI_CUSTOMER_GETDETAIL message format. then “Close” after the successful import. We only need the receiver channel.com “Imported Objects” Rightclick on “RFCs” and choose “Import” Enter data: Application Server: cpce801 System Number: 75 your CE8-user and password Choose the RFCs you want to import. We import the message into our Software Component Version. 1. So before you leave. Choose “Finish”. We also don’t need any mapping. from there jump into the Integration Repository. Save.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. We can create communication channel templates now. type RFC: Open your namespace “Adapter Objects” and rightclick on “Comm Channel Templates”. Important: Every change in the Integration Repository must be committed in a second step. As a prerequisite you should have completed chapters 3-5. then choose “Receiver”-type.

How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. you should always add a meaningful text in the field “Description” and also provide some further documentation. rfc. bapi. Press here to add documentation 1. by clicking on in the menu of the XI Content object: 2. ES) from external systems ____________________________________________________________________________________________ Don’t forget the descriptions and the documentation! For all objects. Press here to show the documentation panel 28/59 .

title = ccCRM. created previously in the SLD) Role – Name = External_CRM_System Choose “Apply” Don’t forget to enter some documentation of your Integration Scenario. since the External_CRM_System contains our own Software Component CCVENDOR_CRM. Since we want to send a message. The text “Insert Application Component” should appear. Save. bapi. o o o Application Component Type = Product Version. choose this one. switch to the change mode here.com (our external product. click on the +-icon and choose ObjectType = Function Module Click on the 7th icon of the table (“Display input help”) and choose the BAPI_CUST _GETDETAIL from CCVENDOR_CRM. In the outbound-table. Create a graphical representation of the SAP system by rightclicking into the first grey column. It’s no bad idea to describe the scenario quite detailed here. we need to add a line to the “Outbound Interfaces”. Choose “Insert Application Component”. Enter the name “SendCustDetailRequest” and press “Finish”. o o o Application Component Type = Product Version. rightclick into the External_CRM_System column and choose “Create Action” On the next popup we have to choose “Internal”. rfc. choose “New” Enter a name and description: IS_GetCustomerDetail and choose “Create”. title = SAP R/3 ENTERPRISE 47X110 Role – Name = SAP_System Choose “Apply” Create a graphical representation of the external system by rightclicking into the second grey column. of ccvendor. then “Close” You can now find a window with the details of the action. Enter a meaningful description and documentation Save and close the created action 29/59 . ES) from external systems ____________________________________________________________________________________________ Create the Integration Scenario: Open your namespace “Integration Scenarios…” and rightclick on “Integration Scenarios”.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. Create action to send the BAPI message from the External_CRM_System Still in the edit mode of your Integration Scenario. 10.

Enter a meaningful description and documentation Save and close the created action Create connection for message flow between the previously created actions Still in the edit mode of your Integration Scenario. Rightclick the Receive-action and choose “Define as End Action” 30/59 . Make sure to move the boxes accordingly: Rightclick the Send-action and choose “Define as Start Action”. since from the view of our Software Component “CCVENDOR_CRM” SAP is the Partner Software Component. rfc. switch to the change mode here. In the SAP_System. it’s necessary that both actions are on the same level. so we need to add a line to the “Inbound Interfaces”. check the location of the two created actions. ES) from external systems ____________________________________________________________________________________________ Create action to receive the BAPI message in the SAP_System Still in the edit mode of your Integration Scenario. rightclick into the SAP_System column and choose “Create Action” On the next popup we have to choose “External”. In the inbound-table.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. we want to receive the BAPI message. To get a synchronous RFC/BAPI-connection. click on the +-icon and choose ObjectType = Function Module Click on the 7th icon (“Display input help”) and choose the BAPI_CUST_GETDETAIL from CCVENDOR_CRM. Enter the name “RecvCustDetailRequest” and press “Finish”. bapi. then “Close” You can now find a window with the details of the action.

rightclick and choose “Create Connection …”. Choose apply then save the Integration Scenario 31/59 . In the following popup. If you cannot see the checkboxes. bapi. make sure that both checkboxes “BAPI_CUSTOMER_GETDETAIL” are marked. then press the top middle button to switch the actions.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. You can use the F4-help-icon in the “Name”-field to find the channel template in our Software Component CCVENDOR_CRM. rfc. ES) from external systems ____________________________________________________________________________________________ Mark both actions by holding the shift-key. You can also see that the communication is synchronous: Go to the “Assign Comm Channel Template” tab and assign the previously created templates rfc_inbound_receiver in the receiver part.

we copy the Integration Scenario created in the XI Integration Repository into a Configuration Scenario. This automatically starts the: 32/59 . rfc. “Clear SLD Data Import the Integration Scenario: In the first step. You should only receive warning messages like: “Check Result for Object IS_GetCustomerDetail Component View IS_GetCustomerDetail: Connection from Action to send the Customer Detail Request to SAP to Action to receive the Customer Detail Request in SAP has no mapping” Activate all your changes (check chapter 5 about how to activate). So we will also check.g. e. Click “Continue”. ES) from external systems ____________________________________________________________________________________________ Check the consistency of the scenario by choosing “Component View” “Check Configurability”. if this works as expected. Click “Finish” and “Close”. in our tutorial we will generate a separate Integration Scenario for each communication method. So before you leave. you should clear the SLD cache with “Environment” Cache”. Export the Repository Content: After you have finished the creation of all the XI Content Objects. Just choose “Tools Export Design Objects”. 8. Important: Every change in the Integration Directory must be committed in a second step. you should add them directly into the already defined Integration Scenario. For certifiable XI Content it must be possible. select the Software Component Version “CCVENDOR_CRM. into CS_ccGetCustomerDetail (“CS” is ConfiguationScenario). so that you can find it later easily. With these simple steps you have created the certifiable content for the RFC inbound scenario completely. For a better overview.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. If there are further communication steps involved in your scenario (other IDOCs or RFCs). Note: When you are ready for a certification test drive. you can export the content so that it can be easily implemented at your customers site. please provide us the export path with the name of your XI content and the exported SLD content zip file (see chapter 3). After that. Clear SLD cache: To have a consistent start. we want to test the communication. to configure it automatically with the Integration Scenario Configurator. it’s not necessary to export the Integration Directory Content. Choose “Tools” “Transfer Integration Scenario from the Integration Repository” and use the F4-help-icon to find your Integration Scenario IS_GetCustomerDetail in your Software Component Version. bapi. Since the system landscape is different for each customer. from there jump into the Integration Directory. so that it fits into our existing landscape with an external RFC client and the CE8 SAP system. The scenario is copied into a Configuration Scenario and you should change the name. we want to configure our Integration Scenario in the XI Integration Directory.2 Create the Configuration Scenario in XI Integration Directory In the next step. You can also add your company name or initials as a prefix. 1. That’s it. Open the Integration Builder. you should make sure to jump to the “Change Lists”-Tab. rightclick on your change list and choose “Activate”.0” and export the objects that belong to your content that should be certified (usually “all objects of your Software Component Version”).

Now click into the field “Communication Channel” for the Receiver Business System on the very right. use the arrow icons on the top to choose the Communication Step you want to configure. o Click on “Assign”. Now give the Communication Channel a new unique name. Then click the “Create”-icon (3rd icon) to start the Communication Channel Wizard. rfc.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. click “Cancel”. and then press “continue”. ES) from external systems ____________________________________________________________________________________________ Integration Scenario Configurator: In this step we have to assign Services to our two Application Components “SAP_System” and “External _CRM_System” of our Integration Scenario. then choose it. 3. If it’s available. after that click “finish” and then “close”. Assign Services: This is where we have to assign the Business Systems: o o In the popup. this is chosen automatically. Since we only have one step in our Integration Scenario. Click on the “Create”-icon of the table below (4th icon) and choose 2 times “Continue” Look for your Business System CC_CRM. bapi. o o o 33/59 . then make sure that our template rfc_inbound_receiver is chosen. These services are the physically existent Business Systems “CC_CRM” and “SAP_CE8” that we have created in the System Landscape Directory in chapter 3. then it has been already created. then “Close” If not yet assigned. If it’s not available here. We can start directly with step 2: 2. so that it does not collide with other configuration objects. Press “continue”. use the arrow icons on the top to choose Role = SAP_System. o o o o Now use the arrow icons on the top to choose Role = External_CRM_System. Configure Connections: This is where we have to assign the Communication Channels: o In the popup. click on the “+”-icon of the table below and choose the F4-Help to find the Business System CC_CRM. deselect the “Create Communication Channels Automatically” (Important!) and choose “Finish”. Click on the “+”-icon of the table below and choose the F4-Help to find the Business System SAP_CE8.

Close the log without saving. If you have later changed the Integration Scenario in the XI Integration Repository and you want to update the existing Configuration Scenario.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. 8. rfc.3 Finish the configuration manually With the wizard we have already created all the needed XI objects. 4. choose “Settings” “Integration Scenario from the Integration Repository” “Update”. ES) from external systems ____________________________________________________________________________________________ o Finish the configuration of the connections by pressing “Apply”. Go on with the configuration steps and generate the new configuration. 34/59 . press “Start”. then you can also start the Integration Scenario Configurator manually: Open your Configuration Scenario with a double click Switch to the Edit Mode Choose “Configuration Scenario” “Integration Scenario Configurator” To update the scenario. bapi. Close the Integration Scenario Configurator and choose “Apply”. Quickly check the log. now we need to configure the RFC connection between XI and the SAP Backend System CE8 in the receiver communication channel. Generate: Generate all the needed agreements automatically and finish the wizard: o o o o Change the general settings to “Generation” (no simulation). if there are any errors.

Sender-Service = CC_CRM and execute with F8. Switch into the edit mode and enter the following data: RFC Server Type: SAP System Application Server: cpce801. so they can only be found in the Runtime Workbench trace.dmzwdf. With a doubleclick on the flag you can inspect the details. 35/59 . bapi.sap. ES) from external systems ____________________________________________________________________________________________ Finish Configuration in XI Integration Directory: Add the connection details to SAP into the previously created Receiver Communication Channel: Open CS_ccGetCustomerDetail Service Without Party Business System SAP_CE8 CommChannel rfc_inbound_receiver. Check the status of your message.4 Check the RFC communication That’s it! Now you should be able to call the BAPI_CUSTOMER_GETDETAIL from the external client via http. then you also need to set the following parameter in the channel: Open the “Advanced Mode” and select “Commit Handling for Single BAPI Calls”. Get the port number for http-requests In the NX7 system. for NX7 system this is 80. rfc. Check message in Runtime Workbench Open the Integration Builder. choose “Goto” “Services” Find the http port number. 8. If you want to make a BAPI call that needs a closing “BAPI_ TRANSACTION_COMMIT” to commit the database change. e.sap. open “Monitoring” “Integration Engine Monitoring” Open the Monitor for processed XML Messages Enter appropriate selection criteria.com Check message in Integration Server Monitoring In NX7 system. Post the request to iccpi7. jump into the Runtime Workbench Open the Message-Monitoring and choose the “Adapter Engine” Enter appropriate selection criteria and click on “Start” Check the status and if necessary the details.corp System Number: 75 Logon Language: EN Logon Client: 850 Your user and password for CE8.g. go to the ICM Monitor (transaction SMICM) In the menu. The synchronous messages are not persisted in the Integration Server by default.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. To finish the configuration in XI Integration Directory. save and activate all the changes done before.

namespace and interface can be taken from the matching Interface Determination. Sender-Service = CC_CRM and execute with F8 Check the status of your message..How to configure SAP XI/PI to use the standard SAP communication APIs (idoc.0" encoding="UTF-8"?> <rfc:BAPI_CUSTOMER_GETDETAIL..640) <?xml version="1. Sender part: POST /sap/xi/adapter_plain?service=CC_CRM&namespace=urn%3asapcom%3adocument%3asap%3arfc%3afunctions&interface=BAPI_CUSTOMER_GETDETAIL HTTP/1.0. Congratulations! You have successfully created certifiable content and tested the communication. The information about service. Now all you have to do is fill out the Technical Profile questionnaire and complete the Configuration Guide document.Response> Check message in Integration Server Monitoring In NX7 system. ES) from external systems ____________________________________________________________________________________________ Sample Request: Below you can see the path to post the request to.Response xmlns:rfc="urn:sap-com:document:sa.g. Please make sure to read more information on the configuration in chapters 11 and 12.0 Content-type: text/xml.0" encoding="UTF-8" ?> <rfc:BAPI_CUSTOMER_GETDETAIL xmlns:rfc="urn:sap-com:document:sap:rfc:functions"> <CUSTOMERNO>0000001000</CUSTOMERNO> <PI_SALESORG>0001</PI_SALESORG> </rfc:BAPI_CUSTOMER_GETDETAIL> Sample Response: HTTP/1... Then you are ready for a certification test drive. open “Monitoring” “Integration Engine Monitoring” Open the Monitor for processed XML Messages Enter appropriate selection criteria. bapi. rfc. 36/59 . With a doubleclick on the flag you can inspect the details."> <PE_ADDRESS><FORM_OF_AD>Company</FORM_OF_AD> <NAME>Becker Berlin</NAME> [. charset=utf-8 Host: localhost Authorization: Basic <your user and password in BASE64 encoding> Accept: */* <?xml version="1. e.0 200 OK content-type: application/xml content-length: 263 msgguid: 8BE65800476811D995B100300546F7E9 server: SAP Web Application Server (1.] </PE_ADDRESS> <RETURN/> </rfc:BAPI_CUSTOMER_GETDETAIL.

you should make sure to jump to the “Change Lists”-Tab. choose “New” Enter a name for the RFC receiver: rfc_outbound_receiver and enter a meaningful description. then “Continue”. 9. rightclick on your change list and choose “Activate”. 1. As a prerequisite you should have completed chapters 3-5. rfc. type HTTP: Open your namespace “Adapter Objects” and rightclick on “Comm Channel Templates”. ES) from external systems ____________________________________________________________________________________________ 9 XI Content for synchronous RFC/BAPI Outbound In the following chapter we will configure the XI system. Save. from there jump into the Integration Repository. That’s it. Create Communication Channel Templates: The communication channels serve as the technical endpoints to the connected systems. We also don’t need any mapping. we only need to import one message into the XI system. 37/59 . then choose “Receiver”-type. You can find the complete configuration in our XI system.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc.0 of ccvendor. save. We can create communication channel templates now. Important: Every change in the Integration Repository must be committed in a second step. with which you can transfer catalog data. then “Close” after the successful import. so it should be easy to copy it using different external systems and modules. bapi. in our case it’s QIRF_SEND_CATALOG_DATA. We import the message into our Software Component Version. so that we can call a function module that is implemented in the external system via http. The module is defined in an external server sample that will be called from XI. Import QIRF_SEND_CATALOG_DATA metadata: Since the external system already understands the QIRF_SEND_CATALOG_DATA message format. the details of the connection are usually defined later during the configuration and are therefore not part of the static XI Content. So before you leave.1 Create the Repository Objects for the RFC Outbound Scenario Open the Integration Builder. this makes the configuration of the integration scenario later easier. Choose “Finish”. we will use the function module “QIRF_SEND_ CATALOG_ DATA”. Open your Software Component Version CCVENDOR_CRM.com “Imported Objects” Rightclick on “RFCs” and choose “Import” Enter data: Application Server: cpce801 System Number: 75 your CE8-user and password Choose the RFCs you want to import. Choose “Adapter Type” = “HTTP” by using the F4-Help-icon. Receiver communication channel. As a sample.

That’s it. 38/59 . by clicking on in the menu of the XI Content object: 2. the details of the connection are usually defined later during the configuration and are therefore not part of the static XI Content. Press here to add documentation 1. ES) from external systems ____________________________________________________________________________________________ Sender communication channel. Save. you should always add a meaningful text in the field “Description” and also provide some further documentation. Press here to show the documentation panel Create the Integration Scenario: Open your namespace “Integration Scenarios…” and rightclick on “Integration Scenarios”. The text “Insert Application Component” should appear. Don’t forget the descriptions and the documentation! For all objects.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. choose “New” Enter a name and description: IS_ReceiveCatalogData and choose “Create”. Choose “Adapter Type” = “RFC” by using the F4-Help-icon. type RFC: Open your namespace “Adapter Objects” and rightclick on “Comm Channel Templates”. rfc. Create a graphical representation of the SAP system by rightclicking into the first grey column. choose “New” Enter a name for the RFC sender: rfc_outbound_sender and enter a meaningful description. bapi. choose this one.

created previously in the SLD) Role – Name = External_CRM_System Choose “Apply” Don’t forget to enter some documentation of your Integration Scenario. of ccvendor. Since we want to send a message. switch to the change mode here. since from the view of our Software Component “CCVENDOR_CRM” SAP is the Partner Software Component. In the outbound-table. Create action to send the RFC message from the SAP_System Still in the edit mode of your Integration Scenario. title = ccCRM. Enter a meaningful description and documentation Save and close the created action 39/59 . rightclick into the SAP_System column and choose “Create Action” On the next popup we have to choose “External”.com (our external product. title = SAP R/3 ENTERPRISE 47X110 Role – Name = SAP_System Choose “Apply” Create a graphical representation of the external system by rightclicking into the second grey column. then “Close” You can now find a window with the details of the action. Enter the name “SendCatalogDataQuery” and press “Finish”. It’s no bad idea to describe the scenario quite detailed here. o o o Application Component Type = Product Version. rfc. click on the +-icon and choose ObjectType = Function Module Click on the 7th icon of the table (“Display input help”) and choose the QIRF_SEND_CATALOG_DATA from CCVENDOR_CRM. Choose “Insert Application Component”. bapi. 10. Save. ES) from external systems ____________________________________________________________________________________________ o o o Application Component Type = Product Version.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. we need to add a line to the “Outbound Interfaces”.

Enter the name “RecvCatalogDataQuery” and press “Finish”. we want to receive the RFC message. Make sure to move the boxes accordingly: Rightclick the Send-action and choose “Define as Start Action”. click on the +-icon and choose ObjectType = Function Module Click on the 7th icon (“Display input help”) and choose the QIRF_SEND_CATALOG_DATA from CCVENDOR_CRM. rfc. switch to the change mode here. In the following popup. rightclick and choose “Create Connection …”. In the inbound-table. then press the top middle button to switch the actions. so we need to add a line to the “Inbound Interfaces”. Enter a meaningful description and documentation Save and close the created action Create connection for message flow between the previously created actions Still in the edit mode of your Integration Scenario. then “Close” You can now find a window with the details of the action. check the location of the two created actions.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. it’s necessary that both actions are on the same level. In the External_System. If you cannot see the checkboxes. make sure that both checkboxes “QIRF_SEND_CATALOG_DATA” are marked. You can also see that the communication is synchronous: 40/59 . rightclick into the External_CRM_System column and choose “Create Action” On the next popup we have to choose “Internal”. To get a synchronous RFC/BAPI-connection. ES) from external systems ____________________________________________________________________________________________ Create action to receive the RFC message in the External_CRM_System Still in the edit mode of your Integration Scenario. bapi. since the External_CRM_System contains our own Software Component CCVENDOR_CRM. Rightclick the Receive-action and choose “Define as End Action” Mark both actions by holding the shift-key.

rfc. 1. Export the Repository Content: After you have finished the creation of all the XI Content Objects. You should only receive warning messages like: “Check Result for Object IS_ReceiveCatalogData Component View IS_RecvCatalogData: Connection from Action to send the Catalog Data Query from SAP to Action to receive the Catalog Data Query from SAP has no mapping” Activate all your changes (check chapter 5 about how to activate). You can use the F4-help-icon in the “Name”-field to find the channel template in our Software Component CCVENDOR_CRM. you should add them directly into the already defined Integration Scenario. Just choose “Tools Export Design Objects”. select the Software Component Version “CCVENDOR_CRM. For a better overview. in our tutorial we will generate a separate Integration Scenario for each communication method.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. That’s it. If there are further communication steps involved in your scenario (other IDOCs or RFCs). 41/59 . bapi.0” and export the objects that belong to your content that should be certified (usually “all objects of your Software Component Version”). you can export the content so that it can be easily implemented at your customers site. Choose apply then save the Integration Scenario Check the consistency of the scenario by choosing “Component View” “Check Configurability”. With these simple steps you have created the certifiable content for the RFC inbound scenario completely. ES) from external systems ____________________________________________________________________________________________ Go to the “Assign Comm Channel Template” tab and assign the previously created templates rfc_outbound_sender in the sender part and rfc_outbound_receiver in the receiver part.

We can start directly with step 2: 2. from there jump into the Integration Directory. For certifiable XI Content it must be possible. Choose “Tools” “Transfer Integration Scenario from the Integration Repository” and use the F4-help-icon to find your Integration Scenario IS_ReceiveCatalogData in your Software Component Version. to configure it automatically with the Integration Scenario Configurator. into CS_ccReceiveCatalogData (“CS” is ConfiguationScenario). This automatically starts the: Integration Scenario Configurator: In this step we have to assign Services to our two Application Components “SAP_System” and “External _CRM_System” of our Integration Scenario. Important: Every change in the Integration Directory must be committed in a second step. rightclick on your change list and choose “Activate”. 9. After that. “Clear SLD Data Import the Integration Scenario: In the first step. use the arrow icons on the top to choose Role = SAP_System.2 Create the Configuration Scenario in XI Integration Directory In the next step. please provide us the export path with the name of your XI content and the exported SLD content zip file (see chapter 3). The scenario is copied into a Configuration Scenario and you should change the name. So we will also check. rfc. bapi. Click “Finish” and “Close”. if this works as expected. 42/59 . we want to configure our Integration Scenario in the XI Integration Directory. you should clear the SLD cache with “Environment” Cache”. it’s not necessary to export the Integration Directory Content.g. we copy the Integration Scenario created in the XI Integration Repository into a Configuration Scenario. so that it fits into our existing landscape with an external RFC server and the CE8 SAP system. Assign Services: This is where we have to assign the Business Systems: o o In the popup. So before you leave. we want to test the communication. Open the Integration Builder. e. so that you can find it later easily. Click on the “+”-icon of the table below and choose the F4-Help to find the Business System SAP_CE8. These services are the physically existent Business Systems “CC_CRM” and “SAP_CE8” that we have created in the System Landscape Directory in chapter 3. Since the system landscape is different for each customer. Clear SLD cache: To have a consistent start. ES) from external systems ____________________________________________________________________________________________ Note: When you are ready for a certification test drive. Click “Continue”.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. You can also add your company name or initials as a prefix. you should make sure to jump to the “Change Lists”-Tab.

after that click “finish” and then “close”. rfc. Configure Connections: This is where we have to assign the Communication Channels: o In the popup. use the arrow icons on the top to choose the Communication Step you want to configure. then make sure that our template rfc_outbound_receiver is chosen. Click on the “Create”-icon of the table below (4th icon) and choose 2 times “Continue” Look for your Business System CC_CRM. ES) from external systems ____________________________________________________________________________________________ o o o o Now use the arrow icons on the top to choose Role = External_CRM_System. so that it does not collide with other configuration objects.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. Since we only have one step in our Integration Scenario. and then press “continue”. Then click the “Create”-icon (3rd icon) to start the Communication Channel Wizard. If it’s available. 43/59 . then it has been already created. deselect the “Create Communication Channels Automatically” (Important!) and choose “Finish”. o Click on “Assign”. and then press “continue”. Press “continue”. click “Cancel”. In the table below. Then click the “Create”-icon (3rd icon) to start the Communication Channel Wizard. If it’s not available here. so that it does not collide with other configuration objects. after that click “finish” and then “close”. then make sure that our template rfc_outbound_sender is chosen. Now give the Communication Channel a new unique name. Now click into the field “Communication Channel” for the Receiver Business System on the very right. 3. click on the “+”-icon of the table below and choose the F4-Help to find the Business System CC_CRM. then “Close” If not yet assigned. click into the field “Communication Channel” for the Sender Business System. then choose it. o o o o o o o Finish the configuration of the connections by pressing “Apply”. Now give the Communication Channel a new unique name. bapi. this is chosen automatically. Press “continue”.

corp System Number: 75 Logon Language: EN Logon Client: 850 Your user and password for CE8.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. rfc.3 Finish the configuration manually With the wizard we have already created all the needed XI objects.sap. 44/59 . if SAP Backend is Unicode enabled.dmzwdf. Generate: Generate all the needed agreements automatically and finish the wizard: o o o o Change the general settings to “Generation” (no simulation). tables etc. choose “Settings” “Integration Scenario from the Integration Repository” “Update”.corp Appl Server Service: sapgw75 Program ID: CC_GET_CAT_REQUEST <could be any name> Select “Unicode” appropriately. then you can also start the Integration Scenario Configurator manually: Open your Configuration Scenario with a double click Switch to the Edit Mode Choose “Configuration Scenario” “Integration Scenario Configurator” To update the scenario. If you have later changed the Integration Scenario in the XI Integration Repository and you want to update the existing Configuration Scenario. Quickly check the log. Switch into the edit mode and enter the following data: RFC Server Parmeter: This specifies the Gateway of the SAP Backend System CE8: Appl Server: cpce801.dmzwdf. bapi.) cannot be read from the external http Server. Go on with the configuration steps and generate the new configuration. press “Start”. This channel registers on the gateway of the backend using a Program ID. now we need to configure the RFC connection between XI and the SAP Backend System CE8 in the sender communication channel. We also have to configure the connection to the external http server in the receiver communication channel. Close the log without saving.sap. if there are any errors. ES) from external systems ____________________________________________________________________________________________ 4. Open the “Advanced Mode” and deselect the “Verify Sender System” (important!) RFC Metadata Repository Parameter: Since the metadata of the RFC modules (structures. it’s necessary to specify our SAP Application Server here: Application Server: cpce801. Close the Integration Scenario Configurator and choose “Apply”. Finish Configuration in XI Integration Directory: Add the connection details to SAP into the previously created Sender Communication Channel: Open CS_ccReceiveCatalogData Service Without Party Business System SAP_CE8 CommChannel rfc_outbound_sender. 9.

e. ES) from external systems ____________________________________________________________________________________________ Now add the connection details to the external http Server into the previously created Receiver Communication Channel: Open CS_ccReceiveCatalogData Service Without Party Business System CC_CRM CommChannel rfc_outbound_receiver. then the external RFC Server also has to be Unicode enabled.4 Check the RFC communication That’s it! Now you should be able to call the QIRF_SEND_CATALOG_DATA in the external http Server. then test the connection. Finish Configuration in SAP Backend System CE8: Create a TCP/IP destination in the CE8 system that connects with the Sender Communication Channel created above: Enter SM59.68. Unicode: If the RFC Metadata Repository System specified in the Receiver Communication Channel is a Unicode system.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. then any call fails with “BE multiple receives defined”. 9.56. because this is a shared system that is used by many ISVs. press “Create” RFC Destination: CC_GET_CAT_REQUEST Connection Type: T Description: <enter something> Now press return key Activation Type: Registered Server Program Program ID: Use the one from the SenderCommChannel: CC_GET_CAT_REQUEST Save. Configuration considerations: Uniqueness of the receiver: The receiver of a certain synchronous call from a certain Backend system must be unique. Switch into the edit mode and enter the following data: o Target host: Host of http server o Service number: Port of http server o Path: Path of http service To access the internet: o Proxy Host: 155. save and activate all the changes done before. in the NX7 Integration Directory you can only have one configured receiver for the call QIRF_SEND_CATALOG_DATA from CE8.229 o Proxy Port: 8080 o Authentication data if necessary To finish the configuration in XI Integration Directory. bapi. Therefore it’s difficult to configure outbound RFC integration scenarios on NX7. rfc. If someone configures a second receiver.g. 45/59 .

see above) Enter some sample data in the import and table parameters Execute (press F8) Now the call is transferred through XI to the external RFC server and the result is displayed. With a doubleclick on the flag you can inspect the details. Check message in Integration Server Monitoring In NX7 system. Function module: QIRF_SEND_CATALOG_DATA Press the third icon or press F8 to test the module To call the module in the external system. ES) from external systems ____________________________________________________________________________________________ Test the communication from the SAP Backend System: Go into the SAP Backend CE8. Sender-Service = CC_CRM and execute with F8 Check the status of your message. jump into the Runtime Workbench Open the Message-Monitoring and choose the “Adapter Engine” Enter appropriate selection criteria and click on “Start” Check the status and if necessary the details. e. Check message in Runtime Workbench Open the Integration Builder.g. rfc. also modules that should be executed externally. open “Monitoring” “Integration Engine Monitoring” Open the Monitor for processed XML Messages Enter appropriate selection criteria. The external web server should accept the message and answer with an appropriate response. Sample Request from SAP: POST /?msgguid=E8F0CF214E7B11D9C29000300546F7E9&service=SAP_CE8&namespace=urn%3asapcom%3adocument%3asap%3arfc%3afunctions&interface=QIRF_SEND_CATALOG_DATA HTTP/1.0 content-type: text/xml content-length: 408 connection: close accept: */* accept-encoding: gzip <?xml version="1.0" encoding="UTF-8" ?> <rfc:QIRF_SEND_CATALOG_DATA xmlns:rfc="urn:sap-com:document:sap:rfc:functions"> <I_CATALOG>SAMPLE</I_CATALOG> <I_CATALOG_TYPE></I_CATALOG_TYPE> <I_IND_CATALOG_IS_CODEGROUP>X</I_IND_CATALOG_IS_CODEGROUP> <I_IND_CATALOG_IS_SEL_SET>X</I_IND_CATALOG_IS_SEL_SET> <I_LANGUAGE>E</I_LANGUAGE> <I_PLANT_OF_SELECTED_SET/> <T_QAICATAB/> <T_QIERRTAB/> </rfc:QIRF_SEND_CATALOG_DATA> 46/59 . Transaction SE37. fill the RFC target sys: RFC target sys: CC_GET_CAT_REQUEST (defined earlier. Here you can test any available function module. bapi.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc.

how to configure the XI system. rightclick on your change list and choose “Activate”. You can find the complete configuration in our XI system. so it should be easy to copy it using different external systems and modules.2 Create the Repository Objects for the Web Service Consumption Scenario Open the Integration Builder. we will use the SAP HTTP Adapter. 47/59 . from here you can download the WSDL file by clicking on WSDL (back-end).How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. To send the message to XI. bapi. Through the ES Workplace. 10 XI Content to invoke Web Services / SAP Enterprise Services In the following chapter we will illustrate.1 Download the WSDL file from the ES Workplace The ES Workplace can be used to browse through all the available SAP ES. you should make sure to jump to the “Change Lists”-Tab.Response> Congratulations! You have successfully created certifiable content and tested the communication. comparable with the RFC module (BAPI) BAPI_CUSTOMER_GETDETAIL from chapter 8. 10. So before you leave. 10.0 system. Now all you have to do is fill out the Technical Profile questionnaire and complete the Configuration Guide document. Please make sure to read more information on the configuration in chapters 11 and 12.Response xmlns:rfc="urn:sap-com:document:sap:rfc:functions"> <T_QAICATAB> <item> <SATZART>Q45</SATZART> <KATAB/> <KATALGART>1</KATALGART> <AUSWMGWRK/> <AUSWMENGE/> <CODEGRUPPE>COLOR</CODEGRUPPE> <CODE>1</CODE> <KURZTEXT>MY_COLOR</KURZTEXT> <BEWERTUNG/><FEHLKLASSE/><MUSSTEXTKZ/><BB_VORSCH/><QKENNZAHL/> </item> </T_QAICATAB> <T_QIERRTAB/> </rfc:QIRF_SEND_CATALOG_DATA.0 200 OK content-type: text/xml content-length: 263 <?xml version="1. navigate to the Business Object “Customer” and choose the Service Operation “Customer-BasicDataByIDQueryResponse_In” provided by an SAP ECC 6. Then you are ready for a certification test drive. As a RAC-Subscriber you could also request access to ES Workplace and after that download WSDL files and use the Enterprise Services published there. rfc. to call services that are described through a WSDL file. from there jump into the Integration Repository.0" encoding="UTF-8" ?> <rfc:QIRF_SEND_CATALOG_DATA. Important: Every change in the Integration Repository must be committed in a second step. For the sample we will use the SAP Enterprise Service (ES) “CustomerBasicDataByIDQueryResponse_In” that provides customer details from SAP. As a prerequisite you should have completed chapters 3-5. ES) from external systems ____________________________________________________________________________________________ Sample Response: HTTP/1.

we only need to import this message into the XI system. bapi. Don’t forget the descriptions and the documentation! For all objects. Press here to show the documentation panel 48/59 . ES) from external systems ____________________________________________________________________________________________ Import WSDL file: Since the external system already understands the CustomerBasicDataByIDQueryResponse_In message format. For the name we could use the technical name of the ES: ECC_CUSTOMER001QR. We import the message into our Software Component Version. Click the button to import the external definition and choose the file containing the WSDL. Click on “Create”. rightclick on “External Definitions”. We also don’t need any mapping.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. 1.0 of ccvendor. you should always add a meaningful text in the field “Description” and also provide some further documentation. by clicking on in the menu of the XI Content object: 2. rfc. after the upload you could save the external definition.com Open your namespace “Interface Objects”. Press here to add documentation 1. Open your Software Component Version CCVENDOR_CRM. choose “New” Enter a name for the external definition and a meaningful description.

Save the interface. Outbound Interface to send the message: Open your namespace “Interface Objects”. We now have to map these messages into a synchronous outbound and a synchronous inbound interface. the output message is the request and the input message is the response. the outbound and the error message. ES) from external systems ____________________________________________________________________________________________ Create Message Interfaces: The external definition contains specification of the inbound. rightclick on “Message Interfaces”. Choose “Category” = “Outbound” and “Mode” = “Synchronous” You could use the F4-help icon to fill the 3 message types accordingly. For the sender. rfc. F4-Help-Icons 49/59 . With the F4-help you can navigate to your external definition “ECC_CUSTOMER001QR” in your namespace and choose the correct message (see screenshot below).How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. bapi. choose “New” Enter a name for the Outbound Interface: SendCustDetailRequestESInterface and enter a meaningful description.

Save the interface. With the F4-help you can navigate to your external definition “ECC_CUSTOMER001QR” in your namespace and choose the correct message (see screenshot below). then choose “Receiver”-type. Web Services are usually invoked via SOAP. Save. the input message is the request and the output message is the response.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. save. We only need the receiver channel. this makes the configuration of the integration scenario later easier. For the receiver. type SOAP: Open your namespace “Adapter Objects” and rightclick on “Comm Channel Templates”. choose “New” Enter a name for the SOAP receiver: ES_inbound_receiver and enter a meaningful description. choose “New” Enter a name for the Inbound Interface: RecvCustDetailRequestESInterface and enter a meaningful description. ES) from external systems ____________________________________________________________________________________________ Inbound Interface to receive the message: Open your namespace “Interface Objects”. Choose “Category” = “Inbound” and “Mode” = “Synchronous” You could use the F4-help icon to fill the 3 message types accordingly. 50/59 . That’s it. rightclick on “Message Interfaces”. so we create one Receiver communication channel. the details of the connection are usually defined later during the configuration and are therefore not part of the static XI Content. We can create communication channel templates now. Choose “Adapter Type” = “SOAP”. bapi. Create Communication Channel Templates: The communication channels serve as the technical endpoints to the connected systems. rfc.

title = ccCRM. switch to the change mode here.com (our external product. title = SAP ECC 6. The text “Insert Application Component” should appear. we need to add a line to the “Outbound Interfaces”. created previously in the SLD) Role – Name = External_CRM_System Choose “Apply” Don’t forget to enter some documentation of your Integration Scenario. In the outbound-table. o o o Application Component Type = Product Version.0 Role – Name = SAP_System Choose “Apply” Create a graphical representation of the external system by rightclicking into the second grey column. Enter a meaningful description and documentation Save and close the created action Create action to receive the message in the SAP_System 51/59 . o o o Application Component Type = Product Version. rfc. then “Close” You can now find a window with the details of the action. since the External_CRM_System contains our own Software Component CCVENDOR_CRM. click on the +-icon and choose ObjectType = Message Interface Click on the 7th icon of the table (“Display input help”) and choose the “SendCustDetailRequestESInterface” from CCVENDOR_CRM. choose “New” Enter a name and description: IS_ES_CustomerDetail and choose “Create”.0 of ccvendor. Create action to send the Webservice Request from the External_CRM_System Still in the edit mode of your Integration Scenario. ES) from external systems ____________________________________________________________________________________________ Create the Integration Scenario: Open your namespace “Integration Scenarios…” and rightclick on “Integration Scenarios”.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. It’s no bad idea to describe the scenario quite detailed here. Enter the name “SendCustDetailRequestES” and press “Finish”. Create a graphical representation of the SAP system by rightclicking into the first grey column. 1. Choose “Insert Application Component”. Save. choose this one. rightclick into the External_CRM_System column and choose “Create Action” On the next popup we have to choose “Internal”. bapi. Since we want to send a message.

Rightclick the Receive-action and choose “Define as End Action” 52/59 . ES) from external systems ____________________________________________________________________________________________ Still in the edit mode of your Integration Scenario. To get a synchronous Webservice-connection. it’s necessary that both actions are on the same level. In the SAP_System. bapi. switch to the change mode here. Enter the name “RecvCustDetailRequestES” and press “Finish”. we want to receive the message. since from the view of our Software Component “CCVENDOR_CRM” SAP is the Partner Software Component. Make sure to move the boxes accordingly: Rightclick the Send-action and choose “Define as Start Action”. then “Close” You can now find a window with the details of the action. rightclick into the SAP_System column and choose “Create Action” On the next popup we have to choose “External”.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. rfc. In the inbound-table. click on the +-icon and choose ObjectType = Message Interface Click on the 7th icon (“Display input help”) and choose the “RecvCustDetailRequestESInterface” from CCVENDOR_CRM. Enter a meaningful description and documentation Save and close the created action Create connection for message flow between the previously created actions Still in the edit mode of your Integration Scenario. check the location of the two created actions. so we need to add a line to the “Inbound Interfaces”.

How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. ES) from external systems ____________________________________________________________________________________________ Mark both actions by holding the shift-key. bapi. then press the top middle button to switch the actions. Choose apply then save the Integration Scenario 53/59 . You can use the F4-help-icon in the “Name”-field to find the channel template in our Software Component CCVENDOR_CRM. rightclick and choose “Create Connection …”. rfc. make sure that the checkboxes are marked. You can also see that the communication is synchronous: Go to the “Assign Comm Channel Template” tab and assign the previously created templates ES_inbound_receiver in the receiver part. If you cannot see the checkboxes. In the following popup.

Clear SLD cache: To have a consistent start. Export the Repository Content: After you have finished the creation of all the XI Content Objects. After that we want to test the communication.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. Just choose “Tools Export Design Objects”. For a better overview. For certifiable XI Content it must be possible to configure it automatically with the Integration Scenario Configurator. you should add them directly into the already defined Integration Scenario. You should only receive warning messages like: “Check Result for Object IS_ES_CustomerDetail Component View IS_ES_CustomerDetail: Connection from SendCustDetailRequestES to RecvCustDetailRequestES has no mapping” Activate all your changes (check chapter 5 about how to activate). bapi. rightclick on your change list and choose “Activate”.2 Create the Configuration Scenario in XI Integration Directory In the next step. so that it fits into our existing landscape with an external web client and the system providing the web service / Enterprise Service (in our sample the ES Workplace). from there jump into the Integration Directory. Click “Continue”. we want to configure our Integration Scenario in the XI Integration Directory. If there are further communication steps involved in your scenario (other Web Services or IDOCs or RFCs). Since the system landscape is different for each customer. Open the Integration Builder. we copy the Integration Scenario created in the XI Integration Repository into a Configuration Scenario. 54/59 . in our tutorial we will generate a separate Integration Scenario for each communication method. So we will also check if this works as expected. With these simple steps you have created certifiable content to call a Web Service or SAP Enterprise Service. Choose “Tools” “Transfer Integration Scenario from the Integration Repository” and use the F4-help-icon to find your Integration Scenario IS_ES_CustomerDetail in your Software Component Version. you can export the content so that it can be easily implemented at your customers site. you should clear the SLD cache with “Environment” Cache”. please provide us the export path with the name of your XI content and the exported SLD content zip file (see chapter 3). ES) from external systems ____________________________________________________________________________________________ Check the consistency of the scenario by choosing “Component View” “Check Configurability”.0” and export the objects that belong to your content that should be certified (usually “all objects of your Software Component Version”). rfc. That’s it. you should make sure to jump to the “Change Lists”-Tab. 10. select the Software Component Version “CCVENDOR_CRM. So before you leave. “Clear SLD Data Import the Integration Scenario: In the first step. Note: When you are ready for a certification test drive. 1. it’s not necessary to export the Integration Directory Content. Important: Every change in the Integration Directory must be committed in a second step.

How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. so that you can find it later easily. then “Close” If not yet assigned. then it has been already created. Now click into the field “Communication Channel” for the Receiver Business System on the very right. You can also add your company name or initials as a prefix. Click on the “+”-icon of the table below and choose the F4-Help to find the Business System SAP_CF5. We can start directly with step 2: 5. then choose it. bapi. use the arrow icons on the top to choose Role = SAP_System. rfc. Then click the “Create”-icon (3rd icon) to start the Communication Channel Wizard. Since we only have one step in our Integration Scenario. click on the “+”-icon of the table below and choose the F4-Help to find the Business System CC_CRM. If it’s available. Click “Finish” and “Close”. o o o o Now use the arrow icons on the top to choose Role = External_CRM_System. e. use the arrow icons on the top to choose the Communication Step you want to configure. 6. into CS_ccESCustomerDetail (“CS” is ConfiguationScenario). ES) from external systems ____________________________________________________________________________________________ The scenario is copied into a Configuration Scenario and you should change the name. this is chosen automatically. Click on the “Create”-icon of the table below (4th icon) and choose 2 times “Continue” Look for your Business System CC_CRM.g. Assign Services: This is where we have to assign the Business Systems: o o In the popup. Configure Connections: This is where we have to assign the Communication Channels: o In the popup. These services are the physically existent Business Systems “CC_CRM” and “SAP_CF5” that we have created in the System Landscape Directory in chapter 3. This automatically starts the: Integration Scenario Configurator: In this step we have to assign Services to our two Application Components “SAP_System” and “External _CRM_System” of our Integration Scenario. 55/59 o o . o Click on “Assign”. If it’s not available here. deselect the “Create Communication Channels Automatically” (Important!) and choose “Finish”. click “Cancel”.

choose “Settings” “Integration Scenario from the Integration Repository” “Update”.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. 56/59 .3 Finish the configuration manually With the wizard we have already created all the needed XI objects. then make sure that our template ES_inbound_receiver is chosen. now we need to configure the SOAP connection between XI and the SAP Backend System that provides the web service / Enterprise Service. Now give the Communication Channel a new unique name. after that click “finish” and then “close”. 7. so that it does not collide with other configuration objects. Close the Integration Scenario Configurator and choose “Apply”. rfc. 10. Go on with the configuration steps and generate the new configuration. then you can also start the Integration Scenario Configurator manually: Open your Configuration Scenario with a double click Switch to the Edit Mode Choose “Configuration Scenario” “Integration Scenario Configurator” To update the scenario. press “Start”. If you have later changed the Integration Scenario in the XI Integration Repository and you want to update the existing Configuration Scenario. Quickly check the log. if there are any errors. ES) from external systems ____________________________________________________________________________________________ o Press “continue”. o Finish the configuration of the connections by pressing “Apply”. and then press “continue”. bapi. Close the log without saving. Generate: Generate all the needed agreements automatically and finish the wizard: o o o o Change the general settings to “Generation” (no simulation).

4 Check the communication That’s it! Now you should be able to call the ES “CustomerBasicDataByIDQueryResponse_In” from the external web client via http. open “Monitoring” “Integration Engine Monitoring” Open the Monitor for processed XML Messages Enter appropriate selection criteria.56. save and activate all the changes done before. Sample: <soap:address location="http://erp. go to the ICM Monitor (transaction SMICM) In the menu. e.229 Proxy Port: 8080 To finish the configuration in XI Integration Directory. then you have received a separate user for this. Post the request to iccpi7.com Check message in Integration Server Monitoring In NX7 system. Switch into the edit mode and enter the following data: Target URL: If the WSDL-file was taken from an SAP system. jump into the Runtime Workbench Open the Message-Monitoring and choose the “Adapter Engine” Enter appropriate selection criteria and click on “Start” Check the status and if necessary the details.68. The synchronous messages are not persisted in the Integration Server by default. choose “Goto” “Services” Find the http port number.sap. ES) from external systems ____________________________________________________________________________________________ Finish Configuration in XI Integration Directory: Add the connection details to SAP into the previously created Receiver Communication Channel: Open CS_ccESCustomerDetail Service Without Party Business System SAP_CF5 CommChannel ccES_inbound_receiver. then it should contain the Target URL of the Enterprise Service in the <soap:address> tag. Sure.g.esworkplace. rfc. Check the status of your message. 57/59 . Check message in Runtime Workbench Open the Integration Builder. via http you could also easily call the ES directly without using XI). bapi. for NX7 system this is 80. (Remember that this is only a sample. If you use the ES Workplace. Configure the Proxy: Proxy Host: 155. Sender-Service = CC_CRM and execute with F8. so they can only be found in the Runtime Workbench trace. With a doubleclick on the flag you can inspect the details. 10.com:80/sap/bc/srt/ xip/sap/ECC_CUSTOMER001QR?sap-client=800" /> Configure the User Authentication and enter your User/Password.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc.sap. Get the port number for http-requests In the NX7 system.

Congratulations! You have successfully created certifiable content and tested the communication.0" encoding="UTF-8" ?> <ns0:CustomerBasicDataByIDQuery_sync xmlns:ns0="http://sap. The information about service.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. namespace and interface can be taken from the matching Interface Determination. log on to SLD and go to “Administration Content Import (Upload CIM data)”. you need to provide a Configuration Guide document which describes all the necessary steps to be carried out by the customer to import and configure your XI Content package. e. You could use the template provided by ICC in the archive file (“XI Content Configuration_Guide_Template”). Please make sure to read more information on the configuration in chapters 11 and 12. There you can browse and select your SLD content zip file. The Configuration Guide document must cover these minimum steps: 1. charset=utf-8 Host: ld0301W06 Authorization: Basic <your user and password in BASE64 encoding> Accept: */* <?xml version="1. or you could write your own documentation. Now all you have to do is fill out the Technical Profile questionnaire and complete the Configuration Guide document. Sender part: POST /sap/xi/adapter_plain?service=CC_CRM&namespace=http://ccvendor. Import your SLD content file into the customer’s SLD system. open “Monitoring” “Integration Engine Monitoring” Open the Monitor for processed XML Messages Enter appropriate selection criteria. Then you are ready for a certification test drive.0 Content-type: text/xml.g. With a doubleclick on the flag you can inspect the details. To do that. 11 How to import/configure your XI Content in a target XI system For the certification. rfc. ES) from external systems ____________________________________________________________________________________________ Sample Request: Below you can see the path to post the request to. 58/59 .com/xi/crm_demo& interface=SendCustDetailRequestESInterface HTTP/1.com/xi/SAPGlobal20/Global"> <CustomerBasicDataSelectionByID> <CustomerID>1000</CustomerID> </CustomerBasicDataSelectionByID> </ns0:CustomerBasicDataByIDQuery_sync> Check message in Integration Server Monitoring In NX7 system. Sender-Service = CC_CRM and execute with F8 Check the status of your message. bapi.

After your assigned ICC consultant reviewed the documentations. chapter 4. he or she will discuss the details of the certification test drive and schedule a date for the actual functional certification test. bapi. There you can select your content file. zip-file that contains your exported SLD Content. ] 3. You can find a Configuration Guide template provided by ICC in the same archive file contained this tutorial. we need the following files from you: tpz-file that contains the exported Integration Repository Content. 12 Files needed for Certification For a certification test drive. Finish the configuration of the communication channels manually. Configuration Guide document of your integration scenario. Product Version. Complete the Technical Profile document for your package. 6. Import your XI content file into the customer’s XI Integration Repository. like you did when configuring your XI content for the certification test. then please send the file path and name during the export process to your assigned ICC consultant. Copy your Integration Scenario from the Integration Repository into the Directory. Software Component and Software Component Version as defined in the SLD (see chapter 3). We can retrieve the file for you. This guide should list all the steps that are necessary to import and configure your XI Content into a customer’s XI system (see chapter above). ES) from external systems ____________________________________________________________________________________________ 2. To do that. Assign the services. copy the tpz file with the content into the repository import directory on the XI server. Clear SLD 4. This can be done with “Tools Transfer Integration Scenario from the Integration Repository”. usually something like: \usr\sap\<sysid>\SYS\global\xi\repository_server\import Then log on to the Integration Repository and choose “Tools Import Design Objects”. If you cannot access this file directly (because it was saved on one of the ICC test systems). Please find further details about PPMS data collection in the XI Content certification catalog. 59/59 . Log on to the XI Integration Directory and clear the SLD cache with “Environment Data Cache”. configure the connections and generate all the communication agreements by using the automatically starting Integration Scenario Configurator wizard. You also can find this document in the same archive file. rfc.How to configure SAP XI/PI to use the standard SAP communication APIs (idoc. 5. PPMS data sheet containing information regarding your Product.