Maintenance & ReliabilityFree referencePDF, Excel, Word exportInfor EAMAll Infor EAM tools

Infor EAM / HxGN EAM Work Management Table Reference (R5 Tables)

A searchable reference of the R5 tables behind work management in Infor EAM 11.x and HxGN EAM 12: work orders, activities, booked labor, equipment, PM schedules, stores, purchasing and cases. Each row gives key columns, the columns report writers actually use, and the usual join.

Download:

Table	Area	Holds	Key columns	Useful reporting columns	Common join
R5EVENTS	Work orders	Work order and event header, one row per work order	EVT_CODE (EVT_ORG for organization)	EVT_DESC, EVT_TYPE, EVT_RTYPE, EVT_STATUS, EVT_RSTATUS, EVT_MRC, EVT_JOBTYPE, EVT_PRIORITY, EVT_REPORTED, EVT_TARGET, EVT_START, EVT_COMPLETED, EVT_LASTSAVED	EVT_OBJECT + EVT_OBJECT_ORG to R5OBJECTS; EVT_PPM to R5PPMS; EVT_MRC to R5MRCS
R5ACTIVITIES	Work orders	Activities (operations) on a work order, with trade and estimated hours	ACT_EVENT, ACT_ACT	ACT_TRADE, ACT_EST, ACT_MRC, ACT_TASK	ACT_EVENT to R5EVENTS.EVT_CODE; ACT_TRADE to R5TRADES
R5BOOKEDHOURS	Labor	Labor hours booked against work order activities	BOO_CODE	BOO_EVENT, BOO_ACT, BOO_PERSON, BOO_HOURS, BOO_DATE	BOO_EVENT + BOO_ACT to R5ACTIVITIES; BOO_PERSON to R5PERSONNEL
R5ACTCHECKLISTS	Work orders	Checklist items on work order activities	ACK_CODE	ACK_EVENT, ACK_ACT, ACK_DESC, ACK_COMPLETED	ACK_EVENT + ACK_ACT to R5ACTIVITIES
R5OBJECTS	Assets	Equipment master: assets, positions, systems and locations	OBJ_CODE, OBJ_ORG	OBJ_DESC, OBJ_OBTYPE, OBJ_CLASS, OBJ_MRC, OBJ_STATUS, OBJ_PARENT, OBJ_SERIALNO, OBJ_MANUFACT, OBJ_LOCATION	Joined from EVT_OBJECT, PPO_OBJECT, REA_OBJECT, CSM_OBJECT (always with the _ORG column)
R5READINGS	Assets	Meter readings recorded against equipment	REA_OBJECT plus reading date	REA_DATE, REA_READING, REA_UOM	REA_OBJECT to R5OBJECTS; REA_UOM to R5UOMS
R5PPMS	Preventive maintenance	PM header: frequency and period unit of measure, revision controlled	PPM_CODE, PPM_REVISION	PPM_DESC, PPM_FREQ, PPM_PERIODUOM, PPM_ORG	PPM_CODE + PPM_REVISION to R5PPMOBJECTS.PPO_PPM + PPO_REVISION
R5PPMOBJECTS	Preventive maintenance	PM schedule lines: which PM applies to which equipment and when it is next due	PPO_PPM, PPO_REVISION, PPO_OBJECT, PPO_OBJECT_ORG	PPO_DUE, PPO_FREQ, PPO_PERIODUOM, PPO_ORG	PPO_OBJECT + PPO_OBJECT_ORG to R5OBJECTS
R5STANDWORKS	Preventive maintenance	Standard work orders used as templates	STW_CODE	STW_DESC	Referenced by PM and work order setup
R5TASKS	Planning	Task plans (standard operations, instructions and materials)	TSK_CODE	TSK_DESC	ACT_TASK to TSK_CODE
R5MRCS	Organization	Departments (maintenance responsibility centres)	MRC_CODE	MRC_DESC, MRC_ORG, MRC_STORE	EVT_MRC, OBJ_MRC, ACT_MRC, PER_MRC to MRC_CODE
R5PERSONNEL	Labor	Employees who book hours and are assigned to work	PER_CODE	PER_DESC, PER_TRADE, PER_MRC	BOO_PERSON to PER_CODE
R5TRADES	Labor	Trades (crafts) used to plan and book labor	TRD_CODE	TRD_DESC	ACT_TRADE, PER_TRADE to TRD_CODE
R5CREWS	Labor	Crews of employees	CRW_CODE	CRW_DESC	Crew employee and work order assignment tables
R5PARTS	Materials	Part master	PAR_CODE, PAR_ORG	PAR_DESC, PAR_UOM, PAR_CLASS, PAR_COMMODITY	TRL_PART, STO_PART, ORL_PART, RQL_PART to PAR_CODE
R5STORES	Materials	Storerooms	STR_CODE	STR_DESC, STR_ORG	STO_STORE, BIN_STORE, TRL_STORE to STR_CODE
R5BINS	Materials	Bins within a store	BIN_STORE, BIN_CODE	BIN_STORE, BIN_CODE	BIN_STORE to R5STORES
R5STOCK	Materials	Part stock per store	STO_PART, STO_PART_ORG, STO_STORE	STO_QTY	STO_PART to R5PARTS; STO_STORE to R5STORES
R5TRANSACTIONS	Materials	Store transaction headers (issues, returns, receipts, transfers)	TRA_CODE	TRA_TYPE, TRA_DATE	TRA_CODE to R5TRANSLINES.TRL_TRANS
R5TRANSLINES	Materials	Store transaction lines, including parts issued to work orders	TRL_TRANS plus line	TRL_PART, TRL_QTY, TRL_PRICE, TRL_EVENT, TRL_TYPE, TRL_STORE, TRL_DATE	TRL_EVENT to R5EVENTS.EVT_CODE; TRL_PART to R5PARTS
R5ORDERS	Purchasing	Purchase order headers	ORD_CODE, ORD_ORG	ORD_STATUS, ORD_SUPPLIER	ORD_CODE + ORD_ORG to ORL_ORDER + ORL_ORDER_ORG
R5ORDERLINES	Purchasing	Purchase order lines	ORL_ORDER, ORL_ORDER_ORG plus line	ORL_PART, ORL_ORDQTY, ORL_RECVQTY	ORL_PART to R5PARTS
R5REQUISITIONS	Purchasing	Requisition headers	REQ_CODE	REQ_STATUS	REQ_CODE to R5REQUISLINES.RQL_REQ
R5REQUISLINES	Purchasing	Requisition lines	RQL_REQ plus line	RQL_PART, RQL_QTY	RQL_PART to R5PARTS
R5CASEMANAGEMENT	Cases	Case management records, kept separate from work orders	CSM_CODE, CSM_ORG	CSM_DESC, CSM_STATUS, CSM_MRC	CSM_OBJECT + CSM_OBJECT_ORG to R5OBJECTS
R5UCODES	Codes	User codes and their mapping to system codes (statuses, types)	UCO_ENTITY, UCO_CODE	UCO_DESC, UCO_RENTITY, UCO_RCODE, UCO_SYSTEM	Decode EVT_STATUS with UCO_RENTITY = 'EVST' and UCO_CODE = EVT_STATUS
R5ORGANIZATION	Organization	Organizations in a multi-organization installation	ORG_CODE	ORG_DESC	Every *_ORG column (EVT_ORG, OBJ_ORG, PAR_ORG) to ORG_CODE

