BEx Query Designer Jump Query Error

Creating a jump query from BW (nw2004s) to R3 (6.20).
Services in SICF activated
webgui, system and shuffler all published to internal.
Table TWPURLSVR maintained on the R3 side.
The query logs into the portal, but upon attempting to do a dispaly w/in the query receive the following:
Business Server Page (BSP) Error
What happened?
Call of BSP page terminated due to error.
Note
Following error text processed in system:
BSP Exception: the Application Name ! in URL /sap/bc/bsp/rsrr_web/!?okcode=ENTR&G_S_WEB-DEST=TW1C100&G_S_WEB-HANDLE=45FDQG3EXVLGC22F7ZTBYNX6I&client=100&language=EN&logingroup=SPACE is invalid.
Error Type:
Your SAP Business Server Pages Team
Any suggestions appreciated!

Whats your R/2 WAS version?
Delete the entries from the TWPURLSVR table and maintain it in RSBBS_RSRR_URL where you can store the full URL and dont have to worry about the different fields.
If 620 then you will need a standalone ITS and the URL can be maintained in the format below.
http://<server port>/scripts/wgate/webgui/!?client=100&transaction=RSRR&
For WAS 640 and above.
http://<server port>//sap/bc/gui/sap/its/webgui?

Similar Messages

BEX Query error at Program SAPLRSDU_UTIL_DB2 - 'Table Does not Exist'

Hello all,
My BEX Query was running fine till yesterday in QAS system, but today when i try to execute either in RSRT/Analyzer i am seing this error:
Runtime Errors         RAISE_EXCEPTION
Date and Time          10/26/2011 14:03:44
What happened?
     The current ABAP/4 program encountered an unexpected
     situation.
Error analysis
     A RAISE statement in the program "SAPLRSDU_UTIL_DB2" raised the exception
     condition "TABLE_DOES_NOT_EXIST".
     Since the exception was not intercepted by a superior
     program, processing was terminated.
     Short description of exception condition:
     For detailed documentation of the exception condition, use
     Transaction SE37 (Function Library). You can take the called
     function module from the display of active calls.
Trigger Location of Runtime Error
     Program                                 SAPLRSDU_UTIL_DB2
     Include                                 LRSDU_UTIL_DB2U35
     Row                                     41
     Module type                             (FUNCTION)
     Module Name                             RSDU_GET_PARTITIONING_TYPE_DB2
Any suggestion?
I would really appreciate you help!
Thanks,
DC

Thanks you all for your response!.
Checked the Info providers, Tranformations - All are active.
Couple of reports which are based out of same MultiProvider are giving the same issue.
I could figure out where the problem is!
There is a RKF (in all the error giving queries) and 'GL Account' has been restricted with a Heirarchy 'ZZ21430 in it - but this restricted hierarcy is missing in 'RSH1'.
Dev system - 'ZZ21430' doesnt exist in RSH1 and query doesnt give any error, is running fine.
QAS system - 'ZZ21430' doesnt exist RSH1 and query is giving error!
What could be the reason for this?
I would appreciate your help!
Thanks,
DC

BEX query error---Error reading the data of InfoProvider

Hello all,
we are getting the following msg when we execute the query-
Error reading the data of InfoProvider ZEUDPR01
Errors occurred when extracting data from DataSource 9AEU_DOM
Short Text: Error for COM routine using application program (return c
Parameter: 1028533- LC kernel
Message in Source System: E102(/SAPAPO/OM) ...
Short Text: COM - error Unknown
Parameter: Unknown
Message in Source System: E001(/SAPAPO/OM) ...
Messages for DataSource 9AEU_DOM from source system PA1CLNT100
Errors occurred during parallel processing of query 4, RC: 3
Error while reading data; navigation is possible
Row: 54 Inc: WRITE_MESSAGES Prog: CL_RSDR_AT_QUERY
Found
This is the error observed for a particular selection only..for rest of the selection we get the data correctly.
Please help with the possible causes of error.
Thanks,
Pallavi

Hi Pallavi,
How did you manage the pb?
we have the same error after Stack 21 (SP23)
we could not run query.
Thanks.
John

Bex query error problem

Hi Friends,
1) when i am executing the query it is showing below error.
Please give me solution how to slove below problem:-
Error no sid found for value 'TB' of Characteristic 0UNIT error
error while reading the data; Navigation is possible.
2) Variables selection not appearing while executing query
i created 2 variables on plant and material these variable screen is not appearing while executing the query.
it is showing empty screen. Plz give me solution how to solve.
I am waiting for your replies.
thanks,
Guna

Hi Ravi,
I did all the things waht u gave the tips before thread,
This query is created by on infoset.
infoset is combination of different master data.MARA and MARC this master data loaded in to ZWMAT_PLT.
MARD table master data loaded in to 0MAT_ST_LOC.
MKAL table master data loaded in to DSO ZWPROVER.
i created info set using ZWMAT_PLT,0MAT_ST_LOC and ZWPROVER.
i created query on infoset. when ever executing this query i faced same problem.
another thing is variable selection screen also not appearing.
Please give me help on this issue.
Thanks.
guna.

Bex Query Error - form LRECH_F_CHFP_01-01

Hello Friends,
My query is getting the error below when saving and running, can you please advice me some ways to get rid of? What should i check?
- System error in program SAPLRRI2 and form LRECH_F_CHFP_01-01
Thanks for your helps in advance..

What is the version you are in Bi7.0 or 3.x?
What is the GUI and the patch level you are using?
try to install the latest GUI and patch along with the .net component and check if it works fine or not?
Try to search for SAP notes related to your error.
Regards
KP

BEx query error after adjust 0vender master table

Dear Experts
Since we need change "lower case" setting on Ovender infoObject (no record with Lower case for Ovendor), To active it without delete transcation data, I manually adjust table ( P table, S table and T table ) with delete data, then active it and reload 0vendor master.
after that, when we execute report, system give the errer "System error in program CL_RSDM_READ_MASTER_DATA and form sidvaldirect_read2"
Pls help
Thanks

Hi,
The first thing to be noted here is that, the "Lower case" settings check box in the Info-object maintainance scree is not for the purpose of allowing or rejecting records with Lower case.if the lower case check box is selected then the Variable entry screen or any selection related to the info object distinguishes between Upper case and Lower case entries. If unselected then it does not distinguish between Upper case and lower case entries in Variable entry screen or any selection related to the info object.
The kind of operation on Ovender infoObject (no record with Lower case for Ovendor) must be done in Start Routine's either in the Transfer rules or Update Rules depending on your context need like its global or local.
As your previous data doesnt hole any lower case entries in 0Vendor, no need to delete the data also. You can simply write a Start routine to block lower case records from entering the system.
As far as your manipulation w.r.t to Info object tables is concerned, My suggestion is not to deal with DB tables independently, as the application may not recognise the operation of individual tables content deletion.
hope this helps.
regards,
kishore

Error while trying to run Bex Query -------- Field symbol is not assigned.

Hello Every body,
I am facing the following error after giving some value in Selection screen and trying to run the Bex Query
ERROR : Field symbol is not assigned.
Thanks in advance,
Praveen

can u plz give details of variables, what it is build on and the value u r inputing,
also is thr any dump.
double click on the error message it shows u. it will give u the detailed error message. post that too

Error while trying to Open and Delete a BEx Query in Query Designer.

Hi Experts,
I have been facing this issue with BEx Query in Designer mode for a couple of days now in Development Environment in BI 7.0.
I would like to Delete an unwanted BEx Query because I need to give it's name to another BEx Query.
Whenever I try to Open this Query in BEx Query Designer to Delete, it gives out an error saying:
"An error occurred while communicating with the BI server.
As a result of this error, the system has been
disconnected from the BI server.
Detailed Description:
STOP: Program error is class SAPMSSY1 method : UNCAUGHT_EXCEPTION
STOP: System eror in program CL_RSR and form GET_CHANMID-01 - (see long text)"
Details text is as below:
Diagnosis
This internal error is an intended termination resulting from a program state that is not permitted.
Procedure
Analyze the situation and inform SAP.
If the termination occurred when you executed a query or Web template, or during interaction in the planning modeler, and if you can reproduce this termination, record a trace (transaction RSTT).
For more information about recording a trace, see the documentation for the trace tool environment as well as SAP Note 899572.
I have tried with SAP Note 899572, but still it's the same.
Has anyone faced similar issue? Could you please let me know if you have better ideas or solution?
Your time is much appreciated.
Thanks,
Chandu

Arun - Thanks a million. You saved me Nine. It worked.
Could you also please tell me how to rename (Technical) a Query or is it still "Save the Query As" the only way...?
Points already assigned.
Thanks,
Chandu

Error in opening Query in Bex Query Designer

