FAQs about ESUs

A1 What is an ESU?

An ESU is a downloadable package addressing issues reported in a specific SAR. The package is delivered in a self-extracting executable and must be merged into the appropriate OneWorld environment. The ESU merge process is similar to the one run during an upgrade or update (although very short in comparison), and requires the use of the deployment server. When an ESU is installed the objects included in that ESU will be merged into the environment into which it is installed. The Spec Merge report, R98700, is run and takes the changed code and merges the information into a path code on the deployment server. The specification merge report will print out replaced and changed objects. The SAR updates have now been applied to the path code on the deployment server. The final step is to create a package and deploy the package to the workstations. You should test the ESU before you deploy to your production environment; also, be aware that if you have custom code you will need to retrofit it. Therefore, you will want to manage your software and the frequency of ESUs that you download and deploy.

A2 How is it installed?

First, the appropriate ESU is found by using either the SAR Search capability on the Knowledge Garden, or the Update Center. If you need to use a search to find a solution to a specific problem, begin with SAR search. If you already know the ESU number or SAR number that you are interested in, or want to see a listing of all ESUs completed after a specific date, you should begin with the Update Center. If you start with SAR search and find a SAR that addresses your problem, click on the SAR number in the search Results List. This will lead you to detailed information about that SAR. Click again on “Show/Hide Detailed Document Information” and you will find additional SAR detail. If an ESU exists for this SAR, you will see the ESU number.exe in the Code Change field. Click on this and it will take you to the Update Center where you will be able to download the ESU using the Download Manager.

If you see the following symbol by the ESU number be sure to click on this icon and read the text behind it. J.D. Edwards uses this symbol to alert you that there is additional information available about this ESU.

If you decide that you want to download the ESU, click the box to the left of the ESU number and then click "Add to Downloads". This will load the ESU in your Download Manager. If this is the first time you have downloaded using the Update Center you will be prompted to download a JAVA applet that is necessary for the Download Manager to work. Be certain that your correct email address to notify you in the event that we discover a problem with a software update that you have downloaded. It is only used in this event.

A3 When I search on the SAR I need in the Knowledge Garden, I find that the ESU number has changed. Why is this?

ESUs are designed to be cumulative and can include of a number of SARs (individual fixes of problems) that all affect the same object.. This means that when a new fix is made for a SAR that affects an object in a particular ESU, the SAR will be added to that ESU and the change of that SAR will be integrated in the affected object of the ESU. This update is done once a week. Every time such an update is made (and the objects in an ESU have changed due to newly added SARs), the ESU gets a new number. A new next number is retrieved from our next numbering system to indicate that this is a newly updated ESU. All the SARs that are included in the ESU will then point to the new ESU number. This rollup method allows for clients to pull only one ESU, rather than multiple ESUs each time a fix is issued.

Example:

SAR 4465796 affects object P4210 and points to ESU JD13468. A new SAR 5742345 is fixed and also affects object P4210. The SAR will then be included in JD13468. The day that the JD13468 gets updated with the new changes from SAR 5742345, it is assigned a new ESU number, for example JD13858. From then on, SAR 4465796 and SAR 5742345 point to JD13858 until it gets updated again.

The new ESU number can be found in the Update Center (Support/Update Center/Search) by two methods:

1. Enter the original ESU number (e.g. JD13468) and do an ESU search. The following Superseded message (yellow triangle with an exclamation mark) will display with the new ESU number. Click OK and the new ESU will display.

2. Enter a SAR number that was included in the original ESU (e.g. 4465796) and search on ESU. This will display the new ESU number.

If the new ESU number is not yet available, the Alert symbol (white triangle, lined in red, with an exclamation mark) will display when doing the above searches. The Alert symbol will also display if there is something important to note about the ESU. When clicking on the Alert symbol, a message will display with information regarding the ESU.

A4 What are the most important things I need to do to insure success with ESUs?

Make sure that you have a complete, current backup of your environment. Make sure you have read and understood all of the documentation associated with ESUs. This includes the documents included in the Tech Best Practices under Support/Knowledge/Tech Best Practices, in addition to the installation documentation. Also, be sure that you are keeping accurate track of which ESUs you have applied (for support purposes) and the nature of any custom modifications in your environment.

A5 What is included in the “Objects/SARS/Special Instructions”?

This is an .htm document specific to the individual ESU. It includes a list of all SARs included in this ESU, a list of objects included, and, if needed, a list of any special instructions. Also please see question A7 below regarding the cumulative nature of ESUs. In addition, the .htm is included in the ESU that is downloaded.

A6 How can I find the ESU I need?

You have two search methods available to you on the Knowledge Garden from the Support site. The Support site can be accessed by clicking on the Support icon at the top of the Knowledge Garden or the Support blue navigational bar.

The first method is to click on the SARs navigational bar (blue bar). This will bring you to detailed instructions on how to use the SAR search as well as a link to the search form. The SAR search enables you to search for a SAR using a key word for the problem in question or entering a specific SAR number. You can also click the Search drop down menu then, click the SAR orange bar. This will bring you directly to the SAR search form. When you find the SAR that addresses the problem, open the SAR then click on the “show detailed information” link. If the SAR is at a status 01 and an ESU has been completed for the SAR, the ESU number and the link to the ESU will appear on the Code Change line. The ESU link brings you to the Update Center where you can download the ESU.

