My Oracle Support Banner

Billable Charges Getting Skipped Due To BILLABLE_CHG_STAT = ‘50’ (Doc ID 2742173.1)

Last updated on JANUARY 12, 2021

Applies to:

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

Goal

On RMB v2.6.0.1.0, Billable charges getting skipped.

We are observing an issue where already frozen Bill segments are getting re-processed by C1-BLGEN job.
It is possibly due to BILLABLE_CHG_STAT = ‘50’ and it is throwing warning messages “ Skipped Billable Charges”

Eg:
22:02:28,431 [RMBRECWorker:1] INFO (com.splwg.base.api.program.Displayer_Impl) LAST-TIMESTAMP 99999999999999999999999
22:02:32,986 [RMBRECWorker:1] INFO (com.splwg.ccb.domain.pricing.priceitem.ProductParametersCache) Removing Least Recently Used Entry :AIDMXXXXX
22:03:12,424 [RMBRECWorker:1] INFO (com.splwg.ccb.domain.pricing.priceitem.ProductParametersCache) Removing Least Recently Used Entry :BDIXXXX
22:03:26,630 [RMBRECWorker:1] INFO (com.splwg.ccb.domain.pricing.priceitem.ProductParametersCache) Removing Least Recently Used Entry :BREXXXXX
22:03:29,120 [RMBRECWorker:1] INFO (com.splwg.ccb.domain.pricing.priceitem.ProductParametersCache) Removing Least Recently Used Entry :CARXXXXXX
22:03:43,417 [RMBRECWorker:1] INFO (com.splwg.base.api.program.Displayer_Impl) Skipped - Billable charge : 44448nnnnnn
22:03:43,417 [RMBRECWorker:1] INFO (com.splwg.base.api.program.Displayer_Impl) Invalid status : 50
22:03:43,417 [RMBRECWorker:1] INFO (com.splwg.base.api.program.Displayer_Impl) Skipped - Billable charge : 44448nnnnnn
22:03:43,417 [RMBRECWorker:1] INFO (com.splwg.base.api.program.Displayer_Impl) Invalid status : 50
22:03:43,417 [RMBRECWorker:1] INFO (com.splwg.base.api.program.Displayer_Impl) Skipped - Billable charge : 44448nnnnnn
22:03:43,417 [RMBRECWorker:1] INFO (com.splwg.base.api.program.Displayer_Impl) Invalid status : 50
22:03:43,417 [RMBRECWorker:1] INFO (com.splwg.base.api.program.Displayer_Impl) Skipped - Billable charge : 44448nnnnnn

We expect Bill segments should not getting re-processed by C1-BLGEN job as all bill segments are frozen.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. This billable charge has 10 frozen Bill segment with status = 50
2. Run C1-BLGEN batch
3. It throws the warning/error.
 

Solution

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
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.