SAP - Language Translation Config v1

8/10/2019 SAP - Language Translation Config v1

http://slidepdf.com/reader/full/sap-language-translation-config-v1 1/52



2

Document Change History

Document Version Date Comments

Version 1 15.05.2014



3

ContentsLanguage Handling Overview ....................................................................................................................... 5

Logon Display in English ............................................................................................................................ 5

Logon Display in Arabic ............................................................................................................................. 6

Language-Dependent Objects in SAP ERP 6.0........................................................................................... 7

Levels of Translation Shipped by SAP ....................................................................................................... 8

Typical Customzing Description ................................................................................................................ 9

Secondary Language Access in SAP Systems .......................................................................................... 10

Language Supplementation .................................................................................................................... 11

Language Supplementation as a Solution: Example ............................................................................... 12

Completing the Language Import: Overview of Main Steps ................................................................... 13

Language Supplementation: Pros and Cons ........................................................................................... 14

Best Business Practice: Translation Handling ......................................................................................... 15

Installing Languages .................................................................................................................................... 17

Language Installation To-Do List ............................................................................................................. 17

Step 1: Read Language Installation Documentation ........................................................................... 18

Step 2: Check Prerequisites ................................................................................................................ 19

Step 2a: Prerequisite for Arabic - Ensure that Unicode is Used ..................................................... 19

Step 2b: Get Required Authorizations for transaction SMLT .......................................................... 20

Step 3: Check language availability and download language import files (language DVD) ................ 21

Step 4: Execute Program RSCPINST .................................................................................................... 22

Step 5: Maintain ABAP Profile Parameters ......................................................................................... 23

Step 6: Classify Language with Transaction SMLT .............................................................................. 24

Step 7: Import Language with Transaction SMLT ............................................................................... 25

Step 8: Import Support Packages with Transaction SMLT .................................................................. 26

Step 9: Supplement Language in either Basic or Expert Mode .......................................................... 27

Step 9a: Supplement Language (Basic Mode) ................................................................................ 28

Step 9b: Supplement Language (Expert Mode) .............................................................................. 29

Step 10: Delete Language Load ........................................................................................................... 30

Step 11: Check and Analyze Logs with Transaction SMLT .................................................................. 31

Step 12: Check Language Installation ................................................................................................. 32

Optional: Step 13: Perform Periodic Language Supplementation ...................................................... 33





5

Language Handling Overview

Logon Display in English

© 2014 SAP AG or an SAP affiliate company. All rights reserved. 3

Customer

Logon with Language EN

ABAP-based SAP systems require the user to specify the logon language in the logonwindow. In the example above, the user selected English as the logon language. As aconsequence, the user interface appears in English.



6

Logon Display in Arabic

© 2014 SAP AG or an SAP affiliate company. All rights reserved. 4Customer

Logon with Language AR

In this case, the user selected Arabic as logon language. Hence the User interfaceappears in Arabic.



7

Language-Dependent Objects in SAP ERP 6.0


Master data

Language-Dependent Objects in SAP ERP 6.0

Customizing

descriptionUser

interface

ABAP

Dictionary

Screen

Painter

The groups shown above can be identified by users as requiring translation. The group of development objects include the objects in the user interface, menus,input forms, and field descriptions, but also textual elements in reports, custom -definedfunctions, transactions, and more. In the slide above, you will find examples on the lefthand side (User interface, ABAP dictionary, Screen painter). Global customizing and configuration texts that must be available throughout theenterprise in all countries in a local language must be typically translated as well.Because most of the customizing is customer -specific, almost all international

customers need to translate this kind of data. Last but not least, master data is an important area which requires translation. The mostimportant group in this category is material and product data. Because a globalenterprise offers identical products in many countries, the product descriptions must betranslated into all the languages of these countries. Another group is the names andaddresses of business partners; for more information about address formats andversions, see Address Format and Address Versions.



8

Levels of Translation Shipped by SAP

The level of SAP standard translations is different for different languages. This isbecause business requirements are not the same for different countries. In Japan, there

is a strong demand to provide all language-dependent texts in Japanese. On the otherhand, users in Scandinavia typically do not have this requirement. Some customerseven do not offer their users the option to log on with a Scandinavian language – theyuse an English interface instead. Hence, a reduced scope for the translation is possiblein some countries.

Existing translation levels can be categorized as follows:

