cancel
Showing results for 
Search instead for 
Did you mean: 

Can't open anyone BEx query through Analyzer or RSRT (Message Number RS_EXCEPTION 301 )Hello everyone, I have the following problem. On a newly installed BW System with fillowing parameters:

Boyan_P
Participant
0 Kudos

Hello everyone,

I have the following problem. On a newly installed BW System with fillowing parameters:

ProductReleaseVendorShort Description of Product Verion
SAP NETWEAVER7.4sap.comSAP NETWEAVER 7.4

ComponentReleaseSP-LevelSupport PackageSPP LevelSupport Package PatchTypeShort Decription of Component
SAP_BASIS7407SAPKB740070-SAP Basis Component
SAP_ABA7407SAPKA740070-Cross-Application Component
SAP_GWFND7408SAPK-74008INSAPGWFND0-SAP Gateway Foundation 7.40
SAP_UI7409SAPK-74009INSAPUI0-User Interface Technology 7.40
PI_BASIS7407SAPK-74007INPIBASIS0-Basis Plug-In
ST-PI2008_1_7107SAPKITLRE70-SAP Solution Tools Plug-In
BI_CONT74710SAPK-74710INBICONT0-Business Intelligence Content
BI_CONT_XT74710SAPK-74710INBICONTXT0-Business Intelligence Content for Bobj I
SAP_BW7407SAPKW740070-SAP Business Warehouse
RTLPOSDM100_7314SAPK-10204INRTLPOSDM0-RTLPOSDM
ST-A/PI01R_7310-0-Servicetools for SAP Basis 731

When I try to execute any BEx Query we get the following error:

EAn exception with the type CX_SY_DYN_CALL_ILLEGAL_FORM occurred, but wasRS_EXCEPTION000An exception with the typeCX_SY_DYN_CALL_ILLEGAL_FORM
  ESubroutine call failed: The index specified had the value 7.184, which waRS_EXCEPTION000Subroutine call failed: The index specified had   the value 7.184, which was
  AAn error occurred when getting data from the processor.BRAIN670
  I>> Row: 273 Inc: GP00O2TOY9WCRHXPMOCUI7KQ0K0 Prog: GP00O2TOY9WCRHXPMOCUI7RS_EXCEPTION301GP00O2TOY9WCRHXPMOCUI7KQ0K0GP00O2TOY9WCRHXPMOCUI7KQ0K0


The error is the same when the query is execute through BEx:

and RSRT:

I install some DSO - 0PP_O01 (Goods Being Processed (Quantities) from BI Content, just for the test. I loaded data into it w/o any problems or error. I rewiew the data. There are about 6K records, that is enogh for test.

Then i wrote a simple BEx Query but got the above error.

Than I started to look for applicable Note and find the following Note:

2106561 - Query execution aborts with CX_SY_CONVERSION_NO_NUMBER or CX_SY_DYN_CALL_ILLEGAL_FORM

Unfortunately from BASIS Team said that that Note is not applicable for may case because of the latest version of BW Kernel.

Is anyone has any idea what could be the problem?

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

Can you please tell whats your Kernel version currently installed on your system.

Please check whether its according to the note :

1969546 - Release Roadmap Kernel 740

Check whether you get the issue only with latest Kernel or also with a lower Kernel patch.

Also check below note and check whether you are using any of the characteristic mentioned in note.

Please check the settings as mentioned.

2074801 - Dumps and Issues with special InfoObjects like 0FISCYEAR, 0CALMONTH...

Please try to again regenerate the query in RSRT using the button "Generate Report".

Please then check the issue again.

Regards,

Amit

Boyan_P
Participant
0 Kudos

Hi Amit,

About the Kernel - here is the information:

Kernel Information
Kernel release742
CompilationNT 6.1 7601 x86 M
Sup.Pkg lvl.17
ABAP Load1981
CUA load40
Modeopt
Rsyn file
Database Information
DB client lib.DB6_81
DB releasesDB6 09.07.*, DB6 09.08.*, DB6 10.*
DBSL version742.06
DBSL Patch Level15
SAP versions
SAP versions700, 710, 701, 702, 703, 711, 720, 730,  731, 732, 738, 740

Remainig part of your advices could be checked at monday by the BASIS Administrator.

former_member532796
Participant
0 Kudos

Hi Boyan,

How did you fix this issue? We are also having the same issue after upgrade to 7.4 SP12.

Appreciate if you post the solution.

Thx.

Boyan_P
Participant
0 Kudos

We could not find a working solution so our BASIS team reinstall the BW again. In our case it was a totally new BW system for new client without any data.

But I think that that is not some kind of solution that's why I had not put it here as a solution.