Autocreate Configuration not Calling Custom Matching if Model Exists More Than Once in the BOM (Doc ID 2061275.1)

Last updated on OCTOBER 09, 2015

Applies to:

Oracle Configure to Order - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

On : 12.1.3 version, Configuration Process

ACTUAL BEHAVIOR
-----------------------------
Custom matching is not being accessed if a model appears more than once in the overall model structure. For example, in the structure that follows, Model 4 is a child of both Model 2 and Model 5.
The instance is set up to use custom matching for all models.
However, when a child model appears more than once under a top level model, custom matching is not being used.
Example:
Parent Model 1
  Child Model 2
  Child Model 3
  Child Model 4
  Child Model 5
  Child Model 4
Custom matching will work for models 1,2,3, and 5 but standard matching will be used for model 4.


EXPECTED BEHAVIOR
-----------------------
Expect the custom matching will work for model 4 when using the standard matching.


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