Table and column names follow the R5 schema used by Infor EAM 11.x. HxGN EAM 12 keeps the R5 schema but adds columns release by release, and installations differ: confirm every column in your own data dictionary (for example ALL_TAB_COLUMNS on Oracle or INFORMATION_SCHEMA.COLUMNS on SQL Server). Status code values differ by installation: list yours with SELECT * FROM R5UCODES WHERE UCO_RENTITY = 'EVST'.

Get a data dictionary for your EAM

We can extract the full R5 table and UDF list from your EAM database and return it as a searchable workbook with your user status mappings.

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

Was this tool useful?

How to use it

Search by table name, column prefix or area. Every EAM column carries a three-letter prefix that tells you its table: EVT_ is R5EVENTS, ACT_ is R5ACTIVITIES, BOO_ is R5BOOKEDHOURS, OBJ_ is R5OBJECTS, PPO_ is R5PPMOBJECTS, TRL_ is R5TRANSLINES. When you see an unfamiliar column in a Dataspy, Grid Designer field or BIRT dataset, the prefix gets you to the right row here. Export the table to Excel and add your own custom fields (the UDF columns such as EVT_UDFCHAR01) so the sheet becomes your installation data dictionary.

Read-only queries belong on a reporting copy, not the production database.
Use Grid Designer or Dataspies for end users before reaching for SQL.

