JDE UBE Runtime Baseline Log Worksheet
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.
| UBE | Version | Environment | Run date | Rows processed | Elapsed minutes | Rows per minute | Notes | |
|---|---|---|---|---|---|---|---|---|
31,579 | ||||||||
38,710 | ||||||||
21,818 | ||||||||
1,759 |
Record the same UBE, version, data selection and environment for fair comparisons. Run each measurement more than once.
Upgrade performance comparison
Optional: send your log for a short before and after comparison.
Optional. The tool and every export work without this. No spam.
How to use it
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
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.
- 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
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.
Frequently Asked Questions
Where do I find elapsed time?
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?
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?
At least three per measurement, ideally in similar conditions. Use the median if one run is clearly disturbed.
Can I add more columns?
Export to Excel and extend it there, for example with CPU time, queue name or number of copies.
Netray can help analyze UBE history and highlight jobs whose throughput changed after an upgrade.
Related Tools
JDE UBE Batch Window Calculator
Model UBE elapsed time against your batch window as you add parallel queue slots, including a contention penalty for each extra slot.
ERP Migration & SelectionJDE Cutover Data Load Time Calculator
Build the cutover weekend timeline: load hours from row counts and streams, plus index rebuild, validation and a contingency buffer.
OracleJDE F0911 Table Growth Forecast Calculator
Project F0911 Account Ledger size over a horizon from daily documents, lines per document, row bytes, index overhead and annual volume growth.
OracleJDE Package Build and Deployment Request Template
A change request document for JDE package builds and deployments with objects, targets, approvals, back-out and verification steps.
More Oracle tools
See all- JD Edwards Document Types Reference (OP, SO, OV, PV)
- JD Edwards UBE Job Scheduling Worksheet
- JD Edwards Table Reference (F4211, F4311, F0101, F4101, F4102)
- JD Edwards Tools Release Upgrade Checklist
- JD Edwards Orchestrator Design Template
- JD Edwards Security Workbench Worksheet
- JD Edwards Environment Refresh Runbook Template
- JD Edwards UBE Runtime Log Worksheet
- JD Edwards Next Numbers Capacity Worksheet