Generic Ssa Notok Error Message Sbl Dat 00472 Siebel

or search for a resolution mostly from Oracle Support, IT Toolbox, Siebel Unleashed etc. I have tried to search for all the solutions for a particular sbl-bpr-00119 error code in all the mentioned sites and put all the solutions in (sbl-bpr-00162)--(sbl-dat-00472) this site. Search This Blog SBL-DAT-00472: Generic SSA NOTOK error message 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. ExplanationThis 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 - R

the script. The Script was something like var AgreeBO = TheApplication().GetBusObject(“Service Agreement”); var AgreeBC = AgreeBO.GetBusComp(“Service Agreement”); var OrderType = “”;   with(AgreeBC)       {          ActivateField(“Oppty Order Type”)          ClearToQuery();          SetViewMode(3);          SetSearchSpec("Id",AgreeId);          ExecuteQuery();          if(FirstRecord())          {             OrderType = GetFieldValue(“Oppty Order Type”);        } AgreeBO = null; AgreeBC = null; There is nothing unusual in the Script but when I executed this script I got the following error Generic SSA NOTOK error message.(SBL-DAT-00472) Now after a bit of playing with the code I came to know that following line of code was the reason http://www.error-codes.info/2010/12/sbl-dat-00472-generic-ssa-notok-error.html for this error OrderType = GetFieldValue(“Oppty Order Type”); This Field “Oppty Order Type” was a joined field from Opportunity. The join was not new it was an old join and there are several fields that were being pulled from this join. I am yet to do the RCA (Root Cause Analysis) of this error but the following things are quite clear It was an error due http://siebelunleashed.com/generic-ssa-notok-error-messagesbl-dat-00472/ to Configuration problem There is an error in the field or the join. I haven’t tried various alternatives like deleting the field and recreating it again. What I did was not to use this field but to use the actual field in Opportunity BC. But will keep you posted whatever I find out. And in case if any of you have faced this kind of error before. Please share with us all. Happy Reading 🙂 Share:PrintEmailTweeteScript, Problem Solutions eScript, Problem Solutions← COMCreateObject – Opening an EXE File.Siebel Workflow Process an Introduction → This Post has been viewed : 20,345 Times Visitors to this post, also read:Client Side Business Service- Siebel Open UISiebel 7.8 Signals - A Case Study!How to create Hierarchical Picklist?Open UI - IP 2014 finally - component version…Debugging Workflow – A case studyCOMCreateObject – Opening an EXE File.EAI Data Maps - making Siebel Integration simple 7 Responses to Generic SSA NOTOK error message.(SBL-DAT-00472) Piyush says: December 9, 2008 at 3:49 am I think this error occurs, when For join fields, there is already present the inner join, but duing configuration we have created new join and implement the same. I hope this will giv

NOTOK Error in SiebelThis error occurs in Siebel when there is some fundamental configuration mistake, like syntax errors or missing workflows or incorrect joins are configured. This error can be very difficult to fix, as it http://howtosiebel.blogspot.com.metacomment.io/2016/05/guide-to-resolve-generic-ssa-notok.html leaves very thin trace behind and there is no indication to start with. When I faced this error I narrowed it down by going through the most common reasons of this error and started http://howtosiebel.blogspot.co.at/search?updated-max=2016-06-01T02:55:00-07:00&max-results=3&reverse-paginate=true to rule them out one by one.Following is the list which I followed from various support web articles.1. Deleted WorkflowsRuntime events that are created automatically by workflow deployment have row id of workflow generic ssa specified on them, and if that workflow does not exist in system then run time event can throw this error. To debug this turn on the personalisation logs and narrow down which runtime event is causing the trouble.2. Explicit Joins on 1:1 tablesSomeone has c... 1 Comments Go to page leave a comment Comments vijay kona 2016-05-25 22:20:29 0 very useful info..Thanks Alex!! Ads Your Comment Login to generic ssa notok leave a comment Google Facebook Twitter See also How to send error information How to send error information How to send error information Last Updated: Apr 05, 2016 06:19AM PDT S... How to guide 2015/16 Search for: How to guide 2015/16 DISCLAIMER: Please note that this website is for educational purpos... Error Message: I created a post about this yesterday but I focused too much on how this error only happens when pla... [SR-1394] Implement SE-0061 - Add Generic Result and Error Handling to autoreleasepool() - Swift Timothy Wood added a comment - 3 May 2016 3:44 PM Closing as duplicate. Timothy Wood added a commen... How to Resolve 404 Not Found Problems Articles How to Resolve 404 Not Found Problems 404 Not Found issues can be a common windows error wh... How to write a great error message Imagine being in an office. In your cubicle. You’ve worked long hours this week for an upcoming prod... Welcome to SSA Best | SSA Best No front page content has been created yet. Welcome to the Benefit Eligibility Screening Tool (BEST)... How To Fix Home Error?   What is Home error? The Home error is the Hexadecimal format of the error caused. Th

fundamental configuration mistake, like syntax errors or missing workflows or incorrect joins are configured. This error can be very difficult to fix, as it leaves very thin trace behind and there is no indication to start with. When I faced this error I narrowed it down by going through the most common reasons of this error and started to rule them out one by one. Following is the list which I followed from various support web articles. 1. Deleted Workflows Runtime events that are created automatically by workflow deployment have row id of workflow specified on them, and if that workflow does not exist in system then run time event can throw this error. To debug this turn on the personalisation logs and narrow down which runtime event is causing the trouble. 2. Explicit Joins on 1:1 tables Someone has created explicit join based on 1:1 extention table and name of the join is same as the table name. For example table S_SRV_REQ1_FNX is extension table of S_SRV_REQ, so one should not create join in Service request BC with table S_SRV_REQ1_FNX to avoid getting this error. 3. Calculated Fields This is the most common cause of this error. Any syntax mistake in calculation or calculation which compares a two different data types can result into SSA NOTOK Error. For example following calculation will cause this error : IIf ([Status] = 1, 10, 0) This because the status field is DTYPE_TEXT and it is compared to integer value. In my case I had a field in BC with syntactically incorrect calculation. Which was easy to find as it popped up as first thing in BC validation. 4. BC field Validations This is another place where calculated fields can be referred and could cause this error. This might not error out every time as calculation might not be evaluated in all conditions. So do check field level validations as well when trying to fix this issue. 5. Run-time events or DVMs Another place I would look for would be RTE and DVMs as they also use Siebel query language to identify records and validate things and any syntax goof up can cause this error to popup. Another place you might get this error is while generating sample XML for BIP reports, this happens because application is not able to find the folder location specified in component parameter for XMLPReportDataDir . Please feel free to share and discuss your experiences with this error in comments below. Labels: SBL-DAT-XXXXX Siebel Errors No comments : Email This BlogThis! Share to Twitter Share to Facebook Share to Pinterest April 29, 2016 7 Siebel Tools hacks every developer should know! These a