Home > generic ssa > generic ssa notok error message.sbl-dat-00472

Generic Ssa Notok Error Message.sbl-dat-00472

fundamental configuration mistake, like syntax errors or missing workflows or incorrect joins are configured. This error can be very difficult to fix, sbl-bpr-00119 as it leaves very thin trace behind and there is no indication (sbl-bpr-00162)--(sbl-dat-00472) 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

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 for this error OrderType = GetFieldValue(“Oppty Order Type”); http://howtosiebel.blogspot.com/2016/05/guide-to-resolve-generic-ssa-notok.html 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 to Configuration problem There is an error in the field or the join. http://siebelunleashed.com/generic-ssa-notok-error-messagesbl-dat-00472/ 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,340 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 give fair bit of idea… Reply Piyush says: December 8, 2008 at 9:49 pm I think this error occurs, when For join fields, there is already prese

Technology and Trends Enterprise Architecture and EAI ERP Hardware IT Management and Strategy Java Knowledge Management Linux Networking Oracle PeopleSoft Project and Portfolio Management SAP SCM http://siebel.ittoolbox.com/groups/technical-functional/siebel-analytics-l/generic-ssa-notok-error-message-20316 Security Siebel Storage UNIX Visual Basic Web Design and Development Windows < Back http://howtosiebel.blogspot.com.metacomment.io/2016/05/guide-to-resolve-generic-ssa-notok.html CHOOSE A DISCUSSION GROUP Research Directory TOPICS Database Hardware Networking SAP Security Web Design MEMBERS Paul_Pedant DACREE MarkDeVries MacProTX Inside-ERP VoIP_News Inside-CRM I_am_the_dragon maxwellarnold Michael Meyers-Jouan TerryCurran Chris_Day Andrew.S.Baker Ramnath.Awate JoeTorre Locutus bracke Dennis Stevenson PCMag Craig Borysowich DukeGanote Richard mircea_luca iudithm Nikki Klein Clinton Jones AbhaiTripathi knowscognosdoi Iqbalyk generic ssa bluesguyAZ59 COMPANIES HP, Voltage Security and ... Hitachi America, LTD Arbor Networks, Inc. Quest Software View All Topics View All Members View All Companies Toolbox for IT Topics Siebel Groups Ask a New Question Siebel Analytics For discussion on Siebel Analytics , please visit the Oracle BI group. More Siebel Groups Your account is ready. You're now being signed in. Solve problems - generic ssa notok It's Free Create your account in seconds E-mail address is taken If this is your account,sign in here Email address Username Between 5 and 30 characters. No spaces please The Profile Name is already in use Password Notify me of new activity in this group: Real Time Daily Never Keep me informed of the latest: White Papers Newsletter Jobs By clicking "Join Now", you agree to Toolbox for Technology terms of use, and have read and understand our privacy policy. Generic SSA NOTOK error message. Unknown User asked Jul 10, 2000 | Replies (1) ITtoolbox Portal for CRM - http://CRM.ITtoolbox.com hi, while configuring a business component i added an mvg applet for position and performed a data validation for a field as well as set a search specification for the business component.everything was working ok yesterday but today when i opened the relevant screen i am getting the following error"Generic SSA NOTOK error message." can anybody throw light on the possible reasons for this error. Thanx Join this group Popular White Paper On This Topic The Death of Traditional Data Integration: How the Changing Natur

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 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 WorkflowsRuntime 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 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 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 o

 

Related content

generic ssa notok error

Generic Ssa Notok Error p fundamental configuration mistake like syntax errors or missing workflows or incorrect joins are configured This error can be very difficult relatedl to fix as it leaves very thin trace behind sbl-bpr- and there is no indication to start with When I faced this error sbl-bpr- -- sbl-dat- 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 Deleted Workflows Runtime events that are created automatically by workflow deployment have row

generic ssa notok error message siebel

Generic Ssa Notok Error Message Siebel p 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 relatedl indication to start with When I faced this error I narrowed it sbl-bpr- down by going through the most common reasons of this error and started to rule them sbl-bpr- -- sbl-dat- out one by one Following is the list which I followed from various support web articles Deleted Workflows Runtime events that are created automatically by workflow deployment

generic ssa notok error message

Generic Ssa Notok Error Message table id toc tbody tr td div id toctitle Contents div ul li a href sbl-bpr- -- sbl-dat- a li ul td tr tbody table p or search for a resolution mostly from Oracle Support IT Toolbox Siebel relatedl Unleashed etc I have tried to search for all sbl-bpr- the solutions for a particular error code in all the mentioned sites p h id sbl-bpr- -- sbl-dat- p and put all the solutions in this site Search This Blog SBL-DAT- Generic SSA NOTOK error message Applies to Siebel Tools - Version to - Release V

generic ssa not ok error message.sbl-dat-00472

Generic Ssa Not Ok Error Message sbl-dat- table id toc tbody tr td div id toctitle Contents div ul li a href Sbl-bpr- a li ul td tr tbody table p fundamental configuration mistake like syntax errors or missing workflows or incorrect joins are configured relatedl This error can be very difficult to fix as p h id Sbl-bpr- p it leaves very thin trace behind and there is no indication sbl-bpr- -- sbl-dat- 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

generic ssa notok error message sbl dat 00472 siebel

Generic Ssa Notok Error Message Sbl Dat Siebel p or search for a resolution mostly from Oracle Support IT Toolbox Siebel Unleashed etc I have relatedl tried to search for all the solutions for a particular sbl-bpr- error code in all the mentioned sites and put all the solutions in sbl-bpr- -- sbl-dat- this site Search This Blog SBL-DAT- Generic SSA NOTOK error message Applies to Siebel Tools - Version to - Release V to V Information in this document applies to any platform Error Message Area Data Manager - DAT Version Siebel Purpose This document is intended to provide