Skip to Content

XI Software Logistics 1: SLD Preparation

Done with your XI development/testing and now need to migrate your changes to CON / PRD system? Take a look at the XI Software Logistics, which offers various functionalities from organising shipment units to version management. In this series of blogs, we’ll take a holistic look at XI Software Logistics Solution. The first blog discusses role of SLD and preparation activities associated with it in detail.

SLD Preparation is one of the most important and initial steps in XI transport irrespective of whether you are using CMS or File transfer method. Once it’s ensured that all SLD objects are in place, we can go ahead with exporting XI objects from Integration Builder.

Various options are available for implementing SLD in the landscape ranging from individual SLD per system to a single central SLD for entire landscape and each one with its own pros and cons. You can refer to the planning guide of System Landscape Directory at -> Planning -> WAS which discusses various landscape scenarios and its various aspects. For this article we’ll consider a scenario wherein DEV and TEST system share same SLD while PRD system has its own SLD. So pictorially landscape can be presented as:


SLD Objects
SLD Objects accessed in Integration Repository
1. Products
2. Software Component Version (SWCV)

SLD Objects accessed in Integration Directory
1. Technical System
2. Business System

Products and SWCVs will remain same across SLDs while technical and business systems will have three sets specific to each environment viz. DEV, CON, PRD.


TSd = Technical System in DEV env……………..BSd = Business System in DEV env
TSt = Technical System in CON env……………..BSt = Business System in CON env
TSp = Technical System in PRD env……………..BSp = Business System in PRD env

Now key point here is that in SLDp we need to have (at least) Technical and Business Systems of CON environment as well. Why is that ? Because we need to mark transport source and targets for all business systems. We’ll discuss this in detail later in section ‘Business System Attributes’.

SLD Objects to be transported:
So the objects that we need to transport from source SLD to target are :


Transport Mechanism
We can move objects by exporting them from source SLD and then later importing them into target SLD.

Exporting Objects(Product,SWCV,TS,BS):
In SLD choose the object and then click on export button as shown below.


Alternatively from respective browser page you can select multiple objects (like TS) and export them together.
Now you get a file to download containing exported objects.


Download this file on local desktop.

Importing objects (Product, SWCV, TS, BS):
In Target SLD follow the below link to import the file :
Administration -> Content -> Import


SLD Bridge
Further we can configure SLDT to forward and update the information received from CON technical systems to SLDP. This is achieved by configuring SLD data supplier bridge of SLDT. Add a new SLD Client pointing to SLDP as below:
Administration -> Data Supplier Bridge -> Add SLD


Settings will take effect when data supplier bridge is restarted.

Why not to create ?
As such Products and SWCVs can be created directly in target SLD instead of transporting from Source SLD. However its essential for SWCV to have identical GUID in both source and target SLD and the best of ensuring the same is export /import method.


Business System Attribute :
Two important attributes of Business System decide what environment the system belongs to and what is the transport target for the business system.


So here system SAPISU belongs to Dev environment and upon transport all the communication channels below system will automatically change to IST_200 in target environment QA. So please create business system group and maintain group and target system for each and every business system as explained below.

Creating Business System Groups
For transport of configuration objects its required to create and maintain transport targets for all business systems. In the Group dropdown, select Edit Groups. Now here you can create a new Transport group say PRD.

Maintaining Transport Targets
Home page –> Business Landscape –> Select Business System


Click on transport targets


In target now we can choose BSp1 and thus assign transport target.
So now objects being moved, business system group created and target system maintained, SLD preparation is done and now it’s a time to start XI Transports. All The Best.

