File Name Format Is Incorrect When Different Message Type Files Are Dispatched
(Doc ID 2987267.1)
Last updated on DECEMBER 28, 2023
Applies to:
Oracle Banking Payments - Version 14.7.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 14.7.0.3.0 version, Implementation Support
SDD file name format is incorrect when different message type files are dispatched
Scenario 1
ACTUAL BEHAVIOR
---------------
message type in filename is displaying incorrect. for both types, it is displaying as pacs002. even for pacs004 , filename is appended with pacs002 .
EXPECTED BEHAVIOR
-----------------------
Based on message type, filename should also append the same message type.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Upload pacs003 with 2 transactions and 2 collections are generated
2. Both moved to BO queue.
3. Cancel 1 transaction before settlement and pacs002 is ready for dispatch. and cancel 2nd one after settlement time and pacs004 also ready for dispatch.
4. Dispatch both file together.
Scenario 2
ACTUAL BEHAVIOR
---------------
Message type in filename is displaying incorrect. for both types, it is displaying as pacs003
EXPECTED BEHAVIOR
-----------------------
Based on message type, filename should also append the same message type. even for pacs002 , filename is appended with pacs003.
STEPS
-----------------------
1. Upload pacs003 and collections are generated. moved to BO queue , cancel transaction before settlement and pacs002 is ready for dispatch.
2. At the same time create outgoing SDD collection from PCDAOTXN. pacs003 is ready for dispatch.
3. System will bulk both message in single dispatch reference and dispatch both messages together.
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 |
References |