SBL-DAT-00436: Invalid definition for translated code column '%1' in table definition '%2'.

Applies to:

Siebel Tools - Version: 7.5.3.3 SIA [16172] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3.3 [16172] Cons Sec
Database: Oracle 9.2.0.2
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: Compaq Tru64 UNIX

This document was previously published as Siebel SR 38-1604439241.
Reviewed for relevance September 27, 2010.

Symptoms

SBL-DAT-00436

Hi

I had a requirement to MLOV 4 vanilla columns. After completing this, I ran the MLOV Upgrade utility. This failed during validation, identifying 36 columns with the error:

1- Two or more columns defined in the same LOV domain are inconsistently bounded (one bounded, one not)
2- Two or more columns are defined in the same LOV domain and at least one of them does not have a Translation Table Name of S_LST_OF_VAL.

I tried correcting this, following the fix as in Bookshelf 7.5.3, subsection 'To fix the LOV types that appear in the log file'.

Please note I did not fix every column as I have made the appropriate checks and am aware some columns point to LOV types that are not translatable.
Step 7 mentions 'Set the Translate Table name for all columns displayed to S_LST_OF_VAL.'

On making this change on the server, my newly compiled srf causes the application to crash, with the following error message when the application first loads:

We detected an Error which may have occurred for one or more of the following reasons:

Invalid definition for translated code column 'Organization.PROD_CD.TransCode' in table definition 'Internal Product'.(SBL-DAT-00436)

I can get rid of this error, and allow the application to work normally, if I remove the S_LST_OF_VAL that I added to column (PROD_CD) on table (S_PROD_INT). Please can you tell me what to do, as if I do not make this change, the MLOV upgrade utility will fail during verification.

Cause

The cause is a product defect.

Solution

Message 1

For the benefit of other users, the majority of errors that were in the validation error log were resolved by setting to TRUE the LOV bounded property of the target column as documented in:

Siebel Tools Reference Version 7.5.3
Pick Applets and Static Picklists
Multilingual Lists of Values

"Check that all the columns using that type have a check mark in the LOV Bounded property."


The following error occurred when Translation Table property was set to 'S_LST_OF_VAL' on column S_PROD_INT.PROD_CD when enabling Multilingual Lists of Values on this column:

We detected an Error which may have occurred for one or more of the following reasons:
Invalid definition for translated code column 'Organization.PROD_CD.TransCode' in table definition 'Internal Product'.(SBL-DAT-00436)


The reason for this was found to be that there are four standard fields on business component 'Internal Product' which are defined on column S_PROD_INT.PROD_CD and these four fields also have multiple different pick lists. When all fields bar one are inactivated, the MLOV can be enabled and the application works correctly.

Change Request 12-R0KRSU has been logged since the standard configutation precludes enabling MLOV on PROD_CD unless some fields are disabled.

Keywords: MLOV, multi-lingual list of values, upgrade,

Applies to:

Siebel Tools - Version: 7.7.1 SIA [18306] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.7.1 [18306] Auto
Database: Oracle 9i
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: Sun Solaris 8

This document was previously published as Siebel SR 38-1400357527.
”Checked for Relevance on 07-09-2010

Symptoms

SBL-DAT-00436

Hi,

We have a requirement in Picklists wherein we need to store a code in the Db and display a descriptive value.

We have searched the support web and found MLOV configuration as the solution. Given below are the steps that were mentioned:

In Tools OBE Table --> Column, the "Translate" and "Translation Table Name" properties for the corresponding Columns should be set to "TRUE" and "S_LST_OF_VAL" values respectively.   

After performing these configuration changes, we are able to store the LIC in the Db.

But while doing this, we found that the "Translate" property is read-only for the vanilla columns even when the Table object is checked out and we are not able to change the settings. For Custom extension Columns we can set this property.

We also found one SR # 38-759905051 in reference which says that we cannot set the "Translate" property for vanilla fields on our own.
This property can be set only by the Siebel Expert Services.

Is there any other solution for storing the LIC in the Db without changing the settings for "Translate" property. If so please let us know.

Thanks & Regards,
Sunil

Solution

Message 1

DESCRIPTION:

After setting SR_AREA to multilingual LOV (MLOV) the application does not longer start.

SYMPTOMS:

"Invalid definition for translated code column 'Organization.SR_AREA.TransCode' in table definition 'Service Request'.(SBL-DAT-00436)"

SOLUTION:

Change request 12-N7DQ64 has been logged: Can not transform SR_AREA to MLOV in SIA. The same process works in the horizontal application.

Please have in mind that the translation property of the column object is not related to the MLOV configuration.


Siebel Technical Support

Additional keywords: MLOV, HMLOV , hierarchical MLOV