No authorization error in Bex report

Hi
    When i open an workbook i get the selection screen and when i select values and execute i get an message" warning you don’t have sufficient authorization"
When i click close button on the message the work book opens up but with out output (values) instead i get you don’t have sufficient authorization. I checked in for authorizations in Su01 and su53 every thing looks fine.
NOte: I was able to open this report couple of days back
Can someone help me out in this issue?
Thanks a lot
Sheetal

hi,
who's assigned the role to you. he is having the authorization rights to change these and all. please check out with that. if you having the rights to modify means go to your role change the authorization. otherwise contact your role head.
if helpful provide points
regards
harikrishna N

Similar Messages

  • Authorization Errors from BEx queries

    We are developing Crystal reports on top of BEx queries. We are working on BO XI 3.1 FP2.8, Crystal Reports FP2.8 and SAP Integration Kit FP2.8 and SAP BW is BI 7.0 Suppport pack 5.0. How can we display the Authorization errors that are returned on BEx queries on the Crystal reports.
    If i run the Crystal reports and if it comes back empty, there can be 2 reasons one no Data and second no proper authorizations. We want to display a mesage to users to tell them the report is empty either becaus of no data or Authorization error.
    Thanks,
    Venkat

    Thank you Ingo. Is there any work around where we can get the return code to a temporary KeyFigure and use that.
    Regards,
    Venkat

  • Run Time Errors in BEx Report Designer?....asking for Portal Setup??

    In BEx Report Designer, I keep getting short dumps and timeouts when trying to design flashy reports.
    I keep getting 2 errors when I time out:
    1. 'Query (view) definition cannot be retrieved from Portal.
    Please try again or check query and Portal Setup!
    Time limit exceeded.
    2. xxx Error when reading Query (via BICS)
    Please check query and Portal setup!
    Time limit exceeded.
    We are running ECC 6.0, BI2004s, and SEM 6.0.  All in Sandbox/Dev environment.
    We are NOT running EP. 
    I am aware that we have some memory issues, and we're adding 4Gb more on Thursday....can the solution be that simple, or are these errors telling me we need Portals installed?  I was under the impression that Portals were NOT required for 2004s, so long as you did not use WAD etc.
    Any thoughts??

    You would need to install portals(EP) for the report designer to work. When you design your flashy report in designer and try it launch it... it would try to connect to EP to publish it. It bombs when it doesnt find the portal.
    On a personal note: Report designer have a long way to go when you think the output would be something like crystal .. NO not yet ... But SAP just got started ... I think they would be there pretty soon. And they promise many enhancements as of SP 13.. so lets all wait.

  • No authorization error in BW report

    Hi ,
    when I am trying to run a report in BW , its giving an error like,
    "you dont have authorization to read  the object"
    how can i solve this problem ? please help.
    Regards,
    Ryan.

    Hi Srinivas,
    thanks a lot for your reply.
    can you tell me whether there is any settings to be done in CRM  system regarding the authorization in BW ?
    Waiting for your reply.
    Regards,
    Ryan.

  • Error in BEX report

    HI BW guru's.
    Iam executing a zreport in BEX, which is showing up all the vales that are there in the cube, except one master data attribute. when I check in master data contents it is having the values in it. But in the BEX all the values for the column shows upo as "ERROR".
    can any one explain me what went wrong and what needs to be done in order to display the values of the master data in the query.
    Thanks in Advance,
    Dilse...
    Harish

    HI Pals,
      Thanks Siggi and Dirk, I ahve checked both the options which you ahve suggested. But still the could not overcome.
    As to our earlier mails I have checked that data is available for 0base_uom.
    I shall explain my problem once again so that you have a clear cut idea.
    When I am executing a material master data query, the quantity of valuated stock ( 0VALSTCKQTY ) field in the report is showing as an error.
    This field 0VALSTCKQTY is a key figure attribute to ZMAT_ACC ( Master data  infoobject ). All the values of 0VALSTCKQTY are populated in BW but I am not sure why these values are not displaying in the report and all the values in the report shows an error. Currently I am investigating on this why its happening. This is very important to proceed further.
    Thanks in advance,
    Dilse...
    Harish

  • Bex reporting issue

    Hi gurus
    I m facing a typical error in Bex Reporting. This report displays the details of consumer address details. The data is successfully browsed from data tgt browser in ODS.while creating the reporting and query it gives me these 3 errors.
    Note: Z_CRDAT is key fig of date type / ZADD_ODS is the ODS .
    1. Error in SQL Statement: SAPSQL_FIELDLIST_SUM_TYPE /BIC/Z_CRDAT
    2. System error in program SAPLRSDRC and form RSDRC / FORM DATA_GET_ODS      
        Message no. BRAIN299                                                  
    Diagnosis                                                            
    This internal error is a targeted termination since the program has an incorrect status.                                                     
    Procedure                                                                 
    Analyse the situation and inform SAP.                                 
    3. System error: RSDRC / FORM DATA_GET_ODS ERROR IN RSDRO_READ_ODS_DATA ZADD_ODS 99       
    Message no. DBMAN100                                            
    Diagnosis                                                                               
    A system error with the following parameters has occurred in the data
    Manager:                                                                               
    Parameter 1 = &v1&                                                                               
    Parameter 2 = &v2&                                                                               
    Parameter 3 = &v3&                                                                               
    Parameter 4 = &v4&

    hi gurus
    can any body suggest me anything against this error .
    gaurav

  • RFC connection Error While run BEx Report

    Hi All
    I got BI 7.0 and create new user with roles only access: TR: RRMX to see only BEx Reporting... I create basically new customize role and put only one transcation code RRMX and assigned to user...
    When goto BEx designer I got that error
    rfc error received user has no rfc authorization for function group syst.
    I am not sure what kind of authrouzation user need to only view BEx Reporting...
    But when I put SAP_ALL in that profile same user, thats works fine, but I don't want to give SAP_ALL to user...
    2nd question same look like BEx Analyzer the side bar when I click open nothing happend and it writedown like German language..
    Please advised

    Hi Alls
    I am Angeline again, I resolved that problem and want to shair with you guys....
    1.     Tr: PFCG and click on Maintain roles
    2.     Role Name: Z_RUN_QUERIES
    3.     Click on Authorization Tab Saved Entry
    4.     In Edit mode Select the template: S_RS_RREPU and adopt reference (Business Content)
    5.     Expand u2018Business Explorer u2013 Componentsu2019
    6.     Selected: u201CType of a reporting component Calculated key figure, query restricted
    7.     key figure u2013 template structure and click on Edit
    8.     Un-Check REP Query
    9.     Generate the Profile
    10.     Create Transport number
    11.     click on user TAB and define user name in it
    12.     click User compare and complete compare and saved the entry
    13.     TR: SU01 in User click on Roles and define Z_RUN_QUERIES and profile
    Thanks

  • Error while opening BEx reports

    Hello Gurus,
    I got a problem with BEx reports. When I tried to open the BI reports in BEx Analyzer, its giving the following error.
    "Characteristic 0TCKAKYFNM does not exist. Check authorizations"
    I got this problem only with the Production server. All the rpeorts worked fine in DEV and QA servers.
    When checked, there is no infoobject named "0TCKAKYFNM" exists in the system.
    Also we have checked with Basis people for any authorization object with the name 0TCKAKYFNM but of no use.
    We are using BI7.0
    Any suggestions will be of great use.
    Rgds
    Kumar

    Hi Kumar,
    Check the 0TCAKYFNM objcet properties - i.e Display the Char and goto Tab - Business Explorer.
    If the Authorization relevant filed is checked then by default your object can be used to provide data level authorizations.
    If this object is included in your infoprovider then you need to provide the values or '*' in the analysis authorization object.
    If you r not using any authhorizations, then plz uncheck the 'authorization relevant' checkbox in the object properties.
    Regards,
    Geeta

  • BEx report designer error

    Hi,
    When am trying open Query in BEx report designer it is getting below error plz help me to solve this issue.
    error while loading query metadata check the wuery and portal settings
    RSBOLAP  017 Java communication error : RFC destination NOT_CONFIGURD Does not exist
    Thanks,
    Medha.

    Hi Medha
    this is due to two reaso
    1 For the system IP there should be open a port
    2 May be its a authorization problem check this object is added or not S_RFC
    Shashi..

  • Error Message in BEx Report Designer 7.0

    I am getting the following error message when I try to add a data provider (Query) to BEx Report Designer:
    RSBOLAP 017 Java Communication Error: RFC destination NOT_CONFIGURED does not exist
    Would anyone be able to provide feedback on what to do?

    Hi Selva Kumar,
    Its a Basis Issue , report to a Basis asministrator about the  configuration of Report Designer .
    For info refer this link:
    https://forums.sdn.sap.com/click.jspa?searchID=21289661&messageID=6734602
    Cheers,
    Tanish

  • We are facing error while executing Bex report.

    Hi Gurus:
    We are facing error while executing Bex report.
    Messge :                                                                          
    u201CQuery 0: Runtime error program state check for conversation 05284411 / CP  with parallel processing via RFC
    Message no. DBMAN428u201D
    The query is based upon Multiprovider (based upon 2 basic cubes).
    Both cubes are partitioned by   info object 0CALMONTH, (valid range - 01.2005 - 012.2010).
    Those cubes are not containing any non-cumulative key figures and Service package level for  SAP NetWeaver BI 7.0 is  u2018SAPKW70012u2019.
    I have checked those cubes in RSRV and carry out following steps:
    "All Elementary Tests -> Transaction Data" and execute the repair "Consistency of the Time Dimension for an Info Cube"
    I have found system inconsistency like u201CRecord with the DIMID 2 contains non-fitting time characteristics u201C
    Detail ERROR:
    Record with the DIMID 2 contains non-fitting time characteristics
    Message no. RSCV053Diagnosis
    The data record of the time dimension table with the described DIMID contains values for time characteristics that do not fit together.
    I have found the u2018 Note 1130450 - Query displays error DBMAN 284; RSRV: Time dimension checku2019  for this but still not sure this will work or not .
    I tested this in dev server , didn't feel useful.
    Could you please let us know what to correct this error.
    Anwser will be rewared.
    Regards,

    >
    Surendra Pande wrote:
    > Anwser will be rewared.
    > Regards,
    Go read the RULES of these forums.

  • Bex Report Designer: Error while loading metadata

    hi experts,
    I am working with BI7 Bex Report Designer and we are using SP9. when i tried to load the Query in Report Designer its giving below error.
    Error while loading metadata.
    Check the Query and portal settings.(but the query is working fine in Analyzer).
    and its giving message class RSBOLAP, message number 018 and Description is java system error: incoming call is not authorized.
    when i double click the error its giving below error details.
    Diagnosis
    An error occurred in the BI components on the SAP J2EE Engine.
    System Response
    Procedure
    Contact your system administrator to have the error analyzed in detail.
    Procedure for System Administration
    Start the Visual Administrator, log on to the SAP J2EE Engine and choose "<J2EE_SID>" ->"Server" -> "Services" -> "Log Viewer".
    The file "defaultTrace.trc" includes detailed information about the error that occurred. In Windows, you can find this file in the Log Viewer under "Cluster <computer name>" -> "Server <server number>" -> "<drive>:\usr\sap\<SID>\JC<INSTANCE>\j2ee\cluster\server<NUMBER>\log". ". In Unix, the file is located under "/usr/sap/<SID>/JC<INSTANCE>/j2ee/cluster/server<NUMBER>/log".
    If the file does not include enough detail about the error, you can increase the log level to obtain more information. To do this, choose "<J2EE_SID>" -> "Server" -> "Services" -> "Log Configurator". On the "Locations" tab page, choose "com" -> "sap" -> "ip" -> "bi" -> "webapplications". Using the selection list on the right side of the screen, you can increase the log level, whereby "DEBUG" represents the log level with the most information. You can save your settings by choosing the "Save" icon. The change to the log level is active immediately. Once you have successfully analyzed the error, you should set the log level back to its default value using the appropriate pushbutton; continuous writing to the log file negatively affects the overall performance of the system.
    could you plz suggest me how to rectify the problem.
    regards
    vadlamudi

    Hi vadlamudi
    The error message RSBOLAP 018 means, that the ABAP stack can't communicate with the Java Stack.
    1) Please ensure, that the user, used for the Report Designer, is valid in the Portal too. Depending on the user management setup this means that there either needs to be the same user or an assigned user in the Portal.
    2) In case the user is valid, it means a basic misconfiguration according to note 937697. In this case please run the Support Desk Tool and ensure, that all checks are green. Please ensure, that the latest version of the Support Desk Tool is used.
    Regards,
    Janine

  • BI 7.01 BEx report/workbokTime_Out Errors

    Hi,
    Our BEx reports/workbooks are failing with time_out error's. Below are the time_out error details: BEx workbooks  are executed through VB Script.
    Some days they run fine and some days they time_out.
    The program "CL_RSDRH_HIER_CACHE===========CP" has exceeded the maximum
      permitted runtime without
    interruption and has therefore been terminated.
    Programs with long runtime should generally be started as background
    jobs. If this is not possible, you can increase the system profile
    parameter "rdisp/max_wprun_time".
    Depending on the cause of the error, you may have to take one of the
    following measures:
    - Endless loop: Correct program;
    - Dataset resulting from database access is too large:
       Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table
       (for example);
    - Database has unsuitable index: Check index generation.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "TIME_OUT" " "
    "CL_RSDRH_HIER_CACHE===========CP" or "CL_RSDRH_HIER_CACHE===========CM00D"
    "ADD_MEM"
    Other time_out error's as below:
    The program "SAPLRSDRC_SPLIT" has exceeded the maximum permitted runtime
      without
    interruption and has therefore been terminated.
    Termination occurred in the ABAP program "SAPLRSDRC_SPLIT" - in "SELAGGR_GET2".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 1101
    of the (Include) program "LRSDRC_SPLITF01".
    The program "CL_RSDRH_HIER_CACHE===========CP" has exceeded the maximum
      permitted runtime without
    interruption and has therefore been terminated.
    Termination occurred in the ABAP program "CL_RSDRH_HIER_CACHE===========CP" -
    in "CHECK".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 80
    of the (Include) program "CL_RSDRH_HIER_CACHE===========CM001".
    The program "SAPLRSDRC_SPLIT" has exceeded the maximum permitted runtime
      without
    interruption and has therefore been terminated.
    Termination occurred in the ABAP program "SAPLRSDRC_SPLIT" - in
      "SELDR_TO_AGGROBJ".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 214
    of the (Include) program "LRSDRC_SPLITF01".
    The program "SAPLSENA" has exceeded the maximum permitted runtime without
    interruption and has therefore been terminated.
    Termination occurred in the ABAP program "SAPLSENA" - in "FLUSH_PACKAGE".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 229
    of the (Include) program "LSENAF01".
    The parameter "rdisp/max_wprun_time" is set at 7200 Seconds.
    Pl. suggest how to resolve.

    Hello,
    I think this is quite easy.
    Execute the report SAP_DROP_TMP_TABLES (via SE38 transaction) and the issue should be solved.
    For more details, see notes 698280 and 1139396.
    Let me know if persist.
    Best Regards,
    Edward John

  • BI 7.01 BEx report/workbok Time_Out Errors

    Hi,
    Our BEx reports/workbooks are failing with time_out error's. Below are the time_out error details: BEx workbooks are executed through VB Script.
    Some days they run fine and some days they time_out.
    The program "CL_RSDRH_HIER_CACHE===========CP" has exceeded the maximum
    permitted runtime without
    interruption and has therefore been terminated.
    Programs with long runtime should generally be started as background
    jobs. If this is not possible, you can increase the system profile
    parameter "rdisp/max_wprun_time".
    Depending on the cause of the error, you may have to take one of the
    following measures:
    - Endless loop: Correct program;
    - Dataset resulting from database access is too large:
    Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table
    (for example);
    - Database has unsuitable index: Check index generation.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "TIME_OUT" " "
    "CL_RSDRH_HIER_CACHE===========CP" or "CL_RSDRH_HIER_CACHE===========CM00D"
    "ADD_MEM"
    Other time_out error's as below:
    1) The program "SAPLRSDRC_SPLIT" has exceeded the maximum permitted runtime
    without
    interruption and has therefore been terminated.
    Termination occurred in the ABAP program "SAPLRSDRC_SPLIT" - in "SELAGGR_GET2".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 1101
    of the (Include) program "LRSDRC_SPLITF01".
    2) The program "CL_RSDRH_HIER_CACHE===========CP" has exceeded the maximum
    permitted runtime without
    interruption and has therefore been terminated.
    Termination occurred in the ABAP program "CL_RSDRH_HIER_CACHE===========CP" -
    in "CHECK".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 80
    of the (Include) program "CL_RSDRH_HIER_CACHE===========CM001".
    3) The program "SAPLRSDRC_SPLIT" has exceeded the maximum permitted runtime
    without
    interruption and has therefore been terminated.
    Termination occurred in the ABAP program "SAPLRSDRC_SPLIT" - in
    "SELDR_TO_AGGROBJ".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 214
    of the (Include) program "LRSDRC_SPLITF01".
    4) The program "SAPLSENA" has exceeded the maximum permitted runtime without
    interruption and has therefore been terminated.
    Termination occurred in the ABAP program "SAPLSENA" - in "FLUSH_PACKAGE".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 229
    of the (Include) program "LSENAF01".
    Recently we have increased the parameter "rdisp/max_wprun_time" from 5400 to  7200 Seconds.
    Pl. advise.

    Hello,
    I think this is quite easy.
    Execute the report SAP_DROP_TMP_TABLES (via SE38 transaction) and the issue should be solved.
    For more details, see notes 698280 and 1139396.
    Let me know if persist.
    Best Regards,
    Edward John

  • Error Transporting FI ODS with Bex Reporting On

    Hello,
    We are getting error
    "Value Xxxxx for characteristic 0INV_DOC_NO is invalid".
    "Value Xxxxx for characteristic 0REF_DOC_NO  is invalid".
    "Value Xxxxx for characteristic 0REF_KEY1 is invalid".
    "Value Xxxxx for characteristic 0REF_KEY2 is invalid".
    "Value Xxxxx for characteristic 0TXTLG is invalid".
    "Value Xx#xx# for characteristic zsmthg is invalid".
    in transport log while activation fo ODS, we have only checked Bex reporting  flag to report on ODS and
    are trying to move the request to production .
    This ODS has approximately 14,000,0000 and upper level cube is working fine for reports.
    Any Ideas for this error message ?
    Thanks
    Ooops

    Hi,
    when activating your ODS for reporting, the system will generate master data SIDs for all IObjs of your ODS.
    In other words, your ODS was prior this setting just a table with fields not usable in reporting thus not checked when loaded.
    Now the system is checking each value of the IObj and verify that it complies with the IObj rules (lower case not allowed, special characters allowed in Tx RSKC, and so on...).
    If the values are fine, the system will create this master data and corresponding SIDs for all IObjs if they aren't created yet)...
    All these checks are performed because you now want to report on this ODS, therefore the system will link your ODS table fields an their corresponding IObjs...
    I suggest to copy your ODS to another; enable the reporting flag on the copy and start loading some data from the original to the copy and escalate the several issue you will face one by one.
    Hope this helps
    Olivier.

Maybe you are looking for