Skip to end of metadata
Go to start of metadata
With transaction RRMX you can launch BExAnalyzer from the SAPGUI. Executing a workbook from 'SAP Easy Access Menu' or RRMXP uses the same architecture. This page includes all known SAP GUI 730 / 740 issues related to RRMX with BW release 7.0 onwards.

As per note 1652771 BW 3.5 Add-On (BEx 3x frontend) is not delivered with SAP GUI 730.
That means:

  • With SAP GUI 730 you cannot create/change/execute 3x workbooks. 
  • With SAP GUI 730 you cannot use BEx Analyzer 3x for RRMX.
  • With SAP GUI 730 on Precalculation Server you cannot precalculate 3x workbooks.
  • According note 147519 SAPGUI 710 & 720 is not supported. Thus installing SAPGUI 730 or 740 is MANDATORY.
  • This page does not include the issues solved with current frontend patch mentioned in Current BI ADDON.
  • This page only mentioned code/parameter changes required in the BW ABAP server.

A - How Tx RRMX works

  • The Tx RRMX generates a shortcut file which contains all necessary information (including the ticket for authorization which is valid for only 2 minutes) for establishing the connection between BEx Analyzer and backend system.  
  • The generated file has the extension *.7xbex.
  • The file is downloaded temporary.
    • To identify the folder run modul GET_TEMP_DIRECTORY from class CL_GUI_FRONTEND_SERVICES, add folder '\tmp' at the end of the string.
    • Example: C:\Users\...\AppData\Local\SAP\SAP GUI\tmp
  • Once the BEx Analyzer is started and the connection is established, the shortcut file is deleted automatically.

1 - BEx Analyzer version

For using SAP GUI 730 / 740 you should ONLY use the BEx Analyzer 7x version. There are three ways to set the BEx Anlayzer version for Tx RRMX which is described below. If you have a different setting then mentioned below, you make observe a error or Not opening of analyzer. One of the reason is that the setting used leads to open a 3x Analyzer or 3x workbook which is not supported/installed with SAPGUI 730 / 740.

Global: The default version can be set in Tx RRMX_CUST:

Client specific: In BEx Analyzer 7x you can override the global version in the "Global Settings".
Make sure that flag is not set for "Launch SAP BW 3x BEx Analyzer from SAP GUI":

User sepcific: You can maintain the parmater RRMX_VERSION in the user profile.
Logon to backend and navigate: System > User Pofile > Own Data > TAB Parameters.
Enter the Parameter RRMX_VERSION = 70.

2 - Prerequisite

3 - Minimum requirements for RRMX to work.

  • The SAP AG certificate should be valid/OK on the PC as described in note 1742365. Regarding this please also review wikipage Certificates in BEx Analyzer and Workbooks.
  • 1599266 Version: 4, BExAnalyzer: RRMX/RRMXP launches incorrect BExAnalyzer Vers.
  • To establish the connection after the BexAnalyzer is launched, automatic logon to BW server is done with a help of a logon-ticket. This logon-ticket is generated based on Single-Sign-on(SSO) ticket OR Secured-Network-connection(SNC) ticket. When SSO is disabled then SNC is used, thus in this case SNC must be enabled. In note 1498947 you find information about setting of logon tickets login/create_sso2_ticket and login/accept_sso2_ticket. ATLEAST ONE of the following requirement must be fulfilled as described in note 1498947.
    • Is SSO for SAP-LOGON ticket working?
      • To check: Execute Tx RZ11:
        • Profil Parameter: login/accept_sso2_ticket -> Display -> Current Value = 1
        • Profil Parameter: login/create_sso2_ticket -> Display -> Current Value = 1 OR 2
        • Profil Parameter: login/ticket_expiration_time -> Please increase this value in case you get an error something like "The system received an expired SSO ticket".
        • Profil Parameter: rdisp/max_wprun_time -> Please increase this value in case you get an error something like "Time limit exceeded". Recommended is 3600 seconds.
      • If you observe any issue in this check, please consult SAP Notes in area of BC-SEC-LGN for assistance.
    • Is SNC active?
      • To check: Execute Transaction SM51. In menu select 'GOTO-> SNC Status'.
      • All application server should have an active 'SNC status'
      • If you observe any issue in this check, please consult SAP Notes in area of BC-SEC-LGN for assistance.
  • When transaction RRMX is executed from BI system, the ABAP backend prepares a file RRMX.3xbex or RRMX.7xbex with all information necessary (including the logon-ticket as mentioned above) for establishing the connection with BExAnalyzer. This file has extension .3xbex or .7xbex depending on the version of BExAnalyzer that should be started. The file is downloaded temporarily into the folder "C:\Documents and Settings\...\SapWorkDir". The user should have the WRITE authorization for this folder SapWorkDir. The path of folder SapWorkDir is determined via method cl_gui_frontend_services=>get_sapgui_workdir. As explained in note 1442303 point 2.2, please confirm it is working properly.
    Should the Method cl_gui_frontend_services=>get_sapgui_workdir not return the desired folder, please open a OSS ticket on component BC-FES-GUI for assistance. Please also have a look at 1562985
  • If using SAP_BASIS 7.00, ensure that the SAP_BASIS 7.00 Support Package 27 (or higher) is applied and ensure that the 7.00 kernel has patch 129 or higher.
  • User needs S_GUI authorization (Authority Object: 'S_GUI', ID : 'ACTVT', FIELD : '61').

