This chapter provides reference information for Oracle Communications Billing and Revenue Management (BRM) Conversion Manager utilities.
Important:
The cmt_mta_cycle_fees utility is run internally by the pin_cmt utility. Do not run this utility by itself.The cmt_mta_cycle_fees utility applies cycle forward fees to BRM accounts that have been deployed by the pin_cmt utility. See "Understanding Conversion Manager" and "Loading Legacy Data into the BRM Database".
Important:
Conversion Manager is an optional component, not part of base BRM.Note:
To connect to the BRM database, the cmt_mta_cycle_fees utility needs a configuration file in the directory from which you run the utility.BRM_Home/apps/cmt
where, BRM_Home is the directory in which you installed the BRM software.
The stage ID used when the data was imported.
The billing day of month for the accounts that need cycle fees applied.
Use the pin_cmt utility to load legacy data in XML format into your BRM database. See "Understanding Conversion Manager" and "Loading Legacy Data into the BRM Database".
Important:
Conversion Manager is an optional component, not part of base BRM.Note:
To specify a database connection, edit the pin_cmt Infranet.properties file in BRM_Home/apps/cmt.pin_cmt -import -file XML_input_data_file stage_ID| -import_custom -file XML_input_data_file stage_ID| -recovery load batch_ID| -deploy DOM stage_ID
Imports the specified data file into the BRM database.
Note:
Ensure that there are no extra spaces in the input XML file. If you need to indent text in the XML file, use the TAB key to add space.Imports data that uses new storable classes into the BRM database.
Reloads data after a failed load process. The batch ID is recorded in the cmt.pinlog file in BRM_Home/apps/cmt.
Deploys data. DOM is the billing cycle's day of the month. stage_ID is the stage ID used when the data was imported.
In this example, accounts with a billing day of month of 15 and stage ID of 100 are deployed:
pin_cmt -deploy 15 100