This site has been specifically designed to troubleshoot all Siebel related issues. When any exception or error occurs in Siebel, the cause is given by a specific error code. Whenever we face an issue, we try to Google or search for a resolution mostly from Oracle Support, IT Toolbox, Siebel Unleashed etc. I have tried to search for all the solutions for a particular error code in all the mentioned sites and put all the solutions in this site.

Search This Blog

SBL-DAT-00493: Text constant (%1) needs to be enclosed in single quotes.

I reproduced the problem in Vanilla V8.0 ( see the attached file Account.sif;
fields "Test Calculated*")

So it seems the field A has a Text type in V8.0 whereas it had
an Number type in V7.5.

I didn't find any documentation in bookshelf V7.5 that recommend
setting a specific type for calculated fields (The type was dynamically deduced).

In V8.0,
since Revision A (April 2007), in the bookshelf "Siebel Developer's Reference > Operators,
Expressions, and Conditions >Calculated Field Rules",there has been this sentence:"For
a calculated field whose calculated value is not of type DTYPE_TEXT, the field type must be
specified explicitly."

Is it a standard behaviour in V8.0?If yes, is there any
documentation about how we can migrate all our existing calculated Fields?( we didn't find
anything in the Database Upgrade Guide)

Thanks in advance.

Solution

V8 has changed the way the calculated fields interact with other parts of the application.

Bookshelf states:
"Siebel Developer's Reference > Operators, Expressions, and Conditions >Calculated Field Rules",
"For a calculated field whose calculated value is not of type DTYPE_TEXT, the field type must be specified explicitly."

This caused the customer an issue as when upgrading the calculated fields gave a search error.

There were two ways in which this issue could be resolved.

1) After upgrading, navigate through the application and look for the error in the logs. This will then give the BC upon which the error occurs.

2) CR#12-1JPYP1L and CR#12-1JVI3Q3 have been raised for this issue; one to see if this can be added to the upgrade process and the other to see if the functionality of v7.x can be regressed for v8.

Symptoms

SBL-DAT-00493

Dear Support Team,

We have migrated from 7.5.2 to 7.5.3.1, in the forecast area before
migration, subordinates were able to submit their forecasts, but after migration they can't
submit their forecasts. When they try to submit their forecasts, the application crashes.
Attached you can find siebel log file in which SIEBEL_LOG_EVENTS was set to 4. I logged in as a
subordinate and then navigate to forecasts screen and then tried to change status field from
"Active" to "Submitted". In the log file this change starts from line 22025.This thursday we
will go for production test, for that reason could you please advice us ASAP.

Solution

Customer found that they were unable to submit forecasts and it crashed the Client application.

Turning on Client-side logging had the error ""ObjMgrLog Error 4 2003-10-21 16:14:02 (SBL-DAT-00493) Text constant (Y) needs to be enclosed in single quotes. Please continue or ask your systems administrator to check your application configuration if the problem persists." followed by a call stack.

This behavior was not reproducible with the Standard SRF and only with the custom SRF. The log indicated that the error occurred after an insertion into S_ACCNT_ATT table. Customer had a custom Business Component called "Forecast Attachment" and it was based on S_ACCNT_ATT table. In forecast submission Customer was generating forecast data (based on opportunities and products) into an excel file.

One of the custom user properties on Forecast 2000 -- Forecast Business Component, had a text constant (Y) without quotation marks. Customer fixed this User Property and they were able to successfully submit forecasts.

When querying on an MLOV enabled field in the customer's database with for example

EXISTS([LF Area Category] = Skydda)

this produces an SQL statement that has one bind variable missing,

resulting in the error message

"Not enough values for host variables"

This is reproducible in
7.5.3.11 [16199] SVE SIA (Fin Svcs)

Change Request
12-U4DBNJ
"Less bind variables available than requested by the SQL spool. This is related to MLOV config."
had been logged for this behavior
and this is fixed in
7.5.3.12 Fix Pack [16272]
(Fix request 12-UXRMM1)

Symptoms

SBL-DAT-00493

If we define a Detail BC as a Business Component which use MVL to call other calculated
fielda from a Main BC. (e.g. Account BC and Contact BC use MVL to call Field "A" which is a
calculated field from CUT Address BC)

The scenario is shown as follows

Detail BCs
cannot call any calculated field (e.g. Field "A") from a Main BC which contain a calcuated
formula as IIf([English Flag] = 'Y',1,0)

This leads to the error message, "Text constant
(Y) needs to be enclosed in single quotes", when the Siebel application is turned
on.

However, if Detail BCs are not use MVL to call Field "A", using the same formula in
Field "A" will not cause an error message