Autopay Route Type Date Calculation Algorithm Needs Hard Coded Parameter (Doc ID 2134197.1)

Last updated on MAY 06, 2016

Applies to:

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

Goal

Issue with current Algorithm Spot: Current Autopay Route Type-Date Calculation algorithm doesn’t have bill/account entity as a hard parameter.
In some ORMB environments autopay date rules differ by division and not having any ID as a hard parameter prevents users from retrieving any Account level attributes. This limits the functionality this spot offers.

Bill Date exists as one of the hard parameter on this spot; so putting Bill Id as another Hard Parameter should not be an issue for such environments.

This article informs what options users have in such scenario.
 

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