JD Edwards Environment Refresh Runbook Template
Refreshing a JD Edwards test or prototype environment from production is routine work, but every site seems to rebuild the runbook from memory. This template gives you a clean, repeatable document you can attach to the change request.
Fill in
JD Edwards Environment Refresh Runbook Template
JD Edwards Environment Refresh Runbook
Company: Acme Precision Ltd Source: JDE Production (PD920) Target: JDE Prototype (PY920) Planned date: 2026-11-07 Scope: Business data and control tables Owner: A. Rao, CNC administrator
Data sources in scope
Source data sources: Business Data - PROD, Control Tables - Prod, System - 920 (not refreshed)
Target data sources: Business Data - TEST, Control Tables - Test
The System data source, security tables and server map settings are normally NOT overwritten by a business data refresh. Confirm this before starting.
Pre-checks
| Step | Check | Owner | Done |
|---|---|---|---|
| 1 | Backup of the target database taken and restore tested | ||
| 2 | Target web server, enterprise server and batch queues stopped or held | ||
| 3 | Pending packages and open object transfers on the target path code reviewed | ||
| 4 | Disk space on target database confirmed against source size | ||
| 5 | Integrations, EDI and scheduled UBEs pointing at the target disabled |
Refresh steps
| Step | Action | Owner | Start | End |
|---|---|---|---|---|
| 1 | Copy or restore the source database backup onto the target database server | |||
| 2 | Repoint data source records, library lists and database users on the target | |||
| 3 | Reset environment-specific control data (next numbers, UDC values, URLs, printer and server settings) per the site list | |||
| 4 | Run the data masking scripts | |||
| 5 | Rebuild or refresh indexes and statistics | |||
| 6 | Restart services and clear caches on web and enterprise servers |
Data masking
Mask bank account numbers (F0030), employee personal data and customer e-mail addresses in the address book tables before users are allowed in.
Validation
| Test | Expected result | Actual | Pass / Fail |
|---|---|---|---|
| Sign in with a test user on the target | Correct environment banner and role | ||
| Open Work With Submitted Jobs and run a small UBE | Job completes on the target enterprise server | ||
| Count records in F0101 and F4211 against the source | Counts match the refresh timestamp | ||
| Outbound e-mail and integrations | Disabled or pointed at test endpoints |
Approvals
A starting point, not a vendor procedure. Table names and steps vary by database platform, JDE tools release and how your path codes are set up. Always follow your own change control and test the runbook on a lower environment first.
Automate your JDE refresh checks
Optional: we can review your runbook and suggest scripted validation of counts, data sources and masking.
Optional. The tool and every export work without this. No spam.
How to use the template
Fill in the source and target environment, the planned date and the scope. List the data sources that are touched and those that must not be. Then export the document to PDF or Word, add names against each step and walk through it with the database administrator before the change window. The tables are left blank on purpose so owners and timestamps are recorded live during the refresh.
- Decide scope first: business data only, or business data plus control tables.
- Name one owner for the runbook.
- Attach the export to the change record.
What a JDE refresh actually moves
In EnterpriseOne the business data and control tables (UDCs, menus, next numbers, user preferences) live in separate data sources from the System data source, which holds security, user profiles and the object configuration tables. A business data refresh usually restores only the first group. That is why the runbook asks you to list data sources explicitly. Central objects and path code specifications are a different matter and are normally handled by packages and deployment, not a database copy.
Reset after the copy
A copied production database carries production settings: next numbers, URLs, printer and server mappings, e-mail addresses, scheduled jobs and integration endpoints. Skipping the reset step is the most common cause of a test system sending e-mail to real suppliers or posting into a live interface. Treat the reset and masking steps as mandatory and tick them off in the document.
- Disable scheduled UBEs and outbound integrations first.
- Mask personal and bank data.
- Re-test sign-on, a UBE run and a form open before releasing the system.
Common mistakes
Teams overwrite the System data source and lose test users and security. They forget to hold batch queues and a half-finished job writes into a half-copied database. They skip a restore test of the target backup. They do not record the refresh timestamp, so testers cannot tell which production day they are looking at. Write the timestamp into the runbook and send it to testers.
Frequently Asked Questions
How often should we refresh a JDE test environment?
It depends on how fast production data changes and how heavily testers rely on it. Many sites refresh before a major upgrade, before a large project test cycle, or quarterly. Agree a calendar with the functional leads so nobody loses work unexpectedly.
Should the System data source be refreshed too?
Normally no. It holds security, user profiles and object configuration that differ between environments. Overwriting it can remove test users or point the target at production resources. Include it only when you have a deliberate reason and a plan to reset it.
Does this replace Oracle documentation?
No. It is a working checklist for your own change process. Use Oracle's documentation and your database vendor's procedures for the technical details that match your tools release and platform.
Why mask data in a test environment?
Test systems have wider access and weaker controls than production. Bank details, employee information and customer contacts copied there create privacy and compliance exposure. Masking after the copy reduces that risk while keeping realistic volumes.
If you refresh several JDE environments a quarter, Netray can help script the reset and masking steps and check record counts automatically. Ask for a review of your current runbook.
Related Tools
JD Edwards Object Promotion Request Template
A change request form for promoting JDE objects through OMW project statuses and path codes, with testing evidence, package plan and rollback.
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 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.
OracleJD Edwards Batch Window Runtime Calculator
Estimate how long a JDE UBE will take from record volume, throughput and parallel runs, and test whether growth will break the batch window.
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 UBE Runtime Log Worksheet
- JD Edwards Data Dictionary Item Request Template
- JD Edwards User Defined Code Change Log Worksheet