Moving DataSources between source systems

Hi Gurus,
I'm facing problems when trying to move a datasource between two source systems. Here are some details about the situation:
- I created a DataSource based on a DB-Connect source system (Oracle DB)
- I moved this DS to test system where it has been attached to the Oracle-Test-DB.
- Now I'd like to load data in SAP test system from the Oracle-Prod-DB. So I created a new source system in the SAP test environment pointing to Oracle-Prod-DB. Then I updated the conversion of logical systems now changing the source system to the Oracle-Prod-DB. After collecting the datasource and transporting it to SAP test system I noticed that the datasource already existed remained untouched and an additional datasource has been created.
So, can you Gurus share any piece of advice how to change a datasource from one source system to another.
Any help is appreciated.
Thanks in advance.
Heiko

Hi Srini,
Thank you for you´re answer.
I have checked  WE20 and W21. The ports and the partner profiles are created automaticly in BW and R/3 sides, when creating the new source system in RSA1.
The main problem is, that the R/3 can´t send data to BW, although the ALE and RFC configurations are setup properly. After I replicated and activated several data sources in BW succesfully, I´m requesting data from the R/3 system with an infopackage, but after a few hours the follwing failure message occurs in the monitor :
Errors while sending packages from OLTP to BI
Diagnosis
No IDocs could be sent to BI using RFC.
System Response
There are IDocs in the source system ALE outbox that did not arrive in the ALE inbox of BI.
Further analysis:
Check the TRFC log.
You can access this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".
Error handling:
If the TRFC is incorrect, check whether the source system is fully connected to BI. In particular, check the authorizations of the background user in the source system.
In the TRFC (SM58) log in R/3 there appears an status text with the following entry:
"No service for system SAPABC client 123 in the integration directory".
For this entry I have found the SAPnote 940313. In this note,there is described how to send Idocs over Integration Server. Now I think that our R/3 system tries to send Idocs over the Integration server too.
But is there another alternative to send Idocs from R/3 to BW without using the Integration server?
Best regards
Mehmet

