Other ERPsFree referencePDF, Excel, Word exportInfor XAAll Infor XA tools

Infor XA (MAPICS) AMFLIB Database File Reference

A searchable list of the 50 core Infor XA (MAPICS) physical files in library AMFLIB, grouped by application area, with what one record represents and the usual join partner. File names and descriptions are taken from the XA 9.2.0 table definition list and apply to XA 9.x and 10.

Download:

File (system name)	Application area	Description	One record represents	Typical join partner	Notes
ITMRVA	M8E	Item revision-A	One item revision (general item data)	ITMRVB, ITMRVC, ITMSIT	Engineering view of the item; revisions sit side by side
ITMRVB	M8E	Item revision-B costing and planning info	Costing and planning data for one item revision	ITMRVA	Read with ITMRVA for the same item and revision
ITMRVC	M8E	Item revision-C purchasing information	Purchasing data for one item revision	ITMRVA, VENITF	Buyer and purchasing defaults at revision level
ITMSIT	M7X	Item Enterprise (item current revision)	The current revision of an item	ITMRVA, ITEMBL	Start here when you only need today's item data
ITEMBL	M75	Item balance file	Balance of one item in one warehouse	ITMSIT, WHSMST, SLQNTY	On-hand and related quantities by warehouse
ITMPLN	M75	Item planning information	Planning data for an item	ITEMBL, PLNORD	Used by MRP alongside REQMTS and PLNORD
PSTHDR	M8E	Product structure header	One parent item's product structure (BOM) header	PSTDTL	BOM header
PSTDTL	M8E	Product structure detail	One component line in a parent's structure	PSTHDR, ITMSIT	BOM components; explode recursively for multi-level BOMs
RTGHDR	M8E	Routing header	One routing header for an item	RTGOPR	Routing header
RTGOPR	M8E	Routing-standard operations for items	One operation in an item's standard routing	RTGHDR	Operation descriptions are held separately in RTGODS
WHSMST	M7X	Warehouse master file	One warehouse	ITEMBL, SITMST	Warehouse codes used across inventory files
SITMST	M7X	Site master	One site	WHSMST	Multi-site setups link warehouses to sites
SLDATA	M79	Location detail file	One stock location	SLQNTY	Location definitions
SLQNTY	M75	Location quantity file	Quantity of an item held at a location	SLDATA, ITEMBL	Detail behind the warehouse balance
MOMAST	M75	Manufacturing order master file	One open manufacturing order	MODATA, MOROUT	Open MOs; closed orders move to MO history
MODATA	M75	Manufacturing order detail	One component requirement on an MO	MOMAST	Pick list and material issue detail
MOROUT	M71	Open order operations detail	One operation on an open MO	MOMAST, MOTRAN	Production Control (M71) operation status
MOTRAN	M71	Shop activity transaction file	One shop floor activity transaction	MOROUT	Labour and quantity reporting against operations
MOHMST	M75	Order history-summary	One closed MO (summary)	MOHDTA, MOHRTG	History counterpart of MOMAST
MOHDTA	M75	Order history-component detail	One component line of a closed MO	MOHMST	History counterpart of MODATA
MOHRTG	M71	Order history-operations detail	One operation of a closed MO	MOHMST	History counterpart of MOROUT
MOHTRN	M71	Shop activity transaction history	One historical shop activity transaction	MOHRTG	History counterpart of MOTRAN; often large
POMAST	M75	Purchase order master file	One open purchase order header	POITEM, VENNAM	Open POs
POITEM	M75	Purchase order item detail file	One line item on an open PO	POMAST, ITMSIT	PO lines
POHSTM	M7K	Purchase order history master file	One historical PO header	POHISTI	Purchasing (M7K) history
POHISTI	M7K	Purchase order history-item file	One historical PO line	POHSTM	Note the 7-character name
VENNAM	M7X	Vendor master	One vendor	POMAST, OPNPAYM	Shared by purchasing and payables
VENITF	M7K	Vendor/item master file	One vendor and item combination	VENNAM, ITMRVC	Approved vendor and vendor item data
MBC6REP	M79	Quote/order header physical file	One customer quote or order header	MBCDREP, MBBFREP	Customer Order Management (COM) uses MBxxREP names
MBCDREP	M79	Line item physical file	One CO or quote line item	MBC6REP	COM line items
MBBFREP	M79	Customer physical file	One customer	MBC6REP, MBDEREP, OPENAR	COM customer master
MBDEREP	M79	Ship to physical file	One ship-to address for a customer	MBBFREP	Ship-to addresses
MBDHREP	M79	Shipment header physical file	One shipment	MBC6REP	Shipment header
MBF9REP	M79	Invoice header physical file	One customer invoice header	MBC6REP, OPENAR	Invoice header
MBFBREP	M79	CO history header physical file	One historical customer order header	MBDRREP	History counterpart of MBC6REP
MBDRREP	M79	CO history line item physical file	One historical CO line	MBFBREP	History counterpart of MBCDREP
IMHIST	M75	(PRE)-Inventory transaction history file	One posted inventory transaction	ITMSIT, WHSMST	Usually the largest history file; restored history goes to IMHGEN
INVTXN	M75	Transaction file	One inventory transaction	IMHIST	Inventory transaction file
GELMAS	M77	General ledger master	One GL account master record	TEMGEN	General Ledger (M77)
TEMGEN	M77	Temporary general ledger	One GL entry waiting to be posted	GELMAS	Check it is empty before period close
OPENAR	M74	Open receivables detail	One open receivable item	MBBFREP, ARHSTS	Accounts Receivable (M74)
ARHSTS	M74	Current paid item history	One paid receivable item	OPENAR	AR history
OPNPAYM	M73	Open payables invoice header	One open payables invoice	OPNPAYN, VENNAM	Accounts Payable (M73)
OPNPAYN	M73	Open payables item detail	One item detail of an open payables invoice	OPNPAYM	Invoice item detail
CHECKH	M73	Check history	One issued check	VENNAM, APHSTS	Payments history
APHSTS	M73	Current invoice payment history	One paid payables invoice	CHECKH	AP history
PLNORD	M7B	Planned order	One planned order from MRP	ITMPLN, REQMTS	MRP (M7B) output
REQMTS	M7B	Requirements physical file	One requirement used in planning	PLNORD	MRP requirements
MZF0REP	M7X	User physical file	One XA application user	MZGUCPP	XA users are defined here as well as being IBM i profiles
MZGUCPP	M7X	User security physical file	One user security entry	MZF0REP	XA application security, separate from IBM i object authority

