Why PCS 7 Process-Hierarchy Names Stay in English Below Level 2

When translated process-hierarchy (PH) names appear at level 2 but not at level 3 in OS Runtime, check which project received the translated text tables. In the reported multiproject, the translation had been imported into the AS project but not into the OS project; importing the same translated texts into the project containing the OS and compiling that OS made the deeper-level names appear translated. PCS 7's documented workflow transfers project text data to the OS during OS compilation, so engineering-project and runtime-OS text libraries must be treated separately.

How PCS 7 uses translated project text

In a PCS 7 multiproject, the AS and OS can be separate STEP 7 projects. A translated text table imported into one project does not establish that the corresponding runtime OS project has received the translation. Siemens' PCS 7 Engineering System V9.1 SP2 manual describes multilingual text import into the selected project and explains that compiling/downloading in the corresponding display language transfers changed text to the WinCC text library. Its Operator Station manual says OS compilation makes configured tags, messages and texts from SIMATIC Manager known to the OS. The manuals provide the mechanism; the exact split between level 2 and level 3 in this case was observed in the project, not a documented general behavior.

Correct the project receiving the translation

For the reported case, the fix was to import the translated text tables into the OS project as well as the AS project, then compile the OS. Apply the procedure to the project that actually contains the runtime OS:

Open the multiproject in SIMATIC Manager and identify the specific project containing the OS that displays the PH names.
Select its master data library folder, or the project folder if no master data library exists.
Select Options > Manage Multilingual Texts > Import and import the appropriate translated text file(s). Siemens' PCS 7 V9.1 SP2 Engineering System manual describes selecting the target project and the exported *.xls or *.csv file in this dialog. Check the import log.
Confirm that the required display language is installed for the project and selected as the language for display devices. Siemens warns that the compile/download language must match the language used for the text changes; otherwise the changed texts may not be added to the WinCC text library.
Compile the OS in the project containing the OS using the same language setting. For a multiproject, follow the release-specific merge and compile sequence required for the project structure.
Start or update the intended OS Runtime using the site's normal approved procedure, then switch the runtime language and check the level 2 and level 3 PH names.

If the project uses a PCS 7 release other than the cited V9.1 SP2 documentation, confirm the equivalent menu names and compile workflow in that release's manual.

Check exact text keys only if names remain untranslated

The replies suggest checking the exact text-library entry if importing into the OS project and recompiling does not resolve a name. Search for the full text key as represented in the project and verify source/target language columns and the import log. Do not alter the source-language spelling while translating; preserve the project's original key. A reply suggests spaces or special characters can become $ during OS compilation, but another reply limits that effect to specific hierarchy/tag-name conditions. The reported resolution did not require renaming PH folders, and the available evidence does not show that special-character conversion caused this case.

Why the AS project alone was insufficient here

The reported multiproject had translation data imported into the AS project only. The final answer says the same translated texts also had to be imported into the OS project and the OS compiled for the runtime names to display translated. This does not mean every text must always be duplicated manually: follow the import/export structure and OS configuration for the installed release. It does mean that an AS-side translation by itself is not evidence that the OS Runtime's text library contains the required PH-name translations.

Verification

Review the import log for the OS project and confirm that the correct target language is included. Verify the language for display devices before compiling. After compiling the OS, switch Runtime to the target language and inspect at least one level 2 and one level 3 PH name whose source and translation entries are known. Confirm exact spelling, spacing and target-language values in the relevant text library. If translations remain missing, identify whether the text key exists in the OS project and whether the OS was compiled in the language in which the translation was imported.

Limitations and Operational Precautions

The source does not identify the PCS 7 version, exact import file, OS project names, language pair or compile log. Siemens references opened for this article are PCS 7 V9.1/V9.1 SP2 editions; use their commands only where applicable to the installed version. The thread's successful correction is specific to a multiproject that lacked the imported translations in its OS project. Do not rename hierarchy folders or change OS area identifiers as a first response: that was not the reported fix and can affect project naming/tag mapping. Preserve the original text files and project backup before editing translations.

Verification

Confirm that the runtime OS—not only the AS engineering project—contains the translated PH-name text, that the OS was compiled with the intended display language, and that both lower-level and higher-level names change when Runtime language changes. Record the PCS 7 version, import-log outcome and OS compile result so a later library update or project merge can be checked consistently.

Engineer FAQ

Why does the level 2 PH name translate but level 3 does not? In the reported case, translated text was imported into the AS project but not the project containing the OS; the source does not establish a general level-dependent rule.

Where should PH-name translations be imported for Runtime? Import them into the project containing the target OS, then compile the OS using the corresponding display language.

Does importing a translation into the AS project automatically populate the OS text library? The documented workflow makes OS compilation the transfer point for SIMATIC Manager data to the OS; the reported case required importing the translation into the OS project too.

Which file types does the V9.1 SP2 manual document for multilingual text import? It describes *.xls and *.csv text tables and an import log.

Does the compile language matter? Yes. Siemens' V9.1 SP2 Engineering System manual says compile/download must use the language in which changes were made, or changed texts may not be added to the WinCC text library.

Should I rename PH folders that include spaces? Not based on this symptom alone. The thread's final correction says special-character effects depend on hierarchy and HID configuration; the successful fix was to import texts into the OS project and compile.

How do AS and OS PH views differ? The discussion says the AS text export showed individual names while WinCC showed hierarchical paths; a reply states that difference was normal and not the cause of the translation issue.

What should I check if the names remain in English after the OS compile? Check the OS-project import log, exact source text keys, target-language cells, selected display language and OS compile result.

Does compiling the AS prove that the runtime OS has updated texts? No. Verify that the project containing the OS has received the translation and that the OS compilation completed with the intended language.

Which release documentation applies? Use the manuals for the installed PCS 7 version. The cited V9.1 SP2 steps explain the workflow but the source ticket does not state its PCS 7 release.

Technical References

Siemens, Engineering System (V9.1 SP2), Configuration Manual, A5E50302363-AC (07/2022), §9.4.11, “How to manage multilingual texts,” including importing to the selected project and compiling/downloading in the matching language: https://cache.industry.siemens.com/dl/files/497/109812497/att_1111338/v1/ps7phesb_en-US.pdf?download=true
Siemens, Operator Station (V9.1), Configuration Manual, A5E50302515-AA (02/2021), §6.5.1, “Compiling the OS,” describing transfer of SIMATIC Manager tags, messages and texts to the OS: https://cache.industry.siemens.com/dl/files/374/109794374/att_1057419/v1/ps7phosb_en-US.pdf

PCS 7 multilingual text import and OS compilation

PCS 7 process hierarchy name translation

Why PCS 7 Process-Hierarchy Names Stay in English Below Level 2