OracleFree worksheetPDF, Excel, Word exportOracle JD Edwards World

JD Edwards World Custom Program and Modification Inventory Worksheet

Almost every long-lived World installation carries custom RPG, CL programs, DREAM Writer versions and extra files that nobody has listed in years. This worksheet turns that hidden pile into a decision list you can plan a migration or a clean-up from.

Download:

Object name	Object type	Library	Business purpose	Active users	Last changed	Criticality (1 to 5)	Rebuild effort (days)	Priority score	Decision
								36
								8
								36
								35
								0

Total rebuild effort

Highest user count

Highest priority score

Objects inventoried

Average effort per object (days)

4.8

Object names are examples only. Fill the list from your own object inventory, for example from a listing of custom libraries and DREAM Writer versions. Priority score is a simple ranking aid: criticality times active users.

Optional help summarizing legacy RPG and CL

We can walk through your inventory and show how private AI can document what old programs do.

Optional. The tool and every export work without this. No spam.

How to use it

List objects library by library. Include modified vendor objects as well as fully custom ones, because modified standard code is where upgrades and migrations hurt most. For each object, record the business purpose in a sentence a finance or warehouse manager would understand, count the real users, and assign a criticality from one to five. Then set a decision. Anything with zero users and an old change date is a candidate to retire with sign-off.

Include interfaces, flat file drops and scheduled CL jobs
Record who last changed the object and when
Do not rate criticality yourself; ask the process owner
Review undecided rows in a weekly meeting

The scoring logic

Priority score multiplies criticality by active users. It is deliberately simple. It pushes widely used, business-critical code to the top of your analysis list and leaves unused objects at the bottom. The effort column gives a rough rebuild size in days that you refine after reading the source. Totals show the overall modification burden for budgeting.

Reading the results

A high count of rows marked Replace with standard is good news: it means the modification was solving a gap that standard functionality or a newer release now handles. Rows marked Rebuild with high effort are where migration estimates usually go wrong, so review them first. Check that nothing critical is marked Retire without a named approver.

Common mistakes

People inventory only programs and forget custom files, user-defined code tables and menus. Another mistake is trusting object descriptions, which are often stale. Compare last-used information where your system captures it. Finally, avoid carrying every modification into the new platform by default; each one should earn its place.

Frequently Asked Questions

What counts as a modification in World?

Any change to a vendor-delivered program, file or display, plus any object you created in custom libraries. DREAM Writer versions with changed processing options are lighter-weight customization but still belong on the list.

How do I find unused objects?

Use your object description and last-used date information, job logs, and user interviews. Last-used dates are a hint, not proof, because year-end or audit programs may run once a year.

Do I need the source code for every program?

You need it for anything you plan to keep or rebuild. Confirm source members still exist and match the compiled objects before you rely on them. Missing source is a risk to record in the worksheet.

Can I use this outside JD Edwards?

Yes. The structure works for any IBM i application with custom RPG or CL. Change the object types list to match your environment.

Netray can help read legacy RPG and CL source to summarize what each object does, so your inventory is based on the code and not on memory.

Talk to an Expert Explore More Free Tools

Related Tools

Oracle

More Oracle tools

See all

Back to All Tools