You must be Logged on to comment or reply to a post.
    • Hi Youvaraj,

             i need to track the list of IB objects that are getting successfully imported intot he target system. Will this list be stored in any DB tables or any file system. I basically need to develop a custom ABAP code that would fetch the list of the XI Objects created both in the ABAP stack and in the JAVA stack.

  • Hi,

    This is a very useful blog, thanks for sharing.

    Can you maybe expand a bit on how the XI transports are configured between QA and Prod for this scenario?

    I presume that you will use the CMS. How are you going to configure the tracks?

    Thanks and Regards

    • Hi Manish,

      Sorry for delayed reply and thanks for your comments. About transport from QA to PRD, it will be on the same grounds as we discussed in this series. Only few things such ‘assembly’ option is different and yeah little tricky. And about tracks, we don’t need seperate for QA to PRD, since in the same track itself we update repository/directory URL of the PRD system.
      Let me know if any specific query regarding this.


  • Hi Youvraj,

    It is a good article. We are also doing an XI implementation and are contemplating whether to have a single SLD for all the systems ot to have different SLDs for DEV/TST & PRD.

    Can you please suggest what is the best architecture based on your experience.

    Thanks & Regards,
    Manas Jindal

  • Hi Youvraj,
    Below are the high level steps I have followed and a question. Appreciate your help in advance.

    Scenario: Trying to move Integ Rep (IR) and Integ Dir (ID) transports using CMS. QA has its own SLD and PROD has its own SLD.

    – Exported business systems, technical systems, products and software components from the DEV/QA SLD.

    – Imported the above items into the PROD SLD. This helps persist the GUID.

    – Setup a CMS track for IR objects using the QA XI REP URL for the dev system and PROD XI REP URL for the consolidation system. Selected the software component for which the objects needed to be migrated. Moved the IR objects and that completed successfully. Please correct me if I missed any thing.

    – The question is about the migration of the ID objects. I am planning to setup a CMS track for ID objects using the QA XI DIR URL for the dev system and PROD XI REP URL for the consolidation system. Once I move the ID objects using this track, they will have references to the QA business systems. Is that a true statement? If true, then how can I replace them with PROD business systems?


    • Hi Amjad,
      ID objects will have reference to QA system. When you import them in PRD, they’ll pick up their target systems from SLD. Means you’ve to first maintain transport target for all BS in QA. Prior to that create Business System Group in SLD as mentioed in the blog and then mark targets. Now while importing, corresponding BS belonging to PRD landscape will be picked up and get reflected.
      Hope this answers your query.


  • Hello, I am not a seasoned XI developer by far, however, upon reading XI books and documentation, i see that S/W components are attached to Products, and the Products are Imported into the  Intergration Builder. I have also seen, and been told, that it is common practice to create a Product that reflects the Project, and then attach the S/W components under that, for which XI would be interfacing. For example, if I were working on a new project, say, “myProj” I would create a product called “myProd”, then attach the S/W components involved, say, CRM under that. When the Product gets imported into the Intergration Builder, I continue my developments under a new namespace, that is under the Product “myProj”.

    Is this right?

    In reality, “myProj” is not a Product, it is a project.

    I hope this is clear



  • Hi Youvraj,

    Excellent work……..

    Wanted to share one of the issues i have with PI 7.0.


    I have installed a new PI 7.0 server which is on local SLD. I also have old PI 7.0 in which all the scenarios are configured.

    I am trying to import the scenarios from the old PI 7.0 to new PI 7.0.

    Both the servers are on local SLD and on different transport domains.

    I tried simple file transfer. I was successful.

    But when i am trying to import the ID objects which have got reference to SLD i am getting the error as below.

    Import failed because of business system transfer of object Service | ECC_XI: Obligatory transport target for business system ECC_XI not found in System Landscape Directory

    Import failed because of business system transfer of
    object Service | ECC_XI: Obligatory transport target
    for business system ECC_XI not found in System Landscape

    Obligatory transport target for business system ECC_XI
    not found in System Landscape Directory (BS_TARGET_NOT_FOUND)

    Business system P70 is not assigned to a business system
    group with the ID (XISystemGroup) (BS_GROUP_LOAD_BY_BS_PROC_EX)

    I have also imported the SLD contents related to the scenario.

    P70 is the SID of my new PI 7.0 and BWS is the SID of my old PI 7.0.

    ECC_XI is the business system which is referenced in the scenario.

    I tried things but didn’t worked out.

    Please suggest wat all need to done. Please let me know what business group to be created and transport targets to be created for what systems.

    Your suggestions will be really helpful.



  • Hi Youvraj,

    If possible please leave your phone number so that i can talk to you regarding the issue.

    It will be really helpful for me.



  • Hi,

    We are working with SAP PI 7.1 and the requeriment says add a new group between QA and PRD, called PREPROD, and PREPROD is a copy of PROD. What is  form for do transport?