Book Transfer Transaction Failed To Come To OBPM When Acct Desc More Than 70 Char
(Doc ID 2678968.1)
Last updated on DECEMBER 18, 2020
Applies to:Oracle Banking Payments - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On : 220.127.116.11.0 version, Implementation Support
Book Transfer transaction failed to come to OBPM when Acct Desc more than 70 char
7 transactions not reaching to OBPM application in Canada branch. All these 7 transactions had come to OBPM through Single Payment Service request and all of them should have created Book Transfer transactions. But none of them were available any of the tables or screens. They were not even logged in pmtb_incoming_log table or any exception log table. After our analysis we found that issue was faced when Account description is more than 70 characters on External Account Maintenance screen STDCRACC.
System should have inserted account description in PBTB_TXN table by truncating account description value to 70 characters. After successful payment processing, Success JSON response should have been sent to external system who had sent Single Payment Service request.
The issue can be reproduced at will with the following steps:
1. Create any Account with account description more than 70 characters on STDCRACC screen.
2. Inject Single Payment Service request by passing this account under "cdtraccothrid" tag. This Single Payment Service request should derive INTERNAL network.
3. Validate processing of this Single Payment Service request in OBPM
4. This transaction is nowhere available on any front end screen and not available in any of the backend tables as well. It didn't even logged in pmtb_incoming_log table
The issue has the following business impact:
Due to this issue, users cannot perform transaction with Account description more than 70 Characters.
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