Last updated on FEBRUARY 22, 2017
Applies to:Oracle Communications MetaSolv Solution - Version 6.2.1 and later
Information in this document applies to any platform.
We have some orders that the “DD” task was marked as completed in Metasolv Production 03/31/15 around 8:00PM.
When you look at the “DD” task associated with these orders in the Metasolv Client it shows the Actual Completion Date and Time correctly as 3/31/2015 with the actual time.
However, our reports are showing 4/1/2015.
User has pulled the task record from the Metasolv database and it is also showing 4/1/2015 as the actual completion date.
This matches what the reports are showing but doesn’t match the front-end application. Can you please answer the following:
1. Why is the actual completion date of the “DD” Task shown by the front-end Metasolv application different from that stored in the ACTUAL_COMPLETION_DATE field of the associated TASK table record?
2. If #1 is related to a time zone conversion then:
a. Is this conversion done to EVERY date field in Metasolv?
i. If only some then we need a list of which ones are impacted.
b. Is this conversion applied to user defined fields with a type of DATE in ASR_USER_DATA, EWO_USER_DATA and PSR_USER_DATA?
c. How is a user defined field with a type of Date and a default value of “TO_DATE ('', 'MM-DD-YYYY')” impacted?
d. Is enabling Time Zone conversion an option when installing/configuring Metasolv? We do remember it asking for the time zone when logging in as ASAP for the first time.
i. If so can this be disabled as we only need EST?
ii. How will disabling it in production impact dates already stored? I.E.: will the dates associated with this order revert back to “3/31/2015 8:47 PM”?
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