Transfer Rules Deleted while recreating Source System

Hi:
We connected our QBW system to upgraded SAP ECC 6.0 QAT system. We needed to recreate the source system for ECC since that appeared inactive. After our Basis admin re-created the source system, all transfer rules were deleted. Now we can not extract data. We had done the same thing in BWD when the SAP Dev system was upgraded 3 weeks ago and we did not have this problem. Is it possible to activate all transfer rules in QAT again? Or do we have to restore a backup? Or do we have to collect them again from the Development and transport to QBW??
Thanks

Hi Sunil,
yes when you delet the source system and recreate it evey thing will be vanished
right click on the souce system click Replicate datasouce
Then try with
a) Right click on source system and click on Restore if it doesn't work
b) Transport from Development to Quality
and active all the transfer rules using the report RS_TRANSTRU_ACTIVATE_ALL
hope this information helps you
thanks
kishore

Similar Messages

Transfer rules to the new source system not visible in Transport connection

Dear All,
Recently our source system has been changed from R3 4.7 to ECC 6.O. Corresponding to that all the activities in BI have finished successfully. All my datasources in 4.7 have been replicated in ECC 6 in BI and transfer rules re-assigned. I have also collected them in a Transport request.
Now when I am checking the entire flow in Transport connection, it shows me the transfer rules pointing to the old system only. That is, in RSA1 it shows the new system assignment. But in Transport connection not.
What I have to do so that I can crosscheck in Transport connection all my objects having transfer rules to new system ?
Regards,
Srinivas

I think you should check the source system assignment in the transport connection. It might have directed to the old sytem.
Cheers
Chanda

Error in collecting transfer Rules in transport request after system copy

Hello,
Recently we had a system copy from Production to Test system.
We are trying to collect all the transfer rules from production in the transport request with the procedure which is given in the below link.
Re: Q: Transfer Rules after system copy
When we are trying to transport such objects, system first prompt for transportable workbench request, after specifying request once, it prompts for it again and after providing transport request number system results with message u201CSpecify a requestu201D.
Please suggest how to overcome this issue.

thats scary that you are copying your transfer rules from production to test system well if you guy sare doing it good luck..
a part from that make sure your prd is open so it allows items to be able to transport an dthere is a conenction between prd to test for transports to go through
if you have already copied all te data source to TEST, replicate them IN BWQ( your test system) then send over tranfer fules .
hope that helps.

Error while creating SOURCE SYSTEM

Hi All,
I have a problem while creating Source System to a Solman syatem configured with BW content. I have configured few some source systems already in the same Solman System.The system shows the following error, previous to this i get the message a "generating connection to the source system"
<b>Error in source system RXX_100
Message no. RSAR502
Diagnosis
With Remote Function Call to system RXX_100 error Screen output without connection to user. ccurred.
Procedure
Remove the cause of the error.</b>
Kindly provide me suggestions and DOCS related to the same.
Suitable points will be awarded for replies.
Expecting your kind reply,
Vineeth

Hi ,
In SCC4 the source client should not set as production when creating the source system connection between two systems.Please check below SAP note
973555 - System must be open for creating/connecting source systems
Thanks,
Shanaka

Error while activating source system

Dear friends,
I am getting Error ' Basic type does not exit' while activating source system in RSA1.
please give the solution .
Regards,
D.prabhu

Hello,
this is due to incomplete partner profiles;
When createing your source system you have to ensure that your source system is open for modifications (transaction SCC4) and that you have administrative rights in this system. Indeed the creation of a source system will create all partners profiles in both systems thus the source system needs to be open for modification.
ensure this and "restore" your source system from RSA1
hope this helps...
Olivier.

Error message: While activating source system in RSA1

When trying to activate a source system, I am getting a error message saying, Incorrect IDoc type ZSAG018 in the ALE definition of the source system.
System response: Error when sending data to BW.
Procedure: Enter Idoc type ZSAE008.
Prior to this there was a service pack that was applied to the R/3 system, and while testing thhe info package I got a error message and in source system when trying to activate, I get this message.
Can anybody kindly help me resolve the issue.
Message was edited by:
Muzafaruddin Mohammed

Hi,
You try to create the source sytem one more time by deleting it.And also delete the Partner Profiles, port number.
Re: Source connectivity problem
With rgds,
Anil Kumar Sharma .P

Error while creating source system in BI: Modification not possible

Hi All,
We are about to move to production, and therefore it's necessary to create in BI the source system related to our ECC (R/3). While trying to perform this action from BI side we received the error message:
SAP system has status 'not modifiable'. Because of this, and following with known consultants practices we've changed the client to customazing but it still not working although the message at this time is: Changes to repository or cross-client Customazing are not permitted. We have also verified transaction SE06 but it's not possible to change the Cross-Application Component to Modifiable.
Did someone face with this same problem before?
Thanks to all in advance,
Regards,
José.-

Hi Rick,
I really appreciate your quick response. We followed your recommendation and could create the source system without problems. Thanks once again!
Best Regards,
José.-

"Error in source system" while creating source system

Hello,
I don't know what's our general problem (I suppose that it's ageneral problem) but we always have the following eror while creating a source system:
When we want to create a source system on BI, we first get an error "No connection to source system possible". After checking the RFC connection and correct the password of the remote user on the automatically created _DIALOG RFC connection the exception changes to "Error in source system".
The error occurs after the information "Please log on as an administrator in the following screen".
The remote user on R/3 side has got profiles S_BI-WHM_RFC and S_BI-WX_RFC (found two conflicting statements regarding this profiles), on BI side it has got SAP_ALL and some more profiles
What else could be the problem?
Greetings & Thanks
Bettina

Hello,
now we know that
1. the remote user needs profiles SAP_ALL and SAP_NEW and has to be dialog user with a password unequal that password it should have in the future (otherwise you don't see the error messages that appear during the login process)
2. the system has to be changeable (scc4 and se03)
After the source system is created the changeability can be changed to the original values and the remote user can be changed to a communication user again.
Thanks for the tip regarding the authorizations.
Greetings
Bettina

How to track transfer rule / transformation changes (in source code)?

Hi all,
let's say i add a routine to a transfer rule and i transport the change request to production, there's a way to know after that what was changed doing a comparison between the two source codes?
Also, in the change request i have in this case one or more routine hashcodes like for example 4G0HLLGZZ0HR9BQQVMG7JTIBW, through this alphanumeric value i can track which routine was modified?
Thanks a lot for the help
Regards
Stefano

There is no version control for the code in Transformation Rules. If you could change your logic to call an ABAP Class then you could have some kind of version control with the Class instead. Hope that helps.

Issue in while connecting Source system

Hi All,
I mistakenly Ran the function module RSAP_BIW_DISCONNECT in BIW, I suppose to run this FM in Source system side,
We observed that Source system in RSA1 (BI) has been deleted), and also one record from the table RSBASIDOC (which is from source connection) has been deleted .
When I try to create he source system in BI, after entering logical system and ALEREMOTE and BWUSER logins, it was asking me to login to source system, after entering the details,
A pop-up message:
RFC destination already exists in source system
Do you want to use this destination, check, or
cancel source system connection?
options: USE, CHECK and Cancel, -> We pressed USE
Then it came back to RSA1 screen and a pop-up message
Connection BA is used in the ERQXXXX
source system as a connection BWQXXXX to BW.
Do you want to delete this connection in the source system?
Connection Is Restored After It Has Been Deleted Successfully
Options: Delete, Do not delete.
When we go for Delete : It is saying that "Error in source system ERQXXXXX"
Thanks in Advance,
Teena

Hi,
Please find the link which might help you:
http://help.sap.com/saphelp_nw70/helpdata/EN/00/dc54384ac9a81be10000009b38f8cf/frameset.htm
Best Regards,
rajani

Issues with BW conn. while upgrading source system from R/3 4.6 to ECC 6.0

Hello
We are upgrading our existing R/3 4.6 system to an ECC 6.0 system. In this regard, I have a few questions concerning R/3 to BW extractions.
Question 1: If we have a PROD BW system PB1 mapped to a PROD 4.6 R/3 system PR1. And then we make a copy of PB1 and call it DB1. Will we get all the transfer rules mapped between DB1 and PR1 automatically.. or do we need to re-create all the transfer rules again?
Question 2: Lets say we now want to connect our ECC 6.0 DEV system ie DE1 to DB1, do we need to re-create all the transfer rules between these 2 clients?
Thanks.
Srinivas.

Hi Srinivas,
questions 1:
no need to create again...they will link up that..it is nothing but Mirror concept...
question 2 :
This one laso no need to craeted....
So your issue is solved,post me if you have any furthur...
Regards
Srinivas

0IC_C03 delete requests when source system is deleted

Hi All,
I have a problem with my stock cube 0IC_C03. I want to delete a compressed request in this cube. The problem is that the original sourcesystem from which this request is loaded does not exist anymore. Therefore the system gives me a shortdump.
The general message is timeout during connect, which is correct because this system does not exists anymore.
Is there a way to delete this data ?
Best Regards
Marcel

Dear Marcel ,
If source system is not available and you loaded with PSA, the system would give a dump, the better way to handle is delete the entire data from the infocube and do a init again with BX and from there on with BF. this is important as Inventory infocube uses Marker Update for giving the stock details from time to time...
Thanks,
Krishna

Error while assigning source system to SAP Remote cube

I need to do a query using remote cube and the source sys is flat file.
it wont let me assign the source system to the remote cube.
the r/3 system icon is seen next to the remote cube technical name...
I can't see my flatfile source system
can somebody help me.

Hello Kiran,
I don't think its possible to use Remote cubes for PC_FILE or FLAT FILE as Source system.
You can use Virtual Providers in these different scenarios
Virtual Providers based on DTP => used for SAP source systems
Virtual Providers based on BAPI => used for non-SAP or external systems
Virtual Providers bsaed on Function modules => You use this VirtualProvider if you want to display data from non-BI data sources in BI without having to copy the dataset into the BI structures. The data can be local or remote. You can also use your own calculations to change the data before it is passed to the OLAP processor. This function is used primarily in the SAP Strategic Enterprise Management (SEM) application.
Use InfoObects as Virtual Providers
Your case is none of these.
More details can be found under this link:
http://help.sap.com/saphelp_nw70/helpdata/EN/84/497e4ec079584ca36b8edba0ea9495/frameset.htm

Error while loading source system data

BW unknown in source system
The BW IDoc type ZSBA003 is not the same as the source system IDoc type
The following errors occurred in the source system:
EDI: Partner profile not available
Entry in inbound table not found
Entry in outbound table not found
Entry in outbound table not found

hi Steve,
check with transaction we20, if your bw myself source system exist under 'partner type ls' (ls = logical system).
it should exist with
outbound parameter
message type-RSRQST
inbound parameter
message type-RSINFO RSSEND
check also for r/3 source system
you may ask basis for help.

Error msg RSAR502,while creating source system?

Hello Gurus,
when i am creating source system i got error msg called RSAR502,can any one solve this issue..
Thanks in Advance

Hi,
Check the OSS note : 184586,493422.
Take the help of ur Basis support.
Hope it helps-
MM

Transfer Rules Deleted while recreating Source System

Similar Messages

Maybe you are looking for