Do Not Group Settlements by Bank Charge Bearer Code For SEPA Transactions (Doc ID 2026991.1)

Last updated on SEPTEMBER 02, 2016

Applies to:

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

Symptoms

The Create Settlement Process seems to group settlements incorrectly for the SEPA Direct Debit template, IBY_SEPA_DD_CORE_3_3_USTD.xsl.  After further investigation, it was found that this is occurring because the system groups
by bank charge bearer code.

After Patch 16730344:R12.IBY.B (ibyteftb.pls 120.31.12010000.23), transactions will have the same (LOGICAL_GROUP_REFERENCE) if they have the same values in the following columns :

ORG_ID
PAYEEINSTRID
CURRENCYNAMECODE
SETTLEDATE
LEGAL_ENTITY_ID
BANK_CHARGE_BEARER_CODE
SEQ_TYPE
SERVICE_LEVEL
LOCALINSTR
CATEGORY_PURPOSE

This logical grouping behavior (i.e. including bank_charge_bearer_code) is not relevant for SEPA payments. In SEPA no bank charges exist for transactions. Such logical Grouping makes only sense for EFT payments like SWIFT. From a functional perspective it makes no sense to take it into account for SEPA.

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