Timeclock Employee Id Interface
- Joseph Wall (Deactivated)
Issue/Symptom/Question
How are employee identifiers that are used for the timeclock interfaced into PENTA?
Applies To
Timeclock
Employee Timeclock Identifier
Resolution/Fix/Answer
The PENTA Interface for Timeclock Id can be used:
The new table for table driven interfaces is INTR_HR_TIMECLKID
| INTR_RQST_ID | Required | NOT NULL | VARCHAR2(13) |
| SEQ_NUM | Required | NOT NULL | NUMBER(10) |
| EMP_ID | Required | NOT NULL | NUMBER(3) |
| ACTIVITY_CD | Required | NOT NULL | VARCHAR2(1) |
| TIMECLK_EMP_ID_TYPE_CD | Required | NOT NULL | VARCHAR2(3) |
| LONG_KEY | Required - must be Unique | NOT NULL | VARCHAR2(2000) |
| DESCR_2000 | Optional | VARCHAR2(2000) |
The Pipe delimited flat file record looks like this:
[emp_id]|TIMECLKID|[activity_cd]|[timeclk_emp_id_type_cd]|[long_key(the ID)]|[descr_2000]|
Activity code behavior is standard for the employee interface:
- (A)dd
- (U)pdate, or add if record doesn't exist
- (C)hange
- (D)elete
The ID type must be one of the values in TIMECLK_EMP_ID_TYPE table.
TIMECLK_EMP_ID_TYPE_CD:
PIN PIN
QRC QR Code
BIO Biometric Scan
- An employee can only have one key(ID) of each type.
- Type/key combinations must be unique across all employees, but the same key can be used for different types.
- Employee ID + Type is the key that is used when looking for a record to update or delete. Key and description are ignored when deleting.
- The key is free form and required.
- The description is free form and optional.
- The key is not encrypted.
The resulting records after the interface completes are maintained in TIMECLK_EMP_ID
 Pipe Delimited Example for QR Code and PIN for an employee:
123|TIMECLKID|U|QRC|1234567890|QR Code for Emp 123| or if no description 123|TIMECLKID|U|QRC|1234567890||
123|TIMECLKID|U|PIN|123456|PIN Code for Emp 123|
NOTE: With the requirement that the PIN and QRC being unique, do not include the record in the file unless loading a unique code. Including the record with a blank or null code will cause an error in the interface because blank or null is not unique.