# JD Edwards Environment Refresh Runbook Template

> Source: https://netray.co/tools/jde-environment-refresh-runbook-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A fill-in runbook for refreshing a JDE test or development environment from production: scope, data sources, pre-checks, steps, validation and sign-off.

## Category

oracle

## Erp

Oracle JD Edwards EnterpriseOne

## Audience

- JDE CNC administrator
- Database administrator
- Change manager

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company name

**Key:** company

**Type:** text

**Default:** Acme Precision Ltd

#### Source environment

**Key:** source_env

**Type:** text

**Default:** JDE Production (PD920)

#### Target environment

**Key:** target_env

**Type:** text

**Default:** JDE Prototype (PY920)

#### Planned refresh date

**Key:** refresh_date

**Type:** date

**Default:** 2026-11-07

#### Refresh scope

**Key:** scope

**Type:** select

**Options:**

- Business data only
- Business data and control tables
- Full copy including central objects

**Default:** Business data and control tables

#### Source data sources

**Key:** source_ds

**Type:** textarea

**Default:** Business Data - PROD, Control Tables - Prod, System - 920 (not refreshed)

#### Target data sources

**Key:** target_ds

**Type:** textarea

**Default:** Business Data - TEST, Control Tables - Test

#### Data masking requirement

**Key:** mask

**Type:** textarea

**Default:** Mask bank account numbers (F0030), employee personal data and customer e-mail addresses in the address book tables before users are allowed in.

#### Runbook owner

**Key:** owner

**Type:** text

**Default:** A. Rao, CNC administrator

**Blocks:**

#### JD Edwards Environment Refresh Runbook

**Body:** Company: {{company}}
Source: {{source_env}}
Target: {{target_env}}
Planned date: {{refresh_date}}
Scope: {{scope}}
Owner: {{owner}}

#### Data sources in scope

**Body:** Source data sources:
{{source_ds}}

Target data sources:
{{target_ds}}

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

**Table:**

**Columns:**

- Step
- Check
- Owner
- Done

**Rows:**

**0:** 1

**1:** Backup of the target database taken and restore tested

**0:** 2

**1:** Target web server, enterprise server and batch queues stopped or held

**0:** 3

**1:** Pending packages and open object transfers on the target path code reviewed

**0:** 4

**1:** Disk space on target database confirmed against source size

**0:** 5

**1:** Integrations, EDI and scheduled UBEs pointing at the target disabled

#### Refresh steps

**Table:**

**Columns:**

- Step
- Action
- Owner
- Start
- End

**Rows:**

**0:** 1

**1:** Copy or restore the source database backup onto the target database server

**0:** 2

**1:** Repoint data source records, library lists and database users on the target

**0:** 3

**1:** Reset environment-specific control data (next numbers, UDC values, URLs, printer and server settings) per the site list

**0:** 4

**1:** Run the data masking scripts

**0:** 5

**1:** Rebuild or refresh indexes and statistics

**0:** 6

**1:** Restart services and clear caches on web and enterprise servers

#### Data masking

**Body:** {{mask}}

#### Validation

**Table:**

**Columns:**

- Test
- Expected result
- Actual
- Pass / Fail

**Rows:**

**0:** Sign in with a test user on the target

**1:** Correct environment banner and role

**0:** Open Work With Submitted Jobs and run a small UBE

**1:** Job completes on the target enterprise server

**0:** Count records in F0101 and F4211 against the source

**1:** Counts match the refresh timestamp

**0:** Outbound e-mail and integrations

**1:** Disabled or pointed at test endpoints

#### Approvals

**Signatures:**

- CNC administrator
- Database administrator
- Functional lead
- Change manager

**Notes:** 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.

## Content

**Intro:** 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.

**Sections:**

#### How to use the template

**Body:** 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.

**Bullets:**

- 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

**Body:** 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

**Body:** 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.

**Bullets:**

- 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

**Body:** 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.

**Cta:** 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.

**Faq:**

#### How often should we refresh a JDE test environment?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

jde environment refresh checklist, jd edwards pd to py refresh, jde copy production to test, jde cnc runbook template, jd edwards environment copy procedure, jde refresh test environment, jde data refresh plan

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