eConfigurator: AddItem Changes IntegrationId If a Constraint Exists Otherwise Returns with Conflict
(Doc ID 480578.1)
Last updated on FEBRUARY 03, 2019
Applies to:Siebel eConfigurator - Version 7.7.2  to 184.108.40.206 SIA  [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***
Customer has following product structure :
For ChildProduct1 max cardinality = min cardinality = default cardinality = 1
- Call LoadInstance (ChildProduct1 is added as default cardinality = 1)
- Call GetInstance to get the IntegrationId of ChildProduct1
- Call CreateSession
- Call AddItem of ChildProduct1
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.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|