The translation level “User Interface” includes all elements of the SAP systemthat are necessary to operate it in the user's language, for example, screens,messages, menus, and interactive PDF forms.

The translation level “User Interface and Selected Help” includes all elementsof the User Interface level, plus selected help - for example, F1 online help forsystem messages, data elements, reports, and authorization profiles. Oneexample for this level would be simplified Chinese.

The translation level “User Interface, Selected Help, and Forms” includes allelements of the User Interface and Selected Help level, plus forms - for example,SAPscript forms and SAP Interactive Forms software by Adobe. For instanceFrench and Spanish are delivered based on this translation level.

The translation level “Complete Translation” means that all application texts areavailable in the respective language. This includes, for example, payroll-specificdocumentation and release notes. Japanese and German can be named asexamples.

In some application areas, the translation level can deviate from the “global” translationlevel for a specific language. This is especially valid for industry-specific areas. You can find the mapping between SAP language and translation level for SAP ERP 6.0in the SAP Service Marketplace (http://service.sap.com/languages).

http://service.sap.com/languages






9

Typical Customzing Description


Typical Customizing Description

SP01001

Sales Org.Client

DE01001

TVKO

S.O. EspanaSP01ES001

S.O. SpainSP01EN001

V.O. SpanienSP01DE001

S.O. GermanyDE01EN001

TextSales Org.Lang.Client

DE01DE V.O. Deutschland001

TVKOT

Data definition is stored in a Customizing table

For example, TVKO - Sales Organizations

During customizing, language-dependent data is

maintained in the logon language

Yellow data will be shown during

customizing when the user is logged on

in EN

User does not necessarily

know that language-dependent data

is maintained!

SAP typically implements language-dependent functionality in customizing for ABAP-based systems as follows:

In addition to language-independent tables (in the example above, TVKO – SalesOrganizations), there are language-dependent tables that contain the translations.Typically, the names of these tables end with a “T” (for TEXT table). In the aboveexample, table TVKOT contains the translation part of table TVKO. Hence the texts inthis table, with the language key that fits to the logon language, will be shown duringcustomizing.

The user performing the customizing is not necessarily aware of language dependencyof the maintained data. However, Java-based solutions have a different approach forlanguage-dependent data; the texts are typically included in resource files.



10

Secondary Language Access in SAP Systems


Secondary Language Access in SAP Systems

Most parts of the system contain language-dependent data

Language-dependent data is selected according to logon language

Objects behave differently if language-dependent data does not exist

As of SAP NetWeaver Application Server 6.20 for ABAP Dictionary objects: Profile parameter

zcsa/second_language

For example, screens, menu texts, text elements

Does not work for Customizing texts

Customizing texts

Nothing is displayed

Transaction is not usable anymore

System might become unstable if logon language is not complete

System might not be usable for the end user

SAP translation is not complete (level of translation) and customer produces language-dependent data

A solution must be found to provide a stable system

In SAP systems, user interface texts are, in most cases, language -dependent. In ABAP- based systems, the language-dependent data is selected according to the logonlanguage. However, in some cases, language-dependent data might not be translated.In this case, the system’s behavior depends on the type of the object that should bedisplayed in the User Interface.

As of SAP NetWeaver Application Server 6.20, SAP introduced the profile parameterzcsa/second_language for ABAP dictionary objects. The language specified in thisprofile parameter will be used if the translation is missing. This process is valid forscreens, menu texts, text elements, and other objects.

However, the parameter does not work for Customizing texts. In case of missingtranslations in this area, the typical behavior is to show empty fields. But in some cases,transactions will not work due to missing texts. One possible reason for missing textscan be Customizing that is created by customers, but not yet translated.



11

Language Supplementation


Language Supplementation

Gaps in the language-dependent data will be fi lled

• For every language, a specific supplementation language is defined

Language supplementation as of SAP R/3 4.6C is flexible

• Possibility to supplement all types of data

• Master and transaction data

• Single tables

Periodic scheduling of supplementation

• SAP Note 315375

Supplementation description

• SAP Note 1156507

Language supplementation simply copies existing texts from the source language to atarget language. By default, this procedure just fills existing gaps in the target language.

A supplementation language must be defined for every language (except English andGerman). For global systems, English is usually used as the supplementation language. For newer releases, it is possible to supplement all kinds of language-dependent tables.Supplementation can also be performed for single tables.

In addition, it is possible to schedule a supplementation run periodically in order to filltexts of new customizing objects, for example, those created by ongoing projects. Fordetails, refer to SAP Note 315375.

You will find a general description of supplementation in SAP Note 1156507. If you want to check an existing language import, read SAP Note 1159021.

https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361706E6F7465735F6E756D6265723D33313533373526














12

Language Supplementation as a Solution: Example


Language Supplementation As Solution - Example

S.O. EspanaSP01001

S.O. SpainSP01001

S.O. FranceFR01001

S.O. GermanyDE01001

TextSales Org.Client

TVKOT

ES

EN

EN

EN

Lang.

S.O. GermanyDE01001 ES

S.O. FranceFR01001 ES

In the graphic above, you can see the supplementation principle for table TVKOT andlanguage Spanish (ES).

For Spanish, which uses the language key ES, the translation of sales organizationsDE01 and FR01 are missing. The supplementation run copies the English texts forthese sales organizations (S.O. Germany and S.O. France) to the corresponding entrieswith a Spanish language key. As a result, a user who logs on in Spanish will see theEnglish texts for these sales organizations. If customers want to display Spanish

descriptions, this can be achieved by overwriting the English texts in the Customizingtransaction.



13

Completing the Language Import: Overview of Main Steps


Completing the Language Import –

Main Steps

Language import into client 000 Client-independent texts

Supplementation started in client 000 Supplementation of client-independent objects

Client distribution into configuration clients Import of client-dependent Customizing descriptions

Supplementation started for configuration clients Supplementation of client-dependent Customizing tables

Periodic Supplementation in configuration client and client 000 Delta Supplementation (Customizing / Development)

Combined in

Basic

Supplementation

Mode

This slide provides an overview of the basic steps that need to be triggered during alanguage installation. As a first step, the SAP standard texts are imported into client 000followed by a supplementation in this client. After this, all existing logon clients must beprocessed manually by the administrator (client-dependent SAP standard customizingneeds to be copied from client 000 and the clients need to be supplemented). Theperiodic supplementation is optional and is intended for newly created texts in thesource language (for example, EN).



14

Language Supplementation: Pros and Cons


ConsPros

Language Supplementation: Pros and Cons

Easy to handle

Periodic supplementation

Automatic process

Configurable

No maintenance necessary

Translation issues are minimized

Only required data

is translated

Language supplementation is

necessary in all systems

Master language must be complete

Responsibility of configuration team

If source language changes, there is no

supplementation

Texts can be out of date

Translation Workbench status

Status will change to yellow

Full usage of transaction SE63 is

problematic

The advantage of the supplementation method is that customers receive a stablesystem with relatively little effort. In addition, periodic scheduling guarantees that gaps

will be filled in the future. Hence, it is not necessary to translate all missing texts, socustomers can focus on data.

One disadvantage of this method is the fact that supplementation needs to bescheduled separately in all systems; the result of the process cannot be transported. Inaddition, as a prerequisite, the source language must be complete. Otherwise, any textsthat are not available in the source and in the target language, will not be available inthe target language even after the supplementation.

Textual change management is another possible problem. For instance, if a text needsto be changed in the source language, it will not be automatically updated in the target

language. Therefore, customers need to perform double maintenance regardingchanges in the source language.

Last but not least, the translation status displayed in the Translation Workbench(transaction SE63) will be incorrect after a supplementation. If customers want to makeuse of the full range of the Translation Workbench, SAP does not recommend usingsupplementation, which might require to setup a separate translation system.



15

Best Business Practice: Translation Handling


Best Business Practice: Translation Handling

Master language (mostly English) must be defined.

The master language is copied into the target language using language supplementation.

• Standard tools can be used periodically

• Scheduled in all systems• In case of extended use of the Translation Workbench, the system where the translation takes place should be excluded

from supplementation.

Translation of required data (for example, terms of payment) is performed by manual translation

within the development system:

By logging on in the target language (mainly Customizing)

By using IMG activities (Goto Translate) By calling transaction SE63 and selecting objects manually

On-the-fly translation in SE63 using transport requests or worklists

Translation tools (SE63) might be helpful for starting the rollout into a new logon language.

Initial translation of customer-specific developments

One of the key decisions in a global project is the definition of a master language. In

most projects, English is defined as the master language. All language -dependent andlanguage-independent data (including documentation) should be available in English.One reason for this is that English is used as global supplementation language – and asupplementation language should be complete. Most customers run thesupplementation periodically in all systems in the landscape. In case of extended use ofthe Translation Workbench, supplementation should be skipped for those systemswhere the SE63 translation takes place.

However, most customers go for the manual approach. Customizing data can betranslated by logging on in the target language and using the standard Customizingtransactions or, alternatively, choosing Goto translation. Customers can check which

areas need to be translated in the language-dependent view of the IMG. In some cases, it also makes sense to use the Translation Workbench and call objectsdirectly.

As of SAP NetWeaver 7.0, customers can make use of on-the-fly translation usingtransport requests or work lists. In this way, they can make use of the advantages of theTranslation Workbench without difficult setup. If customers need to translate a large number of development objects andsupplementation is not sufficient, a full use of the Translation Workbench could make



16

sense. In this case, the effort for setup and administration of the Translation Workbenchcould be compensated by the advantages from using the features of transaction SE63.



17

Installing Languages

Language Installation To-Do List

The following list shows the steps that are required during language installation.

1. Read language installation documentation.

2. Check prerequisites.

3. Check language availability and download language import files (language DVD).

4. Execute program RSCPINST.

5. Maintain Profile Parameters.

6. Classify language with transaction SMLT.

7. Import language with transaction SMLT.

8. Import support packages with transaction SMLT.

9. Supplement language in either basic or expert mode.

10.Delete language load.

11.Check and analyze logs with transaction SMLT.

12.Check language installation.

13.Optional: Perform periodic language supplementation.

Each step is described in greater detail in the subsequent pages of this document.



18

Step 1: Read Language Installation Documentation

To ensure sufficient knowledge, complete the following tasks:

Read the Language Installation Documentation on the SAP Help Portal

Ensure that you read the following notes:

Note Number Use

330104 Transport requests used for language

delivery // SRx

195442 Language import and Support Packages

1156507 Language supplementation, RSREFILL

and client maintenance

110910 Deleting the language load

508854 How to Use Unicode

For a detailed collection of SAP notes for this topic, see SAP note 1375438 section 4,

"Language Import and Language Handling (BC-CTS-LAN)"

http://help.sap.com/saphelp_erp60_sp/helpdata/EN/04/c89d3665c45904e10000009b38f839/frameset.htm

























19

Step 2: Check Prerequisites

Step 2a: Prerequisite for Arabic - Ensure that Unicode is Used

Unicode is a prerequisite for installing Arabic. The screenshot above shows how you

can check in your system whether this prerequisite is met. For more information about

this requirement, refer to SAP note 73606.







20

Step 2b: Get Required Authorizations for transaction SMLT

Users require the following authorizations in the field CTS_LANFKT of the authorization

object S_CTS_LANG to perform the corresponding activities:

Authorization Activities

ADMI Language transport administration;

particularly for classifying additional

languages

INST Import of a language package

SUPL Language supplementation

SHOW Display authorization; you cannot calltransaction SMLT without this

authorization

All authorizations needed for language transports are in the SAP role

SAP_BC_TRANSPORT_ADMINISTRATOR.



21

Step 3: Check language availability and download language import files (language DVD)

For Business Suite products:

Check: SAP note 330104 Transport requests used for language delivery // SRx

- Find out DVD material number via SAP note 330104

- Search in the download area of SAP Service Marketplace with the DVD

material number

- Go to https://service.sap.com/support > Software downloads >

Installations and Upgrades > Search for installations and upgrades >

Search for <material number >

Note: It might be possible that some products are not available in the

desired language. In this case, customers can translate ABAP-based

products on their own (see section Translation Tools).

Non-ABAP products:

For Non-ABAP products, SAP note 330104 does not apply. Instead:

- Check PAM (search for the product) for language availability

- Contact [email protected], if PAM search is not successful







https://service.sap.com/support






https://service.sap.com/PAM



mailto:[email protected]











22

Step 4: Execute Program RSCPINST

When you execute program RSCPINST and see the screen that is shown in the

screenshot below, complete the following activities:

1. Add a language key (for example, AR for Arabic).

2. Simulate.

3. Activate.

Note: A full description of this procedure can be found in SAP note 42305.







23

Step 5: Maintain ABAP Profile Parameters


5. RZ11: Maintain ABAP Profile Parameters

1. Transaction RZ11

2. zcsa/installed_languages

a) 1-char value: see table T002 via transaction SE16

