This chapter provides reference information for Oracle Communications Billing and Revenue Management (BRM) calculating taxes utilities.
Use the load_tax_supplier utility to load one or more tax suppliers into the BRM database's /config/tax_supplier object. You define the tax suppliers in either the BRM_Home/setup/scripts/pin_tax_supplier.xml file or another file that uses the same format. The format of the XML file is specified in the pin_tax_supplier.xsd schema file in the BRM_Home/xsd directory.
You can define only one tax supplier as the default tax supplier for your database.
Caution:The load_tax_supplier utility overwrites existing tax suppliers. If you are updating tax suppliers, you cannot load new tax suppliers only. You must load complete sets of tax suppliers each time you run the load_tax_supplier utility.
To connect to the BRM database, the load_tax_supplier utility needs a configuration file in the directory from which you run the utility. See "Creating Configuration Files for BRM Utilities" in BRM System Administrator's Guide for more information.
Each time you run this utility, you must restart the Connection Manager (CM).
Note:You cannot load separate /config/tax_supplier objects for each brand. All brands use the same object.
See "About Tax Suppliers" for information about tax suppliers.
Creates a log file for debugging purposes. Use this parameter for debugging when the utility appears to have run with no errors, but the data has not been loaded into the database.
Displays information about successful or failed processing as the utility runs.
To redirect the output to a log file, use the following command. Replace filename.log with the name of the log file:
load_tax_supplier pin_tax_supplier.xml–v > filename.log
Note:If a file with the same name exists, it is overwritten.
Checks the validity of the XML file, but doesn't create an object.
Displays the syntax and parameters for this utility.
The name and location of the file that defines the tax suppliers. The default pin_tax_supplier.xml file is in BRM_Home/setup/scripts.
If you do not run the utility from the directory in which the file is located, you must include the complete path to the file, for example: