SIEBEL ERROR CODES: November 2010

SBL-DAT-00373: DataSource named %1 could not be found. Check your configuration file.

Applies to:

Siebel Campaigns
Siebel Marketing
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V8 (Enterprise)
Version: 8.0 [20405] Auto
Database: Oracle 10.2.0.2
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Microsoft Windows 2003 Server SP1

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

Symptoms

The following errors could be seen in the Siebel Marketing Object Manager Log:

ObjMgrSessionLog    Error    1    000003d346c90d48:0    2007-08-20 13:47:41    (physmod.cpp (6827)) SBL-DAT-00373: DataSource named Analytics Web could not be found. Check your configuration file.

ObjMgrLog    Error    1    000003d646c90d48:0    2007-08-20 13:48:03    (sweview.cpp (1410)) SBL-UIF-00401: View: Campaign Literature View Admin does not contain applet: ISS Promotion List Applet.

ObjMgrLog    Error    1    000003dc46c90d48:0    2007-08-20 13:48:14    (sweview.cpp (1410)) SBL-UIF-00401: View: Campaign Execution History View does not contain applet: Campaign Load Wave Contact/Prospect List Applet.

Is any functionality loss to be expected by these?

Cause

The errors are due to the underlying code, but have no functionality impact.

Solution

Message 1

The behavior could be reproduced on fresh 8.0/8.1 installations, but no missing or not working functionality could be detected.

Change request 12-1LAUOJL has been logged to address this.

Applies to:

Siebel Tools - Version: 8.0 [20405] - Release: V8
Information in this document applies to any platform.
""Checked for Relevance on 31-Mar-2010""

Symptoms

We are getting error while creating genbscript manually from command prompt:

"DataSource named RBTDev8Ent_DSN could not be found. Check your configuration file.(SBL-DAT-00373)"

Cause

The customer tried to generate Browser scripts using the genbscript.exe utility from the command line interface and encountered the following error:
- - -
D:\sba80\siebsrvr\BIN>genbscript enu/siebel.cfg D:\sba80\sweapp\public\enu
CSSModel::Load failed.
---------------
DataSource named RBTDev8Ent_DSN could not be found. Check your configuration file.(SBL-DAT-00373)
---------------
(Please wait a few seconds for this utility to finish)

D:\sba80\siebsrvr\BIN>
- - -

Their "siebel.cfg" file was reviewed and revealed the following:
- - -
[Siebel]
...
DataSource = RBTDev8Ent_DSN
...
ServerDbODBCDataSource = RBTDev8Ent_DSN
...

[DataSources]
Local                    = Local
Sample                   = Sample
ServerDataSrc            = Server
GatewayDataSrc           = Gateway
...

[ServerDataSrc]
...
ConnectString = RBTDev8Ent_DSN
...
- - -

The Bookshelf mentions the following about the DataSource parameter:

Siebel System Administration Guide
Siebel Application Configuration Parameters
Siebel Application Parameters' Descriptions
- - -
Name DataSource

Description Name of the default data source that appears in the Connect to drop-down list in the Siebel login screen. Must correspond to an existing data source defined in the configuration file. By default, this parameter is set to Local.
- - -

The following parameter was therefore not appropriate:
- - -
DataSource = RBTDev8Ent_DSN
- - -

RBTDev8Ent_DSN was indeed not one of the DataSource names defined in the configuration file.

Solution

The issue was resolved once the DataSource parameter was set to one of the DataSource names mentioned in the siebel.cfg file.

Applies to:

Siebel Tools - Version: 7.5.3.15 [16279] to 8.1.1 SIA [21111] - Release: V7 to V8
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Professional)
Version: 7.7.2 [18325]
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server

Goal

How to setup an object manager to use EBCs (External Business Components)

Object Manager log reports

ObjMgrSessionLog Error 1 (physmod.cpp (6421)) SBL-DAT-00373: DataSource named IRMBDDataSrc could not be found. Check your configuration file.

ObjMgrMiscLog Error 1 (busobj.cpp (1345)) SBL-DAT-00222: An error has occurred creating business component 'IRM BackDoor Audit'
used by business object 'IRM Interface Analysis'.

How can the DataSource be added to the object manager parameter OM - Named Data Source name in 7.7.2?

Solution

Message 1

For the benefit of other readers:

Bookshelf,

Integration Platform Technologies: Siebel Enterprise Application Integration > External Business Components > Process of Configuring External Business Components >
Specifying Run-Time Parameters

has most of the required configuration steps for EBCs, including information on how the EBC DataSource / named subsystem can be added to the object manager parameter
OM - Named Data Source name

In additon to that

External Business Components (EBC) - access to Oracle via ODBC? No! - Datasource configuration steps (Doc ID 525666.1)

and (for Oracle):

External Business Component Datasource Setup for thin client - NamedDataSource and DSSQLStyle in 7.8 (Doc ID 536141.1)

helped to overcome this customer's EBC setup difficulties.

Note that when configuring a new named Subsystem / Datasource on the Enterprise,
you must not use spaces in the Datasource Alias name, as these cannot be accessed - not even from the srvrmgr command line tool

list advanced params for named subsystem "EBC Datasrc" would NOT WORK there

Change request 12-1F4B85L , Enterprise Profile Configuration allows creating Alias Names with Spaces
was logged to prevent creation of such alias names.

Engineering has closed the above CR with following comments "This is not a regular UI stitting on database tables, this will have code changes on the Server side in the Admin code and hence it is not advisable to implement it".

Regards,
Siebel Technical Support

Applies to:

Siebel Communications, Media and Energy CRM - Version: 7.7.2.8 SIA [18379] - Release: V7
Information in this document applies to any platform.

Symptoms

Statement of what the issue is
Overview:

When attempting to access the System Admin screens the following error occurs...

ERROR
-----------------------

ObjMgrMiscLog Error 1 0 2008-10-15 17:38:33 (busobj.cpp (1374)) SBL-DAT-00222: Une erreur s'est produite lors de la création du Business Component 'Server Compgroup Components' utilisé par le Business Object 'Server Admin'.

Cause

This issue is caused by an incorrect nameddatasource param for the OM...

ServerDataSrc,GatewayDataSrc;ExtranetCRM (see ; between data sources)

Tested this in a 7.7 environment and get same error.

Solution

Hi,

Thank you for your update.

Looking at the OM parameters you have attached we can see the NamedDataSource is set to

ServerDataSrc,GatewayDataSrc;ExtranetCRM

As you will see there is a ";" between GatewayDataSrc and ExtranetCRM. I believe this should be a ",". Can you modify this parameter in your OM to be

ServerDataSrc,GatewayDataSrc,ExtranetCRM

and check to see if this resolves the issue you are seeing.

Rgds,

Oracle Technical Support.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.7.1 [18306]
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: Microsoft Windows 2000 Advanced Server SP 4

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

Symptoms

SBL-DAT-00373, SBL-DAT-00403

Hello

I try to configure the Marketing Server.
I installed everything, launched components, wfp ....
Then I installed Siebel Analytics on an other Server but I installed the Siebel Analytics Web Server components on the same server than the Siebel Web Server.

I follow the guidelines in the bookshelf " Siebel Marketing Installation and Administration Guide" - " "Updating Marketing Connection Settings".

