Back to standard
Development → Back to standard answers a question every JD Edwards EnterpriseOne customer meets before an upgrade: of all the standard objects changed over the years, which changes still matter? Each changed object, and each copy of a standard object, costs retrofit days at every upgrade. The page lists them, compares each one with Oracle's own object in the pristine path code (PS920, Oracle's objects as delivered) or in another path code, and sorts them: those that can go back to standard as they are, those that differ, and by what, and those that differ but that nobody runs. JD Edwards is only read.
At a glance
What is compared
The comparison takes, for one path code (PD920 for instance):
- the standard objects it holds as changed — those the Object Librarian flags as changed in that path code;
- the copies of standard objects — an object the customer added that kept the application id of a standard object of the same type. A copy is compared with its original: a copy that adds nothing can be replaced by the standard object, and a copy has to be retrofitted like a changed object when Oracle changes its original.
Each object is compared with the same object — or, for a copy, with its original — in the path code named as reference: usually the pristine one, or any other path code.
Record by record
The comparison reads the specifications of the object in the two path codes and matches them record by record: each record is identified inside the object by a few values (a form and a control, an index and its rank, a section…). Two records with the same identification are the same when their values and their specification are the same. What is compared:
| Object | Records compared |
|---|---|
| Table | Its columns, its indexes and the columns of each index. |
| Business view | Its specification. |
| Data structure | Its specification, named mappings included. |
| Business function | Its functions and their specifications. |
| Application | The application, its forms, the controls of each form, the texts of the forms, the event rules. |
| Report | Its sections and objects, its texts, the event rules — those of the report itself (its versions hold overrides only). |
| Named event rules | Their specification. |
Not compared, and said so on each object: the C source of a business function (its functions and their data structures are compared, not its code), the data dictionary, the processing option texts, a report's versions.
A copy under its original's names
A copy carries names of its own: P550101 for P0101, its forms W550101A for W0101A, a table's own column prefix. Before a copy is compared with its original, these names are put back to the original's — in the identifications, the values and the specifications —, so that a name alone is never a difference. The opened row says so: A copy of P0101, compared with it under the original's names.
The page
The heading names the path code, the path code it was compared with and the date of the comparison. When several path codes were compared, a list next to the buttons switches from one to the other.
| Button | Does |
|---|---|
| Compare a path code / Compare again | Opens the comparison job, with the path code and the reference already filled in. Compare a path code before the first comparison, Compare again after. Shows only to those who may run the job. |
| Read again | Reads the list again — after a comparison, for instance. |
Before the first comparison, the page says so: the comparison reads every standard object the path code holds as changed and compares it with the path code named, read-only, in a few minutes.
The figures
| Figure | Counts |
|---|---|
| identical to the standard | The objects every record of which is the same as the standard's: can go back as they are — or, when the upgrade analysis exists for the path code, the days of retrofit they save at each upgrade. |
| differ and nobody runs them | The applications and reports that differ and that no user ran, with the days they save. A dash, with the usage is not known for this path code, when the upgrade analysis has no usage for it. |
| differ | The objects with at least one record added, removed or changed. |
| not in the path code compared with | The objects the reference path code holds no specification of: nothing to compare them with. |
The five views
Five cards above the list choose what it shows, each with its count. The view chosen is kept for the next visit.
| View | Shows |
|---|---|
| Can go back as they are | The objects identical to the standard: only the "changed" flag is left. |
| Changed, never run | The applications and reports that differ and that no user ran — a change that serves nobody. Empty when the usage is not known. |
| Differ | What was changed, record by record. |
| Not in the standard | The objects with nothing to compare with — absent from the reference path code, or without a specification in either. |
| All | Every object compared. |
The list
| Column | Content |
|---|---|
| Object | The object's name. |
| Copy of | For a copy, its original. |
| What it is | The object's description. |
| Type | Its type (APPL, UBE, TBLE, BSFN…). |
| Compared with the standard | Identical, Differs with its counts (+ added, − removed, ~ changed), Not in the standard or No specification. |
| Where it differs | The kinds of records that differ, with their number: Form controls (5), Event rules (2). |
| OMW project | The OMW projects that hold the object, with their description — why it was changed, when the project says it. A user's default project is left out when the object sits in another one. |
| Last run, Users | Its last use and its users, from the upgrade analysis. |
| Retrofit days | The days of retrofit the upgrade analysis gives it, when it is to retrofit. |
The list has the usual search, filters, grouping and columns, and exports to Excel.
What differs, and by what
Opening a row compares the object now, in the two path codes, and shows what was found:
- the verdict in one line: how many records were added, removed and changed, how many are the same, the schemas read and the OMW project that holds it;
- for an identical object, that the standard object can be taken back — or, for a copy, that it adds nothing to its original and that the standard object can be used in its place;
- one block per kind of record that differs — Table columns, Indexes, Index columns, Business view, Data structure, Named mappings, Functions, Application, Forms, Form controls, Form texts, Report sections and objects, Report texts, Event rules, Named event rules — with:
- Added by you: the records only the path code examined holds;
- Removed by you — in the standard only: the records only the reference holds;
- Changed: each record identified in words (form W4210A · control 12 · event 13), its values as standard → yours, and, when its specification differs, the lines that differ — removed in red, added in green.
A long list is cut and the rest counted (… and 12 more); a long difference stops after 120 lines (… and 40 more line(s)).
The comparison job
The job Compare with the standard (nomajde-standard-compare, menu Jobs) makes the comparison of one path code and keeps the verdict of every object; what the page lists is what the last run kept. Comparing a path code again replaces what it held. It takes a few minutes — 350 objects in under a minute on a demonstration system.
| Parameter | Default | Meaning |
|---|---|---|
| Path code to examine | PD920 | The path code whose changed objects and copies are compared. |
| Path code to compare with | PS920 | The reference: PS920 for Oracle's objects as delivered, or another path code. |
The job is read-only on JD Edwards: it reads the specifications of the two path codes, runs no Oracle batch and adds nothing to JD Edwards. A path code cannot be compared with itself. It has no schedule: run it before an upgrade, or after a clean-up, to see where things stand.
Opening a row does not need the job again: the comparison of that object is made on the spot.
Access
The page is in the Development folder of the Nomajde menu. The predefined roles Developer and Administrator hold it, and may run the comparison job (see Predefined roles). The buttons that open the job show only to those who may run it. The connection used to read JD Edwards needs read access to the Object Librarian, the central objects of the two path codes and the OMW tables.
Tips & best practices
- Start with Can go back as they are: each line is an object to take back from the standard at no cost, and the retrofit days it saves at every upgrade.
- Run the upgrade analysis of the same path code first: the last use, the users and the retrofit days come from it, and so does the Changed, never run view.
- Read the OMW project before deciding: its description often says why the object was changed, and who to ask.
- The reference need not be the pristine path code: the job accepts any path code to compare with.
- A difference made only of a copy's own names is not shown: what remains after the names are put back is a real change.
Related
- Prepare for upgrade — what a release makes you retrofit, and how the original of a copy is found.
- Object Management Workbench — the OMW projects, their objects and their log.
- Cross Reference — where an object is used before taking it back.
- Jobs — the comparison job in the Jobs folder.