10 Voucher Manager Utilities

This chapter provides reference information for Oracle Communications Billing and Revenue Management (BRM) Voucher Manager utilities.

Important:

Voucher Manager is deprecated and supported only for backward compatibility. Use Oracle Communications Convergent Charging Controller to manage vouchers.

load_pin_dealers

Use this utility to load dealer information into the Oracle Communications Billing and Revenue Management (BRM) database. This utility loads dealer information from the pin_dealer file to a /config/dealers object.

You use this utility to configure a set of dealers for vouchers and identify the dealers associated with any specific card. The dealer names and codes are loaded into the database. See "About Dealers" and "Loading Dealer Details".

Note:

• When you run the load_pin_dealers utility, it overwrites the existing dealers. If you are updating dealers, you cannot load new dealers only. You must load complete sets of dealers each time you run the load_pin_dealers utility.

• To connect to the BRM database, the load_pin_dealers utility requires 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.

Location

BRM_home/bin

Syntax

load_pin_dealers [-v] [-d] dealer_input_file

Parameters

-v

Displays information about successful or failed processing as the utility runs.

Note:

This parameter is always used in conjunction with other parameters and commands. It is not position dependent. For example, you can enter -v at the beginning or end of a command to initiate the verbose parameter. To redirect the output to a log file, use the following syntax with the verbose parameter. Replace filename.log with the name of the log file:

load_pin_dealers any_other_parameter –v > filename.log

-d

Writes error information for debugging purposes to the utility log file.

dealer_input_file

The name and location of the file that contains the dealer information. For example, the default file for dealer information is pin_dealers.

A sample definition file is provided in BRM_home/sys/data/config/pin_dealers.

Use this syntax for entries:

dealer_name : dealer_code

Results

Reports success or displays an error.

By default, the file is located in the same directory as the utility and is called default.pinlog. You can specify a different name and location in the Infranet.properties file.

load_pin_recharge_card_type

Use this utility to load voucher information into the Oracle Communications Billing and Revenue Management (BRM) database. This utility loads voucher information such as dealer name, dealer code, recharge card type, and recharge card code from the pin_recharge_card_type file to a /config/recharge_card_type object. See "About Recharge Card Types" and "Loading Recharge Card Details".

This utility associates card types with their dealers.

Note:

• When you run the load_pin_recharge_card_type utility, it overwrites the existing recharge card types. If you are updating a set of recharge card types, you cannot load new recharge card types only. You must load complete sets of recharge card types each time you run the load_pin_recharge_card_type utility.

• To connect to the BRM database, the load_pin_recharge_card_type utility requires 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.

Location

BRM_home/bin

Syntax

load_pin_recharge_card_type [-v] [-d] card_type_input_file 

Parameters

-v

Displays information about successful or failed processing as the utility runs.

Note:

This parameter is always used in conjunction with other parameters and commands. It is not position dependent. For example, you can enter -v at the beginning or end of a command to initiate the verbose parameter. To redirect the output to a log file, use the following syntax with the verbose parameter. Replace filename.log with the name of the log file:

load_pin_recharge_card_type any_other_parameter –v > filename.log

-d

Writes error information for debugging purposes to the utility log file.

card_type_input_file

The name and location of the file that contains the recharge card type information. For example, the default file for recharge card type information is pin_recharge_card_type.

A sample definition file is provided in BRM_home/sys/data/config/pin_recharge_card_type.

Use this syntax for entries:

recharge_card_type : recharge_card_code : dealer_name : dealer_code

Results

Reports success or displays an error.

By default, the file is located in the same directory as the utility and is called default.pinlog. You can specify a different name and location in the Infranet.properties file.

load_pin_voucher_config

Use this utility to load voucher information into the Oracle Communications Billing and Revenue Management (BRM) database. This utility loads voucher specific information such as batch part no, pack part number, pack quantity and batch quantity from the pin_voucher_config file to a /config/voucher object. See "About Voucher Details" and "Loading Voucher Details".

Note:

• When you run the load_pin_voucher_config utility, it overwrites the existing dealers. If you are updating dealers, you cannot load new dealers only. You must load complete sets of dealers each time you run the load_pin_voucher_config utility.

• To connect to the BRM database, the load_pin_voucher_config utility requires 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.

Location

BRM_home/bin

Syntax

load_pin_voucher_config [-d] [-v] voucher_input_file

Parameters

-v

Displays information about successful or failed processing as the utility runs.

Note:

This parameter is always used in conjunction with other parameters and commands. It is not position dependent. For example, you can enter -v at the beginning or end of a command to initiate the verbose parameter. To redirect the output to a log file, use the following syntax with the verbose parameter. Replace filename.log with the name of the log file:

load_pin_vocher_config any_other_parameter –v > filename.log

-d

Writes error information for debugging purposes to the utility log file.

voucher_input_file

The name and location of the file that contains the voucher information. For example, the default file for voucher information is pin_voucher_config.

A sample definition file is provided in BRM_home/sys/data/config/pin_voucher_config.

Use this syntax for entries:

batch_part_no : pack_part_no : pack_quantity : batch_quantity

Results

Reports success or displays an error.

By default, the file is located in the same directory as the utility and is called default.pinlog. You can specify a different name and location in the Infranet.properties file.

pin_voucher_expiration

Use this utility to move Oracle Communications Billing and Revenue Management (BRM) vouchers from the New state to the Expired state. See "Managing Expired Vouchers".

Note:

To connect to the BRM database, the pin_voucher_expiration utility requires 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.

Location

BRM_home/bin

Syntax

pin_voucher_expiration [-v] [-d]

Parameters

-v

Displays information about successful or failed processing as the utility runs.

Note:

This parameter is always used in conjunction with other parameters and commands. It is not position dependent. For example, you can enter -v at the beginning or end of a command to initiate the verbose parameter. To redirect the output to a log file, use the following syntax with the verbose parameter. Replace filename.log with the name of the log file:

pin_voucher_expiration any_other_parameter –v > filename.log

-d

Writes error information for debugging purposes to the utility log file.

Results

Reports success or displays an error.

By default, the file is located in the same directory as the utility and is called default.pinlog. You can specify a different name and location in the Infranet.properties file.