7/7/25, 7:29 AM

UI WebGUI and Internet Transaction

Server
Generated on: 2025-07-07 07:29:27 GMT+0000

Support Content | 1.0

Public

Original content: https://help.sap.com/docs/SUPPORT_CONTENT/uiwits?locale=en-US&state=PRODUCTION&version=1.0

Warning

This document has been generated from SAP Help Portal and is an incomplete version of the official SAP product documentation.
The information included in custom documentation may not reflect the arrangement of topics in SAP Help Portal, and may be
missing important aspects and/or correlations to other topics. For this reason, it is not for production use.

For more information, please visit https://help.sap.com/docs/disclaimer.

This is custom documentation. For more information, please visit SAP Help Portal. 1
 7/7/25, 7:29 AM

ITSmobile

What's ITSmobile This page is the landing page of:

ITSmobile

ITSmobile is a SAP technology to connect mobile devices to a SAP system in order to

run applications based on the widely used Dynpro programming model.
Articles, Guidelines...
ITSmobile AJAX Communication
ITSmobile replaces the Web SAPConsole which will be phased out with SAP Netweaver Getting to know ITSmobile by
7.01. It is available for SAP systems based on SAP Netweaver 2004, SAP Netweaver 7.0, Checking out the ITSMobile
Services
SAP Netweaver 7.10 and higher. ITSmobile is an integrated part of SAP Netweaver and Mobile Devices and Browser
based on ITS. Prerequisites to run ITSmobile
Features and Improvements
Service Parameters and Settings for
ITSmobile
ITS Performance
ITSmobile Visual Editor
Generate and Modify Templates
Do you want to run a dynpro-based application on a mobile device? And even make
manual adjustments to fulfill your own special requirements? No problem - using the
ITSmobile it only takes you three steps:

1. You first need to create an 'Internet Service' by generating the relevant

templates. This whole procedure takes place in transaction SE80 where
different ITSmobile generation styles are offered. The recommendation is to use
STYLE: MOBILE4. Review the following page which explains the three ITS
Services required to use the different ITSmobile generation styles: Getting to
know ITSmobile by Checking out the Internet Services.
2. Once you have successfully completed the generation of the ITSmobile
templates you then need to create an ICF service. This is the second step by
using transaction SICF. The ICF service that is created here will link your
ITSmobile service using the parameter ~SOURCES . Now you can display your
Internet Service in a browser - on a desktop browser or on a mobile device
browser.

3. It is very important to use the OLD ITS Handler CL_HTTP_EXT_ITS in the SICF
settings. The new Handler CL_HTTP_EXT_ITS_2 should NOT be used.
4. If more functionality is required e.g. F-Keys or you do not like the standard
design, take the third step. Make manual adjustments to the templates in
the transaction SE80, or include a new CSS file with your own design. See also
the sample video in KBA 2242078 - ITSmobile: How to create a sample service
[VIDEO].

Another option for making adjustments to the templates is to the follow the steps on
the ITSmobile Visual Editor WIKI page.

Important

If you make any subsequent changes in SE80 to the templates, CSS files or MIME's -
then the ITSMobile service needs to be republished.

If you have applied ITSmobile related SAP Notes via transaction SNOTE it is important
to regenerate the ITSmobile templates.

Republish the various ITSmobile generation services in SE80 i.e (

ITSGENMOBILE, ITSGENMOBILE4, ITSGENMOBILEXV and ITSGENMOBXML or
run report SIAC_PUBLISH_ALL_INT in transaction SE38 which will publish ALL
the ITS based services)

This is custom documentation. For more information, please visit SAP Help Portal. 2
 7/7/25, 7:29 AM
Then run the report: SIAC_REGENERATE_TEMPLATES in SE38. This will
regenerate the ITSmobile templates.
Finally republish the newly generated ITSmobile service templates. Do this in
SE80 (or run report SIAC_PUBLISH_ALL_INT in SE38 which will publish ALL
the ITS based services)

See also SAP notes

1260901 - ITSmobile test service updated after Generator modifications

2416791 - Regenerating templates for RFUI

Features

Barcode Scanning

ITSmobile supports data input via 1D and 2D barcode scanning.

SAP Note 1311169 - ITSmobile: Barcode scanner AutoEnter has information on the
AutoEnter feature.

Voice Enabling (pick by voice)

ITSmobile supports voice enabling of ABAP/Dynpro based screens using the "Speech"
property to send additional, speech related data, to the frontend/Browser. Together
with the new ITS XV Template generator(ITSGENMOBILEXV), which generates
XHTML+Voice based templates, it is possible to add speech in/output to your
application. Voice enabled browsers, like Opera, will do the rest of the job.

RFID (Radio-frequency identification)

ITSmobile supports ABAP Property RFID which helps you to execute RFID operations
on dynpro based screens using ITSmobile. The RFID property sends additional, RFID
related data to the frontend/Browser. ITSmobile will deliver this data via javascript to
your own device specific implementation for your specific RFID reader.

ITSmobile Information

ITSmobile Documentation (ABAP Platform)

ITSmobile on the SAP help portal for ABAP Platform (Creating Mobile Applications with
ITSmobile)

ITSmobile Notes

Only general ITSmobile notes are listed here; find further related SAP Notes using
search key "ITSmobile" in SAP for Me .

1070064 - Comparison of Web SAP Console with SAP ITSmobile

1037715 - ITSmobile: Supported screen elements
2063269 - Classification of correct investigation area for SAP cases involving
RF devices

ITSmobile FAQs
You have questions regarding ITS? Please check out the frequently asked questions
(FAQ).

This is custom documentation. For more information, please visit SAP Help Portal. 3
 7/7/25, 7:29 AM
ITSmobile Troubleshooting Guide: ITSmobile issues

Forum

Please discuss ITSmobile topics and issues in the SAP Community Forum Internet
Transaction Server (ITS).

Features and Improvements

ITSmobile is a technology with still ongoing development to improve the technology This page is part of:
and to provide new features the customer requires. We suggest to install the latest
ITSmobile
version to ensure not to miss a new feature or a great improvement.

On this page you will find a feature list of the ITSmobile with a short description and thePrerequisitefor the
system requirements. following features:
NOTIFY_BELL_SIGNAL support
ALV Grid support
System messages and express
mails
An ALV Grid control can't be identified by the ITSmobile Generator. Application popups
Messages with sound
RFID Support
It has some limited features as set out in the note 1037715 - ITSmobile: Supported
Voice Enabling
screen elements Mobile System Logon
Default, Base Service of generator
Include functionality
NOTIFY_BELL_SIGNAL support
New Generator
ITSmobile Visual Editor
ITSmobile supports NOTIFY_BELL_SIGNAL. With the introduction of this feature,
ITSmobile is compatible with SAPConsole. BGSOUND tag is used to generate the
sound.

New Generator

To improve the performance ITSmobile offers a new generator. Templates created with
the new generating style "Mobile Devices (Without HTML Tables)" does not use the
slow table structure to arrange the screen elements.

RFID Support

Unfortunately, there is no standard RFID interface that enables useres to connect all
the handhelds RFID devices made by different manufacturers. To allow as many
different device types as possible to be used, the technical software connection of the
devices in ITSmobile is based on JavaScript. It is therefore possible to connect any
device whose RFID functions can be programmed using JavaScript. In many cases, the
device manufacturer provides an ActiveX control or similar object that can be
addressed in the browser using JavaScript.

Applications also have widely varying requirements of an RFID interface (reading,

writing, deleting RFID tags...). To fullfill these requirements, ITSmobile provides the
extensible ABAP property RFID. By defining your own RFID data in this property, you
can create your own RFID commands.

The RFID support provided by ITSmobile simply involves the provision of an RFID
pushbutton. This RFID pushbutton is linked to the RFID data and fields and is therefore
similar to a "trigger" on the RFID device. Pressing the RFID pushbutton or "pulling the
trigger" initiate the same function.

Message with sound

This is custom documentation. For more information, please visit SAP Help Portal. 4
 7/7/25, 7:29 AM
With the new ITSmobile parameter ~ITSMOBILEMSGSOUND setting to "1" a sound file
(.wav file) will be played when a message arrives at the browser. The sound file is
specified using the HTML tag "bgsound" in the body. Please make sure, that your
browser supports this html tag otherwise the sound file is ignored. ITSmobile
generates different sound files for the different message types to allow the user to
identify the importance of the message on the played sound.

Additionally we changed the message icon. We now have a separate icon for each
message type to visualize the different message types too. Check the new testcase
MESSAGE within the sample service ITSMOBILE01 for an example.

