PAENCUMBER – No description in the Lawson data dictionary

System
Personnel (PA)
Prefix
PEN
Primary key
COMPANY, POSITION, PROCESS-LEVEL, DEPARTMENT, JOB-CODE, EMPLOYEE, GLT-OBJ-ID, ATN-OBJ-ID
Fields
14
Updated by
2 programs
Referenced by
35 programs

PAENCUMBER is a Lawson Personnel table (prefix PEN); no description in the lawson data dictionary. It is indexed by COMPANY, POSITION, PROCESS-LEVEL, DEPARTMENT, JOB-CODE, EMPLOYEE, GLT-OBJ-ID, ATN-OBJ-ID (PENSET1); alternate indexes: PENSET2, PENSET3 and PENSET4. It is related 1:1 to ACACTIVITY, ACCOMMITX, PRSYSTEM, DEPTCODE, EMPLOYEE, GLCOMMITX, JOBCODE and PAEMPLOYEE and 1:M to PAPOSITION. It is updated by PA182 and PA82.1 and referenced by BN305, HR00.1, HR01.1, HR02.1, HR11.1, HR11.2, HR11.4, HR28.1 and 27 more. The table has 14 fields, 4 indexes and 10 documented relations.

About PAENCUMBER

No description in the Lawson data dictionary.

Fields (14)

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

Field / columnTypeDescription & valuesUpdated by
PEN-COMPANY PK
COMPANY
Numeric 4PA182
PEN-POSITION PK
POSITION
Alpha 12Contains the user-defined code that represents a position in the company.PA182
PEN-PROCESS-LEVEL PK
PROCESS_LEVEL
Alpha 5PA182
PEN-DEPARTMENT PK
DEPARTMENT
Alpha 5Contains the department.PA182
PEN-JOB-CODE PK
JOB_CODE
Alpha 9Contains a user-defined code that represents a type of job.PA182
PEN-EMPLOYEE PK
EMPLOYEE
Numeric 9Contains the employee number. Each person employed by the company is assigned a unique number. The system uses the employee number to correlate all of the information related to that person.PA182
PEN-GLT-OBJ-ID PK
GLT_OBJ_ID
Numeric 12This is the object identifier. It is used to relate commitments or posted transactions back to the originating subsystems. Each subsystem record that is updated as a commitment or posted transaction is assigned an object identifier. The object identifier is maintained in the subsystem files and in the Activity Commitments Detail and Activity Transaction files. The object identifier is a unique key used to drill back from Activity Management to the subsystems.PA182
PEN-ATN-OBJ-ID PK
ATN_OBJ_ID
Numeric 12This is the object identifier. It is used to relate commitments or posted transactions back to the originating subsystems. Each subsystem record that is updated as a commitment or posted transaction is assigned an object identifier. The object identifier is maintained in the subsystem files and in the Activity Commitments Detail and Activity Transaction files. The object identifier is a unique key used to drill back from Activity Management to the subsystems.PA182
PEN-ENCUMBER-SAL
ENCUMBER_SAL
Signed 13.2Contains the sum of all wage amounts from the time records for pay codes tied to this pay summary group.PA182
PEN-ENCUMBER-FRNG
ENCUMBER_FRNG
Signed 13.2Contains the sum of all wage amounts from the time records for pay codes tied to this pay summary group.PA182
PEN-ACTIVITY
ACTIVITY
Alpha 15Activities are the processes or procedures that produce work. Cost objects (products, services, customers, and so on) are the reasons for performing the activity.PA182
PEN-DATE-STAMP
DATE_STAMP
Numeric 8 (yyyymmdd)This field contains the server date (month, date, and year) of the last change to this record.PA182
PEN-SHORT-NAME-CND
SHORT_NAME_CND
Derived
PEN-LABEL-NAME-1
LABEL_NAME_1
Derived

Indexes (4)

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

IndexKeysFlagsConditionUsed in
PENSET1COMPANY, POSITION, PROCESS-LEVEL, DEPARTMENT, JOB-CODE, EMPLOYEE, GLT-OBJ-ID, ATN-OBJ-IDPrimaryHR00.1, HR01.1, HR02.1, LT101, LT111, PA02.1, PA182, PA502 +1 more
PENSET2COMPANY, EMPLOYEE, POSITION, PROCESS-LEVEL, DEPARTMENT, JOB-CODE, GLT-OBJ-ID, ATN-OBJ-IDBN305, HR11.1, HR11.2, HR11.4, HR28.1, HR511, LT101, LT111 +22 more (list truncated in source)
PENSET3GLT-OBJ-IDSubsetWhere GLT-OBJ-ID != Zeroes
PENSET4ATN-OBJ-IDSubsetWhere ATN-OBJ-ID != Zeroes

Relations

One to one (9) — lookups and parents

RelationTableRulesConditionField map
ActivityACACTIVITYRequiredWhen PEN-ACTIVITY != SpacesPEN-ACTIVITYACV-ACTIVITY
Atn Obj IdACCOMMITXRequiredWhen PEN-ATN-OBJ-ID != ZeroesPEN-ATN-OBJ-IDMIX-ATN-OBJ-ID
CompanyPRSYSTEMRequiredPEN-COMPANYPRS-COMPANY, SpacesPRS-PROCESS-LEVEL
DepartmentDEPTCODERequiredWhen PEN-DEPARTMENT != SpacesPEN-COMPANYDPT-COMPANY, PEN-PROCESS-LEVELDPT-PROCESS-LEVEL, PEN-DEPARTMENTDPT-DEPARTMENT
EmployeeEMPLOYEERequiredPEN-COMPANYEMP-COMPANY, PEN-EMPLOYEEEMP-EMPLOYEE
Glt Obj IdGLCOMMITXRequiredWhen PEN-GLT-OBJ-ID != ZeroesPEN-GLT-OBJ-IDGOX-GLT-OBJ-ID
Job CodeJOBCODERequiredWhen PEN-JOB-CODE != SpacesPEN-COMPANYJBC-COMPANY, PEN-JOB-CODEJBC-JOB-CODE
PaemployeePAEMPLOYEERequiredPEN-COMPANYPEM-COMPANY, PEN-EMPLOYEEPEM-EMPLOYEE
Process LevelPRSYSTEMRequiredWhen PEN-PROCESS-LEVEL != SpacesPEN-COMPANYPRS-COMPANY, PEN-PROCESS-LEVELPRS-PROCESS-LEVEL

One to many (1) — child tables

RelationTableRulesConditionField map
PositionPAPOSITIONRequiredWhen PEN-POSITION != SpacesPEN-COMPANYPOS-COMPANY, PEN-POSITIONPOS-POSITION, POS-EFFECT-DATE

Programs

Updated by (2)

Referenced by (35)