Source system is changed

Hi Gurus
Currently we are facing a big technical problem.
Our old sourcesystem client is 200 but it is changed to 400 now
But all the source system assignments for infosources are based on client 200
is there any solution for this issue
Thanks in advance

I think you can use BDLS program to convert the logical name of source system.
[Note 121163 - BDLS: Converting logical system names|https://service.sap.com/sap/support/notes/121163]
http://help.sap.com/saphelp_nw70/helpdata/en/d7/9c73631d6c11d2a56e0060087832f8/frameset.htm
and related notes
[Note 886102 - System Landscape Copy for SAP NetWeaver BW|https://service.sap.com/sap/support/notes/886102]

Similar Messages

  • DS-BW:Data load called from BW failed after Source System program_id change

    Hi,
    In my BW 7.0 instance I have Data Services 3.2 as source system.
    Some time ago I have changed instance of Data Services I am connecting to - I just changed PROGRAM_ID in RFC connection parameters for that source system.
    Since that time when I am trying to execute infopackage to call a job I am getting following error:
         OCI call <OCISessionBegin> for connection <xxxxxxx> failed: <ORA-01017: inv
    where <xxxxxx> is Oracle database connection name for Data Services instance I connected originally.
    What can be reason for that?
    Regards,
    ak

    In Data Services Server Manager on DS box there were configurations for job server I connected originally and for the other job server. After removing original config it works fine.
    ak

  • RSA1 - Source system connection : Change in logical system name

    Dear friends,
    Can you please tell me how can i change the logical system name for a source system connection.
    There is no change in source system & source system connection check works well, just we have decided that from current logical system name SID_100 should be changed to SIDCLNT100.
    Can i do this by running BDLS in BW for RSBASIDOC table from SID_100 to SIDCLNT100 ?
    thanks
    ashish

    HI Sunny,
    This is not the same problem, may be similar though..i am not getting a way.
    let me describe u in a bit more details.
    Currently, we have a working source system connection to a system SID_CLT.  there is no change in source system.
    now, can i change this system connection technical name from SID_CLT to SIDCLNT*** .. 
    thanks
    ashish

  • Source System IP changed

    Hi BI Basis Gurus,
    Please can you suggest:
    Our source System IP has been changed , is replication of datasources , infosources etc the only option?
    Do we have any mapping method which saves us form replication .....
    What should be the ideal steps to follow in this case
    Please reply ASAP
    Manish

    Hi
    Once you maintain your new ip address in the sm59, you may need to replicate the data sources...if still you get problem then you may need to activate transfer structure using program 'RS_TRANSTRU_ACTIVATE_ALL'...
    if your source system id is changed then you need to maintain it in rsa1-tools--assignment of sources systems to source system ids....
    Hope it helps
    Thanks,
    Teja

  • Source system icons changes when connecting SAP BW to mySAP ERP 2004

    Hi,
    Just an Interesting observation in relation to the creation of source systems in SAP BW to SAP Web AS 6.40 based systems (mySAP ERP 2004, mySAP SRM, etc).
    I thought it would be interesting to share!
    The behavior is logical but can be a surprise for a BW administrator who is not aware of the new internal SAP BW systems within mySAP ERP 2004.
    Scenario:
    The customer was connecting a stand-alone BW system to two new systems with latest and greatest mySAP ERP 2004 (ECC 5.00) and mySAP SRM.
    Observation:
    In the past the SAP R/3 source system would be created with a "SAP R/3 icon" indicating a SAP Source system.
    <b>As of mySAP ERP 2004, the source systems will be created in the SAP BW standalone system with the "SAP BW System icon".</b>
    Note: This is also the same behavior for new releases of mySAP SRM, and other SAP applications that are <u>based on SAP Web AS 6.40 or greater</u>
    Why?:
    The standalone SAP BW system is connecting to a system that contains an internal SAP BW system. The standalone SAP BW system determines that it is possible to extract <u>both</u> from the internal BW System <b>and</b> from the Plug-in extractors. It simply denotes that this source system is a SAP BW system and uses the BW Source system icon. (Remember SAP BW is client independent*!).
    Note: This behavior will still occur even if you do not use the internal SAP BW system within mySAP ERP! It is there whether you use it or not.
    Second Note: You can still use the ERP Content extractors from the mySAP ERP Source System as you did in prior releases.
    Another related observation:
    I would expect that this case will probably be true even if you only use the internal SAP BW.
    Scenario: You use the internal SAP BW in another client in the mySAP ERP system than your ERP processing.
    Result: The connection between the BW client and the ERP client source system(s) (i.e. client 001 for ERP, client 100 for BW), both the 'myself' and ERP client source systems, will show up as BW source systems!
    Source system 001 and source system 100 will be displayed as SAP BW icons because SAP BW is client independent*
    user master and authorizations are client dependent
    I hope this was interesting.
    Cheers,
    Mike.

    Hello,
    I used my user id to login. I recieved a message :
    User already exists in source system  I continue:
    Anothre window pops up : "Check  RFC connection" and it asks
    'RFC connection already exists in source system . Do you want to check, use or cancel source system connection'
    Here I select Use - but i get an error : Error in source system'.
    how can i track down this error.
    Kindly inform.
    Regards,
    Nikekab

  • Transport managment, source system changed in import

    Hi all,
    i faced with the need to change the source system in transport management. I mean, dev source system to assign a different test system source. now is the following:
    InfoPackage ZPAK_4MSK400H4M9FGMEKV9ZGDSN4M, source system LGDCLNT300 changed by source system LGTCLNT010 in import (tr STMS).
    I'm looking for opportunities to change the target source systems LGPCLNT010.
    Where can I find a setting to change the source system during the import?
    Thnx.
    PS LGPCLNT010 source system already exists in test. only need to assign LGDCLNT300 (DEV) -> LGPCLNT010 (TEST).

    Hi,
    The entries  are maintained in table RSLOGSYSMAP. Goto SM30 put the table name and click on maintain.
    Or simply goto transport connection from RSA1 and click on "Conversion button" on tool bar.
    Regards,
    Durgesh.

  • 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

  • The detailed procedure after  of BW source system.

    Hi all.
    our BW source system was changed to another new R/3 system
    from PRDCLNT131 to  QASCLNT100.
    the source system of All datasources in BW  was PRDCLNT131 butd now we should  change the source system to QASCLNT100 and we should re-create all transformations and  DTPs for every  datasource  !!
    With BDLS, Could the source system be converted  from PRDCLNT131 to QASCLNT100  ?  Could the transformation and DTP    be converted  by BDLS ?
    If yes,  How to do converted the source system and transformation and DTP ?
    Please give me detailed procedures.
    Thanks in advance.
    shon,

    Hi Pedro,
    this has no impact and you can ignore it. When you look in table RSBASIDOC you will see that the SRCTYPE is not 3 but something else (D I guess).
    This column is only relevant for the way the system is displayed in RSA1, so it does not really matter.
    Best regards,
    Ralf

  • Changing the source system in QA

    Hello All,
    I just wanted a quick opinion from your experience on the following issue:
    We  have a ECC Dev client 20 connected to BI Dev client 20
    Similarly we have ECC QA 120 connected to BI QA 120
    But due to some reason we now want to connect a new ECC QA client 150 to BI QA 120 and take out ECC QA 120 totally(120 is wiped off).
    I already have a lot of development transported to BI QA where the source system is ECC 120. Now if 120 dies and we pull the data from 150, what are the pitfalls to watch for?
    Like all my Master data objects , DSO and Cubes still point to ECC QA client 120 but now the "actual" source system is going to be ECC QA 150.
    Points,
    Gaurav

    You need to replicate all the data sources in BI from QA 150 and change the source system assignment to 150 instead of 120.
    Also, you need to reinitilase delta for delta enabled extractors.
    Two  things to watch out:
    1.  If you dont have source system identifier,  then if you happen to get records with same key, then it will overwrite. This applies to both master and transaction data.
    2. For transaction data that is not delta enables, there may be a possibiltiy with which the records will get duplicated. So, better to delete the old requests before reload the data from QA150.
    Ravi Thothadri

  • How to change the source system for just a datasource

    Hi,
    Our test/development BI system ( BI 7.0 Unicode ) is connected to our development system and to our test system, 1 BI system connected to 2 R/3 systems.
    During some time, the test system won't be available so all datasources that point to the test system must be connected to the development system. In RSA1 is not possible to change the source system in a datasource: RSDS 057
    'Creation of DataSources for SAP source system D30CLNT007 is not permitted' , same error trying to copy the datasource,.
    Any idea about how to proceed ?
    Regards,
    Joan

    Hi,
    If I try to repliclate metadata in the datasource, message RSAR 051 appears: 'error when opening an RFC connection'. This error is expected because the logical system pointed in the datasource does not exist.
    Is not possible to change the source system in datasource ( in RSA1 ) because the field is always greyed, also if I try to copy the datasource the message RSDS 057 appears.
    Any idea about how to proceed ?
    Regards,
    Joan

  • What are the changes to be done on BW end during hardware change of source system?

    Hello Gurus,
    There is some hardware changes happening and I need help in certain things which I need to do from BW point of view.  First of all, I have attached a figure showing my system landscape.  I would kindly request you to go though the fig first.
    For QA, initially we were using AG3 as the source system, now they have made the hardware changes, made a system copy of AG3 into the new system AEQ.  We have connected our BW QA system to this new system AEQ.  Now when I check the system, there are no data in set up tables (I am using SD and MM), but there are data in tables.  But when I replicate data sources from AEQ to BW QA, the existing transformations and DTPs will disappear. So, that left me with 2 options-
    1. Either transport old transformation and DTP from BW DEV to BW QA
    2. Or create new transformation and DTP in BW QA system.
    Can you experts please suggest me what should be the solution?
    Also, please note that, the basis team started the hardware changes with ECC QA system for some reason.  Once ECC QA is fine, they are planning to make the changes in ECC DEV system (from AG2 to AED).  Currently, AG2 is connected to BW DEV and AEQ is connected to BW QA.
    Can you please suggest me whether there will be any issue if we opt to transport transformation and DTP from BW DEV to BW QA when BW DEV is still connected to old source system?  Or, is there any other easy way to sort this out? Please suggest?
    Thanks a lot
    Rakesh

    Hi,
    1. Either transport old transformation and DTP from BW DEV to BW QA?
    Yes, better to transport from bw dev to bw qa
    2. Or create new transformation and DTP in BW QA system?
    at BW Quality, creation may not be possible. Better to transport from bw dev to bwq.
    or use standard abap program to activate transformations and dtp.
    When changes are applying at source then you just need to take care the delta queues
    clear all queues by running related V3 jobs and delta info packs. make them as 0 count.
    once basis team was done changes later try to check your delta loads at bwq .
    Thanks

  • How to Change Source system type of ECC6.0 in BW system

    Hi BW Experter,
       I connected ECC6.0 PRD system with BI7.0 PRD system  , the connection is successful,
    but the source system type of ECC6.0 PRD is not collect . The ECC6.0 PRD is as a
    BW system type in the source system list of bw system  .
       I found that Tcode RSA1 has ever been run in PRD ECC6.0 , So I did a connection testing of
    ECC6.0 QA with BI7.0 PRD .  
         Step 1. Connect ECC6.0 QA with BI7.0 PRD , ECC6.0 QA was as SAP system type in  source system list of bw system .
         Step 2. Run tcode RSA1 in QA ECC6.0
         Step 3. Delete connection of  ECC6.0 QA with BI7.0 PRD .
         Step 4. Connect ECC6.0 QA with BI7.0 PRD again , ECC6.0 QA was as SAP system type in source system list of bw system .
       I want to know how to change ECC6.0  PRD  source system type to SAP .
    If it can't been change to SAP ,Is there any impact when  ECC6.0 PRD  is as bw system type in source system  .
    Thank you for your help .

    I got the soulution from note:  1087980 - ECC Source systems appearing in BI folder
    Summary
    Symptom
    Source system connection for an ECC system appears in the BI folder, rather than in SAP folder, as expected.
    Other terms
    Wrong folder,RSA1, RSBASIDOC, RSAP_BIW_DISCONNECT
    Reason and Prerequisites
    Transaction RSA1 was inadvertently used on an ECC system , thereby creating a 'Myself' source system entry in RSBASIDOC table
    Solution
    This is just a display issue and does not cause any operational issues. Therefore, it need not be corrected, especially if the ECC system in question is used as a BI system as well.
    If it is absolutely required that the ECC source system appear in the correct folder, perform the following steps.
    1. Check that an entry with SRCTYPE 'M' exists in table RSBASIDOC table of ECC source system.
    2. Note the values for SLOGSYS and RLOGSYS. It should be same.
    3. Run the function module RSAP_BIW_DISCONNECT in the ECC system.
       NOTE: Never run that function module in a BI system!
    4. Enter the following values : 
    I_BIW_LOGSYS   <RLOGSYS> as noted in step 2
    I_OLTP_LOGSYS  <SLOGSYS> as noted in step 2
    I_FORCE_DELETE <X>
    < DO NOT ENTER ANY VALUE IN THE FIELD  - RFC target sys !!!!! >
    5. Go to RSA1-> Source systems in the BI system connected to the ECC system.
    6. Select the ECC source system and select RESTORE in the right click menu.
    Now the ECC system should appear in the SAP folder.
    If running RSAP_BIW_DISCONNECT results in an error like OTHER_ERROR, please check if a valid RFC connection exists in transaction sm59.
    If the myself source system connection cannot be deleted in any case, log a service marketplace message with SAP Support.
    Edited by: fang frank on Jul 15, 2009 8:31 AM

  • Does not allow to change source system in Variant

    Hi Gurus,
    I am creating a variant for the program RSIMPCUST, but it does not allow me to change source system name. It is showing me gray color. Do you how to fix this issue ?.
    Thanks
    Liza

    Hello Liza,
    Did you try my solution?
    [Re: Change source system name in variant in BWQ]
    There are solutions to change variants properties, but that particular program has the logsys parameter not able to change, so you cannot change the value of that variant (only with debug).
    It's best to go for that solution I already provided to you...
    Diogo.

  • Change source system in Dev

    Hi
    I have a dev system that is mapped to 2 source systems, R/3 clients (clients 245 and 246) and datasources are mapped to either of these systems.  One of these R/3 clients (245) has now been deleted and I want to convert all of the datasources that pointed to it to the new client (246).   I want to convert only the datasources pointing to the old client (245), but not change those that are already pointing to the new client (246).  Would BDLS help in this situation.
    Thanks in advance
    Simon

    you can do these:
    1 )  change in SM59, the source r/3 qlty to point to your dev server. That should do the trick without making a lot of changes. once you change the source system via this option, you have to perform a check/restore (so that the partner profile in dev system can be updated), replication and activation of the transfer structures.
    2) You can also ask your BASIS guy to run program for BDLS that changes the system pointer.

  • Change source system in Infosource

    Hi
    I am working on BI7. I have one isse. For an infosource source system has been assigned to client 100. I would like to change it to 200. Pl let me know how to make this change.

    Hi
    I didn't get your question,how a infosource is assigned to source  system,your data source will be assigned to source system and your infosource and data sourece will be assigned to each other..
    delete the datasource from source system 100 and create a data source in 200 and assign it to your infosource(i am considering both 100 and 200 source systems are assigned linked to your BW system via RFC(SM59))..
    Hope it helps
    Thanks
    Teja

Maybe you are looking for

  • Creation of new Row in Tree Table

    We are creating a new row using CreateListener which is written in Bean, after creating the row, we are adding it to the iterator and the new row is not getting highlighted and focus is not in new row in the table by default. It takes an click to mak

  • Batch number maangement , Attribute1 & 2

    Hi, Experts, Pls advise where to find the manual for batch managment in how to operate this function. The attribute 1 and attribute 2, what're those for? Thanks. Emily

  • How do I safely get rid of a partition?

    hi i recently bought a powrmac g4 off ebay with a 933 Mhz processor, 1.25 GB RAM and a 120 gig HD that was partitioned into 2 drives (by, i assume, the previous owner) with one of them running the OS. I just installed a new shiney Maxtor 200 gig HD a

  • Training videos for OS X

    I recently bought an iMac for my parents, who are seniors without even basic computer skills. Does anyone know of a good video instruction course for Mac which will cover everything from fundamentals, such as mousing, to basic OS skills? iSight/iChat

  • ADS LogonWithAlias - cannot logon with alias user id

    Hi, We have Erec and use ADS.  Now when the candidate enters their detials - such as logon id - into EREC, the SAP ERP backend generates a random user id and their logon id in put into the alias field in the SAP record (SU01) btw we use ABAP for the