ASL BSEGs Are Not Deleted On DISAGG PROCESS (Doc ID 3045542.1)

Last updated on SEPTEMBER 09, 2024

Applies to:

Symptoms

On RMB v5.1.0.0.0, ASL BSEGs are not deleted after DISAGG Batch run.

After successfully complete DISAGG batches for SSL parent accumulation group, ASL accumulation entries in ASL accumulation table are not getting deleted.

ACTUAL BEHAVIOR
----------------------
1) All pending billable charges (SSL Credits, ASL Credits, Enrollment based Fees, Claims) are deleted after C1-BSEGD batch on the Pending bill.
2) Billable charges are not deleted after the C1-TXNCU batch, C1-TXNCU batch is running into null pointer exception.
3) Entries in the SSL accumulation, ASL accumulation batches should be deleted after the C1-SLACU batch.

EXPECTED BEHAVIOR
-------------------------
1) All pending billable charges (SSL Credits, ASL Credits, Enrollment based Fees, Claims) should be deleted after C1-BSEGD batch.
2) Billable charges should be deleted after the C1-TXNCU batch

STEPS
-------------
1. Create ASO Customer
2. Create JAN month transaction and run TFM batches.
3. Run Accum batches ( SSL and ASL) for both.
4. Create bill in 'pending' status for jan month
5. Bill is Generated in 'Pending' status.
6. After that Modify SSL
i. Parent Level : Modify SSL PAYOUT LIMIT
ii. Bill group level : modify SSL LIMIT
7. Create Dis-aggregation request ( on account)
8. Run f1-flush
9. Run Dis-Agg batches
    - C1-BSEGD (bill seg deletion) and check whether bill segments are deleted or not.
    - C1-PNDB
    - C1-IDENT
    - C1-PDTXN
    - C1-TXNCU
    - C1-SLACU
    - C1-DRSUA

Cause

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