CMT Issue: Numeric Dynamic Field with Comma Decimal Not Correctly Transferred
Last updated on DECEMBER 11, 2017
Applies to:Oracle Health Insurance Claims Adjudication - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
A numeric dynamic field with decimals using a decimal comma is included in the CMT (Configuration Migration Tool) set with a decimal point and subsequently in the target environment the decimal point is ignored. So a value of 1,25 in the source arrives as 125 in the target. The problem seems to be a in incorrect creation of the CMT set in case of numeric fields with decimals.
The Field is defined as N0302 (3 digits + 2 decimals).
Work around : Manual editing of the specific XML file to replace the decimal point by a comma.
The issue can be reproduced at will with the following steps:
1. Field definition N0302 = 3 digits + 2 decimals
2. Field usage "factor" for table PRI_SMPL_ADJUSTMENT_RULES with definition N0302
3. Enter content 1,25
4. Add rule to PPC
5.Transfer PPC with CMT
Due to this issue, Extra work in managing CMT. Risk of overlooking certain config having this decimals.
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