Language Localization Guide. version v12.15

Transcription

1 version v12.15

2 Disclaimer This document is for informational purposes only and is subject to change without notice. This document and its contents, including the viewpoints, dates and functional content expressed herein are believed to be accurate as of its date of publication. However, Epicor Software Corporation makes no guarantee, representations or warranties with regard to the enclosed information and specifically disclaims any applicable implied warranties, such as fitness for a particular purpose, merchantability, satisfactory quality or reasonable skill and care. As each user of Epicor software is likely to be unique in their requirements in the use of such software and their business processes, users of this document are always advised to discuss the content of this document with their Epicor account manager. All information contained herein is subject to change without notice and changes to this document since printing and other important information about the software product are made or published in release notes, and you are urged to obtain the current release notes for the software product. We welcome user comments and reserve the right to revise this publication and/or make improvements or changes to the products or programs described in this publication at any time, without notice. The usage of any Epicor software shall be pursuant to an Epicor end user license agreement and the performance of any consulting services by Epicor personnel shall be pursuant to Epicor's standard services terms and conditions. Usage of the solution(s) described in this document with other Epicor software or third party products may require the purchase of licenses for such other products. Where any software is expressed to be compliant with local laws or requirements in this document, such compliance is not a warranty and is based solely on Epicor's current understanding of such laws and requirements. All laws and requirements are subject to varying interpretations as well as to change and accordingly Epicor cannot guarantee that the software will be compliant and up to date with such changes. All statements of platform and product compatibility in this document shall be considered individually in relation to the products referred to in the relevant statement, i.e., where any Epicor software is stated to be compatible with one product and also stated to be compatible with another product, it should not be interpreted that such Epicor software is compatible with both of the products running at the same time on the same platform or environment. Additionally platform or product compatibility may require the application of Epicor or third-party updates, patches and/or service packs and Epicor has no responsibility for compatibility issues which may be caused by updates, patches and/or service packs released by third parties after the date of publication of this document. Epicor is a registered trademark and/or trademark of Epicor Software Corporation in the United States, certain other countries and/or the EU. All other trademarks mentioned are the property of their respective owners. Copyright Epicor Software Corporation All rights reserved. No part of this publication may be reproduced in any form without the prior written consent of Epicor Software Corporation

3 Table of Contents 1 System Language Localization 4 Language Packs Available 5 Setup 6 Running the License Key 6 Activating the Feature 6 Creating the Language Set 7 Downloading Language Packs 8 Setting Up Translated Forms 8 Setting Up Translated Reports 9 Setting User Language 9 2 Customer, Supplier, and Location Specific Forms 11 Walkthroughs 12 Assigning Form Templates 12 Printing Custom Forms 13 Setup 14 Defining the Script Path for Form Templates

4 1 System Language Localization This functionality replaces the system text with translations into your language of choice. While you can manually adjust translation values yourself (see Language Localization: Concepts and Features in the Prophet 21 help file), the process described in this chapter includes instructions on acquiring and installing a pre-written translation package that contain scripts to populate the table of native terms used within Prophet 21 and the tables containing the translated terms and messages, as well as translated forms and reports. You can still use the process described in the help files to tweak the translation to fit your specific needs after running this process. Use Crystal Reports for modifications to reports and forms. Note: The scripts delivered with the translation packs need to be run through SQL32. Important! The translation package described in this chapter will display all system labels in the language you designate, however it has no impact on user-defined fields and labels created through DynaChange TM. Even if a field created through Screen Designer matches a label in the translation table, Prophet 21 will use the label designated in DynaChange TM. You can, however, use DynaChange TM to create multiple version of the screen and apply those versions to people needing alternate language displays. Field labels, tab labels, and menu options that you have modified via DynaChange TM Designer take precedence over translation and the user modified values will not be translated, even if the user modified value matches a term used elsewhere in the system

5 Language Packs Available Language Packs Available Epicor currently offers the following language packs, available for download from the customer site. French Canadian Spanish (LAC) - 5 -

6 Setup Setup The following tasks set up the system specifically for use with the functions described in this chapter. Running the License Key When you purchase a translation pack, Epicor will deliver a license key to you along with instructions on how to apply it to your system. You must run this key before performing any of the other steps described here, and the key unlocks some of the essential functions used within this process. Note: You can download the translation pack files prior to running the license key, but you will not be able to apply them to the system without it. Activating the Feature Navigation Path: Setup > System Setup > System > System Settings > General Once you've run the license key, you must activate this functionality in your system. Do this by activating the Enable Translation setting found at the end of the path shown above

