Skip to main content

Server Jobs or Repeating Jobs - picking component parameters : The Server object was not found.(SBL-SCO-09100) (Doc ID 1944522.1)

APPLIES TO:
Siebel CRM - Version 8.1.1.11 [IP2013] to 17.0 [IP2017] [Release V8 to V17]
Siebel eAutomotive - Version 8.1.1.14.4 [IP2014] to 8.1.1.14.4 [IP2014] [Release V8]
Information in this document applies to any platform.

DESCRIPTION
In Siebel version 8.1.1.11 Patch Sets ; 10, 11, 12 , 8.1.1.14 , IP15, IP16, IP17:
1) In Administration - Server Management --> Jobs
2) Create a job for Generate Triggers component
3) Go to Parameter applet and select EXEC parameter
The picking of the parameter can fail with the error :

The Server object <?> was not found.(SBL-SCO-09100)

OCCURRENCE
This is happening for some job parameters, not all parameters.
The behavior may not necessarily occur if you are using Siebel version 8.1.1.11 Patch Set 10, 11, 12 , 8.1.1.14 , IP15, IP16, IP17 :
This behavior has been observed for several target components (ie. it is not restricted to Generate Triggers).

SYMPTOMS
 The Server object <?> was not found.(SBL-SCO-09100)



 SBL-CSO-09100 error when picking job parameter

WORKAROUND
 A bug was raised for this issue :

SBL-CSO-09100: THE SERVER OBJECT <?> WAS NOT FOUND

Siebel Engineering provided a Siebel Tools archive file (.sif) for the 'Batch Job Parameter' business component.

The root cause of the issue has been determined that there have been some code changes in 8.1.1.11 Patch Set 10 through Patch Set 12, that is affecting the compilation process.  The sequencing of fields at compilation time can change.  This is affecting the resultant query at runtime (ie. when the Siebel application is running).  So the order of the fields is changing in the SQL select statement.  For the business component Batch Job Parameter, this is having the affect that the fields are not being interpreted correctly and is resulting in the error :

The Server object <?> was not found.(SBL-SCO-09100)

At Job parameter pick time.

Please find attached, a Siebel Tools .sif file :

buscomp-batch-job-parameter.sif

This contains only the business component : Batch Job Parameter.

Please import this (Siebel Tools import wizard) into a suitable development / test environment and then compile this specific business component into your Siebel .srf
This Batch Job Parameter business component can be used in 8.1.1.11, 8.1.1.14 , IP15, IP16, it has been confirmed to resolve this problem in this Siebel versions.
For Ip2017 - create a WorkSpace and then do the Import in the Tools.
When you have tested this in your development / test environment, the Siebel .srf can be moved to your live / production system, as per your standard release process.

Source:

https://support.oracle.com/ > Doc ID 1944522.1

Comments

Popular posts from this blog

How to set Profile Attribute in Siebel Workflow

For setting the Profile Attribute in Siebel Workflow, follow below steps: Add Business Service box in workflow. Open Business Service properties. Set  SessionAccessService in Business Service Name. Set  SetProfileAttr in Method Name. Then click on Business Service and set Input Arguments as below: Against Name argument you will add your profile attribute name and against Value argument you will add value for the new profile attribute, it could be from Process Property or Literal.

How to call Popup Applet through Server Script in Siebel

Background: Based on the requirements you need to show data or reports on a popup applet. You can invoke popup applet using workflow (below business service will be used in business service step), applet server script or browser script and using vanilla method and setting field user properties. Procedure: Below is the script for calling popup applet through server script: if (MethodName == "MethodName") { var oServiceAF = TheApplication().GetService("SLM Save List Service"); var inputPropAF = TheApplication().NewPropertySet(); var outputPropAF = TheApplication().NewPropertySet(); inputPropAF.SetProperty("Applet Name","ABC Popup Applet"); inputPropAF.SetProperty("Applet Mode","6"); inputPropAF.SetProperty("Applet Height", "700"); inputPropAF.SetProperty("Applet Width", "700"); oServiceAF.InvokeMethod("LoadPopupApplet", inputPropAF, outputPropAF) return (CancelOperati...

How to create and publish Inbound Web Service in Siebel based on Workflow

Inbound Web Services: The Inbound Web Service allows an external system to call a Siebel published Web Service. You can publish a business service or a business process as a Web Service and generate a Web Service Definition Language (WSDL) file that an external system can import. The Inbound Web Services can only be published from Siebel C using SOAP-RPC binding. Source: Oracle Docs What Is The Difference Between Web Services and APIs? An API is an interface that allows you to build on the data and functionality of another application, while a web service is a network-based resource that fulfills a specific task. Yes, there’s overlap between the two: all web services are APIs, but not all APIs are web services. Both web services and APIs are — at their core — very useful and very much used today. However, it’s the web services associated with SOAP and/or Service Oriented Architecture which are falling out of favor. Source: NordicApis Process: Prepare the workflow which will serve as Si...