Change of the source system

Hi
all
Background installation from  SAP r/3 was already done and the system is up and running.
Now i would like to replace the SAP R/3 with ECC version , where I must replicate the same extractor now with obviously a different version of  ECC.
I wonder if the source system change will effect the similar infoobjects which were already installed and assigned to a different source system.
Please explain me the effect and defects, or if any changes on the master data already existing.
thanks

When you change the source system - all your transfer rules , data sources etc will be gone and you will have to do them again.
The master data and transacton data will not be affected only that you will have to init the same again and deltas subsequently...
You could instead - keep the old system connection alive and then create a new set of transfer rules , data sources etc for the new system - that way you can have the old Transfer rules , data sources active and then have the coding done the for same alive for reference as well..

Similar Messages

  • Change in the source system

    Dear All,
    We have currently BW 3.5 and CRM R/3 server up and running in Production.
    Now CRM server is being upgrade to CRM 7.0 . Now i being the BW consultant needs to find out what is that needs to be done at BW side.
    My idea :-
    1) We first need to create a new Source system and repllicate all the data sources in bw system.
    2) Assign this datasource to the old infosource.
    3) create an infopkg and try loading the data once again to the old cube.
    We can ahieve this in Dev system and then transport the Transfer rules again to BW Production system.
    Can we directly get this done in Production system????
    Kindly add your idea to this list and suggest if we can do this directly in the Productions system without the need to transport the Transfer rule from Deve system.
    Thanks & Regards,
    Anup

    first, temporarily disconnect the source system connection when the upgrade is started...
    after that as you said, please transport the transfer rules from DEV box to production box. it is not advisble to do directly in production box.
    Since the end user is having access to the production box, it is not advisble to open the production box as modifiable and allow to changes.
    Hence we cannot take long down time isnt..? After upgrade is done, please restore the source system connection.
    Better you dont delete the source system of your CRM system in BI.
    Hope this would help you.

  • 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

  • Change the source system

    Hello
    In our Quality Box , I need to change the source system connection (from QR1 to QR2). I created the new connection successfully. Now the issue is all the Transfer structure still using OLD connection ( i.e QR1) . I run BDLS and it did not word. How can I re-assign the new source system (QR1)  to all of my Transfer structures in one go. Is there any report ?
    Farooq

    Hello,
    You cant directly convert the existing objects for a source system to the new source system.
    For that you need to do a transport of the objects to the QA box while maintaining the entry in BDLS to convert to the new source system.
    Regards,
    Shashank

  • How to change the Source system from ONE DataSource?

    Hi,
    I'm trying to change a DataSource's source system (active with dtp and transfer rules), but it's not possible to  do it in change mode because the field 'Source Sytem' is not enabled. I know I can use the BDLS transaction but I understand that this is for change all Datasources and I only want to change one of all.
    Thanks for your help

    Hi Marcel,
    As I understand apart from file and web services all other data sources are replicated from underlying source system. BDLS transaction is used to change the source system but in case of system copy activity and it is necessary because the data sources points to old source system.
    In your case as I understand you will have to replicate the current data source directly from underlying source system and then build the rest of the flow. May I know how you have got this single data source for which the source system is different?
    Regards,
    Durgesh.

  • How can we change the Job priority in the Source system

    Hi All,
    We are facing an issue with the process chain execution in the Production system. We have a process chain which runs daily in BI system and the chain is designed in such a way, that as soon as the chain starts in BI system,  a corresponding job is triggered in the Source system (ECC  6.0system).
    Now the issue is that after we have our Source system upgraded the memory allocation for the particular Job (FIGL )is reduced and due to which the FIGL job is failing frequently. When we have consulted some experts.They  advised Us to increase the Priority of the Job in source system to A/1, as of now the job is running in B/2 priority.
    Please let us know the way how we can increase the priority of the Source system Job, so that when the process chain triggers a job in source system and that particular jobs  should run with Priority A/1.
    Thanks in advance.
    Regards,
    Chandra.

    Hi Chandra,
    First please find the job name in SM37 for FIGL and check the job status to be in "released" status. Select that job and go to job menu and click on change. then it will take you to the job screen where you have "job class". Here you can change the job class to "A" to get to high priority.
    If you are unable to edit the job then create a new job with the same variants by clicking STEP button in the Job screen.
    Try these steps, let me know if are able to do so.
    Regards,
    Ravi Kanth

  • How to Identify the Source System in a Transformation Rule?

    Hi,
       In a 3.x system if I needed to identify the source system, the interface had a parameter SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS. I do not see the same in a Transformation Rule. Can anyone tell me how can I make a decision in my transformation rule depending on the Source System?
        Say for instance I want to change the following Update Rule from a 3.x System to a Transformation in BI7:
    IF SOURCE_SYSTEM = 'ABC'.
       RESULT = 1.
    ELSEIF SOURCE_SYSTEM = 'A11'.
       RESULT = 2.
    ELSEIF SOURCE_SYSTEM = 'AZ1'.
       RESULT = 3.
    ELSE.
       RESULT = 0.
    ENDIF.
      Can anyone help? Points will be rewarded.
    Regards,
    Kazmi.

    Hi Siggi,
       But how would I know the Request ID within a transformation ? REQUID is the key of the table rsbkrequest ? The interface of the transformation method has the following parameters:
      IMPORTING
        request     type rsrequest
        datapackid  type rsdatapid
        SOURCE_FIELDS
       EXPORTING
         RESULT
    So all I can be aware of is the Request Name and the Data Packet Number. For instance when I took your approach, I got the Request Name as "DTPR_8E3VKVN0RJPDNXAKMP0PZJ99B" now I cannot look up with this against the key of the table because REQUID is a number field. Now, if I look up against the field "Data Transfer Process ID (DTP)" I do not find any entry in this table.
       Any more info?
    Regards,
    Thanks.

  • Error occured in the Source system while loading mater data

    hi all
    While loadng the master data info package.The request is getting failed with error occured in the source system.
    error message says "<b>if the source system is a Client Workstation, then it is possible that the file that was to be loaded was being edited at the time of the data request. Make sure that the file is in the specified directory and is not being edited, and restart the request</b>".
       I had tried repeating the Request but again It is getting failed.
       please help me resolving the issue.
      Thanks(=Points)
          Priya

    Hello Priya
    If u r loading thru flat file
    1. Check the correct path in infopackage
    2. Check if it is opened,if it is then close it and run package again
    If loading thru R/3
    1. Check DS is not opened in change mode
    2. Check if RSA3 is able to extract data...if it is then check in RSA7 and chk IDOC status...
    3. Are you running init..then make sure no document is posted in R/3 side...
    Thanks
    Tripple k

  • Error in the Source system while data loding through Process Chain

    Hi,
    I am facing issue while data loading for certain extractors through Process chain. Load of 0BPM_WIHEAD, 0BP_LOGHIST, OBPM_OBJREL, 0BPM_DEADLINES(there are 2-3 more extractors) is getting failed daily with message Error occurred in the source system and if we repeat the same it is getting executed successfully.
    Regards,
    Javed

    Hi..
    It means that the extraction job is failing in the source system..
    Please check the Job log in the source system  --> Copy the request nimber --> In the source system go to SM37 --> Give * then the request number......execute --> Check the Job log..
    Look there may be multiple reasons behind this....
    1) Connection problem : Go to SM59 and test the connection, If you don't have the access in SM59...then go to RSA1 --> Source Systems --> Right click --> Connection Parameters --> Connection Test
    2) Or may be work processes are not available and due to which jobs are failing due to time out...
    In both the cases you can check with the Basis Team if they can suggest something....or you can change the process chain scheduling time if possible, and schedule it in such a time when less no of jobs are running..
    Regards,
    Debjani..

  • ALE Change Pointers in source system not active

    Hi All,
    I am trying to load 0COSTELMNT using deltas. The initial load is OK and then i use a delta and it fails and i get the error:
    "ALE Change Pointers in source system not active"
    I have carried out the following steps in an attempt to resolve the problem - but it didnt. Anyone have any advice??
    (1) Checked BD61 – to confirm whether the change pointers are active
    (2) Checked BDCP to confirm the number range is maintained
    (3) Checked SALE (Activate change pointers for message types)  to confirm whether the change pointer has been activated for the type we need:
    COCOKA     Control segment CO object/cost element
    COELEM     Cost element master data
    (4) In transaction snum, Selected number ranges and confirmed the intervals are setup
    No. 01
    FROM: 0000000001
    TO: 0000009999
    (5) Activate transfer structure
    (6) Replicate Datasources
    Thanks,

    If you are transferring master data from source system, the BD61 setting on the source system should be checked.
    Why it has been unchecked - not sure (likely someone did it by mistake).
    It shouldn't have any effect on txnl delta. What will be effected though is that you will have lost delta of the ALE based data sources for the period this setting was unchecked.

  • We would like to test old deltas from the source system( copied to new)

    Hi Gurus,
    The scenario is
    They will make a DB copy of the Prod system onto a QA system, the Copied system will have
    its system ID changed(SID) to a new one.
    There will be deltas available in the RSA7, as this is a copy of the  3 weeks old prod
    system. Now the delta's will be available on the Copied system pointing to the BW Prod system.
    We would like to test these delta's to BW Dev. why we would like to do the delta's to the
    BW dev system is to check whether we can do system copies without clearing the delta's on
    the source system.
    After the system copy we will do all the activities necessary to reflect the system changes
    a. Like BDLS, We20, we21,ALE checks, RFCDES, RSLOGSYSDEST, RSBASIDOC, etc on the source system to
    reflect the changes of the BW Prod system to BW Dev system.
    b. Likewise, we will perform all the above activities on the BW dev system by changing the
    existing source system to the new source system( performing BDLS,we0, we21, etc)to reflect
    the new Source system with the new (SID).
    c. We will check the source system connection
    d. Replicate the datasources on the new source system
    e. Activate the Transfer rules for the new source system.
    Now for us to do delta's from the new source system to the Bw dev system we need to change
    underlying tables in source system to point the delta's, arfc TID's etc to the BW dev system.
    We can change the entries in the TRFCQOUT, ARFCCSTATE, ARFCDATA tables to point the LUW's and
    destination to the BW dev system.
    What I presume is if we run the BDLS on the Copied system to change the BW prod system to BW
    and also  the underlying Tables for the LUW's and etc will still be pointing to BW Dev. I would
    like to know if this is the case .
    Lastly, appreciate if anyone can say if this is possible to do without having to clear the
    BW delta queue on the source system.

    Hi Ramesh,
    Appreciate a lot for your response, but i would like to know if we can reflect the entries in table RSSDLINIT(Last Valid Initializations to an OLTP Source) and RSSDLINITSEL(Last Valid Initializations to an OLTP Source)  in the BW system on the copied source system
    tables ROOSPRMSC(Control Parameter Per DataSource Channel), ROOSPRMSF(Control Parameter Per DataSource Channel) by executing the ABAP program RSSM_OLTP_INIT_DELTA_UPDATE after we do the BDLS conversion on the new copied source system.
    After the BDLS conversion I reckon the entries in the RSA7 queue, ARFCCSTATE, TRFCQOUT tables willl reflect the BW Development system instead of the BW Production system isnt it.
    response much appreciated.
    Kalyan

  • Job Termination In the source system (TSV_TNEW_PAGE_ALLOC_FAILED)

    Hi Experts,
       I have a load in bw which extracts the data from R/3.  In the IP selection i have OLAP variable set to 0calmonth and the selection is one month.  The loads gets failed with the page allocation error in the source system.  I tried reducing the packet size with different option.  Still i couldn't complete the load.
    If any one come across with this kind of situation please help to resolve this issue.
    Thanks
    Deepthi

    Hi ,
    Below are the parameters and values for them which are recommended by SAP.There is a SAP Note available for this.ASk yr basis consultant to check the notes.
    ES/TABLE                    SHM_SEGS
    ES/SHM_SEG_SIZE             2048
    em/global_area_MB           250
    abap/heap_area_total        4000000000
    abap/heap_area_dia          2000000000
    abap/heap_area_nondia       2000000000
    ES/SHM_PROC_SEG_COUNT       16
    ES/SHM_MAX_PRIV_SEGS        15
    ES/SHM_USER_COUNT          2048
    ES/SHM_SEG_COUNT           2048
    Need to do a system bounce for the parameter change to take effect.
    Regards
    Balaji

  • Steps in BW after the upgrade of the source system R3 in netweaver 2004s???

    Hi,
    1. Who can tell me which are the steps to execute in BW after the upgrade of the source system R/3 4.6 to Netweaver 2004s (ECC6) ?
    2. Do the delta loads continue to run or must be re-initialized?
    Thanks for your help
    Dominique

    hi Dominique,
    you should take care not after upgrade, but also before upgrade
    or your upgrade has been done ?
    also stated, before upgrade
    If you use Logistic Cockpit, please make sure that you know notes 328181, 396647, 380078.
    These are absolutely prerequisit notes for using Logistic Cockpit.
    Never change the extract structure (communication structure) when there is data in SM13 or in the DeltaQueue!
    Never upgrade your PlugIn System when you have data in SM13 or in the DeltaQueue!
    SM13 and RSA7 have ALWAYS to be EMPTY BEFORE you apply any changes to communication structures, extract structures or any referenced Data Dictionary object or BEFORE you upgrade your PlugIn system!!!
    SM13 and RSA7 have to be EMPTY also when you apply PlugIn Support Packages!
    458305-OLTP system upgrade: What should I be aware of afterwards?
    Note 458305 - OLTP: System upgrade or SP - What should I be aware of after
    Note 301192 - Procedure after upgrading an R/3 source system
    Note 359412, there may be some others
    hope this helps.

  • Customized delta data source for deleting data record in the source system.

    Hello Gurus,
           there is a customized delta data source,  how to implement delta function for deleting data record in the source system?
    I mean if there is record deleted in the source sytem, how to notify SAP BW system for this deleting change by this customized delta
    data source?
    Many thanks.

    Hi,
    when ever record deleted we need to write the code to insert the record in  Z table load this records into BW in a cube with similar structure.while loading into this cube multiply the Keyfigure by -1.
    add this cube in the Multi Provider.The union of the records in the orginal cube and the cube having deleted records will result in zero vale and will not be displayed in report .
    Regards,

Maybe you are looking for