Skip to Content
avatar image
Former Member

How to change route definition in productive client without CR transport?

I don't know why route definition is client-specific object within SAP.

Obviously users is indeed neccessary to change route definition(continually in some cases) but ususally client-specific object in productive client is set to be "No change allowed".

As a result, when users want to change a route in productive client, he have to change it in QA client and transport to productive one. It doesn't make sense and I cannot understand.

Does anyone have a workaround for this? Much thanks.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

5 Answers

  • Best Answer
    avatar image
    Former Member
    Sep 08, 2010 at 10:05 AM

    hi,

    I agree that generally configuration items should be moved via transports and not changed directly in prod. system.

    However, routes definition is specific case. Usually for complex supply chains there are lots of routes maintained with different transit times. And to me the transit time duration or forwarding agent assignment should be treated as a masterdata and not as configuration item. Which I find as one of the mistakes taken by SAP.

    To workaround that you can think of introducing a new transaction which will update route definition tables in background. Or create your own custom tables with route characteristics that would be selected instead of standard SAP ones.

    Regards,

    Dominik Modrzejewski

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      I agreed with Dominik.

      I suppose SAP doesn't consider the real situaiton carefully for this point. Obviously, route and distance on that should be looked as master data.

      It's annoying issue for us for now and we have to plan a Z program to update database directly.

  • avatar image
    Former Member
    Sep 08, 2010 at 03:42 AM

    Hi,

    It is not only with route, but even if you want to change the description of something, you have to make the change in the development system and move across the clients to the production system. This is the universally followed methodology in software deployment. In SAP, it is through transports, in JAVA it is through deployment, but the approach is the same everywhere. So there is no question of doing the configuration directly in production client. This should not be done even at critical times.

    Coming to your case of route definition, this is a configuration which should not undergo frequent changes. If there are changes being experienced here, you really have to think about the process of assigning the routes and reconfigure the entire route determination process to make it suit to the business reqmt.

    However if you want to change the route often, you can change the same in the sales order or delivery at every transaction level. So I think this should not be a problem to you.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 08, 2010 at 05:57 AM

    Hi,

    You can go to tcode SCC4 and change the modification setting in production. However it is not advisable to do that, it is always better to change the setting in DEV and test in QA then only transport to production.

    Thanks.

    Add comment
    10|10000 characters needed characters exceeded

  • Sep 08, 2010 at 10:36 AM

    Hi,

    you can change the table attributtes so that when changing it, it won't create a transport order. Execute SE11 for TVRO table and in tool bar select "utilities" and "table maintenance generator". Here in "dialog table transport details" block, select "no, or user, recording routine" and save. Please check this procedure with an abaper.

    Regards,

    Joan

    Add comment
    10|10000 characters needed characters exceeded

  • Feb 01, 2012 at 08:27 AM

    Note 582328 - Route definition cannot be maintained in production system

    Add comment
    10|10000 characters needed characters exceeded