R12: AR/IBY: When First SEPA Direct Debit Is Reversed, Expect Next Direct Debit To Have SEQ_TYPE FRST Not RCUR (Doc ID 1512140.1)

Last updated on SEPTEMBER 02, 2016

Applies to:

Oracle Receivables - Version 12.1.1 and later
Oracle Payments - Version 12.1.1 and later
Information in this document applies to any platform.

Symptoms

When processing SEPA direct debits, Oracle is making use of the debit authorizations entered at the customer.  Based on the information entered there, Oracle is determining whether the direct debit is a first or recurring direct debit. When the direct debit is created, in the column SEQ_TYPE (iby_trxn_summaries_all) you are able to see the type of direct debit being made.
 
When Release 12 was first released, the behavior was as follows:

Oracle doesn't reverse the SEQ_TYPE of the customer when a reversal is taking place. So when a first direct debit is performed and later on reversed, then the next direct debit will still be a recurring.

Steps:

1. First direct debit remittance batch is created for a customer and settlement record is created in iby_trxn_summaries_all with SEQ_TYPE=FRST.

2. Receipt associated with that settlement record is then reversed in AR.

3. A new remittance batch is created with a transaction for the customer that had a reversal on the first direct debit. 

Settlement record in iby_trxn_summaries_all is having SEQ_TYPE = RCUR.  We would expect the record to be a First direct debit (SEQ_TYPE = FRST) because the original first direct debit was reversed.

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