Return to Navigation

Understanding Industry-Specific Translate Values

This section discusses:

Generally speaking, translate values are field values that appear in drop-down list boxes (note that not all values shown in drop-down list boxes are translate values). Translate values are a relatively small and static set of values (for example, male and female constitute the values available for the Gender field) and are stored in the Translate table, which is a prompt table in the database used to store values for fields that do not need individual prompt tables of their own.

Because translate values are not market-aware, it often causes development overhead whenever a change is made for specific industries.

For example, if you want to modify the values in the Gender field from male and female to boy and girl for a specific industry, you must access PeopleSoft Application Designer and update the Translate table and the corresponding component and page.

Using industry-specific translate pages you can quickly set up field values for industry use without performing any development tasks in PeopleSoft Application Designer. As you open a page after the setup, depending on the market to which this opened page belongs, the system displays industry-specific translate values (for drop-down list boxes with declared industry-specific translate values).

System-delivered industry-specific translate values can be accessed under select Set Up CRM, then select Product Related, then select Industry Industry, then select Specific Translates.

Note: While this functionality also enables you to insert additional translate values for fields for informational purposes or even for driving processes (that is, perform this action if the user selects option one and perform that action if user selects option two), its main purpose is to provide a quick and easy way to change the label display of translate values on pages for different industries. Therefore, we recommend that you confine the changes you make through this functionality only to the labels of fields that have translate values. Proficient knowledge of PeopleTools is required if you want to drive processes off of translate values based on user selection.