Search This Blog

SBL-DAT-00144: Could not find '%1' named '%2'. This object is inactive or nonexistent.

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


References

NOTE:563439.1 - Siebel 8 - Search Center - All Users, Except Siebel Administrator, Get Error SBL-DAT-00144

Show Related Information Related


Products
  • Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel Tools
Keywords
CONFIGURATION; SIEBEL APPLICATION
Errors
SBL-DAT-00144; SBL-SRH-50043

Applies to:

Siebel Reports - Version: 8.1.1.3 SIA[21219] and later   [Release: V8 and later ]
Information in this document applies to any platform.
Siebel 8.1.1.3 Fix Pack, BI Publisher 10.1.3.4.1

Symptoms

When attempting to run BIP reports by clicking Reports menu icon, the following error occurs:

ERROR
-----------------------
"SBL-DAT-00144: Could not find 'Business Component' named 'Report Template Position BC'. This object is inactive or nonexistent."

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. In Siebel application (Thin or Thick client), you click Reports menu icon
2. The error above is displayed.

Changes

This happens after installing Siebel 8.1.1.3 Fix Pack.

Cause

The error can occur when you have not complete all configuration steps to integrate BI Publisher with Siebel 8.1.1.3 Fix Pack.

You should follow all steps from Bookshelf 8.1: Siebel Reports Guide, Rev. C (June 2010).

Solution

Please note that after installing 8.1.1.3 Fix Pack you should follow all steps from Bookshelf 8.1: Siebel Reports Guide, Rev. C (June 2010), under Chapter 4. Integrating Oracle BI Publisher with Siebel Business Applications > Process of Configuring the Siebel Application for Integration with Oracle BI Publisher, which includes import BIP_8113FP.sif file and Apply DDL.

Bookshelf 8.1: Siebel Reports Guide, Rev. C (June 2010) can be downloaded from:
http://download.oracle.com/docs/cd/E14004_01/books/Reports/ReportsTOC.html



Show Related Information Related


Products
  • Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel Reports
Keywords
REPORT; INSTALL; BI PUBLISHER
Errors
SBL-DAT-00144; 00144 ERROR

Applies to:

Siebel Universal Customer Master - Version: 8.0 [20405] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

Data is being processed from an external system into UCM using "UCM Account Batch Data Management Workflow" in batch mode.

Some data was left was an incomplete status. The failure occurred when the Account details were the same, but the Country in the Address was different. Exact Match is being used, and for these cases, it should have updated the existing master.

For example: the master record in UCM has 1689 Ingleton Avenue,Burnaby, BC, V5C 4L8, USA and the record processed is 1689 Ingleton Avenue,Burnaby, BC, V5C 4L8, CANADA. This record goes to incomplete status. The records corresponding S_UCM_ADDR_PER record stays in "Batch" status. UCM_TYPE_CD = 'Batch' is the status used for records imported into UCM_ORG_EXT using EIM.

The error seen in the failure log is :-

Error invoking service 'UCM Batch Manager', method 'HandleMatchCase' at step 'Process AutoMatch'.(SBL-BPR-00162)
--
Could not find '<?>' named '<?>'. This object is inactive or nonexistent.(SBL-DAT-00144)

Also noticed was the following :-

SBL-DAT-00144: Could not find 'Business Object' named 'CIF StatusObject Reference'. This object is inactive or nonexistent.

Cause

The problem is due to reported behaviour in the following change request :-

Bug 12-1MBPPSX - Could not find 'Business Object' named 'CIF StatusObject Reference'

There is a SQL select statement on S_PARTY which will not work. It has a criteria including a WHERE clause on LAST_UPD, for which 0 rows will be returned (leading to above error). This is because S_PARTY.LAST_UPD has already been updated in a previous UPDATE. Because 0 rows are returned, the error above occurs.

Solution

After making the following changes, the error could be avoided, and the address update processed ok :-

1. Find the 'CIFAccountUpdate' Integration Object in Tools.
2. For the 'Account' Integration Component, review the Integration Compenent Keys. For the key named 'Status Key', inactivate the 'Updated' Integration Component Key Field.
3. Compile to SRF, and re-test scenario where an incoming Account / Address matches existing data, but with a different Country.

References

BUG:12-1MBPPSX - COULD NOT FIND 'BUSINESS OBJECT' NAMED 'CIF STATUSOBJECT REFERENCE'

Show Related Information Related


Products
  • Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel Universal Customer Master
Keywords
BATCH MANAGER; STATUS KEY; WHERE CLAUSE; INCOMPLETE STATUS; ACCOUNT DETAILS; SCENARIO; UNIVERSAL CUSTOMER MASTER
Errors
SBL-BPR-00162; SBL-DAT-00144

Applies to:

Siebel Universal Customer Master - Version: 8.0 [20405] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

Data is being processed from an external system into UCM using "UCM Account Batch Data Management Workflow" in batch mode.

Some data was left was an incomplete status. The failure occurred when the Account details were the same, but the Country in the Address was different. Exact Match is being used, and for these cases, it should have updated the existing master.

For example: the master record in UCM has 1689 Ingleton Avenue,Burnaby, BC, V5C 4L8, USA and the record processed is 1689 Ingleton Avenue,Burnaby, BC, V5C 4L8, CANADA. This record goes to incomplete status. The records corresponding S_UCM_ADDR_PER record stays in "Batch" status. UCM_TYPE_CD = 'Batch' is the status used for records imported into UCM_ORG_EXT using EIM.

