Accrual Adjustment Calculation Lines Computes Incorrectly while Generating Adjustment
(Doc ID 2217664.1)
Last updated on FEBRUARY 24, 2019
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.
On ORMB 18.104.22.168.0 version, RT - Rates
Rates which get invoked on adjustment generation do not compute rate components correctly.
Rate component of 'service quantity' RC type gets populated as insufficient data when rate value algorithm returns 0 as value. In previous environment (initial build/version of V22.214.171.124.0) RC value evaluated as 0 if its rate value algorithm returns 0 as value.
This behavior is different on the initial version of V126.96.36.199.0 but failing in existing version i.e. V188.8.131.52.0 73639
Following are the patches post which the behavior of RC changed resulting in above mentioned issue.
1) Apply Bug 22319157 - V184.108.40.206.0 ROLL UP PACK POST MANDATORY ROLLUP (p22319157_24010_Linux-x86-64.zip)
2) Incremental rollup Bug 24372193 - V220.127.116.11.0 INCREMENTAL ROLL UP PACK POST BUG 22319157 ROLLUP (p24372193_24010_Linux-x86-64.zip)
Value of RC 50 is expected to be evaluated as 0 when its rate value algorithm returns 0 as value. This is how it is working in current PROD environment (V18.104.22.168) as well as on the initial build/patch of V22.214.171.124.0. (before the deployment of two patch as mentioned above).
DEBUG (org.hibernate.SQL) select message_la0_.MESSAGE_CAT_NBR as MESSAGE1_995_0_, message_la0_.MESSAGE_NBR as MESSAGE2_995_0_, message_la0_.LANGUAGE_CD as LANGUAGE3_995_0_, message_la0_.VERSION as VERSION995_0_, message_la0_.MESSAGE_TEXT as MESSAGE5_995_0_, message_la0_.DESCRLONG as DESCRLONG995_0_, message_la0_.DESCRLONG_OVRD as DESCRLONG7_995_0_, message_la0_.MESSAGE_TEXT_OVRD as MESSAGE8_995_0_, message_la0_.OWNER_FLG as OWNER9_995_0_ from CI_MSG_L message_la0_ where message_la0_.MESSAGE_CAT_NBR=? and message_la0_.MESSAGE_NBR=? and message_la0_.LANGUAGE_CD=?
SS0001 - 139661-7213-1 2016-11-10 13:42:35,322 [[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] INFO (support.context.FrameworkSession) (Server Message)
Call Sequence: ;CIPRRCEN;CIPRRTVN;CIPRRTAN;CIPAGRTX;CIPAGDRX;CIPAADJG;CIPAADJO;CIPAADUP
Program Name: CIPAADUP
Text: Eligibility Criteria (EAGACCR2/01-01-2001/060/010/010) - RC Value can not be found for RC Sequence 050.
Description: RC Value can not be found for the specified RC Sequence.
SS0001 - 139661-7213-1 2016-11-10 13:42:35,322 [[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] INFO (support.context.FrameworkSession) Issuing rollback
STEPS TO REPRODUCE
1. To reproduce this error, you need to update the rate schedule.
2. Create a custom rate value algorithm which return 0 as value using getValue() method. This will work for adjustments as it
doesn't have any billing (billable charge, pricing...etc ) specific logic like C1_RATEVALUE algorithm.
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