SBL-DAT-00144 "Could not find name"

Applies to:

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

Symptoms

The customer reported that the 8.0.0.2 Public Sector application standard Solutions find object returns an error.  The other Find objects worked fine without any errors.  In this case, only the Solutions Find object returned this error in the Public Sector application.

If you are getting this error for all of the find objects with a Siebel 8.0.0.2 client with the configuration steps documented for ACR 367, verify that you have added the Search Find Results View to the application and that the view is in the user's responsibilities

Another possible cause for a similar error is if the user is entering a find condition in the Search for: control which should be used only for Siebel Search indexes not find objects.  In that case, the following error is returned. 

The view <?> cannot be displayed.  Please contact your System Administrator (SBL-SRH-50043).

If you are getting this error, then try doing the find search using the find fields and not the Search For field.

 

Cause

This incorrect behavior is due to change request 12-1013BID which was raised as a product defect.
The standard 8.0.0.2 SIA Public Sector Application Find configuration uses the Solution - SHCEService Find object and not the Solutions Find object.
Note that the Solution-SHCEService and the Solutions Find objects both have the display name of Solutions.
The Solution-SHCEService Find object had the following two views..
SHCE Service Solution Find View
SHCE Service Async Query Results Solution List View

These views are in the seed data Field Technician - Handheld Responsibility which most seed data users do not have access to.
Product Defect 12-1013BID notes that the 8.0.0.2 Public Sector application should use the Solutions Find object, which displays the All Solution List View. This view is included in most of the seed data responsibilities.

This behavior is also related to how Siebel Search Find with Siebel 8 works with Responsibilities.

See this document too.

Siebel 8 - Search Center - All Users, Except Siebel Administrator, Get Error SBL-DAT-00144 <Doc: 563439.1> .

Solution

The workaround for this behavior is to modify the SIA application to use the Solutions Find object.
This modification needs to be done in the srf file and in the Siebel applications server database Repository Tables. This is because the following sql is executed to find the application's find objects.
SELECT
T1.CONFLICT_ID,
T1.LAST_UPD,
T1.CREATED,
T1.LAST_UPD_BY,
T1.CREATED_BY,
T1.MODIFICATION_NUM,
T1.ROW_ID,
T1.NAME,
T2.OBJ_LOCKED_LANG,
T2.OBJ_LOCKED_FLG,
T2.OBJ_LOCKED_BY,
T1.APPLICATION_ID,
T2.NAME,
T2.PROJECT_ID,
T3.LOCKED_FLG,
T3.LOCKED_BY,
T3.NAME,
T3.UIFREEZE_FLG,
T3.UIFREEZE_BY,
T1.REPOSITORY_ID,
T1.FIND_NAME,
T2.MODULE_NAME,
T1.INACTIVE_FLG,
T2.ROW_ID,
T3.ROW_ID
FROM
SIEBEL.S_APPL_FIND T1
INNER JOIN SIEBEL.S_APPLICATION T2 ON T1.APPLICATION_ID = T2.ROW_ID
LEFT OUTER JOIN SIEBEL.S_PROJECT T3 ON T2.PROJECT_ID = T3.ROW_ID
WHERE
(T2.NAME = ? AND T1.INACTIVE_FLG != ?)
ORDER BY
T1.NAME

ObjMgrSqlLog Detail 4 00000002480306a0:0 2008-04-14 18:25:45 Bind variable 1: Siebel Public Sector

ObjMgrSqlLog Detail 4 00000002480306a0:0 2008-04-14 18:25:45 Bind variable 2: Y
In summary the workaround is the following steps:

1. Modify the Siebel Public Sector to not use the Solution-SHCEService find object.
But instead have it use the Solutions find object.
2. Due to the architecture change with Search/Find with Siebel 8.0, you have to make sure that the server RDBMS also has this change for the Siebel Repository.

Oracle Siebel Support