# Infor EAM / HxGN EAM Work Management Table Reference (R5 Tables) > Source: https://netray.co/tools/infor-eam-work-management-table-reference > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer The R5 tables behind work orders, equipment, PM schedules, labor, stores and cases in Infor EAM 11.x and HxGN EAM 12, with key columns and common joins. ## Category maintenance ## Erp Infor EAM ## Audience - EAM administrator - Report developer - Maintenance systems analyst ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### Table **Key:** table **Type:** text #### Area **Key:** area **Type:** text #### Holds **Key:** description **Type:** text #### Key columns **Key:** keys **Type:** text #### Useful reporting columns **Key:** reporting **Type:** text #### Common join **Key:** join **Type:** text **Rows:** **Table:** R5EVENTS **Area:** Work orders **Description:** Work order and event header, one row per work order **Keys:** EVT_CODE (EVT_ORG for organization) **Reporting:** 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 **Join:** EVT_OBJECT + EVT_OBJECT_ORG to R5OBJECTS; EVT_PPM to R5PPMS; EVT_MRC to R5MRCS **Table:** R5ACTIVITIES **Area:** Work orders **Description:** Activities (operations) on a work order, with trade and estimated hours **Keys:** ACT_EVENT, ACT_ACT **Reporting:** ACT_TRADE, ACT_EST, ACT_MRC, ACT_TASK **Join:** ACT_EVENT to R5EVENTS.EVT_CODE; ACT_TRADE to R5TRADES **Table:** R5BOOKEDHOURS **Area:** Labor **Description:** Labor hours booked against work order activities **Keys:** BOO_CODE **Reporting:** BOO_EVENT, BOO_ACT, BOO_PERSON, BOO_HOURS, BOO_DATE **Join:** BOO_EVENT + BOO_ACT to R5ACTIVITIES; BOO_PERSON to R5PERSONNEL **Table:** R5ACTCHECKLISTS **Area:** Work orders **Description:** Checklist items on work order activities **Keys:** ACK_CODE **Reporting:** ACK_EVENT, ACK_ACT, ACK_DESC, ACK_COMPLETED **Join:** ACK_EVENT + ACK_ACT to R5ACTIVITIES **Table:** R5OBJECTS **Area:** Assets **Description:** Equipment master: assets, positions, systems and locations **Keys:** OBJ_CODE, OBJ_ORG **Reporting:** OBJ_DESC, OBJ_OBTYPE, OBJ_CLASS, OBJ_MRC, OBJ_STATUS, OBJ_PARENT, OBJ_SERIALNO, OBJ_MANUFACT, OBJ_LOCATION **Join:** Joined from EVT_OBJECT, PPO_OBJECT, REA_OBJECT, CSM_OBJECT (always with the _ORG column) **Table:** R5READINGS **Area:** Assets **Description:** Meter readings recorded against equipment **Keys:** REA_OBJECT plus reading date **Reporting:** REA_DATE, REA_READING, REA_UOM **Join:** REA_OBJECT to R5OBJECTS; REA_UOM to R5UOMS **Table:** R5PPMS **Area:** Preventive maintenance **Description:** PM header: frequency and period unit of measure, revision controlled **Keys:** PPM_CODE, PPM_REVISION **Reporting:** PPM_DESC, PPM_FREQ, PPM_PERIODUOM, PPM_ORG **Join:** PPM_CODE + PPM_REVISION to R5PPMOBJECTS.PPO_PPM + PPO_REVISION **Table:** R5PPMOBJECTS **Area:** Preventive maintenance **Description:** PM schedule lines: which PM applies to which equipment and when it is next due **Keys:** PPO_PPM, PPO_REVISION, PPO_OBJECT, PPO_OBJECT_ORG **Reporting:** PPO_DUE, PPO_FREQ, PPO_PERIODUOM, PPO_ORG **Join:** PPO_OBJECT + PPO_OBJECT_ORG to R5OBJECTS **Table:** R5STANDWORKS **Area:** Preventive maintenance **Description:** Standard work orders used as templates **Keys:** STW_CODE **Reporting:** STW_DESC **Join:** Referenced by PM and work order setup **Table:** R5TASKS **Area:** Planning **Description:** Task plans (standard operations, instructions and materials) **Keys:** TSK_CODE **Reporting:** TSK_DESC **Join:** ACT_TASK to TSK_CODE **Table:** R5MRCS **Area:** Organization **Description:** Departments (maintenance responsibility centres) **Keys:** MRC_CODE **Reporting:** MRC_DESC, MRC_ORG, MRC_STORE **Join:** EVT_MRC, OBJ_MRC, ACT_MRC, PER_MRC to MRC_CODE **Table:** R5PERSONNEL **Area:** Labor **Description:** Employees who book hours and are assigned to work **Keys:** PER_CODE **Reporting:** PER_DESC, PER_TRADE, PER_MRC **Join:** BOO_PERSON to PER_CODE **Table:** R5TRADES **Area:** Labor **Description:** Trades (crafts) used to plan and book labor **Keys:** TRD_CODE **Reporting:** TRD_DESC **Join:** ACT_TRADE, PER_TRADE to TRD_CODE **Table:** R5CREWS **Area:** Labor **Description:** Crews of employees **Keys:** CRW_CODE **Reporting:** CRW_DESC **Join:** Crew employee and work order assignment tables **Table:** R5PARTS **Area:** Materials **Description:** Part master **Keys:** PAR_CODE, PAR_ORG **Reporting:** PAR_DESC, PAR_UOM, PAR_CLASS, PAR_COMMODITY **Join:** TRL_PART, STO_PART, ORL_PART, RQL_PART to PAR_CODE **Table:** R5STORES **Area:** Materials **Description:** Storerooms **Keys:** STR_CODE **Reporting:** STR_DESC, STR_ORG **Join:** STO_STORE, BIN_STORE, TRL_STORE to STR_CODE **Table:** R5BINS **Area:** Materials **Description:** Bins within a store **Keys:** BIN_STORE, BIN_CODE **Reporting:** BIN_STORE, BIN_CODE **Join:** BIN_STORE to R5STORES **Table:** R5STOCK **Area:** Materials **Description:** Part stock per store **Keys:** STO_PART, STO_PART_ORG, STO_STORE **Reporting:** STO_QTY **Join:** STO_PART to R5PARTS; STO_STORE to R5STORES **Table:** R5TRANSACTIONS **Area:** Materials **Description:** Store transaction headers (issues, returns, receipts, transfers) **Keys:** TRA_CODE **Reporting:** TRA_TYPE, TRA_DATE **Join:** TRA_CODE to R5TRANSLINES.TRL_TRANS **Table:** R5TRANSLINES **Area:** Materials **Description:** Store transaction lines, including parts issued to work orders **Keys:** TRL_TRANS plus line **Reporting:** TRL_PART, TRL_QTY, TRL_PRICE, TRL_EVENT, TRL_TYPE, TRL_STORE, TRL_DATE **Join:** TRL_EVENT to R5EVENTS.EVT_CODE; TRL_PART to R5PARTS **Table:** R5ORDERS **Area:** Purchasing **Description:** Purchase order headers **Keys:** ORD_CODE, ORD_ORG **Reporting:** ORD_STATUS, ORD_SUPPLIER **Join:** ORD_CODE + ORD_ORG to ORL_ORDER + ORL_ORDER_ORG **Table:** R5ORDERLINES **Area:** Purchasing **Description:** Purchase order lines **Keys:** ORL_ORDER, ORL_ORDER_ORG plus line **Reporting:** ORL_PART, ORL_ORDQTY, ORL_RECVQTY **Join:** ORL_PART to R5PARTS **Table:** R5REQUISITIONS **Area:** Purchasing **Description:** Requisition headers **Keys:** REQ_CODE **Reporting:** REQ_STATUS **Join:** REQ_CODE to R5REQUISLINES.RQL_REQ **Table:** R5REQUISLINES **Area:** Purchasing **Description:** Requisition lines **Keys:** RQL_REQ plus line **Reporting:** RQL_PART, RQL_QTY **Join:** RQL_PART to R5PARTS **Table:** R5CASEMANAGEMENT **Area:** Cases **Description:** Case management records, kept separate from work orders **Keys:** CSM_CODE, CSM_ORG **Reporting:** CSM_DESC, CSM_STATUS, CSM_MRC **Join:** CSM_OBJECT + CSM_OBJECT_ORG to R5OBJECTS **Table:** R5UCODES **Area:** Codes **Description:** User codes and their mapping to system codes (statuses, types) **Keys:** UCO_ENTITY, UCO_CODE **Reporting:** UCO_DESC, UCO_RENTITY, UCO_RCODE, UCO_SYSTEM **Join:** Decode EVT_STATUS with UCO_RENTITY = 'EVST' and UCO_CODE = EVT_STATUS **Table:** R5ORGANIZATION **Area:** Organization **Description:** Organizations in a multi-organization installation **Keys:** ORG_CODE **Reporting:** ORG_DESC **Join:** Every *_ORG column (EVT_ORG, OBJ_ORG, PAR_ORG) to ORG_CODE **Notes:** 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'. ## Content **Intro:** 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. **Sections:** #### How to use it **Body:** 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. **Bullets:** - 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 **Body:** 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 **Body:** 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 **Body:** 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. **Cta:** 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. **Faq:** #### What is Infor EAM? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms infor eam tables, infor eam r5events, infor eam database schema, infor eam cmms, infor eam asset management, infor eam case vs work order, hxgn eam tables, infor eam system --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json