# Infor Lawson S3 HR and Payroll Table Reference > Source: https://netray.co/tools/infor-lawson-s3-hr-payroll-table-reference > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer The Lawson S3 Human Resources, Personnel Administration, Payroll, Benefits and Time Accrual tables with field prefixes, primary index keys and common joins. ## Category other-erp ## Erp Infor Lawson S3 ## Audience - HRIS analyst - Lawson developer - Payroll systems analyst - Report writer ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### Table **Key:** table **Type:** text #### System **Key:** system **Type:** text #### Description **Key:** description **Type:** text #### Field prefix **Key:** prefix **Type:** text #### Primary index keys **Key:** index **Type:** text #### Key reporting columns **Key:** cols **Type:** text #### Common join **Key:** join **Type:** text **Rows:** **Table:** EMPLOYEE **System:** HR **Description:** Employee **Prefix:** EMP- **Index:** EMPSET1: COMPANY, EMPLOYEE **Cols:** LAST-NAME, FIRST-NAME, EMP-STATUS, PROCESS-LEVEL, DEPARTMENT, JOB-CODE, DATE-HIRED, TERM-DATE, PAY-RATE **Join:** PAEMPLOYEE on COMPANY, EMPLOYEE **Table:** PAEMPLOYEE **System:** PA **Description:** Employee Personnel Information **Prefix:** PEM- **Index:** PEMSET1: COMPANY, EMPLOYEE **Cols:** BIRTHDATE, SEX, EEO-CLASS, SENIOR-DATE, LOCAT-CODE, WK-PHONE-NBR **Join:** EMPLOYEE on COMPANY, EMPLOYEE **Table:** PAEMPPOS **System:** PA **Description:** Employee Multiple Positions, Jobs **Prefix:** PEP- **Index:** PEPSET1: COMPANY, EMPLOYEE, POS-LEVEL, EFFECT-DATE **Cols:** POSITION, JOB-CODE, PROCESS-LEVEL, DEPARTMENT, FTE, END-DATE, PAY-RATE **Join:** PAPOSITION on COMPANY, POSITION **Table:** PAPOSITION **System:** PA **Description:** Positions **Prefix:** POS- **Index:** POSSET1: COMPANY, POSITION, EFFECT-DATE **Cols:** DESCRIPTION, POSIT-STATUS, JOB-CODE, PROCESS-LEVEL, DEPARTMENT, END-DATE **Join:** JOBCODE on COMPANY, JOB-CODE **Table:** JOBCODE **System:** HR **Description:** Job Code Parameters **Prefix:** JBC- **Index:** JBCSET1: COMPANY, JOB-CODE **Cols:** DESCRIPTION, JOB-CLASS, EEO-CAT, PAY-GRADE, EXEMPT, ACTIVE-FLAG **Join:** EMPLOYEE on COMPANY, JOB-CODE **Table:** DEPTCODE **System:** HR **Description:** Department **Prefix:** DPT- **Index:** DPTSET1: COMPANY, PROCESS-LEVEL, DEPARTMENT **Cols:** NAME, ACTIVE-FLAG, DEP-ACCT-UNIT, DEP-ACCOUNT **Join:** EMPLOYEE on COMPANY, PROCESS-LEVEL, DEPARTMENT **Table:** PRSYSTEM **System:** HR **Description:** HR Company and Process Levels **Prefix:** PRS- **Index:** PRSSET1: COMPANY, PROCESS-LEVEL **Cols:** NAME, PAYROLL-YEAR, BANK-CODE, ACTIVE-FLAG **Join:** EMPLOYEE on COMPANY, PROCESS-LEVEL **Table:** HRSUPER **System:** HR **Description:** Supervisors **Prefix:** HSU- **Index:** HSUSET1: COMPANY, CODE **Cols:** DESCRIPTION, EMPLOYEE, SUPER-RPTS-TO, ACTIVE-FLAG **Join:** EMPLOYEE on COMPANY and EMPLOYEE.SUPERVISOR = HRSUPER.CODE **Table:** PCODES **System:** HR **Description:** Human Resource Code **Prefix:** PCO- **Index:** PCOSET1: TYPE, CODE **Cols:** DESCRIPTION, ACTIVE-FLAG **Join:** Code fields on EMPLOYEE or PAEMPLOYEE, filtered by TYPE **Table:** PERSACTION **System:** PA **Description:** Personnel Action (pending) **Prefix:** PCT- **Index:** PCTSET1: COMPANY, ACTION-TYPE, EFFECT-DATE, ACTION-CODE, EMPLOYEE, ACTION-NBR **Cols:** REASON, NEW-VALUE, POSITION, JOB-CODE, USER-ID, APPROVAL-FLAG **Join:** EMPLOYEE on COMPANY, EMPLOYEE **Table:** PERSACTHST **System:** PA **Description:** Personnel Action History **Prefix:** PAH- **Index:** PAHSET1: COMPANY, EMPLOYEE, EFFECT-DATE, ACTION-CODE, ACTION-NBR **Cols:** ACTION-TYPE, REASON, USER-ID, DATE-STAMP, OBJ-ID **Join:** HRHISTORY on COMPANY, EMPLOYEE and ACT-OBJ-ID = OBJ-ID **Table:** HRHISTORY **System:** HR **Description:** HR History (field-level change history) **Prefix:** HRH- **Index:** HRHSET1: COMPANY, EMPLOYEE, OBJ-ID, FLD-NBR, BEG-DATE, SEQ-NBR **Cols:** FLD-NBR, BEG-DATE, A-VALUE, N-VALUE, D-VALUE, ACT-OBJ-ID, USER-ID **Join:** PERSACTHST on ACT-OBJ-ID **Table:** HREMPUSF **System:** HR **Description:** Employee/Applicant User Fields **Prefix:** HEU- **Index:** HEUSET1: COMPANY, EMP-APP, EMPLOYEE, FIELD-KEY **Cols:** FIELD-KEY, A-FIELD, N-FIELD, D-FIELD **Join:** EMPLOYEE on COMPANY, EMPLOYEE **Table:** PAYMASTR **System:** PR **Description:** Employee Payment Master **Prefix:** PYM- **Index:** PYMSET1: COMPANY, EMPLOYEE, CHECK-ID **Cols:** CHECK-DATE, PER-END-DATE, GROSS-PAY, NET-PAY-AMT, CHECK-TYPE, CHECK-NBR, STATUS **Join:** PRTIME and PAYDEDUCTN on COMPANY, EMPLOYEE, CHECK-ID **Table:** PRCHECK **System:** PR **Description:** Employee Payment **Prefix:** PCH- **Index:** PCHSET1: BNK-ACCT-NBR, PRINT-TYPE, CHECK-NBR, CHECK-ID **Cols:** CHECK-DATE, CHECK-AMOUNT, STATUS, RECON-DATE, VOID-IND **Join:** PAYMASTR on COMPANY, CHECK-ID **Table:** PRTIME **System:** PR **Description:** Employee Pay/Hours History **Prefix:** PRT- **Index:** PRTSET1: COMPANY, EMPLOYEE, CHECK-ID, PAY-SUM-GRP, TIME-SEQ **Cols:** HOURS, RATE, WAGE-AMOUNT, TR-DATE, PAYROLL-YEAR, QUARTER, JOB-CODE, DEPARTMENT **Join:** PAYMASTR on COMPANY, EMPLOYEE, CHECK-ID **Table:** PRDISTRIB **System:** PR **Description:** Employee Payment Distribution **Prefix:** PRD- **Index:** PRDSET1: COMPANY, EMPLOYEE, CHECK-ID, OBJ-ID **Cols:** DIST-COMPANY, DST-ACCT-UNIT, DST-ACCOUNT, DST-SUB-ACCT, DIST-AMT, HOURS, GL-DATE **Join:** PAYMASTR on COMPANY, EMPLOYEE, CHECK-ID **Table:** PAYDEDUCTN **System:** PR **Description:** Employee Payment Deductions **Prefix:** PYD- **Index:** PYDSET1: COMPANY, EMPLOYEE, CHECK-ID, DED-CODE, EDM-SEQ-NBR, REPORT-ENTITY, BUS-NBR-GRP, QC-ENT-NBR-GRP, PROCESS-LEVEL, WORK-STATE **Cols:** DED-AMT, TAX-WAGES, WAGE-AMOUNT, CHECK-DATE, PAYROLL-YEAR, QUARTER **Join:** DEDCODE on COMPANY, DED-CODE **Table:** TIMERECORD **System:** PR **Description:** Employee Time Records (not yet paid) **Prefix:** TRD- **Index:** TRDSET1: COMPANY, EMPLOYEE, TIME-SEQ **Cols:** PAY-CODE, HOURS, RATE, WAGE-AMOUNT, TR-DATE, STATUS, BATCH-NBR **Join:** PRPAYCODE on COMPANY, PAY-CODE **Table:** PRPAYCODE **System:** PR **Description:** Pay Code **Prefix:** PCD- **Index:** PCDSET1: COMPANY, PROCESS-LEVEL, JOB-CODE, PAY-CODE **Cols:** DESCRIPTION, CALC-TYPE, PAY-SUM-GRP, NORM-RATE **Join:** TIMERECORD on COMPANY, PAY-CODE **Table:** DEDCODE **System:** PR **Description:** Deduction **Prefix:** DDC- **Index:** DDCSET1: COMPANY, DED-CODE **Cols:** DESCRIPTION, CALC-TYPE, DED-CLASS, TAX-CATEGORY, EFFECT-DATE, END-DATE **Join:** EMDEDMASTR on COMPANY, DED-CODE **Table:** EMDEDMASTR **System:** PR **Description:** Employee Deduction **Prefix:** EDM- **Index:** EDMSET1: COMPANY, EMPLOYEE, DED-CODE, SEQ-NBR **Cols:** EFFECT-DATE, END-DATE, NEXT-AMOUNT, BALANCE-AMT, DED-CYCLE **Join:** DEDCODE on COMPANY, DED-CODE **Table:** BENEFIT **System:** BN **Description:** Employee Benefit **Prefix:** BEN- **Index:** BENSET1: COMPANY, PLAN-TYPE, EMPLOYEE, START-DATE, PLAN-CODE **Cols:** STOP-DATE, COV-OPTION, COVER-AMT, EMP-PRE-CONT, EMP-AFT-CONT, COMP-CONT **Join:** EMPLOYEE on COMPANY, EMPLOYEE **Table:** TAEMPTRANS **System:** TA **Description:** Time accrual plan transactions per employee **Prefix:** TTR- **Index:** TTRSET1: COMPANY, EMPLOYEE, PLAN, EMPLOYEE-GROUP, POSITION, DATE, SEQ-NBR **Cols:** TRAN-TYPE, TA-HOURS, BALANCE-TYPE, STATUS **Join:** EMPLOYEE on COMPANY, EMPLOYEE **Notes:** Tables, prefixes and index keys checked against the LawsonGuru data dictionary for Lawson Applications 9.0. Screen tokens in the page text were checked against the same dictionary's program list. In the database, columns usually drop the prefix and use underscores (EMP-LAST-NAME becomes LAST_NAME). Confirm on your own product line, because Apps 10 and local changes can add fields. ## Content **Intro:** This reference lists the Lawson S3 HR, Personnel Administration, Payroll, Benefits and Time Accrual tables that HRIS analysts and developers query most, checked against the Lawson Applications 9.0 data dictionary. Each row gives the field prefix, the primary index keys, the columns used most in reports and the usual join. **Sections:** #### Where employee data lives **Body:** Core employee data is split across two tables keyed by COMPANY and EMPLOYEE. EMPLOYEE holds name, address, status, process level, department, job code, pay rate and hire and termination dates. PAEMPLOYEE holds personnel details such as birth date, EEO class, seniority date and phone numbers. Most HR reports start with EMPLOYEE joined to PAEMPLOYEE on both keys. Position data sits in PAEMPPOS, effective-dated by POS-LEVEL and EFFECT-DATE, so filter for the current row with END-DATE or the latest effective date. Codes used on employee records, such as location or EEO values, are described in PCODES by TYPE and CODE. #### Personnel actions and history **Body:** Personnel actions entered on PA52.1 Individual Action are held in PERSACTION while they are pending, keyed by company, action type, effective date, action code, employee and action number. When an action is processed, it is recorded in PERSACTHST, and the field-level before and after values go to HRHISTORY, linked through ACT-OBJ-ID. To audit a pay change, start from PERSACTHST for the employee and action code, then read HRHISTORY rows with the matching ACT-OBJ-ID. HR11.1 Employee is the main employee maintenance screen. It updates EMPLOYEE and PAEMPLOYEE directly, which is why some changes appear in HRHISTORY without a personnel action. **Bullets:** - HR11.1 Employee: EMPLOYEE, PAEMPLOYEE - PA52.1 Individual Action: PERSACTION, then PERSACTHST - PA02.1 Position: PAPOSITION - HR04.2 Human Resource Codes: PCODES - PR14.1 Employee Deduction: EMDEDMASTR #### Payroll history vs time records **Body:** TIMERECORD holds time that has been entered but not yet paid. PR36.1 Time Record Entry and interfaces write to it, and the payroll cycle reads it. After PR140 Earnings and Deductions Calculation and PR197 Payroll Close, paid history lives in PAYMASTR (one row per payment, keyed by COMPANY, EMPLOYEE and CHECK-ID), PRTIME (pay and hours lines), PAYDEDUCTN (deduction amounts) and PRDISTRIB (GL distribution). PRCHECK holds the payment record, which PR160 Payment Print updates. For year-to-date earnings, sum PRTIME by PAYROLL-YEAR. For net pay and payment dates, use PAYMASTR. #### Employee Self Service and common mistakes **Body:** Employee Self Service pages read and update the same tables through Lawson forms and data calls, so the data an employee sees comes from EMPLOYEE, PAEMPLOYEE, EMDEDMASTR, BENEFIT and payroll history. A self-service change usually goes through the same validation as the matching form. The most common reporting mistakes are ignoring effective dating on PAEMPPOS and PAPOSITION, reading TIMERECORD as paid history, and joining PRTIME to PAYMASTR without CHECK-ID, which duplicates amounts. Payroll tables hold sensitive data, so use a read-only account and limit columns to what the report needs. **Cta:** If HR or payroll wants answers from Lawson in plain English without exporting sensitive data, we can set up a private assistant on your servers that respects Lawson security. **Faq:** #### What is the difference between EMPLOYEE and PAEMPLOYEE in Lawson? **Answer:** Both are keyed by COMPANY and EMPLOYEE. EMPLOYEE holds core HR and payroll attributes such as name, status, process level, department, job code and pay rate. PAEMPLOYEE holds personnel details such as birth date, EEO class, seniority date and phone numbers. Most reports join the two. #### Where does Lawson store paycheck history? **Answer:** Each payment is a row in PAYMASTR keyed by COMPANY, EMPLOYEE and CHECK-ID, with check date, gross and net pay. Pay and hours lines are in PRTIME, deductions in PAYDEDUCTN, and GL distributions in PRDISTRIB, all joined on the same three keys. PRCHECK holds the payment record. #### What data does Infor Lawson Employee Self Service use? **Answer:** Employee Self Service works on the same S3 tables as the HR and payroll forms: EMPLOYEE and PAEMPLOYEE for personal data, EMDEDMASTR for deductions, BENEFIT for benefits and PAYMASTR and PRTIME for pay history. Changes made in self service pass through the normal application validation. #### How do I find who changed an employee's pay rate? **Answer:** Read PERSACTHST for the employee and the action code your site uses for pay changes, then read HRHISTORY rows where ACT-OBJ-ID matches the action's OBJ-ID. HRHISTORY holds the field number, effective date, new value and USER-ID. Direct changes on HR11.1 can also appear in HRHISTORY. ## Search terms lawson hris software training, infor lawson employee self service, infor lawson software, infor lawson 10 user guide, lawson employee table, lawson paymastr table, lawson prtime table, lawson persaction table --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json