Skip Headers
JD Edwards EnterpriseOne Tools Translation Tools Guide
Release 8.98 Update 4

Part Number E14722-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

11 Translating Across Multiple Releases or Environments

This chapter contains the following topics:

11.1 Understanding Translation for Multiple Releases

You might have to translate more than one release at a time if you translated in these situations:

The Multiple Release Exact Match program (P7903) uses source text to locate target text with the same text strings. Using the Multiple Release Exact Match program across multiple releases or environments has these benefits:

11.2 Matching Criteria for Updates and Audits in the Multiple Release Exact Match Program (P7903)

This section provides an overview of matching criteria and discusses how to translate across multiple releases or environments.

11.2.1 Understanding Matching Criteria

The Multiple Release Exact Match program (P7903) requires specific matching criteria to update status, audit trail, and target translations. This table documents those criteria and what the program does when it finds or does not find the specified criteria. The table also lists which source and target translation items it uses when matching them for updates and for creating audit trails.

Criteria Program Response
Reports and Forms (Data Dictionary Verification and Status Update) Data Dictionary Verification

The program verifies the source data dictionary items against the Data Field Display Text table (F9202) translations to ensure that a data item name exists but no text overrides exist.

Data Dictionary Status Update

If the program finds a data item name and no text override, it updates the data dictionary status to 15 (DD Default) when you run the Multiple Release Exact Match program in final mode.

Source If the program detects blank source items, the status of the item is updated to Skip (30) when you run the Multiple Release Exact Match program in final mode.
Primary Source Text The program always matches the primary source text against the text in the secondary search environment.
Primary Source and Status The primary source text and status must exist, and the program always verifies against the primary target.
Secondary Source The secondary source, status, and target must exist for an exact match.
Status Verification The Multiple Release Exact Match program verifies whether the:
  • Primary pate translated is a null (does not exist) date.

  • Secondary date translated is greater than or equal to the primary date translated.

  • Primary target is null (does not exist) or blank.

  • Secondary complete status is equal to the secondary search complete status.

Audit Trail In the Primary Update Code Page Environment, the Audit Trail information updates the:
  • Last translator to XTRANS (use XTRANS with Search/Replace & Review Approved).

  • Date translated to secondary last date translated.

  • User, PID, job, date, and time to the current audit information.

  • Primary Selection Status (20) to Primary Update Status (36)


11.2.2 Translating Across Multiple Releases or Environments

You must be a senior translator to run the Multiple Release Exact Match program (P7903).

To translate across multiple releases or environments:

  1. From the Translation Applications menu (GH791), select Exact Match Quality Assurance, and then Translation Tools.

  2. On the EnterpriseOne Translation Tools form, from the Form menu, select Exact Match.

  3. Complete the criteria in these categories:

    • Language

      You can change languages to submit more than one language.

    • Mode

      You can run the process in Preliminary or Final mode.

    • Preliminary

      The system does not update records. It only reports the total number of records.

    • Final

      The system updates records to the primary compare and code page environments.

      Note:

      You should run the Exact Match process in Preliminary mode first. Preliminary mode enables you to verify the record totals.
    • Selection Filter

    • Primary Product Code

      You use the primary product code in conjunction with the status selection in the primary compare environment to define a record set.

      Note:

      You should repeat the process for each individual product code. If you do not enter a value in the Primary Product Code field, the system searches all product codes for matching records.
    • Status

    • Primary Selection Status

      The record status that the system selects from primary environment. This value is typically 20 (Untranslated).

    • Secondary Complete Status

      The record status that the system matches against the selection status in the secondary environment. This value is typically 11 (Complete).

    • Primary Update Status

      The record status that the system uses to update records in the primary environment. This value is typically 36 (Exact Match).

    • Primary Skip Status

      The record status that the system uses to update blank records in the primary environment. This value is typically 30 (Skip).

    • Compare Environments

    • Primary Update

      The compare environment that the system uses to select and update matching records that it finds from the secondary environment.

    • Secondary Search

      The compare environment that the system uses to verify the secondary complete status and the source text of the match type.

    • Code Page Environments

    • Primary Update

      In Final mode, the code page environment from which the system updates the secondary code page environment after a match is found.

    • Secondary Search

      Once the match is found the secondary compare environment, the code page data that the system uses to update the primary environment.

    • Match Type

    • None

      No match is required.

    • Source and Key

      The source and the primary key of each table must match.

    • Source and Product Code

      The source term and product code must match.

    • Source

      Same term (Default) must match but in any product code. It does not have to be the product code that you specified in the Primary Product Code field.

  4. In the detail area, select the tables to include in the exact match process.

    From the Form menu, select one of these options:

    • Yes

      Include all tables in the exact match process.

    • No

      Exclude all tables from the exact match process. This selection clears all tables from the process so that you can select only those that you want.

      Alternatively, you can include or exclude tables from the exact match process by double-clicking a cell in the Include column and typing one of these values:

    • 1

      Include the table in the exact match process.

    • 0

      Exclude the table in the exact match process.

  5. From the Form menu, select Submit.

    Alternatively, you can click the Submit button on the header of the form.

    Clicking Submit runs the Multiple Release Exact Match batch process (R79850) and produces a report.

After you run the Exact Match process in Final mode, you should review and approve the results.