Skip to Content

Let’s imagine this scenario: you have a landscape with 3 XI instances, and around 100 business system defined, and a new instance of XI in needed for no-regression test purpose. So, how much time want you spend to create all the new business systems and the corresponding transport-target for the transports ? Ok, can spend some time making ALL the new business systems for the instance, but also the transport-target ? So many clicks! I made an light tool that allow to create automatically a CIM definition with the transport-target associations.

It’s a Microsoft Excel file with 2 columns, one for the list of business system sources, and one for the list of business system target. You have to enumerate in the Excel the source systems and the corresponding target systems. Than you can create the XML file that contain all the data in order to create the associations and import it in the SLD.

image

Enter the SLD with a user with role SAP_SLD_ADMINISTRATOR, than click “Administration”, “Import”, select the XML file to import, than click “Import Selected File”

You may have a warning like this: “The target namespace for the legacy import already contains versioned data for one or more export lines. The data of the selected import may possibly interfere with the previously imported data.” that is possible to ignore, the worst that may happen is that the associations are not created for one of these reasons:

1) the source system is not defined in the SLD 2) the target system is not defined in the SLD 3) the association already exist 4) the source system and the target system are in the system business system group

The beta version of SLD Transport Target Creator it’s available for download from this page of SAP site. You will really appreciate this tool in case you have a big business system landscape to manage only. Thanks to Sergio and Roberto for supporting this idea.

To report this post you need to login first.

7 Comments

You must be Logged on to comment or reply to a post.

  1. Saravana Kumar Kuppusamy
    …if i make a typo in the xls for a BS name which i beleive can happen when 100 of BS are to be configured ? How easy it is to revert the changes ?
    Also does your tool do a delta import ?

    Regards
    Saravana

    (0) 
    1. Sandro Garofano Post author
      >…if i make a typo in the xls for a BS name which i beleive can happen when 100 of BS are to be configured ?
      Could you please expain again this point ?

      >How easy it is to revert the changes ?
      At the moment you must to revert the changes manually, from SLD Administration, removing the association to the target system exacty in the same way you should follow in case you create the association manually without this tool.

      >Also does your tool do a delta import ?
      It is only a delta import, it makes the import of the association to target systems only, and only of the target systems you typed-in.

      Regards
      Sandro

      (0) 
      1. Saravana Kumar Kuppusamy
        Sandro, It is possible that when 100s of BS are involved, we make a typing mistake in the xls. Now, if we find this mistake after import in the target SLD, how do we revert ?
        Now , after using this tool, i will have to manually check each BS whether it is mapped to the intended target BS. This negates the very purpose of using this tool.
        It is a good idea of programmatically creating associations, i was just trying to point out the gaps i percieve in your approach.
        Your blog got me curious, i was browsing the help site, i could see Java/ABAP SLD client APIs available -> http://help.sap.com/saphelp_nw04/helpdata/en/29/2a63043f9c784da9175eb39cae51ed/content.htm

        May be exploring these APIs can help create associations(using APIs) directly on the SLD rather than a macro(hard code XMl tag approach) -> xml generation -> import in target SLD

        Regards
        Saravana

        (0) 
        1. Sandro Garofano Post author
          Even if you make some mistakes introducing the business system name, the SLD will validate your data and and will create the association only in the case that the target system name exist and the target system has a group associated different from the group of the target system.

          In the case the BS name is wrong typed (the BS do not exist), the SLD will not crete the association. In the case the BS is wrong typed but existing it will be necessary to remove the association manually, exactly like if you make the wrong association manually.

          Anyway the import give the feedback about the import status of entries

          I agree with you about the fact that is better to use the SLD API, just Excel allow  more easy editing functions like find-replace.

          Regards,
          Sandro

          (0) 
  2. Puloma Chaudhuri
    Hi,

    Useful blog.
    Thanks.

    But I think the macro works if you put the ‘fd.Show’ statement as follows:
    Set fd = Application.FileDialog(msoFileDialogSaveAs)
    fd.Show

    Regards,
    Puloma.

    (0) 
  3. Praveen Kumar
    Hi Sandro,

    I see comments stopped in 2006 on this blog, given the usefullness this has for an administrator 🙂

    I have one question though. How do I use this tool to REMOVE a transport target? Typically, I select ‘(None)’ while defining transport target in Business Landscape -> Click BS -> Transport Target.

    BTW, any plans for updated versions of this useful tool?

    rgds,
    Praveen K.

    (0) 

Leave a Reply