But I have still an error when I try to access to the catalog (as mentionned in "Guidelines for Testing the Marketing".
The system returns the message (in french) :
"Une erreur s'est produite en raison d'une recherche non valide du champ 'Type de paramètre'. L'expression non valide était :<?>"

In the log file of the Siebel Object Manager, I found :
ObjMgrSessionLog Error 1 0 2004-09-17 12:34:43 (physmod.cpp (6414)) SBL-DAT-00373: DataSource nommé Analytics Web introuvable. Veuillez vérifier le fichier de configuration.

I verify everything (Outbound Web Services),Marketing server, ODBC.

Do you have an idea to help me ?

FYI :
Siebel Web server is "SATAS20"
We connect with http://satas20/marketing_fra/

Siebel Analytics Web Server is : SATAS20
I can connect by using http://satas20/analytics

The integration of Siebel Analytics in Siebel is OK. I can access to Dashboard, answers.... inside Siebel.

Solution

Message 1

For the benefit of other readers, when ones click the “Folder Location” field in the Segments > My Segments view, the connection to the Siebel Analytics Web Server (SAW) is done through the corresponding Web Services (SAWSessionServiceSoap, WebCatalogServiceSoap and JobManagementServiceSoap) that should be configured in the Administration - Marketing > Servers view for the “Default Marketing Server” entry as instructed by the Siebel Marketing Installation and Administration Guide Version 7.7 > Installing and Administering Siebel Marketing. The mentioned error was generated when invoking these Web Services to connect to the SAW in order to get the proper folders list.

The English version of the message is:
SBL-DAT-00403 : The query could not be run because there is an invalid character in the field 'Parameter Type'. Please ensure that the value in the field is formatted correctly with only valid characters.

Customer was using a French application (FRA) and upon further investigation it was determined that the error was generated due to the fact that the List of Values (LOV´s) used by the Siebel Marketing application had not been correctly translated. After checking the list of values like SAW_SERVER_DETAIL, SME_DD_SERVER_TYPE and SAW_SERVER_DETAIL_TYPE and ensuring they were translated, the error message was eliminated.

Thank you,
Siebel Technical Support.

SBL-DAT-00369: An internal error with the connector DLL '%1' has occurred, preventing one of the following export functions from being loaded:

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3.4 [16180]
Database: Oracle 9.2.0.4
Application Server OS: HP-UX 11i
Database Server OS: HP-UX 11i

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

Symptoms

SBL-DAT-00254, SBL-DAT-00369

After installing the Siebel Industry Applications Sample Database the user accounts noted in the Siebel Release notes do not work for Siebel Communications, Media, and Energy.

eg. CCORWIN, PCARR, etc.

Only the sadmin account works. Other verticals seem to work fine.

Solution

Message 1

For the benefit of other readers:

The Customer was attempting to use the Siebel Version 7.5.3.4 SIA (Industry Apps - Comms / Media / Energy) client Application with Sample Database System which worked fine with 'SADMIN / SADMIN' User_ID and Password. However, when the Customer used these User_ID Login's "CCORWIN or PCARR" - then they would be presented with this error message instead : "The User ID or Password is not recognised"

This was similar error behavior to Service Request Number 38-1038794181 available out on SupportWeb. However, the workaround solution presented in this SR did not work as expected and this error message was presented instead :

"An Internal Error with the Connector DLL '<?>' has occurred, preventing one of the following export functions from being loaded: _SSACreateSqlObj@12 or SSASQLObjLogon@24. Please verify that the correct version of the runtime client specific to your database platform is installed on the machine where your Siebel Server is running. If this problem still persists, please verify that the Database Connectivity Settings are correct ? (SBL-DAT-00369)"

"The User Name you have entered is invalid or your user position is not defined. Please try and logon again or contact your systems adminstrator for assistance. (SBL-DAT-00254)"

Following on from my research and testing, I discovered that these User_ID's 'CCORWIN and PCARR' have been marked as inactive and are no longer required for the Siebel Version 7.5.3.x release.

Message 2

Continued...

The workaround solution this time was to use the other Login User_ID's such as TBALL (Tom Ball) or WBECKER (William Becker).

I have raised Product Defect Change Request Number 12-JZ7A1Z to have this new matter addressed.

Keywords: Siebel 7.5.3.x, CME - Comms / Media / Energy, User_ID, Login, Password, Sample, Database, System, Connector, DLL, SBL-DAT-00369, SBL-DAT-00254

SBL-DAT-00376: There is no field for denormalized column '%1' from table definition '%2' defined in business component '%3'.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.7.2.1 [18353] Life Sci
Database: Oracle 9i
Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: HP-UX 11i

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

Symptoms

SBL-DAT-00376

Hi Support Web,

I have a requirement where a Manager can enter Time Off Territory for his sales Rep via 'My Teams Time off Territory' View. I have unchecked the read-only property for the Position field in BC so that the manager can select the Sales Rep's position in the My Teams View. This record is not visible in the Sales Rep's 'My Time off territory View'. It appears in the Managers My Teams and My Time off Territory View but not in the Rep's My View.

How can we enable this functionality? I have changed the View Visibility Applet Type but of no use.

A quick response is greatly appreciated.

Thanks,

Solution

Message 1

For the benefit of other readers :

Customer was facing the following issue which was also reproducible in sample database.

a) login into Siebel Tools and query for "Pharma Time Off Territory" BC.

    Activate the following fields :
    Employee First Name (MM), Employee Job Title (MM) , Employee Last Name (MM) , Employee Login Name (MM) .

b ) Expose the controls corresponding to those fields in "My Teams Time oFf Territory " view -> "Pharma Activity TOT List Applet".

c) In the List Applet "Pharma Activity TOT List Applet", add an MVG applet "Employee Mvg Applet" on the List Column 'Owned By'. Expose this List Column on the list Applet . Save and compile the changes .

d) Relogin into Siebel application and navigate to "Pharma Activity TOT List Applet "    , click on the "Owned By" field to invoke the MVG Applet and click on the "New" button to add a new record in the associate applet , you get an error
" There is no field for denormalized column APPT_REPT_END_DT from table definition 'S_ACT_EMP' defined in business component 'Pharma TimeOff Territory'.

Change request 12-XQRR9R was logged to address the issue of denormalized column errors . Normally when a Change request is logged , it is reviewed , prioritized and a fix is implemented in one of the future releases.

Message 2

The workaround which was provided was that the customer was asked to manually add all the denormalized columns in the Business Component "Pharma TimeOff Territory". Customer did the changes and was able to successfully associate Employees in the associate applet.

Thank you,
Siebel Technical Support

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3 [16157]
Database: Oracle 9i
Application Server OS: Microsoft Windows 2000 Server SP 2
Database Server OS: HP-UX 11.0

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

Symptoms

SBL-DAT-00376

Our Load campaign has started to fail. We have not changed anything and teh load has been working ok.

[0] Method 'AssocCurrentRow' of business component 'Organization' (integration component 'Contact Organization') for record with search specification '[Name]="IAMS B2I UK"' returned the following error:"There is no field for denormalized column 'MEMBER_FLG' from table definition 'S_CONTACT_BU' defined in business component 'Marketing Contact'.(SBL-DAT-00376)"(SBL-EAI-04375) (0x6c3c)
--[1] Error invoking service 'EAI Siebel Adapter', method 'Upsert' at step 'Update Camp Con'.(SBL-BPR-00162) (0x80d8)
--Object manager error: ([1] Error invoking service 'EAI Siebel Adapter', method 'Upsert' at step 'Update Camp Con'.(SBL-BPR-00162) (0x80d8))
--Error (null) invoking method "(null)" for Business Service "(null)"
--Error invoking service 'Campaign Execution', method 'EAI List Import' at step 'EAI List Import'.(SBL-BPR-00162)

Solution

Message 1

For the benefit of other readers:-

The customer had been loading campaigns successfully. However they were now failing with the errors described.

The error indicated that the process was trying to update the S_CONTACT_BU table. This table holds the relationship between contacts and organization. The error was that the field MEMBER_FLG was not mapped in the Integration object “Marketing Contact”. This was correct as this mapping did not exist.

However all the contacts were coming from the S_CONTACT table so there was no need for the process to be trying to create new relationship records between contact and organization.

The customer investigated the was Contacts were being created in the application and it was determined that they were being created in the 'Default Organisation' which was incorrect. Once this was resolved the Campaign Load worked as expected.

Please note that if the contacts had been coming from an external source and contact/organization records were required, then the mapping of the MEMBER_FLG field would have to be addressed.

Siebel Technical Support

Keywords: campaign populate, integration object, marketing contact

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3 [16157]
Database: Oracle 9i
Application Server OS: Microsoft Windows 2000 Advanced Server SP 2
Database Server OS: Microsoft Windows 2000 Advanced Server SP 3

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

Symptoms

SBL-DAT-00376

Hi, we are trying to assign a new member to the Opportunity Sales Team (from the "Opportunity Form Applet - Child", Sales Rep field).
In that moment the application raise up a MVG Applet, and if we press the New button it pop up a shuttle applet ("Sales Team Mvg Applet")

When we select one member and press the Add Button it gives an error:
"No aparece el campo para la columna desnormalizada '<?>' de la definicion de tabla '<?>' definida en el business component '<?>'(SBL-DAT-00376)"
the translation would be:
"There is no field for denormalized column '<?>' from table definition '<?>' defined in business component '<?>'."

Do you have any idea of what is causing this error?

Thaks in advanced,

Diego Croce.

Solution

Message 1

Diego,

