Bex Query Transportation Error

Hi Guru's
          While i try to access bex query for transportation using transport connection>queryElements>Query, sap throws Dump Error.
Is any body came across with this pls help me for solution.
Asap.

Hi,
This happens whenever there is not a sufficient memory available for processing. This can happen with any activity in the system like data loading, deletion, creation of objects etc.
Please ask your basis team to make sure that there is sufficient memory (tablespace) available in the system.
This will solve the issue.
Regards,
Yogesh

Similar Messages

  • BEx Query Transports (NW04s)

    I transported a few queries using transport connection collection from DEV to QA.
    <b>These were the first transports.</b>
    After these transports queries that had not yet been transported are requesting a request when they are being saved in query designer:
    <b>error msg:</b> BEx transport request '' is not available or not suitable; Choose an existing request.
    To correct this problem I created a standard BEx request in transport connection. But now, when a query is saved entries are entered in the standard request, even though the query was never transported. (??????)
    I thought the query would go to standard BEx request the first time it was changed after it was transported.
    Also, I want to create multiple requests assigned to different packages:
    How do I assign the BEx query elements to the packages for transport?

    You get that message when you try to modify a Query that has been previously transported, hence the "transport not suitable" message.  Therefore you need to assign a new transport to the query.  You can do this in two ways, Sameer mentioned one of the methods.  
    Sameer's solution is risky, keeping a transport open (assigned) picks up any changes made in the BW environment.  That means that if some other BW developer is modifying objects, they will be saved to your "assigned" transport.  Therefore you must be careful and coordinate with your BW team if you are to use this method.  You must also remember to "delete" the assigned transport to "close" it in Transport Connection.
    What I recommend is to go to Transport Connection via RSA1, object types, then query elements.  Collect the queries you wish to modify and create a new transport for them.  Next, make your query changes.  Make sure to exit all BW sessions (if you're on BW3.5) after you're done changing your query.  Then recollect the query in transport connection to pick up the new changes you made (assign it to the original transport).

  • Bex Query Variable error in Webi and Crystal for Enterprise

    Hi,
    We just upgrade to BOBJ 4.1 SP2 and BW7.4 SP5
    I am creating a webi report based on a BEx query. There is Variable on Period/Fiscal Year from BEX side(Mandatory prompt) when I try to create a Webi or Cyrstal for Enterprise report the below error pops up. Other Bex queries work correctly. Can it be the values in the variable the following values exist when execute from Bex i.e. 001.2012; Period 2013
    Is the SAP Note : 1611185 relevant for 4.1 SP2
    Error:
    com.businessobjects.sdk.core.server.CommunicationException$UnexpectedServerException: Termination message sent
    ABEND DBMAN (257): SQL Error: INTERNAL_ERROR
      MSGV1: INTERNAL_ERROR
    Is this True for BOBj4.1 SP2?
    http://scn.sap.com/thread/3362312
    Selection range variables are not fully supported in Crystal Reports for Enterprise.
    Message was edited by: Tienie Nothnagel

    Henry Banks wrote:
    > I know what you mean.  In BEx, it's automatic: the default values are pre-selected at runtime, based on user authorizations
    >
    > In WebI, user needs to do a 3-click workflow to select the authorized values from the prompt dialog. This can be broken down into 3 phases:
    >
    > (a) initialize prompt u2013 empty pane.
    >  (b) refresh list of values,
    >  (c) select response values.
    Thanks Henry! I was looking for this confirmation that it is a limitation of Webi and I'm not missing something.
    Henry Banks wrote:
    > ---> make this BEx variable u2018mandatoryu2019 u2013 this will trigger an automatic refresh mechanism on the list of values, and show it to the user.  This will eliminate steps (a) & (b).
    >
    It is not possible to set Authorization variables as mandatory. They are set to "optional" and cannot be changed (BEx limitation).
    Henry Banks wrote:
    > Unfortunately, BEx and WebI are not like-for-like replacement tools. Not all u2018normalu2019 BW features integrate natively into BObj.
    > So this will also have to be an excercise in positioning a new product to your onboarding users.  (i.e.  just click the button)
    > Regards,
    > H
    I understand that. Thanks for your suggestion.

  • Prompt in BeX query getting error

    Hi All,
    I am getting below error when I am creating prompt in BeX query. It working fime if I am using this query in Olap Analysis but in Webi I am getting below error. I am using BO 4.0
    The DSL Service returned an error: java.lang.UnsupportedOperationException
         at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.selection.SingleMember.getSingleMember(SingleMember.java:321)
         at com.businessobjects.mds.olap.protocol.bics.internal.BICSQueryViewWrapper.cacheVariables(BICSQueryViewWrapper.java:418)
         at com.businessobjects.mds.olap.protocol.bics.internal.BICSQueryViewWrapper.<init>(BICSQueryViewWrapper.java:124)
         at com.businessobjects.mds.olap.protocol.bics.internal.BICSClientImpl.getCube(BICSClientImpl.java:1098)
         at com.businessobjects.mds.olap.protocol.bics.internal.BICSClientImpl.getCube(BICSClientImpl.java:1067)
         at com.businessobjects.dsl.services.workspace.impl.QueryViewAnalyzer.getQueryCube(QueryViewAnalyzer.java:309)
         at com.businessobjects.dsl.services.workspace.impl.QueryViewAnalyzer.createOlapUniverse(QueryViewAnalyzer.java:281)
         at com.businessobjects.dsl.services.workspace.impl.QueryV
    Please help me out to solve this issue.

    Hi,
    1) Check product availability matrix (PAM) if everything is on supported version.
    2) Upgrade to some latest patch of 4.0
    If this does not help then I would recommend, raise it directly to SAP Support team.
    Probably you can open connections to your BW system and engineer can directly check the query you are using.
    Thanks,
    Vivek

  • 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

  • Bex Query report error in cal month /year column

    Hi Experts,
    We have a bex query on virtual provider with only one column in it i.e 'cal year / month'( This virtual provider ahs been created from planning area). I'm having the problem with this column.
    In the excel output of this report the cal year /month is displaying as follows.
    01/0000 02/0000 03/0000 04/0000 05/0000 06/0000 07/0000 08/0000 09/0000 08/2008 09/2008 10/2008 11/2008 12/2008 01/2009 02/2009 03/2009 04/2009 05/2009 03/2010 04/2010 05/2010 06/2010 07/2010 08/2010 09/2010 10/2010 11/2010 12/2010 01/2011 02/2011 03/2011 04/2011 05/2011 06/2011 07/2011 08/2011 09/2011 10/2011 11/2011 12/2011 01/2012 02/2012 03/2012 04/2012 05/2012 06/2012 07/2012 08/2012
    I'm not getting why the first 9 columns its displaying as 01/0000 02/0000 03/0000 04/0000 05/0000 06/0000 07/0000 08/0000 09/0000 .
    It should display as
    08/2008 09/2008 10/2008 11/2008 12/2008 01/2009 02/2009 03/2009 04/2009 05/2009
    06/2009 07/2009 08/2009 09/2009 10/2009 11/2009 12/2009 01/2010 02/2010 03/2010 04/2010 05/2010 06/2010 07/2010 08/2010 09/2010 10/2010 11/2010 12/2010 01/2011 02/2011 03/2011 04/2011 05/2011 06/2011 07/2011 08/2011 09/2011 10/2011 11/2011 12/2011 01/2012 02/2012 03/2012 04/2012 05/2012 06/2012 07/2012 08/2012
    My data source is fetching the correct data including this cal year/ month.
    Thanks in advance for your help.
    Regards,
    Brahma Reddy

    I assume you are running Crystal for enterprise 4.0 SP02 Patch 08 !!
    According to OSS note 1651521 , This issue has been fixed in FP3 which is planned to be released in first quarter of 2012 !!!!!! ouch !!!!! 
    I am facing same issue , Pls let me know if you already solved it.
    Regards,
    Miraj Desai.
    Edited by: Anne Howard on Nov 29, 2011 6:58 AM

  • Query transport error message

    Dear All,
    Having trouble transporting a query.  In the log, it has the following error message:-
    "Start of the after-import method for object type R3TR ELEM (Activation Mode)
    Message no. R7501 "
    Not sure if this is the only problem, because there are several red error messages, but the above message is the first one in the list.
    Regards, Frederick

    Hi Frederick,
    Do the error messages talk about particular elements being missing? Try to collect the query in RSA1 > Transport Connection and see if there are any elements that have $TMP data package...correct this and try to put into a fresh request and transport again.
    Hope this helps...

  • Query transport error

    Hi All,
    While transporting query......i.e frm AWB.......transport connector........select objects and when i select required query and transferring i am getting following error
    Object '0FIN_REP_SIMPL_1_EHP3' (AREA) of type 'InfoArea' is not available in version 'A'.
    Please help me on this.
    Regards

    Hi,
    I think u r collected query all objects( in collection mode u r used before after )so it is collectd the all objects on depending this query,
    so at the time of collections u collect the Query elements alone not all objects
    collect it freshly and do the once again transport.
    Thanks & Regrdsa
    sathish

  • Business Explorer (BEX) Query open Error

    Hi
    When opening  BEX(Business Explorer) Queries from Excel  ,  it asks for System to choose.
    But business doesn't want to see this option. It should go directly to open query selection for the system it has logged in.
    Say , it has logged in BIQ  , it should go to open the queries selction for BIQ without asking to login to BIQ as user has already logged in BIQ.
    In some other users desktop , when they open Queries from Excel it directly goes to open query selection without prompting for System selection
    We are using  SAP GUI 7.20  patch 4 ,  BEX 3.5 patch 3.
    We also have BEX 7.20 but we will not use it
    We tried to with applying all latest patches but we still get the same error.
    We perfomred a Excel test provided by SAP , that shows gree.
    Business wants to use SAP GUI 7.20 patch 4 and BEX 3.5 patch 3.
    Can any one help on this ?
    Note:  please don't recommed to apply latest patch to  GUI or BEX  or apply patch to System component. . Thats not the solution as the current version works in some other desktops.
    Please let me know if you want to understand more in this scenario.
    Thanks
    Rabi Kumar

    Dear Das,
    In that case you need to call the RRMX transaction from your BW system and  if SSO works , then it leads you directly
    to the Open save dialog.
    For SSO , I would suggest you to please implement the below note:
    Note 1498947 :    RRMX: Logon mechanism for 720 GUI.
    Regards,
    Arvind

  • SAP query transport error - need help

    hello,
      The system is throwing the following error when importing the query from development to QA client.
    We already have the query imported the first time without errors. This is happening with subsequent transports if there is a change or any modification to the query.
    Below is the error log from SAP regarding the failed transport :
    R3TRAQQUFI was repaired in this system
    Message no. TW104
    Diagnosis
    Object R3TRAQQUFI is in repair status. Therefore, it cannot be imported.
    System Response
    The object is not imported.
    Procedure
    If you still want to import the object, release the relevant repair and repeat the import.
    Please help
    Thanks in advance.

    Hi
    Here I am sending the step by step procedure for the SAP Query. Hope this helps you, if so please issue points.
    1. Go to SQ02 .
    Select Environment -> Query Areas
    Select Standard Area (Client specific) as show below
    2. Select Environment -> Transports
    Select Import radio button
    Check Overwriting allowed (only with import/upload/copy)
    Remove Check for Test Run
    Select Transport InfoSets and queries radio button
    Fill Infoset and Query with corresponding names
    Fill Import option with transport request number.
    3.  Click on Execute button
    With this it will be done.
    Thanks for your patience

  • Bex Query runtime error '457'

    Hi,
    whenver iam trying to restrict a Fisical year/period time characterstic in query designer iam getting a runtime error with the message "Query run time error'457' This key is already asssociated with an element of this collection".
    Does any one know what might be the reason and how to resolve this issue.
    Thanks,
    Vaka.

    Hi,
    Check SAP Note - 517232
    hope it helps
    regards
    Vikash

  • BEx Query : System error in program CL_RSR_LFMM and form GET_CHANM-01

    Hi Guru's,
    I have a query built over an Infoset (with 3 ODS's and 2 master data Objects)and when I am trying to run the query by selecting Currency Conversion in the Amount key figures I am getting BRAIN 299 System error in program CL_RSR_LFMM and form GET_CHANM-01 Error. If I run without Currency Conversion setting It runs ok.
    Any Advice will be appreciated

    Solved on my own

  • ERROR while excecuting BEx query

    Hi Friends,
    I executed a Bex query and error is displayed Page not Found while connecting.I am using a Remote desktop.
    Can you please let me know how can i correct the error.
    Appreciate your help
    Thanks
    Sahasra

    Hi Sahasra,
    Can you provide more details about your issue. At the same time you can check the following points.
    1. When you are executing the query, does it ask for your SAP user ID and password.
    2. You can check the link on your webpage, whether its referring to the correct query. Query name will be there on URL.
    3. There could be a connection issue, check with you basis team.
    Thanks,
    Sachin

  • Transport Error For Bex Query  to BW Production

    Dear Experts,
    We are facing an issue during transport of a Bex report.
    The RC 16 error has taken place.  After I did google;  I found this as below, but not the exact steps to solve this:
    Return code (16) indicates import is cancelled.
    Ex: RC 16 error
    1. Import cancelled due to system down while importing.
    2. Import cancelled due to user expires whileimporting
    3. Import cancelled due to insufficient roles.
    Would you please suggest me how to encounter this error, solve the error and successfully transport the Bex Query?
    Please help.
    Regards, Aparajit

    Hi all,
    The issue is resolved with Re transport.
    The Query is in production now.
    Thank you very miuch for your guidance  Rama,
    Ganesh  and   Nikhil 
    Regards- Aparajit

  • Can't modify a Bex query, it is tied to a released transport

    Hello BW expert,
    I could not change a existing Bex query. It is always tied to a released transport.
    I have tested I can create a new BEx query and transport it to QA without errors.
    The issue is when I opened an existing query, it has a error.
    Bex transport request xxxxx is not available or not suitable.
    double click the errors, below is the details.
    No request has been set up as the standard transport request for BEx objects.
    The (set up) request 'DB2K901272' (for the package '' ) has already been released.
    The (set up) request 'DB2K901272' (for the package '' ) is not of the type 'transportable change request'.
    I have released transport 901272  before opening the query, I don’t know why this query is still tied to it.
    I tried to create a new BEx transport (DB2K901277) and opened the query again, but an error is still there.
    Third, I tried to collect all query elements for the query in the transport connection, and  put them in a standard transport, then I opened the query, but it is still tied to the same released transport.
    I never see an error like this before. Is there something we could change in the setting so the query is always in changeable mode?
    Thanks in advance!
    Jun

    Hello Vinod,
    I tried, still have the same issue. 
    I collect the query by query elment, select all the elements and the query in the transport connection, then click the the BEx transport. I see a Bex transport created, but no elements are included in the transport, it is a empty transport request. could this be the issue?
    Thank you very much!
    Jun

Maybe you are looking for