Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

Purpose:

In this Wiki, we will take a look at this common error which happens during the transport of Process Integration (PI) or Process Orchestration (PO) ESR and/or Integration Directory objects.

Overview:

We will document some of the known causes and solutions to this error and clear up some of the questions surrounding the required configurations for different System Landscape Directory (SLD) set-ups.

Background:

There are several different causes for this particular error ranging from SLD registration issues to incorrect configuration of the transport infrastructure.

How to Reproduce:

The error can occur when transporting PI objects using any of the standard transport methods:

  1. File System Transports
  2. CMS Transports
  3. CTS+ Transports

Understanding Your System Landscape:

It is essential to know/understand the landscape, particularly the SLD landscape of the PI system(s) as this effects the configurations required to set up the transports.

Central SLD landscape:
This is where each system in the PI landscape (Dev, QA and PRD) all feed in to one Central SLD. This can be installed on any of the 3 PI systems or on any other Java system e.g. Solution Manager.

Local SLD landscape:
This is where each system in the PI landscape (Dev, QA and PRD) all use their own local SLD’s. In this case there are 3 separate SLD’s, each of which need to be correctly maintained for the transport to execute correctly.

Other SLD landscape types:
The SLD landscape options can be more complex e.g. a combination of Local/Central (Dev and QA share 1 SLD, while PRD has a separate SLD). Or where there are more PI/PO systems involved than the standard Dev/QA/PRD e.g. pre-prod systems etc. This further increases the complexity of the transport landscape and thus the required transport configurations.

System Background:
It is also important to know/understand the background of the PI system. One common cause of this error is a failure to execute the necessary PI Configuration Wizards. These Configuration Wizards are mandatory after a new PI installation, an Upgrade, System Copy etc. Also any recent changes to the SLD landscape set up may require new configurations of your PI Transport Targets and Groups.

If you have recently completed a major system operational change such as a new PI installation, an Upgrade, System Copy etc, ensure that the relevant Configuration Wizard has been successfully executed for your installation type. See SAP Note 1286428 Configuration Wizard: PI Wizard Templates overview, for the list of Wizards available for these various system operations.

Configurations:

Transport Groups

All systems that are related to the same PI Integration Server domain can be assigned to a Business System Group. Business System Groups are a prerequisite for defining Transport Targets in the SLD. Usually you divide the systems into groups depending on the stage or technical tier e.g. DEV, QA, PRD. You can create a group of all Business Systems that are associated with one and the same PI Integration Server. The Integration Server acts as a central system for the Business System group. When defining Transport Targets between two groups, you ensure that during transport Business System components in the Source/Target Integration Directory are properly assigned or mapped to each other.

See Creating and Removing Business System Groups

Transport Targets

In the SLD, you create Transport Targets for Integration Directory content transports. These Transport Targets define which system in one environment (DEV, TEST, QA, PROD) corresponds to which system in another environment.

For example, you define that the Business System BSD in your Development environment corresponds to a Business System BSQ in your Quality Assurance environment and that the SAP NetWeaver PI system PID in your Development environment corresponds to PIQ in your Quality Assurance environment.

If you have one Central SLD for all 3 PI systems (DEV, QA and PRD), the configuration of the Transport Targets and Groups is fairly straightforward.

If you have separate SLD's the configuration becomes more complex. But bear in mind the following:

  • The DEV SLD only requires information about DEV Business Systems, because Business Systems are not imported from other environments.
  • The QA SLD requires information about the Business Systems from both DEV and QA environments, because Business Systems from DEV are imported and mapped to Business Systems from QA. Therefore the DEV Business Systems must exist in the QA SLD.
  • PROD SLD requires information about the Business Systems from both QA and PROD environment, because Business Systems from QA are imported and mapped to Business Systems from PROD. Therefore the QA Business Systems must exist in the PRD SLD.

See Configure Groups and Transport Targets in the SLD and the System Landscape Directory: Planning Guide
-> In particular section 3.2.1 SAP NetWeaver Process Integration

Business System Naming Conventions

In landscapes, where more than one PI installation is used, you must make sure that Business System names are unique in the whole landscape. For example, it is not possible to configure a transport of BS_IF123 in Dev to BS_IF123 in QA. The name of the Business System must be unique. For example, BS_IF123_DEV -> BS_IF123_QA will work.

See PI Best Practices Naming Conventions

SLD Synchronization

If you have a multi-SLD landscape set up, the SLD used by the Target PI must contain the Business Systems of both Source and Target PI. The most efficient way to achieve this is to set up SLD Synchronization between the Source and Target SLD's. For more details on this process see the resources below:
SAP Help: SLD Content Synchronization

SAP Blog: Demo: The Full Automatic Sync Feature in the SLD of SAP NetWeaver 7.1

Troubleshooting steps:

  1. Firstly establish that both Source and Target PI systems are in good health i.e. the basic configurations of both systems are correct. Use SAP Note 817920 XI/PI/AEX Readiness Check 3.0/7.0, 7.1, 7.3, 7.31, 7.4. In particular, ensure the SLD and PI Cache related checks are working as expected.
  2. Ensure the Business Systems involved have unique names in both Source and Target environments. For example, it is not possible to transport Test_BS on Dev to Test_BS on QA. If you have Test_BS_DEV and Test_BS_QA then the transport will be possible.
  3. Based on the information above regarding your SLD landscape set up and the required configuration of your Business Systems, ensure the necessary Technical System/Business System is available in the SLD used by both the Source and Target PI system

  4. Ensure the Transport Groups and Transport Targets are correctly configured

Related Content/References:

SAP Doc: SAP Process Integration (PI) Software Logistics – How to deal with PI transports via CTS+

SAP Doc: How to Configure Enhanced CTS for SAP NetWeaver Process Integration 7.1 SP06

SAP Doc: Manual transports in PI using File System..Its simple

SAP Wiki: How does version management work in Enterprise Service Repository/Integration Repository?

SAP Wiki: How to Manually Correct the Registration of XI Components Within the SLD

SAP Wiki: IB and software lifecycle common problems

SAP Doc: System Landscape Directory (SLD)

Related Notes/KBA's:

SAP KBA 2216549 Import of PI Integrated Configuration object fails

SAP KBA 2093527 Error "Obligatory transport target for business system XXX not found" - explained

SAP KBA 1604679 PI: transport target for business system not found

SAP Note 1059576 XI Directory import fails due to inconsistent SLD host names

 

 

 

  • No labels