CHK_IM_DOC_DET_REAS_CODE_STATUS Constraint Differs From Valid Values in IM_DOC_DETAIL_REASON_CODES Table
Last updated on OCTOBER 09, 2016
Applies to:Oracle Retail Invoice Matching - Version 15.0 and later
Information in this document applies to any platform.
Why does the CHK_IM_DOC_DET_REAS_CODE_STATUS constraint differs from valid values on IM_DOC_DETAIL_REASON_CODES table ?
The constraint says status should be in 'APPRVE', but the column IM_DOC_DETAIL_REASON_CODES.STATUS comments says "valid values are: disput - disputed; apprve - approved; deny - denied."
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