Overview of Multilingual User Interface Setup

Setting up the multilingual user interface in PPM involves the following high-level tasks:

  1. Confirm that your database language semantics settings are correct. For information, see the Installation and Administration Guide.

  2. Deploy the language packs for the languages that you want supported in the PPM system.

  3. Make sure that you have the following access grants:

    • System: Submit Reports access grant. This is required to run the Translation Details and Translation Summary reports.

    • Sys Admin: Manage Translations access grant. This is required to use the translation scripts (kExportAttributes.sh and kImportAttributes.sh).

    Note: You have these access grants by default if you belong to either the PPM Administrator or the PPM All Access Grants security group.

  4. Assess how importing PPM-provided content translations will affect your PPM system.

    Each language pack provides default translations for the generic configurations provided with each PPM installation. If you are working with a new installation of PPM, we recommend that you import all default translations before you start working on the system configurations for your business. However, if you are working with an upgraded PPM system, your enterprise has likely made significant configuration changes to the original generic content. In this case, the default translations provided for these configurations may not be fully relevant.

  5. (Optional) Based on the results of your impact assessment (Step 4), import the portions you want of the PPM-provided PPM content translations for all deployed languages.

  6. If you use Best Practices, assess and import the portions that you want of the default translations for the Best Practices content.

    Note: If you are working with a new installation of PPM, we recommend that you simply import all default translations before you begin to work on the system configurations for your business. However, if you are working with an upgraded PPM system, your enterprise has likely made significant configuration changes to the original Best Practices content. In this case, the default translations provided for these configurations may not be fully relevant.

  7. Perform configuration tasks as necessary, on an ongoing basis, after the installation or upgrade.

  8. Going forward, as configurations are modified to support changing business needs, managing the added dimension of multiple languages becomes important. To address this, develop and implement a strategy for managing translations of the master data and translatable configuration entities for your organization.

This section provides guidance for performing these tasks.