AR_ITEM_OBJ_ID0 Not Populated for Usage Items Leading to Mismatch in Bill Due And Item Due (Doc ID 2967929.1)

Last updated on AUGUST 23, 2023

Applies to:

Symptoms

On : 12.0.0.8.0 version, Core Billing

One user has the below observation that the items for the bill is not matching with bill_t due.
The wholesale billing is enabled at the system level.

Note that this scenario was working fine in Patch Set 3 that  /item/sbd_usage item for "11-aug to 11-sept" is populated with ar_item_obj_id0.

STEPS
-----------------------
Accounts created with Billing Day of Month (BDOM) 11.

1. Run billing on 11th May
    Two precreate "/item/sbd_usage" items are created for "11-may to 11-june" and "11-june to 11-july".

2. Suspend Child on 10th June

3. Run billing on 11th June
    /item/sbd_usage precreate does not happen, so only 1 item left for "11-june to 11-july" (ar_item_obj_id0 is not populated).
    i.e. no /item/sbd_usage "11-july to 11-aug" created

4. Un-suspend Child on 12th June

5. Process usage
    Charges are accumulated on /item/sbd_usage "11-june to 11-july".

6. Run billing on 11th July
    /item/sbd_usage "11-june to 11-july" is not rolled up since ar_item_obj_id0 was not populated by billing on 11-june.

    Charges were considered in parent bill and item status was changed to 2.
     -- 2 /item/sbd_usage items for "11-july to 11-aug" and "11-aug to 11-sept" are precreated.
     -- /item/sbd_usage item for "11-july to 11-aug" is populated with ar_item_obj_id0.

7. Process usage
    Charges are accumulated on /item/sbd_usage "11-july to 11-aug".

8. Run billing on 8th Aug
    -- /item/sbd_usage "11-sept to 11-oct" is pre-created.
    -- Charges are rolled up for item "11-july to 11-aug".
    -- /item/sbd_usage item for "11-aug to 11-sept" is populated with ar_item_obj_id0.

Cause

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