Source System - Deletion issues

Hi everyone,
I´m facing an upcoming problem in my BI 7.0 project and I would like to minimize the consequences of the situation as following:
The Basis team, for some reasons, is going to eliminate in DEV the client (eg. 200) that I have all my connections set with BI and will create another one (eg. 230). The same thing is going to happen with QA environment (300 -> 330). Production will remain the same (400)
What would be the best way to reconnect all Infoproviders and Infoobjects with this new source system ? Logically, I will have to put everything in a request and sent it later to QA to restore all the connections in this environment. The major work will be done in DEV environment.
I just want to know if there´s way to reconnect everything not manually. I have both 3.5 (Master Data) and 7.0 (Transactional) Datasources.
Thanks in advance,
Fábio

Hello,
I believe what you can do is following the steps in the PDF "How To - System Copy in SAP Business Intelligence System Landscapes" https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/bff13df2-0c01-0010-6ba7-bc50346a6fd8
I did not require a transport either.
I had a similar action occur when my R3 QAS system got replaced, it had a new Physical and Logical name as well as a new client number.
I followed Section 3.7 "System refresh of source system without copying the SAP BW system in parallel (LSN "Option 2")"
We were on R3 4.6c and BW 3.5 at the time.
Maybe that will help you!
Nick
Edited by: Nick Bertz on Jan 12, 2009 4:08 PM

Similar Messages

Field not delivered by source system - Deleted from rule

Dear Support,
While activating business content for example 0CRM_COMP,
I get the following error:
Field TYPE not delivered by source system -> Deleted from rule
Field CAMP_TYPE not delivered by source system -> Deleted from rule
Field CAMP_TYPETX not delivered by source system -> Deleted from rule
Similar errors for different fields appear.
My system config is
BI 7.0, SP14
BI Cont 703 Sp6
Any fix or solution will be suitable awarded.
Thanks and Regards
Raj Jain

HI Raj,
The business Content is not always consistent.
If you get messages like that, the best way to deal with them is to manually adjust the objects.
In this case it means that you will have to check the datasource. It may be that in R/3 you will have to "unhide" or add some fields to the datasource. (I cannot be sure as I cannot go into details).
Hope this helps,
Udo

Source system connection issues

Hello BI Experts,
We had issues with the source system connection - from our BI system (NW 04s) to our R/3 system (ECC 6.0) .
From RSA1, when we right click on the R3 source sytem and do a "Check", it was erroring out: "Error in source system <Logsysname1>". This Logsysname1 was different one from the actual R/3 system's Logsys name (Logsysname2) .
To Fix this, we restored the connection by selecting the (R/3) Source system and right click and "Restore".
After providing the passwords for the RFC users, the system again asked "The Connection <XY> is used in the <Logsysname1> Source system as a connection." And we selected the "Delete" option here. Then in the Logon screen to R/3, we provided the administrator user Id and password.
Once the source system connection is complete, we checked the connection as mentioned above and the "Source Sytem connection is OK" now.
(1) But now, in the transaction RSA1, the R/3 system is displayed under "BI" instead of "SAP".
(2) When we asked our BI consultant to check the dataloads, he encountered an error: "No transfer structure is available for InfoSource <X> in the Source system. Errors in Source system".
How can we bring the R/3 system under "SAP" now?
If we delete the R/3 system (which is listed under BI) and recreate under "SAP", will the transfer rules will also get deleted?? How to avoid this issue?
Please advise.
John
SAP Basis.

