Generic Ssa Not Ok 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, as

Sbl-bpr-00119

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 check field l

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 Security Siebel Storage UNIX Visual Basic Web Design and Development Windows < Back 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 bluesguyAZ59 COMPANIES HP, Voltage Security and ... Hitachi America, LTD Arbor Networks, Inc. Quest Software View All Topics View All Members View All http://howtosiebel.blogspot.com/2016/05/guide-to-resolve-generic-ssa-notok.html Companies Toolbox for IT Topics Siebel Groups Ask a New Question Siebel Development The Siebel Development group is a forum where peers share technical expertise, solve problems, and discuss issues related to Siebel development. Home | Invite Peers | More Siebel Groups Your account is ready. You're now being signed in. Solve problems - It's Free Create your account in seconds E-mail address is taken If this is your account,sign in here Email address http://siebel.ittoolbox.com/groups/technical-functional/siebel-dev-l/generic-ssa-notok-error-message-when-click-book-appointment-in-siebel-78213-3309179 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 when click Book Appointment in Siebel 7.8.2.13 Ridwan Sugianto asked Feb 16, 2010 | Replies (2) hi, we're using siebel scheduling and siebel field service, our requirement is to block the activity of user within the working hour so service request will not be assigned during blocking hour. When we try to do book appointment in Acitivity View we got an error, the condition is : 1. Service Region, Early Start Time, and Start Time already define Uncheck Lock Assignment. The error message is occured when we try to click book appointment Error message is : Generic SSA NOTOK Error Message When we look through the log, we found that: SrmRouting SrmRoutingSubevent 4 0 2010-02-12 20:26:46 SNDREQ IDS : FLAGS [1] : REQID [] : SRBSESSID [979b46903ceSIEBSS_DEV_1] : SRMCONNID [10] SRC : SRC_ID [0-1] : SRC_KEY [] DEST : ROUTE_ID [AsgnSrvr] : ROUTE_KEY [All AM Rule Set] : ROUTE_SRVR [] : LANG_CODE [ENU] :

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();          http://siebelunleashed.com/generic-ssa-notok-error-messagesbl-dat-00472/ 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 generic ssa reason 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 generic ssa not error due 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,342 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