Turning Off Cycle Fee Opcode In CMT Deploy Stops Billinfo_t.Billing_status Being Updated To 0 (Doc ID 1389446.1)

Last updated on SEPTEMBER 24, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 and later
Information in this document applies to any platform.
Checked for relevance on 10-Jan-2014

Goal

There is a need to turn off the cycle fee opcode when running CMT deploy to prevent cycle fee proration from happening for the month that the migration is occuring. But after doing this, the billinfo_t.billing_status is not updated to 0 after running "pin_cmt -deploy".

Steps to Reproduce

1. Change the following property in the cmt Infranet.properties file:
infranet.cmt.deploy.opcode=false
2. Prepare a CMT input file. Run "pin_cmt -import -file <file_name> <batch_number>" to load the file.
3. Run "pin_cmt -deploy <DOM> <batch_number>" to deploy the account loaded to production.
4. Check the account's billinfo_t setting, specifically the billing_status field. This will still be set to 1 instead of 0. The only way the account can then be billed is by updating the billing_status manually to 0.

Actual result:
The billinfo_t.billing_status field remains set to 1, indicating that the account should not be billed.

Expected result:
The billinfo_t.billing_status field should be automatically set from 1 to 0 after "pin_cmt -deploy" has been run, even if the cycle fee opcode has not bee run, as this will change the characteristics of a migrated account to production mode.

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