Error connecting ECC source system to BI

Hi Guru,
I'm trying to connect with ecc system to my bi.
My 100 client is ECC & 110 client is BI(already connected). I want to replicate ecc meta data(data sources) to bi..
But I'm connecting getting this error..
Kindly give your valuable feedbacks.
Thanks & Regards,
JTS

Issue Solved.
Problem with RFC connection.
Regards,
JTS

Similar Messages

Could not make connection to source system

Hello Experts,
I am trying to fetch data based on selection for last month in info-package but when I try to enter selection (pull down button), I get error message - "Could not make connection to source system..."
Any idea why this message?
I have already checked connection to ECC - is fine.
Datasource is replicated.
Also if I try to run info-package without selection - I am getting yellow status, No data fetched. RSA3 shows many rows but Info-package to data (Full extraction.)
Regards,
SM

Srini/Vikram,
user credential is good. sm59 connection is good. there is data in selection as RSA3 fetches rows in ecc.
when I run any info-package - I am getting yellow status? No data while rsa3 indicate data for Full update?
why so?
I am more of design person, not much into hands-on - so seeing these error for first time.
Q1) if a package is already schedule - let us sat thru data source 2lis_11_vaitm. Now I want to go back and retrieve last month data already extracted... once again. I should be able to pull this data in new infopackage using Full update - data selection option.
Q2) - rsa3 should fetch data based on set-up tables, so any infopackage based on Full update mode - should fetch data - independent of any other infopackage.
q3) we need to do delete and fill-set-up table - only if extract structure is changed? right?
regards, sm

RFC connection to source system is damaged , no Metadata uploaded

Hello Friends,
I need your help to understand and rectify why my transport is failing again and again.
RFC connection to source system BT1CLNT200 is damaged ==> no Metadata upload
Environment - Production Support (Dev - Quality - Testing - Production)
Alive scenario - Need to create two InfoObject and incorporate the fields in to data targets and reports.
What we have did?
1st request - We have created new request and captured two Infoobjects in to the request.
2nd Request - We have captured the replicated Datasource along with that the below sequence displayed by default in the same package.
Communication structure
DataSource Replica
Transfer Rules
InfoSource transaction data
Transfer structure
3rd Request - we have captured DSO and Cube only in this request.
4th Request - Captured 2 update rules (ODS) Update Rule (Cube)
The above 3rd request failed in the testing system (successful in Quality System) and ODS is inactive in the Testing system.
Testing system Error Message:
The creation of the export DataSource failed
RFC connection to source system BT1CLNT200 is damaged ==> no Metadata uploa
RFC connection to source system BT1CLNT200 is damaged ==> no Metadata uploa
Error when creating the export DataSource and dependent Objects
Error when activating ODS Object ZEOINV09
Error/warning in dict. activator, detailed log > Detail
Structure change at field level (convert table /BIC/AZEOINV0900)
Table /BIC/AZEOINV0900 could not be activated
Return code..............: 8
Following tables must be converted
DDIC Object TABL /BIC/AZEOINV0900 has not been activated
Error when resetting ODS Object ZEOINV09 to the active version
So we have captured the data mart Datasource and created a new( 5th ) request (transported only 5th request )and transported in the below sequence
Communication structure
Datasource Replica
Transfer Rules
Infosource transaction data
Transfer structure
development to Quality - Successfully
Failed in testing system again.
How to rectify this error, please help us
Thanks,
Nithi.

Hello All,
*Question -1*
I have checked the connections and typed the steps below - what i have seen in the screen.
Steps :
R/3 Connection - I have double clicked on the BT1CLNTXXX and tested the connections.
Connection Type :
Logon - 0KB , 10 KB , 20KB, 30 KB
R/3 connection:
5 msec, 0msec, 1msec,1msec,1msec
Please let me know whether RFC connection is OK or not.
Question - 2
I want to know is there is any option to check before transporting the TR from Developement to Quality - "Preview Check " the sequence , so that we can avoid the Transport failure because of TR sequence.
Regards,
Nithi.

Which types of errors occured in "source system"?

hi
which types of errors occured in "source system"? how will correct it? send me data on it

Hi,
The common error will be RFC Connection .pls chk this links;
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a61e5e07211d2acb80000e829fbfe/frameset.htm
http://help.sap.com/bp_biv335/BI_EN/BBLibrary/documentation/B84_BB_ConfigGuide_EN_DE.doc
Hope this helps.
Regards
CSM Reddy

RFC connection to source system ABPCLNT310 is damaged

Hello,
I'm importing a transport in BW Prod (condition type data for billing and orders), but receive this error message in STMS:
The creation of the export DataSource failed
Reading the Metadata of 0SD_O05 ...
Creating DataSource 80SD_O05 ...
RFC connection to source system ABPCLNT310 is damaged ==> no Metadata upload
RFC connection to source system ABPCLNT310 is damaged ==> no Metadata upload
Error when creating the export DataSource and dependent Objects
Error when activating ODS-objekt 0SD_O05
The creation of the export DataSource failed
The import worked fine in BW QA system. Why do I get this error? It is possible to manually generate the export data source from the ODS object, but when I try to import again, it once again fails...
Best regards,
Fredrik

hi Fredrik,
check if helps oss note 597326, 886102, 184322
RFC connection to source system Damaged
Error when transporting ODS Object
597326 - Activating ODS: Error when creating the export DataSource
Symptom
When you activate or transport ODS objects, the following errors appear in the log:
"The creation of the export DataSource failed". Message number RSBM 035
"Error &1 in function module &2". Message number RSBM 006
"Error when creating the export DataSource and dependent Objects". Message number RSDODSO 169
"Error when activating the ODS object &1". Message number RSDODSO 168
Other terms
RSBM 035, RSBM 006, RSDODSO 169, RSDODSO 168
Reason and Prerequisites
A characteristic involved is active but it is using new or inactive attributes.
Characteristics involved are all characteristics used in the ODS object.
Solution
Check all characteristics involved as described in the following:
Check the Compounding and Attributes tabs in the characteristics maintenance.
All characteristics here must be active. This is displayed by a green icon.
If this is not the case for a characteristic involved (a gray icon is displayed on one of the two tabs), activate the characteristic involved. This also activates the inactive dependent characteristics.
After you have checked and repaired all the characteristics involved as described above, the loading/maintenance of master data should work again

Create ECC source systems to talk to BI

I am a developer and the system that I am working with do not have the source systems created. There is no Basis support here yet. Would someone help by listing the steps to create the source systems, so that the ECC systems can talk to the BI NW2004s system? I want to be able to load data.

Hi,
Please check these links.
Connection between Source Systems and BW
http://help.sap.com/saphelp_nw70/helpdata/en/00/dc54384ac9a81be10000009b38f8cf/frameset.htm
Creating SAP Source Systems
http://help.sap.com/saphelp_nw70/helpdata/en/ac/4a4e38493e4774e10000009b38f889/frameset.htm
BW connectivity(.doc)
http://help.sap.com/bp_biv335/BI_EN/BBLibrary/documentation/B84_BB_ConfigGuide_EN_DE.doc
hope this helps
Regards.

IP failed due to errors in CRM source system

hi
After executing IP full load for data source 0crm_oppt_h, i was unable to get the records( 0 records from 0). i checked in crm dev side in rsa3 , i am able to get the records there. so i have deleted the datasource and replicated once again. After activating update rules and transfer rules properly i have scheduled the IP, i am getting error message as ' error occured in source system '.
I have no selections is IP. I have checked the Idocs, trfc and the source system is connection is ok
I have checked the job in source system , It is cancelled. the job log is given below. I want to know how to correct this and what the steps i need to take futher. I am new to CRM . Please guide me
'You are not participant in the private activity CRM_ORDER 027 E'

hi
After executing IP full load for data source 0crm_oppt_h, i was unable to get the records( 0 records from 0). i checked in crm dev side in rsa3 , i am able to get the records there. so i have deleted the datasource and replicated once again. After activating update rules and transfer rules properly i have scheduled the IP, i am getting error message as ' error occured in source system '.
I have no selections is IP. I have checked the Idocs, trfc and the source system is connection is ok
I have checked the job in source system , It is cancelled. the job log is given below. I want to know how to correct this and what the steps i need to take futher. I am new to CRM . Please guide me
'You are not participant in the private activity CRM_ORDER 027 E'

Conversion factor error in the source system

Hi All,
I got conversion factor error in the source system, when i tried to load maste data.
can anybody help me in. It is urgent please...
Thanks in advance
Narendra

Hi...Post the error
Regards

Question about Note 886102 - Empty the delta queue of the connected SAP source systems

Dear expert
I'm doing the system refresh from ECC PRD to QAS using the hot backup of PRD
Before i start the database restore i was told to do the following step since this ECC has connection with one BW system
-----------------------Step -----------------------------
2.17 SAP note 886102 scenario C3
Empty the delta queue for all of the connected BW systems.
Execute all delta info packages two times on BW side, to clean up the delta queue in the source system. This is needed, because BDLS cannot rename the still available LUW-s in the qRFC queue.
----------------------Step-----------------------
But unfortunately i missed to execute this step
And the Q11 is now retoreing the backup of the database
My quesion
1. what will be bad consequence due to not execute this step? any way to makeup this error?
Best regards,

Hi Kate,
The probably issue which I could forsee is data getting wrongly updated into production if RFC connection from ECC to BW is not stopped.
Solution here could be to disable or deletethe RFC connections between ECC and BW before starting the SAP system at database level.
delete from sapr3.rfcdes where rfcdest = '<name>';
Once the system is up and running you can recreate them if required.
Also before starting SAP set the number of batch processes to 0 on the profile at OS level so that any released jobs don't start as soon as SAP is up.
Once the SAP system is up execute BDLS and change the logical system name.
Hope this helps.
Regards,
Deepak Kori

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 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 when creating source system

Hi,
Could someone help me to solve this issue :When I want to create a source system D99100 in BI , I get the following message:
the test and remore connection via sm59 in BI are OK.
Source system cannot use any of the proposed connection names
Message no. RSAR362
Diagnosis
Every connection to a source system is named using a unique two-digit identifier. Source system D99100 does not accept any of the proposed values.
The last proposed value was B9.
System Response
Source system has not been connected.
Procedure
If you want to recreate the source system from BI information, then you can only use a single value, namely B9, because the connection already has this name in BI.
Delete the existing connections in the source system or contact a BI consultant.

Hello,
By this time your issue might be resolved.
When you are trying to Connect or Reactivate source systems you might get this error. In the source system (R/3) check the table entries RSBASIDOC. Some reason after system copy, these entries should correct if you run BDLS and some time it mess up.
Go the table and go to the edit mode and change the entrie for that RFC destination. Change the filed TSPREFIX to some thing else and save it. Go back to BW and try to reconnect and you will be able to connect it.
Hope this helps in the future for this thread.
PREDDY.

Error while creating source system entry in SAP BW system

Hi,
I am creating source system entry in SAP BW system for ECC system.In T-Code RSA1 i entered all the details of source system and BW system like RFC destination of source system and RFC user passowrd.
After clicking on enter system is promting me to enter into the souce system using administrator user.but i don't have admin user with SAP_ALL and SAP_NEW profiles because in my organisation they don't assign these profiles to any user.
So can you please update me what are the authorization required for dialog user in source system.
Regards,
Gaurav

I would recommend to create a USER ID as COMMUNICATION type and assign SAP_ALL for it... this way, it can never be misused..
This will ensure that the user ID will have correct authorization in the source system and will not face any authorization related errors later on

Error connecting multiple BW systems to one OLTP system

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

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

Error in the Source system while data loding through Process Chain

Hi,
I am facing issue while data loading for certain extractors through Process chain. Load of 0BPM_WIHEAD, 0BP_LOGHIST, OBPM_OBJREL, 0BPM_DEADLINES(there are 2-3 more extractors) is getting failed daily with message Error occurred in the source system and if we repeat the same it is getting executed successfully.
Regards,
Javed

Hi..
It means that the extraction job is failing in the source system..
Please check the Job log in the source system --> Copy the request nimber --> In the source system go to SM37 --> Give * then the request number......execute --> Check the Job log..
Look there may be multiple reasons behind this....
1) Connection problem : Go to SM59 and test the connection, If you don't have the access in SM59...then go to RSA1 --> Source Systems --> Right click --> Connection Parameters --> Connection Test
2) Or may be work processes are not available and due to which jobs are failing due to time out...
In both the cases you can check with the Basis Team if they can suggest something....or you can change the process chain scheduling time if possible, and schedule it in such a time when less no of jobs are running..
Regards,
Debjani..

Error connecting ECC source system to BI

Similar Messages

Maybe you are looking for