Thank you for using Siebel Support Web.

I have tested creating a new record in "Opportunity Form Applet - Child", Sales Rep field on our out of the box machine. I was able to do so without any problems. I could not reproduce the behavior. Hence, I guess you have customized "Opportunity Form Applet - Child" applet or the underlying BC. Please confirm and also please provide us the details of the configuration.

This error occurs because the columns in the table that is de-normalized and fields mapped to each of these columns do not exist in the custom BC. Please go to the cfg file and change the attribute "EnableShuttle" from TRUE to FALSE. This then will replace the question marks in the error message with the appropriate column, table name and business component name. Then you can add the missing columns.

Please test this and update your service request with the results.

Thanks

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

SBL-DAT-00366: Business component '%1' does not support cached update mode.

Applies to:

Siebel CRM - Version: 8.0.0.5 [20420] - Release: V8

Information in this document applies to any platform.

Symptoms

Data Map Objects have an advanced option called Cached Updates (See Siebel Order Management Infrastructure Guide > Data Transfer Utilities Business Service > Example of Defining Data Maps to Use with the DTU). This option enables cached updates at the destination buscomp level. All updates at the order buscomp, and its descendant buscomps, are cached and issued in one batch to the database.

However if a field in the Data Map is defined as an Oracle Sequence Object, you will get an error message e.g.

Business component 'Order Entry - Line Items (Simple)' does not support cached update mode.(SBL-DAT-00366)

Cause

This is currently the expected behaviour of the product. The Change Request Enhancement 12-1SPY32D has been raised for this to be addressed in a future release.

Solution

Removing the advanced option Cached Updates from the data map object prevents the error from occurring.

References

BUG:12-1SPY32D - CACHED UPDATE MODE DOES NOT SUPPORT ORACLE SEQUENCE OBJECT ON 'ORDER ENTRY - LINE ITEMS (SIMPLE)

SBL-DAT-00364: A beginning of file reached error has occurred. Please continue or contact your systems administrator if the problem persists.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3.3 [16172] Cons Sec
Database: Oracle 9.2.0.2
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: HP-UX 11.0

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

Symptoms

SBL-DAT-00364

Screen Quote
View Line Item Details
Applet Sizes x Dates

Scrolling to the top of the dynamic column list applet generates an error message
" A beginning of file reached error occured"

Select the Sizes x Dates applet and scroll down a couple of records.
Now scroll back up using the single record scroll button or using Ctrl + Up Arrow and the error message will pop up. The screen shot is attached.

Thanks,
shahid

Solution

Message 1

For the benefit of other users, the customer received the error “A beginning of file reached error has occurred. Please continue or contact your systems administrator if the problem persists (SBL-DAT-00364)” when scrolling in the Quotes ^ Line Items Detail ^ Size X Dates Applet.

Summary:

The issue was reproduced as follows:
1)    Create a Quote
2)    Associate the Quote to an Account
3)    Populate the Shipments tab with two Delivery Dates
4)    Select an address on the Personal Bill To/Ship To Tabs
5)    Click on Line Item Detail
6)    Add Product with a Size Distribution
7)    Select the “Fill Sizes All” button
8)    Scroll to the bottom of the Size X Dates value list
9)    Select Ctrl and Up Arrow to move up the list
10)    Before reaching the top user receives the error “A beginning of file reached error has occurred. Please continue or contact your systems administrator if the problem persists (SBL-DAT-00364)”

The situation was not reproducible with one shipment date. Searching on SupportWeb found Service Request #38-1168563861 and Change Request #12-JETMNB which has been logged on a similar issue and attached to this Service Request for your review. However, as this problem seems to be specific to having multiple Shipments displayed, Change Request #12-K4O1JC was created.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3 [16157]
Database: Oracle 9.2.0.2
Application Server OS: Microsoft Windows 2000 Advanced Server SP 2
Database Server OS: Microsoft Windows 2000 Advanced Server SP 2

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

Symptoms

SBL-DAT-00364

In a tree applet if the user uses the “red arrow” to scroll down to the next page, then clicks the “+” to view the children of any node in the new page, and then uses the red arrow to scroll up again, a message box appears specifying that “A beginning of file reached error” has occurred (SBL-DAT-00364). The error occurs regardless of whether the node had any children or not.
In addition when the user clicks the “+” to view the children of a node on the second page, if the node has no children the node becomes the first record in the right hand list applet followed by the records from the first page. For example: The first page of tree nodes has records A,B and C. These are displayed in the tree and list applets, the user clicks the red arrow to scroll down to the next page to see records D, E and F. These appear in the tree applet and the list applet. The user clicks on E to see its children but E has no children. At this time the list applet is refreshed and displays the records E, A, B.

Solution

Message 1

For the benefit of other readers:

Description:

In a tree applet if the user uses the “red arrow” to scroll down to the next page, then clicks the “+” to view the children of any node in the new page, and then uses the red arrow to scroll up again, a message box appears specifying that “A beginning of file reached error” has occurred (SBL-DAT-00364). The error occurs regardless of whether the node had any children or not.

Resolution:

Technical Support has reproduced this behavior and the following Change Request has been logged to have this behavior corrected: # 12-I27QW2 “Account explorer view is not working”.

Keywords: SBL-DAT-00364, a beginning of file reached, error message, Account explorer view, red arrow, scroll up

Applies to:

Siebel CRM - Version: 7.8.2.3 SIA [19221] and later [Release: V7 and later ]
Siebel CRM - Version: 7.8.2.3 SIA [19221] and later [Release: V7 and later]
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.8.2.3 [19221] FRA Engy/Oil
Database: Oracle 9.2.0.7
Application Server OS: Sun Solaris 10
Database Server OS: Sun Solaris 10

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

Symptoms

SBL-CSR-00364

Dear support,
When logging to siebel with a user that has a position different from sadmin, we experience a strange behavior in the contacts screen. This issue seems to be similar to SR 38-1168563861

    - Log on to a Siebel 7.8 Vanilla (I tried it on 7.8.2.3 SIA [19221] FRA(*)) with user ccheng
    - go to "Contact List View"
    - put the cursor on last line (with shortcut ALT+L)
    - go to "Visible Contact List View" using the "My contacts" combo box filter
    - despite we're on the first record, the scroll bar cursor isn't on top of the vertical scroll bar
    - when trying to get the scroll bar cursor on top of the bar, by clicking the single up arrow, we get the following message :

"A beginning of file reached error has occurred. Please continue or contact your systems administrator if the problem persists (SBL-DAT-00364)"

With user sadmin, this problem doesn't appear.
Could you confirm us that this is a standard behavior ? Is there a workaround ?

Thank you for your help.
Regards,

Cause

This behavior is caused by Bug 12-1J5Z6CN

Solution

For the benefit of other users:

The behavior could be reproduced in standard ENU applications with sample database with following steps:
- log into any high interactive 7.8.x application (HOR or SIA) with sample DB as user CCHENG
- navigate Site Map > Contacts > Contacts List
(you should be in 'My Contacts', if not navigate to it)
- in view pull down switch from 'My Contacts' to 'All Contacts'
- make sure that Last Name field is sorted
- navigate to last record with [Alt-L]
- in view pull down switch back to 'My Contacts'
- although first record in the list is selected, the vertical scroll bar is not in top position
- click the up-arrow button on vertical scroll bar
=> popup: "A beginning of file reached error has occurred. Please continue or contact your systems administrator if the problem persists (SBL-DAT-00364)"
- with user SADMIN no error happens

Change Request CR 12-1J5Z6CN has been raised to address this defect.
The workaround is not to click 'previous record' in this situation.

Oracle/Siebel Technical Support

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3 [16157] FIN Fin Svcs
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: Microsoft Windows 2000 Server SP 4

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

Symptoms

We are experiencing the following error.

