Examining Related-Language Messaging Scenarios

Actual related-language messaging scenarios include publishing a non-base language message and switching a preferred language.

This section discusses how to:

Publish a non-base language message to a PeopleSoft subscribing system with a different base language and no prior data.
Switch the preferred language to Japanese and update the same employee's name and address.

Publishing a Non-Base Language Message to a Subscribing System with a Different Base Language and No Prior Data

In the following example, the publishing system base language is English, the subscriber base language is Japanese, and the user’s preferred language is German.

This is the process for publishing:

An online user adds a new level 0 key on a page.

The data is stored in both the base language table (English) and the related-language table (German).
The system publishes a message in the user’s preferred language (German).
The data is inserted into the subscribing system.

The data is inserted into both the base language table and related-language table (German) because it is added for the first time; data cannot reside in a related-language table without corresponding data being in the base table.

Switching the Preferred Language to Japanese and Updating the Same Employee's Name and Address

This is the process for switching a preferred language:

A user switches the preferred language from English to Japanese.

The user updates the same record as in the previous scenario. Data that is not language-sensitive is updated in the base table (English). Language-sensitive data is inserted into the related-language table (Japanese).
A system publishes a message in the user’s preferred language (Japanese).
Data is inserted into the subscribing system.

All data goes to the base table (Japanese), because the message was sent in the same language as the subscribing system’s base language.