Using Language-Specific Templates

Use

With language-specific templates, there is a separate set of templates for each language supported. The names of these templates have an language indicator that matches the logon language at runtime.

The naming convention for language-specific HTML templates is:

<module pool>_<screen number>_<language>.html

For example, SAPLEC30_1000_D.html.

The HTML templates for a service are stored in a directory with the same name as the service:

...\ 2.0\<virtual-ITS> \Templates\Service

For example, C:\Program Files\SAP\ITS\2.0\<virtual-ITS>\Templates\ECS3.

A typical template directory for the languages German and English might contain:

saplec30_1000_d.html saplec30_1000_e.html saplec30_2000_d.html saplec30_2000_e.html

Note

You can store different sets of HTML templates for the same SAP transaction, and avoid having to define a separate transaction for each variant. For example, you could create HTML templates in one design, other templates in a second design, and so forth.

It is sufficient to define a separate service for each variant, for example, ECS3_SAP and ECS3_UpToDate. Each service then calls the same transaction ( ~transaction statement in the <service>.srvc file). Since each service has its own template directory, you can store different HTML template variants.

The disadvantage of the variant scheme is that HTML pages are stored several times. If structural changes are made to the HTML templates, the different language variants must be adapted one by one.