SBL-BPR-00239: Cannot find Service Calendar with name "%1".

Applies to:

Error Message Area:Business Processes/Workflow - BPR

Version:Siebel 7.7

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-BPR-00239: Cannot find Service Calendar with name "%1".

Scope

This document is informational and intended for any user.

SBL-BPR-00239: Cannot find Service Calendar with name "%1".

Explanation

Cannot find Service Calendar with the specified name in the database. The Service Calendar, and the workflow definition where it is defined, may have been defined in a different application environment.

Corrective Action

You need to edit workflow definition and re-define/re-select Service Calendar: 1. In workflow designer, double click on the Wait step where the Service Calendar is used. 2. In the form applet on the top, click on the icon in "Service Hours" field and select an existing Service Calendar in the applet that pops up.

Applies to:

Product Release: V7 (Enterprise)

Version: 7.7.1 [18306] Auto

Database: Oracle 9.2.0.4

Application Server OS: Sun Solaris 8

Database Server OS: Sun Solaris 8



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

Symptoms

SBL-BPR-00239

Hi,

We are using Siebel eDealer for our Dealer Implementation and Siebel Automotive for
Administration and Maintenance functions.

We are noticing a strange behaviour with
Opportunity Business Component and we are not sure since when this has started happening. Each
time we create a record
in Opportunity Business Component and try to step off we get an error
as "The lookup of LOV '<>' for entry named '<>' failed (SBL-BPR-0023)". The record is
saved to the database but each time the record is created we are getting this error. in eDealer
whenever a new showroom log entry is created for a new contact it also creates the Opportunity
record so it appeared as if the error was occuring when creating the opportunity from a showroom
log entry.

I then created an Opportunity from the Opportunity List View in Automotive
also and each time i create a new record i get the same error. So the problem lies with the
Opportunity Business Component than the showroom log business component. Since the error message
doesn't exactly indicate what LOV is causing the problem , i checked all the fields that use
piclklists and for pre-default/post-default expressions that use Lookup value function and the
LOV values exist in our only environment ,pilot. I also looked at the business component user
properties and verified the LOV values existed for those that are referenced.

The spool
of sql also didn't give me much information. I am not sure how we can trouble-shoot this issue.
The only database activity that has happened in the last few weeks was we did a refresh of siebel
oltp which should not have any effect on the above experienced behaviour. I also tested this
using vanilla application and we still get the same error on our database. This leads me to
believe that this is not a configuration issue with our eDealer Implementation but something at
the database or at the LOV level that is causing the above error. I have looked at the support
web for any relevant findings and...

Solution

Message 1

Customer was using Siebel eDealer for Dealer Implementation and Siebel Automotive for Administration and Maintenance functions.



Each time a record was created in Opportunity Business Component and you try to step off you get an error as "The lookup of LOV '<>' for entry named '<>' failed (SBL-BPR-0023)". The record is saved to the database but each time the record is created we are getting this error. in eDealer whenever a new showroom log entry is created for a new contact it also creates the Opportunity record so it appeared as if the error was occuring when creating the opportunity from a showroom log entry.



The problem lies with the Opportunity Business Component than the showroom log business component.



Resolution:

Customer had defined a workflow that was referencing an invalid LOV in the server database.



The LOV was removed and the workflow process was deleted. It was a process the customer had created for testing purposes.



As soon as the above were removed, the error was not seen again.



Keywords: LOV and SBL-BPR-0023