Hi all,
I am getting an error while opening the InfoProvider for a new Query in the Bex Query Designer.
program error in class SAPMSSY1 method : Uncaught_exception.
ASystem error in program CL_RSR and form GET_COB_PRO-02
In RSRT:
00000003      I>> Row: 78 Inc: LRRMSU13 Prog: SAPLRRMS
00000003      ASystem error in program CL_RSR and form GET_COB_PRO-02- (see long text).
With Regards

Hi Raju,
Check for the authorization
Auth object : S_RS_ICUBE , S_RS_MPRO,S_RS_ISET
Infocube subobject -> aggregate ,data ,definition.
Auth object S_RS_COMP
Activity                       01, 03, 16, 22
And let us know ...
Hope that helps.
Regards
Mr Kapadia

Error while openening InfoProvider in Bex Query Designer

Hi all,
i am getting an error while opening the InfoProvider for a new Query in the Bex Query Designer.
Error Group
RFC_ERROR_SYSTEM_FAILURE
Message
Exception CX_RSR_MESSAGE in program SAPLRRMS
RRMS_X_MESSAGE
Main Program: SAPMSSY1
Include Program: LRRMSU13
What could be the problem?
Thanks in advance
Andreas

Hello Andreas,
seems as if JCo Connections on your system have not been set up correctly.
Please have a look here:
http://help.sap.com/saphelp_erp2005vp/helpdata/en/ca/115e4088dc0272e10000000a155106/frameset.htm
Regards,
Daneil

Giving Error while opening BEx Query Designer.

Hi all,
               A user is trying to open BEx Query Designer 7.0 and she is getting this error
" SAP BEx Query Designer standalone has encountered a problem and needs to close. We are sorry for the inconvenience.
If you were middle of something, the information you are working on might be lost. "
She is not having issues while opening BEx Analyzer. She is having Office 2010. This doesn't seem to be compatibility issue with the Office. This BEx was not installed on her machine 2 weeks back and it was working fine until now.
As a first re-solution i told her to get it re-installed but still she is getting the same issue.
Thanx.

Hello,
There is no relation between Office VS Query Designer. Only with BEx Analyzer and MS Excel.
My suggestion is.
If you don't have version 7.20 of SAPGUI and Business Explorer, please download the installer.
After that, download the latest patch available and install:
http://service.sap.com/swdc
> Support Packages and Patches
> Browse our Download Catalog
> SAP Frontend Components
> SAP GUI FOR WINDOWS
> SAP GUI FOR WINDOWS 7.20 CORE
> Win32
_ > * gui720_5-10007878.exe
   | > BI ADDON FOR SAP GUI
   | > BI 7.0 ADDON FOR SAP GUI 7.20
   |_ > * bi720sp03p_301-20006596.exe
   |
   | > BI ADDON FOR SAP GUI
   | > BW 3.5 ADDON FOR SAP GUI 7.20
   | > Win32
   |_ > bw350gui720_5-20006857.exe
If persist, let me know.
Cheers
Edward John

Bex query designer -- Execute Error

Hello,
when i am executing the Bex query designer -- > Execute. i am getting the following error.
Service not attainable
What has happened?
The call of the URL http: // fe-pit-ttbw.company.com:8000 / irj/servlet/prt/portal/prtroot/pcd! 3aportal_content! 2fcom.sap.pct! 2fplatform_add_ons! 2fcom.sap.ip.bi! 2fiViews! 2fcom.sap.ip.bi.bex it was broken off, because the appropriate service is not available.
Indication
The demolition appeared on the system PIT and with the fault code 404 and the reason trouble(need) found. The selected virtual Host was 0.
What can you do?
Please, choose a valid URL. If you still dispose of no user's identification, you address your system administrator.
Fehlercode:ICF-NF-http-c:000-u:SAPSYS-l:D-i:rb3pnk2_PIT_00-v:0-s:404-r:Notfound HTTP 404 - trouble(need) found your Internet SAP Communication Framework team
Edited by: Ranga123 on Aug 5, 2010 1:14 PM

