SBL-DAT-00374: Date out of range. Valid range is January 1, 1753 to December 31, 4712.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3.5 [16183] ESN
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: HP-UX 11i

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

Symptoms

SBL-DAT-00374

When running a Workflow using wfprocbatchmgr, the following error is raised :-

ObjMgrLog    Error    4    2007-04-16 11:32:07    (SBL-DAT-00374) Fecha fuera de rango. El rango válido es de 1 de enero de 1753 a 31 de diciembre de 4712.

Error translated :-

Date out of range. Valid range is January 1, 1753 to December 31, 4712.

Running the same Workflow via wfprocmgr works fine.

Solution

Message 1

Hello Luis,

Thank you for using the Siebel SupportWeb.

For the benefit of other readers, the following error was seen in the log when running wfprocbatchmgr :-

ObjMgrLog    Error    4    2007-04-16 11:32:07    (SBL-DAT-00374) Fecha fuera de rango. El rango válido es de 1 de enero de 1753 a 31 de diciembre de 4712.

Error translated :-

Date out of range. Valid range is January 1, 1753 to December 31, 4712.

Running a Workflow Process against a specific row_id worked fine, with no error reported. When running wfprocbatchmgr, it executes SQL to find all rows in the underlying Business Object for the Workflow Process (restricted by any Search Specification), then executes the Workflow against each row returned. In this case, it was found that certain rows in S_EVT_ACT had an invalid value stored in TODO_PLAN_START_DT, hence the error. After correcting these values to valid dates, the error did not appear again.


Siebel Technical Support

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3.8 [16192]
Database: Oracle 9.2.0.2
Application Server OS: Microsoft Windows 2000 Advanced Server SP 3
Database Server OS: Sun Solaris 2.7

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

Symptoms

SBL-DAT-00374

Hi Support,

we found a problem at the export function of Siebel.
The error occurs when performing an export from pricing administration/ price list line items.
This View has been customized and also includes the date field "Effective End Date" which somehow seems to cause the problem.
Example: We do have a price list with e.g. >4000 records - doing the export without this field shows the correct data.
See also attachment: export 1
export 2: shows the export including the field "effective end date" as txt
export 3: "effective end date" included export to csv

Please advise


Greetings

Wipke

Solution

Message 1

For the benefit of other readers:

DESCRIPTION:
Siebel export function does not export all records when specific date fields are included in the export.

INVESTIGATION:

A detailed log file has been created by setting the system preference
SIEBEL_LOG_EVENTS = ‘All’

The log file shows multiple error related to date fields:

ObjMgrLog    Error    4    2005-06-13 14:34:58    (SBL-DAT-00374) Date out of range. Valid range is January 1, 1753 to December 31, 4712.

CAUSE:

In Siebel 7.0.x, the Siebel object manager (data objects layer) now validates dates that are inserted into the database per change request 12-W2WMI. It is a new relability feature to prevent users from entering date ranges that are not supported by some of our databases.
It is not possible disable it.
Documentation request 12-CDCZCE has been logged for this feature to be detailed in the Siebel Bookshelf.

SOLUTION:


Enhancement request 12-11LV4D9 has been logged: It should be possible to deactivate date range validation.

For the time until this ER has been fixed, I suggest to validate the incoming data before storing it in the Siebel db.


Thank you

Siebel Technical Support

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3.6 [16186] Fin Svcs
Database: IBM DB2 8.1 FixPack 3
Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: IBM AIX 5L 5.1

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

Symptoms

Hello,

we have the following problem regarding the EAI Siebel Adapter. We use the EAI Siebel Adapter to process a Siebel Message that contains multiple records that should be imported. When an error occurs the error message describes the error and it indicates the record in which the error occured. The record is indicated by the combination of the fields included in the integration component key. The problem is that some times the values of the fields included in the integration component key are not displayed by the error message. Instead the literal "IS NULL" is displayed for each of these fields. For example, the following message was provided by the EAI Siebel Adapter during the importation of products.

Error Message: Method 'SetFieldValue' of business component 'Internal Product' (integration component 'Internal Product') for record with search specification '[Part #] IS NULL' returned the following error:"Date out of range. Valid range is January 1, 1753 to December 31, 4712.(SBL-DAT-00374)"(SBL-EAI-04375), Error Code: undefined

In this case we cannot locate the record in which the error occured.

We are waiting for your response.

Dimitrios Berouklis

Solution

Message 1

For the benefit of other users:

EAI Siebel Adapter display error message that contains a field with a value null. This is intermittent behavior. Some time it shows the values but some other time it shows null value. Change request#12-NJ171O logged against this behavior. Please note that change requests will be analyzed, prioritized and fixed in feature product release.

Thank you,

Siebel Technical Support