Siebel SQLs/Error Messages >  SBL-ESC-00201 Error creating triggers

SBL-ESC-00201 Error creating triggers

On : 8.1.1.11.15 [IP2013] version, Siebel Workflow

SBL-ESC-00201

Trying to run Generate Triggers for a Workflow Policy that uses an 'IS DELETED' condition, it fails with the error SBL-ESC-00201.

On one policy that we set up some months back it works fine. On a second policy that we just created it fails each time.

The second policy's condition is based on workflow policy object 'CCCI_Google_Activity', here is the condition:

Activity IS DELETED

It is from 'CCCI Google Activity' workflow policy component and is considered as a child workflow policy component of 'CCCI Google Archive' workflow policy component.

The policy we set up months ago has a similar condition that is based on another workflow policy object 'CCCI_GR_Person', the delete trigger is created successfully, here is the condition:

Contact IS DELETED

It is Contact workflow policy component and is considered as a child workflow policy component of 'Global Registry IDs' workflow policy component.

I don't see any significant differences between the two Workflow Policies or the associated Workflow Policy Objects.

ERROR
-----------------------
SBL-ESC-00201: Error creating triggers

In WorkMon log, the following errors:

SQLStatementOptions Free Statement Details 5 0004936755ce0eec:0 2015-12-15 10:53:49 (SQLFreeStmt) Option: SQL_RESET_PARAMS
GenericLog GenericError 1 0004936755ce0eec:0 2015-12-15 10:53:49 Message: GEN-11,
Additional Message: no trigger type

ProcReq GenericFatal 0 0004936755ce0eec:0 2015-12-15 10:53:49 Failed to load trigger condition information in LoadConditions
GenericLog GenericError 1 0004936755ce0eec:0 2015-12-15 10:53:49 Message: GEN-10,
Additional Message: Calling Function: LoadConditions; Called Function: Failed to load trigger condition information

CAUSE
Custom CX table configuration issue.

The 2 different Workflow Policy Objects are based on 2 different custom CX tables.

The workflow policy object 'CCCI_GR_Person' is based on the table CX_GR_INTEG.
The workflow policy object 'CCCI_Google_Activity' is based on the table CX_GOOG_ARCHIVE.

Based on how workflow policy component's Target Column Name and Target Component Name are configured which uses the column from CX table:

Contact IS DELETED:

Contact, non-primary
Source Table Name: S_CONTACT
Source Column Name: ROW_ID
Target Column Name: ENTITY_ID
Target Component Name: Global Registry IDs

Activity IS DELETED:

CCCI Google Activity, non-primary
Source Table Name: S_EVT_ACT
Target Column Name: SBL_ROW_ID
Target Component Name: CCCI Google Archive

The only difference between them by comparing the columns SBL_ROW_ID and ENTITY_ID, how they are configured on the 2 CX tables, is the following:

=====
table: CX_COOG_ARCHIVE

SBL_ROW_ID Foreign Key Table = blank

table: CX_GR_INTEG

ENTITY_ID Foreign Key Table = S_ADDR_PER
=====

The Workflow Policy Component 'CCCI Google Activity' has the Workflow Policy Column 'Activity Id'.
SBL_ROW_ID should have a 'Foreign Key Table' like S_EVT_ACT because it is related to S_EVT_ACT.

SOLUTION
Since these are custom tables and Tech Support does not have information for creating and configuring a custom table, suggest customer to look into 'Foreign Key Table' for column SBL_ROW_ID on CX_COOG_ARCHIVE table, if it should have a foreign key table mapped. If so, add the table name there, do the necessary changes to sync this schema change to Siebel database and rerun Generate Triggers to see if it works or not. You should always test thoroughly in pre production environment first before implementing in production environment.

Customer made that change (entering S_EVT_ACT as the foreign key table on CX_GOOG_ARCHIVE.SBL_ROW_ID), then compile on the server to test. Customer did have to clear the cache for the Generate Triggers process again (refer to Solution in Doc ID 1597130.1), but it did work after that.