Skip to main content

Error: 'LGPS Data has not created'

When generating the LGPS report, the following error appears: 'LGPS Data has not created' or 'Failed :contrib rate ORA-01427: single-row subquery returns more than one row'.

O
Written by Onyema Onyejekwe
Updated over 2 months ago

If you encounter the error message while generating a Local Government Pension Scheme (LGPS) report, two main issues may be causing this problem:

  • There is duplicate data in the tiered rates of the pension scheme.

  • An adjustment to an employee's pension contributions was made using the Adjust Normal Amount feature, and the pay code used for this adjustment is the same as that used for the employee's main pension contributions.

We have compiled a list of possible causes and solutions. Please follow the steps below according to the identified issue.

๐Ÿ“ŒNote: We strongly recommend testing any configuration changes in your UAT environment and verifying the results before applying them to your Live system.


Duplicate data in tiered rates

First, check for duplicate data in the tiered rates of the pension scheme. The LGPS may contain duplicate entries for weekly rates or thresholds.

Example: Multiple entries exist with an effective date of 01-Apr-2025, a weekly threshold of ยฃ342.33, and a monthly threshold of ยฃ1483.41.

To resolve this, follow the steps below in Portal.

Identify the relevant pension schemes

Review the LGPS Log to determine which employee the ORA-01427 error pertains to. After locating the employee, check their pension scheme. To do this, follow these steps.

  1. Click Employee then in the search field, search for employee.

  2. Beside the relevant employee, click VIEW then click Pension.

  3. Beside the relevant pension, click the three dot icon then click Edit.

  4. Take note of the pension scheme for the employee.

Alternatively, you can check the pension schemes included in the LGPS report by following these steps.

  1. Click Local Government Pension Scheme (LGPS) then click Configure.

  2. Click Pension Scheme Identification then note the pension schemes that have LGPS enabled.

Delete duplicate rate in pension scheme settings

To delete a duplicate line, follow the steps below.

  1. Click Settings then under Codes, click Pension Scheme.

  2. In the Pension Code drop-down menu, select the relevant pension code.

  3. Click Next Page then beside the Banded Scheme Type, click Rates.

  4. At the end of the duplicate line, click the three-dot icon.

  5. Click Delete, then click Save.

  6. To save changes, click Save.

If the employee deductions for the affected pension schemes have already closed for the period, support will need to perform some updates to the data to allow the report to run for that closed period.

Please raise a new case online and reference this article title. When doing so, include the following details:

  • Payroll period

  • Pension scheme

  • Pension pay codes.

  • Affected thresholds


Adjust normal amount

If you made an adjustment to an employee's pension contributions using the Adjust Normal Amount feature, ensure that the pay code utilized for this adjustment is different from the pay code used for the employee's main pension contributions.

If the codes are the same, the LGPS generate data process may fail. To resolve this, follow the steps below in Portal.

Identify the relevant pension schemes

Review the LGPS Log to determine which employee the ORA-01427 error pertains to. Locate the employee and check their pension scheme. To do this, follow these steps.

  1. Click Employee then in the search field, search for employee.

  2. Beside the relevant employee, click VIEW then click Pension.

  3. Beside the relevant pension, click the three dot icon then click Edit.

  4. Take note of the pension scheme for the employee.

Alternatively, you can check the pension schemes included in the LGPS report by following these steps.

  1. Click Local Government Pension Scheme (LGPS) then click Configure.

  2. Click Pension Scheme Identification then take note of the pension schemes that have the LGPS enabled.

Update pension scheme settings

Update the pension scheme settings to ensure that a distinct pay code is used for adjustments, separate from the pay code used for main/tiered pension contributions.

To do this, follow these steps.

  1. Click Settings then under Codes, click Pension Scheme.

  2. From the Pension Code dropdown menu, select the relevant pension code.

  3. Under the Employee Pay Codes, review the pre-tax adjustment pay code.

    ๐Ÿ“ŒNote: This will be used for pension adjustments via the Adjust Normal Amount feature.

  4. Under the Employee Pay Codes, review the Deduction 1, Deduction 2, and Deduction 3 Pay Codes fields.

    ๐Ÿค“Tip: These are used for main pension contributions.

  5. If the pre tax adjustment pay code is the same as the Deduction 1, Deduction 2 or Deduction 3 pay codes, update the Pre Tax Adjustment field to a different pay code.

  6. You might need to set up a new pay code for this.

  7. Repeat these steps under the Employer Pay Codes section.

    ๐Ÿ“ŒNote: The pay code in the deduction field is used for main pension contributions. The pay code used in the adjustment field is used for pension adjustments. Do not use the same pay code for both deductions and adjustments.

  8. To save changes, click Save.

If the employee deductions for the affected pension schemes have already closed for the period, support will need to perform some updates to the data to allow the report to run for that closed period.

Please raise a new case online and reference this article title. When doing so, include the following details:

  • Payroll period

  • Pension scheme

  • Pension pay codes

Did this answer your question?