The second method is to click on the Update Center navigational bar. This method requires that you know either the SAR number of the ESU number specific to your issue. Click the Search link at the top right corner. This will bring you to the Update Center Search form where you can filter your search by release, priority of SAR, system code, SAR number, ESU number, etc.

A7 If I have more than one problem for a particular program, how will I know in what order to install the ESUs?

ESUs are cumulative. As new ones are built, the previous ones become obsolete, and the earlier SARs will always point to the latest cumulative ESU.

A8 What skill set is needed at the client site to successfully apply an ESU?

Answer:

The skills needed to apply an ESU are OneWorld Modifications and Deployment. You will also need detailed knowledge of the custom modifications that have been done.

A9 What will Global Support Services need to know if you call?

The first thing a Global Support Services consultant will try to do is to discover whether you are having a problem with the install and deployment itself, or if the problem is related to the Application. They will request the following reports in order to determine if your ESU installation was successful.

R98700 Spec Merge

R9621 Client Package Build

R9622 Server Package Build

Builderror.txt file and the Buildlog.txt

These reports can be gathered using the Support Assistant Technical profile "Applied ASUs/ESUs Report".

If the problem is determined to be with the install, you will be directed to the Customer Support install group for help.

If the problem is not with the install itself, the Customer Support consultant will try to determine the details of the problem you are having. They may ask for print screens of the problem, values of processing options, logs, etc. They will need to know which ESUs have been applied, and the SARs included in the ".htm" document on your system. Support Assistant is an excellent tool in providing this information to the consultant. Support Assistant

A10 Where can I find more information and troubleshooting tips for ESUs?

The Software Delivery site on the Knowledge Garden, under Support/Software/Software Delivery, provides up-to-date information about ESUs and links to the Update Center and SAR search. The site includes Headline News and any announcements made to customers regarding ESUs and their availability. In addition, information regarding ASUs and Service Packs are also listed. Information regarding ESU Installation Troubleshooting can be found under OneWorld/ESUs.

Prerequisite ESUs

B1: What is a prerequisite ESU?

Prerequisite ESUs were created as a result of customer feedback regarding the ESU process, and are for the B7332 release only. As the number of objects and SARs began to grow within an ESU, it became necessary to stop this process by creating a prerequisite ESU. Prerequisites are required to be installed in order to obtain any future fixes for the programs/objects that are included in the prerequisite ESU. Future fixes are then much smaller and contain fewer objects, making them less time consuming to install and test.

The first prerequisite ESU was released in May, 2000 and was number 4116422 (Prerequisite ESU’s do not being with the JD prefix).

In November, 2000, three additional prerequisite ESUs were released for B7332. They were ESU 4364899 for Payroll/HRM, ESU 4605023 for Financials and Distribution, and ESU 4605031 for Manufacturing. The prerequisite ESU 4116422 from May must be installed before installing any of these November Prerequisite ESUs.

It is important to note prerequisite ESUs do not include all J.D. Edwards objects as a new release would, but rather only those in the objects list for the particular prerequisite ESU in question. To see a list of the objects and SAR’s for these ESUs, please refer to the Objects/SARs and Special Instructions for the appropriate prerequisite ESU number (4116422, 4364899, 4605023 or 4605031) on the Knowledge Garden®.

Update ASUs for OneWorld Xe

C1 What is an Update to OneWorld Xe?

Updates to OneWorld Xe provide a mechanism in which clients can obtain all Xe ESUs since Xe was released in September, 2000. JD Edwards has released 6 cumulative Updates as of June 2002. Updates are NOT mandatory. The Updates and their dates are listed below.

OneWorld Xe, Update 1: September 2000 through January 30, 2001

OneWorld Xe, Update 2: September 2000 through April 10, 2001

OneWorld Xe, Update 3: September 2000 through July 10, 2001

OneWorld Xe, Update 4: September 2000 through October 16, 2001

OneWorld Xe, Update 5: September 2000 through January 22, 2002

OneWorld Xe, Update 6: September 2000 through April 16, 2002

It is important to know that when a new update becomes available the previous ones are expired.

C2 Where can I find a list of SARs and Objects included in the Updates?

The Headline News section of the Software Delivery site on the Knowledge Garden contains a current list of SARs and objects included in the Updates. For example, OneWorld Xe, Update 6 is cumulative and includes all SARs that were in OneWorld, Xe Update 1 plus additional SARs that were added for OneWorld Xe, Update 6. This spreadsheet includes a column entitled "Update". If you want to see only the SARs included in OneWorld Xe, Update 6 that were not included in OneWorld Xe, Update 1, please filter on "Update 6".

C3 Do I need to install Update 1 before Update 2, 3, or 4?

No. Updates are cumulative. Update 6 includes all changes from Updates 1 through 5.

C4 Will there be any Updates for B7332?

No. We will not be providing Updates for B7332.

C5 What ESUs were included in the Updates?

ESU numbers are constantly changing as any additional fixes are added. By using the spreadsheets referenced in C2, client's can determine what was included in the Update by SAR and/or Object.

C6 How can I find out what ESUs are available since the cut-off of Update 4?

The Update Center can be used to search on ESUs by a particular date. For Update 4, you can search on all Xe ESUs after 10/17/01 in the filter criteria. This will give you a list as to what is available for download.