Which data can vary by language?
How do online translations work?
How do I change the session language and translate my online data?
Which data can vary by language?
The following language-specific fields can be translated in a multiple language installation of Oracle iProcurement:
Punchout catalog definition:
Catalog Name
Description
Keywords
Transparent punchout catalog definition:
Catalog Name
Description
Local catalog definition:
Catalog Name
Description
Informational catalog definition:
Catalog Name
Description
Keywords
Store definition:
Store Name
Store Type *
Short Description
Long Description
Image
Non-catalog request template:
Template Name
Organization *
Item Type *
Item Description
Commodity *
Unit of Measure *
Negotiated *
Restrict Suppliers *
Information Template Name
Base and category descriptors:
Descriptor name
Description
Item and browsing categories:
Category Name
Description
* The options or values in these fields, such as Yes or No, vary depending on your session language.
Schema and items that you upload can also be translated. See the Readme files
Note: Translating a catalog definition does not mean that the catalog's contents are automatically translated. It depends on your setup. For example, data in Oracle Purchasing honors the existing translations of the data. If you provided both German and English versions of a category name when defining categories in Oracle Purchasing, then both German and English versions of the category name are available in Oracle iProcurement. In another example, you can translate a punchout catalog's name, but the supplier controls whether the data exists in a particular language.
How do online translations work?
The language in which you are currently viewing fields and data in Oracle iProcurement is called the session language. The language in which you first entered the data is the "initial" language.
For example, you have three language installations of Oracle iProcurement - English, French, and Japanese. The first time you enter these fields, your session language is English. The data you enter is propagated to French and Japanese as well as English. Any change you make in English is made in all languages; however, once you change your session language and translate the data, you must maintain that language separately. For example, you change your session language to French and change a catalog name. Later, you change your session language to English and change the catalog's name in English. That change is now made only in English and Japanese. The application detects that you already made a language-specific change to the French version, and no longer propagates changes to French, unless your session language is currently French.
How do I change the session language and translate my online data?
To vary online data by language, change the session language:
Enter and save the data in one language first. For example, create a store in French.
Click "Preferences" at the top of any page.
In your general preferences, select the desired language, such as English, and click Apply Changes.
Return to the page where you entered the data. For example, return to the page where you defined your store.
Translate the language-specific fields to the new language.
Save your changes.
This is a placeholder for catalog management. Create a file detailing the procedure for contacting your technical support group and replace this file.
A byte can be, but is not necessarily, the same as a character. For example, 700 Japanese characters will typically be longer than 700 bytes, and a special symbol (though it is a single character), may be more than one byte. Therefore, the actual, byte limits are given in the instructions. (For example, a store's Long Description can be a maximum of 2,000 bytes.) How bytes translate to character limits depends on the language and characters you are using and how the database administrator has configured the database character set.