Wrong Source System

Hi, Experts:
We moved transports for a new application from development into 2 QA systems (QB1 and QB2) in BI. The migration went OK for one of the system QB1, but got 2 problems with wrong source system for QB2.
1. The ODS can't be acitivated with an error message: "Invalid source system PB1CLNT100 entered."
2. The datasource connected to the ODS has the wrong source system "PE1CLNT100". It should be "QE2CLNT100" instead. I could manually replicate the source system from QE2 in QB2. But I can't link the datasource from the correct source system to ODS. When I tried to create transformation, it gave error that "ODS is not active due to invalid source system".
How should I fix this please?
Thanks,
Jenny

As praveen says you have to make your transporting scheme correct.
When transporting a datasource from dev to another stage you have you define how the names from your source system have to change.
In your case i expect the two QA system to be connected to different R3 source systems.
You have to change that in the way praveen says and then do some re-transports.
Success
Marco

Similar Messages

G/L account picked for the "wrong" source system entry

Dear Experts,
in SRM 7.0, Classic Scenario, i am facing the following issue with respect to G/L account determination in the SC:
We have three R/3 systems connected to SRM. All these R/3 systems use the same Material Groups, but the G/L accounts are different in each R/3 system.
In the Table "Determination of G/L Account using product categories", i have maintained the repsective combinations. For each combination of product category and account assignment category, the respective G/L account is defaultet for the respective source system.
But in the shopping cart, the determination of the correct G/L does not always work. When a user enters the shopping cart initially with a line item that is accounted to his default account assignment category, than the correct G/L account for his source system is derived. But if he changes the account assignment category of the line item, than a G/L account from a "wrong" source system is getting picked up from the table.
I have checked the GUIDs of the product categories between "Comm_category" and "bbp_det_account" and they are correct.
What can be the reason for the picking of the G/L account from the wrong source system?
Can the note 1357871 bring the correction?
Thank you very much!

Hello Dima,
I think your problem comes from your source system for product category management.
Could you clarify one point: if you change account assignment category, does new G/L account have to be determined for same backend system too or not ?
If yes, correct new G/L account will be determined using your customizing (IMG: SAP Implementation Guide > SAP Supplier Relationship Management > SRM Server > Cross-Application Basic Settings > Account Assignment > Define G/L Account for Product Category and Account Assignment Category ).
If it does not work, log an OSS message.
If no, you need to switch value for each SC item field BBP_PDIGP-LOGSYS_FI from old backend source system to the new one. For this, use BBP_DOC_CHANGE_BADI.
Then, your customized G/L account definition for product category and account assignment category should be OK.
Regards.
Laurent.

Test System (BQ1) Objects showing up wrong Source System after Transport.