For ITSmobile developers we store the message data within the ITS context to allow
programmers their own visualization of messages. New ITS context fields are:
~MESSAGETYPE[1] content e.g. S, I, W, E
S = success message, I = informantion, W = warning, E = error
~MESSAGENUMBER[1] contains SAP message number, e.g. 013
~MESSAGEID[1] contains SAP message id, e.g. SITS_MOBILE
~MESSAGELINE[1] contains the message text

Application popups (~POPUPS)

With the ITS default settings, application popups are not visualized. The ITS
automatically submits a <ENTER> against the backend to commit the popup. For the
most mobile applications this default behavior is fine. Anyway, if your application is
using popups e.g. the commonly used logoff popup ( "Logoff ?, with YES and NO
button" ) you have to set the ITS parameter (gui setting) ~popups to "1" to get the
popups visualized. Please keep in mind, that your service must have the appropriate
template for each popup.

With the improvement pack 2, ITS already delivers a template for the commonly used
logoff page ( dynpro: SAPLSPO1, number: 100). If you specify the default service
itsmobile within your template search path (e.g. ~sources myservice,itsmobile ) you do
not need to create an own template, the default template from service itsmobile is
used.

If you miss other templates for commonly used dynpros, please create a message at
SAP, component BC-FES-ITS.
There is no way to display specific popups only, please carefully check if you really
need this feature.

System messages and express mails (~SHOW_SYSTEM_MODAL)

With the ITS default settings, system messages and express mails are not visualized.
(Please see transaction SM02 and SO01 how to create system messages and express
mails.) The ITS automatically submits a <ENTER> against the backend to commit this
messages/mails. That means even important messages and mails like system
availability information or express mails generated from the update task are not
delivered to the mobile users. Depending on your own organization it may be necessary
to visualize this messages to mobile users e.g. to stop comissioning when the update
task stops working due some problem.

If you set the ITS parameter ~SHOW_SYSTEM_MODAL to "1" system messages and
express mails are delivered to the ITSmobile users. As like the ~popups switch you
need a template for each message/mail dynpro within your service.

This is custom documentation. For more information, please visit SAP Help Portal. 5
 7/7/25, 7:29 AM
ITSmobile Improvement Update 2 already contains a default template for the system
messages and express mails (Dynpro SAPMSSY0, number 120). To use this default
template, please add the itsmobile service to your template search path (~sources).
This default template at least delivers a notice containing the message title to the
ITSmobile users. The visualization of the messages and mails is limited since the
message/mail dynpro is a list dynpro. If you would like to create your own template,
please have a look at the default template implementation in service itsmobile to see
how list elements are available / accessible through the ITS context.

Voice Enabling

Generating XHtml+Voice to support speech input/output.

This package provides the additional generator ITSGENMOBILEXV, style "Mobile

Geräte mit Sprachunterstützung". This generator creates XHTML+Voice templates and
the Java Speech Grammar Format 1.0 (JSGF V1.0). The text necessary for speech
input/output is saved as XML properties in the ABAP Workbench. The properties will be
passed to the ITS during runtime. The speech input/output can be activated by
browsers which are able to support X+V.

The main purpose of speech support is the implementation of PickByVoice application.

The output text is stored in the ABAP/backend to ensure a translation to other
languages.

A detailed documentation is available on the SAP Help Portal.

NEW: ITSGENMOBILE4

Voice support has now been added to ITSGENMOBILE4. Voice support has been added
to the tableless ITSmobile Generator. This generating style is "Mobile Devices (Without
HTML Tables)"

Defauld/Base Service of generator

Easy way to create your own generator

Own template generating programs can now be extended with a default service for
generating program templates. If you want to write an own template generator, it is no
longer required to copy all generation templates in your service. You can copy only the
templates that you would like to change. Technically this is done by the overwriting the
function _GET_FROM_TEMPLATE. This function first checks the own service for
templates. If no template is found the template of the default service will be used.

Function _GET_FROM_TEMPLATE of class CL_ITS_GENERATE_HTML_XV_MOBILE can

be used for an example. This example first searches through service ITSMOBILEGENXV
and than through default service ITSMOBILEGEN for templates.

Include functionality

Until now it was necessary to change the generator or the corresponding template in
order to include a own or modified include file for javascript or css stylesheets. The
latest update provides service parameter to identify the own include files. It is not
necessary to change the generator/templates anymore which makes it easier to
include modifications.

Include service parameter for mobile devices:

This is custom documentation. For more information, please visit SAP Help Portal. 6
 7/7/25, 7:29 AM
~itsmobileCssInclude to replace CSS stylesheets

~itsmobileJsInclude to replace javascript

~itsmobileVoiceInclude to replace speech generating

Example: javascript include ~itsmobileJsInclude = myjavascript is set in the service

settings => during runtime the file myjavascript which is located in my own service will
be used, instead of the default file mobile.js in service ITSMOBILE.

Mobile System Logon

Mobile system logon, own login class can be derived, that avoids waiting periods.

Class CL_MOBILE_SYSTEM_LOGIN used to be a final class, it was necessary to copy

the class for own implementations. With the latest update the class can be derived
which makes own modifications on the login class more comfortable. Example: device
specific meta tags can by set on the login screen by overwriting the method
WRITE_CONTENT_BEGIN_HTML in the derived class.

DYNPRO_COMPRESSION

This feature is only available with style MOBILE4

If you wish to remove lines containing no visible elements that are still visible on the
screen then set ~DYNPRO_COMPRESSION service parameter to the value of "1" in the
GUI Configuration section of the ITSMobile service in transaction SICF.

Application popups
Integrated ITS

SAP Web AS 640: Kernel Patch 220, SAP Basis Support Package: 22

SAP Web AS 700: Kernel Patch 140, SAP Basis Support Package: 15

SAP Web AS 710: Kernel Patch 84, SAP Basis Support Package: 6

Standalone ITS

ITS 6.20 Patchlevel 29, SAP Basis Support Package: 64

Default, Base Service of generator

Integrated ITS

SAP Web AS 640: Kernel Patch 210, SAP Basis Support Package: 22

SAP Web AS 700: Kernel Patch 132, SAP Basis Support Package: 15

SAP Web AS 710: Kernel Patch 81, SAP Basis Support Package: 5

Standalone ITS

ITS 6.20 Patchlevel 28, SAP Basis Support Package: 64

This is custom documentation. For more information, please visit SAP Help Portal. 7
 7/7/25, 7:29 AM

Include functionality
Integrated ITS

SAP Web AS 640: Kernel Patch 210, SAP Basis Support Package: 22

SAP Web AS 700: Kernel Patch 132, SAP Basis Support Package: 15

SAP Web AS 710: Kernel Patch 81, SAP Basis Support Package: 5

Standalone ITS

ITS 6.20 Patchlevel 28, SAP Basis Support Package: 64

Messages with sound

Integrated ITS

SAP Web AS 640: Kernel Patch 220, SAP Basis Support Package: 22

SAP Web AS 700: Kernel Patch 140, SAP Basis Support Package: 15

SAP Web AS 710: Kernel Patch 84, SAP Basis Support Package: 6

Standalone ITS

ITS 6.20 Patchlevel 29, SAP Basis Support Package: 64

Mobile System Logon

Integrated ITS

SAP Web AS 640: Kernel Patch 210, SAP Basis Support Package: 22

SAP Web AS 700: Kernel Patch 132, SAP Basis Support Package: 15

SAP Web AS 710: Kernel Patch 81, SAP Basis Support Package: 5

Standalone ITS

ITS 6.20 Patchlevel 28, SAP Basis Support Package: 64

NOTIFY_BELL_SIGNAL support

Note: 1260592
Integrated ITS

SAP Web AS 640 SAPKB64024

SAP Web AS 700 SAPKB70018
SAP Web AS 701 SAPKB70103
SAP Web AS 710 SAPKB71008

Standalone ITS

620 SAPKB62066

New Generator
This is custom documentation. For more information, please visit SAP Help Portal. 8
 7/7/25, 7:29 AM
Integrated ITS

SAP Web AS 640: Kernel Patch , SAP Basis Support Package: 24 (SAPKB64024)

SAP Web AS 700: Kernel Patch , SAP Basis Support Package: 18 (SAPKB70018)

SAP Web AS 710: Kernel Patch , SAP Basis Support Package: 7 (SAPKB71007)

SAPKB70103
SAPKB71101

Standalone ITS

ITS 6.20 Update not supported

SAPKB46C58
SAPKB62066

RFID Support
Integrated ITS

SAP Web AS 640: Kernel Patch 228, SAP Basis Support Package: 23

SAP Web AS 700: Kernel Patch 155, SAP Basis Support Package: 16

SAP Web AS 710: Kernel Patch 99, SAP Basis Support Package: 6

Standalone ITS

ITS 6.20 Update not supported