4 - Specific Issues

  • When there are multiple application servers that are load balanced, load balancer selects an available server at any point of time. So based on the active server, RRMX has to make connection. Implement note 1610061 and maintain the parameter ANA_RRMXP_USE_IP as mentioned in the note.
  • If the client PC and the BW server are in different DNS domains ensure that the instance profile parameter SAPLOCALHOSTFULL is specified with the full qualified host name of the server as mentioned in note 1471630
  • When launching BExAnalyzer through transaction RRMX, if RSADMIN parameter REUSE_XL_INSTANCE is not set to DISABLE and an Excel instance is already running then a VBA popup appears asking to save changes you made to 'Object'. Please consider note 1443825
  • In case of a scenario that includes access from external clients to which the server names are unknown, the parameter ANA_RRMXP_HOST (described in note 1291645) wouldn’t be enough for establishing the connection. In that case please also implement the note 1548170, additionally specifying the parameter ANA_RRMXP_GUIHOST as described in that note.
  • In case the secnario includes access from external clients to which the server names are unknown remove the parameter ANA_RRMXP_HOST from the RSADMIN table if exists as mentioned in note 1548170
  • One of the following parameters can be used to control usage of BexAnalyzer. If you are using these parameters please consider the note 1473879 to understand the effect.
    • VER_MIN_ANA
    • VER_MIN_ANA_3X
    • VER_MIN_ANA_7X
    • VER_MIN_ANA_SAPBEX0

5 - Specific Issues with RRMXP

  • When there are multiple application servers that are load balanced, load balancer selects an available server at any point of time. Based on the active server, RRMX has to make connection. Please apply the correction of the note 1721965
  • Please apply the correction of the note 1499983
  • Please check the setting required for the automatic connection/logon 1646433
  • There is 2 method to use the iview (BSP/Transaction RRMXP) to launch the workbook, The 2 methos are described in the note 1646028
  • If SAPGUI window is not hidden after BExAnalyzer is started via RRMXP or Portal and has to be closed manually, then consider note 1499568
  • The connection transfer to the BExAnalyzer fails because the host can only be accessed using the fully qualified hostname. please consider note 1291645 and maintain parameter ANA_RRMXP_HOST
  • When launching BExAnalyzer via transaction RRMXP the started Excel process does not exit when Analyzer is closed. It is still visible in the task manager. In addition an error message that macros can contain viruses may appear when closing BExAnalyzer. Please consider note 1278220 (SAPKW70021)

 

6 - Limitation

This new architecture has some limitations:

  • Reusing of Excel instances is not supported. Every call will launch its own Excel instance.
  • *.bex file is no longer used. Therefore creating shortcut from BEx Browser won't work rather give out a memory error.
  • Connecting to BW server via Microsoft Applocale and then calling TA:RRMX will no longer work with GUI 720. In general it is not supported.
  • There may be further limitations with older patches, thus always check/confirm with the current patches which mentioned at Current BI ADDON

Which BexAnalyzer should be launched? See note 970002

 

Your Analysis

Please read this first

  • Applying the above mentioned recommendations solved most RRMX issues in the past.
  • Once you have applied the recommendations and in case issue remains please answer ALL following questions.
  • You can copy/paste this question part in your OSS incident. Do not copy the detail paragraphs into OSS incident (-document).
01. Which FEP is installed? Please attach the installation check file. - Note 1229206
    Attached file name:
02. Which BW support package are you using?
    SAPKW_______
03. Is the SAP AG certificate valid/OK?
    YES/NO
04. Is Addin BExAnalyzer.xla loaded when started via
    START->PROGRAM->Business Explorer->Analyzer?
    YES/NO
05. Do you see yellow *help button*?
    YES/NO
06. Can you logon to desired BW system with user and password when
    analyzer is started via START->PROGRAM->Business Explorer->Analyzer?
    YES/NO
07. Are note 1599266 (Version: 4) and 1807477 implemented?
    YES/NO
08. Do you see *both* the profile parameter
    'login/accept_sso2_ticket=1' *AND*
    'login/create_sso2_ticket=1 OR 2' ?
    YES/NO
09. Is SNC active on ALL Application server?
    Check with Transaction SM51, menu->GOTO->SNC status.
    YES/NO
10. What is the value of SapWorkDir?
    C:\......
11. What is the kernel patch?
    Number:
12. Does the user have *S_GUI* authorization?
    YES/NO
13. Does any point mentioned in *Specific Issues* relavant in your case?
    YES/NO (If YES which one)
If the issue is with iview or RRMXP
14. Is note 1499983 applied?
    YES/NO
15. Which method are are using in Iview (Note 1646028)?
    BSP/Transaction RRMXP
16. Is the property of the iview defined as mentioned in the note 1646028?
    Please attach a screenshot of the property.
17. Start Tx RRMXP in backend. Opens the WB in BEx Analyzer correctly?
    YES/NO

 

Link to this page: http://wiki.sdn.sap.com/wiki/x/1IDzEg