Skip to Content
avatar image
Former Member

CHARM SDHF "Multiple source and target clients"

Dear experts,

I would like to ask with regards to SDHF capabilities in terms of handling source and target clients.

Currently, in my system landscape, I have 2 development, 2 quality and 1 production clients.

However, when I use SDHF, once I have chosen the development client, it seems that I cannot create another transport request in the other development client. So, is this a limitation of SDHF or something that I wrongly configured?

The other problem is when I import the changes into quality client, it only imports to my first quality client, and not to the other. So, how do I handle this?


Ja'far Sukor

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Apr 13, 2011 at 10:44 AM


    Normally systems without transport connection are either postprocessing systems or single systems where nt defined transport routes.

    so if you want to move the TR to quality,obviously it move to one client which is the shortestone.if you want tht other client in your case (610) pls execute the report /TMWFLOW/SCMA_BTCH_SYNC_TEST, the source client as 600 (where TR already movied) target as 610.

    moreover you can execute the report in Background with regular interval which take over the syncronization simultaniously,


    Add comment
    10|10000 characters needed characters exceeded

    • Former Member


      Maybe I did something wrong at the Logical Component itself.

      So, in my scenario, where I have two DEV (500 & 510) and two QAS (600 & 610), how should I define my logical component and its type of role?

      Currently, I define the two DEV as Source Systems and the two QAS as Target Systems.

      Should I maintain 600 as the Target System while 610 as another role?


      Ja'far Sukor

  • avatar image
    Former Member
    Apr 05, 2011 at 07:46 PM

    Hi Ja'far,

    For u rgent corrections the system try to use the shortest way to the production systems, see details in this URL:

    The task list of a maintenance cycle contains all the systems that you defined in the maintenance project. The task list of an u rgent

    correction contains the production system in which the problem occurred, and only the systems on the shortest transport route from the development system to the production system. This implements your u rgent correction as quickly as possible.

    So, the track will use just one of those target systems.

    Also, in maintenance task list you have two options to sync the UC:

    - Import U rgent Corrections from Other Test Systems

    - Synchronize UC Level in MC Test and Production Systems

    Additionally, you can also use the following reports:

    - /tmwflow/scma_btch_sync_uc

    - /tmwflow/scma_btch_sync_test

    Best Regards,

    Fernando Rocha

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Another point I would like to add.

      It seems that in my Maintenance Cycle task list, the other target client (610) is being put outside of normal Project Tracks and being labelled as "Systems Without Transport Connection".

      I hope there's any expert can clarify this to me.


      Ja'far Sukor