Understanding JD Edwards Translation Tools

Oracle's JD Edwards EnterpriseOne Translation Tools provide these features:

  • Contextual references.

    As you translate the interface, you can view items in context

  • Consistency features.

    You can view previously translated terms to ensure a consistent translation.

  • Automated translations

    When you select an item to translate, JD Edwards Translation Tools searches the database for that item. If it finds a match, JD Edwards Translation Tools automatically displays the translation.

In most translation applications, items appear in context. For example, all items within a task appear together, and the items of a form are displayed the way that they appear in the software so that you can view the context while translating.

During the translation cycle for a new release of JD Edwards EnterpriseOne software, the items to be translated are made available to the translators through the Delta Process. The Delta Process extracts the translatable items from the software, stores these items in a JD Edwards-supported database, and assigns status codes to the items.

When extracting the translatable items from the software, the Delta Process compares the new release of JD Edwards EnterpriseOne software with the previous release to locate the changes, and assigns a status of 20 (Untranslated) to new or changed items.

As you translate using JD Edwards Translation Tools, you update items on a JD Edwards-supported database every time that you click OK.

Important: The system has no lock capability, and two or more translators can access and translate the same item at the same time. The last translation saved is the translation that is reflected in the system. If two or more translators are working on the same system, they should divide their work to ensure that they do not overwrite each other's work.

JD Edwards EnterpriseOne software contains a variety of product lines that relate to different departments within an organization, such as distribution, manufacturing, and human resources. Multiple systems reside within each product line.

You might be assigned to translate the human resources and financial verticals. As you translate different systems, you will notice that, due to the subject of the applications, terms used in one system are not used in others.

Although you can translate the software items in any order, you should translate the software interface in this order:

  1. Glossary entries (using a translation memory such as TRADOS).

  2. Data dictionary items.

  3. Processing options.

  4. Forms.

  5. Reports.

  6. Menus.

  7. Tasks.

  8. User defined codes.

  9. Resource files.

  10. Miscellaneous items.