Enables you to create the CSP data extract files.

Note: If you are an ASP customer, you must set up the relevant employer code on the structure unit before running the data extract using Maintain Structure Unit Basic Details. The MISC > PENSERVER > EMPLYR system parameter is set to ASP if you are an ASP customer.

The following data must be mapped prior to running the extract to enable ResourceLink pensions data to be read by CSP:

When you run this task, CSP Control Group Selection is displayed if you are an ASP customer to enable you to select a control group as the information needs to be recorded at control group level, not system level.

A dialog box is then displayed asking if you want to run the Initial Migration Routine. Click YES to continue.

Note: This functionality can be added to the scheduler via the HR140U31 task. You can configure the scheduler with the start date (the CSP run date if left blank), end date (today's date if left blank), year closed indicator, year closed and the group list you want to process - the group list is not required for direct customers as all employees are processed.

Extract Details

Extract Type

Display only. Indicates the extract type: Initial, Normal or Exception.

Start Run Date

Enter the date from which the data is processed when running the initial migration process. This is derived from the MISC > PENSERVER > STARTDATE system parameter which can be set by your system administrator.

End Run Date

Enter the date up to which the data is processed when running the initial migration process.

Sequence Number

Display only. The sequence number of the extract; this is 000 for the initial extract.

Year Closed

Enter Y if the pension year is closed to any further data submissions being made to CSP.

Year

Enter the year closed if you have entered Y in the Year Closed field.

Last Closed Year

Display only. The last year that was closed.

Click COMMIT to create the CSP data extract files.

The data is checked prior to extraction. The CSP data extract flat files are produced if no errors are present. If data errors are produced, the invalid records are listed in Processing Exceptions. You should correct the erroneous data in ResourceLink before rerunning the CSP data extract using the list of records in Processing Exceptions.

Note: The initial run builds the base records against which subsequent runs are checked. Whenever a new record is created, the base records are updated.

MD140S04