Similar Messages

  • Moving datasource between source systems

    Hi Gurus,
    I'm facing problems when trying to move a datasource between two source systems. Here are some details about the situation:
    - I created a DataSource based on a DB-Connect source system (Oracle DB)
    - I moved this DS to test system where it has been attached to the Oracle-Test-DB.
    - Now I'd like to load data in SAP test system from the Oracle-Prod-DB. So I created a new source system in the SAP test environment pointing to Oracle-Prod-DB. Then I updated the conversion of logical systems now changing the source system to the Oracle-Prod-DB. After collecting the datasource and transporting it to SAP test system I noticed that the datasource already existed remained untouched and an additional datasource has been created.
    So, can you Gurus share any piece of advice how to change a datasource from one source system to another.
    Any help is appreciated.
    Thanks in advance.
    Heiko

    Hi Srini,
    Thank you for you´re answer.
    I have checked  WE20 and W21. The ports and the partner profiles are created automaticly in BW and R/3 sides, when creating the new source system in RSA1.
    The main problem is, that the R/3 can´t send data to BW, although the ALE and RFC configurations are setup properly. After I replicated and activated several data sources in BW succesfully, I´m requesting data from the R/3 system with an infopackage, but after a few hours the follwing failure message occurs in the monitor :
    Errors while sending packages from OLTP to BI
    Diagnosis
    No IDocs could be sent to BI using RFC.
    System Response
    There are IDocs in the source system ALE outbox that did not arrive in the ALE inbox of BI.
    Further analysis:
    Check the TRFC log.
    You can access this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".
    Error handling:
    If the TRFC is incorrect, check whether the source system is fully connected to BI. In particular, check the authorizations of the background user in the source system.
    In the TRFC (SM58) log in R/3 there appears an status text with the following entry:
    "No service for system SAPABC client 123 in the integration directory".
    For this entry I have found the SAPnote 940313. In this note,there is described how to send Idocs over Integration Server. Now I think that our R/3 system tries to send Idocs over the Integration server too.
    But is there another alternative to send Idocs from R/3 to BW without using the Integration server?
    Best regards
    Mehmet

  • Display Datasource in Source System -- connects to Production ERP

    Hello,
    We have performed a System Copy of BI Prod. In the copied system on one of the Generic DataSource (ZBIP_VKDFSEXT) when I right click and say "Display Datasource in Source System", it is connecting to Production ERP, supposedly it must be connecting to Dev ERP.
    I have tested RFC COnnections and Logical System Settings in WE20 and 21, but they are pointing to DEV ERP.
    Correct replies appreciated.
    Thanks
    SM
    Edited by: SM on Jul 9, 2011 5:32 AM

    Dear SM,
    I guess we have faced same kind of issue earlier,
    at that time we just removed RFC connection between production system because we are not using Production system connection any more.
    and then just clicked on connection parameter of source-system, there we defined new RFC destination.
    Hope it will solve your issue.
    Regards,
    Ashish

  • ERROR - no available datasource for source system exist

    I tried to load the master for 0Bill_Type
    1) Install infoobject business content and Create infoobject
    2) Activate datasource in R/3
    3) Replicate datasource
    4) Assign infosource ---> the error said no available datasource for source system exist
    When I go to source system--> Object overview --> I don't see anything at all?
    Please advise what went wrong ?

    Hi Pandadda,
    I think you have not transferred the APPLICATION COMPONENT HIERARCHY yet. If not, then do the following:
    1. In your R/3 system execute TCODE = SBIW.
    2. Go to BUSINESS CONTENT DATASOURCES
    3. Execute TRANSFER APPLICATION COMPONENT HIERARCHY by clicking the CLOCK.
    Replicate you datasource then check it on your BW system
    R,
    Adwin

  • Cloning use the different gcc version between source system and target sys

    Hi All,
    Our system is: Application tier and Database tier is split to two servers.
    We should run a cloning, but I found the different gcc version on application tier on source system and target system.
    The source application tier server is RedHat Linux ES3, gcc version is 3.2.3
    The target application tier server is RedHat Linux ES3, gcc version is 2.9.6
    There is the same gcc version on database tier on source system and target system, they are gcc 2.9.6.
    My question: Can I use the different gcc version between source system and target system when I run an erp cloning?
    Thanks & Regards
    Owen

    Not necessarily, you might get some errors if the version is higher and it is not supported by the OS. An example is Note: 392311.1 - usr/lib/gcc/i386-redhat-linux/3.4.5/libgcc_s.so: undefined reference to 'dl_iterate_phdr@GLIBC_2.2.4'
    To be on the safe side, make sure you have the same version (unless you want to give it a try).

  • Is there a dependency between source system patch level (IS-U) and BW 7.3

    Hello everybody,
    we think about upgrading our BW. Now there is the question if there is any dependency between source system patch level (IS-U) and BW 7.3.
    Perhaps someone knows a note. I don't find anything.
    Thanks

    Hello Ingo,
    we have also a Problem with the SSO between BOE Server and our BW Portal. Our Systems are in different Domains and we make all settings in BW as described in the SAP Documentation "http://help.sap.com/saphelp_nw04/helpdata/en/a0/88a340fa432b54e10000000a1550b0/frameset.htm"
    but now we didn´t know what we have to to on BOE side to install the SAPSSOEXT and to get the corret UME Proberties that we have to put into BW.
    Can you help us please on that issue? We can´t find any BOE Documentation for that and we working on that issue now for more then 5 weeks.
    Thank you/Kind Regards
    Evelyn

  • Multiple DataTargets in a BI 7.0 System to One DataSource in Source System

    Currently, I do not have access to BI 7.0 system.  I am wondering whether it is possible to connect MULTIPLE DataTargets of a single BI 7.0 system to ONE DataSource in the source system?  I have searched the forum, but I couldn't find relevant posts.  If I am not wrong, until BW 3.5, once a DataSource is assigned to an InfoSource, it can not be assigned to any other InfoSource of the same BW system.  I have heard that this has changed in BI 7.0 with the new DataFlow concept. 
    The current requirement is that multiple DataTargets of a single BI system need to get DELTA data from the same DataSource in the source system.  If this is technically possible in BI 7.0, should the source system also support such an assignment (since the DELTA load timestamps are maintained in the source system)?  What source systems currently support this feature, if any?  What are the appropriate tables in the source system that I need to look at to do further investigation?
    All the useful inputs regarding these questions will be rewarded with points.  Let me know if you need any further clarification of the requirement.  Thanks!
    Sameer

    Hi Sameer,
    But since there is only one transformation between the PSA and DataTarget, all the data (irrespective of the indicator) will flow through unless I filter on the "planning stage" indicator
    You can create one transformation between Datasource and ONE DataTarget. But in your case, you have TWO datatargets. So you have to create two DTP's which can have diffrent filter parameters.
    You can fill two different targets ( cube1: before manual update, cube2: after manual update) using your datasource.
    For this, you need to create two transformation. Keep in mind, everytime you create a transformation you must create a DTP for data movement.
    So you will have:
    DS1 -- TRANS1-- DTP1 --Cube1
    DS1 -- TRANS2DTP2Cube 2
    In DTP1 set  filter for indicator :X and DTP2 set  filter for indicator :Y. Both DTP1 and DTP2 should work in delta mode.
    I would suggest you to create one initialization for your DS1. if it is not possible create two infopackages for two initializations. I suppose you have the indicator in selection parameters of infopackages.
    Derya

  • Error when activating Datasource in Source System

    Dear All,
    I am gettting this error when activating data source in source system(RSA5).
    1)DataSource 0NETWORK_CUST_ATTR; switch to package PS_IS_EHP3_SFWS_SC is off.
    2) The extract structure DTTV_REC_53 of the DataSource 0TV_REC_531 is invalid
    Message no. R8444
    Diagnosis
    An invalid extract structure has been assigned to the DataSource. An extract structure has to be active in the DDIC. It cannot be a view, since the customer is not able to add append fields for filling in the customer exits to a view.

    Hi
    To use this datasource, you need to install EHP3 package.
    http://help.sap.com/saphelp_nw70/helpdata/EN/b0/7b6c759c494ffcbf821d2442687888/frameset.htm
    Chandu.

  • Datasources from source system replicated as 3.x instead 7.x

    Hello BI Gurus,
    I am Basis consultant and got stuck with an issues with incorrect datasource version replication while trying to create and connect to ECC source system.
    Generally they are replicated as 7.x but this time for some strange reason it is replicated as 3.x.
    We tried RSDS to do mass migration even though we would loose DTP etc but that didn't work.
    We deleted and recreated the system which also replicates the datasources as 3.x.
    The source ECC system is refreshed from production so does the target BI system.
    This is the first time we connected specific ECC system to BI system.
    BI system has multiple ECC system as source system connected to it.
    Please help me asap as our development is on hold since long.

    After making the copy, did you guys run BDLS to convert the former Production Logical System Name to the new name for the ECC environment and did that also to convert the former BW Logical System Name in the new ECC environment to the one it will be connected to?
    If you wanted to use the same IDoc Types you were using in the original system you could use function modules RSAP_BIW_DISCONNECT and RSAP_BIW_CONNECT to disconnect the old reference and connect the new one specifying the same IDoc Type... You should do the same in BW and check table RSBASIDOC to confirm.
    But yes, part of the definition of the Datasources, once you convert them is the logical system name... If it is different from the original all datasources get replicated as 3.x to maintain compatibility... At least that's what I've learnt...

  • Activate all the datasources in source system

    Hi,
    We are in the process of transporting from one development server to another development server.
    In the new development server we replicated all the datasources. But, all of them has come as modified version.
    How to activate all of them once rather than going for one by one?
    We checked some of the R3 datasources as well. Those are perfect.
    Please send an immediate response.
    Thanks in advance!
    lasitha.

    Hi,
    Use the abap program RS_TRANSTRU_ACTIVATE_ALL and give the source system name.
    Hope this helps
    janardhan KUmar

  • Deleted records of tables related to datasources at source system

    Hello,
    The tables related to datasources(RSISOSMAP, RSOSFIELDMAP, RSOSOHIE, etc...)  in source system are without records and  basis team does'nt know what happened.
    Do you know any transaction or procedure in source system that can clear those tables?
    Do you know if the transaction BDLS can cause this?
    Source System -> SAP-R/3-ECC 6.0
    BI System -> SAP-BI 7.0
    Tks
    Portella

    The problem was solved with replicate DS in BW
    Tks
    Portella

  • How to recover a datasource from source system

    Dear Experts,
    i am trying to find a datasource(0PS_PRJTYPE_ATTR) in the source system. For some reason, I could only find the text one, not the attribute one. I checked in RSA5, RSA6 and RSA2. I couldn't find it.
    What are the possible ways to recover the datasource, not sure if someone has deleted it.
    Its really urgent, Please guide me.
    Regards
    Shanthi

    Hi,
    The same should be available in the source system (DEV), Surprising how / why the same is available in BW system.
    I checked the SAP ERP source system to which I have an access and the same is not available in the source system not in the BW system
    My sugession is to go for a generic datasource after identifying the table with the help of functional consultant.
    Regards
    Venkata Devaraj

  • Connection between Source Systems and BW

    Hello,
    I´m trying to connect our SAP BI 7.0 system to SAP R/3.
    At the following link, the topics for connecting BW with SAP source systems aren´t mentioned in detail:
    http://help.sap.com/saphelp_dm40/helpdata/en/00/dc54384ac9a81be10000009b38f8cf/frameset.htm
    I already have setup and tested the RFC-connections, so I primarly need a step by step description for the ALE settings (Partner profiles,Port, IDoc types,IDoc segments) in the
    context of BW-SAP R/3 connectivity.
    Thank you for your postings
    Best regards
    Mehmet

    Hi Srini,
    Thank you for you´re answer.
    I have checked  WE20 and W21. The ports and the partner profiles are created automaticly in BW and R/3 sides, when creating the new source system in RSA1.
    The main problem is, that the R/3 can´t send data to BW, although the ALE and RFC configurations are setup properly. After I replicated and activated several data sources in BW succesfully, I´m requesting data from the R/3 system with an infopackage, but after a few hours the follwing failure message occurs in the monitor :
    Errors while sending packages from OLTP to BI
    Diagnosis
    No IDocs could be sent to BI using RFC.
    System Response
    There are IDocs in the source system ALE outbox that did not arrive in the ALE inbox of BI.
    Further analysis:
    Check the TRFC log.
    You can access this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".
    Error handling:
    If the TRFC is incorrect, check whether the source system is fully connected to BI. In particular, check the authorizations of the background user in the source system.
    In the TRFC (SM58) log in R/3 there appears an status text with the following entry:
    "No service for system SAPABC client 123 in the integration directory".
    For this entry I have found the SAPnote 940313. In this note,there is described how to send Idocs over Integration Server. Now I think that our R/3 system tries to send Idocs over the Integration server too.
    But is there another alternative to send Idocs from R/3 to BW without using the Integration server?
    Best regards
    Mehmet

  • Runtime error while activating LO Datasource in Source System

    Hi Gurus,
    I have followed the below steps to activate the SD related LO extractor in ECC
    1. RSA5 --> Select all the 2LIS_11,12&13 data source and activate
    2. LBWE --> Choose the 2LIS_11,12&13 data source and activate.
    Upon execution of the second step , the system return me the following runtime error
    Runtime Errors         DDIC_TYPE_INCONSISTENCY
    Date and Time          07.07.2011 10:14:29
    Short text
         Inconsistency in the Dictionary for the structure "MCQALSB".
    What happened?
         Error in the SAP kernel.
         The current ABAP "SAPLMCEX" program had to be terminated because the
         ABAP processor detected an internal system error.
    Error analysis
         There is an internal system error.
         eliminated with ABAP/4.
    Trigger Location of Runtime Error
         Program                                 SAPLMCEX
         Include                                 LMCEX$04
         Row                                     26
    With this error i cant proceed to activate any of the LO data source
    Please help
    Thanks in advance

    The table MCQALSB need to be activated in SE11 and LBWE works fine

  • 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.

Maybe you are looking for