SBL-DAT-00222: An error has occurred creating business component '%1' used by business object '%2'. Please ask your systems administrator to check you

Applies to:

Siebel Tools - Version: 8.1.1 [21112] and later   [Release: V8 and later ]
Information in this document applies to any platform.
while starting the upgraded application the logfile shows the following error for several times:

SBL-DAT-00222: An error has occurred creating business component 'Activity Plan Action' used by business object 'WebCallCenter Home'.

For your information:
We already reviewed documents 478516.1 & 478420.1, but we think this is another reason for this kind of error.
The position of the error within the logfile shows, that it is being generated while binding the Business Component "Action Home Page" to an applet on the Web Callcenter Homepage. This Business Component is a copy of the BC "Action".
We already checked the fields in BC "Action Home Page", but could not find any connection to BC "Activity Plan Action".
In addition to that we have no problems while working with the application, so this error seems to have no effect.

Symptoms

Comments
--------
The issue shows error starting the upgraded application for several times:

SBL-DAT-00222: An error has occurred creating business component 'Activity Plan Action' used by business object 'WebCallCenter Home'.

Cause

It was found that there is no added 'Activity Plan Action' BC under business object 'Action'.
After adding 'Activity Plan Action' BC to the 'Action' Business Object component, then the error message has gone.

Solution

'Activity Plan Action' BC is not part of 'Action' Business Object

References

BUG:12-Q32ZMJ - ACTIVITY LIST APPLET (WCC HOME) IS MAPPED TO ACTION HOME PAGE BC
NOTE:478420.1 - SBL-DAT-00222: An error has occurred creating business component '%1' used by business object '%2'. Please ask your systems administrator to check your application configuration.
NOTE:478516.1 - SBL-DAT-00222: An error has occurred creating business component '%1' used by business object '%2'. Please ask your systems administrator to check your application configuration.
NOTE:508494.1 - Home Page View Drilldowns

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-00222: An error has occurred creating business component '%1' used by business object '%2'. Please ask your systems administrator to check your application configuration.

Scope

This document is informational and intended for any user.

SBL-DAT-00222: An error has occurred creating business component '%1' used by business object '%2'. Please ask your systems administrator to check your application configuration.

Explanation

1. A business object is being referenced by a view or by script but the business component that is being accessed within the business object either is not configured as a business object component or does not have a link correctly defined on the business object component.

2. In Siebel eDealer application version 7.5.3, when creating an Opportunity in the Account screen, the following error displays: 'An error has occurred creating business component 'eAuto Opportunity Sales Step' used by business object 'Account'. Please ask your systems administrator to check your application configuration. (SBL-DAT-00222)'

3. When attempting to define a new Action record for a Workflow Policy using the Workflow Policy Explorer, the following error displays: 'An error occurred creating business component 'Workflow Action.Sequence(Sequence)' used by business object 'Workflow Object'. Please ask your systems administrator to check your application configuration. (SBL-DAT-00222)'

4. When accessing Server Administration > Component Groups or Server Administration > Servers the following error displays: 'An error has occurred creating business component 'Enterprise Component Group' used by business object 'Server Admin'. Please ask your systems administrator to check your application configuration. (SBL-DAT-00222)'

5. When a runtime event is associated with WriteRecord event of the Service Request business component, when attempting to drill down from a new service request record from the Home Page view, the following error displays: 'An error has occurred creating business component ' used by business object 'WebCallCenter Home'. Please ask your systems administrator to check your application configuration. (SBL-DAT-00222)"

6. After creating a Validation Rule Set on the Contact business component which is invoked by PreWriteRecord runtime of Contact business component, the following error displays: "An error has occurred creating business component 'Contact' used by business object 'Activity Template'. Please ask your systems administrator to check your application configuration. (SBL-DAT-00222)"

Corrective Action

1. Verify that any view or script that refers to the business object only accesses valid business object components within the business object. Check the view to make sure that the applets on it only reference business components within the business object. Verify that any scripts that refer to the business object also only attempt to instantiate business components within the business object.

2. The eAuto Opportunity Sales Step business component is not included in the Account business object. You may add the eAuto Opportunity Sales Step business component to the Account business object by performing these steps:
a. Backup your Siebel Repository File (SRF).
b. Start Siebel Tools.
c. Select Business Object > Account > Business Object Component.
d. Add a new record with the following parameters:
(i) Bus Comp = eAuto Opportunity Sales Step
(ii) Link = Opportunity/eAuto Opportunity Sales Step
(iii) Name = eAuto Opportunity Sales Step
e. Compile the Account business object.

Change request 12-I270YP has been logged to address this behavior.