7 Setup Creating the Language Set Navigation Path: Setup > System Setup > System menu > Language Maintenance To localize your user interface language, you must set up a language record for each language you plan to provide for your users (beyond the system default US English). You can create new language records in Language Maintenance. You will associate a language record to a specific translation

8 Setup Downloading Language Packs Epicor has language packs available for download from the customer site. These are.zip files that contain the following: SQL scripts Translated Crystal Reports Translated Crystal Forms Find the available language packs at the following URL: %2FAdditional+Downloads+and+Updates%2FLanguage+Packs Setting Up Translated Forms Navigation Path: Setup > System Setup > System > System Settings > System Setup > Files and Folders Once you've downloaded the forms from your selected translation pack, place them in the Crystal Reports folder. Important! You must place these forms in the same folder as the baseline Crystal Reports. If you put them elsewhere, the system will not know where to find them. Placing them in the same folder makes both the baseline and translated forms available come print time. The translated forms have the same names as the base forms, but are appended with the language name, so they can safely reside in the same folder with the baseline forms. Designate them for use by customer, location, and supplier as described in Customer, Supplier, and Location Specific Forms on page

9 Setup Setting Up Translated Reports Navigation Path: Setup > System Setup > System > Language Maintenance Once you have downloaded the language pack you need, place the translated reports files in a folder created just for them. Important! Because translated reports have the same name as the standard ones, they must be placed in a different folder. Otherwise they will overwrite the baseline reports. If you are running in a multiple terminal server environment, you must create this translated report folder on each server, or make it a common folder shared by all terminal servers in your network. Then, in Language Maintenance, enter the path to that folder in the Crystal Reports Folder field. Note: This file path field is only available after running the language pack script. Setting User Language Navigation Path: Setup > System Setup > System> User Maintenance Prophet 21 can display different languages by user. Select the language each of your users will see in their session of Prophet 21 by setting it in their user profiles in User Maintenance

10 Setup The default for this setting is U.S. English, but this drop down displays all languages set up in Language Maintenance. Note: Remember, once you make and save a user setting change, it does not take effect until the user logs out and logs in again

11 Setup 2 Customer, Supplier, and Location Specific Forms Prophet 21 custom forms functionality enables the user to specify forms tailored to each customer, supplier, or location. The system uses custom form templates that you create to produce documents requested during transactions. When you submit a transaction and request to print the related forms, the system checks for a template that you pre-assign to the associated entity. When a transaction with custom forms functionality is generated, the system looks first to find a custom template to create the form. If none is assigned, the system generates the form using standard form selection functionality

12 Walkthroughs Walkthroughs This section shows you how to accomplish tasks, and provides explanations of the various areas of the system involved. Assigning Form Templates Navigation Paths: Accounting > Accounts Receivable > Maintenance > Customer Maintenance Inventory > Purchasing > Maintenance > Supplier Maintenance Inventory > Inventory Management > System > Location Maintenance Assign form templates to customers, suppliers, and locations from the Forms tab located in the maintenance window in each area. This tab contains the Form Name and Form Template Filename columns. Form Name Field: Form Template Filename Description: This is the form for which you are assigning a template. Designate the template file for the associated form in this field. The forms available for customization differ for customer, supplier, and location. Customer-Specific Forms Quotes/order acknowledgements RMA acknowledgements Packing lists Invoices Statements Supplier-Specific Forms Purchase orders Inventory return packing lists Location-Specific Forms Transfers Transfer packing lists

13 Walkthroughs Pick tickets Production orders Production order pick tickets Printing Custom Forms Once a custom template is assigned, the system looks for that file to produce a form upon request during a transaction; you can generate printed forms as usual, and the resulting pages will use the custom forms

14 Setup Setup The following tasks set up the system specifically for use with the functions described in this chapter. Defining the Script Path for Form Templates Navigation Path: Setup > System Settings > System Setup > Files and Folders To use custom form templates, define the location of the templates in the Script folder in the Files and Folders screen in System Settings. Ensure that the templates are placed in the given folder. Note: The system does NOT verify the location defined in the Script folder contains the selected form templates. Be sure that the necessary custom templates are in place in the specified folder. The system uses standard form selection functionality when custom templates are not found nor assigned