Employee Interface: Table Driven Method

Use the Employee Interface to load PENTA Employee information using data from external applications. Information you load using this interface adds to or updates the data already stored in PENTA.

Data files you load must have Request Types assigned to the E Interface Type.

If PENTA is unable to load an individual row, it bypasses that set of Employee information and moves on to the next (unless you set up defaults and cross-references). It creates or updates Employees using the accepted rows from the file. It notes the rejected rows and does not load them into PENTA.

Limitations & Restrictions

The types of non-PENTA Employee entries and the extent to which you can maintain the related information are limited.

The interface accepts an Employee record without validating that all the necessary Employee sub-records are in the data file and processed. For example, a data file may contain all the personal data about an Employee but not the pay rate information. PENTA still accepts and loads the Employee information but provides a warning message to inform the user of the situation.

Where to View Loaded Data

You can review interfaced data in the Employee Payroll Information window.

Available Tables

Badge Detail Record

After interfacing employee badge data, you can review it in the Employee Payroll Information window’s Badge Information pop-up window or the Employee HR Information window’s Badges tab.

The following information relates to the INTR_HR_BADGE table.

Column

Entry

Format

Description

Column

Entry

Format

Description

INTR_RQST_ID

Req

C! 13

An interface request value that you enter to initiate the interface process. The value must be consistent for all records PENTA should process together.

SEQ_NUM

Req

I 10

Sequence number uniquely identifying this row within interface request.

EMP_ID

Key

X

Id of the employee associated with the BADGE_ID.

ACTIVITY_CD

Key

C! 1

Required for all activity. Possible values are:

  • A (Add) – If the BADGE_ID already exists, PENTA records an error.

  • C (Change) – Update an existing record. If the column cannot be updated, PENTA records an error.

  • D (Delete) – Delete the record. If the record does not exist or was not created by the interface, PENTA records an error.

  • U (Update) – Add if the record does not exist and update if the record already exists, replacing any supplied column in the existing record.

BADGE_ID

Req

C! 30

ID of the badge associated with the EMP_ID. You cannot assign the same BADGE_ID to multiple employees.

D_ASSIGNED_DATE

Req

D

The date the BADGE_ID was assigned to the EMP_ID.

RECORD_NUM

Opt

I 10

Do not assign this value. PENTA assigns this record number, which you can use to identify records with errors or warning messages.

USER_ID

Req

C 6

Id of the employee performing the load process. This user_id must exist in PENTA.

MODIFICATION_DATE

Opt

D

This defaults as the current date. This column contains the date that the record is marked as modified in the database once the process initiates and completes.

BN Tax Detail Record

The following information relates to the INTR_HR_BNTAX table.

Column

Entry

Format

Description

Column

Entry

Format

Description

INTR_RQST_ID

Req

C! 13

The interface request value that you enter to initiate the interface process. The value must be consistent for all records PENTA should process together.

SEQ_NUM

Req

I 10

Sequence number uniquely identifying this row within interface request.

EMP_ID

Key

X

The Id of the employee associated with the BN Tax Account record.

ACTIVITY_CD

Key

C! 1

Required for all activity. Possible values are:

  • A (Add) – Adds the record to the database. PENTA provides an error message if the record already exists in the database.

  • C (Change) – Update an existing record. If the column is not updateable, PENTA records an error.

  • U (Update) – Add if the record does not exist and update if the record already exists, replacing any supplied column in the existing record.

D_EF