SEPA DD: ReqdColltnDt In Output File Is Different To Due Date Of Transaction (Doc ID 1929061.1)

Last updated on JANUARY 19, 2022

Applies to:

Symptoms

Find that requested collection date field in SEPA DD output file is different to due date of transaction.  When we generate a XML file, the value of the requested collection date is different to expected date (due date in AR transaction workbench).

Example:

From SEPA DD XML output file, we see  <ReqdColltnDt>2014-05-08</ReqdColltnDt>, whereas due date from AR transaction workbench is 31-MAY-2014 for this example.

<PmtInfId>...</PmtInfId>
<PmtMtd>DD</PmtMtd>
<BtchBookg>false</BtchBookg>
<NbOfTxs>31</NbOfTxs>
<CtrlSum>...</CtrlSum>
- <PmtTpInf>
- <SvcLvl>
<Cd>SEPA</Cd>
</SvcLvl>
- <LclInstrm>
<Cd>CORE</Cd>
</LclInstrm>
<SeqTp>RCUR</SeqTp>
- <CtgyPurp>
<Cd>SUPP</Cd>
</CtgyPurp>
</PmtTpInf>
<ReqdColltnDt>2014-05-08</ReqdColltnDt>
- <Cdtr>

Using IBY_SEPA_DD_CORE_3_3_STD.xsl 120.0.12010000.26

We are expecting the requested collection date to be the due date in AR transaction workbench (i.e. 31-MAY-2014 for this example).

Changes

Cause

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