JD Edwards UBE Scheduling Worksheet and Checklist
Batch jobs in JD Edwards EnterpriseOne are easy to schedule and hard to keep track of. This worksheet gives CNC admins and functional leads one place to document every scheduled UBE, which version and queue it uses, when it starts, what it waits for and who owns the output.
| UBE | Version | Purpose | Job queue | Frequency | Start time | Avg run (min) | Depends on | Output / printer | Business owner | |
|---|---|---|---|---|---|---|---|---|---|---|
Example UBE names and versions are placeholders; replace them with your own jobs. Use your Job Scheduler application and Work With Submitted Jobs to confirm real run times, then paste the observed average into the run column.
Morning batch exception summary
Optional: ask how a private assistant could summarise failed jobs from your own job history.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
List each scheduled UBE with its version, the job queue it runs on and the planned start time. Fill the average run time from real history in Work With Submitted Jobs, not from guesswork. The dependency column is the most valuable one: write what must be finished before the job starts. The total of scheduled minutes and the average at the bottom give a quick feel for how heavy the night window is.
- One row per scheduled job and version
- Record the queue so you can spot overloaded queues
- Name an owner who reads the output
- Revisit after every upgrade and package deploy
Planning a batch window
A reliable window starts with sequence: sales update before ledger post, inventory snapshots before MRP, period close tasks after daily posting. Spread long jobs over separate queues so one slow report does not block small ones. Leave slack for restarts, and avoid placing heavy reports at the same minute as backups or database maintenance. If your jobs share a single queue, the sum of run times is a rough floor for the window.
Checklist before you schedule
Before a job goes live in the scheduler, confirm the version has the right processing options and data selection, the user profile it runs under has the needed security, and the output route works. Test the job manually in the same environment, check the log for warnings and keep the first schedule date in a quiet period. Record who to call when it fails.
- Processing options and data selection saved and reviewed
- Runs under a service profile with correct security
- Output printer or share path tested
- Restart and rerun procedure written down
- Retention for logs and output set
Common mistakes
Scheduling with a personal profile that later expires is the classic failure. Another is leaving test versions in the scheduler after a project. Jobs that run fine in a small test database can run for hours in production, so use production volumes for estimates. Always review the schedule after an upgrade because versions and queues may need to be rebuilt.
Frequently Asked Questions
Where do I schedule UBEs in JD Edwards?
Use the Job Scheduler application (P91300) to create scheduled jobs, and Work With Submitted Jobs to monitor them. Server Manager also exposes information about the batch process on the enterprise server. Exact menus vary by release.
How do I find the real run time of a job?
Check submitted job history for the UBE and version, and compare start and end times across several runs. Use a typical value and a worst case, because month end volumes often run longer than daily runs.
Should every job have its own queue?
Not necessarily. Group by weight and priority: a small number of queues for light jobs and separate queues for heavy ones such as MRP. Too many queues add overhead and make monitoring harder.
Does this tool connect to my JDE system?
No. It is a browser based document that you fill in and export to Excel. It does not read or write anything in your environment.
If you want failed or late batch jobs summarised for you each morning, Netray can build a private assistant that reads your JDE job history and posts a short exception summary.
Related Tools
JD Edwards Tools Release Upgrade Checklist
A phased checklist for moving JD Edwards EnterpriseOne to a newer tools release, from certification checks to post-cutover monitoring.
OracleJD Edwards Work Order Status Codes Template
Editable worksheet to document your JD Edwards work order status codes, what each one means, who owns it and where an order can move next.
Developer ToolsJD Edwards SQL Query Generator (Open Sales Order Lines)
Generates a read-only SQL Server query for open JDE sales order lines, with Julian date conversion, implied decimal handling and branch filters.
OracleJD Edwards Security Workbench Worksheet
Editable worksheet to record JD Edwards role security records by type, with the actions allowed, risk notes and approver for each.
More Oracle tools
See all- JD Edwards Document Types Reference (OP, SO, OV, PV)
- JD Edwards Table Reference (F4211, F4311, F0101, F4101, F4102)
- JD Edwards Orchestrator Design Template
- JD Edwards Environment Refresh Runbook Template
- JD Edwards UBE Runtime Log Worksheet
- JD Edwards Next Numbers Capacity Worksheet
- JD Edwards Object Promotion Request Template
- JD Edwards Data Dictionary Item Request Template
- JD Edwards User Defined Code Change Log Worksheet
New to JD Edwards EnterpriseOne? Start with the JD Edwards EnterpriseOne guide and toolkit, or plan with Training Path Builder, Upgrade Path Planner, ERP Table and Field Explorer.
Keep exploring
Free tools
- JD Edwards UBE Runtime Log WorksheetRecord each UBE run with its version, records processed and runtime, and see throughput per second so slow versions stand out.
- JDE UBE Runtime Baseline Log WorksheetAn editable log of UBE runs with computed throughput, so you can compare before and after a tools release, database or hardware change.
- JDE UBE Batch Window CalculatorModel UBE elapsed time against your batch window as you add parallel queue slots, including a contention penalty for each extra slot.
ERP fixes and how-tos
- How to set data selection and processing options in JD EdwardsHow data selection and processing options actually work on a JD Edwards version, how they differ, and how to set them up correctly for a report or batch program.
- JDE UBE failed (status E): how to read jde.log and jdedebug.logA JD Edwards UBE that ends with status E gives almost nothing in the Work With Submitted Jobs screen. Here is exactly where jde.log and jdedebug.log live and how to read them.
- How to set up BI Publisher output for a JD Edwards reportJDE BI means BI Publisher: how to attach an RTF template to a JD Edwards EnterpriseOne UBE version, what to configure first, and why it may print the old way.
Runs with your ERP
- Prometheus Planning & Scheduling with JD Edwards EnterpriseOne maintenanceHow Prometheus Group's planning and scheduling tool works with JD Edwards EnterpriseOne maintenance: Gantt scheduling, time confirmation, setup and pitfalls.
- Vertex Tax Connectors with JD Edwards EnterpriseOneHow Vertex calculates sales, use and VAT tax for JD Edwards EnterpriseOne and World, plus Oracle EBS and Cloud ERP: integration model, flows, setup, pitfalls.
- Oracle CPQ and JD Edwards EnterpriseOne: quote to sales orderHow Oracle CPQ integrates with JD Edwards EnterpriseOne: customer data into quotes, sales orders created from quotes, and status back, with setup and pitfalls.
AI on your ERP
- AI for JD Edwards EnterpriseOne Manufacturing, Without Leaving the F-Tables ExposedGrounded AI over JD Edwards EnterpriseOne Manufacturing: work orders, routings, and Orchestrator data, answered on-prem without sending F-table data to a public model.
- AI for JD Edwards Inventory Management and Shop Floor ManufacturingAI on JD Edwards EnterpriseOne inventory and manufacturing: item ledger, work orders, MRP messages and cost variances, answered in plain English on your own servers.
Integrations
- How to add an AI chatbot to JD Edwards EnterpriseOneAdd an AI chatbot to JD Edwards EnterpriseOne: grounded in ERP data via AIS, for planners, buyers and customers, and able to run fully on-prem.
- How to add AI agents to JD Edwards EnterpriseOneHow to add AI agents to JD Edwards EnterpriseOne: Orchestrator and AIS as the tool layer, read-only first, human approval on writes, on-prem models.