This chapter contains the following topics:
You might have to translate more than one release at a time if you translated in these situations:
In a prior release and the translations need to be matched in a current release.
In the current release and you want to leverage those translations again.
In the current release and the translations need to be matched in a prior release.
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:
Ensures no disconnect between source and target text.
Provides cost-effective budgeting of language assets.
Provides consistent terminology.
Eliminates production time for matching text.
Accelerates the quality assurance process.
This section provides an overview of matching criteria and discusses how to translate across multiple releases or environments.
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.
|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:
|Audit Trail||In the Primary Update Code Page Environment, the Audit Trail information updates the:
You must be a senior translator to run the Multiple Release Exact Match program (P7903).
To translate across multiple releases or environments:
From the Translation Applications menu (GH791), select Exact Match Quality Assurance, and then Translation Tools.
On the EnterpriseOne Translation Tools form, from the Form menu, select Exact Match.
Complete the criteria in these categories:
You can change languages to submit more than one language.
You can run the process in Preliminary or Final mode.
The system does not update records. It only reports the total number of records.
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.
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.
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).
The compare environment that the system uses to select and update matching records that it finds from the secondary environment.
The compare environment that the system uses to verify the secondary complete status and the source text of the match type.
Code Page Environments
In Final mode, the code page environment from which the system updates the secondary code page environment after a match is found.
Once the match is found the secondary compare environment, the code page data that the system uses to update the primary environment.
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.
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.
In the detail area, select the tables to include in the exact match process.
From the Form menu, select one of these options:
Include all tables in the exact match process.
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:
Include the table in the exact match process.
Exclude the table in the exact match process.
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.