1. The World’s Leading Provider of eBusiness Applications Software Using Multiple Languages in a Single User Interface Shaun Letley Senior Configuration Specialist Siebel Expert Services

2. Agenda  Configuration Goals  User Interface Translation  Deployment of Translated SRF’s  Display Formats  Multilingual List Of Values  Global User Data  Questions

3. The World’s Leading Provider of eBusiness Applications Software Global Deployment Workshop Architecture Configuration Goals

4. Configuration Goals To deliver a configuration that  Operates independent of  Language  Currency  Time zone  Operating System Regional Settings  Stores data independent of language  Requires minimum changes with the addition of a new language  Processes and Reports data independent of language  Has zero maintenance overhead  Is easy to administer To deliver a configuration that is on time !!

5. User Interface Localization UI Elements  Labels  View Bar/Screen Bar  Menus Messages  Server Messages  Client Messages  Status  Salutation Region-specific UI  Address Applets  Name Applets On-Line Help

6. User Data Translation Configure Translation of Data Multilingual List of Values  Static non-Hierarchical Pick Lists Master Data  Products  Catalogues  Literature

7. The World’s Leading Provider of eBusiness Applications Software Global Deployment Workshop Architecture User Interface Translation

8. Multilingual Repository Multiple languages are stored in the same repository with individual language translations being stored against each Object Adding additional Languages to the Repository  Executed via Configure DB Server Application  Import/Export Repository  Add Language to an Existing Repository  Specify Localization Repository Filename containing translation strings located in …\dbsrvr\ \mstrep_locale.dat  This will include  Configuration data (SRF)  Seed Data (LOV’s)  Bitmaps

9. User Interface – Locale Configuration Locale settings are available for 36 object types  Examples of Locale enabled Objects  Application  Application, Page Tab, Screen Menu Item  Screen  Screen, Screen View  View  View, View Report, View Web Template Item  Applet  Applet, Chart, Chart Elements, Controls, Drilldown, List Control, Menu Item, Tree Node  Web Template  Web Template, Web Template Item  Examples of Locale attributes  Language attributes  Display Name, Menu Text, Prompt Text, Status Text, Thread Text, Title, ToolTip Text, Text, View bar Text  Display attributes  Available, HTML Height, HTML Width, HTML Max Chars Displayed, Text Alignment, Show In List, Visible  Configuration Management Attributes  Changed, Comments, Language Code, Redo, Translate

10. User Interface – Configuration Object Explorer allows the user to see the locale specific attributes

11. User Interface – Tools active language View  Options  Set the active tools language  Determines  Which strings are displayed in the applet designer  Compile Language of SRF  Language override  Once enabled controlled through Edit Mode on the Configuration Context tool bar  Active Language displayed in status bar of Siebel Tools

12. User Interface – WYSIWYG Editing Visual editors have two modes  Base mode: Changes are stored against the base object

13. User Interface – WYSIWYG Editing Visual editors have two modes  Language Override mode: Changes are stored against the child locale object

14. User Interface – WYSIWYG Editing Editor Modes  Only effective when in Layout Editors  Base Mode: All changes are stored on base object, such as the List Column Object  Language Override Mode: All changes are stored on the locale object, such as the List Column Locale Object  Base Attributes and Locale Attributes appear in Properties window  Locale Attributes suffixed with “– Language Override”  Changes to base properties are stored against the base object  Changes to suffixed properties are stored against the locale object  Previous screen shots would have had the following Visible in List property settings in the Properties window. Show in ListTrue Show in List – Language OverrideFalse Base Mode Language Override Mode

15. User Interface – Locale Management Utility (LMU) Tools  Utilities  Locale Management  Locale Management Utility replaces String Search Utility  Options Tab: Where Source, Target Language and Application(s) are specified

16. User Interface – Locale Management Utility (LMU) Untranslated Strings Tab  Identifies all Untranslated strings that do not exist in the Target language, but do in the Source Language of the specified Application(s)

17. User Interface – Locale Management Utility (LMU) Export Tab  Exports string attributes or all locale attributes  Exports for specific project(s) or selected Application (via Options Tab)

18. User Interface – Locale Management Utility (LMU) Import Tab  Imports previously exported string locale attributes  Exports for specific project(s) or selected Application (via Options Tab)

19. User Interface – Locale Management Utility (LMU) Modified Objects Tab  Identifies changes objects in the repository since a specific date or based on a previously exported file

20. The World’s Leading Provider of eBusiness Applications Software Global Deployment Workshop Architecture Deployment

21. User Interface - Compilation Tools  Compile  Compiles language specific SRF based on Tools Active Language  New Tools  Compile Selected Objects menu item for incremental compiles

22. One Code Page, One Language Siebel Connected Clients ENU, ENU, ENU Siebel Mobile Web Clients ENU, ENU, ENU ENU Siebel Database Database Server Siebel Web Server(s) Siebel Application Server(s) Code page 1252 ENU Repository File (SRF)

23. One Code Page, Multiple Languages Siebel Connected Clients ENU, DEU, ESN Siebel Mobile Web Clients ENU, DEU, ESN ESN DEU ENU Siebel Database Database Server Siebel Web Server(s) Siebel Application Server(s) Code page 1252 ENU Repository File (SRF) DEU Repository File (SRF) ESN Repository File (SRF)

24. Multiple Code Pages, Multiple Languages Code page 1252 Siebel Connected Clients ENU, ENU, ENU Siebel Mobile Web Clients ENU, ENU, ENU ENU Siebel Database Database Server Siebel Web Server(s) Siebel Application Server(s) Code page 932 Siebel Connected Clients JPN, JPN, JPN Siebel Mobile Web Clients JPN, JPN, JPN JPN Siebel Database Database Server Siebel Web Server(s) Siebel Application Server(s)