User status versus system status

R5EVENTS stores two of each classifier. EVT_STATUS and EVT_TYPE hold the user codes your administrators defined, while EVT_RSTATUS and EVT_RTYPE hold the system codes the application logic runs on. Many user statuses can map to one system status, so reports that count open or closed work should filter on EVT_RSTATUS and display EVT_STATUS. The mapping lives in R5UCODES: UCO_RENTITY identifies the code entity (EVST for work order status), UCO_CODE is the user code, UCO_RCODE the system code it maps to, and UCO_DESC its description. Query R5UCODES on your system rather than copying a status list from another site, because codes and descriptions are configurable.

Organizations, cases and archive tables

In a multi-organization installation most masters are keyed by code plus organization. Join R5EVENTS to R5OBJECTS on both EVT_OBJECT = OBJ_CODE and EVT_OBJECT_ORG = OBJ_ORG; a join on code alone multiplies rows when the same equipment code exists in two organizations. Parts behave the same way with PAR_ORG. Cases (R5CASEMANAGEMENT, prefix CSM_) are a separate entity from work orders, used to manage a problem or investigation that may spawn several work orders, and they have their own statuses. If your site runs EAM archiving, old work orders leave R5EVENTS, so check where your archive lives before building a multi-year MTBF or cost trend.

Common join mistakes

The most frequent error is summing booked hours and estimated hours in the same join: R5ACTIVITIES and R5BOOKEDHOURS both sit below R5EVENTS, so joining both directly multiplies rows. Aggregate each in a subquery by work order first. The second is forgetting PPM_REVISION when joining R5PPMOBJECTS to R5PPMS, which duplicates PM lines after a PM is revised. The third is filtering on EVT_TYPE values copied from another site instead of EVT_RTYPE. Finally, R5EVENTS holds more than maintenance work orders, so check SELECT EVT_RTYPE, COUNT(*) FROM R5EVENTS GROUP BY EVT_RTYPE before writing totals.

Frequently Asked Questions

What is Infor EAM?

Infor EAM is an enterprise asset management and CMMS system covering equipment, work orders, preventive maintenance, labor, stores and purchasing. Hexagon acquired the product from Infor in 2021 and now sells it as HxGN EAM. The database schema still uses the R5 table naming described on this page.

Which table holds work orders in Infor EAM?

R5EVENTS holds the work order header, keyed by EVT_CODE. Activities are in R5ACTIVITIES (ACT_EVENT, ACT_ACT), booked labor in R5BOOKEDHOURS, parts issued to work orders in R5TRANSLINES via TRL_EVENT, and checklist items in R5ACTCHECKLISTS.

What is the difference between a case and a work order in Infor EAM?

A work order (R5EVENTS) is a unit of executable work with activities, labor and parts. A case (R5CASEMANAGEMENT) tracks a problem, request or investigation through its own statuses and log, and can lead to one or more work orders. Report them separately and link through the case to work order relationship.

How do I decode work order statuses in SQL?

Join R5UCODES where UCO_RENTITY = 'EVST' and UCO_CODE = EVT_STATUS to get the description and the system code in UCO_RCODE. Run SELECT * FROM R5UCODES WHERE UCO_RENTITY = 'EVST' once to see your installation's list before hardcoding any values.

If you want planners to ask your EAM database questions like these in plain English on your own servers, we can set up a read-only AI layer that respects EAM organizations and roles.

Talk to an Expert Explore More Free Tools