eConfigurator: AddItem Changes IntegrationId If a Constraint Exists Otherwise Returns with Conflict (Doc ID 480578.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel eConfigurator - Version 7.7.2 [18325] to 8.2.2.3 SIA [23021] [Release V7 to V8]
Information in this document applies to any platform.
This document was previously published as Siebel SR 38-3439551071.
***Checked for relevance on 19-06-2013***


Symptoms

Customer has following product structure :

       RootProduct
        --> ChildProduct1
       
For ChildProduct1 max cardinality = min cardinality = default cardinality = 1

Problem description:

Customer expects a failure of last call as max cardinality = 1 and ChildProduct1 already exists after step 1. However it is executed without failure. A further GetInstance call shows that action AddItem has replaced the old child. The new child has a new IntegrationId.

Problem: IntegrationId should remain the same. ChildProduct1 should not be replaced.

 

This behavior can be reproduced from Product Configurator UI as well.

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