System messages and express mails

Integrated ITS

SAP Web AS 640: Kernel Patch 220, SAP Basis Support Package: 22

SAP Web AS 700: Kernel Patch 140, SAP Basis Support Package: 15

SAP Web AS 710: Kernel Patch 84, SAP Basis Support Package: 6

Standalone ITS

ITS 6.20 Patchlevel 29, SAP Basis Support Package: 64

Voice Enabling
Integrated ITS

SAP Web AS 640: Kernel Patch 210, SAP Basis Support Package: 22

SAP Web AS 700: Kernel Patch 132, SAP Basis Support Package: 15

SAP Web AS 710: Kernel Patch 81, SAP Basis Support Package: 5

Standalone ITS

This is custom documentation. For more information, please visit SAP Help Portal. 9
 7/7/25, 7:29 AM
ITS 6.20 Patchlevel 28, SAP Basis Support Package: 64

Voice support for the faster generator: ITSGENMOBILE4. For the generating style "Mobile Devices (Without HTML Tables)"

Required BASIS Support packages

SAP_BASIS 46C SAPKB46C59

SAP_BASIS 620 SAPKB62067
SAP_BASIS 640 SAPKB64025
SAP_BASIS 700 SAPKB70021
SAP_BASIS 701 SAPKB70105
SAP_BASIS 710 SAPKB71009
SAP_BASIS 711 SAPKB71104

See also SAP Note:

#1361067 ITSmobile: voice support in faster generator

One has to republish: ITSGENMOBILE4 in SE80 and re-generate your service templates using the tableless ITSmobile Generator
to have this Voice Support feature if you implement corrections from note #1361067 or if you have upgraded to the above Basis
Suppoprt package.

Getting to know ITSmobile by Checking out the ITSMobile Services

This page is part of:

Internet Services of ITSmobile
ITSmobile

To see which ITSmobile Generators are present in the system, start transaction SM30, view
the table W3GENSTYLES

In your system you can then view the services via SE80

1. Services for Generating ITSMobile Templates

ITSGENMOBILE: For generating style "Mobile Devices (Preserving Layout)"

Comment in Template: STYLE: MOBILE

ITSGENMOBILE4: For generating style "Mobile Devices (Without HTML Tables)"

Comment in Template: STYLE: MOBILE4

ITSGENMOBILEXV: For generating style "Mobile Devices with Voice Input"

Comment in Template: STYLE: MOBILEXV

ITSGENMOBXML: For generating style "Mobile Devices with absolute positioning"

Comment in Template: STYLE: MOBILE5

Here is an example of the comment section of the HTML template for MOBILE5

<!-- Generated Template

NAME: MY_TEMPLATE_NAME

SCREEN: 8000

DATE: 20170612

TIME: 144445

This is custom documentation. For more information, please visit SAP Help Portal. 10
 7/7/25, 7:29 AM
STYLE: MOBILE5

-->

NB: The format for DATE is YYYY / MM / DD

When you generate an HTML template using the ITSMobile Visual Editor template, the style
MOBILEEDIT is set.

See also the SAP Note: 2027612 - Incorrect generation style in HTML template

Comment in Template: STYLE: MOBILEEDIT.

In addition, if you see Comment in Template: STYLE: XML,

this indicates that the generating template was ITSGENMOBXML:

XML was the OLD comment - in newer systems MOBILE5 is the comment in template

this change to the comment section in SE80 for a template is also documented in the note

2027612 - Incorrect generation style in HTML template

Additional information.

Creating your own Generator

See the SAP HELP: Creating a Generation Style

2. Runtime Service

ITSMOBILE

This service contains Mime Objects and HTML Templates which are used by the (Test-)
services during runtime.

The Mime Object folder contains images, script, styles, sounds...

The HTML Templates folder contains templates for controls (e.g. ALV_GRID), includes (e.g.
CUAAREA) and system messages (e.g. SAPMSYST 40).

3. Testservices

Internet Service Generating Style Screens of SAPMIMOB1

Special

ITSMOBILE00 Mobile Devices (Preserving Layout) 100 - 103

ITSMOBILE01 Mobile Devices (Preserving Layout) 500 -

518 Example for Device Inludes

ITSMOBILE02 Mobile Devices with Voice Input 200 - 203

ITSMOBILE03 Mobile Devices (Without HTML Tables) 500 - 518

ITSMOBILE04 Mobile Devices (Without HTML Tables) 200 - 203

This is custom documentation. For more information, please visit SAP Help Portal. 11
 7/7/25, 7:29 AM

ITS Performance

This page is part of:

Performance aspects
1) Performance checklist ITSmobile
SAP system
Application
ICMAN / ITS
Mobile device
2) Known performance issues with mobile devices
Configuration: battery lifetime versus CPU speed/RAM retention
Mobile browsers without cache (obsolate)
Mobile browsers, not supporting table-layout style (slow table
rendering) [only valid for old ITSmobile generator]
3) Conclusion

Performance aspects

This information should help you to analyze performance problems with ITSmobile services. Performance problems are always
difficult to analyze but you should at least be able to verify if the performance gap is related to your sap system, your application,
your network or your mobile device. We will not exactly measure response times and the data traffic of ITSmobile services, neither
will we dive into the performance analysis of the sap system, but instead we will try a couple of simple basic tests to figure out
where the performance comes from and whether it makes sense to invest more time to get a better overall response time.
Please keep in mind, that mobile services are ABAP based. Always call the services you are going to analyze a first time to let the
SAP system compile the ABAP sources and fill the buffers. The ITS also needs this first call to pre-parse the templates and store
them into its template cache. The ICMAN has to read the mimes out of the database into his HTTP-Plugin server cache. All this has
to be done during the first access, so in general the first call of a service is not of interest for performance analysis.

1) Performance checklist

First step is analyzing and understanding the performance problem. That means we have to check the performance of each
involved component. In rare cases, you additionally have to check if the problem is related to a specific SAP server, to a single
location, to a specific application or to distinct screens of an application.

Involved components:

SAP system
Application
ICMAN/ITS
Mobile Device

SAP system

To check the system's performance, start the SAPGUI for Windows and call a couple of SAP basis transactions like SE38, RZ11,
SM50 or SM04 to get an idea of the application servers performance. If the performance of these transactions is already poor it
does not make sense to continue with performance analysis of the mobile services. Use the SAP basic tools to find the reason for
the poor system performance.

Application

ITSmobile Services are ABAP based, that means the mobile transactions can be called with the SAPGUI for Windows. Logon to the
system and call the mobile transactions with the SAPGUI for Windows. You will find the transaction of the mobile service within the
ICF service tree (transaction SICF), in the GUI settings, parameter name ~transaction. Sometimes, if you start this transaction

This is custom documentation. For more information, please visit SAP Help Portal. 12
 7/7/25, 7:29 AM
within the SAPGUI you will get an error message, that the transaction could not be started. Simply terminate the easy access
menu ( enter "/n" in the okcode field until you get the "Start Easy Access Menu" screen.). Now the transaction can be started in the
SAPGUI for Windows.
Input exactly the same data as on your mobile device and you will get an idea of the performance of the transaction. It doesn't
matter if you call the transaction using SAPGUI for Windows or via Browser using HTTP, in both cases the same application code is
running and will need the same execution time to reproduce the same results. If the performance of the transaction is bad, use
ABAP tools to find out the reason. In that case it does not make sense to continue with the analysis of the performance of the
mobile service.

ICMAN / ITS

Next step is to check the response time of the HTML/HTTP related components in the backend. Start your favorite browser on
your desktop PC and call the ping service ( URL: http://<server>:<port>/sap/public/ping?sap-client=000 ) to get an idea how
long the access of an HTTP service in the backend takes. After testing the ping service, start the ITSmobile service "itsmobile00"
(URL: http://<server>:<port>/sap/bc/gui/sap/its/test/mobile/itsmobile00?sap-client=000 ). On your desktop PC you
probably will not experience a big difference between both services, despite the fact that the service "itsmobile00" has to run a
small piece of application coding, the ITS has to convert the data stream to HTML and the browser has to draw the HTLM page. If
possible repeat the test with your desktop PC connected using the same WLAN as your mobile devices, that gives you an idea if
the wireless network has any effect on the response time.

Mobile device

Test on your mobile device:

Do the same test calling service "ping" and calling service "itsmobile00" on your mobile device. If there is a big difference between
the response times on your desktop PC and your mobile device the performance problem is related to the mobile device. The
performance problem is NOT backend related.

2) Known performance issues with mobile devices

If you run the tests described in 1) "Performance checklist" you usually end up with the insight, that as long as no mobile device is
involved the performance is perfect. The ping test from above is the only test case which is pretty fast on mobile devices too. The
reason is, that the transferred data rate is pretty small and there is not much to paint for the browser. If you start the "itsmobile00"
test service on your mobile device you probably already recognize a much longer response time. This longer response time is the
result of the limited CPU power and the poor rendering performance of the browser on many mobile devices. Let us now look
closer to these limitations and discuss how we can get around them to improve the performance on mobile devices.