3. zcsa/second_lang

a) 1-char value: see table T002 via transaction SE16

b) In most cases customers use E (English) or D (German)

c) Should fit to the supplementation language used in 6.

4. Reboot necessary !

The above screenshot shows the profile parameters that must be / should be changedduring the language installation.

1. Execute transaction RZ11.

2. In this step, the zcsa/installed_languages parameter needs to be adapted

(add languages that should be installed for example, A for Arabic). Languagekeys usually are shown with two characters (for example, AR) in the system.However, this parameter requires language keys with one character (for example

A for Arabic). Table T002 shows the mapping between 1-character and 2-character language keys.

3. This is a recommended change / check for the zcsa/second_lang parameter

used as secondary language (that is, the language that is used in case of

missing translation). The default value is D. The supplementation language

defined in step 6 should be aligned with this parameter. So, if you want yoursupplementation language to be English, the value to use in this parameter is E.

4. Reboot.



24

Step 6: Classify Language with Transaction SMLT

Classify a language as follows:

1. Execute transaction SMLT.

2. Choose Language --> Classify

3. In the Language field, specify your language (for example, Arabic, as shown

below).

4. Specify a supplementation language (English is recommended, as shown below).

Result:

The system updates table T002C.



25

Step 7: Import Language with Transaction SMLT


