Inactive Subscription Customization to Maintain Valid_To as Accounting Cycle (Doc ID 2116339.1)

Last updated on APRIL 01, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 and later
Information in this document applies to any platform.

Goal

Qn: On : 7.5.0.10.0 version, Subscription Management

Inactive Subscription

Currently when customer cancel a product/discount, customer is able to pass the MAINTAIN flag in the flist so that the sub balance impacted by this maintains the same VALID_TO as the accounting cycle.
Now, when it comes to inactivating the service (op_cust_update_services)


The Input FList is:
0 PIN_FLD_POID POID [0] 0.0.0.1 /account 1178176 0
0 PIN_FLD_SESSION_OBJ POID [0] 0.0.0.1 /event/session 291027533733981944 0
0 PIN_FLD_PROGRAM_NAME STR [0] "Unit-test script"
0 PIN_FLD_START_T TSTAMP [0] (1429356891) Sat Apr 18 06:34:51 2015
0 PIN_FLD_END_T TSTAMP [0] (1429356891) Sat Apr 18 06:34:51 2015
0 PIN_FLD_SERVICES ARRAY [0] allocated 20, used 3
1 PIN_FLD_STATUS ENUM [0] 10102
1 PIN_FLD_STATUS_FLAGS INT [0] 8
1 PIN_FLD_POID POID [0] 0.0.0.1 /service/wireless/fleetnet 1177280 7

The problem is that the same behavior is expected as when calling xxx_product_cancel opcode, meaning that customer wants the sub balances to maintain the VALID_TO accounting cycle, however, BRM cuts the date to the inactivation date. Customer changed the sub_bal_validity business param, but it only kicks in when transferring and not inactivating.

Is there a simple way to do this?
 

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