Extractor error

[system]

Hi All ,

Does anyone know how to resolve this error :

RFC CallReceive exception <RFC_ABAP_RUNTIME_FAILURE-(Exception_Key: UNCAUGHT_EXCEPTION)- An exception occurred that was not
caught.

Its coming up inside Data Services 4.0 sp1 for data source 0CRM_MRKT_ATTR even though “View data” for same extractor is not throwing any error.

Thanks
Mayank

---

Mayank R (BOB member since 2012-02-05)

[system]

Anyone ?

---

Mayank R (BOB member since 2012-02-05)

[system]

I dont think this extractor is on the list of available extractors for DS. How were you able to import?

---

SalH (BOB member since 2010-11-09)

[system]

Did you follow one of the steps in this thread?

120×120 10.4 KB

All, I receive the following error when trying to import extractors from an SAP Data Store in DS Designer. Any thoughts… The extractors I am trying to pull have been activated and checked (rsa5/rsa3) and the data is viewable in via rsa3. cannot import extractor <name-2LIS_02_HDR> internal error <Extractor: RDPS_REPL_SOURCES_GET_LIST failed> occoured (BODI-1116153) SalH (BOB member since 2010-11-09)

---

SalH (BOB member since 2010-11-09)

[system]

Mayank R, did you ever solved this?

Additional input…

I went to ST22 and it shows the Exception names as - ‘CX_ODQ_INPUT_INVALID’ and Error Analysis shows as below

An exception occurred that is explained indetail below.
The exception, which is assigned to class ‘CX_ODQ_INPUT_INVALID’, was not caught in procedure “_GET_OSOURCE” “)(METHOD)”, nor was it propagated by a RAISING clause. Since the caller of the procedure could not have anticipated that the exception would occur, the current program is terminated. The reason for the exception is: You do not have authorization to display DataSource 2LIS_02_HDR, component MM

What was changed in SAP system ?

1. Some patches are installed on SAP System
2. User Accounts were locked and unlocked. But not sure what SAP Team’s action on this!!

Please help!!!

---

ganeshxp (BOB member since 2008-07-17)

[system]

So you have an entry for this extractor in the table ROOSATTR?

Can you display/access the extractor via rsa* transactions your self? And if you have the similar error simply use su53 to get the autorization details?

I had only one authorization problem in the past on the BODS user: SODQADM had to be added. But that error occured when trying to inititialize the extractor the first time.

Or just forward the error to autorizations. If they do not know what kind of authorization is required, then they need to put on an authorization trace on your BODS user.

---

Johannes Vink (BOB member since 2012-03-20)