Configuration: battery lifetime versus CPU speed/RAM retention

On many mobile devices you will find a menu path like "Settings->System->Power->Battery" that leads to a slider where you can
configure the mobile device to increase battery lifetime by decreasing RAM retension/performance.
Check this setting on your mobile device.

Mobile browsers without cache (obsolate)

Nowadays this issue can be ignored; the devices on the market support caching.

The HTTP data stream of ITSmobile services can be divided into mimes and template data. The template data contains application
values and is changing with every application screen. Mime data is very stable, the content of mime files usually changes only
during the developing phase of a service or if you implement bugfixes. If a mobile device has no browser cache, the mime data is
requested and send again and again from the server with every submit even if the content does not change.
You can use the ITS publish service to store the mime data directly on each mobile device and avoid unnecessary network traffic.
To access the local stored mime data you have to set the ITS parameter ~urlmime to the local storage location. That's it. At
runtime the ITS will read the ~urlmime parameter and use its content to generate the mime links in your html templates referring
to the local storage location. The mimes will not longer be sent over the network, the mimes will be read from the local file system
instead. The disadvantage is the administrative overhead. You have to copy the mimes onto every mobile device. If a mime file

This is custom documentation. For more information, please visit SAP Help Portal. 13
 7/7/25, 7:29 AM
changes, you have to get the changed file to every mobile device. By the way, many mobile devices already has software available
which helps you to automate the distribution of files to many single devices.

Mobile browsers, not supporting table-layout style (slow table rendering) [only valid for old ITSmobile
generator]

Some mobile browsers do not support absolute positioning in HTML pages therefore the ITS template generator has to use HTML
tables for the page layout. The table layout is done with a character table spanning the complete screen using the character
positions from the dynpro for the single fields. This produces an HTML layout pretty close to the dynro screens. To help the
browser to render this pages faster the style "table-layout:fixed" is set. Mobile browser which do not support this attribute need
much more time for rendering because they have to calculate each single cell and column size based on the content. Tables are
also used for rendering subscreens, frames and step loops. Having a dynpro screen, containing a subscreen with a step loop on it
leads to HTML pages containing 3 nested tables. The result is a poor rendering performance on browsers not supporting fixed
table layouts.

For the old ITSmobile template generator (which creates templates with HTML tables) the following information applies:
If possible, avoid such constructions on mobile screens. Anyway it's always a good idea to keep mobile screens simple. If you don't
like to change the dynpro layout, you have to manually change the generated template to speed up the rendering. The ITS template
generator can not do this, because of its generic way creating the templates.
If you manually change the generated template, try to replace the <table> with a <div> tag, convert the table lines (<tr></tr>) to
line breaks (<br>) and use the <span> tag for cells (<td>). This could reduce the rendering time to less than 50% of the original,
generated page if nested tables occur on the page. You may optimize the HTLM for a single screen only, or create your own
template generator to optimize all screens for your specific browser. Please keep in mind, optimizing the generated HTML is a
consulting issue. You need detailed HTML knowledge.

For the new ITSmobile template generator (which creates templates with HTML DIVs) the "slow table rendering perfromance
information" is not valid anymore.
However - here it is sometimes required to optimize the screen using an own CSS stylesheet (consulting issue). From consulting
point of view (where performance plays an important role) the recomendation is to use the new DIV HTMLB ITSmobile template
generator. The new generator cannot ensure that all screens look the same as in the SAP Gui but the performance is better
compared to the old ITSmobile generator.

3) Conclusion
The performance of ITSmobile services mainly depends on the used mobile devices. Saving money here has to be paid for effort to
optimize the generated html or to admistrate local mime files on each device to improve the performance.

ITSM - FAQs

Frequently Asked Questions regarding ITSmobile This page is part of:

ITSmobile
General Questions

#Where can I find a documentation for ITSmobile?

#Which screen elements are supported by ITSmobile?
#Where can I find information regarding the latest updates?
#How should an internet service for ITSmobile look like?
#How can I check if my ITSmobile environment is running?
#Does ITSmobile replace Web SAP Console and SAP Console?
#Which devices are supported?
#My generated internet service is not running, what could be wrong?

Answers General Questions

Where can I find a documentation for ITSmobile?

This is custom documentation. For more information, please visit SAP Help Portal. 14
 7/7/25, 7:29 AM
You can find useful information on this ITSmobile Wiki page and a structured documentation on the SAP Help Portal.
back to top

Which screen elements are supported by ITSmobile?

SAP note 1037715 lists all supported screen elements and their attributes. In addition you can run testservice itsmobile01; this
internet service displays all screen elements. Very complex screen elements, e.g. tablecontrole are not supported by ITSmobile
back to top

Where can I find information regarding the latest updates?

You find information regarding the latest improvement and support packages on the News and Improvements page.

How should an internet service for ITSmobile look like?

When you create an internet service using generation style Mobile Device, you are getting templates of an internet service
optimized for mobile devices. Besides the templates an ICF service with following service parameter has to be created: ~itsmobile
1, ~transaction <your transaction> and ~theme <your theme>. If you want to see an ITSmobile service without generating your
own, check out the test services itsmobile00, itsmobile01 or itsmobile02 (testservice for language generation). These services get
deliverd with ITSmobile.
See also SAP note 1072504 regarding ITSmobile sample application.
back to top

How can I check if my ITSmobile environment is running?

Befor you start to create your own mobile internet service try to start one of the test services itsmobile00, itsmobile01 or
itsmobile02. See also SAP note 1072504 regarding ITSmobile sample application.
back to top

Does ITSmobile replace Web SAP Console and SAP Console?

for text based applications: SAP Console.

for webbased applications (ABAP transaction): ITSmobile
Also see SAP note 1070064
back to top

Which devices are supported?

See SAP Note 1093513 and the page "Mobile Devices and Browser".
back to top

My generated internet service is not running, what could be wrong?

See Online Help for possible errors:

SAP NetWeaver 7.4

SAP NetWeaver 7.3 EHP1
SAP NetWeaver 7.3
SAP NetWeaver 7.0 EHP3
SAP NetWeaver 7.0 EHP2
SAP NetWeaver 7.0 EHP1
SAP NetWeaver 7.0

back to top

ITSMobile Message Sound

This is custom documentation. For more information, please visit SAP Help Portal. 15
 7/7/25, 7:29 AM

This page is part of:

How to confirm if your Handheld Browser Supports Sound.
ITSmobile

First review the ITSMOBILE service in SE80 and copy the sapsoundmsg.wav that exists in
the path

ITSMOBILE → TOPIC 99 →MIME Objects →SOUNDS → ALL → sapsoundmsg.wav

to the handheld device.

Then create a blank page on the device itself with a background sound just to see if the
browser supports sound:

<html>

<head>

<title>HTML bgsound Tag </title>

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" >

</head>

<body>

<p> This doesn't create any result on the screen but it plays sound file 3 times in the background </p>

<bgsound src=".\sapsoundmsg.wav" loop="3" >

</body>

</html>

Other option is to test with the value: "<bgsound src="/sap/public/bc/its/mimes/itsmobile/99 /sounds/all/sapsoundmsg.wav"

if the WAV file is accessible on the Handheld device from the Web Application Server then create the following HTML Page

<html>

<head>

<title>Test Sound</title>

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" >

</head>

<body>

This is custom documentation. For more information, please visit SAP Help Portal. 16
 7/7/25, 7:29 AM
<p> This doesn't create any result on the screen but it plays sound file ONE times in the background </p>

<bgsound src="/sap/public/bc/its/mimes/itsmobile/99 /sounds/all/sapsoundmsg.wav">

</body>

</html>

TESTING

ITSMOBILE01 is the ITSMobile service that calls the transaction( ITMOBILE01 )

Call ITSMOBILE01 the test service via the following URL

http(s)://<Host>.<Domain>:<PORT>/sap/bc/gui/sap/its/test/mobile/itsmobile01

( make sure in SICF that the ITSMOBILE01 is active )

→ click on the "+" button → select "514 MESSAGE" → hit the button "STRT" → click the button "Message Type S and I"

get ONE "dong" sound

if you trace using HTTPWatch or review the View Source the file called is: sapsoundmsg.wav

http(s)://<Host>.<Domain>:<PORT>/sap/public/bc/its/mimes/itsmobile/99/sounds/all/sapsoundmsg.wav

