SBL-DAT-00510: No language independent code exists for value '%1' and type '%2' with language '%3' in table '%4'.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.7.1 [18306] Fin Svcs
Database: Oracle 9i
Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: Sun Solaris 2.8

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

Symptoms

Hi,

Please refer previous SR Number: 38-2628032281 at CitiCapital.

At that time we don't have business approval to go ahead on work on this. Now we request you to go ahead and troubleshoot the issue.

The Issue :

On deletion of any contact or call report record we are getting an error. The error message is attached in the previous SR.

With this message I am trying to atatched my Local.

User name is am20912
password is avadya

Let me know if you need any other information.

Thanks & Regards

Solution

Message 1

From the generated log files, I found the following error message.

SBL-DAT-00509: Definition for table 'CX_CMG_NON_CITY' does not exist.

Upon my further testing, I found the following link is causing the problem.

Link : FINCORP Call Report/Contact(Non Citi)

This link has InterTable “CX_CMG_NON_CITY” but this particular Table in not in the customers database.

This issue got resolved after inactivating this Link.

Applies to:

Siebel Hospitality - Version: 8.0.0.5 [20420] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

When a pre-default value is specified for a MLOV, a TBUI will generate an error. This can be shown as follows:

Configure the Account Type field to be MLOV i.e. so that the LIC is stored on the database rather than the LOV display value.

- Table S_ORG_EXT, Column OU_TYPE_CD, set Translate = TRUE and Translate Table Name = S_LST_OF_VAL

- LOV: Add display value "Test Type 1" with LIC value "TEST_TYPE_01" for lov type 'ACCOUNT_TYPE', translate = true

On the Account BC, field Type maps to OU_TYPE_CD. Set pre-default value to

Expr: "LookupValue(""ACCOUNT_TYPE"", ""TEST_TYPE_01"")"

Create new account in Accounts screen, specify Test Type 1 for account type field. Save. Check the database and OU_TYPE_CD = TEST_TYPE_01, the LIC value.

Created a simple task to add a new account.

Run it, and the following error occurs:

No language independent code exists for value 'TEST_TYPE_01' and type 'ACCOUNT_TYPE' with language 'ENU' in table 'S_LST_OF_VAL'.(SBL-DAT-00510)

Cause

Existing Product Defect. Change Request Defect 12-1RF93U1.

Solution

The current workaround is to not specify a pre-default value.

References

BUG:12-1RF93U1 - PREDEFAULT ON MULTILINGUAL LOV FIELD CAUSES (SBL-DAT-00510) ERROR.

Applies to:

Siebel Hospitality - Version: 8.0.0.5 [20420] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

When a pre-default value is specified for a MLOV, a TBUI will generate an error. This can be shown as follows:

Configure the Account Type field to be MLOV i.e. so that the LIC is stored on the database rather than the LOV display value.

- Table S_ORG_EXT, Column OU_TYPE_CD, set Translate = TRUE and Translate Table Name = S_LST_OF_VAL

- LOV: Add display value "Test Type 1" with LIC value "TEST_TYPE_01" for lov type 'ACCOUNT_TYPE', translate = true

On the Account BC, field Type maps to OU_TYPE_CD. Set pre-default value to

Expr: "LookupValue(""ACCOUNT_TYPE"", ""TEST_TYPE_01"")"

Create new account in Accounts screen, specify Test Type 1 for account type field. Save. Check the database and OU_TYPE_CD = TEST_TYPE_01, the LIC value.

Created a simple task to add a new account.

Run it, and the following error occurs:

No language independent code exists for value 'TEST_TYPE_01' and type 'ACCOUNT_TYPE' with language 'ENU' in table 'S_LST_OF_VAL'.(SBL-DAT-00510)

Cause

Existing Product Defect. Change Request Defect 12-1RF93U1.

Solution

The current workaround is to not specify a pre-default value.

References

BUG:12-1RF93U1 - PREDEFAULT ON MULTILINGUAL LOV FIELD CAUSES (SBL-DAT-00510) ERROR.

Applies to:

Siebel CRM Call Center - Version: 7.8.2.7 [19234] - Release: V7
Information in this document applies to any platform.

Goal

Is there any limitation in using number of LOV for any Type value?

Solution

The is no limitation in using number of LOV for any Type value

This error is due to the way that MLOV enabled fields store the associated Language Independent Code in the database instead of the picked value. To achieve this behavior it is necessary for Siebel to perform a lookup using the value entered by the user in the MLOV field to obtain the corresponding LIC value.

This lookup functionality assumes that entered value will have a corresponding match in the Value field of the List of Values buscomp. This functionality is not compatible with the reconfiguration that the customer performed to pick the Description field instead, as there is no corresponding value found in the Value field of the LOV records.

When you have imported new LOV records you need to make sure that the Type value is pointed correctly to the field column

So you need to Check the TYPE VALUE in the column pointed to to the new LOV/correct LOV.?

Applies to:

