This chapter discusses:
Except where noted in the text, the information in this chapter applies to upgrade and cumulative update customers only. You can run any of the merges in two ways:
Proof mode creates merge reports, but does not update control tables. Use proof mode to examine the changes that are reported without updating your tables.
Update mode creates merge reports and updates items in the control tables.
Tip:
Check each merge as it finishes to make sure it completed successfully. Also, save your logs in case you have to troubleshoot problems.See Also
Chapter 24, "Major Technical Tables" for more information on individual tables.
This section describes:
Section 9.1.2, "Working with Language-Specific Table Merges"
Section 9.1.7, "Working with Report Director Templates Merge"
The basic structure of Release 9.1 software consists of control tables. These tables organize and sequence the information you put into the JD Edwards EnterpriseOne systems. In addition, these tables determine the types of operations to be performed on the input data. For example, the data dictionary tables define all specifications for any data item in JD Edwards EnterpriseOne software.
Control tables differ from transaction tables in the following ways:
Control tables contain data that is shared between JD Edwards EnterpriseOne and the customer.
Transaction tables can be converted, but JD Edwards EnterpriseOne data is never merged into them.
A customer can modify control tables, for example, changing a menu to better suit business needs. Because customers can modify the control tables, JD Edwards EnterpriseOne provides a safe mechanism to merge these control tables with the new data that accompanies a new release. This protects the customer-modified information.
In a customer base merge, a JD Edwards EnterpriseOne change table is merged into the customer control tables. Change tables store information related to control table data that has been changed or added into JD Edwards EnterpriseOne since the last release. This information can show detail such as how a menu has changed. The customer base merges look for changes from one base release to the next base release, for example, Release 8.9 to Release 9.1, and update the customer Release 8.9 tables with the new information from Release 9.1.
The upgrade performs these customer base merges:
Data dictionary merges
User-defined code merges
Solution Explorer merges
Favorites merges
Report director templates merges
Tips of the day merges
Workflow merges
For some merges, you can also specify data selection criteria. This feature lets you choose the information to merge into the Release 9.1 control tables. The ability to limit the information merged reduces the total merge time required.
This information is only for users who are installing an alternate language. The distributed language tables consist of control tables, system tables, and data dictionary tables.
The F91100D table must be loaded to display the text from these tables in the desired language
The F98800D and F98810D tables must be loaded to display text from these tables in the desired language.
The F83100 and F83110 tables must be loaded to display soft code text in reports
Note:
This merge is for upgrades and cumulative updates.The Data Dictionary Merge (R989200P) program updates the customer-specific data dictionary tables by using a combination of information from the new Release 9.1 data dictionary tables and the change tables in the planner database. It runs during the Installation Workbench phase.
The Release 9.1 data dictionary tables are stored as follows:
The following pristine data dictionary tables are stored in a relational database.
Changes made to the data dictionary items that will be replicated to other workstations must be made here.
F9200
F9202
F9203
F9207
F9210
F9211
F9212
F00165
Replicated data dictionary items are stored in specification tables on each workstation.
These tables are the .ddb and .xdb versions of the DDDICT and DDTEXT tables that are located in the \Spec directory.
For installations, upgrades, and cumulative updates that include an alternate language, the Data Dictionary Text tables (GT92002, F9202, and F9203) must be loaded to display the text from these files in the desired language. The data dictionary files add the alternate language on top of the installed English records.
Note:
This merge is for upgrades and cumulative updates.The Solution Explorer Merge (R9690002) program updates the customer-specific Solution Explorer tables using a combination of information from the new Solution Explorer tables and the change tables in the planner database. The merge runs when you run the Installation Workbench. The menu tables are F9000, F9001, F9002, F9005, F9006, F9020, F9022, and F9050.
For users installing an alternate language, the Text Alternate Description table (F9002) contains the language records to display Solution Explorer in the desired language. This process adds the desired language on top of the already installed English records.
Note:
This merge is for upgrades and cumulative updates.The User-Defined Codes Merge (R9600042) program updates the customer-specific user defined codes (UDC) tables by using a combination of information from the new UDC tables and the change tables in the planner database. This merge runs when you run the Installation Workbench. The UDC tables are F0004 and F0005.
During the installation process, this merge is used only for users who are installing an alternate language.
For upgrade and cumulative update customers who are installing an alternate language, the User-Defined Codes Merge (R9600042) program merges the language UDC text. When the merge business function is run, any time a UDC Header record in the F0004 table or a UDC Detail record in the F0005 table is added, the corresponding language records are added to your UDC language tables F0004D or F0005D.
A report interconnect to run the language UDC merge is provided with this merge.
Note:
This merge is for upgrades and cumulative updates only.The Favorites Merge (R96911002) program updates the customer-specific favorites table by using a combination of information from the new favorites table and change tables in the planner database. It runs during the Installation Workbench phase. The favorites table is F91100.
Note:
This merge is for upgrades and cumulative updates only.The Report Director Templates Merge (R96914002) program updates the customer-specific report director templates tables using a combination of information from the new report director templates tables and the change tables in the planner database. The merge runs during the Installation Workbench phase. The report director templates tables are F91400, F91410, F91420, and F91430.
Note:
This merge is for upgrades and cumulative updates only.The Tips of the Day Merge (R96915002) program updates the customer-specific tips of the day tables using a combination of information from the new tips of the day tables and change tables in the planner database. The merge runs during the Installation Workbench phase. The tips of the day tables are F91500 and F91510.
Note:
This merge is for cumulative updates only.The Workflow Merge (R98800) program merges the JD Edwards EnterpriseOne workflow data shipped with a new release with the customer workflow data. The merge runs during the Installation Workbench phase.
The following list shows the workflow tables:
F98800
F98800D
F98800T
F98810
F98810D
F98811
F98830
F98840
F98845
Note:
The workflow merge may overwrite your customer-defined data, as follows:If you have modified a JD Edwards EnterpriseOne workflow process, and the new JD Edwards EnterpriseOne workflow process has been changed, the updated new JD Edwards EnterpriseOne workflow process overwrites the customer-modified workflow process.
If the customer has created a new workflow process, and used a name that is the same as the JD Edwards EnterpriseOne workflow process that has been updated, the updated JD Edwards EnterpriseOne workflow process overwrites the customer-created workflow process with the same name.
If any customer-defined processes are in danger of being overwritten, you should copy the existing process and rename it with another version number before performing the merge.
You can check for processes to be overwritten by using proof mode with the merge.
This section discusses:
This table explains what happens to the following types of objects if they have been modified by the customer when the specification merge programs run during an upgrade or a cumulative update. The table assumes the JD Edwards EnterpriseOne action and the customer action are on the same object.
| JD Edwards EnterpriseOne action | Customer action | Upgrade | Update |
|---|---|---|---|
| An object is modified. | No action. | No action. | Add or replace. |
| An object is modified. | The same object is modified. | Merge (replaces data structures and applications). | Merge (replaces data structures and applications). |
| An object is added. | No action. | No action. | Add. |
| No action. | A new object is added. | Add. | No action. |
| No action. | No action. | No action. | No action. |
| No action. | The same object is modified. | Merge. | No action. |
| An object is deleted. | No action. | No action. | The report should contain a warning. Object Librarian should be updated to product code 88. |
| An object is deleted | An object is modified | The report should contain a warning, and the object is merged. | The report should contain a warning and the object is not deleted. |
See Also
Section 25.7, "Object Specification Merge Report (R98700)" in Chapter 25, "Working with Reports" in this guide for more information about the reports.
For users who are upgrading an alternate language, the merge copies all text for custom objects. For modified JD Edwards EnterpriseOne objects, all changed or added text is copied forward to the new release.
For users who are updating an alternate language, the TAM package contains only base text. The merge replaces central objects base text with base text from the package. Translated text is not removed.
Note:
This merge is for upgrades and cumulative updates only.During an upgrade, the Specification Merge (R98700) program carries over any previous release Object Librarian changes you have made, such as added objects and modification flags, and changed category codes, to the new Object Librarian.
During a cumulative update, the Specification Merge (R98700) program adds any Object Librarian changes, such as added objects and changed category codes, to the existing Object Librarian.
Note:
This merge is for upgrades and cumulative updates only.During an upgrade, the Versions List merge (R98700) program preserves any non-XJDE and non-ZJDE (customer versions) version specifications for objects that are valid in the new release and their processing options data. This process also preserves the processing options data of ZJDE and ZJDEC version (customer versions).
During a cumulative update, the Versions List merge preserves any non-XJDE and non-ZJDE (customer versions) version specifications for objects that are valid in the new release. It also preserves their processing options data and adds new XJDE and ZJDE versions. This process also preserves the processing options data of ZJDE and ZJDEC version (customer versions) for objects that are changed.
Note:
This merge is for upgrades and cumulative updates only.Use this information only if you are installing an alternate language.
When you load an alternate language with the installation, you must load language records into the central objects tables to enable that language. The central objects tables contain the alternate language records needed for displaying text in the selected language.
Language-enabled tables include the processing text (F98306), report text (F98760) and form text (F98750). Depending upon the environment choices during the English installation, you may have several sets of central objects, for example, one set for each environment loaded during the English language installation.
This merge is for customers who have an alternate language and are installing a cumulative update release only.
The Update Language Text Merge () program runs automatically during the Specification Table Merge Workbench. This program copies text from the language database to the central objects database. Any language text records that do not exist are added. Records that already exist are updated if the text has changed. Custom text in JD Edwards EnterpriseOne objects is preserved if the merge flags are set correctly in Object Librarian. This process is called automatically from the Specification Table Merge Workbench or run as a standalone option from R98700. If it is run from the workbench, the Language Plan (F_) table is used to merge each language, data source, and environment selected in the plan.