# JDE 9.1 to 9.2 Upgrade Retrofit Effort Calculator

> Source: https://netray.co/tools/jde-enterpriseone-9-2-upgrade-retrofit-effort-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Estimate retrofit and test hours, cost and duration for a JD Edwards EnterpriseOne upgrade to 9.2 from your counts of modified objects, and see how much replacing mods with UDOs saves.

## Category

oracle

## Erp

JD Edwards EnterpriseOne

## Audience

- CNC administrator
- JDE development lead
- IT manager

## Tool

**Kind:** calculator

**Currency:** $

**Inputs:**

#### Modified interactive applications

**Key:** apps

**Type:** number

**Default:** 120

**Min:** 0

**Step:** 5

**Unit:** objects

#### Modified UBEs (reports and batch)

**Key:** ubes

**Type:** number

**Default:** 150

**Min:** 0

**Step:** 5

**Unit:** objects

#### Modified business functions

**Key:** bsfn

**Type:** number

**Default:** 80

**Min:** 0

**Step:** 5

**Unit:** objects

#### Modified tables

**Key:** tbls

**Type:** number

**Default:** 30

**Min:** 0

**Step:** 1

**Unit:** objects

#### Custom 55-59 objects

**Key:** custom

**Type:** number

**Default:** 300

**Min:** 0

**Step:** 10

**Unit:** objects

**Help:** Mostly carried forward, but each needs a check and a test.

#### Hours per modified application

**Key:** h_app

**Type:** number

**Default:** 4

**Min:** 0

**Step:** 0.5

**Unit:** h

#### Hours per modified UBE

**Key:** h_ube

**Type:** number

**Default:** 3

**Min:** 0

**Step:** 0.5

**Unit:** h

#### Hours per modified business function

**Key:** h_bsfn

**Type:** number

**Default:** 5

**Min:** 0

**Step:** 0.5

**Unit:** h

#### Hours per modified table (incl. conversion)

**Key:** h_tbl

**Type:** number

**Default:** 6

**Min:** 0

**Step:** 0.5

**Unit:** h

#### Hours per custom object carried forward

**Key:** carry

**Type:** number

**Default:** 0.5

**Min:** 0

**Step:** 0.1

**Unit:** h

#### Share of mods replaced by UDOs or orchestrations

**Key:** udo

**Type:** select

**Default:** 0.1

**Options:**

##### 0%

**Value:** 0

##### 10%

**Value:** 0.1

##### 25%

**Value:** 0.25

##### 40%

**Value:** 0.4

#### Testing multiplier

**Key:** test_mult

**Type:** number

**Default:** 1.5

**Min:** 1

**Step:** 0.1

**Help:** 1.5 adds 50% of retrofit hours for unit and regression testing.

#### Blended hourly rate

**Key:** rate

**Type:** number

**Default:** 95

**Min:** 0

**Step:** 5

**Unit:** $/h

#### Developers on retrofit

**Key:** team

**Type:** number

**Default:** 3

**Min:** 1

**Step:** 1

**Unit:** people

#### Productive hours per developer per week

**Key:** hpw

**Type:** number

**Default:** 32

**Min:** 1

**Step:** 1

**Unit:** h

**Outputs:**

#### Modified object retrofit hours (before UDO reduction)

**Key:** mod_hours

**Expr:** apps * h_app + ubes * h_ube + bsfn * h_bsfn + tbls * h_tbl

**Format:** hours

#### Retrofit hours

**Key:** retrofit

**Expr:** mod_hours * (1 - udo) + custom * carry

**Format:** hours

**Description:** Modified objects reduced by the UDO share, plus carry-forward checks of custom objects.

#### Total hours incl. testing

**Key:** total

**Expr:** retrofit * test_mult

**Format:** hours

**Primary:** true

#### Estimated cost

**Key:** cost

**Expr:** total * rate

**Format:** currency

**Primary:** true

#### Elapsed weeks for the team

**Key:** weeks

**Expr:** total / (team * hpw)

**Format:** weeks

#### Hours saved by the UDO share (incl. testing)

**Key:** saved

**Expr:** mod_hours * udo * test_mult

**Format:** hours

**Chart:**

#### Total hours vs modified applications

**Type:** line

**X:** apps

**From:** 0

**To:** 400

**Steps:** 21

**Series:**

- total
- retrofit

**Disclaimer:** Hours per object are planning rules of thumb for a first estimate, not Oracle figures. Replace them with your own averages from a pilot retrofit of 10 to 20 objects.

## Content

**Intro:** This calculator estimates retrofit and testing effort for a JD Edwards EnterpriseOne upgrade to 9.2 from the number of modified Oracle objects and custom objects you carry. It also shows how much effort you avoid by replacing modifications with UDOs such as personalised forms and orchestrations before or during the upgrade.

**Sections:**

#### How to use it

**Body:** Count the Oracle objects you have modified, by type, and your custom objects in system codes 55 to 59. The usual source is an object list from Object Management Workbench and the upgrade's specification merge reports, which show which modified objects were merged and which conflicted. Enter hours per object from your own history if you have it; the defaults are mid-range planning numbers. Pick the share of modifications you expect to retire by replacing them with UDOs, set the testing multiplier, rate and team, and read total hours, cost and elapsed weeks.

**Bullets:**

- Count only objects that are still used; Object Usage Tracking helps find dead mods
- Treat modified tables separately, they drive table conversions and data work
- Run a pilot on 10 to 20 objects and replace the defaults with real averages

#### The formula behind it

**Body:** Modified object hours are the count of each type times its hours per object: applications times hours per application, plus UBEs, business functions and tables likewise. That figure is reduced by the share you replace with UDOs, because a mod retired is a mod you do not retrofit. Custom objects add a small carry-forward check each, since they are not overwritten by the upgrade but still need rebuilding, review and testing. Total hours are retrofit hours times the testing multiplier. Cost is total hours times the rate, and elapsed weeks are total hours divided by team size times productive hours per week.

#### Worked example

**Body:** With the defaults: 120 applications at 4 hours, 150 UBEs at 3, 80 business functions at 5 and 30 tables at 6 give 1,510 hours of modified object work. A 10% UDO share removes 151 hours, leaving 1,359; 300 custom objects at 0.5 hours add 150, for 1,509 retrofit hours. Testing at 1.5 gives about 2,264 hours, roughly 215,000 dollars at 95 per hour, and about 24 weeks for three developers at 32 productive hours. Raising the UDO share to 40% saves about 906 hours.

#### Version differences and gotchas

**Body:** A move from 9.1 to 9.2 is an application upgrade with specification merges and table conversions; once on 9.2, Oracle's continuous delivery model means later updates arrive as ESUs and Tools releases rather than another full upgrade, which is what people mean by a simplified upgrade path. Modified tables cost the most because table conversions must preserve your added columns and data. Visual Compare in the development client helps retrofit applications and reports by showing differences between your version and Oracle's. Do not forget interfaces, versions with changed processing options and BI Publisher templates in the test scope.

**Cta:** If you want your team to ask what a JD Edwards modification does and where it is used in plain English on your own servers before you retrofit it, we can index your objects for that.

**Faq:**

#### How long does a JDE 9.1 to 9.2 upgrade take?

**Answer:** It depends mostly on the number of modified objects, the amount of testing and how much data the table conversions touch. Lightly modified sites can finish in a few months; heavily modified ones take much longer. Use this calculator with your object counts and a pilot retrofit to get a defensible estimate.

#### What is a table conversion in JDE?

**Answer:** A table conversion is a batch process that changes the structure or content of a table during an upgrade or data migration, for example adding columns Oracle introduced or moving data between tables. In an upgrade they run as part of the plan; modified tables need extra care so your added columns survive.

#### What is the JDE simplified upgrade?

**Answer:** After reaching 9.2, Oracle delivers new functionality through continuous delivery: ESUs and Tools releases applied to 9.2 instead of a new major release. Staying close to standard objects and using UDOs keeps those updates cheap, which is why reducing modifications pays off beyond the current upgrade.

#### How can I reduce JDE upgrade retrofit effort?

**Answer:** Retire unused mods found through Object Usage Tracking, replace form changes with personalisation and form extensions, move logic into orchestrations, and keep custom code in 55 to 59 objects instead of changing Oracle objects. Every modification removed lowers retrofit hours and the testing that comes with them.

## Search terms

jde 9.1 to 9.2 upgrade, jde 9.2 upgrade, jde simplified upgrade, jde upgrade, table conversion in jde, jde retrofit estimate, jde upgrade effort

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