→ click the button "Message Type W"

get ONE BEEP sound

OR

"Message Type E".

get THREE Beeps sounds

if you trace using HTTPWatch or review the View Source the file called for "Message Type W"

or "Message Type E" is: sapsounderr.wav

from HTTPWatch trace

http(s)://<Host>.<Domain>:<PORT>/sap/public/bc/its/mimes/itsmobile/99/sounds/all/sapsounderr.wav

For comparison when logged on via SAP GUI for WINDOWS (SAP Logon):

Call transaction: /nITMOBILE01

→ click on the "+" button → select "514 MESSAGE" → hit the button "STRT" → click the buttons "Message Type S and I",
"Message Type W" or "Message Type E".

One will get sounds in SAP GUI for WINDOWS similar to those when called via the itsmobile01 service.

This is custom documentation. For more information, please visit SAP Help Portal. 17
 7/7/25, 7:29 AM

03 Apr 2021 Update:

Newer browsers do not support the <bgsound> tag

Solution is provided in the note 3031889 - ITSmobile audio feature

need the corrections contained in the note 3013443 - ITSmobile Visual Editor: implemented the SoundInclude feature

Another workaround if the Browser does not support the <bgsound and *.wav files is the solution in the

note 1719568 ITSmobile: message sound code moved to a separate include

You will still need to do the code changes to pass the various

~messagetypes for it be effective to be able to emit different sounds.

Note

1428050 ITSmobile: new feature: CURRDYNPRO.MESSAGESOUND

