Attaching a source system in BW

Hello,
Does anyone have any good document regarding the steps of creating a source system (CRM) for BW...?
Best regards,
Fredrik

Hi Fred,
Also go through this document.
http://www.sapgenie.com/sapgenie/docs/MySAP%20BW%20Cookbook%20Vol%202.pdf
Cheers,
Aravindhan

Similar Messages

Communication problems: A device attached to the system is not functioning.

Hi all,
I'm developing an applet and using the OMNIKEY 5321 CL reader for communication and testing. One of the requirements for our card is to read large binary data.
For this purpose i used extented lenght APDU to read the data from card.
When I tested it via JCOP simulation I was able to read up to 32767 bytes as described in specification. But problem occurs when I test it with reader, in this case I'm able to read max 298B in APDU response. When I send greater byte count than 298B i have got following error in JCShell plugin:
jcshell: requestSessionKey.jcsh[1]: Error code: -6 (Card terminal error)
jcshell: requestSessionKey.jcsh[1]: Communication problems: A device attached to the system is not functioning.
Regarding the extend lengh APDU support it should by OK from the OMNIKEY. I'm using newest driver 1.2.9.2 for Win 7.
Here my configuration:
JCOP:JCOP 2.4.2r1
JAVA CARD: jc301
Global Platform: gp22
Can somebody help me? Any ideas?

If you want to use PC/SC directly, I have a simple Go program that reads an APDU file (just hex encoded APDU strings) and sends them to a smart card. You can give that a try if you like.
The code is at: https://bitbucket.org/safarmer/go-apdus
There is a Goclipse project as well as the source. You will need to install Go and run "go get github.com/ebfe/go.pcsclite/scard" to install the required PC/SC wrapper. Once you have done this you can run the program with -file <apth to text file>
An example text file:
# A comment that is ignored
00a4040000
80ca9f7f00- Shane

System.Diagnostics.EventLog - A device attached to the system is not functioning

I was getting an error ....
System.ComponentModel.Win32Exception was caught
ErrorCode=-2147467259
HResult=-2147467259
Message=A device attached to the system is not functioning
NativeErrorCode=31
Source=System
StackTrace:
at System.Diagnostics.EventLogInternal.InternalWriteEvent(UInt32 eventID, UInt16 category, EventLogEntryType type, String[] strings, Byte[] rawData, String currentMachineName)
at System.Diagnostics.EventLogInternal.WriteEntry(String message, EventLogEntryType type, Int32 eventID, Int16 category, Byte[] rawData)
at System.Diagnostics.EventLog.WriteEntry(String message, EventLogEntryType type)
at VB_Braums_ClassLib.LogIt.WriteEventLog(String Entry, EventLogEntryType eventType, String Source) in \\Corp01\Vol1\Mis\Pccode\Ms.net\ProductionLibs\ProductionLibs\ProdLibCommon.vb:line 3666
InnerException:
This code is in a library, so I create a "hello world" to demonstrate the issue. I will post it at the end. This .net 4 framework and it's been around for a while in our code. We are starting to upgrade from XP to Win 7. Basically event log sizes
are limited to the 32667 number. So we had a test, if the string is bigger than that, then we would write it in 32000 byte chucks. On two different win7 boxes we get the "device attached" error message. Run the same code on a XP box and it works.
Oh, and the Win 7 boxes are 64 bit. I wonder if the win 7 32 bit would have the same issue? Can others duplicate it? The tmpsize seems to be different numbers, but if you play with it, you can get it down to number x works and (x+1) does not.
Here the code .....
Module Module1
    Sub Main()
        Dim logName As String = "BraumsLog"
        Dim objEventLog As New System.Diagnostics.EventLog()
        Dim needCreate As Boolean = False
        Dim Source As String = ""
        If Source.Length = 0 Then Source = "Test"
        Dim Entry As String = "".PadLeft(64000, "1"c)
        'Register the App as an Event Source
        If EventLog.SourceExists(Source) Then
            Dim slog As String = EventLog.LogNameFromSourceName(Source, ".")
            If slog <> logName Then EventLog.DeleteEventSource(Source) : needCreate = True
        Else
            needCreate = True
        End If
        If needCreate Then EventLog.CreateEventSource(Source, logName)
        objEventLog.Source = Source
        '*********** New Code ****************
        objEventLog.MaximumKilobytes = 20480
        objEventLog.ModifyOverflowPolicy(OverflowAction.OverwriteAsNeeded, 0)
        'WriteEntry is overloaded; this is one
        'of 10 ways to call it
        Dim tmp As String = ""
        Dim tmpSize As Integer = 32000 '31890 works 31891 does not
        Do While Entry.Length > tmpSize
            tmp = Entry.Substring(0, tmpSize - 1)
            objEventLog.WriteEntry(tmp, EventLogEntryType.Information)
            Debug.WriteLine(tmp.Length.ToString)
            Entry = Entry.Substring(tmpSize)
        Loop
        tmp = Entry
        objEventLog.WriteEntry(tmp, EventLogEntryType.Information)
    End Sub