Product Release: V7 (Enterprise)
Version: 7.7.1 [18306] ESN Com/Med
Database: Oracle 9.2.0.4
Application Server OS: Sun Solaris 8
Database Server OS: Sun Solaris 8

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

Symptoms

SBL-DAT-00510

When I try to create a new workflow, as soon as I hit CNTRL-N, as error message appears, indicating that "No language independent code exists for value 'IN PROGRESS' and type 'WFR_DSGN_STAT_CD' with language 'ENU' in table 'S_LST_OF_VAL'(SBL-DAT-00510)."

We have verified the List of Values in Tools and have noticed, that this Vlaue is really missing. Why?

Than we created this record, but received another error message: "No language independent code exists for value '' and type '<?>' with language '<?>' in table '<?>'(SBL-DAT-00510).

Thanks for your support!

Solution

Message 1

For the benefit of other readers, the user encountered the following error when attempting to create a new Workflow Process :

"No language independent code exists for value '' and type '<?>' with language '<?>' in table '<?>'(SBL-DAT-00510).

The user’s environment had the application in ESN, and Tools installed in ENU with Language set to ESN.

For this SR, the solution was to set both languages (ESN, ENU) in the mobile clients; a database extract was repeated and all the LOVs were then visible.

Applies to:

Siebel Tools - Version: 7.8.2.3 [19221] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.8.2.3 [19221]
Database: Oracle 9.2.0.6
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: Sun Solaris 2.7

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

Symptoms

SBL-UIF-00299

Hi!

I've tried the approached solution mentioned on the SR # 38-3322467511, but unfortunately the behaviour is not the expected.
According to message error

Wrong field values or value types detected in field Priority. Please re-enter your field values. (SBL-UIF-00299)
No language independent code exists for the value '3-Medium ENU X' and type 'ACTIVITY_PRIORITY' with language 'ENU' in table 'S_LST_OF_VAL' (SBL-DAT-00510)


it seems that there is no 'Language Independent Code' in LOV configuration which is incorrect as the 'LOVsConfiguration.jpg' attach file shows.

I do not know if this has anything to do with the fact that we use mulilanguage functionality, because I've already developped this solution before in other implementation and it worked (although it was only one language based).
In Tools configuration I replaced the Value field in Pick Map by Description (as in the SR above was mentioned).

Please let me know what I can do as a workaraound.
Thanks in Advance.

Cause

change request 12-RSSG1

Solution

Message 1

For benefit of other readers:

The customer had tried to reconfigure the picklist for a MLOV enabled field to allow the display of more than 30 characters. This was achieved by changing the corresponding pick map to use the Description field of the List of Values buscomp as the Pick List Field (instead of the default Value field).

The customer them could store text greater than 30 characters in the Description field of the appropriate LOV records.

Whilst this configuration successfully resulted in text of greater than 30 characters to appear in the picklist, once an item was selected it resulted in the following error message when the user tried to leave the field:

Wrong field values or value types detected in field Priority. Please re-enter your field values. (SBL-UIF-00299)
No language independent code exists for the value '3-Medium ENU X' and type 'ACTIVITY_PRIORITY' with language 'ENU' in table 'S_LST_OF_VAL' (SBL-DAT-00510)

Message 2

This error is due to the way that MLOV enabled fields store the associated Language Independent Code in the database instead of the picked value. To achieve this behavior it is necessary for Siebel to perform a lookup using the value entered by the user in the MLOV field to obtain the corresponding LIC value.

This lookup functionality assumes that entered value will have a corresponding match in the Value field of the List of Values buscomp. This functionality is not compatible with the reconfiguration that the customer performed to pick the Description field instead, as there is no corresponding value found in the Value field of the LOV records.

The only workaround for this behavior was to revert to the standard pickmap configuration having the Value field of the List of Values buscomp being picked into the MLOV field, but also picking the Description field into an additional field on the buscomp to allow the display of the corresponding long text whenever a item was picked.

There is an existing change request 12-RSSG1 requesting that maximum number of characters of the Display Value of List of Values should be increased.

keywords: pick; list; map; picklist; MLOV; Multi Lingual; LOV; List of Values; LIC; Lookup; Reverse Lookup;

reviewed for currency on 19/4/2010

Applies to:

Siebel Tools - Version: 8.1.1 [21112] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

When selecting a Picklist within the application we receive the following error: SBL-DAT-00510: No language independent code exists for value 'GTC' and type '' with language 'ENU' in table 'S_LST_OF_VAL'.

Cause

Migration fail to set values on the table definition

Solution

On the table definition the field had Translation table name set to S_LST_OF_VAL but the Lov Type and LOV Bounded was not filled in.
By setting these two fields to what was in the previous version, resolved the problem.
It seems that the migration had not taking this over.

References

NOTE:730901.1 - LOV/MLOVs return error message SBL-UIF-00299 and SBL-DAT-00510 for certain new LOV values in production.
NOTE:498134.1 - Using Business Component Encryption on LOV-based columns