How to Fix the Adjustment Events Since PCM_OP_AR_GET_ACCT_ACTION_ITEMS is Still Referring to /batch Object After Patch 21539432 (Doc ID 2093299.1)

Last updated on JANUARY 10, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.0.0 [Release 7.5.0]
Information in this document applies to any platform.

Goal

The current scenario is:
1. rated CDR (delayed event poid 111)
2. perform billing
3. re-rated cdr (adjustment event poid 222)
4. Re-rated CDR is generated as Adjustment event. This Adjustment event has session_obj_type as /batch object.
5. Delete /batch object
6. Execute PCM_OP_AR_GET_ACCT_ACTION_ITEMS for this account. It fails.

After this <Patch 21539432>:
1. rated CDR (delayed event poid 111)
2. perform billing
3. re-rated cdr (adjustment event poid 222)
4. Re-rated CDR is generated as Adjustment event. This Adjustment event has session_obj_type as delayed event (111) object.
5. Execute PCM_OP_AR_GET_ACCT_ACTION_ITEMS for this account. It is success.

As they are failing for opcode PCM_OP_AR_GET_ACCT_ACTION_ITEMS, what can be done for all the adjustment events, which already have /batch object as session obj_id0?

Also, as part of archiving to free database space, delayed events older than 13 months are deleted, will there be any issue when calling PCM_OP_AR_GET_ACCT_ACTION_ITEMS opcode?
 

Solution

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