# JD Edwards World and IBM i Change Request Form Template

> Source: https://netray.co/tools/jde-world-and-ibm-i-change-request-form-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Fill-in change request form for program, PTF, system value or data changes with backout plan and approval lines, exported as a clean document.

## Category

erp-operations

## Erp

Oracle JD Edwards World

## Audience

- IBM i administrator
- JDE developer
- Change manager

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company

**Key:** company

**Type:** text

**Default:** Acme Precision Ltd

#### Change request number

**Key:** cr_no

**Type:** text

**Default:** CR-2026-0142

#### Request date

**Key:** date

**Type:** date

**Default:** 2026-10-20

#### Requested by

**Key:** requester

**Type:** text

**Default:** A. Patel, Finance Systems

#### System or partition

**Key:** system

**Type:** text

**Default:** PRODLPAR1

#### Change type

**Key:** type

**Type:** select

**Options:**

- Program change
- PTF or cumulative package
- System value
- Data correction
- Interface change
- Hardware or OS upgrade

**Default:** Program change

#### Risk level

**Key:** risk

**Type:** select

**Options:**

- Low
- Medium
- High

**Default:** Medium

#### Change summary

**Key:** summary

**Type:** textarea

**Default:** Update custom purchase order print program to show revised vendor payment terms.

#### Business reason

**Key:** reason

**Type:** textarea

**Default:** New supplier contracts changed standard payment terms effective 1 November.

#### Planned window

**Key:** window

**Type:** text

**Default:** 2026-10-31 20:00 to 22:00

#### Backout plan

**Key:** backout

**Type:** textarea

**Default:** Restore the previous program object from the saved backup library and clear the program cache by restarting the batch subsystem.

**Blocks:**

#### Change Request {{cr_no}}

**Body:** Company: {{company}}
Requested by: {{requester}}
Date: {{date}}
System or partition: {{system}}
Change type: {{type}}
Risk level: {{risk}}

#### Summary and Reason

**Body:** Summary:
{{summary}}

Business reason:
{{reason}}

#### Implementation Plan

**Body:** Planned window: {{window}}

Before the change: take a backup of every object to be replaced, confirm no jobs are using them, and notify affected users.

After the change: run the agreed smoke tests and confirm results with the process owner.

#### Test Evidence

**Table:**

**Columns:**

- Test
- Environment
- Expected result
- Actual result
- Tester

**Rows:**

**0:** Unit test

**1:** Test library

**0:** Regression

**1:** Test library

**0:** User acceptance

**1:** Test library

#### Backout Plan

**Body:** {{backout}}

#### Approvals

**Signatures:**

- Requester
- Process owner
- IBM i administrator
- Change manager

**Notes:** This is a starting point for your own change control process, not a replacement for it. Add fields your auditors require, such as ticket references and segregation of duties confirmations.

## Content

**Intro:** A change on an IBM i production partition touches payroll, orders and the general ledger at the same time. This template gives you a short, consistent form with the five things reviewers always ask for: what, why, when, how tested and how to undo it.

**Sections:**

#### How to fill it in

**Body:** Complete the fields at the top, then write a short summary and a business reason in plain language. Choose a risk level honestly: high means a failure stops orders, shipments or financial close. Describe the planned window and the backout plan before anyone approves anything. After your tests, print the form and add actual results. The signature lines record who agreed to the change before it happened.

**Bullets:**

- One form per change, not one per project
- Backout plan must be specific enough for someone else to run
- Attach test evidence rather than writing passed
- Record the actual implementation time afterwards

#### Why a form matters

**Body:** Auditors test change management by sampling changes and looking for approval, testing and segregation of duties. On IBM i this often means showing that the person who wrote the program did not promote it to production without review. The form is the evidence. It also protects the team, because a clear backout plan makes it safer to say yes to a change.

#### Reading the risk level

**Body:** Low risk changes are reversible within minutes and affect few users, for example a report heading. Medium risk touches a shared program or a data table with a tested backout. High risk includes operating system upgrades, PTF packages that need an IPL, data conversions and any change to posting logic. High risk changes should always have a rehearsal and an agreed go or no-go checkpoint.

#### Common mistakes

**Body:** The most common mistake is a backout plan that says restore from backup without naming which backup, who does it and how long it takes. Another is testing in a library that differs from production. Record the library list and the object versions tested. Finally, do not skip the form for urgent fixes; use a shorter version afterwards and record the emergency approval.

**Cta:** Netray can help set up read-only checks that compare object versions between test and production so your change form is backed by facts.

**Faq:**

#### Is this form enough for audit?

**Answer:** It is a good base, but your auditors and policy decide what is required. Add approval levels, ticket references and segregation of duties fields as needed, and keep the signed copy where auditors can retrieve it.

#### Do PTFs need a change request?

**Answer:** Yes. PTFs and cumulative packages change system behavior and often need an IPL. Treat them as medium or high risk and record the package identifier, the test partition and the backout approach.

#### What about emergency changes?

**Answer:** Allow an emergency path with verbal approval from a named manager, then complete the form within a set period, such as one business day. Review emergency changes monthly to see whether they are being overused.

#### Can I add custom fields?

**Answer:** The downloadable document reflects the fields you see here. For extra fields, copy the exported document into your document system and extend it there.

## Search terms

ibm i change request form, as400 change management template, jde world change control form, ptf installation change request, as400 program promotion form, erp change request template word, legacy system change control document

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