SBL-DAT-00322: The specialized method '%1' is not supported on Business Component '%2' used by Business Object '%3'.

Applies to:

Siebel Tools - Version: 7.7.1 [18306] - Release: V7

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-00322: The specialized method '%1' is not supported on Business Component '%2' used by Business Object '%3'.

Scope

This document is informational and intended for any user.

SBL-DAT-00322: The specialized method '%1' is not supported on Business Component '%2' used by Business Object '%3'.

Explanation

The business component class does not support or does not recognize the method which has been passed to it. This error may occur with either a specialized method provided in the standard Siebel application, or with a user-defined method which has been scripted.

1. Common issues when using a specialized method include:

(a) You have copied a buscomp or applet which uses a special class and the method does not work on the copied object.

(b) The method is reserved for Siebel Systems developers and is not supported for general use.

(c) The method requires a particular object class which does not match the class of the object calling the method.

2. Common issues with user-defined methods include:

(a) If the method is being called through code:

i. The PreInvokeMethod does not correctly return CancelOperation if server script, or “CancelOperation” if browser script.

ii. The script object in Tools is marked Inactive.

iii. The method is defined in server script, but is being called from browser script, and you are attempting to pass parameters from the browser script to the server script as part of the InvokeMethod call.

(b) The user-defined method is being called through a runtime event triggered by a workflow process, but the workflow process step has not been set up correctly.

Corrective Action

1. To resolve issues with specialized methods:

(a) Avoid copying objects which are based on special classes. For more information, see Siebel Bookshelf version 7.7 > Configuring Siebel eBusiness Applications > Overview of Configuring Siebel Applications > About Configuring Siebel Applications > About Copying Objects.

(b) Check Siebel Bookshelf for a reference to the method you are trying to use. If it is not documented, it is not supported for general use.

(c) Make sure the object calling the method supports that method. Refer to Siebel Bookshelf version 7.7 > Developer’s Reference to see which classes support the method.

2. To resolve issues with user-defined methods:

(a) Check the following in the script calling the method:

i. The PreInvokeMethod event should return CancelOperation if it is server script, or “CancelOperation” if it is browser script. For more information, refer to Siebel Bookshelf version 7.7 > Object Interfaces Reference.

ii. Make sure the script object is not marked Inactive in the Siebel Tools Object List Editor.

iii. If the method is defined in applet server script but you are calling it from applet browser script, note that you cannot pass parameters in the InvokeMethod call. If possible, move the script to the business component level, or rewrite the script to avoid passing parameters.

(b) If the method is invoked through a workflow process and run-time event, refer to Siebel Bookshelf 7.7 > Siebel Business Process Designer Administration Guide > For Developers: Understanding How Workflow Processes Are Designed > Invoking Workflow Processes > Invoking a Workflow Process from a Run-Time Event for the setup details. Pay special attention to the following:

i. Make sure the Event Cancel Flag is set to TRUE.

ii. The run-time event should be defined on the BusComp PreInvokeMethod event.

iii. Specify the run-time event on a Condition branch, not a Default branch.

Applies to:

Siebel CRM - Version: 8.0.0.9 SIA[20433] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

The spell check function is not working for any field that is configured for spell check.

STEPS:
Steps to reproduce using a Note field that has 'Check Spelling' enabled:

1. Navigation: Accounts > Accounts List > Drilldown on Account.
2. Select Notes View.
3. Add Note, then save Note.
4. Select Note: Press 'Check Spelling' button.

EXPECTED BEHAVIOR
The check spelling routine launches and checks the spelling of the selected field.


ACTUAL BEHAVIOR
The following error message is displayed:
The specialized method 'GetSpellCheckDivider' is not supported on Business Component 'Account Private Note' used by Business Object 'Account'. (SBL-DAT-00322)
_________________________________________________________________________________________________________________________

Changes

Tests indicated this product defect was introduced after applying the single QF0908 to Fix Pack 8.0.0.9 on the AIX platform.

Cause

This problem was reproduced after QF0908 was applied to 8.0.0.9 SIA [20433].

This is a product defect since neither configuration nor scripting was involved in testing of the vanilla SRF.

Solution

