This chapter contains the following topics:
To update JD Edwards EnterpriseOne successfully, complete the following checklist before starting the update process:
Complete a thorough Impact Analysis to consider the benefits and costs of applying each update.
Prepare the prototype environment.
Prepare the development environment.
Check modification and merge flags.
Backup critical data.
Verify custom changes in master control tables.
Before you deploy any update, complete a thorough analysis of the benefits and costs associated with each update. Not all updates are relevant to your business or to the way you conduct your business. Careful planning at this stage is critical to the success of applying an update. It is recommended that you perform the impact analysis in two phases:
Perform a rough cut by reviewing SARs associated with the update. This review will help you determine if the update is relevant to your needs.
If you determine that an update is relevant, download and install it to your deployment server. Use the Impact Analysis tool to conduct a thorough review, or apply and run the update in the Pristine environment (PS900).
The Impact Analysis tool provided with JD Edwards EnterpriseOne helps perform an impact analysis. A key feature of this tool is a list of the objects in the update that you have modified. You must reapply the modifications using the JD Edwards ER Compare tool.
This section discusses the considerations that are important if your business requires custom modifications. An update does not change or delete any new JD Edwards EnterpriseOne object you create. However, if you modify a standard JD Edwards EnterpriseOne object or interface to an object, there may be an impact to your modifications when applying an update.
These rules describe which of your modifications the update process preserves and which modifications the update replaces.
"Preserve" means that during an update you do not lose your custom modifications when the software you currently have installed automatically merges them with the new JD Edwards EnterpriseOne applications shipped with the update. If there is a direct conflict between your specifications and JD Edwards EnterpriseOne specifications, the update process uses your specifications. When there is no direct conflict between the two, the update process merges the two specifications.
"Replace" means the update replaces your modifications and does not merge them into the update. You will need to redo your custom modifications after the update completes.
Note:
If possible, transfer all modifications to one path code. Do this only if you have tested and approved all modifications or if you have modifications only in development. Having only one environment to update significantly shortens the process.To ensure an accurate and predictable update, follow these rules as you modify your JD Edwards EnterpriseOne objects.
Do not delete controls, grid columns, or hyperitems on existing JD Edwards EnterpriseOne applications; instead, hide or disable them. The updates might use these items for calculations or as variables, and deleting them might disable major functionality.
The update process replaces the current application that resides in your Central Object database. Use Oracle's JD Edwards ER Compare to restore custom changes. This set of tools helps you restore custom changes to:
New hyperitems.
New controls and their event rules.
New grid columns.
Any style changes, such as fonts and colors.
Any code-generator overrides.
Data dictionary overrides.
Location and size changes for controls.
Sequence changes for tabs or columns.
An update replaces custom forms on existing JD Edwards EnterpriseOne applications.
These rules apply to report specifications that were created using Report Design.
An update preserves these changes:
New reports.
New objects to existing reports, including:
Constants.
Alpha variables.
Numeric variables.
Data variables.
Runtime variables.
Database variables.
Dictionary variables.
Any style changes, such as fonts and colors.
Location and size changes for objects.
Data dictionary overrides.
An update replaces custom sections on existing reports.
An update preserves overrides done in Oracle's JD Edwards EnterpriseOne Form Design Aid (FDA), Report Design, or Interactive or Batch Vocabulary Overrides.
An update merges your table specifications from one release level to the next.
An update preserves these changes:
New tables
New indexes
An update replaces columns added or removed from existing JD Edwards EnterpriseOne tables. This includes changing field length, field type, and decimal position.
Instead of adding a new column to an existing JD Edwards EnterpriseOne table, use Oracle's JD Edwards EnterpriseOne Table Design Aid to create a second table that has the same key as the first table and add your modifications to the new table. Use system codes 55 -59. For custom tag files, be aware of data item changes in the JD Edwards EnterpriseOne data dictionary. From one release to the next, JD Edwards EnterpriseOne might change certain data item attributes, such as data item size, which can affect data integrity and how data is stored in the database.
For this reason, you might need to use Oracle's JD Edwards EnterpriseOne Table Conversion tool to convert the tag file data to the new release level. For base tables, the update process takes care of the data dictionary changes by upgrading the JD Edwards EnterpriseOne database to the new release level.
An update preserves custom indices over the custom tag files.
See JD Edwards EnterpriseOne Tools Development Tools: Data Access Tools Guide.
An update merges your control tables during an update using the Change Table process, a delta between the base product and the update, as the basis to do the data merge.
An update preserves these changes:
Data dictionary custom changes, such as changes to row, column, and glossary text. The update process uses your data dictionary as the base. If there is a conflict with JD Edwards EnterpriseOne data items, your changes override them.
User-defined codes. The update process merges any new hard-coded JD Edwards EnterpriseOne values. (Values owned by JD Edwards EnterpriseOne are system 90 and higher, and H90 and higher.) The process also reports any JD Edwards EnterpriseOne hard-coded values that conflict with your custom values.
Oracle's JD Edwards EnterpriseOne Workflow. The update process merges any JD Edwards EnterpriseOne additions, updates, or deleted workflow processes in your data. If there is a conflict with your workflow processes, JD Edwards EnterpriseOne overrides them.
Do not remove columns from existing business views. Changing business views that applications use can cause unpredictable results when you run the application. If you need to hide columns, do so at the application design level using either FDA or Report Design. Performance is not greatly improved by deleting a few columns from a business view.
An update preserves these changes:
New custom business views.
New columns, joins, or indices to the existing business views.
An update replaces columns that you have removed from JD Edwards EnterpriseOne business views.
An update replaces all modifications that you have made to applications, including custom event rules. Use FDA and ER Compare to restore your customizations after an update.
An update replaces modifications that you have made to JD Edwards event logic in reports, tables, and Named Event Rules (NER).
An update preserves new, custom logic that you have added to reports, tables, and NER on events with no previous or current JD Edwards logic.
An update preserves all of these custom data structures:
Forms
Processing options
Reports
Business functions
Generic text
An update replaces these custom modifications to JD Edwards EnterpriseOne data structures:
Forms
Processing options
Reports
Business functions
Generic text
This section discusses how to:
Prepare the prototype environment.
Prepare the development environment.
Check the modification and merge flags.
Verify custom changes in master control tables.
Back up servers and databases.
Prepare the localization update.
This table lists the requirements for preparing the prototype environment.
| Task | Details |
|---|---|
| Personnel | Installer or system administrator |
| Logon status | On the deployment server, in the deployment environment, logged on as user JDE with the database password for user JDE. |
| Prerequisites | None |
| Concurrent Tasks | None |
To make sure you retain all modifications from the base prototype environment, complete these tasks:
Transfer all tested and approved modifications to the base prototype path code.
After the transfer finishes, build a prototype package.
Deploy the prototype package to workstations you want to run at the base release.
Verify the Central Object Database is large enough to accommodate the update.
This table lists the requirements to prepare the development environment.
| Task | Details |
|---|---|
| Personnel | Installer or system administrator |
| Logon status | On the deployment server, in the development environment, logged on as user JDE with the database password for user JDE. |
| Prerequisites | None |
| Concurrent Tasks | None |
To make sure you retain all modifications from the base development environment, complete these tasks:
Make sure that all work in progress is checked into the development path code. From a development workstation, use the Promotion Manager or your own query or report to verify that objects are not checked out.
Build the development package in preparation for deployment to one or more workstations.
Deploy the development package to one or more workstations. You will use these workstations later to help verify that all modifications were carried forward to the new release.
While you update, you cannot make any modifications (except changes to custom business functions written in C language) to carry forward to the next release.
Verify the Central Object Database is large enough to accommodate the update.
This task ensures that your modifications are carried forward to the new release. Before you update, perform these steps to review or set the modification flags on the Object Librarian records for all modified objects.
Do not run the Specification merges until you check the flags for all path codes containing modified objects.
This table lists the requirements for checking modification and merge flags.
| Task | Details |
|---|---|
| Personnel | Installer or system administrator |
| Logon status | On a workstation that accesses Object Librarian tables, or from the deployment server, in the deployment environment. |
| Prerequisites | Make sure you have prepared your environments for the update. |
| Concurrent Tasks | None |
Log onto a workstation or to the deployment environment on the deployment server.
From the Advanced Operations (GH9611) menu, select Specification Merge Selection (P98401).
On Specification Merge Selection, complete these fields:
Location
Type the name of the deployment server that contains the central objects specifications.
Path Code
Type the name of the associated path code (prototype or development).
On the QBE line, type C in the Mod Flag field to list the changed objects, then click Find.
For each object that appears in the grid, verify that the Mod Flag field is set to C, and the Mrg Opt field is set to 1 (merge), which ensures that the modifications are merged when the specification merges run during the update workbenches.
Do not set the Mrg Opt field to 1 unless you want objects merged or saved.
When you finish reviewing or modifying the records, click Close.
To verify the accuracy of modifications, some additional queries are strongly recommended to avoid missing any modified objects. For example, SY = 55 - 59.
Note:
You can also print Oracle's JD Edwards EnterpriseOne Object Librarian Modifications Report (R9840D), which lists all added and modified objects. After the update finishes, review this report to verify whether the object modifications were carried forward to the new release. For more information about the JD Edwards EnterpriseOne Object Librarian Modifications report, see Reports in the Installation Reference Guide.This table lists the requirements to verify custom changes in master control tables:
| Task | Details |
|---|---|
| Personnel | Installer or database administrator |
| Logon status | On the workstation, for each applicable environment, logged on as user JDE with the database password for user JDE. |
| Prerequisites | None |
| Concurrent Tasks | None |
Verify that these master control tables for the data dictionary reside in a relational database accessed by the Data Dictionary data source:
F9200
F9202
F9203
F9207
F9210
F9211
F9212
F00165 (GT92002)
Verify that these master control tables for Solution Explorer tasks reside in a relational database accessed by the Control Tables - Production data source (for production) or Control Tables - CRP (for prototype environments) or Control Tables - Test (for the development environment):
Verify that these master control tables for user-defined codes reside in a relational database accessed by the Control Tables - Production data source (for production) or Control Tables - CRP (for prototype environments) or Control Tables - Test (for the development environment).
F0004
F0005
Verify that these master control tables for workflow reside in a relational database accessed by the Control Tables - Production data source (for production) or Control Tables - CRP (for prototype environments) or Control Tables - Test (for the development environment).
F98800
F98800D
F98800T
F98810
F98810D
F98811
F98830
F98840
F98845
Verify that the media objects queue paths are configured correctly.
Use P98MOQUE from the deployment server in both the JDEPLAN and DEPSRV environments.
Before beginning the software update, back up the entire deployment server, the enterprise server (the complete directory structure for the base installation), and the Oracle or SQL Server databases.
If you are a Localization customer, you must complete all the tasks in Appendix A: Setting Up Localizations. These tasks describe how to set up the software to automatically handle all future updates to the localization that are installed by ESUs.