2. Choose Language > Import Package.

3. Specify the path for the language packages (Frontend / Application Server)

4. Select the language package.

5. Execute.

The system performs the language transport in three steps:

a) The language package is unpacked in a background job, after which the

background job is ended.

b) The import tools R3trans and tp import the language data into the system.

c) Any required follow-up activities are performed in a new background job.



26

Step 8: Import Support Packages with Transaction SMLT

After importing the language, you must also import the language data in the Support

Packages. To do this, execute transaction SMLT, select the language that was imported

in step 7 and navigate as follows: Language > Special Actions > Import Support

Packages.

Note: Required Support Packages to be imported must be available. For more

information about this step, refer to SAP note 195442.







27

Step 9: Supplement Language in either Basic or Expert Mode

English and German are the only two languages that are complete in every SAP

system. In general, other languages are not completely translated. This means that at

least some of the texts do not exist in other languages.

Because missing texts can sometimes cause processes to crash, these missing texts

need to be “filled in” in some way. The language supplementation function in the

language transport tools enables you to do this.

You can supplement language in basic or expert mode:

Supplement Language (Basic Mode) Supplement Language (Expert Mode)

Note: There are disadvantages of supplementation (especially in case of a translation

system). Some tables are not supplemented. For more information, see Language

Supplementation: Pros and Cons and SAP Note 1156507.