also covers this. (3 different BEEP sounds available via CETERM_SOUND.

IDA_BEEP_OK, IDA_BEEP_WARN and IDA_BEEP_LOUD

Other notes

2377744 - ITSmobile: fixed NOTIFY_BELL_SIGNAL on subscreens

External: Blogs and threads

The following is a very interesting blog (Jan 3, 2017) especially if you use the NEWER Browsers on your handheld device.

as the <bgsound> element is now obsolete with NEWER Browsers and is treated as a non-standard element.

https://developer.zebra.com/community/home/blog/2017/01/03/sap-itsmobile-bgsound-support-on-enterprise-browser

Play beep sound on device when

1. BGSOUND

2. IDA_BEEP.

are NOT supported

This is custom documentation. For more information, please visit SAP Help Portal. 18
 7/7/25, 7:29 AM
https://community.ivanti.com/thread/32043

Device Details:

RF Device - Intermec CK71

Wavelink Velocity Client - Release 1.0.29 - 07/01/2014

Operating System-Windows Embedded 6.5 Classic. CE OS 5.2.29217 (Build 29217.5.3.12.26)

ITSmobile AJAX Communication

What is the ITSmobile AJAX? This page is part of:

ITSmobile

First and in general:

ITSmobile is a web technology therefore the W3C knowledge can be used.

(please check https://en.wikipedia.org/wiki/Ajax_(programming))

What does this means:

Standard SAP ITSmobile communicates with http/s via a normal HTTP Post Event.

This is the standard and classical browser communication.

This classical HTTP communication allows only a synchronous data transfer and the

Browser takes care of the communication. (without the possibility to enhance it or change
it)

This is custom documentation. For more information, please visit SAP Help Portal. 19
 7/7/25, 7:29 AM
In general AJAX means: Asynchronous JavaScript and XML, this means AJAX
communication is an asynchronous communication.

AJAX ITSMobile communication allows to send multiple requests to the server. In addition
it is possible to send the request

using JavaScript. So the communication can be controlled/changed by the application (and

not anymore by the browser)

What is the difference between Standard ITSmobile and ITSmobile using

AJAX?

To understand the two different communication behaviors following scenarios are described:

Scenario 1: classical HTTP/S communication – Standard SAP ITSmobile Communication:

User press a button on an ITSmobile webpage, browser sends the request to the server and will wait for a response from the
server.

During the waiting time (synchronous) user can do noting with the webpage/application. The application is not able to react in
case

Of issues or errors.

Scenario 2: AJAX HTTP/S communication – Enhanced SAP ITSmobile Communication:

User press a button on an ITSmobile webpage , browser sends the request to the server (in details the application = ITSmobile
send the request)

and will wait for a response from the server. However the communication is asynchronous, means the application is not locked and
user can do other things.

Following the benefits exists when AJAX communication is used:

First: As the communication is controlled in the own JavaScript Coding (ITSmobile application) the HTML DOM is replaced using
Javascript

BENEFIT: performance improvement, as the browser doesn’t created the full HTML DOM again and again (specially not the CSS
and JS content)

Second: It is possible to control the communication – wireless/network issues can be managed.

Own error message can be displayed or request can be send again automatically, if wireless communication doesn’t exist.

BENEFIT: the usage of industrial browsers is not anymore mandatory

This is custom documentation. For more information, please visit SAP Help Portal. 20
 7/7/25, 7:29 AM

What are the benefits as summery – when AJAX with ITSmobile makes sense?

The major benefits are the performance improvement and the control of the communication.

Therefore:

1. The performance improvement is bigger especially,

when in a project old devices are used with low memory and low hardware capabilities.

It makes sense to use ITSmobile runs AJAX when old hardware is used.

1. An industrial browser doesn have to be used when AJAX is used because the communication can be controlled

If a company uses many devices it makes sense to invest/modify Standard ITSmobile and enhance it with AJAX JavaScript.

Prerequisites

For more information see attached PPT.

06_ITSMobileRunsAjax_englisch_v8 (3).pdf

ITSmobile Visual Editor

What is the New ITSmobile Visual Editor? This page is part of:
ITSmobile
The ITSmobile Visual Editor is a part of ITSmobile. It introduces the following features:

o Fully integrated screen editing within SE80

More Information...
SAP Notes (ITSmobile Visual Editor)
o Screen elements can be freely arranged on screen Working with ITSmobile Visual
Editor
How to Define Colors
o Positions and dimensions of screen elements are set absolute based on unity Areas of the ITSmobile Visual Editor
pixels (px) How to Define Styles and Fonts
ITSmobile Visual Editor
o All styling of screen elements is based on web standard Cascading Style sheets
(CSS)

o Allows to hide individual screen elements on resulting HTML page without the
need to change the underlying ABAP screen.

How to Use ITSmobile Visual Editor?

This is custom documentation. For more information, please visit SAP Help Portal. 21
 7/7/25, 7:29 AM
There are four Steps to get a running ITSmobile Service from ABAP Screens.

In this example the transaction we are calling is the test transaction "ITMOBILE00"
and the service that we are creating is "TEST_MOBILE". Here are the steps to do this.

1. Create Internet Service.

1.1

First call the transaction in question. In this case it is "ITMOBILE00" - then hit the
following in the following order: "CTRL + Shift +F1" and you will get the 'Technical
Information' popup

as can be seen below.

1.2

Then go to transaction SE80 - ABAP Workbench. In the 'Repository Browser' select

'Program' and enter the program name that you displayed in Step 1.1

In this scenario it is called: SAPMIMOB1. Then select the folder 'Screens'. These are all
the corresponding screens for transaction ITMOBILE00

This is custom documentation. For more information, please visit SAP Help Portal. 22
 7/7/25, 7:29 AM

1.3

Then call transaction SICF and create and activate the service name: TEST_MOBILE
with the below 'GUI Configuration'

2. Generate Editor-Templates.

This is custom documentation. For more information, please visit SAP Help Portal. 23
 7/7/25, 7:29 AM
2.1 Call transaction SE80 and navigate to the step shown in Step 1.2. Select all the
Screens you wish to modify using the ITSMobile Visual Editor, then using right click

select the context menu item 'Other Functions' and then select 'Create Template from
Template'

2.2

Now enter the ITSMobile service in the resulting popup and define the folder theme
name. In our example the service is called 'TEST_MOBILE' and Theme '99'

This is custom documentation. For more information, please visit SAP Help Portal. 24
 7/7/25, 7:29 AM

3. Working with ITSmobile Visual Editor.

3.1 Return to the 'Internet Service': TEST_MOBILE in SE80. In the folder "Editor-
Templates" you will see all the screens from step 2.2 that have been created.

3.2

Double click on Editor template. 'SAPMIMOB1' then select the Edit icon(Pencil and
Glasses). You are now using the ITSMobile Visual Editor!

This is custom documentation. For more information, please visit SAP Help Portal. 25
 7/7/25, 7:29 AM

4. Generate HTML-Templates and Publish them.

4.1 Once you have carried out the modifications using the ITSMobile Visual Editor you
will need to create the HTML template.

From the Editor Templates use context menu "Other Functions"->"Create HTML
Template from (Editor) Templates.".

4.2

This is custom documentation. For more information, please visit SAP Help Portal. 26
 7/7/25, 7:29 AM
Now in the "HTML templates" you will see the resulting HTML template will have been
updated.

Next publish the HTML templates, the ITSmobile service with the modifications using
the ITSMobile Visual Editor is now ready to run.

How do you know that the templates were generated correctly?

When you generate an HTML template from an editor template, the style MOBILEEDIT
is set in the comment section of the template.

Prerequisites
Release and Support Package with ITSmobile Visual Editor included:

o 7.00 SP29 (SAPKB70029)

o 7.01 SP14 (SAPKB70114)

o 7.02 SP14 (SAPKB70214)

o 7.30 SP10 (SAPKB73010)

o 7.31 SP07 (SAPKB73107)

o 7.40 SP03 (SAPKB74003)

This is custom documentation. For more information, please visit SAP Help Portal. 27
 7/7/25, 7:29 AM
o 7.50 and higher

Source: ITSmobile Visual Editor Main Note

1872180

Kernel:

The editor uses the kernel-based JSON support. Therefore Kernel 7.20* or higher is
required.

*For systems with kernel 7.20 at least kernel patch 116 is required. (JSON-Support:
refer to SAP Note 1650141 )

Browser:

Internet Explorer 9 or higher is required to run the editor in SE80.

The ITSmobile Visual Editor was designed to work within SAP GUI's HTML Control
using Microsoft Internet Explorer (MSIE) as documented in SAP note 1872180

The HTML Control based on Chromium or Edge will be supported. See SAP Note
3191851 - ITSmobile Visual Editor with Edge Browser Control

For the time being, please configure SAP GUI to make use of the MSIE based HTML
control.

You can change the browser for the HTML Control in the SAP Logon Pad: SAP Logon
→ Options → Interaction Design → Control Setting .

NB: If you call the ITSmobile Visual Editor to process an editor template, and the editor
hangs and does not show the template in the graphical display,

then check the SAP Note 2570160 - ITSmobile Visual Editor: Determining best value
for wait time in communication between ABAP and ITSmobile Visual Editor.

Areas of the ITSmobile Visual Editor

This is custom documentation. For more information, please visit SAP Help Portal. 28
 7/7/25, 7:29 AM

How to Define Colors

Use the CSS color codes to define colors of the screen elements.

The codes are defined using either hexadecimal color values (#00FF00) or RGB color values (rgb(0.255.0)). The value is a
combination of red, green and blue color. The lowest value is 0 (hex 00); the highest value is 255 (hex FF).

The third way to define a color is in using the actual color name (LimeGreen).

By searching for "css color" you will find plenty sources of css color tables.

How to Define Styles and Fonts

Use CSS Code to define the styles of the screen elements.

The picture below shows a snippet of the ITSmobile Visual Editor with an example how a button can be defined.

Please note that shorthand properties can be used to set several properties at once in a single declaration.

This is custom documentation. For more information, please visit SAP Help Portal. 29
 7/7/25, 7:29 AM
Example: Font Shorthand

in our example we used the order* given by the W3C and defined the following style: italic bold 18px/40px arial

* Order of the values: font-style font-variant font-weight font-size/line-height font-family

Font-size and font-family are mandatory, the other values can by omit.

See the KBA 2768002 - ITSmobile: How to apply a different font for input fields

on how to apply a different Font.

SAP Notes (ITSmobile Visual Editor)

Main Note:

1872180 ITSmobile Visual Editor // Main Note //

The note 2570160 is very important if the ITSMobile Visual Editor is not saving changes correctly when used within SE80
(ABAP Workbench)

ITSmobile Visual Editor runs in an HTMLviewer control of the SAP GUI for Windows

Notes of Improvements and Fixes:

2017.

2570160 - ITSmobile Visual Editor: Determining best value for wait time in communication between ABAP and ITSmobile
Visual Editor

2527234 - ITSmobile Visual Editor: Steploop dimensions are not visualized correctly

2015

2051056 ITSmobile Visual Editor: User changes are not always saved correctly
2176355 ITSmobile Visual Editor: Switching templates during start results in error
2168990 ITSmobile Visual Editor: Alignment of element not recognized
2159730 ITSmobile Visual Editor: Editor supported in SAP GUI for Windows only
2141558 ITSmobile Visual Editor: Mass change of (sub-)screen sizes in editor templates
2136447 ITSmobile Visual Editor: First launch of editor after applying ABAP updates may fail
1873703 Improvements for the initialization of the graphical editor

2014

2051056 ITSmobile Visual Editor: User changes are not always saved correctly
2027612 Incorrect generation style in HTML template
2057020 ITSmobile Visual Editor: Adding or removing CSS properties is not possible
1927694 ITSmobile Visual Editor: "Adapt to screen" does not work
1903390 ITSmobile Visual Editor: Accelerated start, corrections
2005958 ITSmobile Visual Editor: Prerequisites for switching screens quickly
1818662 ITSmobile Visual Editor: Improvements and corrections
1876462 ITSmobile Visual Editor: Hide elements

This is custom documentation. For more information, please visit SAP Help Portal. 30
 7/7/25, 7:29 AM

Working with ITSmobile Visual Editor

Mobile Devices and Browser

General This page is part of:
ITSmobile
With the ITSmobile we don't deliver an environment for a certain mobile device or a special
browser. With the wide range of devices, operating systems and (industry) browsers
supporting all possibilities is not possible. But to get all the functionality of the mobile
device, it is highly recommended to use an industrial browser like PocketBrowser
(Motorola/Symbol), IBrowser (Intermec) or NaurTech Browser (Naurtech Corp.).

The ITSmobile framework does not attempt to identify the mobile devices using the
browser ID (user agent string). In fact, the browser identification is completely deactivated
for ITSmobile. It is possible that your generated HTML templates need additional
customization to run on a specific device or browser, this can easily done by a consultant.
To adapt device-specific functionality ( like i.e. function keys), ITSmobile provides a
procedure to include device-specific META tags or Javascripts.

Examples

If device-specific support is required, you can add the device-specific META tags or
JavaScripts using the following service entry in the HTML page:

~ITSMOBILEDEVICEINCLUDE <Name_of_the_template_to_be_included>

It is sufficient to set the service entry and to make the specified template available in the
service. The delivery of ITSmobile contains four testservices. Testservice ITSMOBILE01
contains the file DEVICESAMPLE.HTML, where specific information can be included. In
addition to this you will find three examples of device-specific customization:

DEVINCLUDE_INTERMEC700C.HTML, DEVINCLUDE_NAURTECHCK61.HTML and

DEVINCLUDE_SYMBOL3090.HTML

See Also

SAP Note

1311169

- ITSmobile: Barcode scanner AutoEnter

SAP Note

1093513

- ITSmobile: Supported browsers and mobile devices

~ITSMOBILEDEVICEINCLUDE

Prerequisites to run ITSmobile

1. Mobile Device This page is part of:

ITSmobile
The code created by the ITSmobile generator works for a wide range of devices
and browsers, however we highly recommend the usage of an industrial browser such as:

This is custom documentation. For more information, please visit SAP Help Portal. 31
 7/7/25, 7:29 AM
Motorola Rho Elements

Motorola Pocket Browser (former Symbol Pocket Browser)

Naurtech CE TERM

Wavelink Industrial Browser

2. Application
To be able to generate templates, you require a functioning SAP Web AS ABAP application. The screen layout of the application
must be designed for mobile devices and their limited visualization functions. That means that the size of the screen must be
adjusted to the screen size of the mobile device and the application should use only screen elements that are supported by
ITSmobile

3. Basis Technology

On the system side, you require an ITS with at least the following service/patch status:

Integrated ITS

We recommed that you are on at least the following Support Pack levels

SAPKB62064
SAPKB64022
SAPKB70014
SAPKB71005

See also SAP NOTE 1031074 ITSmobile 1.1: Supplements and improvements

Standalone ITS

ITS 6.20 Patchlevel 27, SAP Basis 4.6C Support Package: 55 - SAPKB46C55

See also SAP NOTE 1031074 ITSmobile 1.1: Supplements and improvements

Please note...

The ITS prerequisites listed above is only the minimum on Support Package level to run the ITSmobile. Further developments and
improvements are always taking place. We suggest to install the latest BASIS and Kernel versions to ensure not to miss a new
feature or a great improvement.

Required ITSMobile Services

In order to correctly work ITSmobile needs the following internet services to be published

ITSMOBILE
ITSGENMOBILE
ITSGENMOBILE4
ITSGENMOBILEXV

Publishing is done in transaction SE80. See the following Wiki for the steps to do this:
How to activate, publish and test ITS services in the integrated ITS

This is custom documentation. For more information, please visit SAP Help Portal. 32
 7/7/25, 7:29 AM

Service Parameters and Settings for ITSmobile

ITS Service Parameters This page is part of:

ITSmobile

This document only describes ITS service parameters that are either of particular interest
or essential to ITS mobile services. If a particular patch level is required for individual
parameters, this information is provided. Please note that there are also general ITS
parameters, such as 'sap-language', ~record, and ~urlmime that can also be set for mobile
applications.

KBA 2494749 - Add or edit ITS Services parameters in SICF - GUI configuration
[VIDEO], might be helpfull when editing Service Parameters in SICF.

List of the Service Parameters

1) Mandatory Parameters
~ITSMOBILE
~TRANSACTION
~THEME
~SOURCES
2) Unwanted parameters
~WEBGUI=1
3) Parameters for Include Control
~ITSMOBILEDEVICEINCLUDE
~ITSMOBILECSSINCLUDE
~ITSMOBILEJSINCLUDE
~ITSMOBILECUAINCLUDE
~ITSMOBILENOCUAINCLUDE
~ITSMOBILEVOICEINCLUDE
4) Parameters for Popup Control
~POPUPS
~SHOW_SYSTEM_MODAL
5) Additional Parameters
~ITSMOBILEMSGSOUND
~ITSMOBILESOUNDINCLUDE
~RESP_CONTENT_TYPE
~ALVGRIDPAGESIZE
~DYNPRO_COMPRESSION
~ITSMOBILENAMESPACE
~ITSMOBILEELEMFACTOR & ~ITSMOBILEELEMUNITS
~ITSMOBILEELEMFACTOR
~ITSMOBILEELEMUNITS
~ITSMOBILESEARCHHELPSHOWCUA
~ITSMOBILESEARCHHELPNOFILTER
~SEARCHHELPRESULTPERPAGE
~ITSMOBILESEARCHHELPPREV & ~ITSMOBILESEARCHHELPNEXT
~ITSMOBILESTANDARDSMODE
~NO_LOGON_USEREXIT

