Agile BoM qty integer / decimal fractions create red lines
Raised this as an SR but thought someone in the community may have a suggested fix for it....
We have observed when importing a BoM or publishing a BoM to a change form the CAD connector if there is a formatting difference for quantity i.e. if the BoM current value for quantity is expressed as an integer say '2' the CAD connector will publish 2.0 and this gets seen as a change in value and a red line created although numerically the value is unchanged.
This is giving us major problems down stream as if that non-change in qty value is not removed as a red line, when the "Agile Product Lifecycle Management Integration Pack for Oracle E-Business Suite: Design to Release" integration publishes the ECO to Oracle E-Business Suite, it errors as to EBS '2' & '2.0' are the same value therefore the change in BoM qty driven by the agile red line is seen as invalid.
We have observed when importing a BoM or publishing a BoM to a change form the CAD connector if there is a formatting difference for quantity i.e. if the BoM current value for quantity is expressed as an integer say '2' the CAD connector will publish 2.0 and this gets seen as a change in value and a red line created although numerically the value is unchanged.
This is giving us major problems down stream as if that non-change in qty value is not removed as a red line, when the "Agile Product Lifecycle Management Integration Pack for Oracle E-Business Suite: Design to Release" integration publishes the ECO to Oracle E-Business Suite, it errors as to EBS '2' & '2.0' are the same value therefore the change in BoM qty driven by the agile red line is seen as invalid.
0