28

Step 9a: Supplement Language (Basic Mode)

Note: It is recommended that experienced consultants use expert mode rather than basic mode. For

more information, see Step 9b: Language Supplementation (Expert Mode).

If you want to start language supplementation in basic mode, complete the following

steps:


2. Language > Supplement Language

3. Enter a description of your supplementation

4. Enter the conditions for selecting the tables you want to supplement

5. Enter a start time and (optional) target server, and then you are ready to

supplement the language by choosing Execute.

Note: Supplementation actions are client-specific. The languages are supplemented in the

client in which you are logged on. If you use multiple clients, you must supplement the

languages explicitly in each production client. Client 000 must be supplemented before all

other clients.



29

Step 9b: Supplement Language (Expert Mode)


9. (b) SMLT: Language Supplementation (Expert Mode)

Supplementat ion Expert Mode:

Language

Specia l Act ions

Supplementat ion (Expert) .

If you go for the expert mode (as alternative to the basic mode), all logon

clients need to be maintained BEFORE supplementation via

• Language > Special actions > Client Maintenance !

Note: based on feedback from

experienced consultants, the

Expert Mode is the

recommended procedure

If you want to start language supplementation in expert mode (as alternative to the

basic mode), all logon clients must be maintained manually before supplementation via

Language > Special actions > Client Maintenance.

Supplementation Expert Mode is available in SMLT under Language > Special

Actions > Supplementation (Expert).

Note: Based on feedback from experienced consultants, the Expert Mode is the

recommended procedure owing to fewer supplementation-related problems

encountered.



30

Step 10: Delete Language Load

Note: This step is required only if you supplemented languages in Expert Mode.

In this step, you delete the language load in by using program RSLANG20.

For detailed information about this step, refer to SAP note 110910.


10. Delete the Language Load

Functionality is included in point 9 (a) –

Supplementation in Basic Mode

•Only texts are changed, but runtime

