Importing Process Integration Content

This step is not covered by the PI template.


SAP NetWeaver supports cross-system applications using SAP NetWeaver usage type PI. Cross-system applications based on SAP NetWeaver deliver interface descriptions, mappings, and other objects relevant to communication, together with their product. Customers must import this content (the process integration content or XI content) into the Integration Repository of SAP NetWeaver. The import is required for configuring the cross-system application in the Integration Directory.

For SAP NetWeaver 2004s, you can import XI content from SAP NetWeaver 2004s, from XI 3.0, and also from XI 2.0 into the Integration Repository (all databases released for XI 3.0 or SAP NetWeaver 2004s are supported when you import XI 2.0 content). The Integration Builder migrates the objects from XI 2.0 to SAP NetWeaver 2004s. XI content from XI 3.0 and from SAP NetWeaver 2004s is always compatible and can be imported into the Integration Repository without migration. The procedure described in this document applies to migration, as well as to importing XI content based on SAP NetWeaver 2004s.

See also: Software Logistics for XI Objects


You must have the role SAP_XI_ADMINISTRATOR or SAP_XI_CONTENT_ORGANIZER to be able to export and import XI content.


You can find the XI content for an SAP application in export files on SAP Service Marketplace at under Download ® Support Packages' and Patches ® Entry by Application Group ® SAP content ® Process Integration Content (XI Content) ® <XI CONTENT software component ® <XI CONTENT software component version>(you can find the name of the software component and the version in the master guide of your application).

You import the XI content by first copying the provided export files into an import directory on the host of the Integration Builder and then importing the files into the Integration Repository. In the following steps, <systemDir> denotes the path for the system directory of the host (generally, <systemDir> corresponds to \usr\sap\<SAPSID>\SYS\global).


       1.      Obtain the export files for the XI content of the cross-system application.

The files are generally stored as a ZIP file on SAP Service Marketplace (see above). You can use the naming convention of these ZIP files to find their SPS (support package stack):

<software component version><SPS>_<patch level>

The files SCM4003_00.ZIP and SCMBASIS4003_00.ZIP refer to support package stack 03 with patch level 0 of the XI content.

Importing XI content with a later version does not overwrite the content that you have already imported into the Integration Repository. Support packages for XI content always contain both previous objects and the changes and enhancements delivered in the support package.

       2.      Copy the export files into the import directory for the Integration Repository (<systemDir>\xi\repository_server\import).

If the files are packed, you must unpack them before importing. (It is advisable to retain the ZIP files, see also the remarks for the last step.)

The actual export files have the extension .tpz. You must not unpack these files. The import directory is created the first time you call the Integration Builder.

       3.      Start the Integration Builder and call the Integration Repository.

To do this, perform the following steps:

                            a.      Log on to the SAP system on which your Integration Builder has been installed.

                            b.      Open the Integration Builder start page by calling it either from your user menu or with Transaction SXMB_IFR.

                            c.      Choose Integration Repository.

       4.      Choose Tools ® Import design objects to import the XI content.

Only the files from the import directory (see above) are offered to be imported. The sequence in which you import the export files is not important.

If version conflicts occur during the import, you can process and resolve them in the Integration Builder. In the case of corrupt export objects, you can force the import and skip objects that cannot be imported. The import is then incomplete, and references to objects that are not imported are lost.


After a successful import, the Integration Builder moves the imported TPZ files into the directory <systemDir>/xi/repository_server/importedFiles. The support package stack of imported software component versions is displayed on the Details tab page for the relevant software component version in the Integration Builder. If an error occurs, this information is important for support. Take one of the following precautions to retain the overview of the imported XI content:

?     If the release and the support package stack are clear from the file name of the TPZ file, simply leave the files in the directory importedFiles (see above).

If a file with the same file name already exists in the directory importedFiles, the Integration Builder adds the date and time of the import to the file name of the imported export file. This enables you to check which file was imported last.

?     After a successful import, you can keep the packed files, from whose naming convention you can derive the support package stack. Move them into the directory importedFiles, for example.