Siebel SQLs/Error Messages >  SBL-ESC-00106: Error loading Attribute handle for Object Order

SBL-ESC-00106: Error loading Attribute handle for Object Order
Error calling function: WFObjectOpen

The customer reviewed Assignment Objects listed for the Order Workflow Policy Object, 'Order (Sales Credit Assignment)' and 'Order'. After customer confirmed that NO Assignment Attributes were associated with the Order asgn object, it was decided to deactivate it in Tools > Workflow Policy Object > Assignment Objects.

Deactivating the Order object resolved the error.

Assignment Manager Failing To Start With Errors: SBL-ESC-00106, SBL-GEN-03006

APPLIES TO:
Siebel Assignment Manager - Version 7.5.3 [16157] to 8.1.1 [21112] [Release V7 to V8]
z*OBSOLETE: Microsoft Windows 2000
**checked for relevance on Jan-24-2016**

Product Release: V7 (Enterprise)
Version: 7.5.3 [16157]
Database: Oracle 9.2.0.2
Application Server OS: Microsoft Windows 2000 Advanced Server SP 3
Database Server OS: Sun Solaris 2.7

This document was previously published as Siebel SR 38-1083309541.
SYMPTOMS
The 'State' for Server Component 'Assignment Manager' is unavailable. The error message on the AsgnSrvr_*.log file is:

1-4VW2-6YM2 in GetColNameById
(attrapi.cpp 4(832) err=700106 sys=0) SBL-ESC-00106: Error loading Attribute handle for Object Opportunity.
(asgnobj.cpp 24(248) err=3006 sys=0) SBL-GEN-03006: Error calling function: WFObjectOpen

CAUSE
The error is pointing to an incorrect configuration of the Workflow Policy Object ("Opportunity" in this specific case, but the errors will be the same for other policy objects).

SOLUTION
To gather further information please execute following two queries. If you are using SQL Plus to spool the information, please set the linesize to at lease 500. This is to ensure that all the information is being captured. Replace <repository_row_id> by the correct row id value.

1.
select link.ROW_ID,
link.SRC_TBL_ID,
link.SRC_COL_ID,
link.TAR_TBL_INST_ID,
link.TAR_COL_ID,
link.PRIMARY_FLG,
link.NAME,
link.ADDTL_JOIN_SPEC
from SIEBEL.S_ESCL_LINK link,
SIEBEL.S_ESCL_OBJECT obj
where obj.NAME = 'Opportunity' AND
obj.REPOSITORY_ID = '<repository_row_id>' AND
(obj.INACTIVE_FLG = 'N' OR obj.INACTIVE_FLG IS NULL) AND
link.OBJECT_ID = obj.ROW_ID AND
(link.INACTIVE_FLG = 'N' OR link.INACTIVE_FLG IS NULL)
order by link.NAME

2.
select link.NAME,
linkcol.NAME,
col.NAME,
linkcol.TBL_INST_ID,
col.COL_ID,
repos_col.DATA_TYPE,
repos_col.LENGTH
from SIEBEL.S_COLUMN repos_col,
SIEBEL.S_ESCL_COL col,
SIEBEL.S_ESCL_LINK_COL linkcol,
SIEBEL.S_ESCL_LINK link,
SIEBEL.S_ESCL_OBJECT obj
where obj.NAME = 'Opportunity' AND
obj.REPOSITORY_ID = '<repository_row_id>' AND
(obj.INACTIVE_FLG = 'N' OR obj.INACTIVE_FLG IS NULL) AND
link.OBJECT_ID = obj.ROW_ID AND
(link.INACTIVE_FLG = 'N' OR link.INACTIVE_FLG IS NULL) AND
linkcol.TBL_INST_ID = link.ROW_ID AND
(linkcol.INACTIVE_FLG = 'N' OR linkcol.INACTIVE_FLG IS NULL) AND
col.ROW_ID = linkcol.COND_COL_ID AND
repos_col.ROW_ID = col.COL_ID
order by link.NAME, linkcol.NAME

Based on the error "1-4VW2-6YM2 in GetColNameById" please research the SQL output to identify the corresponding column that is causing the error.

NAME NAME_1 NAME_2 TBL_INST_ID COL_ID DATA_TYPE LENGTH
Division Name Division Name Division Name 1-4VW2-F4SB 1-4VW2-6YM2 V 50

Here the error can be referred back to the "Division Name" Workflow Policy Column. Please perform next steps:

1. Workflow Policy Object > "Opportunity" > Workflow Policy Component > "Division Name"
Select the record, click the right mouse button and then Validate.... Create a screenshot if an error is found and paste it into a word document.

2.1. Workflow Policy Column > "Division Name"
Select the record, click the right mouse button and then Validate.... Create a screenshot if an error is found.

2.2. Workflow Policy Column > "Division Name"
Reselect the values for Table Name (choose another table and then the correct one) and Column Name. Verify the Inactive flag status. Check in the project to the server. Does Validate... show any error? Restart Assignment Manager.

Solution:
The error was found in the "Division Name" Workflow Policy Column mapping the "S_ORG_INT" table. S_ORG_INT is an obsolete table which has been merged into S_ORG_EXT since Siebel version 7.

Customer inactivated the "Division Name" Workflow Policy Column and configured the already existent "Account Name" Workflow Policy Column instead. These changes fixed the Assignment Manager behavior.