Cross Reference
Cross Reference, right under Data Explorer in the Nomajde menu, answers the two questions every JD Edwards change starts with: what is in this object, and where is it used. One search box finds an application, a report, a data item, a business view, a table, a data structure, a business function or a user defined object; the page then opens on what the object holds, and a click on Where used switches to the other question.
The page reads the cross reference collected from the JD Edwards EnterpriseOne specifications — forms, report sections, event rules, views, tables, data structures, business functions, user defined objects — and the object usage kept over time. It is read-only: nothing is written to JD Edwards.
At a glance
Search
Type part of a name, an identifier or a description; the examples under the search box start one in a click: P01012, P4210, R42565, AN8, V0101E, F0101, F4211, D0100033, B4200310, F4211FSBeginDoc, address number, sales order. The results are grouped by kind — Applications, Reports, Data items, Business views, Tables, Data structures, Business functions, User defined objects — each line with its description from the Object Librarian. A click opens the object on the right.
The closest match comes first: an identifier typed exactly, then — for the applications and the reports — the object whose title is exactly what was typed, before those whose title only starts with it. Typing address book opens on P01012 Address Book, ahead of the twenty applications whose title begins with those words.
A user defined object is found by any part of its identifier, its name or its description; its line says its type and the application, form and version it sits on.
List a whole kind
The chips under the search box — Everything, Applications, Reports, Views, Tables, Data structures, Functions, UDOs — list every object of that kind in the left column, sorted by identifier, with the total: the first 300, then a line says how many there are. With a kind chosen, the search box becomes Narrow the list…: what is typed narrows that kind only — the identifiers that start with it, the titles that contain it. Everything returns to the search over all kinds. A UDO line shows its name, its identifier and its type.
What is in it
| Object | Opens on |
|---|---|
| Application | Its forms as cards: identifier, title, business view, counts of fields, grid columns, buttons and exits, UDOs. A form the application calls from outside is tagged entry point. A form's tabs: Fields, Grid columns, Buttons and exits, Everything, Event rules, Interconnection (the data items a caller hands it) and UDOs (the user defined objects that sit on it, the service requests that run it, the pages and links that open it). |
| Report | Its sections as cards (kind, business view, counts), and in a section its Fields, Labels, Data selection, Data sequencing — in their rank, ascending or descending —, Everything and Event rules. |
| Business view | The tables it reads (the primary one first), its columns, its Joins — which two tables, the join type, the columns they are joined on. |
| Table | Who uses it, then its Columns (data item and SQL name, in order), its Indexes (primary, unique, their columns) and its Triggers. |
| Data structure | Its items in their order, and the business functions that take it. |
| Business function object | Its functions, each with its data structure and its module; Where called lists the objects whose event rules call a function, and where in each. |
| User defined object | What it is — type, system code, owner, status, who changed it and when — and the objects it uses, each line with How it uses it and Where in the page: see User defined objects. The Objects that carry it list the pages, orchestrations or other UDOs that hold this one. |
A control the form gives no text to shows the data dictionary's title in grey: it is what JD Edwards displays. The Event rules tab lists what the rules of a form, a section or a function do — the business functions they call, the tables and views they read and write with the operations, the forms they open, the reports they run.
Every list is a grid of its own: search, filters, grouping, columns and export.
User defined objects
A user defined object opens on what it names, and each line leads on — to the application (on its form), the report, the table, the view, the data item or the other UDO.
| UDO type | What it uses |
|---|---|
| Composite page | The applications and reports its tiles open, the forms shown in its panes, the task of a task tile, the menu of a landing page, the watchlists, queries, personal forms and other pages it carries — each with where in the page. |
| E1 page | The applications and reports its code calls or names — for a page built with HTML and JavaScript as for a classic one. |
| Orchestration | Its steps — service requests, rules, cross references, white lists, other orchestrations, notifications — and its schedule. |
| Service request | The forms it runs (application, form, version), the tables and views its data requests read, the reports it launches, the orchestration a connector calls, the form a message links to. |
| Notification | Its orchestration, rule, watchlist and schedule, and the forms its links open. |
| CafeOne layout, One View report | The forms it shows, the forms its links open. |
| Search, Process | What it reads and the forms it opens; what a process depends on and the table it reads. |
| Form extension | The columns it adds: the data item and its table. |
| Watchlist | Its query. |
| Query, Grid format, Personal form | The application, form and version it sits on. |
A rule, a cross reference, a white list, a schedule and an image name no object, and the page says so; a logic extension is not read. When the content of a type has not been collected yet, the page says to run the UDO step of the cross-reference job.
In the other direction, a form's UDOs tab lists the UDOs that sit on it, the service requests that run it and the pages and links that show or open it; a table, a view and a data item have a UDOs tab too — the data requests and searches that read them, the form extensions that add them.
Where is it used
Where used, on a line of a list, opens the data item, the view or the table on its usages.
| Part | Content |
|---|---|
| Tabs | One per kind of user: Applications, Reports, Business views, Tables, Data structures, Event rules, UDOs (the data requests, searches and form extensions that read or add the object) — and, for a table, its own Columns, Indexes and Triggers. |
| Totals | In how many applications, forms and places the object is used, and as what: a field, a grid column, a label. |
| Only the customer's own objects (55 to 59) | Keeps the objects of the customer's system codes. |
| Only the applications of the upgrade analysis | Keeps the objects the upgrade analysis holds: the impact view of an upgrade. |
| The list | The applications or reports ranked by places; a click opens one. |
Back to …, at the top, returns to where the search came from — same object, same form or section, same tab.
Who uses it
An application and a report say in their heading Last used … · n user(s), or Not used since … — the first day the history knows. A click opens Who uses it: each user and version with their last use. The figures come from JD Edwards' object usage tracking, as collected over time: they reach further back than JD Edwards' own table, which is purged. Nothing is shown when no usage was ever collected for that JD Edwards.
Actions
| Button | Does |
|---|---|
| Create its endpoints… | On an application: opens Create from… of the AIS connector on it, to build the endpoints and the screen that read and save its records. |
| Refresh from JDE | Reads the object again from the JD Edwards specifications — a job of a few seconds that runs in a window on the page; the page then shows the new content without leaving the object. |
Access
The page shows to the roles that hold its menu entry; the functions it reads need the permissions plugin:nomajde.xref:*. Refresh from JDE needs the right to run the job that reads one object again.
Tips & best practices
- Before changing a table or a business view, open it and read the Applications and Reports tabs with Only the customer's own objects ticked: that is the list of what to test.
- During an upgrade, tick Only the applications of the upgrade analysis to see what a change of Oracle reaches in the customer's code.
- Look at Who uses it before retrofitting a modified report: nobody may have run it for years.
- A form's UDOs tab lists what the users built on it — queries, grid formats, personal forms, form extensions, the pages and service requests that open it: what to check again when the form changes with a release.
- The assistant knows the object open on the page: ask it Where is this object used? or What would a change to the table F0101 touch? — see AI assistant.
- To review the user defined objects one by one, choose the UDOs chip: each line gives the type, and a word of the name narrows the list.
Related
- Prepare for upgrade — what to retrofit, in which order, with the UDOs to test again.
- Create from… — an endpoint or a screen from a JD Edwards application.
- Performance — the business functions that cost the most, with who calls them.