Skip to content


This document is written to give system administrators and installation technicians a quick introduction to the language concepts in IFS Cloud.


The purpose with the language concept is to give the end user as much as possible translated texts. In IFS Cloud we differ between client language and database server language.

We also differ between database server stateful session language and stateless session language.

The language is set when the client logins or makes a call to the database, by passing the language to the server session.

Client language

The client language is set either by your environment settings, regional settings or by setting a language in the client. The client language is used to translate all text in the client to the chosen language. It is also used to send down to the server in order to tell the server which language all text should be translated to. The client language can be sent to the database server either by login or by every database call dependent on the state of the session.

Database server language

Database server language is set upon creation of the session. The database session has either retrieved the value from the client or from the environment. Together with the language, territory is also set.

Language impacts the following:

  • Language for server messages
  • Language for day and month names and their abbreviations (specified in the SQL functions TO_CHAR and TO_DATE)
  • Symbols for equivalents of AM, PM, AD, and BC.
  • Default sorting sequence for character data when ORDER BY is specified. (GROUP BY uses a binary sort unless ORDER BY is specified.)
  • Writing direction
  • Affirmative and negative response strings (for example, YES and NO)

Territory impacts the following:

  • Date format
  • Decimal character and group separator
  • Local currency symbol
  • ISO currency symbol
  • Dual currency symbol
  • First day of the week
  • Credit and debit symbols
  • ISO week flag
  • List separator