Upgrade analysis
The Upgrade menu answers the first question of a JD Edwards upgrade or update: what has to be retrofitted, and for how many days? Nomajde reads the customer's objects of a path code, compares them with the list of objects Oracle changed in the target release, and gives each object a kind, a retrofit decision, a complexity and a number of days. JD Edwards is only read; the analysis is kept in Nomajde's own database.
At a glance
The two steps
1. Load an object list from Oracle
Upgrade → Load an object list from Oracle takes the Excel file Oracle publishes for a release or an update — columns Object, Version, Description, System Code, Date — and stores it under the name given in Name of the list (UN9). Loading a list again under the same name replaces it. The loaded lists are shown in Upgrade → Oracle's object lists.
Load two lists when the platform already runs an update: the target one (UN9) and the one in place (UN2).
2. Build the analysis
Upgrade → Build the analysis reads JD Edwards and writes the result.
| Parameter | Default | Meaning |
|---|---|---|
| Path code the upgrade starts from | PD920 | The path code whose objects are analysed. |
| Object list to compare with (its name; blank = none) | blank | The target list. Without one, no object is marked as changed by Oracle. |
| Object list the customer already runs | blank | Optional. With it, only what Oracle changed after that list counts. |
| Central objects schema, when not the pool's (PD920) | blank | The schema of the central objects when it differs from the one of the connection. |
The run collects, for the path code: the objects added or changed by the customer in the Object Librarian, the original of each copy, what is really used (object usage tracking and the history of submitted jobs), and the cross reference between the customer's objects. It can be run again at any time: the decisions typed in the grid are kept.
How an object is judged
| Kind | When | Retrofit |
|---|---|---|
| Audit Trail | An audit table of the database audit. | No — complexity Configuration, 0 day. |
| Custom | An object created by the customer, with no JD Edwards original. | No — Retrofit not needed. |
| Copied | A copy of a standard object: its original is found by the application identifier the copy kept. | Yes when Oracle changed the original in the list. |
| Modified | A standard object changed by the customer. | Yes when Oracle changed it in the list. |
An object Oracle did not change is Not updated: nothing to retrofit. For the others, the complexity and the days follow the object type:
| Object type | Complexity | Days |
|---|---|---|
| Applications, reports | Hard | 3 |
| Business functions | Medium | 1 |
| Everything else | Easy | 0.5 |
Objects to retrofit
Upgrade → Objects to retrofit is the working list: one row per customer object of the path code.
| Columns | Content |
|---|---|
| Path code, Object, Description, Object type, System code | The object as the Object Librarian knows it. |
| Kind, Original | The kind above and, for a copy, the standard object it comes from. |
| Retrofit, Complexity, Days | The result of the analysis. |
| Updated by Oracle on | The date of the object — or of its original — in the target list. |
| Last used, Users, Uses | The usage found in JD Edwards: an object nobody uses is a candidate to drop rather than retrofit. |
| Used by, Waiting for | The customer objects that use it, and the objects it uses that are themselves to retrofit: the order of the work. |
| Modified by, Modified on, Release, Analysed at | Who last changed the object, the list compared with, the time of the analysis. |
What is yours
Eight columns are typed by the team and survive every new analysis: Complexity (your choice), Days (your choice), Module, Assigned to, Status, Start, Finish and Note. A complexity of Easy, Medium or Hard typed there replaces the computed one; days typed there replace the computed days of an object to retrofit. Open a row to edit them, or use the grid's bulk edit to assign a selection at once.
The other screens
| Screen | Use |
|---|---|
| What uses what | Which customer object uses which, with the retrofit and the complexity of each: an object waits for the ones it uses. |
| Outside the reference path code | Customer objects found only in another path code — never promoted, to review before the upgrade. |
| Oracle's object lists | The lists loaded: object, version of the object, description, system code, date. |
Summaries
The Data Explorer model Upgrade analysis gives the totals, with four saved analyses: Retrofit by complexity and object type, Days of retrofit by complexity and object type, Days of retrofit by assignee and module, The customer's objects by kind. The Nomajde home page shows the number of objects to retrofit, the days by object type and the objects by complexity.
Access
The screens show to the roles that hold their menu entries; the two jobs to the holders of their job: permission. The connection used to read JD Edwards needs read access to the Object Librarian tables of the central objects.
Tips & best practices
- Load the list already in place as well: without it every object Oracle ever touched counts, and the estimate is too high.
- Filter Retrofit =
Yand sort on Waiting for to plan: the objects that wait for nothing come first. - Look at Last used before estimating: a modified report nobody has run for three years is a decision to take, not three days to plan.
- The days are a first estimate by object type; correct them in Days (your choice) for the objects the team knows.
- The AI assistant knows the procedure: ask it to prepare an upgrade and it runs the two jobs and reads the result with you.
Related
- Jobs — running a job from the Nomajde menu.
- Non-regression tests — check that JD Edwards still behaves the same once the upgrade is done.