3. As a workaround, create Workflow Policy Actions in the Workflow Policy definition View or Actions applet. Change Request 12-K8G1BS has been logged to address this behavior.

4. Verify that the settings in the configuration (CFG) file are correct. For example, in the [GatewayDataSrc] section, verify the values for ConnectString, etc. Verify that the Siebel Gateway and Siebel Server are available.

5. This error is encountered during drilldown from a new Service Request record in Home Page view. Change Request 12-M3AJ8G has been logged to address this behavior.

6. As a workaround, add Contact business component into Activity Template business object. Also, if an activity template without an activity is selected, the error will not occur. Change request 12-N5DDTX has been logged to address this behavior.

Applies to:

Siebel Tools - Version: 7.8.2 [19213] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.8.2 [19213]
Database: Oracle 9i
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: HP-UX 11i

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

""Checked for Relevance on 12-Apr-2010""

Symptoms

I have a problem creating a working sequence field.

I want to create a table whose task is to provide a unique, incrementing number. From reading postings on support web, I noticed I must use a parent child relationship, and as Organization was suggested, I decided to use that. The BC is really standalone, so I created a CX table with the relevant fields and a new BC for it.

I have gone through the steps listed in the Bookshelf chapter 'Creating Sequence Fields', and compared my configuration with other BCs with sequence fields and I cant see anything different, but every time I try to create a new record (and so generate an incremented sequence number), I get the error message 'An error has occurred creating business component 'RMG Licence Number.SequenceNo (Sequence)' used by business object 'Organization'. With the sequence number BC in the configuration, record creation works as expected, so the basic configuration is right (NB I put the applet in the Organization Skill View to save extra configuration - this is only a prototype).

The only real difference between my configuration and existing sequence number configuration is the use of a CX table. Is this the problem, or have I missed something?

Cause

.

Solution

The documentation about Sequence Fields (Configuring Siebel eBusiness Applications > Configuring Business Components > About Calculated Fields > Creating Sequence Fields) explains in particular that the numbered detail BC has to have the following:
- - -
- Line Number field. This field, named Line Number, is a field of type DTYPE_NUMBER that holds the resulting sequence value.
- BC user property. A BC user property object definition named Sequence Field needs to be present, with the Value property set to "Line Number."
- - -

It mentions also that the sequence BC is named xx.Line Number (Sequence), where xx is the name of the numbered detail BC.

In fact it is possible to use a Line Number field with a name other that Line Number but in this case the sequence BC has to be named xx.yy (Sequence) where yy is the name of the Line Number field.

The following BCs illustrate this scenario in a standard repository version 7.8:

Sales Assessment Attribute
Sales Assessment Attribute.Order (Sequence)

The first BC has indeed a Line Number field named Order and a Sequence Field user property set to "Order".

In their environment the customer used a field named SequenceNo as Line Number field. The Sequence Field user property was therefore set to "SequenceNo".

However the numbered detail BC was named RMG Licence Number and they used a sequence BC named RMG Licence Number.Line Number (Sequence) instead of RMG Licence Number.SequenceNo (Sequence) hence the error encountered:
- - -
An error has occurred creating business component 'RMG Licence Number.SequenceNo (Sequence)' used by business object 'Organization'.

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

The issue was resolved once the field SequenceNo was renamed Line Number and the Sequence Field user property updated accordingly.

Bug 12-1BSBSR6 has been logged asking for a clarification in the Bookshelf regarding the name of the Line Number field and the name of the sequence BC.

References

BUG:12-1BSBSR6 - SEQUENCE FIELDS - CLARIFICATION ABOUT THE LINE NUMBER FIELD AND THE NAME OF THE SEQUENCE BC

Applies to:

Siebel Tools - Version: 7.7.2 [18325] - Release: V7
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.7.2 [18325]
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server

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

Symptoms

SBL-DAT-00222

While checking the log files of the server the following error was encountered several times:

ObjMgrMiscLog     Error     1     0     2004-10-11 13:34:58     (busobj.cpp (1345)) SBL-DAT-00222: Fehler bei der Erstellung von Business Component 'Admin SEA Application', die von Business Object 'Employee' verwendet wird.

The error is not only happening in connection with Business Object 'Employee'.

Right now we don´t have an idea what could have caused the error.

Please not that the server is experiencing other troubles (task crashes too), which are discussed in another SR.

Cause

The following change request was logged

12-PY2S4U Error reported in Log when changing Responsibility

Solution

We had confirmation from engineering that the error reported in the log is benign and should be ignored.It comes from an error in the CSSBCRole class. The code is assuming that the user is operating under the Responsibility Buscomp under App Admin. There is no critical harm functionality-wise.

According to engineering this is not reproducible in Siebel version 8.

References