# JDE UBE Runtime Baseline Log Worksheet

> Source: https://netray.co/tools/jde-ube-runtime-baseline-log-worksheet
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

An editable log of UBE runs with computed throughput, so you can compare before and after a tools release, database or hardware change.

## Category

oracle

## Erp

Oracle JD Edwards EnterpriseOne

## Audience

- JDE CNC administrator
- JDE developer
- Performance tester

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### UBE

**Key:** ube

**Type:** text

#### Version

**Key:** version

**Type:** text

#### Environment

**Key:** env

**Type:** select

**Options:**

- DEV
- TEST
- PROD
- PERF

#### Run date

**Key:** run_date

**Type:** date

#### Rows processed

**Key:** rows

**Type:** number

#### Elapsed minutes

**Key:** minutes

**Type:** number

#### Rows per minute

**Key:** rpm

**Type:** number

**Expr:** rows / minutes

**Format:** integer

#### Notes

**Key:** notes

**Type:** text

**Rows:**

**Ube:** Sales order batch

**Version:** XJDE0001

**Env:** PERF

**Run date:** 2026-10-05

**Rows:** 1200000

**Minutes:** 38

**Notes:** Baseline before upgrade

**Ube:** Sales order batch

**Version:** XJDE0001

**Env:** PERF

**Run date:** 2026-10-19

**Rows:** 1200000

**Minutes:** 31

**Notes:** After database parameter change

**Ube:** GL post

**Version:** ZJDE0001

**Env:** PROD

**Run date:** 2026-10-06

**Rows:** 480000

**Minutes:** 22

**Notes:** Month-end

**Ube:** MRP regeneration

**Version:** XJDE0002

**Env:** PERF

**Run date:** 2026-10-08

**Rows:** 95000

**Minutes:** 54

**Notes:** Full regeneration

**Totals:**

#### Total rows

**Key:** rows

**Agg:** sum

**Format:** integer

#### Total minutes

**Key:** minutes

**Agg:** sum

**Format:** integer

**Summary:**

#### Overall rows per minute

**Key:** overall_rpm

**Expr:** sum_rows / sum_minutes

**Format:** integer

**Primary:** true

#### Runs logged

**Key:** runs

**Expr:** count

**Format:** integer

**Notes:** Record the same UBE, version, data selection and environment for fair comparisons. Run each measurement more than once.

## Content

**Intro:** Nobody can prove an upgrade made batch slower without a baseline. This worksheet is the simple log: the job, the volume, the time, and the rate it works out to.

**Sections:**

#### How to use it

**Body:** Before any change, run the same UBE versions with fixed data selection and record rows and elapsed minutes. Repeat after the change and compare rows per minute, not raw minutes, because volume differs by day. Export to Excel to chart trends.

#### Keeping it fair

**Body:** Compare like with like: same version, same selection, similar concurrent load. A job that ran alone at night is not comparable with one that ran at the month-end peak. Use the notes column to flag those conditions.

**Bullets:**

- Log the tools release and database version in notes.
- Keep runs from a quiet period for the baseline.
- Capture at least three runs per UBE.

#### Reading the result

**Body:** A drop of more than about 10 percent in rows per minute across repeated runs deserves investigation, starting with database statistics, indexes and any changed processing options. A single slow run is rarely meaningful by itself.

**Cta:** Netray can help analyze UBE history and highlight jobs whose throughput changed after an upgrade.

**Faq:**

#### Where do I find elapsed time?

**Answer:** From the job log or the job's start and end times in Work With Submitted Jobs. Convert to minutes and enter it with the row count from the report.

#### Why rows per minute and not minutes?

**Answer:** Volume changes daily. A throughput rate normalizes for that so you can compare a light day with a heavy one.

#### How many runs do I need?

**Answer:** At least three per measurement, ideally in similar conditions. Use the median if one run is clearly disturbed.

#### Can I add more columns?

**Answer:** Export to Excel and extend it there, for example with CPU time, queue name or number of copies.

## Search terms

jde ube performance baseline, jde batch runtime log, jd edwards performance testing template, jde before after upgrade timing, ube runtime tracking excel, jde submitted jobs analysis

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