Hi Experts,
We are working on IS-U BI7.0 Project. We have finished with our Development and have transported the DataSources, Transformations and DTPs from Development (BD1) into Test (BQ1) Systems.
We have entered values in the Conversion of Logical Source Systems correctly.
When we select the DataSource and Click Object Directory Entry from the Extras Menu, we found that the Original Source System is defined as BQ1 instead of BD1 (Development System), which is where the Object is getting Transported from.
We have implemented an SAP Note:1008633 (Incorrect Source System after Transport (RSTRAN 514) but couldn't resolve the issue.
We basically want all the Objects in the BQ1 (Test System) showing the Original Source System as BD1 (Development System) but only the DataSources and it's connected Transformations and DTPs are originating from the BQ1 (Test) System itself (The Transformations when Transported from BD1 to BQ1 are Transported with a different Technical Name which is very strange).
Had anyone faced similar problem and if so, what was the effective solution implemented.
Any help in this regard is very much appreciated.
Thanks in Advance.
Best Regards,
Chandu.

It is resolved by our Basis.
Thanks,
Chandu

BI Content Activation going for wrong source system

Hi,
I am trying to activate business content for the Customer cube in BI 7. The problem is that although the source system selection shows client 200 selected, the content activation goes for client 500 (which is the BI client). That is, during the activation process the process diverts to client 200 for no apparent reason. I have tried selecting other source systems, but the system still goes for client 200. Any idea of what is going on?
Many thanks!
Regards,
Adeel Hashmi

Hi Reddy,
I checked it already and it shows the T90CLNT090 - IDES ALE Central system (client 800) which is shown as "Self-def'd" and not R/3, infact i dont have any source system specified under R/3 option. How do i fix this, as mentioned earlier we have both ECC and BI in the same box, will this affect???

BW - Source System in wrong TAB

Hi SAP BW Gurus,
I am connecting my SAP BW to a new R/3 Source System, but when i create the new system in RSA1 -> Source Systems, despite using the right click of mouse over the TAB SAP, when the Source System is create he apears on the TAB BI.
What i do wrong?
There is any impact of living the source systems like this?
What can i do to place de R/3 Source System in the right TAB (SAP)?
Thanks in advanced,
Pedro Martins

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

Master data is coming wrong in sap bw, although in source system it is corect

Hi all,
Master data is coming wrong at the PSA level itself. Our source system is CRM which has the correct data but still it is coming wrong at PSA level. I tried reloading the data but was in vain.
ID
Name
X
ABC
Y
ABC
We have two fields-- ID and Name. For ID X , the Name is ABC(say) and for ID Y the Name should be DEF(say). But for both the IDs X and Y the name is coming as ABC, which is wrong
Can you please guide me what to do in this case ?

In that case please be informed that
" The business partner number for the person responsible for the territory is determined from the organizational model. It is taken from the territory and employee responsible that have been assigned to the position in the organizational model. The fields are extracted from function modules in mySAP Human Capital Management". (From help.sap.com)
Check the URL http://help.sap.com/saphelp_erp2004/helpdata/en/db/6651d40e4a244e804956171a56d0d1/content.htm
Kindly take help of your CRM functional consultant regarding the same and also with the help of ABAPer debug the extractor to pinpoint from where excatly it is fetching the BP number ....
Hope this helps .

Wrong conversion of source system after transport

Hello,
We ve got a a transport problem in our 3-3 Landscape. Connections for extraction are only between same systems ( f.e. dev to dev)
BI Dev BI Test BI Prod
R3 Dev R3 Test R3 Prod
The conversion of source systems is on the BI test:
BI Dev becomes BI Test
R3 Dev becomes R3 Test
The conversion of source systems is on the BI Prod:
BI Test becomes BI Prod
R3 Test becomes R3 Prod.
With this it tells me the after transport (BI Test to BI Prod) of objects with source system assignement that the R3 Dev System is not known.
The transport before from the BI Dev to BI Test worked well without any problems.
We`ve got the BI Test and the BI DEV on the same host.
Has anybody got an idea what is wrong?
Thank you folks.

It must be R3D (dev system)
Something like following should be maintained in production
R3DCLNT100 <u>R3PCLNT100</u> [Assuming R3PCLNT100 is your production system]
Don't forget to assign points,
-jayant

BI Content collecting objects from wrong/old source system??

Hi Gurus! Lovely day here on the westcoast of Sweden - springtime is coming!
I have selected an infosource for installation in trx RSOR. I also want to pick up some objects in the dataflow before and after that specific infosource. So I guess the system keeps trying to collect metadata from diffrerent source systems that we have assigned.
I don't know the complete history of the systems - other than it's a bloody mess. We have right now a ECC 6 system connected to BI - but before that we had an older version connected (I guess 4.x something) on a diffrerent server.
Somehow the collection process picks up some data from the ECC 6 system - but sometimes it asks for a login to the old system as well.
This is my problem. I don't have an issue with logging on to the old system - because I have all the necessary rights to do that. But I don't want BI trying to collect metadata from our old system. So somewhere there's a pointer of some sort to the old system that I need to delete....
The old system is not visible in the "source system assignment" view so I can't really find out where to change this settings....
Any ideas??

It's probably so. Would I still carry out the instructions Andreas gave me for checking this? Or should I just delete everything and do it all over again, just to get the connections straightened out?
I'm more or less the only one at this point using the system - as it is a kind of sandbox environment. So extreme measures is not a problem

Error: Source system already exists. Message no. RSAR201. Points rewarded.

Error: Source system already exists. Message no. RSAR201
We have installed a BI 7.0 system recently and I am setting up the server to connect to SAP ERP.
In TA SM59 a connection to the SAP ERP has been established. The Remote Logon is OK, (meaning clicking it nothing happens). The Connection Test is OK.
According to the Best Practices paper: B84: BI Connectivity (B84)
http://help.sap.com/bp_biv170/BBLibrary/documentation/B84_BB_ConfigGuide_EN_DE.doc
I have done the following:
In TA RSA1
1.     Choose Modeling.
2.     Choose Source Systems.
3.     Select SAP in the window on the right.
4.     Choose the Context menu (right mouse click).
5.     Choose Create.
6.     Make the following entries:
Available destination: (The above tested connection)
Background user in source system: RFCUSER (I created the user in ERP according to step 1.4 in B84)
Password for source system: *****
Background user in BI: RFCUSER (I created the user in BI according to step 1.4 in B84)
Password for BI user: *****
8.     In the dialog box Please log on as an administrator in the following screen choose Continue.
9.     Log on to the Source System with your administrator user. Choose the correct client.
10.     On the dialog box New Source System Connection choose Continue.
THEN I GET THE ERROR:
Source system already exists.
Message no. RSAR201
What is wrong? I cannot locate any SAP notes to help on this problem.
Best regards,
Carsten Pold

Hello Carsten,
just some guessing at this point...
a)
Is the connection really new? For example, was there another system connected to that ERP, maybe with the same logical name? Or was any of the two systems copied from another system?
b)
Authorisations issues in this process may result in strange error messages. Make sure that the admin user in step 9 really has SAP_ALL. There are a lot of complex activities that this user must be able to do (ALE management, RFC access etc.). To exclude issues with the RFCUSER users: If possible, give them SAP_ALL, too. Of course only temporarily for testing.
c)
I normally don't use existing RFC destinations. Usually, I let the system create those, too. So maybe it makes a difference if you remove the RFC destinations on both sides and try again. In that case, you will of course have to provide the RFC details when creating the source system connection...
I hope this brings you forward a little...
Regards,
Christian!

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 with Source System in BI

Hi,
I replicated the datasources from DEV to BI. They replicated just fine. I can even see it in BI. I then tried to activate the datasource (i created the datasource from a view ) but it gave me a run time error :
ASSIGN_LENGTH_0 Short dump has not been completely restored..too big.
I then tried to go into the source system and tried to activate that and it said:
Source System DEV300 is inactive
BI Unknown in system
BI IDoc type ZSBC019 is not the same as source system IDoc type
The following errors occured in the source syaytem:
Entry in inbound table not found
Entry in outbound table not found
Result of the destination check: No authorization to logon as trusted system
What could have went wrong?
Thanks

Did you try activating the source system in RSA1 ..right click and choose active.
if this doesnt work then you might want to check the inbound and outbound entries in we20 transaction code for the source system. If you have authorization. Or you need to check with your BASIS to set that up for you.

No username of Source system is avbl after livecache system copy

Hi Experts
I have done a livecache system copy from the source system to target system. Here the steps are
Assume my Source SYstem Livecache is RP1 and Target System livecache is RS1.
1. Taken Source system livecache DATA and LOG Area backup RP1.
2. Defined the same source system backup medium name in Target System (RS1 and moving the Source system Liveacache backuped files to Target system and defined the medium name as per that)
3. put the livecache db_admin mode
4. db_activate RECOVER <medium_name>.
5. recover_start <log_medium_name> LOG <nnn>
6. db_online.
Here we faced that
ERR
-24622,ERR_AUTOLOADSYSTAB: Automatic loading of the System Tables failed
-24907,ERR_DBAWRONG: Wrong database system administrator
-24988,ERR_SQL: SQL error
-4008,Unknown user name/password combination
So we activated the SUPERDBA as " db_activate SUPERDBA,<password>
then it came to online. and afterwards we have used the load_systab command to load the tables.
BUT we could not find any Source System name like "RP1ADM" in the tables of the livecache database. Only there are CONTROL,SUPERDBA username availbale. Usually there will be also the source admin name . I dont know why it is missing
Before a month we have done livecahe restore same as now in that time we got the source system name admin also. ( RP1ADM) and also tables which owned by RP1ADM. alos i could find APPSYSPARAM table and the instance also registered.
But now in this restore we could not find the above.
We followed the same procedure and there is no change in the steps also.
Could anyone help me...
Regards
bala

Hello Bala,
1. As I wrote you already, the notes:
886103 System Landscape Copy for SAP SCM
877203     Post steps after the Homogenous liveCache copy using backup/
457425     Homogenous liveCache copy using backup/restore
has all recommended steps to do, when you will run the u201CSystem Landscape Copy for SAP SCMu201D
2. If you run the u201CHomogenous liveCache copy using backup/restoreu201D you should pay attention to the note 457425. After you imported the complete data backup < step 2. > you need to update the system tables.
To update the system tables you need to know the correct database SYSDBA user & password.
After you restored the databackup of the source database, start the database online & run u201Cselect * from usersu201D SQL command to see the SYSDBA user. Then check that you know the DBA user ( DataBase Administrator ) & password of the source database instance => Open the SQL session with this
user & password.
Example:
after db_activate recover <medium_name>
login as control,password
db_online
sql_execute select * from users
sql_connect superdba,<password of source system>
If you didnu2019t get error with the last command, then you could update the system tables with the superdba,<password of source system> using load_systab command.
The system tables will be updated & the correct SYSDBA user & password will be updated in *.UPC file.
3.
user_sysdba:
You make the database system administrator known to Database Manager. It is only necessary to use this DBM command if the database administrator is not known or is incorrectly known to Database Manager.
u201CI have tried like this
after db_activate recover <medium_name>
login as control,password
db_admin
user_sysdba superdba,<password of source system>
db_onlineu201D
You could update the .upc files with the wrong SYSDBA user password u2026
You was lucky, that you knew the correct SYSDBA user and password of the source database.
Example < NLK is my local database >:
A.     I could update the .upc file with wrong password of SYSDBA user:
dbmcli -d NLK -u control,control
dbmcli on NLK>user_sysdba superdba,test
OK
dbmcli on NLK>db_online
OK
dbmcli on NLK>load_systab
ERR
-24909,ERR_DBAUNKNOWN: SYSDBA unknown
dbmcli on NLK>exit
B. I could update the .upc file with wrong SYSDBA user:
dbmcli -d NLK -u control,control
dbmcli on NLK>user_sysdba test,test
OK
dbmcli on NLK> user_get test
OK
u2026
dbmcli on NLK>sql_connect test,test
ERR
-24988,ERR_SQL: SQL error
-4008,Unknown user name/password combination
dbmcli on NLK> dbmcli on NLK>sql_connect superdba,admin
OK
I could connect as test,test; but the test user is NOT SYSDBA user u2026
dbmcli -d NLK -u test,test
dbmcli on NLK>
Itu2019s recommended to user the load_systab command, so the .upc files will be updated with the correct SYSDBA user/password or
you will get error.
4. http://maxdb.sap.com/doc/7_7/86/68627a1bc642e6a6f73d3bc7a55fe1/content.htm
You got error:
ERR
-24622,ERR_AUTOLOADSYSTAB: Automatic loading of the System Tables failed
-24907,ERR_DBAWRONG: Wrong database system administrator
-24988,ERR_SQL: SQL error
-4008,Unknown user name/password combination
The automatically updating the system tables, according to the default value, is switched on.
After you will run the update system tables with the correct SYSDBA user & password the *.UPC file will be updated,
and with the next liveCache restart you will not get this error.
5. See more information in the MAXDB library:
http://maxdb.sap.com/doc/7_7/45/11cbd6459d7201e10000000a155369/content.htm
Thank you and best regards, Natalia Khlopina
Edited by: Natalia Khlopina on May 19, 2010 2:58 PM

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

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

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

Source system creation

hi experts,
this is the first time i am creating source system
i am have requirement to load data one bw system to another bi system,
so, to do that i defined and created logical system in bw for bi system and
i created same for bw in bi system also and everything is ok.
i guess my next step is to create source system(my self) for bw in bi .
when i am trying to create it is showing that it is already exists.and here what type of source system i need to choose. i am not founding any my self bw data mart
status symbol under source system creation node and what type of the source system i need to choose and whether it is manually or automatically.if i choose automatically it is asking create new destination ,create back ground user and connection of source system to bw (it is asking to fill all fields),for manual system creation only logical system and rfc destination. is it required to creat source system or not because my self bw data mart symbol is present in bw system and bi system also.please correct me if anything wrong
thanks
venu

hi chandra shekhar &chitrat,
thanks for your quick reply,when i choose sap business information symbol
it is asking to fill all the entries like crate new destination under this i provided
target computer in this i provided ip address of bi system( i am creating in bw system),system id & system number,and back groung user in source system and
password ,connection to the source system ,target system for back ground user
and connection to the source system what i need to provide
thanks
venu

Error: Infoobject is not defined in the source system

hi
(I posted this in other forums as well - but wondering, it it should be here in BCT/Extractors - I could use more help).
this is my issue:
I am trying to load master data (attr) for an infoobject.
But, it fails with the following error message (when I click on the "Error message" button on the "monitor" screen.
"Infoobject is not defined in the source system"
"Erros in source system".
(I did rsa3 and find it has some data + i checked on the base table as well, it has data; the datasource is from an SRM system) Why is it complaining like this.
any help on what could be wrong here? Pl let me know,
thanks

Thanks Ricardo,
I have tried that b4. and it says the "source system connection is OK".
any other idea?
Do I have to install the infoobjects on the source system as well? SRM is my source system.. I am not sure on that, but If I have to, how do I do that?
thanks
Message was edited by: Esan

Wrong Source System

Similar Messages

Maybe you are looking for