Reconnect of a R/3 source system afer a BW system copy

We want to copy our BW 3.0b development system as a BW sandbox system in order to try out the BW 3.5 migration.
Therefore, we performed a system copy of our BW DEV system to a new machine. On the BW-side we ran BDLS to get a new logical name for the system and defined a RFC connection to our R/3 Dev Source System (incl. appropriate RFC users).
On the R/3 side we also defined an additional RFC connection to the "new - just copied" BW-system.
While trying to reconnect our R/3 Devopment source system within the new BW we encountered the problem that the R/3 system recognized that there already exists a connection to a BW (the old BW dev). If we take this option, the old connection is deleted and a new one is defined. However, from the R/3 perspective we want two BWs connected. It seems the problem has to do with the IDOCs and TRFC port definitions, because the IDOC type ZRSBW010 seems to point to the wrong system.
Unfortunately, we are stuck at the moment.
Any kind of help or hints to relevant SAP documents would be much appreciated.
In the OSS we found some notes on this topic (325525 etc.) but we still not sure how to proceed.
However, in general, we think it shouldn't be a problem to have one R/3 connected to several BW's or is it?
Frank Schülke, E.ON Ruhrgas IT, Germany

We worked out this scenario.  Our solution came with an interpretaion of SAP documentation including SAP Note 886102, obsolete (but informative) SAP Note 184754, and the document How to... System Copy in SAP Business Intelligence System Landscapes - May 2005.
Basically the steps are...
-Using the BW transport collector in the source BW system, collect, release, and export all objects related to the R/3 source system.
-Perform the system copy of the source BW system to the target BW system.
-Change SM59 destinations in the target BW system to the R/3 source systems to invalid hostnames.
-Delete the R/3 source system definitions from the target BW system (the nonsensical hostnames in SM59 ensure you will not make any changes in the actual R/3 source systems).
-Use BDLS to change the logical system in your target BW system.
-Recreate the R/3 source system definitions in the target BW system, this step will make corresponding config for the target BW system in the R/3 source system.  It is important here to activate and replicate.
-Ensure that table RSLOGSYSMAP has the correct entries for your R/3 source systems
-Import the objects you collected in the first step into your target BW system.

