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,