Bug 12-1XZBT2P was created to address this Product Defect.

To fix this error in version 8.0.0.9, download QF[0926]  Patch 9751885,  available for platforms AIX, HPUX, SOLARIS, WINDOWS, and LINUX.

SOLUTION:

1. Select 'Patches and Updates' [tab at top of this portal].
2. Select 'Oracle, Siebel and Hyperion Products'.
3. Click 'Simple Search'.
4. Search By 'Patch Number/Name' and enter '9751885'.
5. Select Platform or Language 'Microsoft Windows (32 bit)'.
6. Click 'Go':  '9751885' retrieves: 8.0.0.9 20433 SBA QF0926 SEBL_ARU
7. Download all parts. The first contains the Readme file with installation instructions.
8. Read and follow directions in the Readme file.
9. If you need to download this software for other operating systems, select the appropriate platform from the 'Platform or Language' dropdown and download those files, too.
10. Install and test in a development environment before installing into production.

References

BUG:12-1XZBT2P - SPELL CHECK IS NOT WORKING FOR 8009 AFTER QF0908 WAS APPLIED: GETSPELLCHECKDIVIDER ERROR
PATCH:9751885 - 8.0.0.9 20433 SBA QF0926 SEBL_ARU

Applies to:

Siebel Tools - Version: 8.1.1.2 and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

The customer implemented a custom control on the applet for directing the user to the specified web link with the following steps.

-The applet has CSSSWEFrameBase class.
-Mentioned custom control has a property Method Invoked
-set to GotoUrl and Control User Property
-set to Url with Value = http://mylink.
-set an Applet User Property CanInvokeMethod: GotoUrl = TRUE to activate the button. 

Users found that when clicking the button, the GotoUrl Method is not property invoked and the error
SBL-DAT-00322 is returned.

The specialized method 'GotoUrl' is not supported on Business Component.

Cause

The cause of this behavior is a product defect.  Change request Bug: 12-1OPDA8F  GotoUrl is not supported with the CSSSWEFrameBase Applet class.

Solution

The following suggestions were given to workaround this behavior.

1. Configure with Symbolic URL
2. Use ActiveXObject to open Internet explorer window and pass the desired URL to open the htm file.

References

BUG:12-1OPDA8F - GOTOURL IS NOT SUPPORTED
NOTE:519340.1 - Print Button

Applies to:

Siebel Tools - Version: 7.8.2 [19213] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: Sun Solaris 8

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

Symptoms

SBL-DAT-00322

After upgrading to Siebel 7.8.2, the customer encounters this error message when pressing a button that calls a custom method. There are both Browser and Server scripts associated with Service Request Business Component for that methods

Error message:
The specialized method 'SubmitToQueue' is not supported for Business Component 'Service Request' used by Business Object 'Service Request'. (SBL-DAT-00322)


The error message appears only for users that have Windows 2000 client machines and who access the application through Sun Web Server 6.1.

The error message does not appear if the same Windows 2000 client users access the application through IIS 4.0.

Cause

Using an Internet sniffer, it could be seen that the Siebel Client application could not access the blank.htm file on the Solaris Web Server.

Below is an extract of the SWSE log files:
[04/Oct/2005:15:51:42] warning ( 7860): for host xxx.xx.xxx.xx trying to GET /callcenter_enu/blank.htm, send-file reports : HTTP4142: can't find /opt/nokiacif/siebel-wse/electra/data/public/enu/blank.htm (File not found)
[04/Oct/2005:16:02:32] warning ( 7860): for host xxx.xx.xxx.xx trying to GET /callcenter_enu/blank.htm, send-file reports : HTTP4142: can't find /opt/nokiacif/siebel-wse/electra/data/public/enu/blank.htm (File not found)
[04/Oct/2005:16:03:25] warning ( 7860): for host xxx.xx.xxx.xx trying to GET /callcenter_enu/blank.htm, send-file reports : HTTP4142: can't find /opt/nokiacif/siebel-wse/electra/data/public/enu/blank.htm (File not found)
[04/Oct/2005:16:14:48] warning ( 7860): for host xxx.xx.xxx.xx trying to

Bug 12-JZZC4U has been logged to address this product defect.

