Applies to:
Siebel Tools - Version: 7.7.1 [18306] to 8.1.1 [21112] - Release: V7 to V8Information in this document applies to any platform.
Error Message Area:Data Manager - DAT
Version:Siebel 7.7
Purpose
This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-00472: Generic SSA NOTOK error message.
Scope
This document is informational and intended for any user.
SBL-DAT-00472: Generic SSA NOTOK error message.
Explanation
This is a generic Object Manager error. Below are some known causes for this error and you should confirm you are not encountering these behaviors:1. The error was reported because the user entered a new record into the Siebel application that fired a runtime event which itself tried to start a workflow process manager server task for a workflow process that no longer existed in the Siebel database. To help determine if you are encountering this behavior, try the following steps:
a. Follow the instructions in FAQ 1482 to enable events logging for the Workflow Process Manager Server component. Review the log file for any message similar to the following:
Cannot initiate process definition '1-E3I'. Verify that it does exist, has an 'Active' status, is activated and has not expired.
b. To determine if a workflow process exists in the database, run the following query (use the information obtained from the workflow process manager log file, in the above example, the ROW_ID = '1-E3I'):
SELECT * FROM S_WF_STEP WHERE ROW_ID = '1-E3I'
If a record is returned, confirm the workflow process is active and has not expired. If a record is not returned, this could be causing the behavior.
c. To view the runtime events in the Siebel client version 7.5.x, navigate to the Site Map > Runtime Events Administration > Events. To view the runtime events in the Siebel client version 7.7, navigate to Site Map > Administration - Runtime Events > Events.
d. Review any Runtime events with a sequence number = -1 because these were created by a workflow process manager.
e. If the error was reported when creating a new record, look for any Events with the following values:
Event = WriteRecord or WriteRecordNew
Object Type = BusComp
Action Set Name = Workflow_<value>
f. Drilldown into the Action Set Name hyperlink to look for any Actions that reference the workflow process with the same ROW_ID as reported in the workflow process manager log file.
2. A user had a personalization rule in a ruleset that was not working correctly and causing the error. To help determine if you are encountering a behavior with the personalization rules, enable tracing to be generated in the Personalization log file. For more information on how to do this, refer to the following Siebel bookshelf references:
a. Siebel Bookshelf version 7.7 > Siebel Personalization Administration Guide > Testing Personalization Rules > Enabling Personalization Event Logging.
b. Siebel Bookshelf version 7.5 > Siebel Personalization Administration Guide > Testing > Using the Log File to Test Personalization Rules > Enabling Personalization Event Logging.
3. Customizations or scripting that is incorrectly configured could cause internal SQL statements to run and produce incorrect results and therefore return the above error. To help troubleshoot this further, you should enable SQL tracing. For the dedicated or mobile client, refer to Technical Note 91 and FAQ 1322. For the web client and application object manager component, refer to FAQ 2116. To trace scripting, refer to Technical Note 485 and Technical Note 552.
Corrective Action
Below are the corrective actions to try for the issues above:1. Once you have located the runtime event or action that is causing the behavior, do the following to resolve the behavior:
a. Delete this Action and or Runtime Event.
b. Select the menu option "Reload Personalization".
c. If the error still persists, try bouncing the Siebel Server Services
2. Use the Personalization log file to test the Personalization Rules. Once you have corrected any rules, make sure you reload the Personalization rules. For more information on how to do this, refer to the following Siebel bookshelf references:
a. Siebel Bookshelf version 7.7 > Siebel Personalization Administration Guide > Testing Personalization Rules > About Clearing and Reloading Siebel Personalization.
b. Siebel Bookshelf version 7.5 > Siebel Personalization Administration Guide > Testing > Clearing and Reloading Siebel Personalization.
3. Review the log files and look for the SQL statements that are executed prior to the error. Try to run these SQL statements directly against the database outside of the Siebel application. Below are some other suggestions:
a. If you are configuring a field that is to be used in generated SQL queries, you should set the Force Active and Immediate Post Changes properties to True in Siebel Tools. For more information about these properties, refer Siebel Bookshelf version 7.7 or 7.5 > Objects Type Reference > Siebel Object Types > Field.
b. Try inactivating the customizations you made to see if the error still reproduces.
c. If you are still unable to resolve this error, log a new service request and include all the log files that you have collected. Provide as much information about the configuration or scripting changes that you have made and a copy of the local developer's database and repository if applicable.
Applies to:
Error Message Area:Data Manager - DATVersion:Siebel 7.5.3
Purpose
This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-00472: Generic SSA NOTOK error message.
Scope
This document is informational and intended for any user.
SBL-DAT-00472: Generic SSA NOTOK error message.
Explanation
This is a generic Object Manager error. Below are some known causes for this error and you should confirm you are not encountering these behaviors:1. The error was reported because the user entered a new record into the Siebel application that fired a runtime event which itself tried to start a workflow process manager server task for a workflow process that no longer existed in the Siebel database. To help determine if you are encountering this behavior, try the following steps:
a. Follow the instructions in FAQ 1482 to enable events logging for the Workflow Process Manager Server component. Review the log file for any message similar to the following:
Cannot initiate process definition '1-E3I'. Verify that it does exist, has an 'Active' status, is activated and has not expired.
b. To determine if a workflow process exists in the database, run the following query (use the information obtained from the workflow process manager log file, in the above example, the ROW_ID = '1-E3I'):
SELECT * FROM S_WF_STEP WHERE ROW_ID = '1-E3I'
If a record is returned, confirm the workflow process is active and has not expired. If a record is not returned, this could be causing the behavior.
c. To view the runtime events in the Siebel client version 7.5.x, navigate to the Site Map > Runtime Events Administration > Events. To view the runtime events in the Siebel client version 7.7, navigate to Site Map > Administration - Runtime Events > Events.
d. Review any Runtime events with a sequence number = -1 because these were created by a workflow process manager.
e. If the error was reported when creating a new record, look for any Events with the following values:
Event = WriteRecord or WriteRecordNew
Object Type = BusComp
Action Set Name = Workflow_<value>
f. Drilldown into the Action Set Name hyperlink to look for any Actions that reference the workflow process with the same ROW_ID as reported in the workflow process manager log file.
2. A user had a personalization rule in a ruleset that was not working correctly and causing the error. To help determine if you are encountering a behavior with the personalization rules, enable tracing to be generated in the Personalization log file. For more information on how to do this, refer to the following Siebel bookshelf references:
a. Siebel Bookshelf version 7.7 > Siebel Personalization Administration Guide > Testing Personalization Rules > Enabling Personalization Event Logging.
b. Siebel Bookshelf version 7.5 > Siebel Personalization Administration Guide > Testing > Using the Log File to Test Personalization Rules > Enabling Personalization Event Logging.
3. Customizations or scripting that is incorrectly configured could cause internal SQL statements to run and produce incorrect results and therefore return the above error. To help troubleshoot this further, you should enable SQL tracing. For the dedicated or mobile client, refer to Technical Note 91 and FAQ 1322. For the web client and application object manager component, refer to FAQ 2116. To trace scripting, refer to Technical Note 485 and Technical Note 552.
Corrective Action
Below are the corrective actions to try for the issues above:1. Once you have located the runtime event or action that is causing the behavior, do the following to resolve the behavior:
a. Delete this Action and or Runtime Event.
b. Select the menu option "Reload Personalization".
c. If the error still persists, try bouncing the Siebel Server Services
2. Use the Personalization log file to test the Personalization Rules. Once you have corrected any rules, make sure you reload the Personalization rules. For more information on how to do this, refer to the following Siebel bookshelf references:
a. Siebel Bookshelf version 7.7 > Siebel Personalization Administration Guide > Testing Personalization Rules > About Clearing and Reloading Siebel Personalization.
b. Siebel Bookshelf version 7.5 > Siebel Personalization Administration Guide > Testing > Clearing and Reloading Siebel Personalization.
3. Review the log files and look for the SQL statements that are executed prior to the error. Try to run these SQL statements directly against the database outside of the Siebel application. Below are some other suggestions:
a. If you are configuring a field that is to be used in generated SQL queries, you should set the Force Active and Immediate Post Changes properties to True in Siebel Tools. For more information about these properties, refer Siebel Bookshelf version 7.7 or 7.5 > Objects Type Reference > Siebel Object Types > Field.
b. Try inactivating the customizations you made to see if the error still reproduces.
c. If you are still unable to resolve this error, log a new service request and include all the log files that you have collected. Provide as much information about the configuration or scripting changes that you have made and a copy of the local developer's database and repository if applicable.
Applies to:
Siebel Tools - Version: 8.0 SIA [20405] - Release: V8IBM AIX on POWER Systems (64-bit)
Database: IBM DB2 8.2
Application Server OS: IBM AIX 5L 5.3
Database Server OS: IBM AIX 5L 5.2 ML6
This document was previously published as Siebel SR 38-3364724871.
Symptoms
Customer has upgraded from Siebel 7.0.5 to 8.0.
While running a workflow in
simulator using tools, receiving the following error in one step:
Error Code:
(SBL-BPR-00162)--(SBL-DAT-00472)
Error Desc:
Error invoking service 'EAI Siebel
Adapter', method 'QueryPage' at step 'Create Integration Object'.(SBL-BPR-00162)
--
Method
'FieldValue' of business component 'Action' (integration component 'Action') returned the
following error:
"Generic SSA NOTOK error message.(SBL-DAT-00472)"(SBL-EAI-04376)
On validating the workflow there were no errors reported.
Cause
This behavior was observed after an upgrade from version 7.0.5 to version 8.0 and was in fact not a Workflow issue. It was related to custom calculated fields and a data type mismatch. By exposing these fields in the UI and performing queries on them they were able to reproduce the same behavior, namely the error SBL-DAT-00472.This behavior has been reproduced using a standard Siebel environment 8.0. Here are the steps:
1. Add new calculated field in BC 'Action' with this calculated value:
IIf ([Description] = 1, 10, 0)
NOTE: Field 'Description' is a DTYPE_TEXT field. It is compared to a number.
2. Expose this calculated field on applet 'Activity List Applet With Navigation'.
3. Recompile the BC and applet.
4. Go to "My Activities" view
> The calculated field is empty where it should display 10 or 0
5. Query on this field:
> the error below occurs:
Generic SSA NOTOK error message.(SBL-DAT-00472)
- - -
This behavior is specific to version 8.0. It is not reproducible with lower versions. Bug 12-1JUH939 has been logged to address this unexpected behavior.
Solution
1. Change the calculated value to:
- -
IIf ([Description] = "1", 10, 0)
- -
NOTE: Now the field 'Description' is compared to a string.
2. Recompile the BC.
3. Go to "My Activities" view:
> The field displays 10 or 0 as expected
4. Query on it:
> No error occurs
To summarize: The issue occurs when the IIf function is used to test the value of a field and the data type of this field is not the same as the data type of the comparison value. More precisely, it is when the field is compared to a number whereas it returns a string.
References
BUG:12-1JUH939 - ERROR SBL-DAT-00472 WHEN QUERYING A CALCULATED FIELD THAT COMPARES A TEXT FIELD TO A NUMBERApplies to:
Siebel Tools - Version: 7.7.2.3 [18361]z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.7.2.3 [18361]
Database: Oracle 9.2.0.3
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Sun Solaris 8
This document was previously published as Siebel SR 38-3041242651.
Symptoms
SBL-DAT-00472Hello Support,
On The "Contact Form Applet" we added two fields from
S_CONTACT_X
ATTRIB_03
ATTRIB_04
The first time I update One of those fields, I can
do it perfectly
When I try to update the second field (order is of no importance which field
was filled out first), I get the error message: "Generic SSA NOTOK error message
(SBL-DAT-00472)"
via FAQ 1482 I set the logging and found the following in the
logfile.
ObjMgrBusCompLog Warning 2 0 2006-05-17
08:40:00 Field "S_CONTACT_X.Mod Id" is not activated in BusComp
"Contact".
ObjMgrBusCompLog Error 1 0 2006-05-17
08:40:00 Field "S_CONTACT_X.Mod Id" is not activated in BusComp "Contact"
for
update.
ObjMgrBusCompLog Error 1 0 2006-05-17
08:40:00 (sqlobj.cpp (9393)) SBL-DAT-00472: Algemeen SSA
NOTOK-foutbericht.
However, I didn't find any field "Mod Id" on the BC
Contact.
I found field "X Mod Id" on BC Contact ->
S_CONTACT_X MODIFICATION_NUM which was read only, I set it off, but after
compiling, I still got the same error.
How can I Activate the field "Mod Id" on BC
Contact?
thanks for your help
Cause
A join from S_CONTACT to S_CONTACT_X which wasn't necessary in order to be able to access the S_CONTACT_X column was active which was causing the issue.Solution
Technical Support advised customer to search on "Mod Id" in tools to find out where it is defined as follows:
a) In Siebel Tools, from the Application Level Menu, select Tools > Search Repository;
b) In the Search Value box, enter Mod Id
c) You can perform a full search (All Types selected) in order to ensure that this column Mod Id is not being used in your Application.
d) If the search results did return any matches, then you will be able to inspect when this column is being used, identifying possible reason for the message displayed in the log file
Once customer made a search on "Mod Id" in their environment, he found out that a join from S_CONTACT to S_CONTACT_X which wasn't necessary in order to be able to access the S_CONTACT_X column was active. Once he inactivated the join between them, he could do the necessary updates.
Siebel Technical Support
Applies to:
Siebel Tools - Version: 7.5.3.12 [16272]z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3.12 [16272]
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: Microsoft Windows 2000 Server SP 3
This document was previously published as Siebel SR 38-2717425431.
Symptoms
SBL-DAT-00472Hello,
I am writing a B.C -> Field -> Field User Prop for a required field in the Activity Plan Action B.C. The ‘Value’ field in the Field User Property is limited to 255 characters.
For Example:
Name = ‘Required’
Value = ‘IIf (([Type] = 'Site Location Services' or [Type] = 'Event' or [Type] = 'Media' or [Type] = 'Foreign Office' or [Type] = 'Service' or [Type] = 'Conversion' or [Type] = 'Visit' or [Type] = 'Investment' or [Type] = 'Application Process' or [Type] = 'Policy Research'), 'Y', 'N')’
How can I populate the Value field with condition which whose length is greater than 255?
I appreciate your help.
Cause
questionSolution
Message 1
I think you should be able to split the expression into two new calculated fields and use them in the expression of the Required field user property.For example to split this expression to enable adding other clauses:
IIf ([First Name] = "Richard" or [First Name] = "John" or [First Name] = "Frazer" or [First Name] = "James" or [First Name] = "Jerry" or [First Name] = "Paul" or [First Name] = "Mickey" or [First Name] = "Simon" or [First Name] = "Peter","Y","N")
Create two new calculated fields in the buscomp with following expressions:
Name= Calc Required 1
IIf ([First Name] = "Richard" or [First Name] = "John" or [First Name] = "Frazer" or [First Name] = "James" or [First Name] = "Jerry" or [First Name] = "Paul","Y","N")
Calc Required 2
IIf ( [First Name] = "Mickey" or [First Name] = "Simon" or [First Name] = "Peter" or [First Name] = "Anthony" or [First Name] = "Andrew","Y","N")
Then change expression of the Required user property to:
IIf ([Calc Required 1] = "Y" or [Calc Required 2] = "Y","Y","N")
Applies to:
Siebel Tools - Version: 7.7.2.4 [18365] - Release: V7IBM AIX on POWER Systems (64-bit)
Product Release: V7 (Professional)
Version: 7.7.2.4 [18365] FRA
Database: Oracle 9.2.0.4
Application Server OS: IBM AIX 5L 5.2
Database Server OS: IBM AIX 5L 5.2
This document was previously published as Siebel SR 38-3259074183.
""Checked for Relevance on 26-Mar-2010""
Symptoms
We are currently experiencing an error message:- - -
Generic SSA NOTOK error message.(SBL-DAT-00472)
- - -
when we try to save or update a record on a view based on the 'Service Agreement' BC.
The applet we are using use fields mapped on columns from an extension table that we created by using wizard. We are able to save some fields but we get an error message when we try to update them or enter new data in the field.
Solution
The BC 'Service Agreement' is based on table S_DOC_AGREE and the custom table named CX_S_DOC_AGRE_X was a 1:1 extension table for base table S_DOC_AGREE.In the BC the customer had created a new join to this custom table and some fields based on this join. However since CX_S_DOC_AGRE_X was a 1:1 extension table for the BC's base table an implicit join to CX_S_DOC_AGRE_X existed already in the BC. There was therefore no need to create an explicit join.
This matter is discussed in the Bookshelf:
Configuring Siebel eBusiness Applications
Configuring Tables and Columns
About Extension Tables
About Implicit Joins
and also in Note 475503.1.
The issue was resolved once the explicit join to CX_S_DOC_AGRE_X table was deleted.
No comments:
Post a Comment