SBL-CFG-00164: There is a conflict with your last request. Please click the Undo button to undo your last request.

Applies to:

Siebel eConfigurator - Version: 8.1.1.2 SIA[21215] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

If an order line item is created in one language via promotion, then it is not possible to customize it in another language. Please see steps to reproduce issue:

• Create a Sales Order 
• Add promotion "TST Promotion" => This adds product "TST Root product" as well 
• Press "Customize" for "TST Root product"
• In eConfigurator UI add "TST Component 1" product and press customize for it
  => shows an attribute with label "Translation2"
• Now modify the product class of "TST Component 1"
• Goto Administration - Product > Product Class
• Lock class "Class_1" and drilldown to workspace
• In Attribute sub view launch Menu > Translations for the attribute
• Modify
• from: ENU / Translation 2
• to: ENU / Translation 1 
• Release class, Refresh Cache
• Go to Sales Order again
• Press Customize for "TST Root product" again
  ==> "There is a conflict with your last request. Please click the Undo button to undo your last request. For a detailed explanation of this conflict, please click the Explanation button. (SBL-CFG-00164)
  Explanation:  is excluded due to the promotion TST Promotion
  

This error can be reproduced with different languages or with upper tetstcase as well.

Cause

Based on the upper testcase it looks like promotion validation is using display name of the attribute name instead of the language independent code (LIC).

Solution

Technical Support was able to duplicate the described behavior and logged Bug 10593366 in order to address this product defect.

As a workaround please check following temporary approaches:

• Do not use attribute conditions in promotion definitions
• Do not translate attribute values

Oracle Product Support

References

BUG:10593366 - CONFLICT MESSAGE (SBL-CFG-00164) WHEN PROMOTION HAS ATTRIBUTE CONDITIONS AND ATTRIBUTE IS TRANSLATED

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3.4 [16180] Com/Med
Database: Oracle 9.2.0.2
Application Server OS: Sun Solaris 8
Database Server OS: Sun Solaris 8

This document was previously published as Siebel SR 38-1383560421.

Symptoms

SBL-CFG-00164

Raised by Lisa Gill : PS consultant on Site

Parent CP, contains child CP - the relationship between parent and child has a default cardinality as 1 max 6, min 1.

In 7.5.3.3 this worked fine, but in 7.5.3.4 with our current product model implementation we are having issues with default cardinality - if this is set to 1, we get an error when pressing the customize button on an Order ( Screen Shot of error attached )

NB This error is not received during product validation, and after removing the default cardinality from the subscription relationship we are able to customize the product and add in the subscription manaully.

Please research in context of other HI Customization issues we are having refer to SR 38-1377925401 for product model, web templates, scripts etc.

Attached doc shows screenshot of error received when pressing customize in the Order>Line Items View when it attempts to launch econfigurator

Solution

Message 1

For the benefit of other readers:

A Parent CP, contains a Child CP - the relationship between parent and child has a default cardinality as 1 max 6, min 1.

In 7.5.3.3 this worked fine, but in 7.5.3.4 with our current product model implementation we are having issues with default cardinality - if this is set to 1, we get an error when pressing the customize button on an Order

<b>There is a conflict with your last request.</b> Please click the Undo button to undo your last request. <br> For a detailed explanation of this conflict, please click the Explanation button. SBL-CFG-00164

NB This error is not received during product validation, and after removing the default cardinality from the subscription relationship we are able to customize the product and add in the subscription manaully.

The behaviour was tested and reproduce by Technical Support.

When a new version of a customizable product is released, Auto Match adjusts the configuration of the product in a quote, asset, or order to reflect the changes. Auto Match is disabled by default.

For Web Client users, you turn Auto Match on by setting its server parameter to TRUE.

Server Parameter for Auto Match:

Parameter Name: eProdCfgAutoMatchInstance
Display Name: Product Configurator - auto match quote on reconfigure.
Data Type: Boolean
Default Value: FALSE
Description: When set to FALSE, Auto Match is turned off. When set to TRUE, Auto Match is turned on.

Continued:

Message 2

For Dedicated Web Client users (also called mobile client users), add the following entries to the configuration file used to start the application, for example Siebel.cfg.

;; This section will be read for mobile clients only

[InfraObjMgr]
eProdCfgAutoMatchInstance=TRUE

Siebel Technical Support.

Applies to:

Siebel Order Management - Version: 8.1.1 SIA [21111] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

The following behaviour is observed when upgrading promotions and using eConfigurator constraints based on product attributes, which are also constrained by the promotion:
The product cannot be customized if the new promotion excludes an attribute value that is required by a component product which is part of the installed asset.
To reproduce, make sure that asset based ordering is enabled.
Create customizable product "Product A" with an enumerated attribute like this:
* Product A
o Attribute A
- Value 1
- Value 2
o Relationship 1
- Product B
- Product C
Create two rules:
* Product B requires Attribute A = Value 1
* Product C requires Attribute A = Value 2
Create two promotions:
* Create Promotion A with “Track as Asset” set. Add Product A under Products – Components. Click Product A. Create attribute constraint: Attribute 1 includes Value 1 (so Value 2 violates the promotion). Release promotion.
* Create Promotion B with “Track as Asset” set. Add Product A under Products – Components. Click Product A. Create attribute constraint: Attribute 1 includes Value 2 (so Value 1 violates the promotion). Add Promotion A under Upgrade tab so Promotion B may serve as an upgrade. Release promotion.
Create quote for an account, add Product A within Promotion A. Click Customize. Value 2 for Attribute A and Product C are excluded due to the promotion and the constraints. Add Product B to the solution.
Create assets from quote items.
Select Promotion A under the account’s installed assets and click Upgrade Promotion in applet menu. Select Promotion B and click OK.
=> The application goes to Quotes > List > Line Items > Totals, showing a new quote with line items:
Product A with
Promotion = Promotion B, Action = Update
Component for product "Product B", Action = -
Promotion A, Action = Delete
Promotion B, Action = Add