Hi,
Please make sure that you have followed the below steps while creating the Source System
1.     In the initial screen of the source system, choose Tools ® Administration ® User Maintenance ® Users and create a background user with a password and the authorization profile S_BI-WX_RFC.
2.     Define the RFC destination parameters for the SAP source system in BW. To do this, choose Tools ® Administration ® Administration ® Network ® RFC Destinations in BW.
Enter the information taken from the source system on the server name.
u2022     Application server: pswdf090
u2022     System ID: IDF
u2022     System number: 90
The destination name has to correspond to the logical name of the source system that you entered for the process step Define Logical System in the implementation guide for the source system. For user and password, enter the background user that you created in step 1.
3.     Define the RFC destination parameters for the SAP BW in the source system. To do this, select Tools ® Administration ® Administration ® Network ® RFC Destinations in the source system. Enter the server name information taken from the BW system.
The destination name has to correspond to the logical name of the BW system that you entered in the process step Define Logical System in the BW Customizing Implementation Guide. ALE communicates using the name of the SAP Business Information Warehouse that you defined. The defined name represents how the SAP Business Information Warehouse is identified. For the user and password, enter the background user that you defined in the BW Customizing Implementation Guide under Business Information Warehouse ® Links to Other Systems ® Link Between SAP Systems and BW.
4.     Test both RFC destinations with the functions Test ® Connection and Test ® Authorization.
If an error occurs during the authorization check, the background user is not permitted in this client and with this password. If an error occurs in the connection test, it means there is a network problem.
5.     In the BW Administrator Workbench choose SOURCESYSTEMTREE ® Root ® Context Menu (right mouse button) ®Create and select the radio button for the manually creating an SAP source system.
6.     Enter a description for the source system and the logical name of the source system that you entered for the process step Maintain Logical System in the source system implementation guide.
If you still have any issues, let us know.
Regards,
Yogesh.

RSA1 Source System Hierarchy Issue (SRCTYPE of RSBASIDOC)

Dear Experts,
Greetings to you all and thanks in advance for your valuable responses!
I am stuck here with a BW issue again. The issue is:
We have a DS connection, which earlier used to get displayed under DATASERVICES node, but I don't who/what changed what/how and now it gets displayed under External System. No matter what I do, it still stays there and due to this we are having issues in Data Extraction.
This our DEV system and in QA we don't have this issue. I don't know what/where to compare.
Earlier, I had the same display issue (but that was an R/3 system) which was solved by 1087980. Still I tried:
Deleted the entry with RSAP_BIW_DISCONNECT.
Recreated the entry under Data Services node, but it still didn't work. It jumped back to External System.
I have compared the tables and found that the SRCTYPE in RSBASIDOC is responsible for all this it should be 'X' instead of 'B'.
Can we change this manually from SAP level? If yes, then how and if no, then is there any alternative?
Thanks,
Avishek

Hi Avishek,
Check whether the sapnote 1692642 - Data Services source system for 3.x DataSources
is relevant to your system or not.
If relevant , then apply it and recreate the source system.
With Regards
Ashutosh Chaturvedi

BI Source system (critical issue)

Hi Friends,
I am working as a basis consultant.
we have a ECC6 Development server and in the same server we hav installed BI-Cont and using as a BI Dev sever too.
Client - 400 is R/3 Develop server
Client - 300 is BI Develop server
we cofigured 400 client as a source system for bi(300) and lot of develpments are made.
Now we are planning to make this ECC6 DEV as a Production server for BI. (simultaniously R/3 developments also will happen in the same server).
Now i have Created a new client-500 for BI(Production) in the same server and i want to add our R/3 Production server client-900(different server) as a Source system.
1 I maintained RS_MANDT_UNIQUE_SET and set to client 500.
2 I maintained table RSADMINA and set client 500
and BW_user
3 Created RFC between client 500 to PRD server client 900
now when i tried RSA1 Transaction in BI PRD client 500, it says "Logical system name has been changed for this system" "Message no. R3206"
when i see the long text it says
"The logical system name of this system is PRDCLNT500. However, this system was originally created with the logical system name DEVCLNT300. It is not permitted to change the logical system name, as connections to other systems will be damaged beyond repair.
System Response
The transaction is canceled.
Procedure
Change the name of the logical system (table T000) for client back to DEVCLNT300. This enables you to continue working with the system.
If you really want to change the logical name, than you can, if and when you:
change the system name back to DEVCLNT300,
delete all existing connections between this system and other systems,
delete all transfer structures that still exist, and
do not use ALE or Workflow."
1 I tried to remove the source system from 300, but it is prompting to delete lot of packages and it is going for a while. so i stopped it.
2 I removed all the RFC Connections between 300-400
3 I deleted the logical system "DEVCLNT300".
Still the same Issue "Logical system name has been changed for this system".
Please help me Resolving this issue, since this issue became so critical.
Thanks in advance
Prakash

