Last updated on JUNE 22, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 7.4.0]
Conversion manager (CMT) does not allow to specify cycle fees that are already charged before migration (charged_from and charged_to fields in purchase_product_cycle_fees_t) .
Consider a scenario with Bill-in-advance enabled for a cycle fee product. The migration of such accounts will not be done properly and the accounts will be charged for the cycle fees twice (once in Legacy System and next in the New migrated env).
Hence CMT must provide a way to handle cycle fees already charged.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms