Defining a New Import Interface Definition

This topic discusses how to set up a new import file definition. For this example, you use a physical, fixed-length data file to import pay period data into the PI_CHECK, PI_EARN_DETAIL, PI_DED_DETAIL, and PI_TAX_DETAIL import tables.

Basic File Layout

Header and footer records are optional. To use data that's not at the employee level, place it here. For examples, see the DETI sample data file header and footer.

Note:

You can map fields that are derived from the PeopleSoft pay calendar or that are derived during the Payroll Interface process. At the field level, select value as the type, and view the text list.

Record Identifiers

For each physical record to be read, set up an interface field as a record flag. On the Interface Field 1 page, enter value in the Type field and External Record Code in theText field. Then each record has a unique flag at the beginning of the input data record.

Sample Values

This table lists sample values:

Default Value Record Name Field Name

A

PI_CHECK

CHK01

B

PI_EARN_DETAIL

ERN01

C

PI_DED_DETAIL

DED01

D

PI_TAX_DETAIL

TAX01

Record Key Fields

Examine each PeopleSoft system record definition into which you want to import data. Examine the DETI sample data file and ensure that you map the same key fields from the data file into the Payroll Interface tables, as a minimum.

Sample Data File Layout

Each record is physical, with a fixed length, but the records do not have to be the same length. Enter the longest record length on the Definition Table component - Interface Definition File page, PI Record Length field.

Record A: Contains PI_EMPLID and all other data fields that are mapped to PI_CHECK. Key record fields are:

  • CHK01

  • Check Number

  • PI_EMPLID, as defined on the System Table component - Interface System Table 1, Employee Field ID field.

Record B, C, D, and subsequent records: These records do not need thePI_EMPLID field. The Import process uses the same Payroll Interface employee ID for these data records until it reads another record A with another Payroll Interface employee ID.

To process multiple records repeatedly, set the Definition Table component - Interface Definition Record page, Occur Ind field to Multi Recs to Single Defn Rec. For an example, see the DETI sample data file, Record ID DPE, Coded Hours.

Record B (Earn Detail)

ERN01 (RECORD)

Earn Type (NON KEY)

Earn Code (NON KEY)

Amount (NON KEY)

The data file might look like this:

A, Emplid, check nbr, data field, data field, etc.
B , earn type, code, amount
B, earn type, code, amount
B , earn type, code, amount
B, earn type, code, amount

Each subsequent record repeats many times as necessary (using Multi Recs to Single Defn Rec).

Record C (Deduction Detail)

DED01 (RECORD)

Ded Code (NON KEY)

Ded Amount (NON KEY)

The data file might look like this:

A, Emplid, check nbr, data field, data field, etc.
B , earn type, code, amount
B, earn type, code, amount
B , earn type, code, amount
B, earn type, code, amount
C, code, amount
C, code, amount
C, code, amount
C, code, amount
C, code, amount
C, code, amount

The PeopleSoft system imports subsequent records in the same way.