JD Edwards Batch Window Runtime Calculator
When a nightly or month end UBE starts overrunning the batch window, the question is how much parallelism or tuning is enough. This calculator gives a first answer from record volume, measured throughput and parallel runs.
Your numbers
Use the record count from your last month end run.
Measured from a previous run: records divided by runtime in seconds.
Number of versions or data-selection slices running at the same time.
Lock waits and database load mean parallel runs rarely scale perfectly.
Your results
A planning estimate based on simple throughput. Real runs depend on locks, I/O, data selection and competing jobs. Calibrate with your own measured runs.
Runtime vs parallel processes
Sweeps Parallel processes from 1 to 16, holding your other inputs fixed.
Review your JDE batch window
Optional: share your run history and get a second opinion on where the time goes.
Optional. The tool and every export work without this. No spam.
How to use the calculator
Enter the records processed on a typical heavy run and the throughput you measured per process. Choose how many parallel processes you could run and a realistic parallel efficiency. Add the window you have and your volume growth. The result shows estimated runtime, how much of the window it uses, the headroom and how many years until growth breaks the window.
- Take records and runtime from the job log.
- Use efficiency between 60 and 90 percent as a start.
- Test the chart to see the diminishing return of more processes.
The formula
Effective throughput equals single-process throughput times processes times efficiency. Runtime equals records divided by effective throughput, converted to hours. Years to limit uses compound growth: runtime grows by the growth rate each year, so the years until runtime equals the window is ln(window divided by runtime) divided by ln(1 plus growth). Treat it as a trend guide, not a prediction.
Splitting a UBE in JDE
Parallel runs in JD Edwards usually come from several versions of the same UBE with different data selection ranges, such as business unit or order number ranges, submitted to one or more queues and servers. The split must not overlap or leave gaps, and the slices should have similar work. Check lock behaviour on shared tables, as slices that update the same records may block each other.
Common mistakes
Assuming perfect scaling, ignoring that the database becomes the bottleneck, and splitting by a range where most records fall in one slice are frequent mistakes. Also avoid using a quiet-hour measurement for a busy window. Re-measure after each change.
Frequently Asked Questions
How do I measure throughput per process?
Divide the records processed by the execution time in seconds from a past run of the same version, for example from the job log or Work With Submitted Jobs. Use a run with typical data selection and a normal system load.
What parallel efficiency should I assume?
Start around 70 to 85 percent and measure. Efficiency drops when slices contend for locks, share slow storage or hit the same indexes. A test split on a production-sized copy gives the real number.
Why does the chart flatten?
Because the model includes a fixed efficiency, runtime falls roughly in proportion to the number of processes. In real systems the curve flattens sooner due to database limits, so treat the high end of the chart with caution.
Does this work for other ERPs?
The arithmetic does. Replace UBE with your batch job and use your own measured throughput. The notes on splitting apply to any batch process that can be partitioned.
If your batch window keeps shrinking, Netray can look at job history with you and suggest where tuning or splitting will help most.
Related Tools
JD Edwards UBE Runtime Log Worksheet
Record each UBE run with its version, records processed and runtime, and see throughput per second so slow versions stand out.
OracleJD Edwards Go-Live Cutover Plan Worksheet
Plan each cutover task with an owner, start hour and duration, and see end times and total window length before the weekend arrives.
OracleJD Edwards Environment Refresh Runbook Template
A fill-in runbook for refreshing a JDE test or development environment from production: scope, data sources, pre-checks, steps, validation and sign-off.
OracleJD Edwards Next Numbers Capacity Worksheet
List the next number series you track, their current and ending values and annual volume, and see how many years of headroom remain.
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 Object Promotion Request Template
- JD Edwards Data Dictionary Item Request Template
- JD Edwards User Defined Code Change Log Worksheet