This section discusses these topics:
When upgrading to a new release, you might need to retrofit some of your modifications to the new release. Because it is a laborious process to recreate custom modifications each time you upgrade the software, the upgrade process preserves most of your custom modifications. This chapter explains how to integrate any custom modifications that the upgrade process did not preserve into your new Release 9.1 software. This integration, called retrofitting, enables refitting of your customizations that could not be merged into the new version of the software.
Retrofitting modifications only needs a workstation with the upgraded software and the development tools provided with Release 9.1. These tools compare the customizations that Release 9.1 merged into the new software with any pathcode in the system. Thus, you can easily compare your upgraded modifications with a version of your modifications before the upgrade or with the pristine environment of the new release.
Note:The ability to carry forward the deletion of standard JD Edwards EnterpriseOne text overrides is not a supported custom modification. That is, if a text override is deleted by a customer it is re-deployed with the next ESU or upgrade. The original static text control should be hidden. A new control with the desired text should be added in its place.
To retrofit custom modifications:
From the workstation on which you will retrofit the object modifications, check out the modified objects.
To check out objects, see JD Edwards EnterpriseOne Tools Object Management Workbench for the Web Guide.
Use the ER Compare utility to compare the upgraded version of the object on the client machine to a version of the object as it was before the upgrade.
This tool enables the direct copy of event rules from the original specifications to the upgraded specifications. See the section of the JD Edwards EnterpriseOne Tools Software Updates Guide entitled: JD Edwards EnterpriseOne ER Compare for more information about this procedure.
Use the other design tools described in the JD Edwards EnterpriseOne Development Tools Guides to retrofit other modified components of objects.
Use ER Compare to show the difference in named event rule (NER) business function source codes.
Redo any custom event rules for Do Initialize events because they have been removed from the UBE event list.
When you have tested and retrofitted the modifications, check them back in and rebuild the package.
Test and fix the modifications, and then rebuild and re-deploy the corrected package.
Repeat this step until all the modifications are functioning properly.
The chapter entitled: Using JD Edwards Compare and Merge Tools in the JD Edwards EnterpriseOne Software Updates Guide fully describes all of the tools that have been created to help you compare between releases as well as with environments on the same release.
The following sections in this guide provide a high-level description of the compare and merge tools, including those that have been added since the base release of JD Edwards EnterpriseOne Tools Release 9.1:
The Application Configuration Analyzer is a set of reports which identify differences for processing options, data dictionary (DD) items, and user defined codes (UDCs) between releases or environments. These reports are:
Versions Compare Report
User Defined Codes Compare Report
Data Dictionary Compare Report
If you have made custom modifications to business data, these reports can help you verify that your modifications were carried forward to the new release. You can use these tools anytime you want to compare items between two environments.
If you are on an older release of JD Edwards EnterpriseOne, you need to identify customizations in order to determine the impact and level of effort to retrofit the customizations into the newer release of JD Edwards EnterpriseOne. This utility helps to identify the customizations in order to determine the impact and level of effort to retrofit the customizations into the newer release of JD Edwards EnterpriseOne. A review of this information, prior to performing modifications within the software, will allow for a smoother and more predictable upgrade of the EnterpriseOne software.
The Customization Object Analyzer is comprised of a UBE that loads a table and UBEs that read from that table to create either a summary or detailed report. The UBEs are:
R9840DL (Object Dataload)
This UBE loads the F98881CU table in a parent-child hierarchy of object changes with a list of all JD Edwards EnterpriseOne customized objects.
RD9840RS (Object Customization Summary Report - BI Publisher)
This UBE creates a summary report from the data in the F98881CU table.
RD9840RD (Object Customization Detail Report - BI Publisher)
This UBE creates a detail report from data in the F98881CU table that shows the details of the customizations grouped by various criteria.
R9840R (Object Customization Summary and Detail Report - Standard Version)
This UBE creates a summary and detail report from the data in the F98881CU table.
The section entitled Customization Object Analyzer in the JD Edwards EnterpriseOne Tools Software Updates Guide.
JD Edwards EnterpriseOne Visual Compare for UDC Descriptions and Glossary tool (P96472) enables you to review and apply text updates for Data Dictionary glossaries and UDCs. You can see a side-by-side comparison of the new and old text values, which enables you to choose whether to accept the changes.
The Visual Compare for UDC Descriptions and Glossary Tool, application P96472, is run from an administrative client workstation within JD Edwards EnterpriseOne and applies the changes to the current environment.
The section entitled JD Edwards Visual Compare for UDC Descriptions and Glossary Tool in the JD Edwards EnterpriseOne Tools Software Updates Guide.
The FDA Compare tool in Oracle's JD Edwards EnterpriseOne Form Design Aid (FDA) enables you to compare one version of an application to another. You can compare them on the application level to determine whether forms have been added, deleted, or rearranged and whether the properties have changed. You also can compare the forms in the applications to each other to see whether controls have been added, deleted, or rearranged and whether the properties have changed.
Additionally, you can compare two different applications as well. This feature is useful when you have made a new application by copying an existing one and then modifying it. Then, when you upgrade, you can not only compare the base application to its new counterpart, but also you can compare a custom application.
While working with the target object, you can use all FDA functions except creating new forms. While comparing, you can change the target object to match the source object. If an object exists in the source but not in the target, you can copy it to the target. If an object exists in both but is different in some way, you can merge the specifications from the source to the target to make them identical.
As a software developer, you might use FDA Compare as the final step before checking in the changes to ensure that you made all of the changes you intended to make. In this way, you can also make sure that you did not move a control or make a property change unintentionally.
As an administrator, you might use FDA Compare to see the changes between a software update and the pristine or current implementation. If you have performed a number of customized modifications, you can more carefully implement the software changes without fear of ruining the customization.
The section entitled JD Edwards FDA Compare in the JD Edwards EnterpriseOne Tools Software Updates Guide.
JD Edwards ER Compare provides a detailed, on-screen comparison of event rules. You can change the target object (your local version) within the utility by moving lines directly from the source. You can also remove or disable lines. In addition to providing an on-screen comparison, you can select to print a report detailing the changes as well.
The section entitled JD Edwards ER Compare in the JD Edwards EnterpriseOne Tools Software Updates Guide.