Installing Oracle-Provided Translations
This section discusses translation installation.
In many cases, Oracle provides translations of the user interface and key application data for PeopleSoft application products. For some PeopleSoft application releases, these translations are delivered separately from the base PeopleSoft application release, and referred to as multi-lingual or multi-language files.
Typically, you would install these translations when you first install your database. However, if you did not install the Oracle-provided translations during your initial install, this section describes the steps to follow to add translations to an already-existing database.
Note: The size impact on the database of installing translations is difficult to predict exactly, but a general rule of thumb is approximately 5% per language.
To add translations, determine how you will perform your upgrade. Choose the most appropriate of the following three options:
Add the translations provided by PeopleSoft application to your existing PeopleSoft database on the same PeopleTools version.
This option is appropriate only if you have not performed any application or PeopleTools maintenance (that is, you have not upgraded, applied patches, or applied maintenance packs), and you have not made any customizations to existing PeopleTools-based objects in your existing database, and your current PeopleTools version matches the version included with your PeopleSoft application. If you have added only new PeopleTools objects to your database, without modifying existing definitions, then you can use this option.
Adding or customizing system data, such as account codes, departments, and locations, is not considered a PeopleTools object change. If you have performed only these types of transactions against your existing database, and you have not modified any objects using Application Designer or PeopleSoft Tree Manager, then you can use this option.
Add the translations provided by the PeopleSoft application to an existing database on a different PeopleTools version.
This option is appropriate if you have not made any customizations to existing PeopleTools-based objects, but your PeopleTools version is different from the version that was available at the time of the GA release of your PeopleSoft application. You will need to set up a separate database with the translations, upgrade the database to your current PeopleTools version, and then copy the translations from your new database to your existing PeopleSoft database.
Use the upgrade process to copy your customizations into a multilingual database.
If you have customized the PeopleTools objects in your database, you cannot simply add the PeopleSoft application translations to your existing database. Instead, you must create a new database containing all of your translations and use the upgrade process to copy customizations from your existing database to your newly installed database.
This procedure is appropriate only if you have not performed any application or PeopleTools maintenance (that is, you have not upgraded, applied patches, or applied maintenance packs), and you have not made any customizations to existing PeopleTools-based objects in your existing database, and your current PeopleTools version matches PeopleTools version included in your PeopleSoft application.
To add translations to an existing database on the same PeopleTools version:
Read the section “Understanding Translation Installation” presented previously in this topic.
Back up your database.
Load your PeopleSoft application translations.
See the product documentation for PeopleTools Installation for your database platform, “Setting Up the Windows File Server.”
Rerun the steps for setting up the batch environment.
If you are running a PeopleSoft Process Scheduler on Microsoft Windows, then you must rerun the steps for setting up the batch environment documented in your PeopleTools installation guide.
Because the PeopleSoft application translation contains translations for your PS/nVision layouts, you must transfer those translations to your Windows-based PeopleSoft Process Scheduler.
If you run only non-Windows-based PeopleSoft Process Schedulers, you do not need to complete this step. This step also does not need to be performed for UNIX batch servers because the only object that contain translations outside the database is PS/nVision reports, which is supported on Windows-based batch servers.
See the product documentation for PeopleTools Installation for your database platform, “Setting Up the Batch Environment.”
Generate database setup from PeopleSoft Data Mover.
Run PeopleSoft Data Mover in bootstrap mode by logging in with your database’s access ID. From PeopleSoft Data Mover, select File, Database Setup, and follow the wizard step by step to generate the database setup script. Be sure to select “Add New Language” in the “Database Type” selection box in the second step of the wizard. The generated database setup script appears in the PeopleSoft Data Mover input view. Be sure to enter the same database parameters that you entered the first time you ran the database setup program to install your English database; do not select any language that already exists in your database.
If you choose a new base language, then the generated script will include the command to swap the base language.
Run the PeopleSoft Data Mover script.
Because you have already created your database and set up the appropriate database-specific objects, you must perform only the “Run Data Mover Import Scripts” task.
Run the VERSION Application Engine program to update your PeopleTools version numbers.
Run the PeopleTools VERSION Application Engine program against your database. This synchronizes the PeopleTools version numbers, taking the new translations into account.
Rerun your database audits.
Your database should now be complete. To ensure that it is complete, rerun the database audits. Refer to the sections about creating and checking a database in your PeopleTools installation guide for more information.
See the product documentation for PeopleTools Installation for your database platform, “Creating a Database.”
This procedure is appropriate only if you have not made any customizations to existing PeopleTools-based objects, but your PeopleTools version is different from the version that was available at the time of the GA release of your PeopleSoft application. To add translations to an existing database on a different PeopleTools version than the one that was available in your PeopleSoft application, you must set up a separate database with the translations, upgrade it to the required PeopleTools version, and then copy the translations from the new database to your existing database.
To add translations to an existing database on a different PeopleTools version:
Read the section “Understanding Translation Installation” presented previously in this topic.
Back up your database.
Install a new database.
Install a new database, including the translations you need at the same time, making sure to perform the steps in the task “Updating Database to Latest PeopleTools Release” in your PeopleTools installation guide. The translations need to be loaded prior to running this task. For more information on installing and upgrading PeopleTools translations, see your PeopleTools installation guide.
See the product documentation for PeopleTools Installation for your database platform, “Updating Database to Latest PeopleTools Release.”
Do a database compare.
Do a database compare of your new database against your existing database to create a project containing all managed object differences between the two databases. Review the database compare report and the generated database compare project to ensure that only language objects are copied, and they don’t overwrite any customizations.
Apply this compare project to the target database.
Export application system data.
In Data Mover, export translated application system data (non managed objects) from the source database to a .dat file. Import the system data into the target database. For application data, the Define System Data menu lists the system data, and the tables involved in determining the system data table names are PS_PM_PS_REC and PSRECDEFN.RELLANGRECNAME. .PS_PM_PS_REC and PS_PM_PS_REC_WHERE define which application data are considered to be system data. These two tables contain base table names, whereas you want to export your data from the related language tables.Determine the related language table name from PSRECDEFN.RELLANGRECNAME.
For example, one table returned by SELECT * FROM PS_PM_PS_REC is the base table name COUNTRY_TBL.
To find the related language table for COUNTRY_TBL, run this select statement:
SELECT RELLANGRECNAME FROM PSRECDEFN WHERE RECNAME = 'COUNTRY_TBL';The related language table is COUNTRYTBL_LANG
In Data Mover, export the translated data from the related language table for the languages being added:
EXPORT COUNTRYTBL_LANG WHERE LANGUAGE_CD IN('ESP');Then in Data Mover, import the translated system data into the target database
IMPORT COUNTRYTBL_LANG;Run the VERSION Application Engine program.
Run the PeopleTools VERSION Application Engine program against your database. This synchronizes the PeopleTools version numbers, taking the new translations into account.
Rerun your database audits.
Your database should now be complete. To ensure that it is complete, rerun the database audits. Refer to the sections about creating and checking a database in your PeopleTools installation guide for more information.
See the product documentation for PeopleTools Installation for your database platform.
This section explains how to load translations by using the upgrade process to copy your customizations into a multilingual database. If you have customized the PeopleTools objects in your database, you cannot simply add the translations contained on the PeopleSoft application to your existing database. Instead, you must create a new database containing all of your translations and use the upgrade process to copy customizations from your existing database to your newly installed database.
To use the upgrade process to copy your customizations into a multilingual database:
Read the section “Understanding Translation Installation” presented previously in this topic.
Back up your database.
Load your PeopleSoft application translations.
See the product documentation for PeopleTools Installation for your database platform, “Setting Up the Windows File Server.”
Rerun the steps for setting up the batch environment.
If you are running a PeopleSoft Process Scheduler on Microsoft Windows, then you must rerun the steps for setting up the batch environment documented in your PeopleTools installation guide.
Because the PeopleSoft application translation contains translations for your PS/nVision layouts, you must transfer those translations to your Windows-based PeopleSoft Process Scheduler.
If you run only non-Windows-based PeopleSoft Process Schedulers, you do not need to complete this step. This step also does not need to be performed for UNIX batch servers because the only object that contain translations outside the database is PS/nVision reports, which is supported on only Windows-based batch servers.
See the product documentation for PeopleTools Installation for your database platform, “Setting Up the Batch Environment.”
Create the new multilingual database.
Create and load your new PeopleSoft global multi-language database, which contains all of the languages you want to use, and apply patches and bundles to bring it to the same level as your source database. Refer to the section on creating a database in your PeopleTools installation guide for more information.
Keep in mind that you must load the English objects provided by PeopleSoft even if you don’t plan to run your system in English. Follow all of the applicable steps in the documentation about creating a database except the swap base language step. You should not swap the base language of your new database until you have copied your customizations into it.
See the product documentation for PeopleTools Installation for your database platform, “Creating a Database.”
Copy the customizations into the new multilingual database.
Use the Application Designer upgrade compare process to compare your existing, customized database against the newly installed database in order to identify your customizations. Once you have identified the objects you have changed, use upgrade copy to copy the objects into your new multilingual database.
If you have maintained all of your customizations in Application Designer projects, you can easily use these projects to copy only the objects you have modified over to your new PeopleSoft global multilingual database.
Create a project with all objects.
This project will be used in the next step to upgrade customizations and translations into the test or production database.
Load changes in the test database.
Using a test database (a copy of the production database) as a target, Using PeopleSoft Data Mover in user mode, import the language tools ptxxxa.db files by running ptxxxa.dms.
Copy the project from the previous step to the database, selecting only the new language.
In the PeopleSoft Pure Internet Architecture, sign in in English and ensure that the new language is marked as Enabled in the Maintain Installed Languages pages.
Run the VERSION Application Engine program to update your PeopleTools version numbers to synchronize the PeopleTools version numbers, taking the new translations into account.
(Optional) Swap your base language. If you have not already swapped your base language and you decide to run your database in a non-English base language, swap the base language of your database.
After testing, repeat the previous steps to load changes in the production database.
Rerun the database audits.
Your database should now be complete. To ensure that it is complete, rerun the database audits, as documented in the PeopleTools installation guide in the chapter on creating a database.
See the product documentation for PeopleTools Installation for your database platform, “Creating a Database.”