HRMS IE SEPA XML File - EndToEndId Tag Value Is Not Unique (Doc ID 2081130.1)

Last updated on JANUARY 10, 2017

Applies to:

Oracle HRMS (Ireland) - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms


Find that there is a problem with the XML file for Danske bank

Running IE SEPA XML File and Report to produce payments XML file for Danske Bank

The tag is on each payment record for each employee.
This tag must always contain a Unique value, even across all payroll files from multiple payrolls and multiple payroll runs.

Uploading sample XML file produced. Each employee payment has this tag setup on it

Ex Gratia Payroll-5450252

The Value is made from the Payroll Name concatenated with the Payroll Action ID.

The Assignment Action ID is not Unique enough, as an employee can have a payment to more than one back account in a payroll run.

There is a Pre_Payments_id in the Pay_Pre_Payments table. This looks to be always Unique.
Perhaps a Payroll Action ID concatenated with this PrePayments ID could work as always been Unique
 


-- Expected Behaviour
The EndToEndId must be unique for each payment over a three month period.

 -- Steps
The issue can be reproduced at will with the following steps.
1. Ran payroll processing
2. Ran the output file for danske bank
3. it was returned with the following comments :

From: ****danskebank.dk]
To: ****
Subject: Re: VIP daa : ExGratia Full Payroll XML test file

Hi,

I have tested the files.

PY7383686.XML validated fine, but all but one payment was rejected as you did not have unique EndToEndId's for each payment.
The EndToEndId must be unique for each payment over a three month period.


Chief Integration Architect



Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms