Timestamp Issue In Cost Scenario
Last updated on AUGUST 01, 2017
Applies to:Oracle Fusion Cost Management Cloud Service - Version 184.108.40.206.0 and later
Oracle Fusion Cost Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
User creates a scenario to publish cost and resource rates and use it in cost accounting.
Once cost is updated, cost accounting currently doesn't allow for cost scenario with same date as it violates unique constraint.
Usually, if an error has been made in update, there is no way for user to have another scenario for that date.
This leads to unusual situation where there could be some transactions that could be in error, but cannot be fixed by defining
retrospective cost scenario because another retrospective scenario for that date already exists.
This could be resolved if Cost Scenario was validating on date and time and not just date.
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