Thank you for Replying
I know the landscape we are having will confuse.
In ECC6 DEV Server a new client 500 is created for BI Producion server (not exactly prod but assume like that).
There is seperate R/3 Production server (client-900) and that shud be configured as a source system for the new BI PRD Client 500.
I dont want any data from 300, infact i would delete the 300client (BIdevclt) after i configure everything in client 500.
I did all the BI post installation steps for client 500.( including RS_MANDT_UNIQUE_SET)
but since the 300 client was configured as BW dev in the same server, i am getting an error if i access RSA1 in client 500 "Logical system name has been changed for this system" "Message no. R3206"
I went through the BDLSS transaction, but it talks about converting logical system and i dont want to do that.
Client400 is configured as source system for bi dev 300. I want to delete all the configuration made in 300.
I want to know deleting the souce client manually from BI dev 300 client is the only way to fix this or anything else we could do it for this ERROR.

Recover from source system deletion

Hi experts,
Our source system assignment to ECC was accidentally deleted which subsequently deleted the transfer stuctures/rules. Apart from restoring from backup, how can we recover the transfer rules? We could manually assign the source system again but there too many to be performed as well as we could not possibly recall all the routines, formulas and infoobject mapping.
Assistance is greatly appreciated.
Thanks!
ismail

Hi Arun,
Re-transport from QA is one of the options and our Basis is recommending that as well. Our options in order of preference is as follows:
1) Restore from backup
2) Re-transport from QA
3) Manually re-create
Thanks for your thoughts.
ismail

Source System Deleted

I am running 2004s SP 10 and have recently delete a source system that no longer connects to an r/3 client.
The problem is that I cannot access transport connection and BI Content tabs in RSA1 because I get an error telling me that my deleted source system cannot be found. I have also noticed there are still some transformations and datasources that still exist and cannot be deleted.
Can someone tell me how to delete these objects or suggest how I can solve this problem.
Thanks

Hi
here is function module by executing this u can dissconnect the source sytem
RSAP_BIW_DISCONNECT
and also using this u can reconnect also
RSAP_BIW_CONNECT
Hope this will help u
Regards,
M Kalpana

Source System Deletion Process in BW

I deleted the Sourse system (NQ2) in BW sandbox server (BSN) using RSA1 with right click option. During this deletion process, it deleted all the dependent objects. Now i connected BSN system to another Source System (NSB) and replicate and activate the datasource successfully.
Now when i checked the infosources in RSA1, say 2LIS_13_VDITM, no datasouce is assigned to this infosource. I can manullay assign the datasource.
is it the right approach to delete the source system and connect to another source system? Do i have to manually assign the source system to all inforsources?
Regards
Amarjit

Hi,
it wasn't necessary to delete your old source system. By doing so you have deleted all independant objects: transfer structures, transfer rules and most important, your PSA data which could be used for testing.
You could have kept your old source system to use it a template.
For instance it would have been possible to recreate all your TRules like for like from your old source system with a special transport by collecting all source system dependent Objects with a "save for system copy".
You would have saved a lot of work!
hope this helps...
Olivier.

Source System Connection Issue after BI 7 Upgrade

Hi all,
We have just upgraded from BW 3.1 to BI 7.
After the upgrade, I checked the connection to our R3 4.6 source system.
It is now saying the following message:
Source system XXX is marked as inactive in BI.
Check failed for RFC connection XXX ; check destination
After going through the RFC connection, I tested the connection for this source system. It said OK. While doing the authorization test, it said: "Name or password is incorrect. Please re-enter".
The thing is that our name & password ARE correct definitely.
Is there any issues post upgrade because authorization stuff between R.3 4.6 (PI 2004.1 SP15) and BI 7?
Any ideas?
Thank you
chris

Hi,
as from NW7.0, passwords are case-sensitive.
If you define the passwords in the RFC in uppercase, it will work.
This is a problem when you link an 'old' (not NW 7.0) system to a NW 7.0 (as in this one, passwords are case-sensitive).

Source system deletion before copy or refresh of Non productive system

Hi
regarding the refresh of non prod BI system. . As part of refresh, we were asked to follow note 886102.
In this Scenario B3 matches to us. While doing the scond step. I have to delete source systems from RSA1 except my self system.
It is taking long time to delete source systems as each object of source system is prompting for request and consuming long time to complete thsi activity.
Please help me with a smarter method to delete the sourcesystems.
Thanks,
Haaris
Edited by: Hari Prasad Bolla on Jul 14, 2010 8:50 PM

