SBL-CFG-50277: Unable to get the value of %3 from property %4 for Attribute %1 of Product %2

Date:

Date:

Applies to:

Product Release: V7 (Enterprise)
Version: 7.8.2 [19213]
Database: Oracle 10g
Application Server OS: Microsoft Windows 2000 Server
Database Server OS: Redhat Linux Advanced Server 2.1

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

Symptoms

SBL-CFG-00183

We are experiencing the same error message encountered in the SRs 38-1023374721
38-1712568631. We have verified that the path specified in the file system is correct. We are using only 1 siebel server in a Windows environment.

We are facing this issue in our dev environment only. The environment was working fine for a period of time before we encountered this problem.

Please advise as to any alternate parameters we can verify besides the Siebel File System parameter of the File System Manager Component.

Solution

Message 1

For the benefit of other readers:

The Customer was experiencing some Siebel Version 7.8.2.x "File System" error behavior, in particular with the *FSM* File System Manager Server Component.

Following on from our research, I discovered that the Customer needed to set this DSFileSystem Parameter Setting for the Server Data Source "ServerDataSrc" as written into this Siebel Version 7.8.2.x Bookshelf > Siebel System Administration Guide Chapter 10: Application Object Manager Administration > About Siebel Application Object Manager Parameters > About AOM Named Subsystem Parameters > Table 24. Selection of Named Subsystem Parameters :

DSFileSystem ServerDataSrc String Set this parameter to *FSM* to allow the use of the File System Manager server component for standard Web clients. We also discovered that this DSFileSystem Parameter setting is now a part of the "Advanced" Object Parameter settings. From within the Siebel Version 7.8.2.x Enterprise Application Server Configuration Screens, you need to set these "Show Advanced Objects" Parameters to TRUE. Additional information can be acquired from reading through the Siebel Version 7.8.2.x Bookshelf > Siebel System Administration Guide > Chapter 6: Configuring Siebel Servers > About Siebel System Parameters > About Advanced Parameters :

Parameters that affect or modify advanced product functionality are, by default, hidden from the Server Manager GUI.

<Continued ...>

Message 2

To make advanced parameters visible, make sure the component-level parameter Show Advanced Objects (alias ShowAdvancedObjects) is set to TRUE for the server component Server Manager (alias ServerMgr) on the Siebel Server you want to see the advanced parameters for. The default value for this parameter is FALSE.

However, once we had set this "ShowAdvancedObjects" Parameter setting from "FALSE" to "TRUE", we were still unable to actually see these DSFileSystem and DSMaxFetchArraySize Parameter Settings from within the Siebel Version 7.8.2.x Enterprise Application Server Component "Call Center Object Manager" Parameter Settings. I therefore raised Product Defect Change Request Number 12-1CG9TS3 to have this matter investigated further.

Keywords: Siebel 7.8.2.x, File, System, Parameter, Settings, "ShowAdvancedObjects", DSFileSystem, DSMaxFetchArraySize, Server, Components

Applies to:

Siebel eConfigurator - Version: 7.8.2.4 [19224] and later [Release: V7 and later ]
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.8.2.4 [19224]
Database: Oracle 9.2.0.5
Application Server OS: Sun Solaris 9
Database Server OS: Sun Solaris 9

This document was previously published as Siebel SR 38-3392775747.
***Checked for relevance on 13-12-2010***

Symptoms

Customer is connected to application in thick (srf in local and db in server) client but cannot reach a tab under Administration Product > Product Definitions > Then select a Product Workspace > Constraints.

If they try to open the tab following message is popped up:
Cannot load rule function table. Plese check if file system directory for cache file is valid or not. Please contact your system administrator.(SBL-CFG-00183)

Product Release: V7 (Enterprise)
Version: 7.5.2.7 [15058] ESN Com/Med
Database: Oracle 8.1.7.4
Application Server OS: HP-UX 11i
Database Server OS: HP-UX 11i

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

Symptoms

SBL-CFG-00124, SBL-CFG-00145, SBL-CFG-00202

Hi,

