# Infor XA (MAPICS) AMFLIB Database File Reference

> Source: https://netray.co/tools/infor-xa-amflib-file-reference
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

The core Infor XA 9.x/10 physical files in AMFLIB with application area, what one record holds and the usual join partner, so you can find the right table before you write a query.

## Category

other-erp

## Erp

Infor XA

## Audience

- ERP administrator
- IBM i developer
- Report writer
- Data migration analyst

## Tool

**Kind:** worksheet

**Mode:** reference

**Columns:**

#### File (system name)

**Key:** file

**Type:** text

#### Application area

**Key:** area

**Type:** text

#### Description

**Key:** desc

**Type:** text

#### One record represents

**Key:** record

**Type:** text

#### Typical join partner

**Key:** join

**Type:** text

#### Notes

**Key:** notes

**Type:** text

**Rows:**

**File:** ITMRVA

**Area:** M8E

**Desc:** Item revision-A

**Record:** One item revision (general item data)

**Join:** ITMRVB, ITMRVC, ITMSIT

**Notes:** Engineering view of the item; revisions sit side by side

**File:** ITMRVB

**Area:** M8E

**Desc:** Item revision-B costing and planning info

**Record:** Costing and planning data for one item revision

**Join:** ITMRVA

**Notes:** Read with ITMRVA for the same item and revision

**File:** ITMRVC

**Area:** M8E

**Desc:** Item revision-C purchasing information

**Record:** Purchasing data for one item revision

**Join:** ITMRVA, VENITF

**Notes:** Buyer and purchasing defaults at revision level

**File:** ITMSIT

**Area:** M7X

**Desc:** Item Enterprise (item current revision)

**Record:** The current revision of an item

**Join:** ITMRVA, ITEMBL

**Notes:** Start here when you only need today's item data

**File:** ITEMBL

**Area:** M75

**Desc:** Item balance file

**Record:** Balance of one item in one warehouse

**Join:** ITMSIT, WHSMST, SLQNTY

**Notes:** On-hand and related quantities by warehouse

**File:** ITMPLN

**Area:** M75

**Desc:** Item planning information

**Record:** Planning data for an item

**Join:** ITEMBL, PLNORD

**Notes:** Used by MRP alongside REQMTS and PLNORD

**File:** PSTHDR

**Area:** M8E

**Desc:** Product structure header

**Record:** One parent item's product structure (BOM) header

**Join:** PSTDTL

**Notes:** BOM header

**File:** PSTDTL

**Area:** M8E

**Desc:** Product structure detail

**Record:** One component line in a parent's structure

**Join:** PSTHDR, ITMSIT

**Notes:** BOM components; explode recursively for multi-level BOMs

**File:** RTGHDR

**Area:** M8E

**Desc:** Routing header

**Record:** One routing header for an item

**Join:** RTGOPR

**Notes:** Routing header

**File:** RTGOPR

**Area:** M8E

**Desc:** Routing-standard operations for items

**Record:** One operation in an item's standard routing

**Join:** RTGHDR

**Notes:** Operation descriptions are held separately in RTGODS

**File:** WHSMST

**Area:** M7X

**Desc:** Warehouse master file

**Record:** One warehouse

**Join:** ITEMBL, SITMST

**Notes:** Warehouse codes used across inventory files

**File:** SITMST

**Area:** M7X

**Desc:** Site master

**Record:** One site

**Join:** WHSMST

**Notes:** Multi-site setups link warehouses to sites

**File:** SLDATA

**Area:** M79

**Desc:** Location detail file

**Record:** One stock location

**Join:** SLQNTY

**Notes:** Location definitions

**File:** SLQNTY

**Area:** M75

**Desc:** Location quantity file

**Record:** Quantity of an item held at a location

**Join:** SLDATA, ITEMBL

**Notes:** Detail behind the warehouse balance

**File:** MOMAST

**Area:** M75

**Desc:** Manufacturing order master file

**Record:** One open manufacturing order

**Join:** MODATA, MOROUT

**Notes:** Open MOs; closed orders move to MO history

**File:** MODATA

**Area:** M75

**Desc:** Manufacturing order detail

**Record:** One component requirement on an MO

**Join:** MOMAST

**Notes:** Pick list and material issue detail

**File:** MOROUT

**Area:** M71

**Desc:** Open order operations detail

**Record:** One operation on an open MO

**Join:** MOMAST, MOTRAN

**Notes:** Production Control (M71) operation status

**File:** MOTRAN

**Area:** M71

**Desc:** Shop activity transaction file

**Record:** One shop floor activity transaction

**Join:** MOROUT

**Notes:** Labour and quantity reporting against operations

**File:** MOHMST

**Area:** M75

**Desc:** Order history-summary

**Record:** One closed MO (summary)

**Join:** MOHDTA, MOHRTG

**Notes:** History counterpart of MOMAST

**File:** MOHDTA

**Area:** M75

**Desc:** Order history-component detail

**Record:** One component line of a closed MO

**Join:** MOHMST

**Notes:** History counterpart of MODATA

**File:** MOHRTG

**Area:** M71

**Desc:** Order history-operations detail

**Record:** One operation of a closed MO

**Join:** MOHMST

**Notes:** History counterpart of MOROUT

**File:** MOHTRN

**Area:** M71

**Desc:** Shop activity transaction history

**Record:** One historical shop activity transaction

**Join:** MOHRTG

**Notes:** History counterpart of MOTRAN; often large

**File:** POMAST

**Area:** M75

**Desc:** Purchase order master file

**Record:** One open purchase order header

**Join:** POITEM, VENNAM

**Notes:** Open POs

**File:** POITEM

**Area:** M75

**Desc:** Purchase order item detail file

**Record:** One line item on an open PO

**Join:** POMAST, ITMSIT

**Notes:** PO lines

**File:** POHSTM

**Area:** M7K

**Desc:** Purchase order history master file

**Record:** One historical PO header

**Join:** POHISTI

**Notes:** Purchasing (M7K) history

**File:** POHISTI

**Area:** M7K

**Desc:** Purchase order history-item file

**Record:** One historical PO line

**Join:** POHSTM

**Notes:** Note the 7-character name

**File:** VENNAM

**Area:** M7X

**Desc:** Vendor master

**Record:** One vendor

**Join:** POMAST, OPNPAYM

**Notes:** Shared by purchasing and payables

**File:** VENITF

**Area:** M7K

**Desc:** Vendor/item master file

**Record:** One vendor and item combination

**Join:** VENNAM, ITMRVC

**Notes:** Approved vendor and vendor item data

**File:** MBC6REP

**Area:** M79

**Desc:** Quote/order header physical file

**Record:** One customer quote or order header

**Join:** MBCDREP, MBBFREP

**Notes:** Customer Order Management (COM) uses MBxxREP names

**File:** MBCDREP

**Area:** M79

**Desc:** Line item physical file

**Record:** One CO or quote line item

**Join:** MBC6REP

**Notes:** COM line items

**File:** MBBFREP

**Area:** M79

**Desc:** Customer physical file

**Record:** One customer

**Join:** MBC6REP, MBDEREP, OPENAR

**Notes:** COM customer master

**File:** MBDEREP

**Area:** M79

**Desc:** Ship to physical file

**Record:** One ship-to address for a customer

**Join:** MBBFREP

**Notes:** Ship-to addresses

**File:** MBDHREP

**Area:** M79

**Desc:** Shipment header physical file

**Record:** One shipment

**Join:** MBC6REP

**Notes:** Shipment header

**File:** MBF9REP

**Area:** M79

**Desc:** Invoice header physical file

**Record:** One customer invoice header

**Join:** MBC6REP, OPENAR

**Notes:** Invoice header

**File:** MBFBREP

**Area:** M79

**Desc:** CO history header physical file

**Record:** One historical customer order header

**Join:** MBDRREP

**Notes:** History counterpart of MBC6REP

**File:** MBDRREP

**Area:** M79

**Desc:** CO history line item physical file

**Record:** One historical CO line

**Join:** MBFBREP

**Notes:** History counterpart of MBCDREP

**File:** IMHIST

**Area:** M75

**Desc:** (PRE)-Inventory transaction history file

**Record:** One posted inventory transaction

**Join:** ITMSIT, WHSMST

**Notes:** Usually the largest history file; restored history goes to IMHGEN

**File:** INVTXN

**Area:** M75

**Desc:** Transaction file

**Record:** One inventory transaction

**Join:** IMHIST

**Notes:** Inventory transaction file

**File:** GELMAS

**Area:** M77

**Desc:** General ledger master

**Record:** One GL account master record

**Join:** TEMGEN

**Notes:** General Ledger (M77)

**File:** TEMGEN

**Area:** M77

**Desc:** Temporary general ledger

**Record:** One GL entry waiting to be posted

**Join:** GELMAS

**Notes:** Check it is empty before period close

**File:** OPENAR

**Area:** M74

**Desc:** Open receivables detail

**Record:** One open receivable item

**Join:** MBBFREP, ARHSTS

**Notes:** Accounts Receivable (M74)

**File:** ARHSTS

**Area:** M74

**Desc:** Current paid item history

**Record:** One paid receivable item

**Join:** OPENAR

**Notes:** AR history

**File:** OPNPAYM

**Area:** M73

**Desc:** Open payables invoice header

**Record:** One open payables invoice

**Join:** OPNPAYN, VENNAM

**Notes:** Accounts Payable (M73)

**File:** OPNPAYN

**Area:** M73

**Desc:** Open payables item detail

**Record:** One item detail of an open payables invoice

**Join:** OPNPAYM

**Notes:** Invoice item detail

**File:** CHECKH

**Area:** M73

**Desc:** Check history

**Record:** One issued check

**Join:** VENNAM, APHSTS

**Notes:** Payments history

**File:** APHSTS

**Area:** M73

**Desc:** Current invoice payment history

**Record:** One paid payables invoice

**Join:** CHECKH

**Notes:** AP history

**File:** PLNORD

**Area:** M7B

**Desc:** Planned order

**Record:** One planned order from MRP

**Join:** ITMPLN, REQMTS

**Notes:** MRP (M7B) output

**File:** REQMTS

**Area:** M7B

**Desc:** Requirements physical file

**Record:** One requirement used in planning

**Join:** PLNORD

**Notes:** MRP requirements

**File:** MZF0REP

**Area:** M7X

**Desc:** User physical file

**Record:** One XA application user

**Join:** MZGUCPP

**Notes:** XA users are defined here as well as being IBM i profiles

**File:** MZGUCPP

**Area:** M7X

**Desc:** User security physical file

**Record:** One user security entry

**Join:** MZF0REP

**Notes:** XA application security, separate from IBM i object authority

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

## Content

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

**Sections:**

#### How to confirm a file on your system

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

**Bullets:**

- 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

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

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

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

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

**Faq:**

#### What library holds the Infor XA tables?

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

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

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

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

## Search terms

infor xa tables, infor xa mapics tables, mapics amflib files, infor xa database files, mapics momast file, infor xa erp file list, mapics mbc6rep, infor xa user guide tables

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