SAP OSS Notes

2020315 SAP OSS Note - BEx Analyzer: System Connection established via RRMX does no








SAP OSS Note 2020315 version 0004 contains details of a know issue related to BEx Analyzer: System Connection established via RRMX does no . This includes any associated symptoms and instructions on how to fix it, see below for full details. Also check out the comments section to view/add related contributions, questions or screen shots, based on real life experience of this oss note and problem.

...For more information about the SAP support system known as OSS please check out the SAP OSS NOTES SECTION, whih includes how to download & implement them onto your SAP system using transaction code SNOTE.

Note 2020315 Details:





When does this problem occur



You are using transaction RRMX on your BW server to launch BEx Analyzer.


Although you have used SNC to logon the BW Server, BEx Analyz

er is started and the connection to your BW server is established using


an RFC reentrance ticket but without using SNC which makes the

 connection unencrypted. You have the option to disable the ticket


creation and force the usage of SNC but you do not want to use SNC

for authentication but only for the encryption. You want to use the


option 'SNC without Single Sign-On' provided by the SAP Logon conn

ection entry properties.


If active, BEx Analyzer by default always uses the RFC reentrance ticket
for establishing the system connection.



Cause of the problem and Pre-requisites



Program error




Solution instructions



The correction from this note contains frontend and backend part.


Please follow the instructions below to implement both.
After implementing this note, when using the t-code RRMX on the BW
server to launch BEx Analyzer, the following is valid regarding the

 established connection:


,,If the existing logon session is using SNC, the system checks if SNC
was used for authentication or not.

,,- If SNC was used for authentication, the connection from BEx Analyzer


will be established using the SNC data only (SNC with Single S

ign-On)


,,- If SNC was NOT used for authentication, the connection from BEx
Analyzer will be established using SNC for encryption and an RFC re

entrance ticket for authentication (SNC without Single Sign-On).


,,If the existing logon session is NOT using SNC,
,,- The connection from BEx Analyzer will be established using an RFC
reentrance ticket without passing SNC data although an SNC user a

ssignment might exist on the BW server.


NOTE: Please note that if you want to make an SNC logon using
user/password without Single Sign-On via a connection entry defined with

 SNC turned on in SAP Logon, you must implement the notes 1617641 and


1701870 first.



Frontend Part: Implement the below mentioned Frontend Patch.


,,SAP NetWeaver 7.0 BW Front End for GUI 730


,,Import Front-End Patch (FEP) 700,, (or higher) for SAP NetWeaver 7.x
BW Front End (bi720sp7,,_700,,-10004472.exe) into your system. The

FEP will be available as soon as SAP Note 1885324 ,,with the short text


"SAPBWNews NW 7.x BW Add-On Frontend Patch 700,, - GUI 7.30", wh

ich describes this FEP in more detail, is released for customers.




,,This SAP Note might already be available before the FEP is released.
,,You can check the planned availability dates in the attached SAP Note
1085218,,.

Backend Part: Implement the below mentioned support package or this note


via transaction code SNOTE.

,,SAP NetWeaver BW 7.00




,,Import Support Package 34 for SAP NetWeaver BW 7.00 (SAPKW70034) into
your BW system. The Support Package will be available as soon a

s SAP Note 1930843,, with the short text "SAPBWNews NW BW 7.0 ABAP


SP34", which describes this Support Package in more detail, is relea

sed for customers.


,,SAP NetWeaver BW 7.01 (SAP NW BW7.0 EHP 1)


,,Import Support Package 17 for SAP NetWeaver BW 7.01 (SAPKW70117) into
your BW system. The Support Package will be available as soon a

s SAP Note 2013377 ,,with the short text "SAPBINews NW7.01 BW ABAP


SP17", which describes this Support Package in more detail, is relea

sed for customers.


,,SAP NetWeaver BW 7.02 (SAP NW BW7.0 EHP 2)


,,Import Support Package 17 for SAP NetWeaver BW 7.02 (SAPKW70217) into
your BW system. The Support Package will be available as soon a

s SAP Note 2017437 ,,with the short text "Preliminary Version SAPBWNews


NW BW 7.02 ABAP SP17", which describes this Support Package in

more detail, is released for customers.


,,SAP NetWeaver BW 7.11


,,Import Support Package 14 for SAP NetWeaver BW 7.11 (SAPKW71114) into
your BW system. The Support Package will be available as soon a

s SAP Note 1940531 ,,with the short text "Preliminary Version SAPBINews


NW7.11 BW ABAP SP14", which describes this Support Package in m

ore detail, is released for customers.


,,SAP NetWeaver BW 7.30


,,Import Support Package 13 for SAP NetWeaver BW 7.30 (SAPKW73013) into
your BW system. The Support Package will be available as soon a

s SAP Note 2021667 ,,with the short text "SAPBWNews NW7.30 BW ABAP


SP13", which describes this Support Package in more detail, is relea

sed for customers.


,,SAP NetWeaver BW 7.31 (SAP NW BW 7.3 EnhP 1)


,,Import Support Package 14 for SAP NetWeaver BW 7.31 (SAPKW73114) into
your BW system. The Support Package will be available as soon a

s SAP Note 2030844 ,,with the short text "Preliminary Version SAPBWNews


NW BW 7.31/7.03 ABAP SP14", which describes this Support Packag

e in more detail, is released for customers.


,,SAP NetWeaver BW 7.40


,,Import Support Package 9 for SAP NetWeaver BW 7.40 (SAPKW74009) into
your BW system. The Support Package will be available as soon as

 SAP Note 2030800 ,,with the short text "Preliminary Version SAPBWNews


NW BW 7.4 ABAP SP09", which describes this Support Package in mo

re detail, is released for customers.






In urgent cases you can use the correction instructions.


Before you use the correction instructions, make sure that you check SAP
Note 1668882 for transaction SNOTE.



This SAP Note might already be available before the Support Package is


released. In this case, however, the short text still contains

the term "preliminary version".






Description of problem



BEx Analyzer, SNC, RRMX, RFC Logon Ticket, RRMXP, encryption


Solution instructions


Please import the corrections attached to this OSS note into your SAP system using SNOTE.

You can also view the full details of this OSS note and download it to your SAP system ready for implementation using transaction code SNOTE. Once it has been downloaded you can read the full details, check out any installation instructions including manual changes and see if there are any pre-requisites.

You can also check if a new version of note 2020315 has been released as well as see if the note is valid for your current SAP system landscape.

Check if SAP OSS note 2020315 has already been downloaded and is valid


To check if this note has already been download, what status it has and if it is valid for your system first execute t-code SNOTE and click on the SAP Note Browser icon
Icon used to execute SAP Note Browser report within SNOTE

From here you can just enter the note number 2020315 and press execute. If the note already exists it's details will be displayed. See here for full step by step instructions on how to check if an SAP note has been downloaded and is valid for your system.



If note 2020315 does not exist on your system you will receive the message "Unable to find SAP Note that meets specified criteria"
Icon used to execute SAP Note Browser report within SNOTE

If this is the case you will need to download the note to you SAP system also using transaction SNOTE. For further details see Download note using SNOTE. Even if it does exist you may still want to check if you have downloaded the latest version of the note.

Alternatively you can find full details of this note on the SAP service market place(SNumber / Service market place login will be required)