# JD Edwards World Custom Object Conversion Effort Calculator

> Source: https://netray.co/tools/jde-world-custom-object-conversion-effort-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Turn your count of custom RPG programs, DREAM Writer reports, screens and interfaces into build and test hours, cost and elapsed time.

## Category

oracle

## Erp

Oracle JD Edwards World

## Audience

- JDE project manager
- IBM i developer
- CIO

## Tool

**Kind:** calculator

**Currency:** $

**Inputs:**

#### Custom RPG programs

**Key:** rpg

**Type:** number

**Default:** 140

**Min:** 0

**Step:** 5

**Unit:** programs

#### Hours to convert one RPG program

**Key:** rpg_hrs

**Type:** number

**Default:** 16

**Min:** 1

**Step:** 1

**Unit:** hours

**Help:** Include analysis, rebuild, unit test and documentation.

#### DREAM Writer reports and batch jobs

**Key:** dw

**Type:** number

**Default:** 90

**Min:** 0

**Step:** 5

**Unit:** objects

#### Hours per DREAM Writer object

**Key:** dw_hrs

**Type:** number

**Default:** 6

**Min:** 1

**Step:** 1

**Unit:** hours

#### Custom green-screen programs

**Key:** screens

**Type:** number

**Default:** 45

**Min:** 0

**Step:** 5

**Unit:** screens

#### Hours per screen program

**Key:** screen_hrs

**Type:** number

**Default:** 20

**Min:** 1

**Step:** 1

**Unit:** hours

#### Custom interfaces

**Key:** interfaces

**Type:** number

**Default:** 25

**Min:** 0

**Step:** 1

**Unit:** interfaces

#### Hours per interface

**Key:** intf_hrs

**Type:** number

**Default:** 40

**Min:** 1

**Step:** 1

**Unit:** hours

#### Share of programs, reports and screens retired as obsolete

**Key:** retire_pct

**Type:** slider

**Default:** 30

**Min:** 0

**Max:** 90

**Step:** 5

**Unit:** %

**Help:** Unused or replaced by standard functionality. Interfaces are not retired in this model.

#### Test hours as a fraction of build hours

**Key:** test_ratio

**Type:** slider

**Default:** 0.5

**Min:** 0.2

**Max:** 1.2

**Step:** 0.1

#### Blended hourly rate

**Key:** rate

**Type:** number

**Default:** 85

**Min:** 0

**Step:** 5

**Unit:** $/hour

#### Developers working in parallel

**Key:** team

**Type:** number

**Default:** 4

**Min:** 1

**Step:** 1

**Unit:** people

**Outputs:**

#### Share carried forward

**Key:** keep

**Expr:** 1 - retire_pct / 100

**Format:** decimal

#### Build hours

**Key:** build

**Expr:** (rpg * rpg_hrs + dw * dw_hrs + screens * screen_hrs) * keep + interfaces * intf_hrs

**Format:** integer

#### Test hours

**Key:** test

**Expr:** build * test_ratio

**Format:** integer

#### Total effort

**Key:** total_hours

**Expr:** build + test

**Format:** integer

**Primary:** true

#### Estimated cost

**Key:** cost

**Expr:** total_hours * rate

**Format:** currency

**Primary:** true

#### Elapsed time (140 productive hours per person per month)

**Key:** months

**Expr:** total_hours / (team * 140)

**Format:** months

**Chart:**

#### Total hours vs share retired

**Type:** line

**X:** retire_pct

**From:** 0

**To:** 90

**Steps:** 19

**Series:**

- total_hours

**Disclaimer:** Hours per object are planning assumptions. Replace them with measured figures from a sample of your own objects.

## Content

**Intro:** Custom code is usually the largest unknown in any JD Edwards World modernization. This calculator gives a first-pass estimate from object counts so you can see how much the decision to retire unused objects changes the effort.

**Sections:**

#### How to use it

**Body:** Count your custom objects: RPG programs in your custom libraries, DREAM Writer versions that are actually scheduled, custom display file programs and interfaces to other systems. Use WRKOBJ, DSPPGMREF and your job scheduler history to separate used from unused. Then enter hours per object type from a sample you have really analysed, not a hope. The retire slider models the share you decide not to carry forward.

#### The method

**Body:** Build hours equal the carried-forward share of programs, reports and screens multiplied by their unit hours, plus all interfaces at their unit hours. Test hours are a ratio of build hours. Cost is total hours times rate, and elapsed months divide hours by team size times 140 productive hours per month. The chart shows how steeply total effort falls as you retire more objects.

**Bullets:**

- Interfaces are kept at full effort because they carry data other systems depend on
- Test ratio of 0.5 is typical for standard logic, higher for financial postings
- Elapsed time does not include waiting for business users to test

#### Reading the result

**Body:** If most of the cost sits in RPG programs, an object-by-object review for fit to standard functionality is the cheapest saving you can make. If interfaces dominate, the integration approach (APIs, files, middleware) matters more than coding hours. Use the three scenarios of 0, 30 and 60 percent retired to give sponsors a range, not a single number.

#### Common mistakes

**Body:** Teams count source members instead of distinct business functions, forget that one DREAM Writer program may have a dozen versions in use, and assume all custom code must be rebuilt. Another mistake is applying the same hours to a 200-line report and a 5,000-line pricing program. Where you can, split your inventory in the companion worksheet before using the totals here.

**Cta:** If you want help producing an object inventory from your IBM i libraries and job history, Netray can run a read-only scan and give you a usage-ranked list.

**Faq:**

#### Does this assume a move to EnterpriseOne?

**Answer:** No. The hours are for rebuilding or converting custom functions on any target platform. Replace the unit hours with those for your chosen approach, whether that is E1, another ERP or a rewritten IBM i application.

#### How do I know which objects are unused?

**Answer:** Check job scheduler history, program call statistics where you have them, and ask the business. Objects not run or called for twelve months, including a full year-end, are candidates for retirement.

#### Why are interfaces not reduced?

**Answer:** Interfaces move data to and from other systems and are rarely safe to drop. If a partner system is being retired too, set the interface count lower.

#### Is 140 productive hours realistic?

**Answer:** It allows for meetings, leave and support work in a typical month. Use a lower number if your developers also carry production support duties.

## Search terms

jd edwards world custom code conversion, rpg program migration effort, jde world modernization estimate, dream writer report conversion, world to enterpriseone custom objects, as400 rpg rewrite cost, jde customization inventory

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json