PAPOSRULE – Position Rules

System
Personnel (PA)
Prefix
PPR
Primary key
COMPANY, PROCESS-LEVEL, DEPARTMENT, EFFECT-DATE
Fields
38
Updated by
7 programs
Referenced by
120 programs

PAPOSRULE is the Position Rules table in Lawson Personnel (prefix PPR). It is indexed by COMPANY, PROCESS-LEVEL, DEPARTMENT, EFFECT-DATE (PPRSET1); alternate indexes: PPRSET2 and PPRSET3. It is related 1:1 to PRSYSTEM and DEPTCODE. It is updated by HR00.1, HR01.1, LP130, LP198, PA06.1, PA111 and PA182 and referenced by BN150, BN305, EXI2.1, EXI4.1, HC01.2, HCDL.1, HCEM.1, HR11.1 and 112 more. The table has 38 fields, 3 indexes and 3 documented relations.

About PAPOSRULE

The Position Rule file contains the position rules which have been defined for a company. Position rules are established for each company and can be changed at the process level or department level.

Fields (38)

Column = COBOL field name without the PPR- prefix, hyphens → underscores. Derived fields are computed by the application and are not stored.

Field / columnTypeDescription & valuesUpdated by
PPR-COMPANY PK
COMPANY		Numeric 4Contains the company number.BN150, EXI2.1, EXI4.1, LP130, PA06.1, PR128, PR131, PR132 +33 more
PPR-PROCESS-LEVEL PK
PROCESS_LEVEL		Alpha 5Contains the process level.PA06.1
PPR-DEPARTMENT PK
DEPARTMENT		Alpha 5Contains the department.PA06.1
PPR-EFFECT-DATE PK
EFFECT_DATE		Numeric 8 (yyyymmdd)Contains the effective date for the position rules.PA06.1, PA406
PPR-POS-USE
POS_USE		Numeric 1Contains the value that indicates whether position codes are used.
  • 1 Yes
  • 2 No
  • 3 Yes;blank allowed for req
PA06.1
PPR-EMP-POS-REL
EMP_POS_REL		Alpha 1Contains the value that indicates the relationship between an employee and a position code.
  • Y Yes
  • N No
PA06.1
PPR-AUTO-CNT
AUTO_CNT		Alpha 1Contains the value that indicates whether automatic counting is used.
  • Y Yes
  • N No
PA06.1
PPR-CNT-UPD-REQ
CNT_UPD_REQ		Numeric 2Contains the code that indicates whether an update is required to make assigned resource counts current.
  • 01 No Update Req;AutoCnt not used
  • 02 No Update Req;Counts Current
  • 03 Update Req;AutoCnt Chged to N
  • 04 Update Req;AutoCnt Chged to Y
  • 05 Update Req;Rule added
  • 06 Update Req;Rule deleted
  • 07 Update Required;Cnt Cat Chged
  • 08 Update Reqd;Mult Pos cnt chged
PA06.1, PA111
PPR-CNT-UPD-REASON
CNT_UPD_REASON		Alpha 15 (Lower Case)Contains the reason that an update is required to make assigned resource counts current.PA06.1, PA111
PPR-CNT-CAT
CNT_CAT		Numeric 1Contains a value that indicates which count category is used for counting head count and FTE in assigned resources.
  • 1 Position
  • 2 Process Level;Job
  • 3 Process Level;Dept;Job
PA06.1
PPR-CNT-MULT-HDCNT
CNT_MULT_HDCNT		Numeric 1Contains the value that indicates how the assigned resource head count should be calculated for an employee holding multiple positions.
  • 1 Primary Position Only
  • 2 All Positions
PA06.1
PPR-CNT-MULT-FTE
CNT_MULT_FTE		Numeric 1Contains the value that indicates how the assigned resource full time equivalent factor should be calculated for an employee holding multiple positions.
  • 1 Primary Position Only
  • 2 All Positions
PA06.1
PPR-EDIT-EMP
EDIT_EMP		Alpha 1Contains a Yes or No value that indicates whether count edits should be performed against budget when employee changes are made.
  • Y Yes
  • N No
PA06.1
PPR-EDIT-REQ
EDIT_REQ		Alpha 1Contains a Yes or No value that indicates whether count edits against budget should be performed when requisition data changes are made.
  • Y Yes
  • N No
