To control the Web Dynpro for ABAP runtime or the Web Dynpro for ABAP application, you can use the following URL query string parameters in a request URL.
You simply extend the relevant URL in the browser:
<schema>://<host>.<domain>.<extension>:<port>/sap/bc/webdynpro/<namespace>/<application name>?<parameter name>=<parameter value>

http://us7211.wdf.sap.corp:50021/sap/bc/webdynpro/sap/othello?sap-wd-renderMode=raw
The parameter names are not case sensitive, nor are the parameter values (exception: sap-exiturl, if it is pointed to a case-sensitive server). You can combine several parameters in one URL.
More Information:
URL of a Web Dynpro Application
Calling a Web Dynpro Application Using Parameters
The URL parameters for Web Dynpro all begin with sap-wd-. This reserves the sap-wd- prefix for SAP. The table below contains a list of URL parameters and values that are relevant for Web Dynpro for ABAP.
WDA URL Parameters
Parameter |
Value |
Description |
sap-wd-client |
ssrClient (default value) xmlClient (automatically inserted by the smart client) |
Key used to select a special client We recommend not entering anything here, so that the default value ssrClient is used. |
sap-wd-configId |
<ID of the configuration> |
Configuration
ID |
sap-wd-deltaRendering |
ON | OFF |
Delta rendering mode. See also: WDDELTARENDERING application parameter. |
sap-wd-inlinecss |
X | |
See WDINLINECSS |
sap-wd-lightspeed |
X | |
See WDLIGHTSPEED With X, the new rendering is switched on; for values other than X, the classic rendering is used. |
sap-ls-useanimation |
X | |
See WDUSEANIMATION |
sap-wd-ssrconsole |
true | |
Web Dynpro console display.
More
information:
|
sap-wd-displaySplashscreen |
X | |
Displays
the initial screen when a Web Dynpro ABAP application is started. |
SAP also provides the following general URL parameters for all browser-based SAP front-end technologies.