On a list applet we query for a medium sized data set. Using the horizontal scroll bar, drag the cursor down to the last record so that the top right of the record says "last record"
Using the Double Up arrow button scroll to the top of the list. (the record indicator should display ### from last record)
When you get to the top and the records stop scrolling, click the single up arrow button once.

the result is the attached error message.
A beginning of file reached error has occurred.
Please continue or contact your systems administrator if the problem persists (SBL-DAT-00364)

Solution

Message 1

For the benefit of other users:

Using the horizontal scroll bar, drag the cursor down to the last record so that the top right of the record says "last record". Using the Double Up (GotoNextSet Control) arrow button scroll to the top of the list (record indicator should display ### from last record). When top reached, the records stop scrolling, click the single up arrow button once than the error “A beginning of file reached error has occurred” appears.

This behavior reproduced and logged change request# 12-JETMNB to address this behavior. Please note that change requests will be prioritized and fixed in feature release.

Thank you

Siebel Technical Support

SBL-DAT-00362: Data value for field '%1' is larger than the limit %2 defined in the database.

Applies to:

Siebel Tools - Version: 7.7.1 [18306] and later [Release: V7 and later ]
Information in this document applies to any platform.
Error Message Area:Data Manager - DAT
Version:Siebel 7.7

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-00362: Data value for field '%1' is larger than the limit %2 defined in the database. Please type in less information to ensure that your data is committed to the database.

Scope

This document is informational and intended for any user.

SBL-DAT-00362: Data value for field '%1' is larger than the limit %2 defined in the database. Please type in less information to ensure that your data is committed to the database.

Explanation

This error message can be encountered when trying to write a record to the Siebel database, if the length of the data that is being saved exceeds the length of the physical base table column. Below are some common causes for this error:

1. The user types more characters than is allowed by the field length and tries to save the record.

2. A record attribute has more characters than the physical column length. To diagnose this behavior further, do the following:

- Check the Business Component (BC) field Text Length property and compare its value with the corresponding base table column length. The field length should be less than or equal to the base table column length. NOTE: That the Text Length on the field is effective only if the "Text Length Override" user property is defined.

- Check the pre-default and post-default properties to ensure they do not exceed the limit. In particular, if they are like Parent: 'BC.field', check the length of the field on the parent BC.

- Determine if any script populates the field.

- If the field is populated using a pick list or pick applet, check the fields that are referred on the pick maps. In particular, check the length of these fields on the business component used by the pick applet and the pick list. Its length should not exceed the length of the field in the business component where the pick list is used.

3. The error occurs when the field uses a static pick list based off a multilingual list of values (MLOV) and the column length is greater than 30.

Corrective Action

The corrective actions for this error will depend on the underlying causes. Below are some suggestions to correct the known causes listed above:

1. Restrict the users to the number defined in the Text Length of the field. For text fields, restrict the field length through the "Text Length Override" user property. If the "Text Length Override" user property is defined, then make sure that the text length of the field is less than or equal to the database column length. For numeric fields, use the "Validation" property. Refer to this document.

How Can Users Restrict the Entry of Characters in a List Column or Control? <Doc: 476698.1>

for more information on how to control the maximum numbers of characters in a field.

2. If the error is caused by "A record attribute has more characters than the physical column length", try the following:

- Ensure the Business Component (BC) field Text Length property is less than or equal to the base table column length.

- Ensure the pre-default and post-default properties do not exceed the field limit. In particular, if they are set to Parent: 'BC.field', check the length of the field on the parent BC.

- Modify any scripts that populate the field as needed to ensure the field length is not exceeded.

- If the field is populated using a pick list or pick applet, ensure that the length of these fields on the business component does not exceed the length of the field in the business component where the pick list is used.

3. Verify the length of the business components field's base column with the MLOV pick list and make sure it is set to a maximum of 30. For more information, refer to the following Siebel Bookshelf references:

- Siebel Bookshelf version 7.5.3 > Siebel Tools Reference > Pick Applets and Static Picklists > Multilingual Lists of Values > About the Language Independent Code.

- Siebel Bookshelf version 7.7 > Configuring Siebel eBusiness Applications > Creating and Administering Lists of Values > About the Language Independent Code.

In both of these bookshelf references is the following caution:

CAUTION: The length of the language-independent code (the value stored in the database) must be equal to the longest display value for the MLOV. If it is not, the display value will be truncated. If the standard column does not meet your requirements and you are using a custom extension column, the column must be VARCHAR and have a maximum length (width) of 30.

References

NOTE:476698.1 - How Can Users Restrict the Entry of Characters in a List Column or Control?

Applies to:

Product Release: V7 (Enterprise)
Version: 7.7.2.7 [18376]
Database: Oracle 9.2.0.6
Application Server OS: Sun Solaris 5.8
Database Server OS: Sun Solaris 5.8

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

Symptoms

SBL-DAT-00362

Hi,

This is regarding the creation of an SR Under Client (after upgrade from 7.0.5 to 7.7.). I'm trying to create an SR. In the configuration on the Service Request BC; the field “Orgn Info - Name Line 1” has the 'Type' property set to "DTYPE_TEXT" and 'Text length' property set to 50. A "Predefault value" is set to "Parent: 'Service Request.Account’". This is a field joined to the column 'OI_NAME_L1' based on the table 'S_SRV_REQ3_FNX'.

The column 'OI_NAME_L1' defined in Tools with properties 'Physical Type' set to "varchar" and 'Text Length' set to 50. The datatype for this column defined in the physical schema is VARCHAR2(50).

In the Account BC:Field “Name”(Account Name) has the 'Type' property set to "DTYPE_TEXT" and 'Text Length' set to 100. I'm hit with the error when the Account name of the Account is more than 50 chars. The field called “Orgn Info - Name Line 1” is a Vanilla field on the Service Request BCs. The field is mapped to a column that can store 50 characters. But the field is defined with the Predefault value of Account Name which has the field length 100.

Field 'Orgn Info - Name Line 1' is not getting used in the Business Application. This field has used with only with Vanilla applet "FIN Service Request Organization Info Update Form Applet" under view "FIN Service Request Organization Detail Change View" and only available to Administrator user.

So,Workaround used for this field is, this field is no longer used in the Business, removed the predefault value from the Field which was storing the value bigger than the Column length capacity. I’am little bit confuse with this vanilla settings. Too smaller length field storing bigger value. I have seen same problem has been raised in SR for the other case. Service Request #: 38-1815646211 Which is explained with same problem with (Change request 12-U3HISR).

Steps to Reproduce:
1) Clients>SR,
2) Select a client with more than 50 charachter in name.
3) then click on the SR
4)...

Solution

Message 1

For the benefit of other readers:

The behavior described has been reproduced using standard Siebel Financial Services version 7.7.2.8 against the sample database. Here are the steps

1. Go to Accounts > Service Requests
2. Create an account record and enter more than 50 characters in the Name field
3. Create a child Service Request
4. Drill down on the child Service Request
> the view accessed is 'Service Request Detail View'
5. Create a new Service Request record and save it:
> You will get this error:
- - -
Data value for field 'Orgn Info - Name Line 1' is larger than the limit 50 defined in the database.

Please type in less information to ensure that your data is committed to the database.(SBL-DAT-00362)
- - -

NOTE: The behavior is the same using versions 7.8.2.6 SIA and 8.0 SIA.

Using Tools we can see the BC 'Service Request' has the following fields:
- - -
Name: Orgn Info - Name Line 1
Join: S_SRV_REQ3_FNX
Column: OI_NAME_L1
Predefault Value: Parent: 'Service Request.Account'

Name: Account
Join: S_ORG_EXT
Column: NAME
- - -

The issue is that in table S_ORG_EXT the column NAME has 100 as Length but in table S_SRV_REQ3_FNX the column OI_NAME_L1 has 50 only.

Change Request 12-1KJ2JK5 has been logged to address this product defect.

The workaround is to remove the pre-default value set on field 'Orgn Info - Name Line 1'.

[...]

Message 2

[...]

NOTE: The SupportWeb posting 38-1815646211 discusses a similar issue addressed by Change Request 12-U3HISR. This issue is fixed in Siebel application version 8.0 SIA.

Applies to:

Siebel Life Sciences CRM - Version: 8.0 [20405] - Release: V8
Information in this document applies to any platform.

Symptoms

The following error occurs when creating a Forecast using a Forecast Series with "Account" Aggregation:

"SBL-DAT-00362: Data value for field 'Aggregation Field Level 1' is larger than the limit 50 defined in the database."

Customer do have some Account records exceeding the size 50.

Cause

I was able to reproduce this issue internally, using the Sample DB:

1) Forecast Series > Aggregation view > "Account"

2) Created an Account with more that 50 characters

3) Add a new Oppty and associated to the new Oppty

4) Created a Forecast

Error : SBL-DAT-00362: Data value for field 'Aggregation Field Level 1' is larger than the limit 50 defined in the database".

This is caused by the OOTB objects configuration:

