My Oracle Support Banner

BACS Payroll Program Erroring if it is Run after Running FPS Program (Doc ID 2585137.1)

Last updated on JUNE 07, 2021

Applies to:

Oracle HRMS (UK) - Version 12.1 HRMS RUP11 and later
Information in this document applies to any platform.

Symptoms

Problem Statement:

When attempting to run BACS report after running FPS (Full Payment Submission) process the following error occurs:

Too many rows returned for LPAD at line     of GEN_BACS_BODY  
Cause: The application dictionary has not been set up correctly. One of the SQL statements that it contains would cause more than one row to be select
or
Too many rows returned for LPAD at line     of MS_BACS_BODY
Cause: The application dictionary has not been set up correctly. One of the SQL statements that it contains would cause more than one row to be select

Steps to Reproduce:
The issue can be reproduced at will with the following steps:

  1. Run quick pay for an employee (or payroll run)
  2. Run pre-payments
  3. Run RTI - Full Payment Submission Process (FPS) 2019/20
  4. Run Oracle seeded program 'BACS'
  5. BACS errors if it is run after running FPS

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.