WD ABAP application launched from UWL doesn’t work as expected
Hello there everyone
We’ve seen some incidents reported on UWL component area where there was a problem involving a backend Task Type which was integrated within the UWL, and the launching of these tasks from the UWL was not being performed correctly.
Instead of the expected WD ABAP application, an odd ABAP screen got displayed together with an error message stating that “The request cannot be started from the Business Workplace”.
Following are two Task Types which are examples of tasks where this issue has already been reported:
This issue is described in the following KBA:
1773641 – ESS LEA: Web Dynpro ABAP based Leave Request use in UWL
This KBA summarizes about this problem, which comprehends missing configuration at ABAP side on SWFVISU transaction and also a missing functionality from UWL side to pull the information related to this configuration parameter once it is correctly configured at SWFVISU.
Following are all the relevant notes which together comprehend the solution for the problem:
1933611 – SWFVISU “CONFIGURATION” visualisation parameter for Web Dynpro ABAP iView not propagated to UWL configuration
1723628 – Webdynpro ABAP launcher produces error
1717586 – New visualization parameter CONFIGURATION for UWL
Thanks for your attention, and I wish you all a Happy 2014!