hi
have u checked if web service is active to open the report in web?
use T-Code SICF
also check if portal is up or not.
also check below post:
[SICF service - error code 404;
Edited by: Gaurav on Aug 5, 2010 2:01 PM

BEX Query Designer - Application Error

Dear experts,
I have a problem with my BEX Query Designer. Whenever I tried to save a query, I caught the following exception:
BEX Query Designer has encountered a problem and cannot proceed with the current action. We are sorry for the inconvenience.
Additional Information:
QD revision 300
Internal Error ID: E-ONGUIUNHANDLEDEXCEPTION
Error Message: Method not found: 'Void com.sap.bi.et.Communication.RZX0.RSZ_X_ELTPROP.set_PROPVERS(System.String)'
Can someone help me to solve the problem?
I am using the following version:
BI AddOn 7.X (based on 7.10), Support Package 3, Revision 520

From the log:
5:01:38 PM.31 ########## --> com.sap.bi.et.QueryDesigner.QDbApplicationData.OnGuiUnhandledException ##########
-EXCEPTION-START- 5:01:38 PM.31: ---
Exception Message: Method not found: 'Void com.sap.bi.et.Communication.RZX0.RSZ_X_ELTPROP.set_PROPVERS(System.String)'.
Exception    at com.sap.bi.et.QueryDesigner.QDbElement.ToTable(RSZ_X_ELTPROP isEltProp, QDbCopyInfo iToTableInfo)
   at com.sap.bi.et.QueryDesigner.QDbQuery.ToTable(RSZ_X_ELTPROP isEltProp, QDbCopyInfo iToTableInfo)
   at com.sap.bi.et.QueryDesigner.QDbElement.ToTables(Hashtable iTables, QDcElement iElementsToSave, QDbCopyInfo iCopyInfo)
   at com.sap.bi.et.QueryDesigner.QDbElement.Save(String iRole, String iNode)
   at com.sap.bi.et.QueryDesigner.QDbCommandSaveElement.Save(QDbElement iElement, Boolean iOutputSuccess)
   at com.sap.bi.et.QueryDesigner.QDbCommandSaveAsElement.Save(QDbElement iOriginalElement, QDbElement iSaveElement)
   at com.sap.bi.et.QueryDesigner.QDbCommandSaveAsElement.ExecuteCommand()
   at com.sap.bi.et.QueryDesigner.QDbCommandBase.Execute()
   at com.sap.bi.et.QueryDesigner.QDbCommandSaveElement.ExecuteCommand()
   at com.sap.bi.et.QueryDesigner.QDbCommandSaveQuery.ExecuteCommand()
   at com.sap.bi.et.QueryDesigner.QDbCommandBase.Execute()
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.CommandExecute(QDbCommandBase iCommand)
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.InitialCommandExecute(QDbCommandBase iCommand)
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.DoExecuteCommandInternal()
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.ItemClickedHandler(Object sender, BarItemClickedEventArgs args)
   at com.sap.bi.et.QueryDesigner.QDdEventDispatcher.MenuItemClickedHandler(Object iSender, BarItemClickedEventArgs iE)
   at Syncfusion.Windows.Forms.Tools.XPMenus.BarManager.OnItemClicked(BarItemClickedEventArgs args)
   at Syncfusion.Windows.Forms.Tools.XPMenus.BarItem.OnItemClicked(EventArgs args)
   at com.sap.bi.et.QueryDesigner.QDiBarItem.OnItemClicked(EventArgs args)
   at Syncfusion.Windows.Forms.Tools.XPMenus.BarItem.PerformClick()
   at Syncfusion.Windows.Forms.Tools.XPMenus.BarRenderer.OnMouseUp(MouseEventArgs e)
   at Syncfusion.Windows.Forms.Tools.XPMenus.BarControlInternal.OnMouseUp(MouseEventArgs e)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at Syncfusion.Windows.Forms.Tools.XPMenus.BarControlInternal.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Full Stack:   at com.sap.bi.et.common.appl.Log.Debug.WriteTraceToFile(Level lLevel, String lString, Exception ex)
   at com.sap.bi.et.common.appl.Log.Trace.Exception(Exception ex, String iAdditionalInformation)
   at com.sap.bi.et.QueryDesigner.QDbApplicationData.OnGuiUnhandledException(Object iSender, ThreadExceptionEventArgs iEventArgs)
   at System.Windows.Forms.Application.ThreadContext.OnThreadException(Exception t)
   at System.Windows.Forms.Control.WndProcException(Exception e)
   at System.Windows.Forms.Control.ControlNativeWindow.OnThreadException(Exception e)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.Run(Form mainForm)
   at com.sap.bi.et.QueryDesigner.QDbApplicationData.Run(Boolean iAsApplication)
   at com.sap.bi.et.QueryDesigner.QDbQueryDesigner.Run(Boolean iAsApplication)
   at com.sap.bi.et.QueryDesigner.QDStarter.QDStartup.Main()
-EXCEPTION-END----

BEx Query Designer Error

Hi All,
I have a problem where I have just updated to SP 18 and now the BEx Query Designer comes up with a problem, I can open the Query Desinger but when I go to open a query from my history the Query Designer shuts down immediatly.
Has anybody got any Ideas?
The SAP Gui and Business Explorer is 710.
Thanks for your help
Jay

Hi Pra,
I do not get an error message the Query Designer just shuts down.
Are there any log files I can look into to check for error messages?
Thanks
Jay

In Bex Query designer - Flat is not supported

Hi all,
In Bex query designer,
While execution of the query, the following error is coming .
Failed to process request; contact your system administrator
Error Summary
Exception occured while processing the current request; this exception cannot be handled by the application or framework
If the information on this page does not help you locate and correct the cause of the problem, contact your system administrator
To facilitate analysis of the problem, keep a copy of this error page Hint: Most Web browsers allow you to select all content, and copy and paste it into an empty document (such as in an email or simple text file)
Root Cause
The initial exception that caused the request to fail was:
Flat mode is not supported!
java.lang.UnsupportedOperationException: Flat mode is not supported!
at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.Characteristic.setHierarchy(Characteristic.java:330)
at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.Characteristic.readStateFromDomNode(Characteristic.java:542)
at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.QvCharacteristic.readStateFromDomNode(QvCharacteristic.java:379)
at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.QvStructure.readStateFromDomNode(QvStructure.java:106)
at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.AttributeContainer.readStateFromDom(AttributeContainer.java:297)
Details: Full Exception Chain
Most important error.
regards
Selvan

Hello,
I have the same problem with Flat mode is not supported! at ... Characteristic.setHierarchy(Characteristic.java:335):
Open, close, reload of the query does not help.
Other SDN-thread "500 Internal Sever - Flat Mode is not Supported!" related to transaction RSRT.
Execution of query via RSRT works, but the problem still persists in the BEx Web Analyzer.
Could be related to a BEx Web Analyzer "bookmark" ("Personalize Web Application").
I have not deleted any item. We use SAP BW 7.0 with a patch level approx. 09.2009.
The "flat-mode" seems to be the "BEx table mode".
SAP hints do not seem to fit here:
- 715820 BW 3.x Front-End Patch 14 (we use BW 7.0)
- 874825 SAPBWNews for BW 3.x Front-End Support Package 19
- 874827 SAPBWNews for BW 3.5 Front-End Patch 08 (we use BW 7.0)
- 905229 update to SAPTableTree
- 909824 Termination in flat mode when an object is deleted (old?)
- 909827 Incorrect InfoProvider-dependent characteristic values
- 910602 Condition includes too many characteristics (usage of deleted elements)
- 915215 Termination when a query definition is changed (old? visibility of elements?)
- 968273 Cache with flat files: Exception is not caught (does not apply to given error)
Any new solutions?
Best regards
Thomas

Drill down ( Collapsible Row ) Report in BEx query designer ?

Dear Friends!
I am supoosed to create a report drill down report for Purchasing History to be precise, I know that we can have drill down feature using heirarchy but is it possible for Us to have PO & PO item heirarachy ? or any other way to do drill down reporting in SAP BEx Query designer ?
like my current report is : -
| Vendor | Purchasing Organisation | Purchasing Group | Plant | PO Number | Item | Material / Service | Description | .... ( keyfigures) |
Now I am supposed to create a report in which
normal view
| Vendor | Purchasing Organisation | Purchasing Group | Plant | |> PO Number| .... ( keyfigures) | Payment |
drill down or collapsible view ( please consider the heading as data I am not talking about dynamically change of headings ).
| Vendor | Purchasing Organisation | Purchasing Group | Plant | V PO Number | Item | Material / Service | Description | .... ( keyfigures) |
is there anyway to design the report in above mention manner ? you any input will be appreciated greatly.
Thank you so much!
Regards
Naim

Hi Naim,
usually we don't do the transactional data as hierarchy. not sure the reason behind your requirement.
we can do one of the below :-
1. To have the default view as
| Vendor | Purchasing Organisation | Purchasing Group | Plant | | PO Number| .( keyfigures) | Payment |
and then user can drill down on rest of the characteristics for detailed view later on.
2. or if they don't want to drill down on characteristics;-
we can build 2 reports , one for header level information and then jump to second query for detailed information(item level) using RRI.
first query:
| Vendor | Purchasing Organisation | Purchasing Group | Plant | | PO Number| .( keyfigures) | Payment |
second query:
| Vendor | Purchasing Organisation | Purchasing Group | Plant | PO Number | Item | Material / Service | Description | .... ( keyfigures) |
Let us know if this works out?
Regards,
Sakthi.

BEx Query Designer Jump Query Error

Similar Messages

Maybe you are looking for