We are experiencing some problems with models in eConfigurator when adding a group of products from different classes in a model under a Class or Dynamic Class domain, without specifiying class (in order to group products from different classes, bookshelf Product Administration Guide, chapter "Adding a Group of Products from Different Classes" )

A customizable product which contains a domain with products from different classes, works itself, but if this CP is a component of other different CP, this CP doesn't work. The error is the following (part is in spanish) :
      "Error al obtener un nuevo trabajador"
      "Error muy grave al completar el modelo"
      "Excepción 44 en módulo de trabajador:
       "Catalog did not build. Possible model inconsistency"

Curiously, this error appears only if one of the customizable products contain a rule. Of course, if you specify a class in the relationship, the CP´s work as well.

The same design of these customizable products works in eCommunications v.7.5.2.211 ENU, without errors.
We are using eCommunications v.7.5.2.214 ESN. So the only difference may be the language.

Can you help us?

Thank you in advance.

Solution

Message 1

For the benefit of others:

Behavior:

When the following stucture exist for a CP, (customizable product) (which also contains nested CP as in CP 2 below):

CP 1
|-------CP 2
|-----------Prod A
|-----------Prod B

And product A & B belong to two different classes, and there is a rule in CP 2 (say, Prod A excludes Prod B),

Upon validating CP 1, the following error message is invoked:

Error getting new worker
Fatel error completing model
Exception 44 in worker Module
Catalog did not build. Possible Model inconsistancy.

Resolution:

The above behavior was determined to be a product defect and Change Request 12-FTALD3 has been submitted to address it.

SBL-CFG-00175: Customizable Product Runtime Internal Error in function %1. Error Dump: %2.

Date:

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3.5 [16183] Com/Med
Database: Oracle 9.2.0.2
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: HP-UX 11.0

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

Symptoms

SBL-CFG-00175

we are running eConfigurator on 7.5.3.2 and had some custom templates that exposed child product attributes on the parent product's user interface. As many of you know, this requirement and customization is very common. They then upgraded to 7.5.3.500 (standard interactivity mode), and this customization stopped working. The error they recieve when navigating to a screen that tries to do this is

'Customizable Product Runtime Internal Error in function CSSCfgUIService::GetAttributes. Error Dump: Got NOTOK.(SBL-CFG-00175)'

We tried this with a much simpler template that I created for another client and on 7.5.3.400 and recieved the same error

Solution

Message 1

Applies to:

Siebel Configurator Runtime - Version: 8.1.1 [21112] - Release: V8
Information in this document applies to any platform.

Symptoms

A complex product has a component product in a product type relationship which has a minimum cardinality of 1. There is also a constraint rule to limit the quantity of the component product. The constraint has a specific explanation text.

In configurator when no product is selected from the relationship then a correct warning message is displayed as follows:
“There is an error with your last request. You are below the minimum quantity of 1 for …. Please click the Undo button to undo your last request. (SBL-CFG-00170)”

When you select the Explanation button there is no further explanation. Why is the specific constraint explanation not displayed in configurator?

Cause

When you have both a cardinality rule and a constraint rule not satisfied at the same time for the same product relationship quantity then the cardinality rule is given priority. This is why the custom explanation is not displayed.

Solution

If you remove the cardinality rule from the product relationship then you will see the explanation message when the constraint rule is not satisfied.

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

Date:

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

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

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 Promotion Violation. THe following Product or Attribute is no longer part of the promotion. : 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:

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)

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

SBL-CFG-00163: The item that you are trying to customize contains invalid sub-items.

Date:

Applies to:

Product Release: V7 (Professional)
Version: 7.8.2 [19213]
Database: Oracle 9i
Application Server OS: Sun Solaris 8
Database Server OS: Sun Solaris 8

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

Symptoms

SBL-CFG-00163

This is a follow-up SR of #38-2902810351 where the customer is experiancing the following.

They are on V7.8.2 and were trying load attr_id on S_ASSET_XA table. However, as per CR #10480570, ATTR_ID is not a required column and hence the customer was suggested to leave this column as null. However, the customer claims that whey try to modify an asset having attributes through Product Configurator and if there is no value in column ATTR_ID, they are getting the following error

"The item that you are trying to customize contains invalid sub-items are attributes or does not comply with the corresponding customizable product definition. Do you wish to proceed and have the invalid selections removed or fixed? (SBL-CFG-00163)"

Solution

Message 1

For the benefit of all users:

Summary:

Customer imported assets with EIM because they came from a legacy system.

Trying to load attr_id on S_ASSET_XA table per EIM was not possible. However, as per CR #10480570, ATTR_ID is not a required column and hence the customer was suggested to leave this column as null.

When trying to modify an asset having attributes through Product Configurator and if there is no value in column ATTR_ID, eConfigurator changes the attribute values of the asset. If you have rules then this could lead to a conflict and error message:

"The item that you are trying to customize contains invalid sub-items are attributes or does not comply with the corresponding customizable product definition. Do you wish to proceed and have the invalid selections removed or fixed? (SBL-CFG-00163)"

Solution:

Change Request CR 10508706 has been logged so that configurator works correctly in case S_ASSET_XA.ATTR_ID is null.

With kind Regards,
Siebel Technical Support

Keywords: EIM, Asset, attribute, S_ASSET_XA, ATTR_ID

Applies to:

Siebel eConfigurator - Version: 7.7.2.5 SIA [18368] to 8.1.1.3[21219] - Release: V7 to V8
HP-UX Itanium
Product Release: V7 (Enterprise)
Version: 7.7.2.5 [18368] CHS Com/Med
Database: Oracle 9.0.1.2
Application Server OS: HP-UX 11.0
Database Server OS: HP-UX 11.0

This document was previously published as Siebel SR 38-2952503327.
***Checked for relevance on 15-10-2010***

Symptoms

Applies to:

Product Release: V7 (MidMarket)
Version: 7.5.2.214 [16066] MME
Database: Oracle 9.0.1.3
Application Server OS: Microsoft Windows 2000 Server
Database Server OS: Microsoft Windows 2000 Server

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

Symptoms

Symptoms

SBL-CFG-00162

Hi,

Our eConfigurator is giving validation errors with Date attributes. When selecting the Date (our ESN deployment supports a dd/mm/yyy) as European Format gives Error1 (see attachments). When selecting the Date Attribute as American Format gives Error2 (see attachments).

Can you please indicate further steps in order to resolve the issue?

Regards
Sebastián Hormaeche

Solution

Message 1

For the benefit of other users:

The issue encountered has to do with Date Fields’ behaviour with Standard Interactivity User Interface (UI) in eConfigurator. To reproduce the issue create a product with a Date attribute, create a Standard Interactivity UI and set the Date settings to dd/mm/yyyy.

- Introduce 17/10/2007 => error: 10/17/2007 is not a valid value for Date_Attribute.(SBL-CFG-00162)
- Introduce 10/17/2007 => expected behaviour: the value '10/17/2007' cannot be converted to a date time value.(SBL-DAT-00359)

Change request #12-1LMFG3A was logged to address this issue.

A possible workaround is to use High Interactivity UI for the product, as the issue does not occur in this type of interface.

Regards,
Siebel Technical Support

Additional Keywords: Product Configurator, SI

Applies to:

Siebel Configurator Runtime, SPE - Version: 8.1.1 [21112] - Release: V8
Information in this document applies to any platform.

Symptoms

Statement of what the issue is
Disconnecting an Asset for a product which actual attribute value does not exist any more results in an error.

Version 8.1.1

Cannot be seen in 8.0

Steps to reproduce:

Product of class with attribute enumerated.
Create order and asset it.
Modify used attribute value, release, clear cache. ( e.g.: Attribute Color with Red, Green and Yellow; asset has Yellow; but in the meantime Yellow has been removed from Color)
For asset hit Disconnect -> error.

log file shows following error message during execution of Business Service 'SIS OM PMT Service' invoke method: 'Synchronize' at 192d5938

EAISiebAdpt EAISiebAdptErr 1 000001ad4a3f0fe4:0 2009-06-22 15:00:02 [0] Method 'SetFieldValue' of business component 'MACD Quote Item XA' (integration component 'XA') returned the following error:
"Fiber is not a valid value for Value.(SBL-CFG-00162)"(SBL-EAI-04376) (0x6900a2)

Cause

Statement describing the cause of the problem:
Regression as not seen in 8.0

The proof that this is the cause of the problem:
tested

Solution

Fix Request FR 12-1TXBEP1 to solve change request CR 10569600 is a modification of Workflow SIS OM Disconnect Asset Sub-process. Detailled instructions are attached in TechNote FR#12-1TXBEP1.doc

References

SBL-CFG-00159

We changed the Product Names of 3 products while keeping their ROW_ID’s on S_PROD_INT intact.

They were then re-arranged in the Product Designer. Two of them, Wireless IntERstate LD and Wireless IntRAstate LD, were removed from the relationship (domain type = class) BeyondMobile Voice Features and then readded with their new product names, Mobile IntERstate LD and Mobile IntRAstate LD. Both of these products are required and there should be only one of each.

The third product was called Wireless International LD and was in the relationship (domain type = product) Wireless International LD. This product was renamed to Mobile International LD and is now part of the relationship Mobile International LD (domain type = product). This product has cardinality of 1 max, 1 min, 1 default. I believe the relationship record was deleted and a new one created with the name Mobile International LD.

Cardinality and quantity rules are no longer working. Customizing the service instance that was created and the order completed BEFORE releasing this new version of the customizable product is now adding a duplicate of these products that already exist. For some reason it doesn't see that they are already there and it adds another one. Customizing a new service instance that was completed AFTER releasing this new version is NOT adding duplicates of these products.

I did a comparison of the database records on S_ORDER_ITEM for a service element that was created before and after the new version of the customizable product was released. The PROD_IDs remained the same, however I noticed that the PORT_VALID_PROD_ID and PROD_PORT_ID values are different. When I update the records that were created BEFORE the new version with the PORT_VALID_PROD_ID and PROD_PORT_ID values that are on the records created AFTER releasing the new version, and then I customize the Service Instance, the duplicates are not created.

For example I updated the old record to have the new v...

Solution

Message 1

For the benefit of other users:

A sub-product was used in a CP model in one product-type relationship (minimum cardinality = 1) and in several (at least 1) class-type relationships (no minimum cardinality).
The CP was added to a sales order associated to an account and made into an asset. The asset showed the sub-product with a quantity of 1, coming from the product-type relationship.
The sub-product name was then changed and the product-type relationship pointing to it was deleted from the CP’s product designer before a new one was created back with type = product. A new CP version was released.

At this point, the asset was modified from the account customer portal, thus bringing a warning message indicating the model change when entering the configuration pages.
When auto-match repaired the sub-product from the now missing relationship, it picked the first relationship the sub-product belonged to, which in this case ended up being the class-type relationship. This is an undetermined behavior though and in some other CP models, auto-match could pick the product-type relationship. That is why, among other reasons, we generally recommend having sub-products belong to only one relationship.

Continuing on, when there was at least one active rule in the CP’s model (related or not to the sub-product), the eCFG engine directly added a new line item with an action type of Add.
[...]

Message 2

[...]
When there was no active rule, it did not add the sub-product but instead showed a red star in the selection pages indicating the missing required sub-product.
This is the subject of CR# 12-1HC2FI1. The customer always had rules so this was not an issue for them though.

Then, when the environment variable PRESERVE_ENGINE_AND_USER_PICKS was set to N (the eCFG engine treats every product selection equally, i.e. as a user pick), the pre-existing line item’s action code stayed unchanged as “–“.
When the variable was set to Y, eCFG considered the initial sub-product selection as an engine pick so it dropped it and set the pre-existing line item’s action code to Delete.

Changing product’s name is an essential part of the customer’s requirement/business. Instead of modifying the product name field, the customer was advised to use a custom field as a display name for the product name so the product name itself would not change and stay stable, which ultimately prevents the above confusion in the first place.

Thank you,

About ERROR CODES

Privacy Policy

Contact Us

SBL-CFG-50277: Unable to get the value of %3 from property %4 for Attribute %1 of Product %2

Applies to:

Purpose

Scope