How do I surface language specific texts in Integrated ITS?

[Former Member]

Hello all,

I'm new to both stand alone and integrated ITS and am researching the upgrade process. In our stand alone templates we used htrc files with our html templates to show language specific texts.

Example.

html template code for a field label

`if (i==2) DETAIL-FLABEL[2]= #KAFN end`

htrc name value pair

z_pz01_en.htrc

KAFN Known As First Name

z_pz01_de.htrc

KAFN Bekannt unter dem Vornamen

I see no hint that htrc's can be used in integrated and am not seeing anything in the way of resource based language texts in integrated. I think I've hit every document out there yet, I have a feeling I'm missing something obvious. Your help is appreciated.

Doug

[Former Member · Accepted solution]

Hi Doug,

double clicking to the theme DM in the transaction SE80 should

show the contents of the htrc 'file'. Depending on the logon language

you will see the values of those parameters.

regards

Tobias

[Former Member · Accepted solution]

Thanks Tobias,

II clicked on Theme 99 and came up with a list of empty parameters. From your answer it sounds like the htrc's from 6.20 are expected to be uploaded to integrated. I was able to get them in through SIAC_UPLOAD and SE80>Create to either the Language-Dependant Mime Objects or Mime Objects folders but they appear to have no effect.

Is there an expected process to get them there in the first place?

Once delivered how are x number of languages reflected? In 6.20 you would have x number of htrc's. What does this look like in integrated? (how would KAFN=Known As First Name be represented 10 times for 10 different languages?)

Thanks again,

Doug

P.S. I did enter the parameter/value KAFN = Known As First Name in Theme 99 parameters having logged on in english and publish but it had no effect.

[former_member316351 · Accepted solution]

Hello Doug,

It sounds like you tried this and it didn't work? Just to reiterate the steps:

1. logon in English and go to transaction SE80

2. choose the Z_PZ01 Internet service

3. double click on the topic being used (see the z_pz01 service GUI Configuration/settings in SICF for the ~theme)

4. in the Parameter tab you should set KAFN as the Parameter Name and Known As First Name as the Value

5. Save and publish the service to your Internal ITS

To do the same for German you will need to logon in German.

You can also use SIAC_UPLOAD to do this. Please follow the steps:

1. logon in English, go to Transaction SE38

2. Execute SIAC_UPLOAD

3. choose the "Theme (Language)" tab

4. type in your Service and Theme values (will need "Allow Overwriting" if something exists already)

5. Execute

6. In the popup choose your English htrc file

7. Check in SE80 for the parameters and values like in step 3 above...

Edgar

[Former Member · Accepted solution]

Edgar,

Thanks so much for the detail!

I have run through the steps for manual creation of translations as well as SIAC_UPLOAD of htrc files and have it working and documented. I will add a few more findings here for others who find this post later.

Some of our old htrc files had duplicate keys (probably from original German version). In stand alone ITS the last key in the file was used so this didn't matter. In integrated ITS this matters for 2 reasons.

1 Uploading/Converting htrc files having logged in in English will cause failures if any of the text being entered in the service parameters has characters that arent consistent with the codepage being used for EN. (Ex. back Azureück). Clean up htrc files to use only the language they should contain.

2 Stand alone ITS was forgiving of htrc files containing duplicate keys. Integrated ITS is not. Remove all duplicate keys.

3. This one is obvious but... if parameters have already been entered in another language you may be prompted to confirm you are changing language and there are several prompts along the way. As these prompts will appear in the logon language itu2019s important to eitheru2026

a. Be fluent in all supported languages , oru2026

b. Memorize button and menu positions.

I do have one additional question.

Our old stand alone setup had an alternate corporate "APCI" design that we used...

File system view -

hostDEV_WWWmimesdesigns"apci"webgui as opposed to the out of box

hostDEV_WWWmimesdesignssap_streamlinewebgui I suppose.

I believe this was then referenced in the global services file ~DESIGN="APCI"

I'm starting research to understand if there is an analog to this in the integrated webgui service or precisely what I have to do to accomplish alternate styles for webgui and our Z_services.

Thanks again, points on the way, If I could award more I would.

Doug

[former_member316351 · Accepted solution]

Hello Doug,

The ~design and the ~designbaseurl are mostly used by the Portal. In the Portal there is a tool to create an ITS design. I think this tool basically copies the mimes from the ITS to a separate location and then the Portal Admin can alter the colors, font styles, etc. to create a unified look with the corporation. (I'm sure that's an overly simplified explanation.)

On the ITS side though it's not recommended to change the ~design of the webgui, but you theoretically could. For the webgui it would probably be better to change the ~theme. To do this you would make a copy of the mimes from the topic dm (development mode) to the topic pm (production mode). Then make your changes to the copy of it in the topic pm. You would need to make sure that ~theme pm is specified in the webgui SICF service and that the service is published after the changes.

Edgar

[Former Member · Accepted solution]

OK. Looks like then portal ITS Theme generator should be the first thing I look into. Still lots more to understand. I get the development mode/production mode concept and that its set by ~runtimeMode but don't get how different sources are grouped depending on that setting. Totally don't get "Topic". I've taken enough of your time. All stuff of future reading. For now though I'll look at portal ITS theme generator.

Thx

Doug