Interval Data with a Custom UOM Code is Incorrectly Imported with UOM Code “16”
Last updated on OCTOBER 19, 2016
Applies to:LODESTAR EIP - Version 4.5 to 22.214.171.124
Information in this document applies to any platform.
***Checked for relevance on 05-Oct-2010***
***Checked for relevance on 11-Apr-2012***
When importing interval data with a custom UOM (Unit of Measure) code, the UOM incorrectly defaults to "16".
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