Export Process Details

The Export process includes three phases — select, compare, and export:

  • During the select phase, payroll data is retrieved from the PeopleSoft HCM tables.

  • During the compare phase, the selected data is compared against the data from the previous export run.

    The comparison phase identifies any data changes that have occurred since the last export.

  • During the export phase, the data is exported to either a flat file or a table.

A full-records export performs the select and export phases; all data is exported. A changes-only export performs the select, compare, and export phases; only data that has changed is exported.

PI_INRUN calls PIPINRUN

Export processing is based on the pay run ID and run number. For each pay run ID, PIPINRUN retrieves the company and pay group from the pay calendars. The company and pay group are used to verify the payroll interface definitions and to select the employees who will be processed.

PIPINRUN calls PIPCMPAR

First, PIPCMPAR verifies the payroll interface setup for the selected configuration ID:

  1. Using the company and pay group, PIPCMPAR obtains the configuration ID from the Pay Group table.

    Using the configuration ID, it retrieves the file definitions and the system ID from the Configuration table.

    1. For the selected system ID, PIPCMPAR verifies all records and fields in PS Tables table.

    2. For the selected system ID, PIPCMPAR verifies all fields in the Field Definition table.

    3. PICMPAR verifies that all the parameters defined in the Definition table are valid.

  2. Using the company and pay group, PIPCMPAR selects from the Job table all employees (with status values defined in the System table) with a matching company and pay group.

Second, PIPCMPAR performs the actual export process. The export process differs for full-records exports and changes-only exports.

  1. For a full-records export, PIPCMPAR does the following for each selected employee in the pay group:

    1. For each table defined in PS Tables, retrieves rows based on the where clause definition (as well as instance IDs, process IDs, and other information that is set up in the interface).

    2. Exports the results to tables PI_PARTIC and PI_PARTIC_EXPT in the format specified in the Definition table (LOG, PHY, CSV, and so on).

      Note:

      For full-records exports, all values are considered new, and therefore, changed. Flags in the PI_PARTIC and PI_PARTIC_EXPT tables are initialized to Y and 1.

  2. Changes-only export, PIPCMPAR, does the following for each selected employee in the pay group:

    1. For each table defined in PS Tables, retrieves rows based on the where clause definition (as well as instance IDs, process IDs, and other information that is set up in the interface).

    2. Compares the value of each field (and row, if designated) to the value that was sent in the last export (the previous run number).

    3. Exports the results to table PI_PARTIC and PI_PARTIC_EXPT in the format specified in the Definition table (LOG, PHY, CSV).

      Note:

      For changes-only exports, flags in the PI_PARTIC and PI_PARTIC_EXPT tables are set to Y and 1 if values change or to N and 0 if values do not change.

PIPINRUN calls PIPXPORT

PIPXPORT reads table PI_PARTIC_EXPT and writes the changed data to temporary table PI_EXTIO or PI_PARTIC_EXTBL.

Note:

If no changes occurred, table PI_EXTIO or PI_PARTIC_EXTBL is empty at the end of the export process.

PI_INRUN calls PI_EXTFL

When the export processing is finished, control returns to the Application Engine. PI_INRUN calls PI_EXTFL to create the export file.

PI_EXTFL does the following:

  1. For each row of data in table PI_EXTIO:

    Writes a line to the export file defined in the File Handle table for the file definition. The data is written in the character set defined on the PI System table (LOG, PHY, CSV, and so on).

  2. Deletes the contents of table PI_EXTIO.

  3. Deletes the run control record.