1) Mandatory Parameters

~ITSMOBILE

This is custom documentation. For more information, please visit SAP Help Portal. 33
 7/7/25, 7:29 AM
The ~ITSMOBILE parameter is mandatory and must be set to 1 for all mobile services. The parameter specifies that the particular
service is for mobile devices and adjusts the ITS environment accordingly. This parameter switches off the ITS browser check and
deactivates the inclusion of the browser-specific Java script on the HTML pages.

The ITS sets up an environment for a mobile service.

Example: ~ITSMOBILE 1

~TRANSACTION

The ~TRANSACTION parameter defines the transaction to be started in the SAP system and thus determines the application to be
run in the Web Application Server. A template must be available in the service for every screen of this application that is called.

Example: ~TRANSACTION itmobile01

When the service is started using the URL, if the subsequent login is successful, the transaction itmobile01 is started.

~THEME

The ~THEME parameter defines the template set that is to be used to display the transaction. You determine which theme must be
specified when you generate the template. The generator saves the templates under the theme you specify. You must specify this
theme with ~THEME in the service so that the templates can be found.

Example: ~THEME 99

When searching the generated templates for the application, the system searches for the template with the matching
name/number in the current service under the HTML templates in folder 99.

~SOURCES

You use the ~SOURCES parameter to specify the services (separated by a comma) in which the templates are to be searched for.
This is useful for screens/templates that are called in different transactions. You consequently do not have to regenerate the
templates for these screens in every service. Instead, you simply specify the service in the ~SOURCES parameter in which the
templates were already generated. Please note that the switch ~SOURCES only applies to the HTML templates. The switch cannot
be used to influence the search order for MIME files (for example, JavaScript, style sheets, and GIFs). Since the runtime service
provides ITSMOBILE for individual system screens, this service should always be specified as the last service.

Example: ~SOURCES itsmobile01, itsmobile

If a template is not found in the itsmobile01 service, the ITS searches the next service listed - in this example: itsmobile - for a
matching template.

2) Unwanted parameters

~WEBGUI=1

Setting the ~webgui parameter to value 1 tells the Internet Transaction Server to start a webgui (SAP GUI for HTML) service.
However ITSmobile services are NOT webgui services. So the ~webgui parameter should be completely removed or set with the
default value "0":
~WEBGUI=1
or
~WEBGUI=0

This is custom documentation. For more information, please visit SAP Help Portal. 34
 7/7/25, 7:29 AM
3) Parameters for Include Control

The parameters for include control are used to be able to make changes to JavaScript, CSS style sheets, or for example, device-
specific function key mapping without having to make changes to the generated templates. By activating these switches, for
example, a separate style sheet can be inserted in all the generated templates without actually changing the generator or the
templates themselves. Please note that the inserted include files replace the default include files from the ITSMOBILE service.
Consequently, your inserted CSS file, for example, must, define all the classes that are defined in the mobile.css default file of the
service ITSMOBILE. Your include files replace the standard include files.

~ITSMOBILEDEVICEINCLUDE

You use ~ITSMOBILEDEVICEINCLUDE to specify your own device include file in which, for example, the mapping of function keys
for a specific device is defined. The device include file is included on every HTML page in the <head> tag. Function keys are
normally mapped using http meta http-equiv instructions that call a specified JavaScript when a key code is entered. The device
include file is exactly the right place for these device/browser-specific instructions. The ITSMOBILE01 service can be used to
illustrate this.

Example: ~ITSMOBILEDEVICEINCLUDE devicesample

The content of the devicesample file is included in the HTML <head> tag on every HTML page. The devicesample file must be
available in the relevant service as an HTML template.

See also SAP Note:

1491666 - ITSMobile: How to obtain function key values

~ITSMOBILECSSINCLUDE

You use ~ITSMOBILECSSINCLUDE to overwrite the default CSS style sheet of the mobile.css file from the ITSMOBILE service. The
specified file must be stored in the SAP system in the current service under MIME objects and must be published. Since your own
CSS file replaces the default CSS style sheet, you must have defined all the CSS classes used by ITSmobile in your file. Therefore it
is recommended to copy the standard mobile.css file and modify it.

Example: ~ITSMOBILECSSINCLUDE mycssstyle

The CSS file mycssstyle.css is included on every HTML page as a style sheet. The file extension .css is adapted and must not be
specified in the parameter. Use transaction SE80 in the SAP system to ensure that the file mycssstyle.css exists in the current
service and was published

See also:

KBA 3056108 -ITSmobile: How to use ~ITSMOBILECSSINCLUDE parameter

KBA 2716570 - ITSmobile: small screen size when using Android devices)
SAP Note 1031074 - ITSmobile 1.1: Supplements and improvements

~ITSMOBILEJSINCLUDE

You use ~ITSMOBILEJSINCLUDE to overwrite the default JavaScript file mobile.js from the ITSMOBILE service. The specified file
must be stored in the SAP system in the current service under MIME objects and published. Since your own JS file replaces the
default JavaScript file, you must have defined all the JavaScript functions used by ITSmobile in your file so that no JavaScript
errors occur when the service is executed.

Example: ~ITSMOBILEJSINCLUDE myjavascript

This is custom documentation. For more information, please visit SAP Help Portal. 35
 7/7/25, 7:29 AM
The JS file myjavascript.js is included on every HTML page as JavaScript. The file extension .js is adapted and must not be
specified in the parameter. Use transaction SE80 in the SAP system to ensure that the file myjavascript.js exists in the current
service under MIME objects and was published.

See also:

SAP Note 1031074 - ITSmobile 1.1: Supplements and improvements

~ITSMOBILECUAINCLUDE

You use ~ITSMOBILECUAINCLUDE to overwrite the CUA area of the HTML page. The default CUA area is at the top of the HTML
page and contains the display of the screen title and error messages, if applicable, and a GIF to trigger enter, a GIF to log off, and
the SAP icon. By specifying a CUA include file, you can independently configure this area without making any changes to the actual
template. When configuring the area, do not forget to display messages. To use the application, it is essential to display the
messages.

Example: ~ITSMOBILECUAINCLUDE mycuaarea

The content of your CUA file mycuaarea.html is included on every HTML page. The file extension .html is adapted and must not be
specified in the parameter. Use transaction SE80 in the SAP system to ensure that the file mycuaarea.html exists in the current
service under HTML templates and was published.

See also:

SAP Note 1031074 - ITSmobile 1.1: Supplements and improvements

~ITSMOBILENOCUAINCLUDE

When the parameter is 1 or X, no CUA area will be rendered at the top of the HTML Page. The default CUA area is at the top of the
HTML page and contains the display of the screen title and error messages, if applicable, and a GIF to trigger enter, a GIF to log off,
and the SAP icon. Having no CUA area saves at least one full line (row), which some applications can appreciate very much.