PA06.1
PPR-EDIT-RESTRICT
EDIT_RESTRICT		Numeric 1Contains a Yes or No value that indicates whether head count and FTE are restricted to the amount budgeted for the count category. The system calculates variance from budget when you make changes such as opening a requisition, hiring a new employee, or transferring an employee to a new position. This rule indicates whether you are allowed to make changes that cause you to exceed your budget. Restrict to budget edits are not performed when you move an employee out of a position. For example, you are not required to equal budget when you terminate an employee.
  • 1 Must equal budget
  • 2 Can not exceed budget
  • 3 Can exceed budget
  • 4 Can't exceed ;allow other chgs
PA06.1
PPR-USE-AUTH
USE_AUTH		Alpha 1Contains a Yes or No value that indicates whether authorized counts should be used for calculating head count and FTE variance. Authorized counts are budgeted counts that have been adjusted during the fiscal period. With authorized counts you can change your original budget without overwriting the original budget figures. You select authorized counts when you want to maintain a history of the original budget counts that were approved. If you select No, original budget counts will be used to calculate variance. You can change budgeted counts throughout the fiscal year, but the original budgeted counts are overwritten by the new counts.
  • Y Yes
  • N No
PA06.1
PPR-EDIT-HDCNT
EDIT_HDCNT		Alpha 1Contains a Yes or No value that indicates whether head count should be edited against budget.
  • Y Yes
  • N No
PA06.1
PPR-EDIT-FTE
EDIT_FTE		Alpha 1Contains the Yes or No value that indicates whether FTE should be edited against budget.
  • Y Yes
  • N No
PA06.1
PPR-CNT-EMP
CNT_EMP		Alpha 1Contains a Yes or No value that indicates whether active employees should be included when calculating the total head count and FTE in PA11 (Assigned Resources). The total head count and FTE is compared to budget when performing edits. You assign a count value of active, not active, or excluded to each employee status code in PA03 (Employee Status Codes).
  • Y Yes
  • N No
PA06.1
PPR-CNT-INACT-EMP
CNT_INACT_EMP		Alpha 1Contains a Yes or No value that indicates whether employees who are not active should be included when calculating the total head count and FTE in PA11 (Assigned Resources). You assign a count value of active, not active, or excluded to each employee status code in HR03.1 (Employee Status Codes).
  • Y Yes
  • N No
PA06.1
PPR-CNT-REQ
CNT_REQ		Alpha 1Contains a Yes or No value that indicates whether counts for active requisitions should be included when calculating total head count and FTE in PA11 (Assigned Resources). You assign a user-defined requisition status in PA42 (Job Requisition) that indicates whether the requisition is active or inactive.
  • Y Yes
  • N No
PA06.1
PPR-MAX-HDCNT-CAT
MAX_HDCNT_CAT		Numeric 5Contains the maximum head count allowed by category. Head counts entered on requisition and budget records are edited against this value.PA06.1
PPR-MIN-FTE-CAT
MIN_FTE_CAT		Signed 11.6Contains the minimum allowable FTE per count category. The FTEs entered on requisition and budget records are edited against this amount. Zero displays as blank.PA06.1
PPR-MAX-FTE-CAT
MAX_FTE_CAT		Signed 11.6Contains the maximum allowable FTE per count category. The FTEs entered on requisition and budget records are edited against this amount. If you selected Yes in the Auto Count field, you must enter a value here. The maximum FTE by category must be greater than or equal to the minimum FTE by category. Zero displays as blank.PA06.1
PPR-MIN-FTE
MIN_FTE		Signed 11.6Contains the minimum allowable FTE for each requisition and for each position assigned to an employee. Zero is a valid value. It displays as blank.PA06.1
PPR-MAX-FTE
MAX_FTE		Signed 11.6Contains the maximum allowable FTE for each position assigned to an employee. The maximum FTE per employee per position must be greater than or equal to the minimum FTE. Zero displays as blank.PA06.1
PPR-MIN-FTE-ALL
MIN_FTE_ALL		Signed 11.6Contains the minimum allowable FTE allowable for an employee, considering all positions assigned to an employee. The minimum FTE for all positions must be greater than or equal to the minimum FTE per position. Zero is a valid value. It displays as blank.PA06.1
PPR-MAX-FTE-ALL
MAX_FTE_ALL		Signed 11.6Contains the maximum allowable FTE for an employee, considering all positions assigned to an employee. The maximum FTE for all positions must be greater than or equal to the maximum FTE per position. Zero displays as blank.PA06.1
PPR-APPROVED-DATE
APPROVED_DATE		Numeric 8 (yyyymmdd)Contains the date that indicates how far into the future budgets have been approved. If automatic counting is used, a date is required. Current budgets are defined and updated in PA70 (Position Budget) and PA71 (Job Budget). Future budgets are defined and updated in PA72 (Position Budget Plan) and PA73 (Job Budget Plan). The approved through date lets you differentiate between your current budget and a future budget that is defined as part of your budget planning process.PA06.1
PPR-DATE-STAMP
DATE_STAMP		Numeric 8 (yyyymmdd)Contains the date (month, day, and year) that changes were made to the record.PA06.1, PA111
PPR-TIME-STAMP
TIME_STAMP		Numeric 6 (hhmmss)Contains the time (hour, minute, and second) changes were made to the record.PA06.1, PA111
PPR-USER-ID
USER_ID		Alpha 10 (Lower Case)Contains the user ID of a person who has made changes to the record.PA06.1, PA111
PPR-PR-PAY-RATE
PR_PAY_RATE		Numeric 1Indicates the manner in which the pay rate defaults from positions.
  • 1 Ignore Positions
  • 2 Primary Position
  • 3 All Positions
