Payment Posting When Done From Payment Tool And Backend Takes Different Flow
(Doc ID 1476793.1)
Last updated on MARCH 13, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 7.3.0]
Information in this document applies to any platform.
Trying to call payment API from an external system for posting payments and the opcode throws an error within a custom opcode. While posting from payment tool it successfully posts.
We are thinking of possibilities to call the opcode set used by payment tool as its a success scenario. But when calling same set of opcodes with same i/p flist, the flow gets diverted inside op_bill_record_event opcode.
When posting through payment tool, op_bill_record_event returns payment related data in addition which is used by the custom code and hence do not throw a coredump
Whereas when using the same i/p flist from backend, the op_bill_record_event return flist does not return the payment related data which the custom code is looking for and hence coredumps in another policy opcode having this custom code.
Please guide us on where and how the flow changes when same opcode is being called in both cases that too with same i/p flist?
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