Understanding Related Language Views

Just as records with language-sensitive fields require related language records, views with language-sensitive fields require related language views.

Related language views work the same way as related language records and must adhere to the same rules:

• Any time you create a view over a table that has a related language record, you typically also need a related language view.

• The related language view consists of, at a minimum, all the key fields from the base view, a language code, and the language-sensitive fields.

• You associate the base view and the related language view in the Record Properties dialog box of the base view.

• When a user logs on in a non-base language, the PeopleSoft system retrieves the data with the appropriate language code from the related language view.

• It’s best to use the same naming convention for related language views as you do for related language records, such as prepending L or _LANG to the _VW suffix of the view name.

Note:

The related language record type must match the base record type—that is, either both are SQL tables or both are SQL views.

Related language views have one additional issue: the SELECT statement from the original view must be modified to select any language-sensitive fields from the appropriate related language tables.

The SELECT statements behind the views vary in complexity, depending on how many tables are involved and how many of those tables have related language records.

Note:

In the following examples, the changes to the SELECT statement for the related language view have been highlighted in bold.