25. The World’s Leading Provider of eBusiness Applications Software Global Deployment Workshop Architecture Display Formats

26. Data Display Formats User Interface representation dictated by Regional Settings (Control Panel) for following where no Locale parameters are Specified on the Siebel Object Manager  Server (Siebel Object Manager)  Web Client  Dedicated Web Client  Mobile Web Client Client items affected are the display of  DatesDD/MM/YYYY, MM/DD/YY, etc  TimesHH:MM, HH:MM:SS, etc  Numbers- 9,999,999.99, 9.999.999.99 -, etc  Currencies£, $, €, etc  Phone Numbers+1, +44, +353, etc

27. Data Display Formats Date/Time Currency Phone Number

28. The World’s Leading Provider of eBusiness Applications Software Global Deployment Workshop Architecture Multilingual List of Values

29. List of Values (LOVs)  Display the language dependent text in the pick list 2. Get the language dependent text and store it into the target table Siebel Client Siebel Database 2 1 S_ORG_EXT

30. Multilingual List of Values (MLOVs)  Display the language dependent text in the pick list 2. Get the language independent code (LIC) of the selected text and store it into the target table Siebel Client ENU Siebel Client ESN Siebel Database 2 1 1 2 S_LST_OF_VAL 2 1 S_ORG_EXT

31. Dynamic Translation of Data - List Of Values Screens  System Administration  List Of Values

32. MLOV Conversion Restrictions LOV Conversion restrictions are  Only Static LOV’s can be converted to MLOV’s  Those based on the S_LST_OF_VAL table  LOV Column must be associated with one and only one LOV Type  LOV Column must have a translation table specified  LOV Column must be LOV bounded  If an LOV is referenced within a Visibility Rule it will require ES approval to convert to an MLOV LOV Translatable Flag displays Siebel eBusiness Application Configuration setting  FYI information that denotes if the LOV Type is translatable without effecting functionality within Siebel

33. Siebel MLOV Wizard – Validation Executed via Configure DB Server Application Run Database Utilities  Multi-lingual List of Values Conversion  Validate MLOV  Validates repository Values against MLOV values to determine if values exist that do not have a corresponding Language Independent Code

34. MLOV Conversion Restrictions  Specifically the following LOVs can not be converted to MLOVs  TAS_STRATEGY, PERIOD_TYPE, FS_CARRIER, CARRIER_PRIORITY, PAY_ACCNT_CD, DISCNT_PERCENT, EAI_ORDER_SYNC_STATUS, FREIGHT_TERMS, PAYMENT_METHOD, FS_INVLOC_ORDPRI, FS_SHIPPING_METHOD, FS_ORDER_STATUS  This is a minimum (known) list. Additions can be made to this by release version and industry specific solution  Hierarchical MLOVs are not supported, so Hierarchical LOVs can not be converted into MLOVs  Siebel Expert Services can perform a MLOV NSCR to advise on the impact of MLOV conversion on a configuration  Recommended by Product Marketing, Technical Support and Expert Services to avoid potential problems moving forward  Conversion via Siebel MLOV Wizard  Log Files written to …\Siebel_Server\Log directory

35. Siebel MLOV Wizard – Conversion Executed via Configure DB Server Application Run Database Utilities  Multi-lingual List of Values Conversion  Translate MLOV  Validates values to ensure that there is a corresponding LIC prior to conversion  Converts the LOV Type to an MLOV Type  All columns associated with LOV Type should then be converted to MLOV columns  Six rules need to be satisfied for conversion to successfully complete

36. The World’s Leading Provider of eBusiness Applications Software Global Deployment Workshop Architecture Global User Data

37. Global User Data Same Product Different (Localized) Description Global User Data means storing attributes for certain entities in multiple languages

38. Global User Data - Administration Separate Administration Views for Global User Data  View  Site Map  Product Administration  Translations

39. Global User Data - Configuration Siebel contains six areas where translation can take place of Global User Data  Product  Class  Attributes  Literature  Catalog  Category Additional Configuration required to implement functionality as not currently configured as standard  Creation of _LANG table if not present as a M:1 extension table of the parent table  For example, S_PROD_INT_LANG is a M:1 table for parent S_PROD_INT  Build BC mapped to _LANG table  Create Applet based on BC to display data and associated with a view

40. The World’s Leading Provider of eBusiness Applications Software Global Deployment Workshop Architecture Restrictions

41. What can not be Translated  DLL Messages and Dialogs  These are install specific although new Languages can be added to the server to provide associated messages and dialog boxes in the correct language through the Configure DBServer utility  Logon screens  Individual URLs can be used to link to translated Login Pages, but until a user logs in it is unknown what language they should be using  System and User preferences  Dynamic and Hierarchical LOV’s  Application Server Processes Log

42. Where to Get More Information Support Web  Siebel 7 Language Support & Global Application features SOD  Global Deployment FAQ ’ s and SR ’ s  Technical Support Technical Notes  Siebel 7.5 Unicode Statement of Direction (SOD) Literature  Siebel Bookshelf – Siebel Global Deployment Guide  Globalization White Paper (Please ask your CAM/TAM/Sales Representative) Siebel  Technical Support  Customer/Technical Account Manager  Professional Services  Global Deployment Competency  Expert Services  Global Deployment Reviews, Workshops and Consultancy  Product Marketing

43. Using Multiple Languages in a Single User Interface Questions ?