Infor LN Change Request Form Template
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.
Fill in
Infor LN Change Request Form Template
Change Request CR-2026-041
Company: Acme Precision Ltd Date raised: 2026-10-20 Requested by: Production planning manager Change type: Normal Environments affected: Development, Test, Production
Title
Add planner field to planned production order report
Description and Reason
Planners need to see the assigned planner on the planned production order report to split follow-up work between shifts.
Impact Assessment
Report layout change only. No data model change. Affects the planning team, about 6 users.
Test Plan
Run the report in test with three planners, compare against the current output, confirm print and export.
Rollback Plan
Restore the previous report version from the saved export and re-convert.
Planned window: 2026-11-02, 18:00 to 19:00
Checks Before Approval
| Check | Yes / No | Comment |
|---|---|---|
| Business owner agrees | ||
| Tested in non-production | ||
| Users informed | ||
| Documentation updated | ||
| Rollback confirmed |
Approvals
This is a generic starting point. Align the fields with your own change management procedure and any audit requirements.
Change control tips
Optional: ask for a short note on setting up lightweight change control for LN without slowing the team down.
Optional. The tool and every export work without this. No spam.
How to fill in the form
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.
- 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
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
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
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.
Frequently Asked Questions
Do I need this if I already use a ticketing tool?
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?
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?
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?
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.
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.
Related Tools
Infor LN and Baan Customization Inventory Worksheet
Editable worksheet to list every Baan or LN customization with type, owner, effort and a retire, keep or replace decision.
Infor LN & BaanInfor LN Session Test Script Template
UAT test script for an LN process or session with prerequisites, numbered steps, expected results and tester sign-off.
Infor LN & BaanInfor LN Cutover Runbook Template
Editable task-by-task cutover plan with owners, durations, dependencies and total cutover hours.
Infor LN & BaanInfor LN User Role and Authorization Matrix Worksheet
Role-by-function matrix for LN access reviews, with access level, risk rating and segregation of duties flags.
More Infor LN & Baan tools
See all- Infor LN Session and Module Code Reference
- Infor LN Production Order Status and Lifecycle Reference
- Infor LN 4GL Session Script Template
- Infor LN Company and Enterprise Unit Design Worksheet
- Infor LN DAL Hook Review Checklist
- Infor LN Warehousing Order Origins and Types Reference
- Infor LN Table Name and SQL Query Builder
- Infor LN Regression Test Effort Calculator
- Baan to Infor LN Data Conversion Mapping Worksheet