Example: ~ITSMOBILENOCUAINCLUDE 1

OR

Example: ~ITSMOBILENOCUAINCLUDE X

~ITSMOBILEVOICEINCLUDE

You use ~ITSMOBILEVOICEINCLUDE to configure the generation of XHTML+Voice to meet your own requirements. Your voice
include file replaces the voice.html default file from the ITSMOBILE service. Your file must contain the BHTML functions
GenerateSpeech and GenerateSpeechDialog(FieldIndex), since these two functions are called from the main page to generate the
HTML for speech support.

Example: ~ITSMOBILEVOICEINCLUDE myvoice

To generate speech support, the functions GenerateSpeech and GenerateSpeechDialog(FieldIndex) are called in your
myvoice.html voice include page. The file extension .html is adapted and must not be specified in the parameter. Use transaction
SE80 in the SAP system to ensure that the file myvoice.html exists in the current service under HTML templates and was
published.

4) Parameters for Popup Control

This is custom documentation. For more information, please visit SAP Help Portal. 36
 7/7/25, 7:29 AM
In the default setting, the ITS displays neither popups nor system messages. If a popup or a system message is received, it is
automatically confirmed by ITS with ENTER and is not displayed. This setting makes sense in the majority of cases.
However, for applications that use popups, for example, when logging off ("Do you really want to log off? YES/NO") it may be
necessary to activate popups. Note that the popups can only be displayed as fullscreen images and that a template must be
available for every popup if the ITS does not provide a default template for the screen.
In addition to the application popups, system messages and express mails (transactions SM02 and SO01) can also be activated to
a limited extent for mobile services. This can make sense if you want to make important system messages (for example, update
task terminations) visible to the mobile user. Again, the messages can only be displayed in fullscreen mode and a template for the
screen must be provided if ITS does not provide a default template.

~POPUPS

You use ~POPUPS to activate the application popups for mobile services. If the switch is set to 1, popups are displayed. Please
note that you must provide an HTML template in your service for every application popup. With the default setting "0", ITS
automatically confirms popups with ENTER.

Example: ~POPUPS 1

Application popups are displayed as fullscreen images.

~SHOW_SYSTEM_MODAL

With ~SHOW_SYSTEM_MODAL, you activate system messages and express mails (transactions SM02/SO01) for mobile services.
Please note that the system messages and express messages are displayed as fullscreen images and that a HTML template must
be available for the screen.

Example: ~ SHOW_SYSTEM_MODAL 1

For system messages and express mails, a short message is displayed as a fullscreen image to mobile users.

See also:

SAP Note:

1122923 - ITSmobile, express message, message type

5) Additional Parameters

~ITSMOBILEMSGSOUND

With ~ITSMOBILEMSGSOUND you can activate beeps for messages. If the parameter is set "the beep" is run with the
HTML tag "bgsound" if a message is received. The browser must support the HTML tag "bgsound" so that the beep can be
outputed.

Example: ~ITSMOBILEMSGSOUND 1

When a new message is received, an output "beep" is received according to the message type.

~ITSMOBILESOUNDINCLUDE

If ~ITSMOBILEMSGSOUND is set, than the HTML tag "bgsound" is used to make the device "beep". On some browsers the
"bgsound" HTML tag is not supported. In such cases the parameter ~ITSMOBILESOUNDINCLUDE can be used as described in

This is custom documentation. For more information, please visit SAP Help Portal. 37
 7/7/25, 7:29 AM
SAP Notes 1719568 - ITSmobile: message sound code moved to a separate include and 3013443 - ITSmobile Visual Editor:
implemented the SoundInclude feature.

Example: ~ITSMOBILESOUNDINCLUDE NEWBEEP

~RESP_CONTENT_TYPE

This parameter is only for mobile applications with Language issue requirements. The parameter sets the HTML response-type to
XHTML+Voice. The parameter must be set for all applications that have been generated with ITSMOBILEGENXV i.e
"Mobile devices with language support". All other applications must not set this parameter.

Example: ~RESP_CONTENT_TYPE Application/xhtml+xml

The HTML Response Type is set to xhtml so that the browser can interpret the response correctly. Browsers that have no language
assistance can react differently. Either the page without language assistance is displayed or the content is offered for download.

~ALVGRIDPAGESIZE

Defines how many lines per page are shown in the ALV table.

If not set, all table lines are shown in one page.

A value -1 of the ~ALVGRIDPAGESIZE parameter leads to ALV Grid controls to have the same height as in SAPGUI.

See also:

SAP Note 3019222 - ITSmobile: automatic page sizing for ALV Grid control

Parameter only relevant if you use ALV grid controls in your dynpro.

Example: ~ALVGRIDPAGESIZE 10

~DYNPRO_COMPRESSION

If you wish to remove lines containing no visible elements that are still visible on the screen then set ~DYNPRO_COMPRESSION
service parameter to the value of "1"

NB: This feature is only available with style MOBILE4 (Generation style ITSGENMOBILE4) and you also need to be on at the
following Support Pack listed in the SAP Note 1493374 - ITSmobile: new feature: dynpro compression.

Example: ~DYNPRO_COMPRESSION 1

See also:

SAP Note 3118444 - ITSmobile: fixed empty line height for DYNPRO_COMPRESSION feature.

~ITSMOBILENAMESPACE

This parameter is only needed when you are using an ITSmobile Services with a namspace e.g. "/AII/servicename",
"/SCWM/RFUI" etc As an ICF service name, cannot contain a "/" character it is not possible to create an ICF service with the same
name as the SE80 service which uses the namespace,which is required for ITSmobile to function correctly.

See SAP note:

1323339 - ITSmobile: Services with a namspace, for further details and an example of how to use this parameter.

This is custom documentation. For more information, please visit SAP Help Portal. 38
 7/7/25, 7:29 AM

Example: ~ITSMOBILENAMESPACE /SCWM/RFUI

You also need to be on the Support Pack mentioned in this note for this feature (one can also apply the SNOTE correction from
SAP note 1323339)

~ITSMOBILEELEMFACTOR & ~ITSMOBILEELEMUNITS

Using the following two parameters allows one to the increase the font size of individual elements, but without increasing
the other individual elements on the screen.

~ITSMOBILEELEMFACTOR

This parameter defines the factor (integer number) by which the width of visible elements will be multiplied.

~ITSMOBILEELEMUNITS

This parameter defines defines which measurements units will be used.

Example:

~ITSMOBILEELEMFACTOR 7

~ITSMOBILEELEMUNITS px

will produce "width:70px" for a 10-dynpro-character wide button.

If the parameter ~ITSMOBILEELEMFACTOR is not specified, the default factor is ""0.82"

NB: This feature is only available with style MOBILE4 and you also need to be on at least the following Support Pack's outlined in
the SAP Note 1316326 - ITSmobile: HTML element size is independent of font size to have this feature.

~ITSMOBILESEARCHHELPSHOWCUA

The CUA Area can be enabled by setting the ~itsmobileSearchhelpShowCUA to"X" (default is OFF, i.e. CUA Area is not shown)

~ITSMOBILESEARCHHELPNOFILTER

The Filter Area can be disabled by setting the ~itsmobileSearchhelpNoFilter to"X" (default is ON, i.e. SearchHelp dialog offers a
possibility to filter/restrict the list of possible selection)
The advantage of setting this is to create more screen space for your ITSMobile service if it uses search help functionality

~SEARCHHELPRESULTPERPAGE

Defines the number of results that are returned in the result table.

See also:

SAP Note 1461464 - ITSmobile: improved SearchHelp dialog.

~ITSMOBILESEARCHHELPPREV & ~ITSMOBILESEARCHHELPNEXT

~ITSMOBILESEARCHHELPPREV and ~ITSMOBILESEARCHHELPNEXT can be used to overwrite default labels of the 'Next' and
'Previous' buttons on a SearchHelp dialog. See SAP Note 1461464 - ITSmobile: improved SearchHelp dialog.

NB: You also need to be on at least the followingBasis Support Pack's and Kernel version's outlined in the SAP Note 1461464 -
ITSmobile: improved SearchHelp dialog

This is custom documentation. For more information, please visit SAP Help Portal. 39
 7/7/25, 7:29 AM
to have these additional search help feature's.

~ITSMOBILESTANDARDSMODE

Turn the Standards Mode explicitily on.

See aso:

SAP Note 2289261 - ITSmobile: fixed MOBILE4 generator not to switch to Standards mode

~NO_LOGON_USEREXIT

Using ~NO_LOGON_USEREXIT 1 will disable User Exit.

See also:

SAP Note 1465767 - Logon user exit SUSR0001 not called .

This is custom documentation. For more information, please visit SAP Help Portal. 40