End Module

Run the same code on an XP 64 bit box and it works? XP comes in multiple flavors.
Perhaps you should compile to x86 CPU and see if it works on Win 7 64 bit. Win 7 comes in 32 and 64 bit also.
On the other hand Win 7 service pack 1 mainstream support ended on the 13th of this month. Extended support ends in 2020 supposedly. Perhaps you should upgrade to Win 8.1 instead. Win 10 is coming soon enough.
Windows lifecycle fact sheet
Microsoft Product Lifecycle Search - Windows 7 result
La vida loca

About creating a new source system on BW pointing to an Oracle database

hi friends
i m facing problems when i
creating a new source system on BW in AIX pointing to an Oracle database, our bw oracle use 10idatabase ,and we want to connet to 9idatabase(Windows) to get data for BW
(1.)     in /oracle/P01/102_64/network/admin tnsnames.ora I hava add
SJPT =
(DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = 68.16.211.177)(PORT = 1521))
    (CONNECT_DATA =
      (SERVICE_NAME = SJPT)
(2) and in etc/hosts I hava add
68.16.211.177 SJPT
(3) in p01adm> tnsping SJPT it is OK
(4)but when i
in BW RSA1 DATA SOURCE
create db connect:
DBMS: ORA
USER NAME: SAP
DB PASSWORD: SAP
[email protected]
i t give me the error message :
ORA-12154: TNS:could not resolve the connect identifier
please help me

HI,my trans.log file is
4 ETW000 R3trans version 6.13 (release 700 - 20.02.06 - 16:15:00).
4 ETW000 unicode enabled version
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time   : 13.11.2007 - 10:16:48
4 ETW000 control file: <no ctrlfile>
4 ETW000 R3trans was called as follows: R3trans -d
4 ETW000 trace at level 2 opened for a given file pointer
4 ETW000 [dev trc     ,00000] Tue Nov 13 10:16:48 2007                              81 0.000081
4 ETW000 [dev trc     ,00000] db_con_init called                                    29 0.000110
4 ETW000 [dev trc     ,00000] create_con (con_name=R/3)                             50 0.000160
4 ETW000 [dev trc     ,00000] Loading DB library '/usr/sap/P01/SYS/exe/run/dboraslib.o' ...
4 ETW000                                                                              43 0.000203
4 ETW000 [dev trc     ,00000] load shared library (/usr/sap/P01/SYS/exe/run/dboraslib.o), hdl 0
4 ETW000                                                                           13346 0.013549
4 ETW000 [dev trc     ,00000] Library '/usr/sap/P01/SYS/exe/run/dboraslib.o' loaded
4 ETW000                                                                              32 0.013581
4 ETW000 [dev trc     ,00000] function DbSlExpFuns loaded from library /usr/sap/P01/SYS/exe/run/dboraslib.o
4 ETW000                                                                              35 0.013616
4 ETW000 [dev trc     ,00000] Version of '/usr/sap/P01/SYS/exe/run/dboraslib.o' is "700.08", patchlevel (0.46)
4 ETW000                                                                              53 0.013669
4 ETW000 [dev trc     ,00000] function dsql_db_init loaded from library /usr/sap/P01/SYS/exe/run/dboraslib.o
4 ETW000                                                                              34 0.013703
4 ETW000 [dev trc     ,00000] function dbdd_exp_funs loaded from library /usr/sap/P01/SYS/exe/run/dboraslib.o
4 ETW000                                                                              53 0.013756
4 ETW000 [dev trc     ,00000] New connection 0 created                              23 0.013779
4 ETW000 [dev trc     ,00000] 0: name = R/3, con_id = -000000001 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
4 ETW000                                                                              39 0.013818
4 ETW000 [dev trc     ,00000] db_con_connect (con_name=R/3)                         45 0.013863
4 ETW000 [dev trc     ,00000] find_con_by_name found the following connection for reuse:
4 ETW000                                                                              32 0.013895
4 ETW000 [dev trc     ,00000] 0: name = R/3, con_id = 000000000 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
4 ETW000                                                                              37 0.013932
4 ETW000 [dev trc     ,00000] Got LIBPATH=/usr/lib:/lib:/usr/sap/P01/SYS/exe/run:/oracle/P01/102_64/lib from environment
4 ETW000                                                                             325 0.014257
4 ETW000 [dev trc     ,00000] -->oci_initialize (con_hdl=0)                         47 0.014304
4 ETW000 [dev trc     ,00000] Client NLS settings: AMERICAN_AMERICA.UTF8          3234 0.017538
4 ETW000 [dev trc     ,00000] Logon as OPS$-user to get SAPSR3's password           28 0.017566
4 ETW000 [dev trc     ,00000] Connecting as /@P01 on connection 0 (nls_hdl 0) ... (dbsl 700 240106)
4 ETW000                                                                              34 0.017600
4 ETW000 [dev trc     ,00000] Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
4 ETW000                                                                              35 0.017635
4 ETW000 [dev trc     ,00000]    0 UTF8                                                      1 0x110f8b9c0 0x110fa3e38 0x110fa36e8
4 ETW000                                                                              36 0.017671
4 ETW000 [dev trc     ,00000] Allocating service context handle for con_hdl=0       37 0.017708
4 ETW000 [dev trc     ,00000] Allocating server context handle                      24 0.017732
4 ETW000 [dev trc     ,00000] Attaching to DB Server P01 (con_hdl=0,svchp=0x110f94398,svrhp=0x110fa6158)
4 ETW000                                                                              72 0.017804
4 ETW000 [dev trc     ,00000] Assigning server context 0x110fa6158 to service context 0x110f94398
4 ETW000                                                                           36191 0.053995
4 ETW000 [dev trc     ,00000] Allocating user session handle                        73 0.054068
4 ETW000 [dev trc     ,00000] Starting user session (con_hdl=0,svchp=0x110f94398,srvhp=0x110fa6158,usrhp=0x110f937a0)
4 ETW000                                                                              43 0.054111
4 ETW000 [dev trc     ,00000] Assigning user session 0x110f937a0 to service context 0x110f94398
4 ETW000                                                                           10613 0.064724
4 ETW000 [dev trc     ,00000] Now '/@P01' is connected (con_hdl 0, nls_hdl 0).
4 ETW000                                                                             964 0.065688
4 ETW000 [dbsloci.    ,00000] *** ERROR => ORA-942 when accessing table SAPUSER
4 ETW000                                                                            1183 0.066871
4 ETW000 [dev trc     ,00000] Disconnecting from connection 0 ...                   73 0.066944
4 ETW000 [dev trc     ,00000] Rolling back transaction ...                          28 0.066972
4 ETW000 [dev trc     ,00000] Closing user session (con_hdl=0,svchp=0x110f94398,usrhp=0x110f937a0)
4 ETW000                                                                             146 0.067118
4 ETW000 [dev trc     ,00000] Now I'm disconnected from ORACLE                     409 0.067527
4 ETW000 [dev trc     ,00000] Try to connect with default password                  23 0.067550
4 ETW000 [dev trc     ,00000] Connecting as SAPSR3/<pwd>@P01 on connection 0 (nls_hdl 0) ... (dbsl 700 240106)
4 ETW000                                                                              34 0.067584
4 ETW000 [dev trc     ,00000] Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
4 ETW000                                                                              36 0.067620
4 ETW000 [dev trc     ,00000]    0 UTF8                                                      1 0x110f8b9c0 0x110fa3e38 0x110fa36e8
4 ETW000                                                                              36 0.067656
4 ETW000 [dev trc     ,00000] Assigning username to user session 0x110f937a0        22 0.067678
4 ETW000 [dev trc     ,00000] Assigning password to user session 0x110f937a0        41 0.067719
4 ETW000 [dev trc     ,00000] Starting user session (con_hdl=0,svchp=0x110f94398,srvhp=0x110fa6158,usrhp=0x110f937a0)
4 ETW000                                                                              37 0.067756
4 ETW000 [dboci.c     ,00000] *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1017
4 ETW000                                                                           33690 0.101446
4 ETW000 [dbsloci.    ,00000] *** ERROR => CONNECT failed with sql error '1017'
4 ETW000                                                                              36 0.101482
4 ETW000 [dblink      ,00431] ***LOG BY2=>sql error 1017   performing CON [dblink#3 @ 431]
4 ETW000                                                                             122 0.101604
4 ETW000 [dblink      ,00431] ***LOG BY0=>ORA-01017: invalid username/password; logon denied [dblink#3 @ 431]
4 ETW000                                                                              34 0.101638
2EETW169 no connect possible: "DBMS = ORACLE                           --- dbs_ora_tnsname = 'P01'"

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

Transporting Process Chain - error Source system does not exist

Hi,
I tried to transport a local PC by itself (not including its main meta chain) since I have only done modifications in the local PC only. In the PC, there are PSA Processing, ODS Processing, ODS Activation, ABAP Program w/ variants and Infocube Rollup.
However, I got the following transport error: Source system does not exist
=======
Diagnosis
Source system is not known.
System Response
The imported data for DataSource was deleted again because the referenced source system does not exist and no mapping is defined in table RSLOGSYSMAP on an existing productive source system.
Procedure
Create the referenced source system in the Data Warehousing Workbench or define mapping to a known source system in table RSLOGSYSMAP.
You get to maintenance using Tools -> Conversion of the logical system names.
============
I have checked at the table RSLOGSYSMAP and all source system mappings are in order.
And the weird thing is, upon checking the PC itself in the transport-to box, I can activate it without any error.
FYI, we are currently upgrading to BI Accelerator. Am not sure if this could be one of the reasons.
Any inputs and tips are highly appreciated and will be rewarded with points accordingly.
Thanks

Hi,
This error is due to the fact that the
mapping table for the after import (RSLOGSYSMAP) is not correct maintained in PB7 system.
You need to maintain table RSLOGSYSMAP in each system
You can find the steps to do it in the attached note 127326:
o Maintain table 'RSLOGSYSMAP' in the target BW with view
   'V_RSLOGSYSMAP' and enter as 'original source system' the logical name of the source system in the source BW and as 'target source system' the logical name of the source system in the target BW.
   This maintenance is required since it allows the correct source system reference of the InfoSources to be transported.
This source system reference in turn is absolutely necessary to activate the transfer structure.
   Example:
   Source BW with source system AAA.
   Target BW with source system BBB where the source system AAA
   corresponds to the source system BBB.
   Entry in RSLOGSYSMAP in the target BW:
   Original source system: AAA, target source system: BBB.
   Give the DDIC user in the source BW in client 000 the
   authorization profile S_RS_ALL to create BW objects.
Cheers
Rajesh

DB connect source system creation in BI

Hi,
I would like to create a DB connect source system to an external MSSQL 2005 database in RSA1.
The external MSSQL 2005 database is setup using Windows Authentication mode.
Question: Which user actually should I specify when creating the source system in RSA1? or which user should I assign the db_ddladmin role in the external MSSQL database?
Many thanks,
YJ.

Hi,
Please note the following with regard to the user:
To avoid problems loading data, proceed as follows:
1. Create a special login for the extraction. You should add this login to the db_ddladmin database role in the
corresponding database. This generates a similar DB user at database level. The user you use must have the 'CREATE VIEW'
authorization at least. This is contained in the role mentioned above.
2. For the extraction, you should only use DB views that were created under this DB user. (refer also to type conversion, naming
convention and so on)
3. Assign the necessary authorizations (SELECT at least) to the selected user in the source tables, or the columns of these tables.
4. Use the specially created login in the logon information when you set up the DB source system in BW.
You will find much more detailed information on how to setup the connection and known problems and issues in the
attached note 512739.
Best Regards,
Des.

RSA1: source system missing after restoring broken in midway

Dear expert,
We are doing the ECC system refresh (ECC PRD to QAS)
ECC QAS has connection with BW QAS
So we after we maintain the RFC logon , steps are as following
Logon Q23 as client 0**
Run SU01 and change the password of ALEREMOTE to ‘****’ (must be uppercased)
Run SM59 and delete ABAP connection ABWCLNT0** if it exists.
Logon ABW using Client 0** as user sapsupport
Run SM59 and choose ABAP connection Q23CNLT0**, update the password of ALEREMOTE and perform connectivity test and make sure it is working fine.
After the steps above we continue on ABW with RSA1 (see picture 1) but unfortunately the remote connection is broken and when i logon RSA1 again
The Q23 client DISAPPEAR(see picture 2)!
Could anyone help to explain why ??? and how to fix/create the ECC QAS source system again ?
Thank you so much

Hi Reagan,
I created it by clicking on the icon of "SAP" then it will pop up a "create" tab
It takes me quite a long time around half an hour.
Finally it shown in the end of RSA1 screen , Q23CLNT0** source system is created successfully.
BUT the strange thing is i refresh the RSA1 screen , i can't not find the Q23 apears in the folder of SAP!!!
And i try to recreate , it shows in the end " Q23CLNT0** "already exist (see attached), how could it be , can anyone come to help?
thank you!
Best regards,
kate
Message was edited by: Kate Ji i updated the content as above

DB Connect Source System Creation

Hi,
I am trying to create source system (DB Connect) to extract data from SQL Server to BI.
I had user id/pwd in DB who is authorised to read view created by DB personnel.
n BW Description of Database Connections Screen
There are two fields
CONN.INFO and PERMANENT
What is the functionality of those 2 fields and from where can i get CONN.INFO
Thanks
Krishna

Hi,
Please note the following with regard to the user:
To avoid problems loading data, proceed as follows:
1. Create a special login for the extraction. You should add this login to the db_ddladmin database role in the
corresponding database. This generates a similar DB user at database level. The user you use must have the 'CREATE VIEW'
authorization at least. This is contained in the role mentioned above.
2. For the extraction, you should only use DB views that were created under this DB user. (refer also to type conversion, naming
convention and so on)
3. Assign the necessary authorizations (SELECT at least) to the selected user in the source tables, or the columns of these tables.
4. Use the specially created login in the logon information when you set up the DB source system in BW.
You will find much more detailed information on how to setup the connection and known problems and issues in the
attached note 512739.
Best Regards,
Des.

How to know querry level fields from which tables in the source system

Hi Experts,
let's say we've two fields in the querry e.g: Actual GI Quantity, Actual Value of GI
This fields from PP Querris level how would i know from which table we're getting data is there any easy process to find out please drop your suggestions..
Next doubt is when generate querry e.g. PM Module we don't know exatly what're the available tables & fields technical names but in my currently project using SAP Delivered Infocubes & Querries at the moment & generating querries but when we test in the Portal it's shows some fields '0', X. I've to check in source system weather it's having any values or not.
Can anybody drops your valuable words
Cheers
Suresh

Hi all,
I'm a colleague of Maarten, and I think maybe we didn't explain well enough what we want. So let me try to elaborate:
We want to obtain the reference (within the SOAP-Body of the XI-message) to the attachment which contains the main payload (at least, in XI itself). This reference seems to have gone missing, once our adapter module (after having gone through XI) is entered (and, by the way, before we enter the SOAP-receiver-adapter).
The JAVA-representation of the XI-message seems to hide the fact that in XI itself, the main payload is an attachment, referenced from within the SOAP-Body.
Nevertheless, we would like to obtain/retain(?) that reference, in order to put it in our own to-be-created-additional-attachment, which would go (via the PayloadSwapBean-module of SAP) into the SOAP-body of the final SOAP-call, and should then reference the 'new attachment' (which was (in XI itself) the main payload).
So, I think both answers (up to now) don't help us much (however: thanks for your reaction anyway of course).
So, maybe someone has another idea?
Regards, Fred

Copy Transferrules from one source system to another

Hi everybody,
we're uploading data from nearly 25 sourcesystems (including separate systems and systems with more than one client to extract from) via flat-file. The source-system exports data to a shared file directory and the bw-system reads it from there. Though this results in only <b>one</b> transferrule for all source-systems, it keeps generating problems every time upload is due.
Somebody had the idea to switch to 'standard' R/3->BW method of data staging, using generic extractors and so on. But this will result in <b>25</b> transferrules which, I'm afraid, have to be set up and maintained seperately. As there's quite some coding in the rules (the transfertructure in fact has 241 fields), flaws are for sure!
We know the trick of exporting a transferrule, changing the source-system-mapping and re-importing the same transport-request. That can be used to copy to one or two other systems, but not for 25.
Does anybody know another way to copy a transferrule from one source system to multiple other source systems?
Looking forward to your answers
Thanks and Regards
Robert

Hi Ralph,
I don't like that methode. Importing the same transport 15 times, each time changing the source-system mapping and making sure, that source-system gets the changes seems to be a huge source of errors, which will be hard to find.
What do you think of the following idea to solve the issue a totally different way:
All transfer-rules directly connected to the source-systems are stripped of all Coding, so there is a plain 1 by 1 transformation including 0logsys.
The InfoSources attached all lead to one ODS-Object, which has the only purpose to collect the data from the source-system without any transformation. So some fields a filled by a system and other fields maybe not.
The coding specific for source-systems is moved to transfer- / update-rules from that ODS-Object to the original ODS-Objects / Cubes and the "collecting" ODS-Object is emptied after every loading process.
This will result in a single point of change. It will be quite a huge program (maybe in startroutine) but it's the one and only point, where changes and corrections have to be made.
Regards
Robert

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

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

Source System Logical Name change

Hello,
We are refreshing our R3Qas system with a copy of our R3Prd system. As part of this task our R3Qas logical name is changing from QASC230 to QASC200.
I am at the point in the refresh where I am beginning tasks on the existing BWQas system.
I Right Click on the source system representing the R3Qas system "QAS client 230" technical name: QASC230. I choose 'Restore' I then provide the logon information but the system it jumps to is the Old R3Qas not the new R3Qas.
I know that it is jumping based on the RFC, So I assume I can change that RFC to jump to the new system, what do you think? Also what about the Source System name an technical name, will it always be QAS Client 230 and QASC230 or can that be changed to reflect the new name of QASC200?
Thanks for your advice and assistance!
Nick

Since the BWQ system was already an existing system that was attached to the previous R3Q system, this task was essentially busy work.
The change that occured was that the existing R3Q system (Physical Name: QAS01 Logical Name: R3QASC230) was being replaced with a new R3Q system (A copy of Production was used) (Physical Name: QAS02 Logical Name: R3QASC200).
The actions that I needed to take to connect BWQ to the new R3Q follow:
1. On QAS02 visit TX SE37. and run RSAP_BIW_DISCONNECT, Choose 'Single Test'. For I_BIW_LOGSYS: I provided BWP001 which corresponds to the logical name of our Production BW system. For I_OLTP_LOGSYS: I provided R3PRDC200 which corresponds to the logical name of the QAS02 system (this system). I then Click 'Execute' and 10 seconds later this step is done.
2. On QAS02 visit TX: BDLS. For the 'Old Logical System Name' provide BWP001. For the 'New Logical System Name' provide BWQ001. Ensure the 1st radio button is selected, and deselect all checkboxes. From the Program menu choose to 'Execute' in background (it took about 45 minutes). Confirm the 'Mapping System Name'.
3. Again on QAS02 visit TX: BDLS. For the 'Old Logical System Name' provide R3PRDC200. For the 'New Logical System Name' provide R3QASC200. Ensure the 1st radio button is selected, and deselect all checkboxes. From the Program menu choose to 'Execute' in background (BASIS already did this step so a message appeared to that effect)
4. On the BWQ box visit TX: BDLS. For the 'Old Logical System Name' provide R3QASC230. For the 'New Logical System Name' provide R3QASC200. Ensure the 1st radio button is selected, and deselect all checkboxes. From the Program menu choose to 'Execute' in background (it took about 45 minutes). Confirm the at the prompt and run.
5. On BWQ create new RFC's based on the old ones to point at the new QAS02 system. Modify the old ones with an X in the 'Target Host' so they do not function.
6. Open up the BWQ client in SCC4. (or perhaps try SM30 to modify the table in the next step)
7. On BWQ visit TX: SE16. Tablename: RSLOGSYSDEST. Change the 'Old' reference to the QAS box to the 'New' information. (ie: R3QASC230 became R3QASC200).
8. On BWQ visit TX: WE20. Expand 'Partner Type LS', Select 'R3QASC200', click the classification tabe, change the 'Partn.Status' from I to 'A' and save.
9. On BWQ right click on the R3 Source system and choose 'Restore' Provide the passwords that are required. When prompted to logon to the remote system use an ADMIN (BASIS) level Account. Click 'Continue' when you get the 'User exists...' prompt. Click 'Only Activate' when prompted. you will then get a termination message regarding the port description.
10. On BWQ Back at WE20: Expand 'Partner Type LS', Select R3QASC200, double click on RSRQST. Under 'Outbound Options' click the drop down for 'Reciever port' Select the 'new' correct system and 'Save'.
11. On BWQ right click on the R3 Source system and choose 'Restore' Provide the passwords that are required. When prompted to logon to the remote system use an ADMIN (BASIS) level Account. Click 'Continue' when you get the 'User exists...' prompt. You will get a prompt to Use or Check, choose 'Use'. When prompted about 'Connection cannot be used' click 'Delete'. Logon again as ADMIN account, Click 'Continue' when you get the 'User exists...' prompt. Click 'Replicate as well' when prompted. you will then get a termination message regarding the port description.
You should be all set now!
Nick

Source System(Logical system) issue

Hi All,
Recently we have done QA refresh & copied with production data.
For 0vendor master data we are extracting data from ECC source system. When I was trying to execute the DTP it is pointing older source system. We tried to create new DTP but when I'm executing still it is showing older system.
By using RSBKDTP_BDLS program I forcefully tried to convert old source system to new source system but we are unable to solve this issue.
Here I'm attaching the issue .Please help on this issue.
Best Regards,
Sammar.K

Hi Ram,
I have compared Production & QA system entry's in RSLOGSYSMAP Table.
in prd system
source       target
qa6            prb01
in qa system
source       target
qa6             qa6
we found in qa it is pointing wrong target.
Regards,
Sammar.K

Attaching a source system in BW

Similar Messages

Maybe you are looking for