# Infor XA (MAPICS) Custom Modification Inventory Worksheet

> Source: https://netray.co/tools/xa-mapics-custom-modification-inventory-worksheet
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

List every XA modification, score value and complexity, and see a priority score to guide keep, replace or retire decisions.

## Category

erp-migration

## Erp

Infor XA

## Audience

- IT manager
- RPG developer
- ERP project manager

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### Modification

**Key:** name

**Type:** text

#### Area

**Key:** area

**Type:** select

**Options:**

- Order entry
- Inventory
- Manufacturing
- Purchasing
- Finance
- Reports
- Interface
- Other

#### Type

**Key:** kind

**Type:** select

**Options:**

- Program change
- Custom program
- Report or query
- Interface or EDI
- Screen change
- Batch job

#### Users

**Key:** users

**Type:** number

**Format:** integer

#### Business value (1-5)

**Key:** value

**Type:** number

**Format:** integer

#### Rebuild effort (1-5)

**Key:** effort

**Type:** number

**Format:** integer

#### Priority score

**Key:** priority

**Type:** number

**Expr:** value * 2 + min(users, 20) / 4 - effort

**Format:** decimal

#### Decision

**Key:** plan

**Type:** select

**Options:**

- Undecided
- Keep as is
- Replace with standard
- Rebuild
- Retire

**Rows:**

#### Customer specific invoice format

**Area:** Order entry

**Kind:** Report or query

**Users:** 4

**Value:** 5

**Effort:** 3

**Plan:** Rebuild

#### Lot traceability screen

**Area:** Inventory

**Kind:** Screen change

**Users:** 12

**Value:** 5

**Effort:** 4

**Plan:** Undecided

#### Nightly EDI 850 import

**Area:** Interface

**Kind:** Interface or EDI

**Users:** 2

**Value:** 5

**Effort:** 3

**Plan:** Keep as is

#### Old commission report

**Area:** Reports

**Kind:** Report or query

**Users:** 1

**Value:** 1

**Effort:** 1

**Plan:** Retire

#### Custom MRP exception list

**Area:** Manufacturing

**Kind:** Custom program

**Users:** 6

**Value:** 4

**Effort:** 2

**Plan:** Replace with standard

**Totals:**

#### Modifications listed

**Key:** name

**Agg:** count

**Format:** integer

#### Total user touchpoints

**Key:** users

**Agg:** sum

**Format:** integer

#### Highest priority score

**Key:** priority

**Agg:** max

**Format:** decimal

**Summary:**

#### Average business value

**Key:** avg_value

**Expr:** avg_value

**Format:** decimal

#### Average rebuild effort

**Key:** avg_effort

**Expr:** avg_effort

**Format:** decimal

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

## Content

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

**Sections:**

#### How to build the inventory

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

**Bullets:**

- 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

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

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

**Bullets:**

- Rating value without asking the process owner
- Ignoring undocumented spreadsheet side processes
- Rebuilding old behavior that the business no longer needs

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

**Faq:**

#### Does this apply to all XA versions?

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

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

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

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

## Search terms

mapics xa customization inventory, infor xa modifications list, as400 custom program inventory, rpg custom code inventory template, erp customization assessment worksheet, xa migration modification review, custom report inventory excel, keep replace retire worksheet

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