Skip to Content

InfoPackage LogicalSystem change at transport

Hi BW-Guys,

we have a normal 3-Tier BW System landscape. I create my Info Package in the DEV-System and Transport them to QAS and PROD. I Setup the "Conversion of Logical System Names" correctly because the mapping works fine for all other source-system dependent objects like e.g. transformations. But when transporting infopackages to QAS and PROD it does not do the mapping and keeps the original logical source system.

As a result the info package doesn't appear anywhere as it is not correctly linked to any source System. I normally change the source System directly in table RSLDPIO. After that it works fine.

Does anybody knows this behaviour and has an idea how to fix it?

Thanks an Regards

Frank

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Best Answer
    Nov 03, 2015 at 10:27 AM

    Hi Guys,

    Thanks for your effort but I found the solution by my own. I should read SAP Notes more carefully ...

    It is a Bug and already mentioned in a SAP Note: 1965709 - Transport InfoPackage overwrites executable version, warning RSAR485 in transport log

    After changing the table the Transport works well and my InfoPackages look perfekt.

    Frank

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 03, 2015 at 09:01 AM

    Hi Frank,

    Just a question, is 7.0 unchecked in "Conversion of Logical System Names"?

    BR

    Ondrej

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 03, 2015 at 08:58 AM

    Hi Frank,

    Once you done source system mappings at dev system, have you tried to load data to psa?

    please check source system connectivity.

    At Dev system try below points.

    1. Replicate your data source from dev source system to dev bw and activate it.

    2. Later move your Dev source system data source to Qua/Prod source system.

    3. Replicate data source to BW Qua/prod respectively.

    4. Move data source from bw dev to bw qua/prod.

    5. Once your data source was active then transport info pack to bw qua/prod.

    Move rest of the data flow objects in sequence.

    Please check/change logical mappings at table RSLOGSYSMAP at BW/Source.

    Thanks

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Frank

      From your points, all settings are good and all other objects except infopackages are moved correctly. Table entries like RSLOGSYSMAP are maintained properly.

      I would like to request to do a sample data load by triggering the infopackage. did you try that? If so, is the data getting extracted from dev source system or quality source system?

      Logically, if your datasource is pointed to quality source system, your infopackage should also fetch data from quality.

      Could you please check this and let us know

      Also could you please transport the infopackage along with your datasource once to see if any changes are there.

      Regards

      Karthik

  • avatar image
    Former Member
    Nov 03, 2015 at 09:08 AM

    Hi,

    It can be done multiple way. Few I am listing down.

    * RSA1->TOOLS->Conversion of logical system names ( ctrl + F12). Maintain the source system in source and Target

    * Via STMS by the basis team. There is option to specify the logical system.

    * Via BDLS. Normally used after system copy.

    hope this helps!!

    Thanks

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Jugal,

      for me it seems that everything is maintained correctly in "Conversion of logical system names" - it it just ignored during the transport of info packages (only). I did this kind of cusomizing several times before but on this system it just doesn't work.

      Frank