3 Setting Default Billing Properties for Account Creation
Learn how to set up system-wide billing defaults, such as the default billing-cycle length, in Oracle Communications Billing and Revenue Management (BRM).
Topics in this document:
Setting the Default Accounting Day of Month
Note:
It is a good idea to leave the accounting DOM set to the date the account was created. This distributes the load for the billing utilities throughout the month.
To set the default accounting day of month (DOM):
-
Go to BRM_home/sys/data/config.
-
Use the following command to create an editable XML file from the customer instance of the /config/business_params object:
pin_bus_params -r BusParamsCustomer bus_params_customer.xml
This command creates an XML file named bus_params_customer.xml.out in your current directory. If you do not want this file in your current directory, specify the path as part of the file name.
-
In bus_params_customer.xml.out, set ActgDom to the day of the month when the customer should be billed. Ordinarily, this can be between 1 and 28, but if you are using 31-day billing, it can be between 1 and 31. See "Configuring 31-Day Billing" for more information about 31-day billing.
<ActgDom>value</ActgDom>
The default value is 0.
Caution:
BRM uses the XML in this file to overwrite the existing instance of the /config/business_params object. If you delete or modify any other parameters in the file, these changes affect the associated aspects of the BRM configuration. -
Save and exit the file.
-
Rename the bus_params_customer.xml.out file to bus_params_customer.xml.
-
Use the following command to load your changes into the /config/business_params object:
pin_bus_params bus_params_customer.xml
You should run this command from the BRM_home/sys/data/config directory, which includes support files used by the utility. To run it from a different directory, see "pin_bus_params" in BRM Developer's Guide.
-
Read the object with the testnap utility or the Object Browser to verify that all fields are correct.
For general instructions on using testnap, see "Using the testnap Utility to Test BRM" in BRM Developer's Guide. For information on how to use Object Browser, see "Reading Objects" in BRM Developer's Guide.
The new value becomes effective immediately and applies to the next account created.
Setting the Default Billing-Cycle Length
-
Go to BRM_home/sys/data/config.
-
Use the following command to create an editable XML file from the customer instance of the /config/business_params object:
pin_bus_params -r BusParamsCustomer bus_params_customer.xml
This command creates an XML file named bus_params_customer.xml.out in your current directory. If you do not want this file in your current directory, specify the path as part of the file name.
-
In bus_params_customer.xml.out, set BillWhen to the number of months in one billing cycle:
<BillWhen>value</BillWhen>
The default value is 1.
Caution:
BRM uses the XML in this file to overwrite the existing instance of the /config/business_params object. If you delete or modify any other parameters in the file, these changes affect the associated aspects of the BRM configuration. -
Save and exit the file.
-
Rename the bus_params_customer.xml.out file to bus_params_customer.xml.
-
Use the following command to load your changes into the /config/business_params object:
pin_bus_params bus_params_customer.xml
You should run this command from the BRM_home/sys/data/config directory, which includes support files used by the utility. To run it from a different directory, see "pin_bus_params" in BRM Developer's Guide.
-
Read the object with the testnap utility or the Object Browser to verify that all fields are correct.
For general instructions on using testnap, see "Using the testnap Utility to Test BRM" in BRM Developer's Guide. For information on how to use Object Browser, see "Reading Objects" in BRM Developer's Guide.
The new value becomes effective immediately and applies to the next account created. You do not need to restart the Connection Manager (CM) to enable this entry.
Specifying the Maximum Number of Months Allowed in Billing Cycles
A billing cycle defines the time period between bills, which corresponds to the billing frequency (how often a bill is generated). For example, if the billing cycle is three months, a bill is generated every three months.
The default maximum number of months allowed in billing cycles is 24.
To change the maximum number of months allowed in billing cycles, modify the value of the bill_when field.
Setting the Default Accounting Type
You can set the default accounting type for all bill units (/billinfo objects) using the business parameter ActgType. BRM uses this setting during account creation only when an accounting type is not passed in the input flist of the Customer FM standard opcode.
To set the default accounting type:
-
Go to BRM_home/sys/data/config.
-
Use the following command to create an editable XML file from the billing instance of the /config/business_params object:
pin_bus_params -r BusParamsBilling bus_params_billing.xml
This command creates an XML file named bus_params_billing.xml.out in your current directory. If you do not want this file in your current directory, specify the path as part of the file name.
-
In bus_params_billing.xml.out, set the following entry:
<ActgType>value</ActgType>
where value is one of the following:- balance_forward: Specifies that BRM uses balance-forward accounting.
- open_item: Specifies that BRM uses open-item accounting.
The default value is balance_forward.
Caution:
BRM uses the XML in this file to overwrite the existing instance of the /config/business_params object. If you delete or modify any other parameters in the file, these changes affect the associated aspects of the BRM configuration. -
Save and exit the file.
-
Rename the bus_params_billing.xml.out file to bus_params_billing.xml.
-
Use the following command to load your changes into the /config/business_params object:
pin_bus_params bus_params_billing.xml
You should run this command from the BRM_home/sys/data/config directory, which includes support files used by the utility. To run it from a different directory, see "pin_bus_params" in BRM Developer's Guide.
-
Read the object with the testnap utility or the Object Browser to verify that all fields are correct.
For general instructions on using testnap, see "Using the testnap Utility to Test BRM" in BRM Developer's Guide. For information on how to use Object Browser, see "Reading Objects" in BRM Developer's Guide.
The new value becomes effective immediately and applies to the next account created.
Setting the First Billing Cycle to the Day after Account Creation
Normally, an account is billed after one month on the day on which the account is created. For example, if an account is created on January 10, the account is billed on February 10, then on March 10, April 10, and so on. However, you can set the first billing date to be the day after account creation. For example, if an account is created on December 16, the account is billed on December 17. After the first billing run, all remaining bills for the account are generated normally. In this example, the account is billed on January 17, February 17, and so on. This option is called advance billing cycle.
To set the first billing cycle to the day after account creation:
-
Open the CM configuration file (BRM_home/sys/cm/pin.conf) in a text editor.
-
Add the following line and set the value to 1.
- fm_bill advance_bill_cycle 1
Note:
To set the first billing cycle to one month after the account is created, comment out the line by using the pound (#) symbol.
-
Save and close the file.
-
Stop and restart the CM.