Communicating Language Strategies for SAP Projects

Language strategy is an SAP OCM communication issue in many ways. Naturally, native language menus help end-users to do their jobs in a “language-friendly” environment. However, it is also important to communicate to all end-users what the language strategy is, why it is, and how it will affect their jobs.

OCM communications about language strategy should take place at the appropriate time, which is generally sometime during ASAP Blueprint. This timing is important so that all project stakeholders are clear on the strategy and can weigh in on their language issues and needs.

There are basically two ways to implement an SAP Language Strategy.

1. One language Worldwide for Menus and data entry.
2. Local language Menus and one language for Worldwide data entry.

Both implementations may need to allow local language data entry for legal, statutory or compelling business requirements of the operating country.

Take for an example an America company may deploy a worldwide SAP system allowing it's end-users to have local language menus, but specifying that all data is to be entered into the system in English. Its Chinese subsidiary is allowed to enter postal addresses in Simplified Chinese for business reasons.

Most often, a decision will be made to limit data from being captured in multiple languages on SAP. The driver for this decision is the resulting complex business and technical issues. Implementing multiple languages for data entry may affect low-level system functions such as data consolidation from software providers or third party service providers. Alternatively, it may affect administrators’ ability to make changes to the SAP database tables and profile files.

In summary, menus and data entry are the two main areas to explain when communicating a language strategy for your SAP project.