Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 
0 Kudos

I am doing a migration project for one of our clients who is migrating from SAP Process Integration(PI) 7.11 dual stack to Process Orchestration (PO) Netweaver 7.5 with service pack 01 java only system. I have built a new java only dev box using SAP migration tool and I have migrated objects from the existing system to the new system. It was completed successfully with a few outliers that will be fixed during the testing phase. My approach is to migrate from the new Java only Dev to the QA box through CTS transport, which will reduce a lot of work related to object creation in the new QA system. I had performed the SLD synchronization from Java only Dev to QA. This synced all the objects including Technical system, Business system, Custom Software component version and Products. I maintained the transport group as per SAP note 2093527.

According to SAP note 2093527, and depending on the method used to transport objects between the landscapes, we need to maintain the transport groups as show below.

If you are using CMS transport please keep in mind the following sequence:


QA   -> PROD

If you are using CTS+ transport then:



After the SLD transport group configuration, I had a deployment issue when I tried to transport objects using CTS plus. I checked the error log and it was complaining about the business system missing in the SLD configuration as shown below. This was not true.  All configurations I had performed were verified by our basis team.

I searched the SDN forum for a lead to fix this issue but every thread related to the same issue and suggested I perform the following activities which I had already performed:

  • Maintain business system
  • Maintain transport groups
  • Refer SAP note 2093527
  • Clear SLD cache
  • Refresh cache
  • Restart system

I talked to my BASIS architect. He looked into the system and found some Dev traces in the QA system but this did not solve the problem and we still had the same issue. After a lot of analysis, he performed the configuration changes in NWA (shown below).  This fixed the issue. I just wanted to put this information as a blog so that it would help PI or BAIS architects in case they face the same issue.  There currently is not a solution mentioned in any SDN threads.

Transport mapping for business system

Integration Server of the DEV system which is associated with Logical Identity

Configuration in QA must match the config in DEV considering the mapping of the transports

This seems to be a minor issue but it if this issue occurs it will be a show stopper in the migration project.

Hope this helps!!!!

Labels in this area