on 11-12-2018 1:21 PM
Hello all,
When starting a classical transaction from an NWBC Fiori Launchpad session, an URL is generated in which the dispatcher port is cut short to ":32" (the suffix of the instance number is missing). The subsequent call of the SAPgui fails with "Partner <Hostname_FQDN>:32 not reached". When analyzing a verbose NWBC trace, I can see this line:
Try to find connection for the following URL: https://<Hostname_FQDN>:<HTTPS_Port>/sap/bc/gui/sap/its/webgui;~service=32?%7etransaction=VA01&%7enosplash=1&sap-client=<CLIENT>&sap-language=EN&sap-user=<USER>
When calling the same transaction from a browser (Chrome), the requested transaction is started without issues.
Where can I influence the URL generated, or how can I make sure the right URL is constructed?
Hi Wilbert,
the WebGUI-URL with all its parameters is needed to start a native GUI-Transaction.
Please check target host and instance number:
Configuration Using RFC Destinations,
Parameters evaluated at runtime:
Regards,
Sandra
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
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.