My Oracle Support Banner

PQSSNCST For MT192, Cross Border Contract Reference Number Field Incorrect (Doc ID 2686506.1)

Last updated on JULY 01, 2020

Applies to:

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

Symptoms

On : 14.3.0.0.0 version, Implementation Support

ACTUAL BEHAVIOR
---------------
In PQSSNCST, For MT192, 'Cross Border Contract Reference Number' field should be displayed in MT103 Transaction Reference instead of Source Reference
Incoming n99, n96, n92 messages transaction reference number are not getting linked to DCN in cross border contract reference number field when transactions are passed in PQSSNCST.

EXPECTED BEHAVIOR
-----------------------
Incoming n99, n96, n92 messages transaction reference number should get linked to DCN in cross border contract reference number field when transactions are passed in PQSSNCST.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1. Inject a incoming MTn92/n96/n99
2. Go to PQSSNCST and check cross border contract reference number field
3. Source reference number is populated instead of transaction reference number
4. Go and force pass in Sanction with DCN
5. Still Source reference number is populated instead of transaction reference number

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot get DCN

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
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.