Using SAP XI/PI Pre-Delivered Content

Applies to:
SAP XI/PI, XI Content. For more information, visit the Repository-based Modeling and Design homepage.

Summary
This document gives an introduction to the SAP XI/PI Predefined content. It tells us how to import the content and use it within SAP XI/PI. Author: Vinay Prabha Gautam

Company: L & T Infotech, Mumbai Created on: 22 October 2008

Author Bio
Vinay Prabha Gautam is a SAP XI/PI Techinical Consultant in L&T Infotech since last two years. Her area of experience is SAP XI 3.0, SAP PI 7.0, ABAP, MDM, SRM-SUS, SCMSNC.

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 1

Using SAP XI/PI Pre-Delivered Content

Table of Contents
Importing XI Content into the SAP XI: ................................................................................................................3 Using Predefined Content (XI-Content) in the Scenario:....................................................................................5 Integration Builder Design............................................................................................................................6 Integration Builder Configuration .................................................................................................................6 Advantages .........................................................................................................................................................7 Related Content..................................................................................................................................................7 Disclaimer and Liability Notice............................................................................................................................8

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 2

Using SAP XI/PI Pre-Delivered Content

In the following article, I have taken an example of SRM-SUS predefined content.

Importing XI Content into the SAP XI:

The predefined XI content is the standard content provided by the SAP for some specific uses. This content is provided for the applications which are frequently integrated with SAP systems using SAP-XI. All design time objects like data types, message types, message mapping and interface mapping are shipped with the predefined content. The XI Content for an SAP application is available on SAP Service Marketplace at service.sap.com/swdc -> Download -> Support Packages and Patches -> Entry by Application Group -> SAP Content -> ESR Content (XI Content) -> <XI CONTENT software component> -> <XI CONTENT software component version>.

Figure 1: Path to download the XI content

For using the XI content, first we need to import the XI Content into the Integration Repository. The steps for importing the XI content are given below. 1. Obtain the export files for the XI Content of the cross-system application. The files are generally stored as zip files on SAP Service Marketplace. You can use the naming convention of these zip files to determine their Support Package level (SP level) : <software component version><SP level>_<patch level>.
Note: When you import XI Content with an older version, this does not overwrite the content that you have already imported into the Integration Repository.

2. Copy the files into the import directory of the Integration Repository ("<systemDir>\xi\repository_server\import"). If the files are packed, you must unpack them before the import.
Note: The actual export files have the extension .tpz. You should not unpack those files.

3. Start the Integration Builder for the design time. To do this, log on to the SAP system in which the Integration Builder has been installed. To call the initial screen of the Integration Builder, use your user menu or call transaction SXMB_IFR. Then choose "Integration Repository".

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 3

Using SAP XI/PI Pre-Delivered Content

4. After you start the Integration Builder, follow the menu path "Tools -> Import design objects..." to import the XI Content. 5. After a successful import, the Integration Builder moves the imported tpz files into the directory "<systemDir>/xi/repository_server/importedFiles". The Support Package level of imported software component versions is available in the Integration Builder on the "Details" tab for the relevant software component version. This information is important for support if an error occurs. After successful import, XI content will be visible under your Software Component in the SLD.

Figure 2: XI content in SLD

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 4

Using SAP XI/PI Pre-Delivered Content

Using Predefined Content (XI-Content) in the Scenario:

After successful import you will be able to see the XI content in the Integration Builder Design with the software component name. Steps for configuring the scenario are given below.

Figure 3: XI content in Integration Builder Design

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 5

Using SAP XI/PI Pre-Delivered Content

Integration Builder Design 1. Identify the message mapping and interface mapping as per your requirement with the sender and receiver message. 2. Do the changes according to your requirement in the message mapping. 3. Sometimes message mapping is directly not present under the Message Mapping tab. In that case the message mapping will be present in .xsl files. In such case, if it is required to change the message mapping, we need to download the .xsl files and modify them according to the requirement. Upload the modified files into the Imported Archives under the Message Mapping tab in the Integration Builder Design.
Note: It is not advisable to do any changes in the standard predefined content. You can create your own software component and create dependency with the Standard Predefined Content Software Component and then use your Software Component for any custom development.

Figure 4: XI content in Integration Builder Configuration

Integration Builder Configuration 1. Create a new configuration scenario 2. Create the business service or assign business system to configuration scenario 3. Create communication channel in the Integration Builder Configuration under communication channel tab to enable the communication between the systems 4. Create Receiver Determination, Interface Determination and Receiver Agreement for the interfaces

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 6

Using SAP XI/PI Pre-Delivered Content

Advantages
1. Less Development: Other than custom developments like changes in mapping or new configurations scenario wherein you need to create data types, message types etc. you may not require to do any development.

2. Re-Usability: In case of any custom development, we can use the standard content and modify it according to our requirement

Related Content
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70d58f84-628c-2a10-349c89f32fcaf6c8 For B2B Integration Using Predefined Integration Content with SAP NetWeaver http://help.sap.com/erp2005_ehp_03/helpdata/EN/d3/35da4105aa3f5de10000000a1550b0/frameset. htm SAP Notes - 705541

For more information, visit the Repository-based Modeling and Design homepage

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 7

Using SAP XI/PI Pre-Delivered Content

Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 8