System Translation

Introduction

Translation of the SAP system is a complex and very time-consuming process because of the various technical objects available for development. Furthermore, not all objects can be translated using the same/identical process.

The process for a high-quality translation must consist of several repeating steps:

• Initial translation of the most significant/known Development and Customizing objects (for example, from this document).
• Testing all relevant processes / applications regarding the translations into the correspondent country language.
• Identify the gaps for the translation:
  • What is missing?
  • Why this object is missing in the previous translations?
  • Define procedure for the future translations and document it accordingly.

• Retry, until the translation is finally okay.

The purpose of this document is to provide an overview of the “System Translation” (ST) tool and steps relevant for translation of the standard VSS and system extensions.

The ST tool consists of two main components:

• ST – Export (see System Translation- Export),
• ST – Import (see System Translation- Import),

And additionally, the SAP Tool “Translation Transport” to be used (see SAP Tool- Translation Transport).

Additionally there will be presented and explained:

• Relevant Development Packages
• Relevant Object Types
• Variants
• Data Extraction Procedure
• Data Import Procedure
• Additional tips/ tricks for analysis/ translation

The special menu exists to access the ST transactions:

• SAP Menu > Tools > ABAP Workbench > Utilities > Translation > System translation >.

There is a special customizing entry in SPRO valid for setup of ST:

• SPRO > Logistics Execution > Vehicle Sales and Service (VSS) > Common Functions > System translation >.

Currently there is only one entry:                   

• “Tags configuration for OpenOffice and Trans. Tool integration” - it contains configuration of Tags for integration of the ST tool and OpenOffice Software.