BC: Forecast 2000 -- Forecast Item Detail Summary
SVF: Aggregation Field Level 1
S_FCST_ITEM_DTL.AGGR_DIM_NAME_1
DTYPE_TEXT 50

S_FCST_ITEM_DTL.AGGR_DIM_NAME_1
Varchar 50

Solution

The following workaround can be used to overcome this issue:

1) Extended table S_FCST_ITEM_DTL > Column: X_ABC_AGGR_DIM_NAME_1
Varchar 100

2) Changed the following BCs:

Forecast 2000 -- Forecast Item Detail Summary
Forecast 2000 -- Forecast Item Detail Summary Flat
Forecast 2000 -- Forecast Item Detail Flat
Forecast 2000 -- Forecast Item Detail

SVF: Aggregation Field Level 1
Column: X_ABC_AGGR_DIM_NAME_1
DTYPE_TEXT 100

3) Created a new Account:

silv12345678901234567890123456789012345678901230000000000

4) Created a new Oppty and associated above Account

5) Created Forecast Series > Aggregation: Account

6) Create a Forecast using new Forecast Series to pick new Oppty

6) Forecast is successfully created.

The same configuration changes should be performed for all other 6 Aggregation fields:

Aggregation Field Level 2 to Aggregation Field Level 6

and corresponding columns:

AGGR_DIM_NAME_2 to AGGR_DIM_NAME_6

Please, also note that above changes and tests have been performed in a vanilla application with no custom changes.

Therefore, please make sure that you make the necessary tests in the overall application to ensure these changes will correctly work with your custom application.

Thank you.

Best regards,
Oracle Technical Suppport

SBL-DAT-00360: Business component '%1' is not defined. Please ask your systems administrator to check your application configuration.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.7.1 [18306] FIN
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: Sun Solaris 2.8

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

Symptoms

SBL-DAT-00360

We are facing an error when creating a mobile client on thin client.

Please find the below error meessage:

"Business component 'Node Id' is not defined.

Please ask your systems administrator to check your application configuration.(SBL-DAT-00360)".

But there is no issue while creating a mobile client on thick client.

Please advise on a solution/workaround for the above problems.

Solution

Message 1

For the benefit of others:

The customer reported the following error occurred when attempting to commit a new mobile client record in the Siebel Remote Administration > Mobile Client views:

********************
Business component '%1' is not defined.

Please ask your systems administrator to check your application configuration.
********************

...where the %1 may reference random ASCII characters or different business components.

This behavior was first reported in Siebel version 7.5.3.x and may be related to Solaris based SWE environments from which web clients are rendered. It has been reported as CR#12-OXIIAN and corrected in Siebel eBusiness Applications 7.8.x and later.

As a workaround, create the mobile clients from a dedicated client on a Windows OS browser or a web client connected to a non-Solaris web server.

For further information, please log a new service request.

Thank you,

Siebel Technical Support

Message 2

Keywords: mobile, web, client, thin, thick, business component, defined, error, SBL-DAT-00360, 00360, Solaris, SWE, web server

Applies to:

Siebel Tools - Version: 7.8.2 [19213] to 8.1.1 [21112] - Release: V7 to V8
Information in this document applies to any platform.
Product Release: V7 (Professional)
Version: 7.8.2.3 [19221]
Database: Microsoft SQL Server 2005
Application Server OS: Microsoft Windows 2003 Server SP2
Database Server OS: Microsoft Windows 2003 Server SP2

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

Symptoms

Hi,

I am getting an error in accessing business component in Siebel Tools and in custom scripting that the Business Component does not exist.
Business Objects\Action (eService)\Action (Call Me Web Collab)

I logged into Tools as SADMIN to verify this and I received the error:
"You do not have the privileges required to view detailed information for this record, or it has recently been deleted.(SBL-DAT-00309)"
I clicked OK and then received,
"The drilled down item is invalid. It does not exist in the database".

I am also getting this error for the following BC's. Please see below BC and BO names

\Business Objects\Admin ISS Product Definition\Internal Product Image
\Business Objects\Action (eService)\FS PickList Parts & Tools
\Business Objects\Admin ISS Product Definition\Product Bundle - Quote
\Business Objects\Action (eService)\Action (Call Me Web Collab)

SBL-DAT-00171, SBL-DAT-00222, SBL-DAT-00309, SBL-DAT-00360
Please advise

thanks.

Cause

For the benefit of others:

The issue is that the Siebel Repository has references to obsolete objects.

Solution

Siebel Tools > Types Tab > Select Business Object object type > Query for the following BO's and Business Object Component objects:

\Business Objects\Admin ISS Product Definition\Internal Product Image
\Business Objects\Admin ISS Product Definition\Product Bundle - Quote
\Business Objects\Action (eService)\FS PickList Parts & Tools
\Business Objects\Action (eService)\Action (Call Me Web Collab)

If you drilldown on any one of the BCs related to Business Object Components, it will get the following error message:

You do not have the privileges required to view detailed information for this record, or it has recently been deleted.(SBL-DAT-00309)

If querying for the BC's mentioned above, they will not be retrieve in Business Components object type.

Resolution:

Change Request #12-1KMUK73 has been logged as a Documentation Defect.

Change Request #12-1KMUKBU has been logged as a Product Defect.

In CR #12-1KMUKBU, it was explained that “Internal Product Image”, “Product Bundle - Quote”, “FS PickList Parts & Tools” and “Action (Call Me Web Collab)” Business Components are obsolete.

Workaround:

In order to avoid SBL-DAT-00309 error message on Siebel Tools, customers need to inactivate the related Business Object Components manually by Tools.

Some of the references to the obsolete business components are still in the Siebel 8.1 SIA and HOR repository. The workaround is the same. Inactivate the Business Object Component objects for the obsolete Business Components in Tools.

Siebel Technical Support

Applies to:

Product Release: V7 (Enterprise)
Version: 7.8.2.5 [19227] DEU Fin Svcs
Database: Oracle 10.1.0.2
Application Server OS: Sun Solaris 10
Database Server OS: Sun Solaris 10

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

Symptoms

Hi Support

we had problem when we try to import couple of workflows from 7.5 to 7.8 after upgrade.
Here are the error messages that we got

Method 'WriteRecord' of business component 'Repository WF Branch Criteria Value' (integration component 'Repository WF Branch Criteria Value') for record with search specification '[Sequence] = "1"' returned the following error:"Business component 'DAB3 Versandauftrag' is not defined.

Please ask your systems administrator to check your application configuration.(SBL-DAT-00360)"(SBL-EAI-04451)

We attached the workflows that we had problem when we try to import,

could you please advice us what can be the problem?

Solution

Message 1

For the benefit of the other readers:

Resolution?

The behavior happens against a branch that has a criteria, I mean, some of the step connectors that have a runtime event against that.

Please apply Alert 1058: Siebel Tools Crashes or Hangs in Compose Condition Criteria Dialog Box When Using New Business Component in Version 7.7.x

http://supportweb.siebel.com/support/private/content/ALERTS/ENU/V7/alert1058.html

Keywords: WriteRecord, Repository WF Branch Criteria Value, Sequence Workflow, Import

Applies to:

Product Release: V7 (Professional)
Version: 7.7.2.4 [18365]
Database: IBM DB2 8.2
Application Server OS: Microsoft Windows 2000 Advanced Server SP 3
Database Server OS: Sun Solaris 9

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

Symptoms

Hi,
We have a very large workflow and this is developed in 7.5. We upgraded all our environments to 7.7. Now we have a requirement to modify that workflow, we need add additional step. When I am trying to add that step, the Tools crashes. I will upload my local database and srf to ftp site tonight. Please go thru the following steps:
1. Open 'ISR Notifications' workflow which has status 'In Progress'
2. I need to add a new wait step just like any other steps.
3. The condition branch should include two conditions:
a. Internal Service Request.Owner IS NULL
b. Internal Service Request.Owner Group: One must match (Ignore case) to 'HP SIF'

When I am trying to add the second condition, and I click on 'New' button to add the value 'HP SIF', Tools crashes. Please let me know why. If its not fixable, is there any other alternative?
Thanks for your help.

Solution

Message 1

For the benefit of other users:

Customer were seeing Siebel Tools was crashing whenever they were trying to modify a workflow based on the Internal Service Request business component.

The tools was crashing and the following error was seen:

