OBPM 14.1 :: SDD Transactions Are Having Queue Code TR After Reject-CMPL Response From GSMOS
(Doc ID 2495163.1)
Last updated on DECEMBER 18, 2020
Applies to:Oracle Banking Payments - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
On : 184.108.40.206.0 version, Implementation Support
OBPM 14.1 PS11 :: SDD transactions are having Queue Code TR after Reject-CMPL response from GSMOS
SDD transactions are having Queue Code as TR in PCDIVIEW screen after receiving a response to the sanction request as FAIL. The concerned DD transaction is not present in TR. The only issue is that the Queue code in PCDVIEW is set as TR instead of ##
Steps To Reproduce:
1. In the PMDSNCKM screen, Status Mapping tab, Map the status FAIL to Auto Cancel.
2. Create a SDD transaction through PACS003 File Upload in such a way that the transaction ends up in Sanction Queue.
2. Provide a FAIL response to the sanction request by injecting the response in the sanction queue in middleware
3. Verify the transaction Details in PCDIVIEW.
The Queue Code field in PCDIVIEW is marked as TR even though the transaction cannot be found in TR.
The Queue Code field in PCDIVIEW should be marked as ##
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