# Infor XA (MAPICS) Application Module Reference > Source: https://netray.co/tools/infor-xa-mapics-module-reference > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A lookup of the main Infor XA (MAPICS) application areas with scope and a migration consideration for each, for inventory of what you use. ## Category other-erp ## Erp Infor XA ## Industry Discrete Manufacturing ## Audience - XA administrator - IT manager - Migration lead ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### Application area **Key:** module **Type:** text #### What it covers **Key:** scope **Type:** text #### Typical users **Key:** users **Type:** text #### Migration consideration **Key:** migrate **Type:** text **Rows:** **Module:** Customer Order Management **Scope:** Order entry, pricing, allocation, shipping and invoicing triggers **Users:** Customer service, sales admin **Migrate:** Pricing rules and order status history need mapping **Module:** Inventory Management **Scope:** Item balances, locations, transactions, cycle counting **Users:** Stores, inventory control **Migrate:** Decide how many years of transactions to carry **Module:** Bill of Material **Scope:** Product structures, where used, effectivity **Users:** Engineering **Migrate:** Clean obsolete structures before loading **Module:** Product Data Management **Scope:** Engineering change control and item revisions **Users:** Engineering, document control **Migrate:** Revision history may need a separate archive **Module:** Master Production Scheduling **Scope:** Planning of end items and forecasts at the schedule level **Users:** Master scheduler **Migrate:** Planning parameters rarely map one to one **Module:** Material Requirements Planning **Scope:** Net requirements, planned orders, action messages **Users:** Planners, buyers **Migrate:** Lead times and lot sizing rules must be validated **Module:** Capacity Requirements Planning **Scope:** Load against work centers from planned and released orders **Users:** Production planning **Migrate:** Work center calendars need recreating **Module:** Shop Floor Control **Scope:** Manufacturing orders, routing, labor and material reporting **Users:** Supervisors, planners **Migrate:** Open orders usually closed or reloaded at cutover **Module:** Product Costing **Scope:** Standard cost roll up, variances **Users:** Cost accountants **Migrate:** Costing method differences affect opening inventory value **Module:** Purchasing **Scope:** Purchase orders, receipts, vendor performance **Users:** Buyers, receiving **Migrate:** Open purchase orders and vendor terms need loading **Module:** Accounts Receivable **Scope:** Customer invoices, cash application, aging **Users:** Credit and collections **Migrate:** Open items at cutover date, not history **Module:** Accounts Payable **Scope:** Vendor invoices, payments, aging **Users:** Accounts payable clerks **Migrate:** Open items and vendor bank details **Module:** General Ledger **Scope:** Chart of accounts, journals, period close, reporting **Users:** Controller, accountants **Migrate:** Account structure and opening balances **Module:** Sales Analysis **Scope:** Sales history and statistics by customer and item **Users:** Sales management **Migrate:** Often replaced by a reporting tool, keep an archive **Module:** Forecasting **Scope:** Statistical demand forecasts from history **Users:** Planners **Migrate:** Needs history exported as input to the new system **Module:** Distribution Requirements Planning **Scope:** Replenishment across plants and warehouses **Users:** Supply chain **Migrate:** Network structure may change in the new design **Module:** Product Configurator **Scope:** Rules based configuration of products to order **Users:** Sales engineering **Migrate:** Rule logic is often the hardest item to reproduce **Notes:** 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. ## Content **Intro:** 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. **Sections:** #### How to use the reference **Body:** 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. **Bullets:** - 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 **Body:** 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 **Body:** 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. **Bullets:** - Do not assume one to one module mapping - Decide history depth per area - Keep read only access to the old system after cutover **Cta:** 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. **Faq:** #### Is MAPICS the same as Infor XA? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms infor xa modules, mapics xa application list, mapics modules explained, infor xa functionality list, mapics erp modules, infor xa module inventory, mapics migration planning --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json