MyCSP Interface Process

The main setup required prior to running the cutover and interface files process determines how people with errors are processed.

Early in the submission process for the period, you will most likely need to review and correct errors before retrying the process on selected records in order to reduce your error count. Later in the monthly cycle, you will retry the process to include all records in order that the MyCSP interface file submission is complete. A new action parameter, the MyCSP interface process retains records in error parameter (halt action parameter) is provided to support this.

We recommend that you create a new configuration group prior to running the interface process and that you specify this group each time you submit the flow. You can use this configuration group to specify overrides for error handling.

MyCSP Interface Process Retains Records in Error (Halt Action Parameter)

The “MyCSP interface process retains records in error” process configuration parameter determines the behaviour of the interface flow if errors are found in the Archive MyCSP Information task.

Parameter Value is N

It is strongly recommended that you run the MyCSP interface process each month with the parameter set to N initially so that you can identify all records in error. After this, you can make corrections and retry without having to mark them for retry manually.

If the parameter is set to N (the default value):

The Archive MyCSP Information task has the status Completed. However, for any archive records in error, the top-level person action is marked as such on the View Process Results page, allowing you to more easily identify (and subsequently retry) those employees' records that are in error.

The application process marks the Halt Process on Error task status as Error. (If there are no errors on any of the archive records, this task is marked as Completed.)

You can review the Errors and Warnings report and correct the employee’s erroneous records in the live system.

After correcting the errors, you can retry the Archive MyCSP Information task (without having to manually mark the records for retry). This automatically reprocesses all person actions marked for retry or marked as errored. Before you run the Retry process, you can also update other employee’s records and manually mark them for retry; this will result in their records also being included in the Retry process.

This is an iterative process, and you can retry as many times as required until there are no errors. Once there are no errors, you can mark the task Review and Confirm MyCSP Audit Errors and Warnings as complete. The process then starts generating the interface files.

Warning: It’s recommended that you don’t skip the Halt Process on Error task. The task intentionally errors in order to prevent the generation of output files that would otherwise be incomplete.

Parameter Value is Y

Once you’ve run through an error checking and correction cycle, if you still find errors that you are unable to fix prior to generating the MyCSP Interface files, you can update the parameter to Y in order to generate all files including those with known errors.

If the parameter is set to Y or to the effective date of the process (in YYYYMM format):

The Archive MyCSP Information task has a status of Completed. For any archive records in error, the person actions are not marked in error.
The Halt Process on Error task is marked as Completed.
You can review the Errors and Warnings report.
Once you mark the Review and Confirm MyCSP Errors and Warnings task as complete, the process will continue to produce the MyCSP interface files, even if errors still exist. Employees that have errors will be included in the files.

Some additional considerations:

Don’t update MyCSP interface files manually. This is likely to cause inconsistencies and errors between the data you report and the information in the archive. Always make corrections and changes at source prior to running the Retry process.
If you wish to correct any errors when the parameter is set to Y, you must identify and mark the employee’s archive record manually for retry before you run the Retry process.
If you have not corrected your errors but have already marked the Review and Confirm MyCSP Errors and Warnings task as complete (and the process has therefore generated the MyCSP interface files), you must identify and manually mark the employee’s records for retry under each file generation task. Then you must identify and mark the employee’s records for retry under the Archive MyCSP Information task.

Process Configuration Group

It is recommended that you specify the error handling action parameters in a configuration group.

Create a new process configuration group for use with the action parameter and specify this group each time you submit the flow. If you change the action parameter value later and want the retry process to use it, it will only do so if you specified the process configuration group on the original submission.

Use the Payroll Process Configuration task to create a new process configuration group and add the action parameters to your configuration group as shown here:

Configuration Group Parameters

PARAMETER NAME	USER ACTION	DEFAULT VALUE	SUGGESTED OVERRIDE
Maximum Errors Allowed Number of consecutive actions that can return an error before the entire process is given a status of Error.	Increase this to a number that is large enough to ensure that all the MyCSP validation checks are performed together for employees in the Paypoint Code. Otherwise, unless the parameter has already been increased for your default configuration group, it will default to 20 (or to the "Chunk Size", if specified).	Default: CHUNK_SIZE or 20; minimum: 0	50
MyCSP interface process retains records in error If the parameter is set to Y, then the process will continue to produce the MyCSP interface files, even if errors still exist.	Add this parameter to your configuration group if you need to generate your interface files for submission despite them still containing errors. We recommend that you enter the month (in format YYYYMM) of the current interface process’s effective date (rather than entering value Y). A date override means that the parameter’s setting effectively reverts to N for the next run in the subsequent month. For example, if the effective date parameter in the Generate MyCSP Interface process is 31 January 2020, enter 202001 here. The parameter will default to N for the February 2020 run. If you set this override to Y, remember to change it to N in the subsequent month for the error correction cycle.	Null (N)	YYYYMM

PARAMETER NAME

USER ACTION

DEFAULT VALUE

SUGGESTED OVERRIDE

Maximum Errors Allowed Number of consecutive actions that can return an error before the entire process is given a status of Error.

Increase this to a number that is large enough to ensure that all the MyCSP validation checks are performed together for employees in the Paypoint Code.

Otherwise, unless the parameter has already been increased for your default configuration group, it will default to 20 (or to the "Chunk Size", if specified).

Default:

CHUNK_SIZE

or 20;

minimum: 0

MyCSP interface process retains records in error If the parameter is set to Y, then the process will continue to produce the MyCSP interface files, even if errors still exist.

Add this parameter to your configuration group if you need to generate your interface files for submission despite them still containing errors.

We recommend that you enter the month (in format YYYYMM) of the current interface process’s effective date (rather than entering value Y). A date override means that the parameter’s setting effectively reverts to N for the next run in the subsequent month. For

example, if the effective date parameter in the Generate

MyCSP Interface process is 31 January 2020, enter 202001 here. The parameter will default to N for the February 2020 run.

If you set this override to Y, remember to change it to N in the subsequent month for the error correction cycle.

Null (N)

YYYYMM