File names and descriptions are from the Infor XA 9.2.0 table definition list (all in library AMFLIB). Key fields are deliberately not listed: run DSPFFD AMFLIB/<file> on your system for the field layout. Sites often run several environments (for example AMFLIB plus AMFLIBx libraries), and XA 10 can add files.

Map your XA environment libraries

Send us your DSPFD output for the files you report on and we will check it against this list, including any site-added files or extra environment libraries.

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

Was this tool useful?

How to confirm a file on your system

Before you build a query, confirm the file and its layout on the IBM i that runs your environment. DSPFD AMFLIB/MOMAST shows the file description, record length, member count and number of deleted records. DSPFFD AMFLIB/MOMAST lists every field with its type, length and text, and is the only safe source for column names, which this page does not list. From SQL, QSYS2.SYSCOLUMNS and QSYS2.SYSTABLESTAT give the same information per library. If your site uses more than one environment, check which library the job's library list puts first, because the same file name can exist in several environment libraries.

DSPFD FILE(AMFLIB/ITEMBL): description, size, deleted records
DSPFFD FILE(AMFLIB/ITEMBL): field names, types, lengths
DSPDBR FILE(AMFLIB/ITEMBL): logical files built over the physical
SELECT * FROM QSYS2.SYSCOLUMNS WHERE TABLE_SCHEMA = 'AMFLIB' AND TABLE_NAME = 'ITEMBL'

Why Customer Order files are called MBxxREP

Most XA files carry readable names such as MOMAST or POITEM, but Customer Order Management (application area M79) uses generated names like MBC6REP (quote/order header), MBCDREP (line item) and MBBFREP (customer). The same pattern appears in system files such as MZF0REP (user) and MZCFREP (application exit). These files belong to the object-based parts of XA, so the physical name tells you nothing about the content. Keep this reference or the definition list at hand when reading COM programs or building order reports, and alias the files in SQL (h for MBC6REP, l for MBCDREP) so the query stays readable.

Item revision files versus ITMSIT

Engineering data in XA is revision based. ITMRVA holds general item data per revision, ITMRVB holds costing and planning data and ITMRVC holds purchasing data, so a full revision record is spread across three files. ITMSIT (Item Enterprise, item current revision) gives the current revision, which is what most reports and integrations want. Use ITMSIT for today's item master values and go to the ITMRVx files only when you need a specific or future revision, for example when checking an engineering change. Balances are separate: ITEMBL holds the item balance by warehouse and SLQNTY holds quantities by location.

History files versus open files

XA keeps open and historical records in different files. Open manufacturing orders live in MOMAST, MODATA, MOROUT and MOTRAN; once closed and moved to history they sit in MOHMST, MOHDTA, MOHRTG and MOHTRN. Purchasing has POMAST and POITEM for open orders and POHSTM and POHISTI for history. Customer orders move from MBC6REP and MBCDREP to MBFBREP and MBDRREP. Inventory transactions accumulate in IMHIST. A report covering all orders for a period therefore needs a UNION of the open and history files, and a report that reads only open files will drop recently closed orders without any error.

Frequently Asked Questions

What library holds the Infor XA tables?

The standard XA application files are in AMFLIB. Many sites also have additional environment libraries, for example a test or second company environment, that hold the same file names. Check the library list of the job or user you are querying for, and qualify the library in SQL so you do not read the wrong environment.

Where is the customer order header in MAPICS XA?

In Customer Order Management the quote and order header is MBC6REP and the line items are in MBCDREP, both in AMFLIB. Closed orders move to MBFBREP (CO history header) and MBDRREP (CO history line item). The customer master is MBBFREP and ship-to addresses are in MBDEREP.

Which file has the bill of material in Infor XA?

Product structures are held in PSTHDR (product structure header) and PSTDTL (product structure detail), application area M8E. Each PSTDTL record is one component line under a parent. For a multi-level BOM you explode recursively, for example with a recursive common table expression in Db2 for i SQL.

Why does this reference not list column names?

Field names differ by release and by site modification, and a wrong column name wastes more time than no column name. Run DSPFFD against the file in your environment, or query QSYS2.SYSCOLUMNS, to get the exact field names, types and lengths before writing SQL or an extract.

If you want planners and buyers to ask XA these questions in plain English, with read-only queries against AMFLIB on your own servers, we can set that up.

Talk to an Expert Explore More Free Tools