representation (the load) is NOT

changed

•One important step if mixed screens

exist

•Report RSLANG20

See SAP Note 110910







31

Step 11: Check and Analyze Logs with Transaction SMLT

In transaction SMLT, manually check and analyze the following items:

Action log

Detailed Information

Job / Application Log





33

Optional: Step 13: Perform Periodic Language Supplementation

Why is periodic supplementation needed ?

• New customer-specific texts are usually not translated immediately

• Objects in Support Packages might be not translated

Solution: Report RSTLAN_SUPPLEMENT_PERIODIC

• Reference is used

• Supplementation can be done monthly, weekly, or daily.

For detailed information about this step, refer to SAP note 315375 - Periodic language

supplementation.







34

Language Import Troubleshooting

Problem Possible Solution

Some SAP standard texts are displayed inwrong language or they are missing

• Check SAP note 990606 • Check that import of language

dependent part in the Support

Packages was executed (SAP Note

195442 / point 8. in this presentation)

• Delete language loads according to

SAP note 110910 (point 10. in this

presentation)

• Solution for missing texts in specific

applications:

• Add-On texts - See SAP note

974677

• Info – Objects in transaction

RSA1- see SAP notes 442764

and/or 562436

• Report groups in transaction

S_ALR_nnnn - See SAP note

719246

• View Selection of Material

Master (MM0x) – see SAP note

107404

Some client dependent SAP standard

texts are displayed in wrong language or

they are missing

• Check if texts exist correctly in client

000. If translation exists in client 000,

but not in other clients - See SAP notes

43853,1156507 and 211226

• Missing texts in specific applications:









































35

Problem Possible Solution

• Units of measure – see SAP

note 211226 (Report

RBZMECHK)

Missing translations Check SAP note 1000586.

Note:

Depending on translation level, not

all SAP standard texts are available

in all languages. The level of

translation for SAP ERP 6.0 can be

checked via

https://service.sap.com/languages

select language.

Customer specific texts are not

translated by SAP

Non-translated texts are not shown in

supplementation language

• Check supplementation according to

point 9. of this presentation in all clients• Check system parameter

zcsa/second_lang (E is recommended

in an international environment)

Missing Texts after transport See SAP note 45548

Need additional information about Arabic

translation corrections for ECC 6.0 EHP6

See SAP note 1730891






















36

Languages for Non-ABAP Products

For JAVA-based applications, texts are stored in resource files and they are included in

the standard installation.

• Language Installation is not necessary

• Check PAM (search for the product) for language availability

• If PAM search is unsuccessful, ask [email protected]











37

Translation Tools

Translation can be done in the following ways:

Manual Translation

Translation Workbench (transaction SE63)



38

Manual Translation


Manual Translation

Transaction SE63 can be used to translate all types of objects

Same display of all objects

Translation workbench is designed for mass translation

Manual Translation: Goto Translation available in many transactions

Customizing can be translated using IMG activity

Additional

information canbe activated for

languagedependencies

Manual translation can be defined as all translation methods available in ABAP-based

SAP systems that do not make use of the full range of the Translation Workbench

(Transaction SE63).

One common way to translate customizing objects in SAP ERP is to choose Goto

Translation in the IMG activity screen (transaction SPRO).

To find branches of the IMG that need translation, customers can switch on the

language-dependent view by choosing

Additional Information Technical Data Language Dependence.





40

Manual Translation Example: Customizing Texts


Example - Manual Translation: Customizing Texts

Goto Translation

This example shows the translation of a sales organization (table TVKOT) via the IMG.

In this IMG activity, you can define new organizations, change existing ones, and also

translate organizations. For translation, highlight the desired entry and choose

Goto Translation.

This will result in a screen where you can choose the languages you want to maintain.

In the example, you can see that sales organization 0002 has not been translated and

exists in English only. Translation can be done for these languages in the window

shown at the right bottom of the slide.



41

Translation Workbench


Components of the Translation Workbench (TA SE63)

Proposal

Pool

As of 4.6C, creation

of transport requests

Update of proposal pool

Provides

proposals for

translation

Statistics

SLLS

Accounting

SLLT

Update

Delete the translated objects

Work-

list

List of objects

that need to be

translated

TranslationEditor

SE63

The examples shown on the previous pages can be described as “case -by-case”

translation methods. These methods fit to customers who want to translate a restricted

set of data. As soon as customers want to translate many ABAP objects belonging to

