OBPM_Derivation Of Transaction Branch Issue For PAIN File Upload
(Doc ID 2779270.1)
Last updated on MAY 26, 2021
Applies to:Oracle Banking Payments - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 14]
Information in this document applies to any platform.
On : 126.96.36.199.0 version, Implementation Support
Issue: OBPM_Derivation of Transaction Branch Issue for PAIN File upload
Expected that ,After processing a pain file the value of debtor agent code should be pickup the transaction booking branch in PAIN file .
Currently in FCUBS, there is a provision to maintain same codes for different branches in STDBRANC (Branch parameters) screen, the same data is carried forwarded to STDCRBRN (Branch Core Parameter) Screen making it mandatory for us to have a maintained in that screen, and one branch code for which default check needs to be mandatorily checked, failing which system would not allow us to save the data in the screen.
In this context, when we post a transaction using a pain file, the debtor agent branch code in the file would be used to derive the transaction booking branch, which is currently deriving a branch which is not expected to process(Ex: Currently picking ORC branch, instead of SRB).
Changes provided that transaction branch has been derived based on the account number branch
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