Other ERPsFree referencePDF, Excel, Word exportInfor XADiscrete Manufacturing

Infor XA (MAPICS) Application Module Reference

Most Infor XA (MAPICS) sites have a long history of customisation, and nobody is sure which modules are still used. This reference lists the main application areas with scope, typical users and one migration point each, so you can build an honest inventory.

Download:

Application area	What it covers	Typical users	Migration consideration
Customer Order Management	Order entry, pricing, allocation, shipping and invoicing triggers	Customer service, sales admin	Pricing rules and order status history need mapping
Inventory Management	Item balances, locations, transactions, cycle counting	Stores, inventory control	Decide how many years of transactions to carry
Bill of Material	Product structures, where used, effectivity	Engineering	Clean obsolete structures before loading
Product Data Management	Engineering change control and item revisions	Engineering, document control	Revision history may need a separate archive
Master Production Scheduling	Planning of end items and forecasts at the schedule level	Master scheduler	Planning parameters rarely map one to one
Material Requirements Planning	Net requirements, planned orders, action messages	Planners, buyers	Lead times and lot sizing rules must be validated
Capacity Requirements Planning	Load against work centers from planned and released orders	Production planning	Work center calendars need recreating
Shop Floor Control	Manufacturing orders, routing, labor and material reporting	Supervisors, planners	Open orders usually closed or reloaded at cutover
Product Costing	Standard cost roll up, variances	Cost accountants	Costing method differences affect opening inventory value
Purchasing	Purchase orders, receipts, vendor performance	Buyers, receiving	Open purchase orders and vendor terms need loading
Accounts Receivable	Customer invoices, cash application, aging	Credit and collections	Open items at cutover date, not history
Accounts Payable	Vendor invoices, payments, aging	Accounts payable clerks	Open items and vendor bank details
General Ledger	Chart of accounts, journals, period close, reporting	Controller, accountants	Account structure and opening balances
Sales Analysis	Sales history and statistics by customer and item	Sales management	Often replaced by a reporting tool, keep an archive
Forecasting	Statistical demand forecasts from history	Planners	Needs history exported as input to the new system
Distribution Requirements Planning	Replenishment across plants and warehouses	Supply chain	Network structure may change in the new design
Product Configurator	Rules based configuration of products to order	Sales engineering	Rule logic is often the hardest item to reproduce

Module names and packaging varied across Infor XA releases and over the years of local customisation. Use this as an inventory prompt and confirm which areas are actually licensed and in daily use at your site.

Legacy XA inventory review

An optional review of your module inventory and custom program list with a migration view.

Optional. The tool and every export work without this. No spam.

How to use the reference

Search for an area, then confirm three things with your users: is it licensed, is it used daily, and who owns the data. Export the table to Excel and add columns for owner, customisation count and retire, migrate or replace. A one page view of what the business really uses is the best input for any decision about staying, upgrading or moving.

Interview the user, not only the administrator
Add a column for customisations per area
Mark each area retire, migrate or replace

Why the inventory matters

XA runs on IBM i, where custom RPG programs, query files and spreadsheets pulling data often sit outside any documentation. A module that looks small on paper can hold heavy custom logic, especially configurator, pricing and shop floor reporting. Counting those dependencies early prevents the typical surprise late in a replacement project.

Common mistakes

Teams often assume a standard module maps cleanly to a module in the target system. In practice, costing, planning parameters and configurator rules differ in structure, so treat them as design work. Another mistake is loading all history. Decide per area whether you need open items only, summarised history or a full archive.

Do not assume one to one module mapping
Decide history depth per area
Keep read only access to the old system after cutover

Frequently Asked Questions

Is MAPICS the same as Infor XA?

MAPICS was the original product name for the manufacturing ERP. Infor XA is the name it carried after Infor acquired the vendor. Many people still say MAPICS, so both terms appear in searches and in internal documentation.

How do I find which modules we actually use?

Combine three sources: your license list, job and program usage on the IBM i, and interviews with department heads. Usage evidence from job logs is more reliable than recollection when settling whether a module is still in use.

Do we need every module in a replacement?

Not necessarily. Some areas such as sales analysis or forecasting may be better served by a reporting or planning tool. Decide area by area whether to replace, merge into another module, or retire.

What about custom RPG programs?

List them with the files they read and write, and who runs them. Many perform work that the target system handles natively, while others encode business rules that must be rebuilt as configuration or extension.

If you are planning to retire XA, we can help catalogue custom programs and queries and build a read only query layer over the legacy data for the transition.

Talk to an Expert Explore More Free Tools

Related Tools

Other ERPs

More Other ERPs tools

See all

Back to All Tools