PA06.1
PPR-PR-EXP-ACTIVTY
PR_EXP_ACTIVTY		Numeric 1Determines whether general ledger expenses and activities to default from positions.
  • 1 Ignore Positions
  • 2 Primary Position
  • 3 All Positions
PA06.1
PPR-PR-PL-DEPT
PR_PL_DEPT		Numeric 1Indicates whether time record entry to defaults from positions.
  • 1 Ignore Positions
  • 2 Primary Position
  • 3 All Positions
PA06.1
PPR-PR-JOB-SHIFT
PR_JOB_SHIFT		Numeric 1Indicates whether the job code and shift default from positions.
  • 1 Ignore Positions
  • 2 Primary Positions
  • 3 All Positions
PA06.1
PPR-PR-SCHEDULE
PR_SCHEDULE		Numeric 1Indicates whether the schedule, pay grade, and step default from positions.
  • 1 Ignore Positions
  • 2 Primary Position
  • 3 All Positions
PA06.1
PPR-PR-LOCATION
PR_LOCATION		Numeric 1—
  • 1 Ignore Postions
  • 2 Primary Position
  • 3 All Positions
PA06.1

Indexes (3)

Keys marked * are descending. Every documented Lawson index is unique unless flagged Duplicates; Subset indexes carry a Where condition.

IndexKeysFlagsConditionUsed in
PPRSET1COMPANY, PROCESS-LEVEL, DEPARTMENT, EFFECT-DATEPrimaryBN150, BN305, HC01.2, HCDL.1, HCEM.1, HR00.1, HR01.1, HR11.1 +22 more (list truncated in source)
PPRSET2COMPANY, PROCESS-LEVEL, DEPARTMENT, EFFECT-DATE*LP130, LP198, PA182, PA211, PR197
PPRSET3COMPANY, EFFECT-DATE*, PROCESS-LEVEL, DEPARTMENTBN150, BN305, HR11.1, HR11.2, HR11.4, HR28.1, HR511, LT101 +22 more (list truncated in source)

Relations

One to one (3) — lookups and parents

RelationTableRulesConditionField map
CompanyPRSYSTEMRequiredWhen (PPR-PROCESS-LEVEL = Spaces)PPR-COMPANY → PRS-COMPANY, Spaces → PRS-PROCESS-LEVEL
DepartmentDEPTCODERequiredWhen (PPR-DEPARTMENT != Spaces)PPR-COMPANY → DPT-COMPANY, PPR-PROCESS-LEVEL → DPT-PROCESS-LEVEL, PPR-DEPARTMENT → DPT-DEPARTMENT
Process LevelPRSYSTEMRequiredWhen (PPR-PROCESS-LEVEL != Spaces)PPR-COMPANY → PRS-COMPANY, PPR-PROCESS-LEVEL → PRS-PROCESS-LEVEL

Programs

Updated by (7)

Referenced by (120)