Issue

The number of system languages implemented in a SAP system significantly adds to the complexity of the initial system design, implementation, testing and continued maintenance with respect to master data, system configuration, development (reports, forms, system interfaces, etc.), process documentation, employee user interface, shared service functions and IT support.

There are currently 21 languages logon languages implemented in Syensqo. As a part of the ERP rebuild project there is an opportunity to simplify and standardize the language implementation.

Recommendation

Summarise the recommendation being made for the reader, leaving the pro/con evaluation and exact decision-making process to the subsequent sections.

Background & Context

Implementing multiple system languages in an SAP environment introduces substantial complexity across various stages of the system lifecycle. Here’s a detailed breakdown:

• System Design and Implementation: Incorporating multiple languages into an SAP system involves complex initial design and setup, including installing and configuring language packs and adapting custom developments to support various languages.

• Testing and Quality Assurance: Extensive testing is required across all supported languages to ensure functionality, data accuracy, and user interface consistency, which adds to the overall complexity and effort.

• Master Data and Configuration: Managing master data and system configurations in multiple languages requires careful translation and consistency, impacting data integrity and the configuration process.

• Development and Documentation: Custom reports, forms, and system interfaces need to be multilingual, and process documentation and training materials must be translated and maintained in all supported languages.

• Ongoing Support and Maintenance: Multilingual support impacts IT and shared services functions, requiring additional resources for support and regular updates in all supported languages.

Syensqo currently has around 23 languages installed, 21 logon languages and 2 languages without logon capability. Following are all the languages implemented

Below is the list of employee 

Assumptions

Clearly describe the underlying assumptions which informed or limited the choices available, or impacted the decision: cost, schedule, regulatory requirements, business drivers, country footprint, technology, etc. Include links as necessary. This section is important because a future change in circumstances might invalidate some key assumptions, which then prompts a decision to be revisited. 

Constraints

The employee counts are provided by Business based on the employee count in SF. The evaluation is done based on these employee counts and if there are any discrepancies, the evaluation needs to be repeated

Impacts

Describe the impact of the decision on other aspects such as other processes, infrastructure, other SAP modules or systems, data cleansing and migration, developments, automations, interfaces, in-flight projects, etc.

Business Rules

The decision may translate into business rules which enforce the decision and will require configuration. List these business rules here. For example, "An Outline Agreement cannot be created via the RFQ process. An awarded RFQ can only result in a Purchase Order". 

Options considered

List the options (viable options or alternatives) you considered. These often require a longer explanation with diagrams, or references to other documents (links are best, but attachments are also possible). Use enough detail to adequately explain what you considered so that a project or business stakeholder reviewing this decision will not come back and ask "did you think about...?"; this leads to loss of credibility and questioning of other decisions. This section also helps ensure that you considered enough suitable alternatives rather than just copy/pasting SAP's recommendations.

Following are the options considered for language implementation

Option A: Implement 4 Core Languages (English, French, Italian and Mandarin)

As part of this option, 4 core languages English, French, Italian and Mandarin are implemented. Additional languages Brazilian Portuguese, German, Spanish and Thai are implemented only for Manufacturing and Maintenance operations.

This gives about a coverage of 92.5% of employees (97.15% with additional languages). This option also covers 66 / 67 manufacturing plants across the globe. 

Screens / User Interfaces

• All standard screens will be available in all eight system languages
• All custom screens will be translated in four core system languages. Custom workflow notifications and error messages will be in four core languages
• Custom screens including screen messages and workflows related to Master blast replacement apps will be maintained in five languages viz. English, Canadian French, Latin American Spanish, Russian and Portuguese.
• Selected screens including screen messages and workflows from Simplified Work Management, Risk Assessment and Work Clearance management will be supported in additional four languages viz. Portuguese, Swedish, Indonesian Bahasa and Simplified Chinese.

Master Data Content

• All master data content must be maintained in English language.
• Master data content must be maintained in additional languages for following scenarios
  • Master data contents that affect minimum safety requirements (e.g. Master Blast, WCM)
  • Master data contents to support country specific regulatory requirements on output Forms, Reports and Interfaces

Configuration Values

These includes Orica specific configuration values maintained in the system to support business processes.

• All configuration values must be maintained in English
• Configuration values must be maintained in additional languages to support
  • Configuration values that affect minimum safety requirements (e.g. Master Blast, WM, WCM)
  • Configuration values to meet country specific regulatory requirements on output Forms, Reports and Interfaces

Output Forms

Output Forms primarily consist of Labels (includes Titles, Headings etc.) and content values (Includes Master data, configuration values, user entered text)  

• All Form labels must be maintained in English
  • Form labels to be translated into additional languages to support safety or country specific regulatory requirements
• Form content values will be outputted as maintained in the system

Reports

• Executive and Management Level reports will be available in English only
• For all operational / analytical reports, labels will be in 4S core languages (English, Canadian French, Latin American Spanish, Russian). Additional languages only for those required to meet country specific legal and regulatory requirements or safety requirements.
• Content values outputted on the Report will be as maintained in the system

Master Data Request Form

Master data request form will be available in 4 core languages. Content values available on the master data request form will be as maintained in the system

Training Material - All Orica developed learning materials, including context sensitive online help will be in four core languages only.

Option B: Implement 8 Core Languages (English, French, Italian, Mandarin, Brazilian Portuguese, German, Spanish, Thai)

Describe the option in sufficient detail for a reader familiar with the subject matter to understand it properly

As a part of this option 8 core languages are implemented. This gives about a coverage of  97.15% of employees and covers 66/67 manufacturing plants

Evaluation

Outline why you selected a position. The best format could be a pro/con table (sample below), but is up to you as the author. You must consider complexity, feasibility, cost/effort to implement, but also ongoing operational impact and cost. You must consider the program principles and explain any deviations in detail. This is probably as important as the decision itself.

	Option A	Option B	Option C	Option D
Criterion 1	Pro Con	Pro Pro	Pro Con	Pro Con
Criterion 2	Pro Con	Con	Pro Pro	Con Con
Criterion 3	Pro	Con	Con	Pro

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log

Workflow history