Need Update on Stop Loss Billable Charge Creation Batch Process to Meet the New Stop Loss Requirements
Last updated on MARCH 08, 2018
Applies to:Oracle Financial Services Revenue Management and Billing - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
This article states on how to update the Stop Loss tables to meet the following Stop Loss requirements in RMB 18.104.22.168.0 version.
• Table, metadata, MO, and BO changes to support new stop loss parameters including run-in parameters and accumulation per Account ID.
• Business scenario: customer has a concept of run-in transactions where these transactions can only contribute to stop loss accumulation up to a certain limit. They also need the ability to setup some customers to accumulate towards different accounts (where the claim was processed in) vs the current implementation of accumulating to a single billing account.
• The following tables need to be updated:
CI_ACCUM_GRP_SSL – Add run-in parameters
CI_ACCUM_GRP_ASL – Add run-in parameters and ASL limit option fields
CI_ACCUM_SSL_AMT – Add Account ID to support multiple account accumulations
CI_ACCUM_ASL_AMT – Add Account ID to support multiple account accumulations
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