Creating Related Language Tables

PeopleSoft applications provide related language tables for most edit tables that you are likely to translate, so in most cases, you won’t have to create your own related language tables. However, if during a customization you create a new table that requires translation, you must create your own related language table.

A one-to-one relationship is recommended between the base record and the related language record. In addition, both base and related language records are recommended to share the same record type. For example, if the base record is a SQL table, then the related language record should be defined as a SQL table.

The following procedure assumes that you know how to design and build records in Application Designer.

Note: If a field is defined as a Long (DESCRLONG), then you must ensure that the table is in a tablespace dedicated to tables containing LONG/IMAGE columns (for example, PSIMAGE tablespace for PeopleTools-owned tables).

Note: Records with duplicate order keys should not have related language tables associated to them. If the record requires a related language record, you must remove the order keys. Do not create a related language record with a duplicate order key.

To create a related language table:

  1. Check the structure of the base table record, noting its key fields, and make sure that it has fields that can be language-sensitive, such as DESCR, DESCRSHORT, or DESCRLONG.

    If the base table has no fields that are language sensitive, then it does not need a related language record.

  2. Design the related language record.

    By convention, the related language record name should reflect its relationship to the base table and end with LANG. For example, if the base table is MY_NEW_TBL, the related language table might be named MY_NEW_LANG.

    The related language record must:

    • Have all the same key fields as the base table.

    • Have an additional key field, which must be LANGUAGE_CD.

    • Have the language-sensitive fields from the base table.

    • Not contain any fields that are not present on the base table except the LANGUAGE_CD key field.

    • Not contain any non-key, non-language-sensitive fields from the base table.

  3. Build the related language table.

    An easy way to build the related language table is to copy the base record definition using the Save As option on the File menu. Once you save the record with a new name, you can remove the fields that are not required on the related language table and add the LANGUAGE_CD key. By using this approach, you avoid having to remember the key structure and column names of the base table.

    Note: When using Save As to create the related language record, you do not need to also save the PeopleCode that is associated with the base record. PeopleCode programs on related language records are not executed; therefore, they are redundant and may be misleading. For this reason, you should not maintain PeopleCode programs on related language records.

    It is also recommended that you remove any search key and alternate search key attributes from the related language table, as these do not need to be translated and can hinder performance.

  4. Associate the related language table with the base table record.

    Open the Record Properties dialog box for the base table. On the Use tab, select the related language record in the Related Language Record field.

    Click OK to close the Record Properties dialog box.

  5. Save the record.