Conversion of Source System in BI 7.0

Hi Guys,
           We created a Generic Extractor and replicated the datasource (7.0) in BI Development. I have an ODS with Transformations for this datasource. Everything works fine in development. The extractor has been transported to R/3 quality and replicated (7.0) in BI Quality. The ODS and transformation has been transported to BI Quality.
But after the transport, when I look at BI Quality system, the transformations are  not active. The strange thing is that the datasource linked to the transformation still shows the R/3 Dev source system. I can see the datasource itself connected to R/3 QA source system, but the datasource linked to the transformation shows the R/3 Dev source system. It seems to me that something has to happen to change the source system of the datasource linked to the transformation to the R/3 QA system. We have installed SP11.
Can anyone please help me out with this. We are literally running out of time.
Thanks a lot in advance.
Harsha.

It should read like these
You are mapping Dev ECC to QA ECC and BI Dev to BI QA to load Data
Once done you can check these entries in table - RSLOGSYSMAP
should look like these
Original source system                   Target system
ECC Dev                                  ECC QA
BI  Dev                                        BI QA
Hope it Helps
Chetan
@CP..

Similar Messages

  • Conversion of Source system name after transport

    Dear All,
    I need one clarification.
    Say you have developed a fresh modelling in BW Dev server and your source system is R3 dev system. Now you need to transport all the request  to BW Quality system but the source system will be R/3 quality system.
    For this change of source system name we need to maintain some mappings.... From Tools menu there is an option to do this...
    My doubt is in Production server how do we maintain the mapping...
    Quality system ---> Production
    or
    Development system---->Production.
    Hope i am clear....
    Thanks &  Regards,
    Anup

    Hello Anup,
    The question you raised particularly is about the change of source system when your transports are alredy done. For this, i would like to say is that when you do any transports in the R/3 or BW front, the source system change is done only when :
    1. It is done, when you have a single base system and different R/3 (source system)
    2. If you have a single source (R/3) and a single destination (BW Quality), you do not need to map the source system.
    Well, i case that is needed, you may do it via :
    1. Go to RSA1
    2. Go to Tools.
    3. Tools -> Conversion of source system.
    In the right most table column, provide the source system you need to connect with your BW system.
    This will internally connect you with the specified R/3 system.
    Hope it helps!
    Neha.

  • Conversion of source system while transport

    Dear Experts,
    We have following landscape:
    BID (BI dev)
    BIQ (BI QA)
    BIP (BI Prod)
    and
    R3D (R3 dev)
    R3Q (R3 QA)
    R3P (R3 Prod)
    For transport we have made following settings for
    "conversion of source system name after transport":
    In BID system (BI dev)
    BID->BIQ
    R3D->R3Q
    Question-
    -Where do I mention settings for production?
    -Can I make folowing settings in Dev so that it works for all the transport?
    BID->BIQ
    R3D->R3Q
    BID->BIP
    R3D->R3P and no settings in BIQ and BIP environment.
    -Do I need to mention below settings in BIP (BI prod)
    BID->BIP
    R3D->R3P
    Thanks

    Hello,
    Please log into the system in which you are trying to import the transport in and go into transaction code RSA11 and then ino "Tools --> Conversion of Logical System Names".
    In order to change the values the system needs to be modifiable and the person having the change access should be doing this (which would be the BASIS team if the security is set properly).
    So, in BIP system in your case please go into the above path and maintain the entry for BID --> BIP and also R3D --> R3P.
    The whole purpose of doing this is to make sure that the datasources which have the source system property get converted into the appropriate source system names when transported over multiple environments.
    Please assign the points if this answers your question.
    Let me know if you need additional information in this regards. If you don't have the access you can check if these parameters are set or not by accessing the view "V_RSLOGSYSMAP" in the system.
    Thanks
    Dharma.

  • "Conversion of Source System names after the transport" : O

    Experts:
    Environment : BI 7.0 and SP 12
    <b>Tranports related to transformation rules are failing with inactive status...</b>
    Further investigation on this, I have noticed that in our QA system, where "Conversion of Source System names after the transport" : O screen, we have columns
    Original Source System, Target Source System, 7.0, Description(I guess, since no name is found)
    Everything looks fine to me with reference to actual techinical names of source/target system...
    My question there is a check box on column "7.0", which is UNCHECKED. Is this correct?
    My understanding is that, this check box needs to be CHECKED, since this is related " Only Valid for RSDS, TRFN and DTPA Objects ". Is this correct?
    If yes, Can I check this box in QA system, save and retransport my requests. If so, what happens to standard BW objects i.e., transfer ruels, update rules etc...
    OR do i need to create another entry with same source/target system and check the 7.0 box.
    OR do i need to create 3 entries with same source/target system and check 7.0 box for each entry i.e., RSDS, TRFN, DTPA.
    Finally, please advise the exact steps that need to be taken here...pros and cons
    Your inputs will be of great help....
    Thanks,
    BI
    Message was edited by:
            B I

    Hi,
       Yes you need to check the checkbox as it is related to Data sources and transformation and DTPs. you can mark the check box if  your client is modifiable, if not you need to transport the setting from DEV. Go to
    SPRO > Business Intelligence>Transport Settings--> Change Source system name after transport.
    you also need to maintain the Source system IDs .
    Hope it helps.

  • Conversion of source system names after transport

    Hi gurus,
    Please someone can tell me how to configure the "conversion of source system names after transport"  in the BI system as my transport is not working on a new BI System  ?
    Thx in advance

    Hi Firmin,
    You can do this in RSA1 in tools under conversion of logical source system names.
    Here you maintain the development system or the system used for development as the source system.
    You will have to mention the logical name of the development system.
    In the target system column mention the system in which the transports would be imported. This could be the quality system or the production system.Again you would have to mention the logical system name
    Check the folllowing link for more informationn on this.
    [Conversion of logical names|http://help.sap.com/saphelp_nw70/helpdata/en/46/94b1fc87bd13eae10000000a155369/content.htm]
    Hope it helps you ,
    Best regards,
    Sunmit.

  • Wrong conversion of source system after transport

    Hello,
    We ve got a a transport problem in our 3-3 Landscape. Connections for extraction are only between same systems ( f.e. dev to dev)
    BI Dev         BI Test       BI Prod
    R3 Dev         R3 Test      R3 Prod
    The conversion of source systems is on the BI test:
    BI Dev becomes BI Test
    R3 Dev becomes R3 Test
    The conversion of source systems is on the BI Prod:
    BI Test becomes BI Prod
    R3 Test becomes R3 Prod.
    With this it tells me the after transport (BI Test to BI Prod) of objects with source system assignement that the R3 Dev System is not known.
    The transport before from the BI Dev to BI Test worked well without any problems.
    We`ve got the BI Test and the BI DEV on the same host.
    Has anybody got an idea what is wrong?
    Thank you folks.

    It must be R3D (dev system)
    Something like following should be maintained in production
    R3DCLNT100 <u>R3PCLNT100</u> [Assuming R3PCLNT100 is your production system]
    Don't forget to assign points,
    -jayant

  • Conversion of source system

    Hello
    I defined a rule so that source system DRQ is replaced with itself during import from Dev to Test system.
    I know that this rule should be specified in the Transport Connection-Conversion. My question is
    Which system (dev or test) should be used to define the rule?

    Test system, definitely, because this is where the conversion will happen.
    The RSLOGSYSMAP table will store this information.

  • Conversion of source system after tranport

    Hi
    Im planning to to transport BI-Obejcts from DEV to QA . Where can i give
    'conversion of sourcesystem after transport' and how can i give them.
    can i give in DEV or QA .please let me know
    kumar

    Hi Ravi,
    Log into your QA system. Go to RSA1 -
    > Transport connection. Click on the icon Source system conversion or just press F8. Click on new entries in the next screen. Here just maintain the source system conversion. For example in Dev if the R/3 source system name is R3DEVCLNT100 and in QA it is R3QACLNT200 then in the original source system field enter R3DEVCLNT100 and in the target source system field enter R3QACLNT200. All the source system dependent objects like datasources, transformations etc which are assigned to R/3 dev system in BW Dev will be assigned to R/3 QA system in BW QA.
    Similarly maintain entries for all other source systems defined in BI. Hope this helps.
    regards,
    Sumit

  • Transport Issue - no conversion of source system name

    Hi Experts,
    I'm desparetly trying to import an transport request containing a transformation into my PRD System . At stage of method execution it fails with RC=8.
    Error MSG:
    The DataSource MY_DS  (MY_DEV_SYS) does not exist in object version A
    in PROD MY_DEV_SYS should be converted to MY_PRD_SYS, entries in RSA1 are maintained.
    MY_DS  exists in active version in PRD. It seems like conversion of source sytem doesn't take place. Any ideas?
    Thanks in advance
    Joe
    System BI 70, SP21

    Hi Everyone,
    I've experienced the same problem on a BW 7.01 system on Support Pack 6.  I was able to solve it through implementing the following notes:
    - 1412414 (SP24) Content is not generated/transport errors; and
    - 1489612 Objects of the type DTRF deleted after method is executed (supplemental note to 1412414)
    See my reply on the below message for further details:
    Re: Source RSDS DS_CA_CLIFID DBW_150 does not exist
    I hope you found this useful as 'solved with workaround' wasn't particularly helpful to me.
    Cheers,
    Campbell

  • Conversion of source system names

    Hello Experts,
    After having some transport problem (transporting infopackages), I notice that the source system mapping is not the same in DEV compared to PRD.
    Other than change log which was not turned on, is there any other way I can find out who or when was the last change to this mapping table?
    Am I right to say the mapping entries should exist in all systems? My DEV currently only has 1 entry compared to 6 entries in QAS and PRD.
    The source system underwhich the infopackage resides is not shown in the DEV source system mapping table.
    Is this the cause of my transport problem?
    Regards,
    Mirella Russo

    Dear Experts,
    Thanks for the useful information. Points awarded.
    Am I right to say that mapping in target system cannot be transported and is set directly in target system QAS, PRD via RSA1 and no mapping is required even if there are other source systems, like flat file source systems, when the source system name is to be the same in all systems? In this case, my source system is a flatfile. Does this mean I need not maintain it? The 'no mapping' warning received in transport log shows that the flatfile source system concerned exists in the target system but no mapping. As I do not need source system name change, can I say I need not maintain in the mapping table? I still cannot understand why the error come about.
    Many thank you in advance.
    Regards,
    Mirella Russo

  • Conversion of source system names --- error in transport

    hi
    i want to transport my object from Dev111 to Quality222
    but the transport ended up in error 8
    it gave the error...
    Source system PRODUCTION333 does not exist
    I am confused,
    shouldnot it should give error related to Quality system ???
    how should be the mapping in Source system names?
    after research it seems it should be maintained in
    RSA1-TOOLS-mapping of SOURCE SYSTEM NAMES.
    i have following systems...
    BW- DEV111 QUTY222  PDN333
    R3   DEV121  QUTY242 PDN363
    What should the entries look like in which system

    Landscape is -Transport should be send from Deve-Quality---Production
    BW....................................
    DEV111 QUTY222 PDN333
    R3.....................................
    DEV121 QUTY242 PDN363
    CAN you advise if the entries SHOULD look like below in Quality and Production System???
    Quality system should have entries like:
    bw DEV111.............. bw Quality 222
    r3 DEV121................ bw Quality222
    Production system should have entries like:
    bw Quality222.............. bw Production333
    r3 DEV242................ bw Production333
    Q1 ......IS THIS HOW ENTRIES SHOULD BE IN Quality & Production system???

  • Quick question on conversion of source system after transport.

    hello all,
    I have transported all my objects from dev to QA in BW (and same in r/3). Now i want to let it all go to production environment. So do I have to go in rsa1 of BW prod system and make a entry in there ?
    In my BWQAS i have an entry in there
    Original source system               Target source system
    R3DCLNT100                               R3QCLNT100.
    So when i make the entry in BW prod environment what should be source system R3D or R3Q?
    Thanks,
    Raj

    It must be R3D (dev system)
    Something like following should be maintained in production
    R3DCLNT100 <u>R3PCLNT100</u> [Assuming R3PCLNT100 is your production system]
    Don't forget to assign points,
    -jayant

  • Source System conversion

    What is the ideal settings for source system conversion in the following scenario.
    1. Source Systems - CRM, ECC6 (ignore flat file)
    2. Landscape - Dev Qual Prod
    3. System Names
    CRM -- CRD, CRQ, CRP
    ECC -- ECD, ECQ, ECP
    BI -- BID, BIQ, BIP
    4. All clients are 100
    5. Source System Conversion in BID
    Source        Target
    CRD100 -     BID100
    ECD100 -     BID100
    Question: I need the conversion also from the CRM and ECC systems is that correct?
    6. Source System Conversion in BIQ
    Source        Target
    CRQ100 -     BIQ100
    ECQ100 -     BIQ100
    BID100 -       BIQ100
    Question: I need the conversion also from the CRM and ECC systems is that correct?
    7. Source System Conversion in BIQ
    Source        Target
    CRP100 -     BIP100
    ECP100 -     BIP100
    BIQ100 -       BIP100
    Question: I need the conversion also from the CRM and ECC systems is that correct?
    If there are thoughts and/or suggestions otherwise would be appreciated.  Thanks

    Hi Niten,
    I am not sure about you requirement for these source system mappings.
    My guess is, when you transport BI objects from dev to quality or dev to production , you want your BI object to adopt to the source system in the target systems landscape.
    example - If you transport a BI datasource which has the source system name in it, or an infopackage, the in BW dev it would point to R/3 dev and after transport it should point to appropriate source system, that is R/3 qa or prod.
    If this is the requirement, then you need to maintain the settings in RSA1 in Tools--->Conversion of logical system names.
    Log on to QA system and in the 'Conversion of source system names after transport' maintain the source system as dev and target system as QA system. Here you have to maintain the logical names of the systems.
    Do the same in production. PN you need dev to prod in this case not QA to Prod. Consult with your basis to confirm the transport route.
    In BW -> In SPRO ->SAP Netweaver->Business Intelligence->Transport settings--->Changin Source system name after transport
    Click on the page symbol next to it, to read more on this.
    Hope it helps,
    Regards,
    Sunmit.

  • Source System Does Not Exist - Transport Problem

    Hi
    We have the next Landscape in BW 7.0 (Netweaver 2004's)
    LRDCLNT300     is R3 DEV
    LRQCLNT700     is R3 QA
    LBDCLNT100     is BW DEV
    LBQCLNT700     is BW QA
    The connections are
    LBDCLNT100  (BW Dev) use as source system        LRDCLNT300  (R3 Dev)
    LBQCLNT700  (BW QA) use as source system        LRQCLNT700  (R3 QA)
    In RSA1->TOOLS -> Conversion of Logical System Names
    In Conversion of source system after the transport we have these entries
    Source System                    Target System
    LBDCLNT100 (BW Dev)         LBQCLNT700 (BW QA)
    LRDCLNT300 (R3   Dev)         LRQCLNT700 (BW QA)
    But when we transport an order from BW DEV to BW QA show the error "source system LRDCLNT300 does not exist"
    Never made the conversion of source system after the transport.
    Can you help us please.

    Thanks Edwin
         I create a RFC for LRDCLNT300 (R3 Dev) in my BW QA system (Target System).
    I try an order again but it didn't work, also I try to check 7.0 checkbox but I got the message "No entry exists for original source system LBDCLNT100 for 3.x object"
    and I have to uncheck again.
    I still have the same problem the objects are associated to R3 Dev, never make the conversion to R3 QA.

  • Conversion of logical system names in queries

    hello,
    We have the following problem in our multisource model.
    Constant values have been assigned in queries in development : for instance, in line 1, the profit center is restricted to the constant value D3/9000/TTBC600
    D3 : development source system
    9000 : controlling area
    TTBC600 : Profit center code
    When we transport the query, we were expecting a conversion of the source system ID in this constant value but it is not the case.
    could you tell me if this is a normal behaviour??
    If yes, it means that we have to enter constant value in hard code without reference to the source system ID (indirect input, you cannot enter more than the length of the object i.e. TTBC600 in this case) and this can be at the origin of conflict if we have same code in different source system.
    Thanks in advance for any answer
    OD

    Did your transports move up ok to your target system?
    I am asking because your problem could be your mapping of source system to source system ID is not set up correctly or your "conversion of source system names after transport" is not set up correctly in your target system.

Maybe you are looking for