multiple object types, a more sophisticated tool is needed. The Translation Workbench

(transaction code SE63) provides such functionality. This transaction is included in

every SAP NetWeaver system and it is designed for professional translation of mass

data.

The Translation Workbench includes the Translation Editor, where the texts will be

translated. In addition, the translation workload can be divided between several

translators via individual packages, which will result in work lists for the translators. A

proposal pool serves as dynamic dictionary of the translation process; it is updated



42

constantly. This of fers a “best proposal” to ensure that the same expression is

translated the same way each time.



43

Translation Resources

A list of useful help documentation and SAP notes about translation tools is

available at SAP note 1375438

Translation eBook




https://websmp108.sap-ag.de/~sapidb/011000358700000423272009E/player.html






44

I18N Topics

SAP GUI for Windows

To learn about how to use Unicode in terms of the SAP GUI, refer to SAP note 508854

SAPGUI: How to use Unicode. In particular, refer to the document attached to the SAP

note (for RTL languages: see part 4 of the document).

Recommendation: "Language for Non-Unicode programs (aka system locale)“ in

Windows Control Panel should be set to local language.







45

SAP Logon Options


I18N –

SAP Logon Options

SAP Logon 730

Options

SAP Logon Options:

General

Set local Language

SAPGUI logon window will

be in local language and logon

language is set as default

The screenshot above shows the logon options for setting a local language.



46

SAP GUI Settings for Arabic (English Logon)


I18N –

SAPGUI Settings for Arabic (English Logon)

Customize Local

Layout (ALT-F12)

Options

Character Set

Arabic [Right-

justified]

The screenshot above shows the menu path required to enable SAP GUI characters in

Arabic during an English-language logon.



47

SAP GUI Settings for Arabic (Arabic Logon)


I18N –

SAPGUI Settings for Arabic (Arabic Logon)

The screenshot above shows the menu path required to enable SAP GUI characters in

Arabic during an Arabic-language logon.



48

Right-to-Left Support

Enable browser based SAP applications for Right-to-Left

• Browser-based SAP front end technologies: Extend URL parameter e.g. by

“sap-language=AR&sap-rtl=X”

• See: SAP URL Parameters

• BSP: You can activate RTL rendering using the URL parameter sap-rtl=true

BIDI enablement – SAP Notes:

• 1947545 - How to set BIDI formatting characters RLM and LRM?

• 1291845 - Display of mixture of Hebrew/Arabic, Latin, and digits

http://help.sap.de/saphelp_nw73/helpdata/en/8b/46468c433b40c3b87b2e07f34dea1b/content.htm?fullscreen=true












49

Printing - Right-to-Left

SAP Notes about Arabic and Right-to-Left:

587150 - Support of Arabic-script languages

789080 - MSWord as SAPScript editor for RTL languages

842887 - Enable printing of Arabic-Indic digits

1258722 - LTR Includes in RTL SAPScript/Smartforms documents

1539317 - Restrictions in form layout mirroring

1687289 - Support for Arabic proportional fonts

1879005 - SWINCF: Incorrect font for Arabic

See also Printing in Unicode Systems















https://websmp104.sap-ag.de/~sapidb/011000358700000842792011E/global_printing_20140127.pdf













50

Address Format and Address Versions


Central Address Database

Address Format and Address Versions

Address fordocuments sent tocountry A

Max MustermannKindergartenstraße 4210119 BerlinDeutschland

Address fordocuments sent tocountry B

Jon Doe110, Main RoadSpringfield, IL 62701United States of America

Address Formatting

Franz Muster Hafenstraße 4

Hamburg20022

Deutschlandetc.

GermanAddress Version

何柏兰淮海中路500号

上海20031

中华人民共和国

ChineseAddress Version

何柏兰

淮海路500号海

20031 华人民共和国

RussianAddress Version

The main SAP note for international address versions is SAP note 316331. Use it

to find out solutions for problems related to address versions: activation, printout,

distribution, possible uses, and so on.

For links to additional documentation about international address versions, refer

to point 6 of SAP note 1375438.














51

Useful Links

SAP Note 1375438 - Globalization Collection Note (Information on Globalization)

http://service.sap.com/globalization

SMP - Globalization Workshop

SCN - Language installation on SAP systems - Step by Step (Language

Supplementation is not documented)

SCN – Internationalization and Unicode

SCN - Bidi Texts on SCN

Email address: [email protected]