Select the line item for product "Product A" and click on Customize.
=> eConfigurator Warning comes up with the following message:
Product - Product A Extended Attribute Modified <b>Promotion Violation. THe following Product or Attribute is no longer part of the promotion.<b> : Extended Attribute - Attribute 1; Old Value = Value 1; New Value = Value 2

Click OK
=> eConfigurator UI comes up, showing conflict message:
There is a conflict with your last request. Please click the Undo button to undo your last request.
For a detailed explanation of this conflict, please click the Explanation button.(SBL-CFG-00164)

Only the following buttons are active:
Undo
Explanation

Click Explanation.
=> Explanation:
Value 1 is excluded due to the promotion Promotion B.

Click OK.
=> The explanation is removed.

As the Proceed button is disabled, the user can only click Undo.
=> The application goes back to Quotes > List > Line Items > Totals.
Go to the Attributes sub view and check.
=> The line item for product "Product A" still has attribute "Attribute 1" with value "Value 1".

The same behaviour is observed with all possible values for UI Property "GoalMode" in product "Product A".

So the product cannot be customized.

Cause

The conflict is caused by the require constraints. When starting eConfigurator, it tries to justify promotion constraints by replacing Value 2 with Value 1 for Attribute A. At this time, Product B is still part of the solution. This raises a conflict message. However, the engine tries to change Attribute A back to Value 1 instead of removing Product B.

This is a product defect and the following Change Request has been created to request that this be fixed in a future version of the Siebel application:
Product Defect BUG 10587912 - Upgrade Promotion creates conflicting quote item that is not customizable

Note that any fix provided in the area of Product Configurator/Promotion Integration applies to the particular test case for which the Change Request has been logged. In general there should not be a promotion constraint and a Customizable Product rule (CP rule) on the same entity.

Solution

There is no workaround except adhering to the guidelines from My Oracle Support Note 560085.1 (Limitation Of Configurator Promotion Constraint Rule Integration), which are still valid especially for asset-based ordering:

1. If possible please stay away from using CP rule and promotion CP rule at the same time. Use only either one of them.
2. If that is not working, avoid defining promotion and CP rule on the same entity.
3. If that's inevitable, users have to live with the behavior where some selection might throw an promotion conflict where they can only undo. The chance of such conflicts can be reduced by defining promotion default on these port/attribute and/or its child if they are involved in CP rule as well, and also by not using promotion constraints to exclude default product from domain product possibly added by preference rule.

References

BUG:10587912 - UPGRADE PROMOTION CREATES CONFLICTING QUOTE ITEM THAT IS NOT CUSTOMIZABLE
NOTE:560085.1 - Limitation Of Configurator Promotion Constraint Rule Integration

Applies to:

Siebel Configurator - Version: 7.8.2.14 SIA[19251] and later   [Release: V7 and later ]
Information in this document applies to any platform.

Symptoms

seen in 7.8.1.14.

A Business Component Based attribute has been defined using a VBC.

After selecting a value from the pick applet the context in the eConfigurator UI was lost and below error message is displayed:

There is a conflict with your last request. Please click the Undo button to undo yur last request
For a detailed explanation of this conflict, please click the Explanation button.(SBL-CFG-00164)

Please note that this was not the conflict page of the eConfigurator UI.

Cause

It turned out that underlying attribute definiton was Text, Enumerated.

If changed to Text, Freeform the pick applet worked as expected.

Comments:

That Business Component Based attributes do not work together with enumerated attributes can be seen in much simpler cases as well but symptoms are different. If a 1 level product structure is used the icon to show the pick applet will not be displayed. Instead you see the down arrow which lists the values from the attribute definiton.

In the current case for the attributes where displayed with attribute inline display and in this case the icons for the popups were rendered.

Solution

need to change underlying attribute definitions, constraints referring to related values need to be crosschecked as well.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3 [16157]
Database: IBM DB2/UDB 7.2
Application Server OS: IBM AIX 5L 5.1
Database Server OS: IBM AIX 5L 5.1

This document was previously published as Siebel SR 38-1092419711.

Symptoms

We are trying to use the Cfg_OnConflict event to automatically respond to _certain_ conflicts. In Cfg_OnConflict, I was attempting to know what conflict caused the event to be triggered by comparing the value of the Explanation parameter (passed in) with the value I had set in the Explanation column for some rule. This was not working so I used TheApplication().RaiseErrorText(...) to dump the Explanation parameter to the screen. The contents of that is:

<b>There is a conflict with your last request.</b> Please click the Undo button to undo your last request. <br> For a detailed explanation of this conflict, please click the Explanation button.(SBL-CFG-00164)

This seems to be a canned explanation from Siebel. I was expecting to have what I had set in the Explanation column for the rule. So I'm assuming that this will be in the Explanation parameter for all rules. Is there a way then to tell what conflict caused the Cfg_OnConflict event?

Solution

Message 1

For the benefit of other users:

Customer's requirement was to determine the rule that caused a conflict in the CFG_OnConflict event. The CFG_OnConflict event has an Explanation argument that is passed. The expected behavior was that this 'Explanation' argument would have the Explanation specified in the 'Explanation field ' by the user in the Rule.

However it was found that the 'Explanation' argument was a system generated message and not the user defined Explanation. The Bookshelf also states that the 'CFG_OnConflict's 'Explanation' argument 'Passes in the system message explaining the conflict'.

Technical Support reproduced the behavior and has logged Change Request#12-I4ZT97 to provide the user-defined explanation instead of the system-generated one when a conflict happens.

Bharathi Ramajayam
Siebel Technical Support