My Oracle Support Banner

Query On DTYPE_DATE Fields using DDMMYY Behave Differently In Siebel2018 vs IP14, Error SBL-DAT-00359 or 0 Row Selected (Doc ID 2512580.1)

Last updated on JULY 21, 2020

Applies to:

Siebel CRM - Version 18.10 and later
Information in this document applies to any platform.

Symptoms

On : 18.10 version, Client Functionality

ACTUAL BEHAVIOR
---------------
We have recently upgraded our Siebel application from IP14 to Siebel 2018. The users have now complained about some missing functionality compared to the previous Siebel version.
When searching on a field with format DTYPE_DATE, it was previously possible to search with DDMMYY, but now this doesn’t work, and they need to search with DD.MM.YY.

Please see the attached WebEx recordings from Siebel IP14 where it works, and from Siebel 2018 which illustrates the problem.

How can we get this functionality back in Siebel 2018?

FYI: I have also compared the Administration - Data > Locale setup between our old environment and our new environment, and it looks the same.


EXPECTED BEHAVIOR
-----------------------
Search with DDMMYY for DTYPE_DATE should work in IP18 the same way as in IP14.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Login to Call Center (Open UI)
2. Navigate to Administration Data - Locale
3. Query for "ENU"
4. Update like customer's screenshot has:

Locale Code:* ENU
Locale Name:* English - United States

UI Directionality:* Left To Right
International Dialing Code: Norway(47)
Locale Posix Code: en_US
Positive Currency Format:* s100
Nevative Currency Format:* (s100)
Currency Decimal Separator:* ,
Currency Grouping Separator:* .
Number Decimal Separator:* ,
Number Grouping Separator:* .
Number Leading Zero: checked
Number Fractional Digits:* 2
List Separator:* ,

Long Date Format:* d. MMMM yyyy
Short Date Format:* dd.MM.yyyy
Date Separator:* .
Time Separator:* :
Time Leading Zero: checked
24-hour clock: checked
Time Designator Position: Suffix
Time A.M. Designator: AM
Time P.M. Designator: PM
First day of week: (blank)

Workdays

Sunday: not checked
Monday: checked
Tuesday: checked
Wednesday: checked
Thursday: checked
Friday: checked
Saturday: not checked.


5. Update the same with Siebel Server - Control Panel - Regional Settings -
Date format

Region and Language

Formats

Format:

Norwegian, Bokmal (Norway)

Language preferences

Date and time formats

Short date: dd.MM.yyyy
Long date: d. MMMM yyyy
Short time: HH:mm
Long time: HH:mm:ss
First day of week: mandag

Examples

Short date: 04.02.2019
Long date: 4.februar 2019
Short time: 12:51
Long time: 12:51:56


6. Restart Gateway and Siebel Server services.
7. To test, I use Opportunities > My Opportunities in Siebel Call Center, I
log in as SADMIN. I use 2 Date fields there: Start Date, Close Date.

When I search by 28.02.19 in Siebel 2019, 1 row is returned which is the correct esult.

When I search by 280219 I got an error in Siebel 2019, the error is:
The value '280219' cannot be converted to a date time value.(SBL-DAT-00359)

In customer's case, they get 0 rows or the same error SBL-DAT-00359, the
error message is not always shown.


Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.