Hi:
The primary source of information is the how to paper on this topic:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/bff13df2-0c01-0010-6ba7-bc50346a6fd8
YOu are correct, you can refreh the BI system without deleting the source system.
Thanks for any points you assign (after all, I wrote the paper!).
Best Regards -
Ron Silberstein
SAP

Source system deletion

Hi ,
We have two R/3 systems as Source systems for our BW.
Right now,both are in a postion to give data for lot of Data targets.
And now, we are planing to drop one source system.
So, kindly give me an idea about the steps to be followed
to make sure that there will be no problems after dropping
(like Metadata inconsistency...etc) .
Kindly provide few notes on this issuse also.
With rgds,
Anil Kumar Sharma .P

Hi Anil!
i think first you got to remove all the source system assignments for all the InfoSources with this particular source system by deleting transfer rules. one more thing is about logical system dependency of your data, i mean if there is any data which has 0logsys compounded and the data is loaded from this source system. then determine what you are going to do with this data and how you are going to refer it in future.
and once you are sure there is no link between this source system and BW. you can then delete this source system by justselecting delete in the context menu of this source system.

Remote Process Chains Source Systems mapping issues

Hi,
We have a process chain in APO system, which upon success calls another process chain in BW.   We recently implemented SCM5/BI7, and taking the advantage of remote chains functionality to call the BW chain from APO.
However, when we transported the APO process chain from DEV to QA, the source systems in the remote chain are still pointing to DEV systems.   We were expecting to see both APO and BW source systems getting switched from DEV to QA.
We have already verified the logical mappings for Sources Systems are in place under RSA1 | Transport Connect | Conversion.   Also, the source systems seem to map correctly for other objects like data sources etc..   Only issue is with the remote chain.
Is there any other setting which need to be set to make it work.   Any help or guidance will be greatly appreciated.
Thanks in advance,
Ravi Chitluru.

Ravi,
I have a similar situation. Can you explain how to run process chains in APO which can gets data from BW cubes, which in turn gets data from R/3.
In this equation R/3->BW->APO, what are the options like 1)run process chains in BW system to pull data from R/3 into BW and run process chains to load BW data into APO 2)run remote process chains to pull data from R/3 into APO(of course via BW).

Source system delete

Hi folks,
Is it possible to delete the 'created' source system like FF, Datamart, R/3 etc with those icons.....
If so, please let me know.....
thanks in advance....

Hi AHP,
Thanks for your response. But I have a problem of deleting R/3 source system. The context menu has no such thing as delete. Please let me know is there anything else to look into, in order to delete the R/3 SS.

Source System Creation issue in BI

Hi Everyone,
I have already created RFC Connection in BW and EC(BackGround Users are ALEREMOTE and BWREMOTE). I am able to login using Remote Login from SM59 from BW to ECC and Vice versa. After this , When I try to create a Source System, it asks me to provide the ALEREMOTE and BWREMOTE Passwords along with the Source System Name.
I provide all the details.
Then the System asks me to login as a Administrator into ECC. And Once, I login, it throws up an error RFC Connection failed.
I think I am missing some steps.Please provide your inputs.
Regards,
Samir

Hi Ananda,
Thanks for your response. I did the same. Created Background users and when Try to Create a Source System ,it prompts me to R/3 side and here it is showing as RFC Failed. Remote Logon is working. But when Icreate a source System and provide password details, it fails.
Please advice.Is there any password restrictions for Background users.I maintained it as "init123". Do we need to use Capitals. And once, we provide the initial password, do we need to change it again somewhere?
Thanks and Regards,
Samir

Restore transfer rules after source system deletion

Hello,
due to several reasons I had to cut source system assignment.
The source system is now new connected to BW.
My transfer rules and datasources are lost.
Is there a programm, t-code, ....available to restore that stuff?
Points will be assigned.
Best regards.
Pascal

Hello,
Just go to transaction rsa13 right-click over your source system and choose "Restore"
Diogo.

Source System - Deletion issues

Similar Messages

Maybe you are looking for