How To Force CMT to Use a Predefined Date for Migrated Items in Item_t
Last updated on AUGUST 24, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
When migrating items in the ITEM_T table, CMT (Conversion Manager) sets the SYSDATE (unix time) into the created_t, the effective_t and the mod_t.
If for testing purposes, pin_virtual_time is set to a date in the past compared to the (unix) system time; because CMT migrates items using the system time, migrated items will be in the future compared to the pin_virtual_time used by billing and billing those items will be impossible.
Is it possible to configure CMT to set a date in the past compared to the pin_virtual_time defined, for the items migrated ?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms