Search This Blog

SBL-CFG-00162: %1 is not a valid value for %2.

Applies to:

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

Symptoms

Steps to reproduce

1)Log into Call Center
2)Create an Attribute Definition called "Date" of Type Date
3)Create a Product Class called "Laura Test"
4)Add this Attribute with name "Start Date" to the Product Class.
5)When the attribute is added to the Product Class choose Menu > Translations and create a translation for ENU language with a value "ENU START DATE"
6)Create a Product called "Test Laura" and assign the new Product Class to the Product
7)Validate the Product
8)Note that when the Configurator opens that ENU START DATE is displayed for the attribute name
9)Input a piece of text into the attribute field (remember type is Date)
10)Error is thrown and the Attribute specified does not appear with the translated name

Attribute should appear with the correct translation text and not in the original attribute name.

Error that does appear:
SBL-CFG-00162: qwerty is not a valid value for Start Date.

Error that should appear:
SBL-CFG-00162: qwerty is not a valid value for ENU START DATE.

See recording: Attribute Translation SBL-CFG error message.wrf

This recording needs to be viewed using webex player. This player can be downloaded from www.webex.com

Cause


This issue is due to a product defect.


The "SBL_CFG" error messages are controlled in the underlying code behind Product Configurator. These error messages cannot be edited through repository or web template files. The translated attribute name should be displaying but instead the original name of the attribute that is associated to the product is showing.

Solution


This issue has been logged as a new Product Defect CR 10587909.

References

BUG:10587909 - TRANSLATION STRING FOR PRODUCT ATTRIBUTE IS NOT APPEARING IN "SBL-CFG" ERROR MESSAGE

Applies to:

Product Release: V7 (Enterprise)
Version: 7.8.2.5 [19227] Pub Sect
Database: Oracle 10.2.0.2
Application Server OS: IBM AIX 5L 5.3
Database Server OS: IBM AIX 5L 5.3

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

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

BUG:10569600 - ASSET BASED ORDERING DOES NOT WORK IF PRODUCT DEFINITION HAS CHANGED

Applies to:

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

Symptoms


If an attribute LOV domain is updated, with values removed, an error is encountered when modifying the asset.

The following is the error from the log:

EAISiebAdpt EAISiebAdptErr 1 000000024ab70a1c:0 2009-09-21 10:08:06 [0] Method 'SetFieldValue' of business component 'MACD Quote Item XA' (integration component 'XA') returned the following error:
"1 is not a valid value for Previous Value.(SBL-CFG-00162)"(SBL-EAI-04376) (0x6900a2)

The application is having issues resolving the Previous Value if the value is outside of the Attribute LOV domain

Changes

1-) Administration - Products > Attribute Definitions

2-) Create 2 attributes

FR 1 - freeform

FR 2 - { 1, 2 , 3}

Release them

3-) Administration - Products > Class Administration

Create a class and add the above attributes.

4-) Administration - Products > Product Definitions

Create 2 Products with the above class. Release them.

5-) Administration - Products > Product Definitions

Create a customizable Product and add the 2 products created on step 4 in different relationships.

Set Min Cardinality of the Child Products to 1.

=> Product Structure

Root Product

Rel 1 - Child Product 1 - Min Card = 1
Rel 2 - Child Product 2 - Min Card = 1

6-) Navigate to Accounts and create a new one

7-) Drilldown on the Account Name and create a Quote

8-) Add Root Product to the Quote (the child products will be added by default)

9-) Hit Auto Order

10-) In the Order, set the Status of the 3 line items to Complete.

11-) Set the Status of the Order to Complete too.

12-) Hit Auto Asset and the products should be displayed under Accounts > Account Summary > Installed Assets applet

13-) Navigate to Administration - Products > Attribute Definitions

14-) Lock attribute FR 2 and change its values to - { 11, 22 , 33}.

15-) Release it and clear the cache.

16-) Navigate to Administration - Products > Product Definitions

17-) Delete Rel 2.

18-) Add the same relationship again:

Rel 2 - Child Product 2 - Min Card = 1

19-) Release the Root Product. Clear the Cache.

20-) Navigate to Accounts > Account Summary > Installed Assets applet

21-) Hit Modify. A warning message is displayed as expected. Hit Ok.

22-) Hit Done and you will get an error message related with a workflow.

SBL-BPR-00162: Error invoking service '<?>', method '<?>' at step '<?>'.

Cause


The behavior reported was considered a Product Defect BUG 10576833

According to engineering review, the business component code currently validates the attribute value for the "value" & "previous value" fields. However, if as is the case in this scenario, the attribute value is removed from the enumerated list, then on modification of the asset, an error is thrown when attempting to save the value in the previous value field. However, since previous value field is used to provide historical data, the validation is not required.

Solution


The fix included in the 8.1.1.2 Fix Pack.

For other versions, please log a Service Request in order to start the Fix Request process.

References

BUG:10576833 - SBL-BPR-00162:ERROR INVOKING SERVICE '', METHOD '' AT STEP '' WHEN MODIFYING AN ASSET

No comments:

Post a Comment