ObjMgrSRFLog Warning 2 0 2005-12-14 16:22:55 (objdef.cpp (12901)) SBL-DAT-00144: Could not find 'Business Component' named 'Internal Service Request'. This object is inactive or nonexistent.
ObjMgrSRFLog Warning 2 0 2005-12-14 16:22:55 (objdef.cpp (2694)) SBL-DAT-00360: Business component 'Internal Service Request' is not defined.

Please ask your systems administrator to check your application configuration.

Internal Service Request is a copy of Service Request.

It was found that the Tools was pointing to incorrect SRF that was not aware of this new business component. Once the correct SRF was pointed everything worked fine and NO crash occurred.

Thank you,

SBL-DAT-00359: The value '%1' cannot be converted to a date time value.

Applies to:

Siebel Tools - Version: 7.7.1 [18306] and later [Release: V7 and later ]
Information in this document applies to any platform.
Error Message Area:Data Manager - DAT
Version:Siebel 7.7

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-00359: The value '%1' cannot be converted to a date time value.

Scope

This document is informational and intended for any user.

SBL-DAT-00359: The value '%1' cannot be converted to a date time value.

Explanation

Below are some reported causes for this error:

1) When calling the SetFormattedFieldValue method this error might be displayed in the Siebel Dedicated Web client. The difference between the Siebel Dedicated Web clients and Siebel Web clients is discussed in the Siebel Bookshelf version 7.7 > Applications Administration Guide > Initial Setup > Setting Up Locales - where it states, "Whereas the Siebel Web Clients use the locale settings specified in the Locale Administration view, the Siebel Mobile Web Client and the Siebel Dedicated Web Client use the locale settings defined in the client operating system's regional settings."

2) An error is displayed when a business component field specifies a Pre Default Value with a timestamp that is not encapsulated in double quotes.

3) When querying on date fields in the Siebel UI using the same date format specified by the application locale, but the date separator is incorrect, then this causes an error. For more information on the Date Separator, please refer to Siebel Bookshelf version 7.7 > Applications Administration Guide > Initial Setup > Setting Up Locales.

4) When using the Find drop-down list in pick applets, where a field is selected based on date and time format, and then an error is displayed. For example, Account Entry Applet - Price List pick field - and then searching on Start Date. Sometimes error SBL-DAT-00403 is displayed advising the user to encapsulate the search criteria in quotations; however the above error message still appears.

5) Querying on Find fields in the Siebel Search Center that are based on dates can cause errors if the query string does not match the application default date format.

6) An error might be generated when importing an XML formatted message into the Siebel application via Integration Objects, especially when the IO Field is set to DTYPE_TEXT and the value in the XML message is encapsulated in double quotes.

7) The EAI Siebel Adapter does not perform date or time validation rather this is done at the user interface layer and therefore if the format is incorrect or contains invalid characters no error appears. In some cases, for example where the year is specified as 2 digits as opposed to 4 digits, then this type of validation is handled by the Siebel object manager as described in Siebel Bookshelf version 7.7 > Siebel eScript Language Reference > Siebel eScript Language Overview > Siebel eScript Programming Guidelines (Use four-digit years in dates).

8) A workflow process might throw an error if it specifies the Match Date property on Update operations, for example,

Field Name: Suspended Date
Type: Expression
Value: [&Match Date] + 30

9) An error might occur when creating a Workflow Policy Condition that involves a comparison between two workflow policy columns based on a date data type.

10) A campaign load might fail if the format of date fields is incorrect.

Corrective Action

How to work with date and numeric fields in Siebel Visual Basic (SVB) (Doc ID 475872.1)

For more information on the script syntax, please refer to Siebel Bookshelf version 7.7 > Siebel Object Interfaces Reference > Interfaces Reference > Business Component Methods > SetFormattedFieldValue Method.

Change Request 12-I54UKV was logged to address this product defect, which has been fixed in Siebel 7.7.

2) The Pre Default Value property should be specified using the format "hh:mm:ss" and encapsulated in double quotes. The field itself should be based on the DTYPE_TIME Date Type. Please refer to this bulletin <Doc: 477773.1> for more information on this matter.

Predefault and Postdefault Values for Fields of Type Date, Date Time, and UTC Date Time (Doc ID 477773.1)

3) Ensure that the Date Separator specified under Application Administration > Locale - reflects the same separator specified in the Short Date Format.

4) As a workaround when performing a query in a pick applet on a date field, use the Query button as opposed to using the Find drop-down list. Change Request 12-PDZ7T2 was logged to address this product defect.

5) Scripting could be used as an alternative in order to validate the search strings entered in the Find fields. Change Request 12-L5URHJ was logged to address this product defect.

6) Either, a) specify the IO Field as DTYPE_DATETIME (no double quotes needed in the XML) using format “YYYY/MM/DD HH:MM:SS” or specify “HH:MM:SS” (without quotes) as the XML element value. In addition, the Length property of the integration component field should be removed, because when an integration object and integration component is generated, the Length property of the integration component field with DTYPE_DATETIME as Type is set to null by default or b) change the Data Type of the integration component field to DTYPE_TEXT and specify the value without quotes. Ensure that the Length property is set correctly, for example from 7 to 8 on integration component field and the BC field.

7) Ensure that date values are passed using the correct format to the EAI Siebel Adaptor. Change Request 12-MDI6LC has been logged to address a product defect related to how the same data validation should be present in the EAI Siebel Adaptor as in the Siebel UI.

8) Ensure that the process property called Match Date has the Data Type set to Date as opposed to String. For more information, please refer to Siebel Bookshelf version 7.7 > Siebel Business Process Designer Administration Guide > For Developers: Workflow Process Steps > About Process Properties > Defining Process Properties.

9) Please refer to this document <Doc: 475967.1> where it states that the comparison of two columns in a workflow policy condition is currently not possible in Siebel 7.

Can a Workflow Manager Policy Have a Condition That Compares Two Columns to Each Other? (Doc ID 475967.1)

Change Request Bug: 12-K9BP8N was logged to address this product enhancement request. Instead use a workflow process to do this comparison.

10) Under Marketing Administration> External Data Mapping > Tables - the field expression should be amended to return a string using the format "mm/dd/yyyy hh:mm:ss".

Applies to:

Siebel Tools - Version: 8.0.0.1 SIA [20408] - Release: V8
Information in this document applies to any platform.

Symptoms

Error SBL-DAT-00359 was observed and the behavior was intermittent and is not observed once the server was restarted.

Behavior was observed only on customer test environment and works fine on development environment with same srf.

Cause

This line of script was causing the error with Clib object.

var TimeBuf;
var FormattedDateMs = FormattedDate.getTime();
Clib.strftime(TimeBuf, “%c”, FormattedDateMs);

Solution

Workaround used was creating a custom function that used .getMinutes, .getHours..etc and concatenated these items together to form the date string as this.SetFieldValue("UPS Customer Time", sStringVariable");

<<CR#12-1PE9QS4>>was logged as product defect that there is problem with Clib and Time buffer parameter.

Applies to:

Siebel Tools - Version: 7.8.2 [19213] and later [Release: V7 and later ]
Information in this document applies to any platform.

Symptoms

For Service Request customer has modified applets to display the Day of the Week for field types DTYPE_UTC_DATETIME.

Customer set the Display Format for Applet Control as ‘DDDD Date Time’.

However, when customer tries to query on this field they got error "The value 'Tuesday 7/29/2008 5:14:08 PM' cannot be converted to a date time value. (SBL-DAT-00359)".

Cause

It seems that “Display Format” is not available for DTYPE_UTCDATETIME and Enhancement Request Bug 12-1L6MQ19 has been logged to have Display Format for DTYPE_UTCDATETIME.

However, the same behavior is happening for a field of type DTYPE_DATETIME for which the display Format is available.

Product Defect Bug 12-1PILZ6F - Error SBL-DAT-00359 is generated when querying on control with Display Format as DDDD Date Time has been created.

Solution

The issue has been replicated internally and Bug 12-1PILZ6F - Error SBL-DAT-00359 is generated when querying on control with Display Format as DDDD Date Time has been created.

The only way to avoid the error would be to remove the Display Format set for this field.
In order to have the weekday of the Service Creation you can do the following:
1. Create a clone of the control and set the Display Format as DDDD for this control, so that you can see the Weekday of Service Request creation.
2. Use the other field for query.

Oracle Customer Support

Note: Bug 12-1PILZ6F - Error SBL-DAT-00359 is generated when querying on control with Display Format as DDDD Date Time has been created has been currently declined as Risks Exceed Benefits.

References

BUG:12-1PILZ6F - ERROR SBL-DAT-00359 IS GENERATED WHEN QUERYING ON CONTROL WITH DISPLAY FORMAT AS DDDD DATE TIME

Applies to:

Error Message Area:Data Manager - DAT
Version:Siebel 7.5.3

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-00359: The value '%1' cannot be converted to a date time value.

Scope

This document is informational and intended for any user.

SBL-DAT-00359: The value '%1' cannot be converted to a date time value.

Explanation

Corrective Action

Below are the corrective actions to try for the reported causes:

1) It is recommended to convert the date into the respective format specified by the regional settings, for example "dd.mm.yyyy", and then call the SetFieldValue with the converted value as described in Technical Note 230. For more information on the script syntax, please refer to Siebel Bookshelf version 7.7 > Siebel Object Interfaces Reference > Interfaces Reference > Business Component Methods > SetFormattedFieldValue Method.