https://service.sap.com/~form/handler?_APP=00200682500000002672&_EVENT=DISPLAY&_SCENARIO=01100035870000000122&_HIER_KEY=501100035870000008578&_HIER_KEY=701100035871000212410&


http://scn.sap.com/community/netweaver-administrator/blog/2012/12/10/installation-of-languages-on-sap-systems


http://dwdf051/globserv/Global_Solution_Mgmt/Solution_Mgmt_I18N/WorkshopsAndOtherMaterial/Nils/language_installation/AR/SCN%20%E2%80%93%20Internationalization%20and%20Unicode




http://wiki.scn.sap.com/wiki/display/ABAP/Bi-directional+texts+-+Left+To+Right+and+Right+To+Left



























© 2014 SAP AG or an SAP affiliate company.

All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG or an

SAP affiliate company.

SAP and other SAP products and serv ices mentioned herein as well as t heir respective logos are trademarks or registered t rademarks of SAP AG

(or an SAP aff iliate company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epxfor additional

trademark information and notices.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP AG or an SAP affiliate company for informational purposes only, without representation or warranty of any kind,

and SAP AG or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP AG or

SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and

services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP AG or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related

presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and S AP AG’s or its affiliated

companies’ strategy and possible future developments, products, and/or platform directions and f unctionality are all subject to change and may bechanged by SAP AG or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment,

promise, or legal obligation to deli ver any material, code, or functionality. All f orward-looking statements are subject to various risks and uncertainties

that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these f orward-looking

statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.


© 2014 SAP AG oder ein SAP-Konzernunternehmen.

Alle Rechte vorbehalten.

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die

ausdrückliche schriftliche Genehmigung durch SAP AG oder ein SAP -Konzernunternehmen nicht gestattet.

SAP und andere in diesem Dokum ent erwähnte Produkte und Dienstleistungen von SAP sowie die dazugehörigen Logos sind Marken oder

eingetragene Marken der SAP AG (oder v on einem SAP-Konzernunternehmen) in Deutschland und verschiedenen anderen Ländern weltweit.

Weitere Hinweise und Informationen zum Markenrecht finden Sie unter http://global.sap.com/corporate-de/legal/copyright/index.epx.

Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch anderer Softwarehersteller enthalten.

Produkte können länderspezifische Unterschiede aufweisen.

Die vorliegenden Unterlagen werden von der SAP AG oder einem SAP-Konzernunternehmen bereitgestellt und dienen ausschließlich zu Informations-

zwecken. Die SAP AG oder i hre Konzernunternehmen übernehmen keinerlei Haftung oder Gewährleistung für Fehler oder Unvollständigkeiten in

dieser Publikation. Die SAP AG oder ein SAP-Konzernunternehmen steht lediglich für Produkte und Dienstleistungen nach der Maßgabe ein, die in der

Vereinbarung über die jeweiligen Produkte und Dienstleistungen ausdrücklich geregelt ist. Keine der hierin enthaltenen Informationen ist als zusätzliche

Garantie zu interpretieren.

Insbesondere sind die SAP AG oder i hre Konzernunternehmen in keiner Weise verpflichtet, in dieser Publikati on oder einer zugehörigen Präsentation

dargestellte Geschäftsabläufe zu verfolgen oder hierin wiedergegebene Funktionen zu entwickeln oder zu v eröffentlichen. Diese Publikation oder

eine zugehörige Präsentation, die Strategie und etwaige künftige Entwicklungen, Produkte und/oder Plattformen der SAP AG oder ihrer Konzern-

unternehmen können von der SAP AG oder i hren Konzernunternehmen jederzeit und ohne Angabe von Gründen unangekündigt geändert werden.

Die in dieser Publikation enthaltenen Informationen stellen keine Zusage, kein Versprechen und keine rechtliche Verpflichtung zur Lieferung von

Material, Code oder Funktionen dar. Sämtliche vorausschauenden Aussagen unterliegen unterschiedlichen Risiken und Unsicherheiten, durch diedie tatsächlichen Ergebnisse von den Erwartungen abweichen können.Die v orausschauenden Aussagen geben die Sicht zu dem Zeitpunkt wieder,

zu dem sie getätigt wurden. Dem Leser wird empfohlen, diesen Aussagen kein übertriebenes Vertrauen zu schenken und sich bei Kaufentscheidungen

nicht auf sie zu stützen.

Documents

SAP - Language Translation Config v1