on 01-13-2016 2:52 PM
In our current BEx Analyzer setup we have some RRI jumps configured in RSBBS to ECC transactions. In the settings of BEx Analyzer we make sure the ''Log on and activate SAP GUI connection" flag is set, so that the transaction is started through the SAP Logon (and not via a web interface if this flag is NOT set).
We're ramping up the roll-out of AO2.1, but i find no such flag in the AO client, and as expected the RRI jump triggers the web page version of the ECC transaction, while we still would like to start the SAP Logon view
Anybody know any solution for this?
I had long discussion about this feature with SAP some years ago, but they didn't agree that SAP GUI is better for many users.
In our project I made a simple workaround. It doesn't work as RRI in general, but helps to move to ERP transaction from excel.
I created simple button on ribbon
and added VBA macro that run sap shortcut with parameters:
shortcut = Path + " -system=" + target + " -client=" + client + " -user=" + user + " -language=RU -reuse=1 -command=""ZBW_RRI_ME23N document=" + order + """ -max"
dummy = Shell(shortcut, vbNormalFocus)
Path is hardcoded:
Private Function GetPath() As String
Dim Path As String
Path = "C:\Program Files (x86)\SAP\FrontEnd\SAPgui\sapshcut.exe"
If File_Exists(Path) = True Then
GetPath = Path
Exit Function
End If
Path = "C:\Program Files\SAP\FrontEnd\SAPgui\sapshcut.exe"
If File_Exists(Path) = True Then
GetPath = Path
Exit Function
End If
End Function
System and client is also hardcoded depending on BW source system:
source = Application.Run("SAPGetSourceInfo", DP, "System")
Case "***"
target = "S1"
client = "100"
Case "***"
target = "S1"
client = "100"
Case "***"
target = "S2"
client = "100"
End Select
Unfortunately file type of examples is not allowed. Please send me or write your email and I'll send you example workbook.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dmitry Kryuchkov wrote:
I had long discussion about this feature with SAP some years ago, but they didn't agree that SAP GUI is better for many users.
This would be funny if it wasn't so sad ...
I faced too many of these answers over the last year. Yet another example where we loose functionality because SAP thinks we don't need it.
Anyway, thank you for taking the time to reply with this workaround!
I won't go down this path since adding a custom button to the ribbon with custom coding sounds a little too intrusive (what happens when you upgrade the A4O client? I assume you have to reimplement this?)
I didn't check this workbook in AAO version > 1.4 , but I think it will work successfully.
I used standard AAO mechanism of ribbon expanding. Yerserday I analyzed user guide of 2.x AAO and didn't see any significant difference of used functionality.
Even if it is required to reimplement imho it won't be too hard.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.