Change Request 12-I54UKV was logged to address this product defect, which has been fixed in Siebel 7.7.

2) The Pre Default Value property should be specified using the format "hh:mm:ss" and encapsulated in double quotes. The field itself should be based on the DTYPE_TIME Date Type. Please refer to Technical Note 539 for more information on this matter.

3) Ensure that the Date Separator specified under Application Administration > Locale - reflects the same separator specified in the Short Date Format.

4) As a workaround when performing a query in a pick applet on a date field, use the Query button as opposed to using the Find drop-down list. Change Request 12-PDZ7T2 was logged to address this product defect.

5) Scripting could be used as an alternative in order to validate the search strings entered in the Find fields. Change Request 12-L5URHJ was logged to address this product defect.

6) Either, a) specify the IO Field as DTYPE_DATETIME (no double quotes needed in the XML) using format “YYYY/MM/DD HH:MM:SS” or specify “HH:MM:SS” (without quotes) as the XML element value. In addition, the Length property of the integration component field should be removed, because when an integration object and integration component is generated, the Length property of the integration component field with DTYPE_DATETIME as Type is set to null by default or b) change the Data Type of the integration component field to DTYPE_TEXT and specify the value without quotes. Ensure that the Length property is set correctly, for example from 7 to 8 on integration component field and the BC field.

7) Ensure that date values are passed using the correct format to the EAI Siebel Adaptor. Change Request 12-MDI6LC has been logged to address a product defect related to how the same data validation should be present in the EAI Siebel Adaptor as in the Siebel UI.

8) Ensure that the process property called Match Date has the Data Type set to Date as opposed to String. For more information, please refer to Siebel Bookshelf version 7.7 > Siebel Business Process Designer Administration Guide > For Developers: Workflow Process Steps > About Process Properties > Defining Process Properties.

9) Please refer to FAQ 1335 where it states that the comparison of two columns in a workflow policy condition is currently not possible in Siebel 7. Change Request 12-K9BP8N was logged to address this product enhancement request. Instead use a workflow process to do this comparison.

10) Under Marketing Administration> External Data Mapping > Tables - the field expression should be amended to return a string using the format "mm/dd/yyyy hh:mm:ss".

SBL-DAT-00367: 'CascadeDelete' property set for many-to-many link definition '%1'.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3 [16157] Fin Svcs
Database: IBM DB2/UDB 7.2
Application Server OS: Microsoft Windows 2000 Advanced Server SP 3
Database Server OS: IBM AIX 5L 5.1

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

Symptoms

SBL-DAT-00367, SBL-DAT-00373

We are facing a performance issue when we delete records from 'UHCKA Influencer' business component. The delete takes around 45 seconds to 1 minute. We did take a spool and found out that the longest running queries are a set of insert statments into SIEBELP.S_DOCK_TXN_SET. Is there any way in which we can improve the performance of Delete on this business component.

Note: UHCKA Influencer is a copy of contact business component.

We are enclosing the sif of UHCKA Influencer and the spool file for you reference

Solution

Message 1

After inactivating some of the unwanted links and turning off the docking transaction, performance improved. However, it was noticed then that only the first time a record was deleted on UHCKA Influencer, performance was slow, susequently the delete is fast.

This is a known issue in Siebel version 7.5.3, when you commit the first delete of a record in the Siebel application using the Siebel Web Client, you may experience a delay in the application before the control is returned to you.

Change Requests 12-HJQX15 and 12-IJU4NB has been raised to address this product defect.

The reason for this behavior is that the Siebel Object Manager needs to read all the link definitions and business component definitions related to the links for the whole repository to find the links that are related to the active business component. This is performed by the Siebel Object Manager the first time a commit is issued for a delete statement. Due to the number of links in the Siebel repository that need to be read, this may take a long time.

The above behavior happens only for the very first delete issued through the Object Manager. Subsequent deletes should complete more quickly for the same business component or different business Components.

Maintenance Release Request 12-IJU4QY has been released for Change Requests 12-HJQX15 and 12-IJU4NB, which has been fixed in Siebel Fix Pack version 7.5.3.6. The latest Fix Pack should be applied to Siebel Maintenance Release 7.5.3.

SBL-DAT-00350: SetUserInfo failed for user %1. This may be due to a problem with the external authentication system.....

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3.5 [16183]
Database: Oracle 9.2.0.2
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: Sun Solaris 5.8

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

Symptoms

SBL-DAT-00350

Dear Siebel,

For our UAT environment, we have setup LDAP as a Security adapter for one of our Object managers.
Directory server was already installed earlier and was used for authentication for the production system.
I am facing a issue where I am not able to add a new contact(or Employee or User) from Siebel.
When I try to add it I get the message saying that
SETUSERINFO failed for user <User Name>. This may be due to a problem....................
Object Class Violation (SBL-DAT-00350). Please see the attached screen shot for the reference.

If I try to add an existing user (on LDAP), I get a proper message saying that the userid already exisitng.

I am attaching the siebns.dat, scomm.cfg file along with this.

I understand that the user id SADMIN which which I am logging into the Siebel application should have access to add the user but not sure where I can set it.
Before this Object class violation, I was getting the Access related error.

Thanks

Solution

Message 1

For the benefits of other users:

Customers are not able to add a new contact (or Employee or User) from Siebel Application with LDAP Security adapter setup. When trying to add a contact, message saying that
“SETUSERINFO failed for user <User Name>. This may be due to a problem..... Object Class Violation (SBL-DAT-00350). Please see the attached screen shot for the reference.” returned.

Solution:

A check on the following item done:
- Customer on supported LDAP and Siebel Application platform.
- Verified “SecExternalUserAdministration”, “SecThickClientExtAuthent”, and “Security Adapter CRC” in Site Map > Application Administration > System Preferences
- Verified Security Adapter configuration for Object Manager
- Verified LDAP directory data (DN) setup (.ldif)
- Verified access permission for Application User
- Verified all the parameters set in LDAP section in OM configuration file

The LDAP access log has the following error when adding a user:

[27/Sep/2004:13:49:22 +1000] conn=784 op=3 ADD dn="=,ou=def,o=abc.com"
[27/Sep/2004:13:49:22 +1000] conn=784 op=3 RESULT err=65 tag=105 nentries=0 etime=0
[27/Sep/2004:13:49:22 +1000] conn=784 op=4 UNBIND
[27/Sep/2004:13:49:22 +1000] conn=784 op=4 fd=39 closed - U1

And the error log has the following:
[27/Sep/2004:13:49:22 +1000] - Entry "=,ou=def,o=abc.com" -- attribute "uid" not allowed

Message 2

LDAP error code 65 means “Object class violation” and the correspondence error log shown attribute “uid” not allowed; this seems to be an issue with the LDAP server. The uid attribute was not being propagated. Issue resolved after reinstall the LDAP server.

Thank you,
Siebel Technical Support

Keywords: SBL-DAT-00350, SETUSERINFO failed

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3 [16157]
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2000 Advanced Server SP 3
Database Server OS: Microsoft Windows 2000 Server SP 3

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

Symptoms

SBL-DAT-00350

When attempting to enable Password Syntax or minimum length checking on our ADSI integration, the New User Registration process appears to be failing to complete successfully when the password is rejected by ADSI. However, it is not returning any error directly. This is somewhat similar to SR 38-980959751, but without any error message.

Specifically, follow along the USER REGISTRATION PROCESS workflow. If I intentionally create a user with an invalid password (say, too few characters), I still get the "Thank you for registering. Please click Finish to continue." view. Clicking FINISH appears to execute the "Insert New User" step, as the user is created in the User Administration screens. However, it fails at "Set New Login Info" with a generic: "We detected an Error which may have occurred for one or more of the following reasons:" (with no reasons listed). An entry is created in the ADSI directory, but with no password; however, no Challenge/Response information is created for the user (which is the other function of "Set Login Info"), so it appears to be failing midway through.

Is there any way to see log information (the eService ObjMgr log file and SWE log files show nothing) which may help here? There does not appear to be an error branch off of Set Login Info which would capture ADSI password rejection; how does Siebel handle this?

Solution

Message 1

For the benefit of other users:

Customer had implemented ADSI authentication and had enabled minimum password length policy in ADSI. The reported behavior was that the New User Registration would fail when the password is rejected by ADSI. However, it was not returning any error directly. Clicking FINISH would fail with a generic error: "We detected an Error which may have occurred for one or more of the following reasons:" (with no reasons listed). An entry was created in the ADSI directory, but with no password; however, no Challenge/Response information is created for the user.

Technical Support reproduced this behavior and logged Change Request#12-K5DHTL for this behavior. A Change Request#12-FIF77M was already logged to improve the error message returned when ADSI password policy fails.

To get around the behavior Technical Support suggested to modify the Standard User Registration Workflow Process to call a custom business service to insert the challenge question/answer inspite of the failure.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.2.215 [16069] HH
Database: Oracle 9.2.0.2
Application Server OS: Microsoft Windows 2000 Advanced Server SP 2
Database Server OS: Sun Solaris 2.7

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

Symptoms

SBL-DAT-00350

We are using Siebel eChannel with ADSL authentication.

From the moment we set ADSL in our Development environment we cannot change the user's password in Partner Personal Profile or generate a new password using the Forgot Password link in the Home page. The error message is: “SetUserInfo failed for user XXXXX. This may be due to a problem with the external authentication system, or attempting to enter user name and password that contains non-ASCII characters.” The change/generate password was working before the ADSL was set in DEV.

We have studied Service Requests 38-937920551, 38-821359193, 38-805263251, 38-685367951 and so far we set the user with Change Password and Reset Password privileges, but that did not help

The password change works thru ADSL on our TST environment, the config of both TST and DEV environments are the same, so we do not know why we are not able to change passwords in DEV. The same ADSL is used for both environments and the user for TST and DEV is the same.

Solution

Message 1

For the benefit of other readers, after enabling ADSI Authentication for Siebel eChannel in a development environment, the customer encountered the following error message when attempting to change a user’s password:

“SetUserInfo failed for user XXXXX. This may be due to a problem with the external authentication system, or attempting to enter user name and password that contains non-ASCII characters.”

This behavior did not occur in the customer’s test environment, which was using the same Active Directory Server.

After further research it was discovered that the test environment was communicating with the Active Directory Server over SSL. Since the appropriate Certificate was not installed on the development server SSL communications was failing.

Once the appropriate certificate was installed on the development environment, the customer was then able to change user passwords.

Note: The ADSI Adapter Requirements section of the Security Adapter Authentication chapter in the 7.5.2 Security Guide states “To perform user management in the ADS directory through the Siebel client, it is strongly recommended that you configure ADS at the server level for SSL communications between the Active Directory client and server.”

SBL-DAT-00368: Column '%1' not defined in table '%2'.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.7.1 [18306]
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Server
Database Server OS: Microsoft Windows 2000 Server

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

Symptoms

SBL-DAT-00368

Hello,

we are unable to delete position through the UI.

using either:
- our custom srf against our oracle db
- the 7.7.1 vanilla srf against our oracle db
- the 7.7.0 vanilla srf against a 7.7.0 sample db (on a test upgrade machine we kept)

Can you please help?
Kindly find attached a log of the error we experience.

Thanks.

Solution

Message 1

For the benefit of others:

The customer was unable to delete a position through the Siebel application UI.

When trying to delete the position, they were getting the error:

“[1] An error occurred while deleting the record
Please try to delete again (SBL-DAT-00236)

[2] Column “” not defined in table ‘<?>.(SBL-DAT-00368)”

This issue could be reproduced against the standard application and the Change Request # 12-OY8PZR has been logged to address this issue.

Also as mentioned in the Security Guide for Siebel eBusiness Applications > Configuring Access Control > Planning for Access Control > Planning for Positions, we do not recommend deleting positions.

This is an excerpt from the Security Guide:

"CAUTION: Do not delete a position. This can cause unexpected and negative results. For example, if you delete a position that is primary for an account, and you do not select a new primary position for that account, Assignment Manager may not be able to assign resources to activities for that account. "

Please review the Security Guide for Siebel eBusiness Applications for additional information.

Enhancement Request #12-OZ290E has been logged to request disabling the delete button on the Position List Applet since we do not recommend deleting positions.

Keywords – delete, position, error, disable, button

Applies to:

Siebel Tools - Version: 7.8.2 [19213] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Professional)
Version: 7.8.2 [19213]
Database: Oracle 9.2.0.0
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Sun Solaris 5.6

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

Symptoms

The issue is that Accounts cannot be deleted.

The user will select Delete from the menu, Ctl-Alt-D, or clicked the Button, everything seems to work fine until the user steps off the record. Once the user steps off the record, a message pops up:

--------------------------------------------------------------------------
[1] An error has occurred while deleting this record.
Please try to Delete again (SBL-DAT-00236)
[2] Column "not defined in table '<?>' (SBL-DAT-00368)
--------------------------------------------------------------------------

Cause

"Organization Id" field in Service Agreement business component has a wrong configuration as follows;

Multi Valued : FALSE
Multi Value Link : Organization
Column : null

Since "Organization Id" field is a MVF, Multi Valued property has to be TRUE.

Solution

Set Multi Valued property of "Organization Id" field to TRUE and the end user can delete account records with no problem.

Applies to:

Siebel Tools, SPE - Version: 8.0.0.5 SIA [20420] - Release: V8

Information in this document applies to any platform.

Symptoms

After upgrade from 7.5.3.15 Siebel application to version 8.0.0.5 in a development environment, the following error message appears when trying to access some customised views and applets within the “Batch Administrion” screen
SBL-DAT-00368: Column 'LANG_ID' not defined in table 'CX_INTGR_REF'.

Cause

Oracle consultant, working on-site found the issue arises because the 'Translation Table Name' property for some of the columns have been set to 'CX_INTGR_REF'.

The property is not needed as the columns are not MLOV enabled.

Solution

Proposed solution:
Remove the value from table user property 'Translation Table Name' or set it to S_LST_OF_VAL or null as BookShelf recommends.

BookShelf reference Siebel Object Types Reference > Siebel Object Types > Column, Translation Table Name property allowed values are S_LST_OF_VAL and NULL.
Setting this property to S_LST_OF_VAL will not cause any error as this table does have a LANG_ID column.

Enhancement request 12-1RRC6RV has beed raised to avoid the check of 'Translation Table Name' when LOV Type is null and LOV Bounded set to FALSE.
In general, when an enhancement request is logged, it is reviewed, prioritized, and may be fixed in a future release.

References

BUG:12-1RRC6RV - "TRANSLATION TABLE NAME" PROPERTY

Search This Blog

Applies to:

Symptoms

Cause

Solution

Applies to:

Symptoms

Cause

Solution

Applies to:

Goal

Solution

Applies to:

Symptoms

Cause

Solution

Applies to:

Symptoms

Solution

Applies to:

Symptoms

Solution

Applies to:

Symptoms

Solution

Applies to:

Symptoms

Solution

Applies to:

Symptoms

Solution

Applies to:

Symptoms

Solution

Applies to:

Symptoms

Solution

Applies to:

Symptoms

Solution

Applies to:

Symptoms

Cause

Solution

References

Applies to:

Symptoms

Solution

Applies to:

Symptoms

Solution

Applies to:

Symptoms

Cause

Solution

Applies to:

Symptoms

Solution

Applies to:

Purpose

Scope

SBL-DAT-00362: Data value for field '%1' is larger than the limit %2 defined in the database. Please type in less information to ensure that your data is committed to the database.

References

Applies to:

Symptoms

Solution

Applies to:

Symptoms

Cause

Solution

Applies to:

Symptoms

Solution

Applies to:

Symptoms

Cause

Solution

Applies to:

Symptoms

Solution