Threading Problem In C1-USGDF If Bill Has Multiple Bill Segments

(Doc ID 1675309.1)

Last updated on AUGUST 14, 2014

Applies to:

Oracle Utilities Customer Care and Billing - Version 2.3.1 to 2.3.1 [Release 2.3]
Information in this document applies to any platform.


On : 2.3.1 version, BI - Billing

As with most of the entities related to an account (e.g. bills, payments), the first 5 digits of the ID is inherited from the first 5 digits of the Account ID.
This helps when running various batch jobs multi-threaded as the entities are not split and processed by different threads.
With the introduction of Usage entity, the ID is not inherited from the Account ID. When running C1-USGDF multi-threaded, this means we could be processing different usages for the same account at the same time. This can cause issues related to concurrency.

Usage Id should follow the same pattern as other entity ids to avoid threading issues.

The issue can be reproduced at will with the following steps:
1. Setup a CCB-MDM account.
2. Generate a usage request.
3. Check the Usage Id. It is not generated as partial parent key.

The issue has the following business impact:
Due to this issue, users cannot this can cause issues related to concurrency.


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