These general URL parameters all begin with sap-. The sap- prefix is reserved for SAP, just like sap-wd and sap-ls.
SAP URL Parameters
Parameter |
Value |
Description |
sap-accessibility |
X | |
Accessibility |
sap-rtl |
X | |
Right-to-left support |
sap-language |
<two character language code> |
Language See below and Configuration Settings |
sap-client |
<three character abbreviation for client> |
Client The sap-client parameter is determined as follows, whereby the first applicable method is used: … 1. Using the sap-client URL parameter 2. Using the standard client in the system logon configuration (transaction SICF) 3. Using the standard client in the system (you can find the requirement for the profile parameter login/system_client in the transaction RZ11, profile maintenance takes place using the transaction RZ10) More
information:
|
sap-cssurl |
<URL> |
URL for using cascading style sheets Pay
attention to the settings for the
|
sap-user |
<user name> |
User ID used for user mapping |
sap-explanation |
X | |
Help mode for an application. More information: Explanation |
sap-config-mode |
X | config |
Configuration mode This parameter is set automatically if the application is running in the portal in the preview mode, or is running from the Web Dynpro explorer in the Development Workbench from the menu option Web Dynpro Application ® Test ® Execute in Administration Mode. This parameter is always evaluated if personalization is called. More information: Personalization Authorization Checks sap-config-mode=config is available for the Configuration of the ALV Display. For more information, see Saving Configuration Data Records. |
sap-ep-version |
<release>.<service pack>.<YYYYMMDDHHMM> |
Portal version This parameter is resolved by the portal manager. It is used to integrate a Web Dynpro application into the SAP NetWeaver, or to determine the portal version. See also Portal Integration. |
sap-theme |
|
See WDTHEMEROOT |
You can also set application parameters in a Web Dynpro application in the Web Dynpro explorer.
This is done on the Parameters tab page in a Web Dynpro application. You can either define your own parameters or select one of the predefined parameters:
●
WDACCESSIBILITY
This parameter is used to activate support for accesibility.
This parameter can be activated in all of the placed named below. OR logic is used (the parameter can be activated in one place). This parameter is normally either defined on a user-specific basis or passed to the URL for test purposes.
Name of the user parameter: ACCESSIBILITY_MODE
Name of the URL parameter sap-accessibility
●
WDCONFIGURATIONID
(configuration name. More information: Application
Configuration)
Passes the ID of the application configuration. Typically, this ID is specified either in the application (various applications are defined for the use of various application configurations) or is defined from the portal as a parameter in the iView.
Name of the URL parameter sap-wd-configid
●
WDDELTARENDERING
View-based Delta
Rendering.
For many applications, it has proven sensible to only send changed views to the client. However, this increases the effort for detecting changes and increase test effort since the application must be completely tested with delta rendering active. Typically, this parameter is set in the application. However, it sometimes makes sense to set the URL parameter for test purposes. If the context changes are to be traced (in WD_TRACE_TOOL, you have to set this parameter.
This application parameter can have the following values:
○ OFF (default value)
Deactivates view-based delta rendering.
○ ON
Activates view-based delta rendering.
As an alternative to this application parameter, you can use the sap‑wd‑deltaRendering URL parameter for view-based delta rendering. This parameter always overrides the application parameter.
●
WDDISABLEUSERPERSONALIZATION
Suppresses the personalization options for the end user. More information: Personalization
This parameter can be used to prevent users from making changes to the UI. The parameter is usually set in the application, in the application configuration, or globally. It is not intended to be used as a URL parameter.
●
WDDISPLAYSPLASHSCREEN
Displays the initial screen when a Web Dynpro ABAP application is
started.

Note that this parameter is deprecated if the WDLIGHTSPEED parameter is active; in such cases it is not evaluated.
●
WDFORCEEXTERNALSTYLESHEET
The Web Dynpro framework automatically compares the versions of the portal and
Web Dynpro for ABAP style sheets. If the Web Dynpro for ABAP has a newer
version, the WDA style sheet is used. This avoids unattractive rendering and
JavaScript errors. Bear in mind that any customer branding will be lost. You
can deactivate this behavior again using the WDFORCEEXTERNALSTYLESHEET
application parameter.
See also SAP Notes 1033496 and 1073498.
●
WDHIDEMOREFIELDHELPASDEFAULT
The display of the extended help is deactivated by default. For selected
individual fields you can reactivate the F1 help; see also Property
Explanationapurl_link_0001_0001_0001.
● WDINLINECSS
This parameter is deactivated by default.
Name of the URL parameter sap-wd-inlinecss
● WDLIGHTSPEED
Activates the new rendering technologie (activated by default in EhP1).
The new rendering technology can be activated and deactivated per client, per application or in the URL. A distinction is made between the parameter being there with an empty value (classical rendering is used) and the parameter not being there (the default value is used).
Name of the URL parameter sap-wd-lightspeed
●
WDPROTECTEDAPPLICATION
Makes using
Web Applications
Without Domain Relaxing secure.
It specifies that the application should run with the SSL (HTTPS) protocol and that no scripting between the portal and the application is allowed.
Note that when you set this parameter, the portal integration no longer functions without any restrictions. Portal eventing does not work anymore. Session handling is also affected (navigating away from iView or closing the browser), as is the work protection mode.
Note also that the BIApplicationFrame UI element does not work properly if you use this parameter.
●
WDSHAREDREPOSITORY
Specifies that the metadata belonging to an application is loaded into the
shared memory. This can lead to memory performance problems.
When using this parameter, make sure that the shared memory is large enough.
●
WDTABLENAVIGATION
Determines the scrolling mode for Tables.
There are the following options:
○
No
specification
Default value, navigation using paginators
○
PAGINATOR
Navigation using paginators
○
SCROLLBAR
Navigation using scroll bars
●
WDTHEMEROOT
Specifies the style sheet for the application without portal integration.
The following style sheets are available:
○ sap_chrome
○ sap_hcb
○ sap_highcont
○ sap_standard
○ sap_tradeshow
○ sap_tradeshow_plus
● WDUSEANIMATION
If the WDLIGHTSPEED parameter is active, this parameter – which is active by default – renders show and hide effects for popups, for example. You can deactivate this parameter for performance reasons.
Name of the user parameter: WDUSEANIMATION
You can also set these parameters (or even one of them) globally for all Web Dynpro for ABAP applications. To do this, execute the WD_GLOBAL_SETTING Web Dynpro for ABAP application, select change mode, and enter the required value of the parameter for all applications.
You can set the parameters described above in the following places:
4. In the Web Dynpro application (in transaction SE80 in the Web Dynpro Explorer for the application on the Parameters tab page).
5. In the application configuration (CONFIGURE_APPLICATION Web Dynpro application, Parameters tab page).
6. Globally for all applications and a specific client (GLOBAL_SETTING Web Dynpro application).
7. For the user and all applications (user parameters – only possible for some parameters).
8. For the current call (as a URL parameter – in this case, the parameter names are not case-sensitive).
The setting options are evaluated in the order below:
9. In the parameters determined by the URL
10. For the standard parameters defined for the Web Dynpro application
The logon language is determined or proposed from the sources listed below: These sources are evaluated in the order below whereby the first in the list is the decisive source.
...
1. sap-language URL parameter (see above)
2. Default language in the setting for the system logon
3. Web browser languages (Accept-Language)
4. Default language of the SAP system

The language from the user account in the SAP system is not evaluated.
The relevant language must be installed in your system.
More Information: