![]() ![]() When you import data, you specify a stage ID. The database number is set to a number defined in the entry in the Infranet.properties file for the pin_cmt utility for example, 0.0.0.12.) (Data is hidden by changing the database number section in the Portal object ID (POID) of each imported object. When the data is imported, it is hidden from BRM processes, so it is not part of your production system. Loading data includes two processes: importing accounts and deploying accounts.įirst, you import the data into the BRM database. You use the pin_cmt utility to load the converted data into the BRM database. However, all delayed events are handled in the current bill. When the accounts are migrated, cycle forward fees and discount grants (for example, free minutes) are applied. Make sure that cycle arrears fees, billing-time discounts, and rollovers have been processed in the legacy system. ![]() Migrated data needs to reference the price list objects in the BRM database. All account data for an account must be loaded before loading balance data.Ĭreate a price list that applies to the migrated data before migrating account and balance data. You can load account and balance data together, or you can load account data first and balance data second. ![]() When data is migrated, rollover events can use the balance data to manage rollovers. Product data, such as products purchased by the accounts.īalance data, including data for all resources. Service data, such as the services subscribed to by the accounts. Conversion Manager supports the following types of data:Īccount data, such as the customer's name, address, profile, and discount information. You use Conversion Manager to load legacy data into BRM. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |