cancel
Showing results for 
Search instead for 
Did you mean: 

While executing query in BEX analyser shows syntax error in program SAPLXRSR

Former Member
0 Kudos

Hig

When i login into SAP 7.3 and process Bex analyser t-code and login again

I am trying to execute query that shows below error -

"An error occured while communicating with BW server

As a result of this error , system has been disconnected from BW server

Detailed description

Syntax error in program SAPLXRSR"

System into which i logged in is BI and when i run t code for bex analyser i select this same system with same SID and hostname.

I have checked internal RFC for BI and its connection test is successful.

What could be next step ???

Few lines from ST22 dumps -

"

What happened?

    Error in the ABAP Application Program

    The current ABAP program "CL_RSROA_SMOD_COMP_MEDIATOR===CP" had to be

     terminated because it has

    come across a statement that unfortunately cannot be executed.

    In include "ZXRSRU01                                ", in line 125 of program

     "SAPLXRSR                                ", the following syntax errors

    have occurred:

    "VANYOMESFIN" cannot be converted to the line type of "I_T_VAR_RANGE".

            Author and last person to change the include are:

    Author         Axxxxx

    Last changed by "Sxxxxx     "

What can you do?

    Correct the error by running a syntax check (or extended program check)

    on program "SAPLXRSR                                ". You can also run the

     syntax check from the ABAP

    Editor.

    If the problem persists, proceed as follows:

Error analysis

    The following syntax error has occurred in program SAPLXRSR

                 :

    "VANYOMESFIN" cannot be converted to the line type of "I_T_VAR_RANGE".

    " "

How to correct the error

    Probably the only way to eliminate the error is to correct the program.

    -

    If you cannot solve the problem yourself, please send the following

    information to SAP:

    1. This description of the problem (short dump)

    To do this, choose  System -> List -> Save -> Local File (unconverted)

    on the screen you are in now.

2. A suitable system log

To do this, call the system log in transaction SM21. Restrict the time

interval to ten minutes before the short dump and five minutes after

it. In the display, choose System -> List -> Save -> Local File

(unconverted).

3. If these are programs of your own, or modified SAP programs: Source

code of these programs

To do this, choose  More Utilities -> Upload/Download -> Download in

the Editor.

4. Details regarding the conditions under which the error occurred or

which actions and input caused the error.

User and Transaction

    Client................. 001

    User.................. Axxxxx

    Language key.......... E

    Transaction.........

    Transaction ID...... 8C4720E38F3CF19894E800155DC31D04

    EPP whole context ID......

    EPP connection ID........

    EPP call counter......... 0

    Program.............. CL_RSROA_SMOD_COMP_MEDIATOR===CP

    Screen.............. SAPMSSY1                                3004

    Screen line.......... 2

    Active debugger..... "none"

Server-Side Connection Information

    Information on caller of Remote Function Call (RFC):

    System.............. ########

    Installation number ##########

    Database Release..... 720

    Kernel Release...... 720

    Connection type..... "E"  (2=R/2, 3=ABAP-System, E=External,

    R=Reg.External) call type....... synchronous and non-transactional (emode 0,

     imode 0)

    Inbound TID..........

    Inbound Queue Name...

    Outbound TID.........

Outbound Queue Name..

Client................. ###

User.................. ############

Transaction.........

Call program............designer

Function module..... BAPI_MDPROVIDER_GET_DIMENSIONS

Call destination..... <unknown>

Source server...... DMZSV709

Source IP address.. 212.190.195.109

Additional information on RFC logon:

Trusted relationship..

Logon return code.... 0

Trusted return code.. 0

Comment:

- In all releases prior to 4.0, no information is provided about the

caller.

- The installation number is provided in caller Release 700 and higher.

Additional information on RFC logon:

Trusted relationship..

Logon return code.... 0

Trusted return code.. 0

Comment: In Releases < 4.0, information about the RFC caller might be

missing or incomplete.

Information on where terminated

    The termination occurred in ABAP program "CL_RSROA_SMOD_COMP_MEDIATOR===CP",

     in "IF_RSROA_SMOD_COMP_MEDIATOR~OLAP_BADI_DEFINE". The main program

    was "SAPMSSY1                                ".

    In the source code, the termination point is in line 2 of (Include)

    program "CL_RSROA_SMOD_COMP_MEDIATOR===CM002".

Please help regarding this

With Regards

Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
0 Kudos

Hi

Can i apply any notes to correct this.

With regards

Former Member
0 Kudos

this is not a patch/upgradation issue, this is cmod code problem try to resolve that code synatctical erors.

u can't apply any note for this,once your code is correctly defined it will work definitely.

Regards,

Giri

former_member182470
Active Contributor
0 Kudos

Before applying Notes, Have you checked the CMOD code as per the suggestions? If everything is Ok, then you can go for Notes.

anshu_lilhori
Active Contributor
0 Kudos

Hi,

Check the cmod variable definition used in this query and also the code written for them.

Else share the variable details and the code with us.

Regards,

AL

Former Member
0 Kudos

Hi

taking help of abaper to check the variables and progeam.

Will update this thread once resolved.

With regards

former_member182470
Active Contributor
0 Kudos

If you observe your error, everything has been clearly given by SAP which line of code and which Include the error has occurred.

Take an ABAPer's help to check the syntax correctness in CMOD. It says something about SMOD also.. Please check everything thoroughly and test the query in RSRT.

umashankar_poojar
Active Contributor
0 Kudos

Hi,

       As Ram is pointed, there could be some syntax error in CMOD code. So check the code and refer below threads for similar issue but in ABAP.

http://scn.sap.com/thread/1557590

http://scn.sap.com/thread/2079279

Search results

http://search.sap.com/ui/scn#query=cannot+be+converted+to+the+line+type&startindex=1&filter=scm_a_si...

Hope it helps you to fix the issue.

Thanks,

Umashankar

RamanKorrapati
Active Contributor
0 Kudos

Hi ,

Seems like you have some custom variables which rae written at Tx-  CMOD. its calling include program.

so do the syntax check for the written code 

Include ZXRSRU01. if you face errors there take abap help and do the necessary corrections on logic.

Thanks