How to install and use Language Packs in SAP ... · SAP EPM RIG How-To Guide How to install and use Language Packs in SAP BusinessObjects Planning and Consolidation (BPC) Applicable

SAP EPM RIGHow-To Guide

How to install and use LanguagePacks in SAP BusinessObjectsPlanning and Consolidation (BPC)

Applicable Releases:

SAP BPC for Microsoft 5.1/7.0 SPx

Version 1.0

July 2009

© Copyright 2009 SAP AG. 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. The information containedherein may be changed without prior notice.

Some software products marketed by SAP AG and its

distributors contain proprietary software components of

other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are

registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel

Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,

Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix,

i5/OS, POWER, POWER5, OpenPower and PowerPC are

trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader

are either trademarks or registered trademarks of Adobe

Systems Incorporated in the United States and/or other

countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered

trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame,WinFrame, VideoFrame, and MultiWin are trademarks or

registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or

registered trademarks of W3C®, World Wide WebConsortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems,

Inc., used under license for technology invented andimplemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP

NetWeaver, and other SAP products and servicesmentioned herein as well as their respective logos are

trademarks or registered trademarks of SAP AG in

Germany and in several other countries all over the world.

All other product and service names mentioned are thetrademarks of their respective companies. Data contained

in this document serves informational purposes only.

National product specifications may vary.

These materials are subject to change without notice.

These materials are provided by SAP AG and its affiliated

companies ("SAP Group") for informational purposes only,

without representation or warranty of any kind, and SAPGroup shall not be liable for errors or omissions with

respect to the materials. The only warranties for SAP

Group products and services are those that are set forth in

the express warranty statements accompanying suchproducts and services, if any. Nothing herein should be

construed as constituting an additional warranty.

These materials are provided “as is” without a warranty of

any kind, either express or implied, including but notlimited to, the implied warranties of merchantability,

fitness for a particular purpose, or non-infringement.

SAP shall not be liable for damages of any kind including

without limitation direct, special, indirect, or consequentialdamages that may result from the use of these materials.

SAP does not warrant the accuracy or completeness of the

information, text, graphics, links or other items contained

within these materials. SAP has no control over theinformation that you may access through the use of hot

links contained in these materials and does not endorse

your use of third party web pages nor provide any warranty

whatsoever relating to third party web pages.

SAP NetWeaver “How-to” Guides are intended to simplify

the product implementation. While specific product

features and procedures typically are explained in a

practical business context, it is not implied that thosefeatures and procedures are the only approach in solving a

specific business problem using SAP NetWeaver. Should

you wish to receive additional information, clarification or

support, please refer to SAP Consulting.

Any software coding and/or code lines / strings (“Code”)

included in this documentation are only examples and are

not intended to be used in a productive system

environment. The Code is only intended better explain andvisualize the syntax and phrasing rules of certain coding.

SAP does not warrant the correctness and completeness of

the Code given herein, and SAP shall not be liable for

errors or damages caused by the usage of the Code, exceptif such damages were caused by SAP intentionally or

grossly negligent.

Disclaimer

Some components of this product are based on Java™. Anycode change in these components may cause unpredictable

and severe malfunctions and is therefore expressively

prohibited, as is any decompilation of these components.

Any Java™ Source Code delivered with this product is onlyto be used by SAP’s Support Services and may not be

modified or altered in any way.

Document HistoryDocument Version Description

1.00 First official release of this guide

Typographic ConventionsType Style Description

Example Text Words or characters quotedfrom the screen. Theseinclude field names, screentitles, pushbuttons labels,menu names, menu paths,and menu options.

Cross-references to otherdocumentation

Example text Emphasized words orphrases in body text, graphictitles, and table titles

Example text File and directory names andtheir paths, messages,names of variables andparameters, source text, andnames of installation,upgrade and database tools.

Example text User entry texts. These arewords or characters that youenter in the system exactly asthey appear in thedocumentation.

<Exampletext>

Variable user entry. Anglebrackets indicate that youreplace these words andcharacters with appropriateentries to make entries in thesystem.

EXAMPLE TEXT Keys on the keyboard, forexample, F2 or ENTER.

IconsIcon Description

Caution

Note or Important

Example

Recommendation or Tip

Table of Contents

1. Scenario ...........................................................................................................................1

2. Background Information .................................................................................................1

3. Prerequisites....................................................................................................................1

4. Step-by-Step Procedure ..................................................................................................2

4.1 Without Language Pack ............................................................................................2

4.2 Installation of the Language Pack on the Server ...................................................... 12

4.3 With the Language Pack ......................................................................................... 18

How-to Install BPC Language Packs

July 2009 1

1. Scenario In this document we will see how to install and use a language pack for BPC 5.1/7.0 on the Microsoftplatform.

2. Background InformationWhat is a language pack?

A language pack is a set of resource files that allows the User Interface of anapplication to be switched on a language different from the one in which it has beendeveloped.

In our case after the installation of the language pack on the server, the user canchoose in which language he wants to see all the messages coming from the serverand which is the language for his user interface.

BPC 5.1 Language Pack contains the following languages:

Chinese, English, French, German, Italian, Korean, Japanese, Portuguese,Russian, Spanish

On BPC 7.0M SP3 there are other languages as well (Note 1289888):

Czech, Danish, Finnish, Dutch, Norwegian, Polish, Slovak, Swedish

For the Hungarian language we have to wait for the 7.0M SP4

Language pack needs to be installed on the server in order to be used by the clients.

3. PrerequisitesBelow you can read the configuration of our test environment.

Server configuration:

Single server with Windows 2003 Enterprise

BPC 5.1 SP9

SQL 2005

Client configuration:

Windows XP Italian

Excel 2003


July 2009 2

4. Step-by-Step ProcedureOur step-by-step procedure will go through 3 main steps:

1) Without a Language Pack: we will see how the system appears and behaves without alanguage pack installed.

2) Installation of the Language Pack on the server: we will learn how to install a Language Packon the server and how to use it from the client.

3) With the Language Pack: we will examine how is the system after the installation of theLanguage Pack.

4.1 Without Language Pack...

In the following slides we will see how the client appears when no language pack has beeninstalled on the server.

1. Initially on our server we don’t have any Language Pack installed. The only language installed isthe English language that comes from the BPC installation.


July 2009 3

2. Now let’s go on the client and start installing the BPC for Office. At a certain point of theinstallation we are requested for the language that we want to see on the client UI. You don’tneed any Language Pack on the server for this and let’s choose Italian.


July 2009 4

3. After the installation of the Office client with the Italian language we start the installation of theAdministration Console. It’s performed automatically with the same language chosen for theOffice client.


July 2009 5

4. After installing both the Office and the Administration clients, if we go on the Web interface westill cannot choose a different language for the Web interface because we don’t have anyLanguage Pack installed on the server.


July 2009 6

5. If we connect through the Office client we can see that the interface is correctly in Italian sincewe chose this language for the client installation.


July 2009 7

6. The Excel interface is completely in Italian, give a look at the action pane.


July 2009 8

7. Some messages have been not translated properly!!! As the one that appears after “Open adynamic schedule template”. This is the translation of “A schedule has been built for you”. In theItalian language this means “A calendar has been created”!


July 2009 9

8. The administration console interface appears in Italian.


July 2009 10

9. Unfortunately all the messages coming from the server are still in the English language. Thisbecause we don’t have any language pack installed on the server.


July 2009 11

10. Just the English language is installed on the server. We need to install the Language Pack if wewant all the messages coming from the server to the client to be in the proper language.


July 2009 12

4.2 Installation of the Language Pack on the Server...

1. First of all, we need to copy the installation package of BPC Language Pack on the server. I didput it on the desktop of our test server. Let’s click on “Setup.exe” to start the installation.


July 2009 13

2. Click on Next.


July 2009 14

3. Accept the license agreement and click on Next


July 2009 15

4. The installation is asking which is the language that we want to use for the server messages.Let’s still choose Italian.


July 2009 16

5. The installation starts


July 2009 17

6. The installation is finished


July 2009 18

4.3 With the Language Pack...

1. After the installation, if we run the server manager on the server we can see that the interfacehas been switched automatically to Italian.

Things to remember:

Server manager will always take the language of the last service pack installed on theserver.

If you want to change it you have to open the Options -> Language menu.

Closing and reopening the server manager interface will revert again to the lastinstalled language.


July 2009 19

2. In order to make the language pack fully working for the client, developers recommend toremove and install the BPC Client (BPC for Office and Administration console) again.


July 2009 20

3. I uninstalled all and now I’m ready to install both the tools again.


July 2009 21

4. The installation process automatically proposes to me the Italian language. I have simply to clickon Next.


July 2009 22

5. Now, with the language pack installed on the server and the Administration console properlyinstalled on the client, the server messages appear in the correct language.


July 2009 23

6. As you can see not all has been translated!


July 2009 24

7. Regarding the Web interface you can choose any language from the combo box. After installingthe first language pack on the server, all the languages in the pack are already available for theWeb Interface


July 2009 25

8. We can also choose Spanish for example


July 2009 26

9. The Web interface is automatically set in Spanish.


July 2009 27

10. If I want my client to be set in Spanish as well, I need again to remove the BPC for Office clientand the Admin console and reinstall both again in the desired language.


July 2009 28

11. Now the interface is correctly in Spanish, but the server messages are still in Italian, the lastlanguage chosen during the Language pack installation on the server.


July 2009 29

12. In order to change the server messages coming from the server, I have to re-apply theLanguage pack on the server choosing the proper language.


July 2009 30

13. Now even the server messages are in Spanish.

www.sdn.sap.com/irj/sdn/howtoguides

http://www.sdn.sap.com/irj/sdn/howtoguides

Documents

How to install and use Language Packs in SAP ... · SAP EPM RIG How-To Guide How to install and use Language Packs in SAP BusinessObjects Planning and Consolidation (BPC) Applicable