Changes to Part Fields in Parts Database Do Not Update Values When Reconfiguring (Doc ID 2146768.1)

Last updated on JUNE 09, 2016

Applies to:

Oracle BigMachines CPQ Cloud Service - Version 2015 R1 and later
Information in this document applies to any platform.

Symptoms

Updates made to a part's field values (i.e. Part Custom Field), are not updated on a existing quote after reconfiguring. 

 

For example:

Part 10A has a Cost field designated for _part_cusom_field5 (float-type).  An administrator changes this field's value for part 10A from 50.0 to 51.0.  After applying this change to the part database, an existing quote's model (which includes Part 10A) is reconfigured.  No changes are made in the configuration, and the Save to Quote action is called.  After entering back to commerce and saving the quote, the part's Cost Field will remain at 50.0.  

It is expected that reconfiguring a model will run the Recommended Item rule, and all data for the part is updated accordingly. 

 

Notes:  

  • On 2015 R1, this affects all Part Sub-Attributes.

  • On 2015 R2, this affects only float and integer type part custom fields when updated individually.  For instance, if only a float-type part custom field is updated in the Parts DB, the quote will not be updated upon reconfigure.  Alternately, if a float-type field and a string-type field are updated in in the Parts DB, the quote will be correctly updated upon reconfigure. 

Changes

Site is on version 2015 R1 or 2015 R2.

Cause

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