Skip to end of metadata
Go to start of metadata

Frequently Asked Questions - General Technical Aspects

Common questions regarding the behavior of the design time or runtime in certain situations
When I click to create a roundtrip to the server and quickly click several times in succession, the system creates yet another request, which triggers a short dump. If I click slowly or only once, no short dump occurs.

There are displaced artefacts inside of the browser window. How can I solve this?

How do I Find the Calling WDA Component?

What Can I Do If I Get JavaScript Errors?

How Can I Test My Accessibility Texts?


When I click to create a roundtrip to the server and quickly click several times in succession, the system creates yet another request, which triggers a short dump. If I click slowly or only once, no short dump occurs?

Before the system sends the page to the server, it activates a click protection.  However, it takes several milliseconds to activate this protection.  During this period the problem described above may occur. We cannot provide a solution for this problem.  The browser environment requires a certain period to activate the click protection.  The protection is executed on the client at the beginning of the submit handling.
back to top

There are displaced artefacts inside of the browser window. How can I solve this?

Very likely, this displacement happens due to a very deep nesting of HTML entities within the browser window. Browsers cannot handle it correctly, if the hierarchy becomes too deep. As an example try to omit nesting multiple TabStrips into each other.  It's better to use other means that don't add to the hierarchy.  Popins in Tables that have complex content are also sensitive to that.
back to top

How do I Find the Calling WDA Component?

I want to ascertain from the cryptic name of type /1BCWDY/2A5JNGDP2YQFUSHKTBT2==CP the real component that is calling.
To find out the name of the calling component:

  1. Enter the cryptic name in SE38 and choose Display.
  2. Choose Implementation and double-click on the component controller include.
  3. In the top component you can see the name.
    The method name that you use to find out the component name at runtime is called:
    CL_WDY_WB_NAMING_SERVICE=>GET_COMPONENT_BY_CLASSNAME

back to top

What Can I Do If I Get JavaScript Errors?

When I call a Web Dynpro ABAP application either stand-alone or in the portal, a JavaScript error is displayed. JavaScript errors are displayed in a popup containing the relevant error message, or as a small yellow triangle in the status bar.

JavaScript Versions
A JavaScript version older than the one on the back end is installed on your computer. An obsolete file can easily be used since the JavaScript files are stored in the ICM server cache as well as in your browser cache. To prevent this happening:

  • Delete the files in your browser cache
  • In your browser go to Tools -> Internet Options. Under Temporary Internet Files choose Delete Files and Delete Cookies.
  • Delete the files in the ICM Server Cache

In transaction SMICM choose Goto -> HTTP Server Cache -> Invalidate -> Global in System.

Monitoring and Administration of the ICM Server Cache

Portal Stylesheets
It may happen that you have integrated a Web Dynpro ABAP application of a newer release into an older portal. Normally the WDA uses the portal stylesheets. Due to the different versions the Web Dynpro ABAP application may not look its best, and some functions may not be available. JavaScript errors may occur here too.

To prevent this you should avoid using portal stylesheets in the iView of the Web Dynpro ABAP application. Deactivate Supply Portal Stylesheet. This means that the Web Dynpro ABAP will only use the internal standard WDA stylesheets.

Brandings defined in the portal will no longer be available to the WDA, and the WDA will use the standard theme.
back to top

How Can I Test My Accessibility Texts?

To test my application in accessibility mode I need to use a screen reader or wait for the tooltip. But if I just want to test my accessibility texts quickly and without much ado, there's a much easier way:

I set the url parameter sap-accessibility-debug=X. In addition, I set the url parameter sap-accessibility=X.
Then the accessibility text of the current focussed element will be displayed with the prefix ACC: in a box beneath the application in the lower part of the browser window.
Example:
back to top