Similar Messages

  • 'Error Occured in the Source System' for Non SAP system

    Hi Gurus,
    We have an Info Package which is getting the data from the Source System 'DOCP' and it has failed due to 'Error Occured in the Source System'.Since the source system is Non SAP system there is no option 'Replicate Data Sources'.So,First I activated the transfer rules by the program and ran the package again .But again the same error occured.
    Please suggest me how to proceed for this error for Non SAP Systems?

    Hi,
    Check the RFC connection in SM59 and reactivate the source system again.
    Hope this helps..
    Thank you,
    S R.

  • ORA-01653: unable to extend table SYS.SOURCE$ by 64 in tablespace SYSTEM"

    Hi,
    While creating a package the , I got the following error.
    "ORA-00604: error occurred at recursive SQL level 1
    ORA-01653: unable to extend table SYS.SOURCE$ by 64 in tablespace SYSTEM"
    Could anyone please explain, how to solve this problem.
    Thank you,
    Regards,
    Gowtham Sen.

    solution: increase the size of the system tablespace.
    the text of all pl/sql objects is stored in the database by sys. packages, procedures, and functions are stored in sys.source$ (which is part of the USER_SOURCE view definition). so, you've created a lot of pl/sql, and the table wants to extend, but there isn't room.
    this is a major problem, because it means that nothing in system can extend. add another datafile, or put the tablespace on autoextend.

  • Source system mapping between BW systems

    Hi All
    I have question regarding source system mapping between BW systems
    We are in BW7 and we still have BW3.5 objects (Cubes,IO,ODS ets)
    We have 1 source in BW Dev that need to split to 2 different  sources in BW QA
    e.d BW Dev map to ECC Dev 110 and when we transport ,it should map
    to 2 sources  ,one is ECCQA Clinet 200 and another map to ECCQA Client 210
    in the conversion in BW QA we have mapped it to the 2 ECC QA sources but 
    the problem is that if we would only work with BW7 objects this will work but since we have
    also BW3.5 objects  the  mapping in not complete for the 3.5 objects , we also checked the 7.0 button in the conversion and it still have missing objects

    Hi... i dont understand your isse you have one source of transport and in the destination if points to two systems and this works for you....and your problem is in 3.5 objects? its a version problem?
    Regards

  • Error Message When I Invoke my web services : Exception source is: mscorlib' , Stack Trace :System.Runtime.Serialization.SerializationException: Type 'System.ServiceModel.ExceptionDetail' in Assembly 'System.ServiceModel, Version=4.0.0.0, Culture=neutral,

    Exception source is: mscorlib' , Stack Trace :System.Runtime.Serialization.SerializationException: Type 'System.ServiceModel.ExceptionDetail' in Assembly 'System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' is not marked
    as serializable.
       at System.Runtime.Serialization.FormatterServices.InternalGetSerializableMembers(RuntimeType type)
       at System.Runtime.Serialization.FormatterServices.GetSerializableMembers(Type type, StreamingContext context)
       at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitMemberInfo()
       at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitSerialize(Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter, ObjectWriter objectWriter,
    SerializationBinder binder)
       at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Write(WriteObjectInfo objectInfo, NameInfo memberNameInfo, NameInfo typeNameInfo)
       at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Serialize(Object graph, Header[] inHeaders, __BinaryWriter serWriter, Boolean fCheck)
       at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize(Stream serializationStream, Object graph, Header[] headers, Boolean fCheck)
       at System.Runtime.Remoting.Channels.CrossAppDomainSerializer.SerializeObject(Object obj, MemoryStream stm)
       at System.AppDomain.Serialize(Object o)
       at System.AppDomain.MarshalObject(Object o)
       at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
       at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
       at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
       at System.Windows.Application.RunDispatcher(Object ignore)
       at System.Windows.Application.RunInternal(Window window)
       at System.Windows.Application.Run(Window window)

    Hi,
    The forum is main about installation problem of .NET Framework. Your problem is out of support in the forum. You should post your thread to the forum:
    https://social.msdn.microsoft.com/Forums/en-US/clr/threads
    Best Wishes!
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place. <br/> Click <a
    href="http://support.microsoft.com/common/survey.aspx?showpage=1&scid=sw%3Ben%3B3559&theme=tech"> HERE</a> to participate the survey.

  • SMSY Data Source changes after performing Managed System Config

    Hello everyone,
    I am working with Solman EHP1 SPS26.  I have setup up my central SLD to push system data to my Solman local SLD which is then retrieved from Landscape Fetch to SMSY.  Initially, everything seemed to be working and all data sources reported SLD.
    However, once I performed the Managed System Confirguration wizard for a particular technical system, that systems data source would change to TMS/RFC under SMSY.  It's actually not even that consistent.  For example, the server says source is RFC, the product system says TMS/RFC and some of the product instances still say SLD.
    Is this normal for this to happen after connecting a managed system?  Will these systems still be updated via the SLD considering SMSY_SETUP is configured to use the SLD?
    Anyone's help would be greatly appreciated.
    Alex

    Hello,
    If you notice in SMSY this is not an editable field.
    It is reporting the last datasource used.
    Thefore when you made a change via managed system setup that became the last data source used.
    So yes it is normal to see this change.
    If you have configured the datasource to be the SLD, it should continue to update these systems.
    Where you need to watch out is making manual changes in SMSY, as the SLD can view this as a different system to the SID it knows and will generate systems with known SIDs appended with a suffix variable to distinguish it, as the SLD will not overwrite manual changes, and will create new systems instead.
    But the field in SMSY reflects the last data source used.
    Hope this helps some.
    Regards,
    Paul

  • Source System changes from SAP System to BI Warehouse on ECC activation

    We are in the process of building a new development environment from an existing development environment.
    After copying from system backup in the new development environment we performed BDLS to map to new source systems. At this point of time the source system for ECC ("SAP System from Release 3.0E" was changed to type "SAP Business Information Warehouse".
    Why does this happen?
    How can we prevent this?
    Thanks for your help.

    Hello.
    Please check the following note if ti can be helpful to fix this issue.
    1087980-ECC Source systems appearing in BI folder
    Thanks,
    Walter Oliveira,

  • Source System Refresh with BW system Connected

    Hi SDN Gurus,
    We are doing a source system refresh for CRM 5.0 Production to CRM Quality.My question is the source system of the BW system will be Changed and the BW Quality will have old data. What are the Post Activities which needs to be done in BW 7.0 system after the CRM system is refreshed.
    So that the Quality BW system which will be now Production can have fresh data from Production System of CRM.
    Thanks and Regards
    Vishwanath

    Hi Ravi,
    Thanks for the same.
    I have another issue. My CRM Reports BI 7.0 is being displayed in Enterprise Portal, We have defined variables for user entry and they can select the values from the selection screen of the variable.
    Let's say we have 80 thousand records and we have variable let's say Client Name, where the user wants to select his client name and display records for that client. The Screen shows him only 72 rows of data i.e nearly 1000 records of Client Name. But we have nearly 20000 client names, and only 1000 client names are being displayed to select from. If he does a filter (eg: A, it displays all the names starting with A, but when we say B or C*, though the data is available in the ODS table, those client name is not displayed in the Screen.
    My question is how to Display all the Values or atleast when he gives A* or B* or Z* it should display those Names, so that he can see the records for those client Name.
    I have done all sorts of R&D to achieve this but in Vain.
    Please help me to sort this.
    Thanks and Regards
    Vishwanath

  • One source system feeding multiple BW systems?

    Is it possible to have the same source R/3 system feed multiple BW systems? It doesn't seem likely to me. I would think delta's would get confused. However I might be missing something.
    Regards
    Steve

    Steve, of course it is possible to connect multiple BW systems to your R/3 system.  You need to create a separate RFC connection for each BW system in R/3 (tcode SM59).  The delta queues are set up per RFC connection (as you can see in RSA7).  When you perform the initialization infopackage in each BW system, a corresponding delta queue will be setup in R/3.
    Hope this helps.

  • Data Flow from SAP Source (ECC) system to SAP BI system

    Hi All,
    I wanted to know how data will be flown from SAP Source system to SAP BI system.Data flow should include
    1) Data will be flown by using the IDOCs?
    2) What all are the interfaces involved while data is transferring?
    3) What will happen exactly, if you execute the PSA?.
    If you have any info on this, could you please post here....I
    Regards,
    K.Krishna Chaitanya.

    Hi Krishna,
    Please go through  this article :
    "http://www.trinay.com/C6747810-561C-4ED6-B85C-8F32CF901602/FinalDownload/DownloadId-C2EB7035A229BFC0BB16C09174241DC8/C6747810-561C-4ED6-B85C-8F32CF901602/SAP%20BW%20Extraction.pdf".
    Hope this answers all the mentioned questions.
    Regards,
    Sarika

  • Problem restoring source system connection post BW system copy

    Hi.
    I am having problems restoring the R/3 connection in our BW system.
    This is the scenario.
    We need to move our BW production system onto a new system, but keep both BW connected to R/3 production for testing etc until cutover to our new BW system.
    Basis performed a system copy and restore of BW production to the new system and ran BDLS.
    When I try to restore the R/3 connection via RSA1 I am getting the following error at the end-
    "A connection already exists there ......." and the message refers to our current/live BW system. The options are to delete the existing or not delete. I have only chosen "do not delete" and therefore the connection is not restored. My concern is that if I choose "delete" this will damage my existing connection between R/3 and the currently live BW system which is we cannot afford to do.
    In our newly copied BW system we are using the existing R/3 SM59 (from system copy), and in R/3 we have created a new SM59 for our new BW system.
    It seems from the error message information that is complains that BW sent R/3 some sort of ID (value = "WS") and that is already taken by the existing BW system. I tried to find where and what this WS value is referring to and the only thing I have found is that in table RSBASISIDOC "WS" is the suffix for transfer structure for that R/3 system. ??? Not sure if this is related for what.
    Thanks for any help

    Hi ,
    Please check with basis or if you can ,then try to restore the source system in BI/BW.This should correct the  inconsistencies between the two systems which is being caused by different Idoc types
    Also check the table RSBASIDOC in the BI system and compare this to R/3 system ,the "basic type" field should be same.
    A restore should work,it has always worked for me.
    Regards
    Amit

  • Connecting IDES source system to BI Dev system

    Hi,
    Can we connect IDES R/3 system to BIW dev system???
    If yes, then is it the same procedure for RFC or something different???
    Thanks & Regards.

    Hi Ganesh,
    Yes, you can. Is like any other R/3 system.
    You just create the source system in BW and that's all.
    Hope this helps.
    Regards,
    Diego

  • How transfer the source code to customer JDI system

    HI Exprts,
    we have typical requirement of transferring the source code from our JDi system to Customer JDI system.
    We have created one track,in that we have 30-40 DCS.now we want to continue the further development at customer place.for that we want to all the source code to Customer JDI system.
    will it be possibel.
    any help will appriciated
    With Regards
    Shobhan

    Hi Shobhan,
    if your developed SCs are configured as "Sources" or "Sources and Archives" then an assembly (and approval) should include a blob from DTR that contains the sources. Importing those SCAs into a track where the same SC is defined as developed SC will also import the sources into DTR.
    (Those sources do not include the full history, only the active version at the time the assembly was done.)
    Regards,
    Marc

  • I looked at system.log in the system profiler today and see lots of activity at 2 a.m. when I was fast asleep, should I worry? It seems to reset hostname and mentions frequent transitions for interface, looks weird to me (I'm not a teckie!)

    I looked at system.log in the system profiler today and see lots of activity at 2 a.m. when I was fast asleep, should I worry? It seems to reset hostname and mentions frequent transitions for interface, looks weird to me (I'm not a teckie!)
    This is a section:
    May 12 02:05:10 wendy-drapers-macbook configd[14]: setting hostname to "wendy-drapers-macbook.local"
    May 12 02:05:29 wendy-drapers-macbook kernel[0]: Auth result for: 00:26:44:14:17:a3 MAC AUTH succeeded
    May 12 02:05:29 wendy-drapers-macbook kernel[0]: AirPort: Link Up on en1
    May 12 02:05:29 wendy-drapers-macbook mDNSResponder[16]: Note: Frequent transitions for interface en1 (192.168.1.92); network traffic reduction measures in effect
    May 12 02:05:29 macbook configd[14]: setting hostname to "macbook.lan"
    May 12 02:05:31 macbook mDNSResponder[16]: Note: Frequent transitions for interface en1 (FE80:0000:0000:0000:021E:C2FF:FEB3:1A3E); network traffic reduction measures in effect
    May 12 02:05:34 macbook com.apple.launchd[1] (org.samba.nmbd): Throttling respawn: Will start in 5 seconds

    I've been seeing messages exactly like that (and many, many other kinds) in the Console since the first version of OS X.  They look menacing but are harmless.
    You don't need any kind of security software.
    Just surf the web carefully, pay attention to where you're going and don't install anything that you don't recognize.  If you are asked to enter an admin user name and password, DON'T.  Unless you know for sure that you initiated the installation from a known and reliable source (like Apple).
    Mac malware relies on social engineering.  No amount of security/anti-virus, blah, blah, blah software is going to help.

  • Error connecting multiple BW systems to one OLTP system

    Hi BW Gurus,
    As part of a major project we had to create a copy of our production BW system and thus have two BW systems connected to one production R/3 system. Before we proceed with the production systems, we decided to try it out with our staging systems.
    1) Created a copy of STG BW (already connected to STG R/3) and renamed it to TST BW.
    2) Transaction BDLS, renamed the logical system ID
    3) Made sure all partner profiles were available and active
    4) Since there was no connection between TST BW and R/3 STG, tried to activate the source system in TST BW. As per OSS note 886102, tried the restore functionality but we are running into a strange error.
    Table RSBASIDOC in the source system already has an entry for STG R/3 and STG BW with IDOC TYP ZSSA015 and Prefix "SA" and now it complains that since this prefix alrady exists, it cannot create another entry with the same prefix for TST BW and STG R/3. It gives us the option to delete the existing entry and create a new one for TST BW. This in turn de-activates the delta between STG BW and STG R/3 and we can successfully initialize with the new system.
    This process turned the queue entry in RSA7 red for STG BW and created a new one for TST BW (green). Delta stopped working for STG BW.
    How can I have both the systems connected and run delta process simulataneously? I have read OSS note 775568 but this is after the fact that the two systems are already connected.
    If I have to start from scratch, can someone please outline the steps involved?
    Do I have to restore the source system or is there an alternate way? I cannot see how the delta would work if there is no connection betweeen the two systems.
    Do I even need to worry about initializing with the TST BW System or can I just run the delta process and it would automatically add another entry in RSA7.
    Any help would be truly appreciated and rewarded!!
    Thank You.
    Sreedhar

    Looks like a much bigger issue than that. We did create the partner profile in WE20 but that didn't help either. It still complains about the prefix. This 2 Character prefix value is actually derived as the concatenation of the first letter of the BW system name and starting alphabet in a sequence. In our example STG BW has prefix of SA and the basic idoc type is ZSSA015. Based on this, TST BW system should have prefix of TA and basic idoc type might be ZSTA016. The program initially looks at RSBASIDOC table for source system and finds value SA and complains that this cannot be used again.
    I have seen messages in this forum where people have actually done this and hopefully someone would reply back as to how to resolve this issue.
    My main question though is, do we have to restore or activate or do not have to do anything to the source system after the copy of BW systems? None of the above three options seem to work for us right now.
    Any ideas?
    Thank You
    Sreedhar

Maybe you are looking for