The error seen in the failure log is :-

Error invoking service 'UCM Batch Manager', method 'HandleMatchCase' at step 'Process AutoMatch'.(SBL-BPR-00162)
--
Could not find '<?>' named '<?>'. This object is inactive or nonexistent.(SBL-DAT-00144)

Also noticed was the following :-

SBL-DAT-00144: Could not find 'Business Object' named 'CIF StatusObject Reference'. This object is inactive or nonexistent.

Cause

The problem is due to reported behaviour in the following change request :-

Bug 12-1MBPPSX - Could not find 'Business Object' named 'CIF StatusObject Reference'

There is a SQL select statement on S_PARTY which will not work. It has a criteria including a WHERE clause on LAST_UPD, for which 0 rows will be returned (leading to above error). This is because S_PARTY.LAST_UPD has already been updated in a previous UPDATE. Because 0 rows are returned, the error above occurs.

Solution

After making the following changes, the error could be avoided, and the address update processed ok :-

1. Find the 'CIFAccountUpdate' Integration Object in Tools.
2. For the 'Account' Integration Component, review the Integration Compenent Keys. For the key named 'Status Key', inactivate the 'Updated' Integration Component Key Field.
3. Compile to SRF, and re-test scenario where an incoming Account / Address matches existing data, but with a different Country.

References

BUG:12-1MBPPSX - COULD NOT FIND 'BUSINESS OBJECT' NAMED 'CIF STATUSOBJECT REFERENCE'

Show Related Information Related


Products
  • Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel Universal Customer Master
Keywords
BATCH MANAGER; STATUS KEY; WHERE CLAUSE; INCOMPLETE STATUS; ACCOUNT DETAILS; SCENARIO; UNIVERSAL CUSTOMER MASTER
Errors
SBL-BPR-00162; SBL-DAT-00144

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3.4 [16180] DAN
Database: Oracle 9.2.0.2
Application Server OS: Microsoft Windows NT Enterprise 4.0 SP 6a
Database Server OS: Microsoft Windows NT Enterprise 4.0 SP 6a

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

Symptoms

SBL-DAT-00144, SBL-DAT-00192, SBL-DAT-00227

Please assign this SR to an engineer with high skills of both Siebel Marketing, Workflow Processes and Business Services.

We have upgraded from 6.3 to 7.5.3.4 DAN and still need to use a customized WF for campaign launch (previously campaign execution).

The customized campaign launch WF includes a custom BS step and it worked fine in Siebel 6.3.

In 7.5.3 we have tried both of the following:

1. Exporting the Campaign Execution WF from 6.3 and then Importing it to 7.5.3, change name to Campaign Launch and then activate.

2. Manually revise the existing Campaign Launch WF in 7.5.3 to include our customizations from 6.3.

When creating snapshots and loading campaign (populating campaign in 6.3) no errors occur.
However, when launching campaign manually the following error displays (no matter which of the above two methods was used):

SBL-OMS-00203: Error 32956 invoking method "RunProcess" for Business Service "Workflow Process Manager"

From looking into the log file (attached) the following two errors turn up:
SBL-DAT-00144 and SBL-DAT-00192.

I've found only one SR in Support Web including the above SBL-DAT errors (SR # 38-1224781281) but this is not related to our problem.

The custom BS in question - Nyk Modify List Output - is included in the SWE section of the cfg file (attached to this SR).

The WF component group is only installed on a single server in accordance with the instructions for SME configuration as specified in the Siebel Marketing Initialization Checklist in the Siebel Marketing Guide. This component installation should be correct as the WF runs OK when loading campaign.

The custom BS is included in the compiled SRF file on the servers.

So basically we need answers to the following questions:
1. Why do we see the SBL-DAT-00144 and SBL-DAT-00192 errors when BS is included in both the siebel.cfg file on the server and the compiled srf file on the server?
2. How do we proceed?

Looking forward to your answer.
...

Solution

Message 1

For the benefits of the other readers:
The customer customized the Campaign Execution workflow in Siebel Marketing 6.3.
After upgrading to Siebel Marketing 7.5.3 they included their customization into Campaign Launch Workflow and launched their campaign. However the Campaign Launch failed with the following error:

(SBL-DAT-00192) Unable to find the definition of Business Service 'Nyk Modify List Output' in either the repository or run-time tables.
(SBL-DAT-00144) Could not find 'Class' named 'Nyk Modify List Output'. This object is inactive or nonexistent.
(SBL-DAT-00227) Unable to create the Business Service 'Nyk Modify List Output'

The customer run Siebel Marketing 7.5.3 in Danish and the default language of the Workflow Process Component was ENU.
They compiled only the Danish Repository and put into SiebSrvr\Object\Dan folder. However the Campaign Launch workflow was run in ENU and their customization were not compiled in the ENU repository located in SiebSrvr\Object\ENU folder.
Changing the default language of the Worflow Process component to DAN resolved the error.

The customer noticed that when launching a custom workflow using button or even the workflow was then defaulted to the Language of the corresponding component used to launch it.

Change Request 12-KWLOVN has been raised to address this Enhancement Request (select a campaign Launch on DAN client should not launch an ENU Workflow)

Magali Barreau-Combeau
Siebel Technical Support

No comments:

Post a Comment