Inconsistent Transaction Status for Run-In Transactions Processed in SSL (Doc ID 2163136.1)

Last updated on JULY 25, 2016

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

On RMB 2.4.0.1.0, when processing run-in transactions that accumulate toward Specific Stop Loss (SSL), the transactions remain in IGNR status whereas its SSL transaction product has already been updated by SSL processing to status 40 (completed).

Expected behavior is if the run-in transaction originally in IGNR status has a leg that is moved to status 40, then the run-in transaction should also be updated to COMP status.

This article confirms the base stop loss code fix via a product patch.

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