Payment Transfer Functionality Behaving Differently Between Online Transaction And Code

(Doc ID 2355881.1)

Last updated on FEBRUARY 06, 2018

Applies to:

Oracle Financial Services Revenue Management and Billing - Version 2.4.0.1.0 and later
Information in this document applies to any platform.

Goal

Why does the payment transfer functionality behave differently between online transaction and code?

The issue is happening when trying to stamp a Characteristic on a payment where the amount of the individual pay segments for this payment net to zero. The current “DTO” approach¬†used to stamp this char fires a base validation to check for the payment amount and errors out if the payment amount is zero.
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms