# Infor LN Change Request Form Template

> Source: https://netray.co/tools/infor-ln-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 LN and Baan changes, covering scope, impact, testing, rollback and sign-off.

## Category

infor-ln

## Erp

Infor LN

## Audience

- LN administrator
- LN 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-041

#### Date raised

**Key:** date

**Type:** date

**Default:** 2026-10-20

#### Requested by

**Key:** requester

**Type:** text

**Default:** Production planning manager

#### Change type

**Key:** type

**Type:** select

**Options:**

- Standard
- Normal
- Emergency
- Customization
- Configuration
- Security

**Default:** Normal

#### Environments affected

**Key:** env

**Type:** text

**Default:** Development, Test, Production

#### Change title

**Key:** title

**Type:** text

**Default:** Add planner field to planned production order report

#### Description and reason

**Key:** description

**Type:** textarea

**Default:** Planners need to see the assigned planner on the planned production order report to split follow-up work between shifts.

#### Impact assessment

**Key:** impact

**Type:** textarea

**Default:** Report layout change only. No data model change. Affects the planning team, about 6 users.

#### Test plan

**Key:** test

**Type:** textarea

**Default:** Run the report in test with three planners, compare against the current output, confirm print and export.

#### Rollback plan

**Key:** rollback

**Type:** textarea

**Default:** Restore the previous report version from the saved export and re-convert.

#### Planned window

**Key:** window

**Type:** text

**Default:** 2026-11-02, 18:00 to 19:00

**Blocks:**

#### Change Request {{cr_no}}

**Body:** Company: {{company}}
Date raised: {{date}}
Requested by: {{requester}}
Change type: {{type}}
Environments affected: {{env}}

#### Title

**Body:** {{title}}

#### Description and Reason

**Body:** {{description}}

#### Impact Assessment

**Body:** {{impact}}

#### Test Plan

**Body:** {{test}}

#### Rollback Plan

**Body:** {{rollback}}

Planned window: {{window}}

#### Checks Before Approval

**Table:**

**Columns:**

- Check
- Yes / No
- Comment

**Rows:**

**0:** Business owner agrees

**0:** Tested in non-production

**0:** Users informed

**0:** Documentation updated

**0:** Rollback confirmed

#### Approvals

**Signatures:**

- Requester
- Business owner
- LN administrator
- Change manager

**Notes:** This is a generic starting point. Align the fields with your own change management procedure and any audit requirements.

## Content

**Intro:** Uncontrolled changes to an ERP are a common cause of month-end surprises. This form captures what is changing, who is affected, how it was tested and how to undo it, in one page that exports to PDF or Word.

**Sections:**

#### How to fill in the form

**Body:** Give each request a number and a clear title. State the reason in the business terms of the person who asked, then describe the impact: which sessions, reports, tables, users and interfaces are touched. Name the environments, because a change that stops at test is a different risk from one that reaches production. Write a test plan someone else could follow, and a rollback plan you have actually checked is possible. Then circulate the exported document for approvals.

**Bullets:**

- One change per form
- Name the sessions or objects affected
- State the user group and approximate size
- Confirm rollback before asking for approval

#### Choosing the change type

**Body:** Standard changes are pre-approved, repeatable and low risk, such as adding a user to an existing role. Normal changes follow full review. Emergency changes fix a production stop and are approved quickly, with the full documentation completed afterwards. Customization and Security get extra scrutiny because they alter behavior or access. Keep the list short, and publish what qualifies for each type so requesters do not argue each time.

#### Impact, testing and rollback

**Body:** Impact analysis is where most forms are thin. Check for reports and integrations that read the same tables, scheduled jobs, and any DAL hooks or scripts that run on the objects you change. Testing should use realistic data and include the failure case. For rollback, record exactly which objects or settings to restore, where the saved copy lives and who performs it. A rollback plan that says restore from backup is rarely enough for a mid-day production change.

#### Common mistakes

**Body:** The usual problems are vague titles, approvals collected after the change is done and missing documentation updates. Another is bundling several changes into one request, which makes it impossible to roll back one without the others. Keep the signed forms with the change record so that an auditor or a new administrator can trace what happened and why.

**Cta:** If you want change requests drafted from your ticket history and checked against the objects in your LN environment, we can discuss an on-prem assistant with a human approval step.

**Faq:**

#### Do I need this if I already use a ticketing tool?

**Answer:** Possibly not. If your tool captures impact, test, rollback and approvals, use that. This form suits teams that approve by email or document, or that need a printable record for an audit.

#### Who should approve an LN change?

**Answer:** At minimum the business owner of the process and the system owner, such as the LN administrator. Add finance or compliance approval for changes that affect postings, tax or security.

#### Can I edit the check list?

**Answer:** The exported Word document can be edited freely. The in-page fields cover the common content, and the check table is a starting set you can extend to match your procedure.

#### How should emergency changes be handled?

**Answer:** Approve verbally or by a short message from the named authority, fix the problem, then complete this form afterwards and review the change at the next meeting.

## Search terms

infor ln change request form, erp change request template, baan change request form, ln change management template, erp change control form word, sap infor change request template pdf

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