How-toInfor XA (MAPICS XA, IBM i)Product Costing

Infor XA costing: cost types, roll-up and standard cost setup

Question
infor xa costing

Also searched as

  • infor xa standard cost roll up
  • mapics xa product costing
  • infor xa cost types

Short answer

Product costing in Infor XA builds an item's cost from its material, labor, and overhead using the bill of material and routing. Standard cost is the frozen planning cost used to value inventory and measure variance, while other cost sets are used for current or simulated views. A cost roll-up calculates costs from the lowest BOM level upward. Exact program names and options vary by release.

Applies to: Infor XA (MAPICS XA) on IBM i. Cost type names and screens vary by release, so verify in your documentation.

Set up and run a cost roll-up

  1. 1Ensure item master data is complete: costing method, unit of measure, and purchased item costs.
  2. 2Confirm BOM structures are accurate, effective and with correct quantities and scrap.
  3. 3Confirm routings, work center rates, setup and run standards and overhead or burden rates.
  4. 4Choose the cost type to update and decide whether this is a simulation or the standard cost update.
  5. 5Run the roll-up from the lowest level to the top, using the low-level codes.
  6. 6Review the cost by element (material, labor, overhead) and compare with the old cost.
  7. 7Investigate items with large changes before accepting them.
  8. 8Freeze or update standard cost at a defined time and record the inventory revaluation impact.

Cost elements and types

Costs are carried by element: material, labor, variable overhead and fixed overhead are common categories. Purchased items get a material cost directly, and manufactured items accumulate cost from components and routing operations. Standard cost is the target; actual cost shows what you paid and spent; a simulated cost lets you test changes without touching the standard.

I am describing the common structure of manufacturing costing rather than exact XA field names, which you should verify in your release.

How the roll-up works

Roll-up processes items from the lowest BOM level up, so each parent can add the already-calculated cost of its children plus its own operations. This only works if low-level codes are current. A BOM change without a low-level code update can give a stale or wrong parent cost.

Labor and overhead come from routing times multiplied by work center rates, so a wrong rate or run time flows into every product that uses the work center.

Parent cost =
  SUM(component qty x component cost, plus scrap)
+ SUM(operation time x work center labor rate)
+ SUM(operation time x overhead rate)

Pitfalls and governance

Changing standard cost revalues on-hand inventory, so coordinate with finance and timing around period close. Keep a simulation review step, document who approves, and retain the before and after report. Be careful with phantom items, subcontracted operations and yield, which are common sources of surprising roll-up results.

Try it here, free

Infor XA (MAPICS) Migration Readiness Assessment

Open full tool

Ten questions that score how ready you are to move off Infor XA (MAPICS), covering customizations, IBM i dependencies, data quality and ownership.

Common pitfalls

  • !Stale low-level codes producing wrong parent costs.
  • !Wrong or outdated work center rates.
  • !Updating standard cost mid-period without finance sign-off.
  • !Ignoring scrap and yield factors.
  • !Skipping the simulation review.
  • !Assuming cost field names from another ERP.

How an ERP-grounded AI assistant handles this

A grounded assistant can read the cost roll-up output and explain why a product's cost moved, by comparing old and new cost by element and listing the BOM and rate changes behind it. Netray builds this over XA data on-prem so cost data stays inside your network.

Frequently asked questions

What is the difference between standard and actual cost?

Standard is a predetermined cost used for valuation and variance reporting. Actual is what was really incurred. The difference is variance.

Why did a parent item cost not change after a BOM edit?

Costs change only when the roll-up is run, and the roll-up depends on current low-level codes. Re-run it after confirming those.

Can I test cost changes safely?

Use a simulated or alternate cost set where available, review the results, and only then update the standard.

Related

How-to

Infor XA Net.Link: what it is, how it is configured and common issues

Net.Link is the web access layer associated with Infor XA (formerly MAPICS XA) that exposes XA functions through a browser, running on an IBM i web application server. It depends on the IBM i version, the web server profile and Java runtime, so most problems after changes trace to those components. Details vary by XA release, so confirm against your installation guide.

How-to

Infor XA REST API: expose XA through IBM i Integrated Web Services or ION

Infor XA has no single built-in REST API. Practical routes are IBM i Integrated Web Services (IWS), which turns RPG or SQL routines into REST endpoints on the same machine, and Infor ION where your environment supports it. For reads, SQL-backed services are straightforward. For writes, call XA's own programs so business rules run.

How-to

SyteLine 1099: set up vendors and run year-end reporting

1099 reporting in SyteLine depends on three things being right before year end: the vendor is flagged as reportable with a valid tax ID, the payments or invoice distributions are tagged to the correct 1099 category, and the year's totals reconcile to the payment history. You then run the 1099 report for the tax year and either file from it or export it to your filing service.

How-to

Infor XA User List Report: Users, Status and Access for an Audit

Infor XA runs on IBM i, so a complete user list is built from two layers: the IBM i user profiles (who can sign on, status, last sign-on, group profiles, special authorities) and the XA application security tables (which menus, functions and facilities each user may run). Export the first with DSPUSRPRF or the QSYS2.USER_INFO view, add the second from your XA security setup, and join them by user ID.

Advanced

Infor XA PowerLink (Power Link), SIWA and Net-Link: What Each Does and Your Options

Infor XA runs on IBM i with a 5250 green-screen core. PowerLink (also written Power Link) and Net-Link are the interface layers Infor offered to put a more modern or web face on that core, and SIWA is another piece of XA's interface and integration tooling. Because naming and packaging changed across releases, confirm exactly what is installed before planning any change.

How-to

Infor XA Factory Track: What It Does and How to Plan Shop Floor Data Collection

Factory Track is the shop floor data collection offering associated with Infor XA. It captures labor, job and material transactions at the work centre, often with bar code terminals, and posts them to XA production control so that job status, costs and inventory stay current without re-keying. Details differ by release, so check your documentation before configuring anything.

AI for ERP

AI for Infor XA on IBM i: On-Prem, No Replatforming Required

Add AI to Infor XA on IBM i (AS/400) without a migration project. Read DB2 for i directly, ground answers in live XA data, keep everything on-prem.

Stuck on Infor XA (MAPICS XA, IBM i)?

Talk to engineers who work inside Infor XA (MAPICS XA, IBM i) every week, and who build private AI that answers these questions from your own ERP data.

Keep exploring

Free tools

ERP fixes and how-tos

Guides

AI on your ERP

Integrations

Software