My Oracle Support Banner

Issue With Queue Notifications For SEPA Transfers (Doc ID 2890255.1)

Last updated on AUGUST 22, 2022

Applies to:

Oracle Banking Payments - Version 14.5.0.0.0 to 14.5.0.0.0 [Release 14]
Information in this document applies to any platform.

Symptoms

On : 14.5.0.0.0 version, Implementation Support

ACTUAL BEHAVIOR
---------------
Issue with Queue Notifications for SEPA transfers

EXPECTED BEHAVIOR
-----------------------
For incoming SEPA payments with source EMS, the notification generated in the queue should contain all payment details, just as in the case of a SWIFT payment coming from SWIF source.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. At PMDSORCE [Source Maintenance] screen, we have ticked the "Notification Required" flag for source EMS, which is used for incoming SEPA payments, and for source SWIF, which is used for incoming SWIFT payments.
2. At PMDEXTNT [External Notification Queue Maintenance] screen, we have performed the exact same maintenance for both sources, SWIF and EMS.
3. Then, we perform one incoming SWIFT payment and one incoming SEPA payments.
4. The notifications are generated in the specified queue. But the notification for the SWIFT payment contains all details of the payment [SWIF source]. On the other hand, the notification for the SEPA payment contains no details of the payment, except for the Transaction Reference Number and the status of the transfer (for example, PAYMENT SUCCESS, FUTURE VALUED, PAYMENT CANCEL, etc.).

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


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