Solution

Fix Request 12-VGISEM has been released for Bug 12-JZZC4U, which has been fixed in Siebel Maintenance Release 7.8.2. The latest Fix Pack should be applied to Siebel Maintenance Release 7.8.2.

For more details refer to Document 477738.1 Browser Script Will Not Execute on Dedicated and Mobile Clients in Siebel Applications Version 7.7.1

References

NOTE:477738.1 - Browser Script Will Not Execute on Dedicated and Mobile Clients in Siebel Applications Version 7.7.1
BUG:12-JZZC4U - BROWSERSCRIPT NOT WORKING ON TWSIEBEL (DEDICATED AND MOBILE CLIENT)

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3.6 [16186] ESN Com/Med
Database: Oracle 8.1.7.4
Application Server OS: HP-UX 11i
Database Server OS: HP-UX 11i

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

Symptoms

SBL-DAT-00322, SBL-EAI-04400

Hello

We have a repetitive error in log file of eCommWirelessObjMgr. This error is in the four OM.

The line error is this:

EAISiebAdpt     EAISiebAdptErr 1       2004-11-17 09:05:39     [0] No hay ningún tipo de objeto de salida especificado en el
argumento de método de servicio(SBL-EAI-04400) (IDS_ERR_EAI_SA_OUT_OBJ_TYPE)
SisnTcpIp       SisnSockError   1       2004-11-17 09:28:15        176: [TCPIP-server] send() failed for sd=-1 (err=9 | Bad fi
le number)
ObjMgrBusServiceLog     InvokeMethod    4       2004-11-17 10:57:11     Begin: Business Service 'Web Engine Interface' invoke
method: 'Request' b23d740
EventContext    EvtCtxView      3       2004-11-17 10:57:11     Account Detail - Activities View
ObjMgrBusCompLog        Delete 4       2004-11-17 10:57:11     BusComp was deleted 13b59970 "WI HTTP Host"
ObjMgrBusCompLog        Delete 4       2004-11-17 10:57:11     BusComp was deleted 5bdeb90 "WI Content Fixup"
ObjMgrBusCompLog        Delete 4       2004-11-17 10:57:11     BusComp was deleted 13b5ca80 "WI Symbolic URL Argument"
ObjMgrBusCompLog        Delete 4       2004-11-17 10:57:11     BusComp was deleted 5d38078 "WI Symbolic URL"
ObjMgrBusCompLog        Delete 4       2004-11-17 10:57:11     BusComp was deleted 5bd9340 "WI Web Application"
ObjMgrBusCompLog        Delete 4       2004-11-17 10:57:11     BusComp was deleted 5be6638 "Message Def"
ObjMgrBusCompLog        Create 4       2004-11-17 10:57:11     Begin: construct BusComp b4434f0 "Action"
ObjMgrBusCompLog        Create 4       2004-11-17 10:57:11     End: construct BusComp b4434f0 "Action"
ObjMgrBusCompLog        Create 4       2004-11-17 10:57:11     Begin: construct BusComp 5be6638 "FIN Alert Organization"
ObjMgrBusCompLog        Create 4       2004-11-17 10:57:11     End: construct BusComp 5be6638 "FIN Alert Organization"
ObjMgrLog       Error   4       2004-11-17 10:57:11     (SBL-DAT-00322) El método especializado 'SetDefaultDuration' no se ad
mite en...

Solution

Message 1

For the benefit of other users:

Both the errors encountered were reproduced with the standard SRF but did not adversely affect the functionality of the application.

1) The error:

(SBL-DAT-00322) The specialized method 'CalculateForHI' is not supported on Business Component 'Asset Mgmt - Asset' used by Business Object 'Asset Management'.

was reproduced when navigating to the Assets > All Assets view. Change Request 12-QZ1CZO has been raised to address this Product Defect.

2) The error:

(SBL-DAT-00322) The specialized method 'SetDefaultDuration' is not supported on Business Component 'Account' used by Business Object 'Account'.

was reproduced when navigating to Accounts > All Accounts across organizations view. Change Request 12-QYYYKH has been raised to address this Product Defect.

Siebel Technical Support