My Oracle Support Banner

Smart Part Number Not Correct When Promotion Constraint Is Applied In The eConfigurator (Doc ID 1454683.1)

Last updated on JANUARY 05, 2023

Applies to:

Siebel eConfigurator - Version 8.1.1.5 SIA [21229] to 8.1.1.7 SIA [21238] [Release V8]
Information in this document applies to any platform.

Symptoms

Smart Part Number is not correctly generated when promotion constraint is applied in the eConfigurator

=> Steps to reproduce the issue:

1-) Navigate to Administration - Product > Attribute Definition and create the following attributes:
 
Fulfillment Method: CD, Download, Download with CD
Edition: Pro, Premier
 
2-) Navigate to Administration - Product > Class Administration and add the above attributes to a class
 
3-) Setup smart part number functionality for the attributes using the matrix:
 
CD,  Pro, Smart Part Number: 123
CD, Premier, Smart Part Number: ABC
Download with CD, Pro, Smart Part Number: A1B1C1
Download with CD, Premier, Smart Part Number: A2B2C2
 
Please refer to document "How To Implement Smart Part Number Generation For Products With Attributes? [Document 729041.1] " for detailed steps to setup
Smart Part Number functionality
 
4-) Navigate to Administration - Product > Product Definition and create a new product with the previously created class
 
5-) In the versions applet, add the smart part number method created in step 3
 
6-) Navigate to Administration - Product > Product Promotions
 
7-) Create a bundle promotion with the product created in step 4
 
8-) Drilldown on the product name and in the Relationships view, click on the Attributes tab.
 
9-) In Attributes applet enter Attribute Name = Edition, Condition = Include.
 
10-) In the Values applet enter value = Premier
 
11-) Navigate to Quotes and create a new one
 
12-) Add product to it
 
Attributes have the following default values:
 
Fulfillment Method: CD
Edition: Pro
 
Smart Part # = 123
 
13-) In the promotions field, open the pick applet and select the promotion
 
14-) Highlight the customizable product and hit Customize
 
Warning message generated by the Auto Match report is displayed:
 
Product - Product A  Extended Attribute Modified <b>Promotion Violation. THe following Product or Attribute is no longer part of the promotion.<b> :
Extended Attribute - Edition; Old Value = Pro; New Value = Premier
 
15-) Hit ok
 
16-) Edition attribute is changed to Premier because of the promotion constraint
 
17-) Hit Done
 
Results: Smart Part # = 123 even though attributes now are
 
Fulfillment Method: CD
Edition: Premier
 
Smart Part # should be ABC

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.