Infor XA (MAPICS) Custom Modification Inventory Worksheet
Most XA sites have years of modifications that nobody fully documented. Before choosing a path forward, you need a list. This worksheet captures each customization, rates it, and produces a rough ranking to start the keep, replace or retire conversation.
| Modification | Area | Type | Users | Business value (1-5) | Rebuild effort (1-5) | Priority score | Decision | |
|---|---|---|---|---|---|---|---|---|
8 | ||||||||
9 | ||||||||
7.5 | ||||||||
1.25 | ||||||||
7.5 |
Priority score is a simple ranking aid: value counts double, usage adds up to five points, and effort subtracts. Adjust the weights to suit your shop.
Modification analysis
An optional discussion about analyzing custom code and reports to speed up the inventory.
Optional. The tool and every export work without this. No spam.
How to build the inventory
Start from several sources: library listings of custom programs, modified source members, custom reports and queries, interfaces, scheduled batch jobs and the stories users tell. For each item record where it sits, who uses it and what business rule it supports. Do not rate anything until the list looks complete.
- Ask each department what they would miss
- Check batch job schedules for forgotten jobs
- Include interfaces to customers and suppliers
How the priority score works
Business value on a one to five scale counts double. Users add up to five points, capped at twenty users. Rebuild effort subtracts. High value, widely used, easy to rebuild items rise to the top. Low value items with few users sink, and these are usually your retire candidates. The score only orders the discussion, it does not make the decision.
Common mistakes
Teams often rate by who shouts loudest rather than by process impact. Many modifications exist only because of a workaround for a problem the standard product has since solved. Test whether standard functions now cover the need before rebuilding.
- Rating value without asking the process owner
- Ignoring undocumented spreadsheet side processes
- Rebuilding old behavior that the business no longer needs
Frequently Asked Questions
Does this apply to all XA versions?
The structure applies to any Infor XA or MAPICS installation. The area list is generic. Rename areas and types to match your modules and the way your developers classify changes.
How many items should I expect?
It varies widely. A mid-size shop with decades of use might list dozens to a few hundred. Count what you can, then validate with users to catch hidden items.
Why cap users at twenty?
So that a widely used screen does not swamp the value rating. Change the formula if your shop is larger or you want usage to matter more.
What should I do with Undecided rows?
Review them in a short workshop with the process owner and a developer. Each should leave with a decision, a named owner and a date, even if the decision is to investigate further.
If you have a large set of custom RPG or reports to analyze, we can talk about tooling to read and summarize them. This worksheet works on its own.
Related Tools
VISUAL to CloudSuite Data Cleanup Worksheet
Track record counts, cleanup effort and owners for each master data object before a VISUAL to CloudSuite Industrial migration.
Compliance & ContractsInfor XA (MAPICS) User Access Review Worksheet
Review each user profile, last sign-on, role and conflicting duties, with a days inactive figure and review decision.
ERP Migration & SelectionERP Cutover Runbook Template for VISUAL and XA Migrations
A fill-in go-live weekend runbook with freeze time, task sequence, rollback criteria, contacts and approvals.
More ERP Migration & Selection tools
See all- ERP TCO Comparison Calculator (5-Year)
- ERP Migration Risk Assessment
- Data Migration Effort Calculator
- ERP Selection Scorecard for Manufacturers
- ERP Go-Live Readiness Checklist
- ERP Change Management Readiness Assessment
- ERP Integration Complexity Calculator
- Cloud vs On-Premise ERP Cost Calculator
- ERP Upgrade vs Replace Assessment