Error Message: File could not be created as the directory specified for the file creation is not valid (SBL-EAI-50228) Error Description: There are several reasons behind this Siebel Open UI error. Few common scenarios where you may face this error message: – When Siebel workflow is trying to create or access file outside Siebel file system – When EIM / Batch Jobs is trying to update or access files – When you try to download or save file from Siebel tools (for example ‘Generate WSDL’ button that generates WSDL file from Siebel tools) Reason: In Siebel Open UI, Oracle has set restriction on downloading files from Siebel application. Now we can not download file on any folder as per our choice. Siebel can access only those folders if their folder paths are set as parameter value of ‘EAI File Transport Folder List’. To check the parameter value, go to Admin-Server configuration > Components and query for the parameter ‘EAI File Transport Folder List’.
Solution: Perform below steps to fix this issue 1) Find out the folder location which one is referred by workflow or Job (For example: D:Log of the system ‘TESTENV’) 2) Locate the folder and share it with everyone or specific ids 3) Go to Administration-Server configuration > Components, query for the parameter ‘EAI File Transport Folder List’ and add the folder path under the column ‘Value on Restart’ (For example: \TESTENVLog). You can add more than one folder location using ‘;’ between two. 4) Restart the component and check new value is displayed under ‘Value’ column or not Now you try to access the folder path from Siebel, you should not see this message again. If you face any challenges, please let us know. For more updates on recent activities, follow ‘TechOneStop‘ on Facebook/Twitter/LinkedIn or Join our website as Follower. Error: SBL-EAI-04262 >>
So lets start our Siebel Open UI training with a question – what is Siebel Open UI?
Siebel Open UI is a browser client for Siebel desktop and mobile application. To open prior version of Siebel Open UI application, you must have Internet Explorer installed in your system. But as per latest browser trends (Nov 2014-Nov 2015) done by StatCounter, Google Chrome has the largest market share (almost 50%) followed by IE and Firefox. So to give browser flexibility to users, Oracle introduces Siebel Open UI. Siebel Open UI is browser and device independent Siebel client. It does not use ActiveX control. Also it has highly optimized and smart UI for mobile devices.
Siebel Open UI Benefits:
1. Improved User Interface
2. Device and Platform Independent
Siebel Open UI has the capability to adjust screen length dynamically for different devices like tablets or smartphones. It has out of box integration with mobile functions like GPS, Email, Calendar sync, Calls, Multi touch gesturing.
4. Shorter Development Cycle
All these enhanced features help developers to customize application quickly and more efficiently.
With Innovation Pack 2013, Oraclehas introduced Incremental Repository Merge that accelerates repository upgradation process without going through major upgrade project.
Siebel Open UI comes with many built in features like
escape key to undo
disable right click to increase user experience
less use of horizontal scrollbar
supports GPS, Google Maps, Email
6. Support custom theme
By default open UI comes with two themes – Tabbed and Tree (Accordion). You can add custom theme or modify out of box themes as per requirement. Users can choose their favorite theme from Tools > User Preference.
So don’t get surprise if your boring Siebel application looks like Facebook from tomorrow! We will discuss about Siebel Open UI theme in later module.
Beside Siebel Open UI benefits, there are few limitations as well.
It does not support automatic logout on closing the browser
It does not do implicit commit on browser back button click
It does not allow to edit attachment content on the fly. Users have to download the file, update, save and upload the modified file again.
It does not support Standard Interactivity(SI) applet. Wherever SI Applet comes in the application, you will see a message box ‘Why can’t I see this applet‘.
To enable Siebel Open UI, parameters ‘EnableOpenUI‘ and ‘HighInteractivity‘ must be set to ‘True‘.
If you are using Web client, follow below steps to verify parameters’ values:
Login into Siebel application as an Administrator
Navigate to Application-Server Configuration and select the server on Servers view
Query for the Application Object Manager (AOM) component on Component view for which you want to enable Open UI mode
EnableOpenUI = TRUE
HighInteractivity = TRUE
In the Component Parameter view tab, query below two parameters and update values as ‘TRUE‘
Logout from the application and restart Siebel Server
For dedicated client, add these two parameters in the client cfg file.
‘Why can’t I see this applet? Open UI cannot display this type of applet. Contact your system administrator’
Cause: Siebel Open UI does not support any Standard Interactivity applet. So, in application wherever Standard Interactivity Applet comes, Siebel Open UI will display this message. Now how to decide that the applet is standard interactivity or high interactivity? If any of the below criteria are met, then the applet is standard interactivity type
• Applet is not based upon any business component • Class of the applet is either based upon or derived from a class that implements base functionality of Standard Interactivity • Applet with user property: High Interactivity Enabled = N • Associated class of the applet has “High Interactivity” set to 1 • Product catalog style layout
1) Remove the applet from the view Best way to remove this type applet from view is by using of Personalization rules. Go to Administration-Personalization > Applet and create a new rule that will always be false. You can write the rule based upon users responsibility that will never match or based upon users positions. Also you can remove the applet from view itself in Siebel tools.
2) Rebuild the applet Create a new applet with same functionality based upon high interactivity class/BC
You will see the message ‘Why can’t I see this applet? ‘ on Siebel Open UI home page also where welcome username appears in Siebel HI application. We can display this welcome username message in Siebel Open UI also. To know more, read ‘Welcome Username is not displaying on Home Page of Siebel Open UI’. If you have any doubt or question, please write us. To get more updates on recent activities, follow ‘TechOneStop’ on Facebook/Twitter/LinkedIn or join our website as follower.
Error: ORA-00942: table or view does not exist Reason: This error occurs when new table/view exists in logical schema (Siebel repository) but not present in physical database Error: ORA-00904: “Field Name”: invalid identifier Reason: This is also because of mismatch between logical schema and physical database How to resolve: To fix both issues, we have to sync physical database with Siebel repository. To do so, Siebel provides DDL Sync utility. DDLsync utility compares the logical schema (schema definition in Siebel repository) with physical schema (physical table/column definitions in database) and applies all differential changes on Physical schema so that both are in sync. But there are exceptional cases as well. 1. Custom column that is in physical schema but not in Siebel repository (logical schema) will not be deleted 2. Custom index that is in physical schema but not in Siebel repository (logical schema) will not be deleted After running DDL Sync utility, if you still face the issue, please let us know. We will try our best to fix it. If you have any other issue, please share with us. To get more updates on recent activities, follow ‘TechOneStop‘ on Facebook/Twitter/LinkedIn or join our website as followers.
Incremental Repository Merge is the new feature that has been introduced from Siebel 188.8.131.52 onward. It makes the Siebel repository upgradation process faster and easier without going through major upgrade project. Recently we have performed IRM for one of our clients. During the process, we have faced many errors/issues. Here we have discussed few major, frequently occurred errors during IRM. Error Message: Importing file “D:Siebel8.1Tools_1tempIRM_PRIOR_CUST.dat”.22001: [DataDirect][ODBC Oracle driver][Oracle]ORA-12899: value too large for column “SIEBEL”.”S_ACCELERATOR”.”INACTIVE_FLG” (actual: 4, maximum: 1) Reason n Solutions: This error comes up because of incorrect registry settings on ODBC data source. To fix this issue, follow below steps: Step 1: Start the Microsoft ODBC Administrator Step 2:On the ODBC Data Source Administrator dialog box, select System DSN tab and copy the DSN name Step 3: In Windows registry, locate following registry entry [HKEY_LOCAL_MACHINESOFTWAREODBCODBC.INISiebel_DSN_Name] Step 4: Verify following registry keys are set properly or not. These keys are required in order for the ODBC driver to behave correctly. If keys are not present, then add new key like below PacketSize = 0 EnableScrollableCursors=0 ColumnsAsChar=1 ColumnSizeAsCharacter=1
Error Message: ERROR::SBL-DEV-62155: CommitCopyInstance EXITING with error – The same values for ‘Column Name’ already exist Reason n Solutions: This error comes up when the database is not running in binary sort order mode. During Incremental Repository Merge, it is mandatory to set the parameter NLS_SORT to BINARY which helps database to in Binary mode.
Error Message: ERROR::c: MAP ENTRY with same id exists
ERROR::BUT strNamePath and ParentId are different
ERROR::SBL-DEV-62252: Could not create HASH entry
ERROR::Type – Workflow Process, strNamePath – eMail Response – Create Activity: 0 Reason n Solutions: This behavior typically occurs when an object already exists in the New Customer Repository but the workflow process which is trying to insert, has a different set of attributes. This is due to one particular workflow, could be ignored. Error Message: ERROR::SBL-DEV-62111: NON-REQUIRED FKey not found in ‘New Standard Repository’
ERROR::Type – WF Branch Connector, strNamePath – ABO Bulk Request – ApplyProductPromotion Reason n Solutions: This is because of one/more non-required foreign keys from the ‘Prior Customer Repository’ are not present in the workflow definition and that’s why the particular workflow object was inserted into the ‘New Customer Repository’ with a NULL value during IRM process. This is also one of those generic errors which can be ignored.
Error Message: ERROR::SBL-DEV-62155: CommitCopyInstance EXITING with error – 1-3ZGTMC.
ERROR::SBL-DEV-62194: INSERTION FAILED. Type View, NamePath – SWLS Technician Breaks View
ERROR::SBL-DEV-62194: INSERTION FAILED. Type Applet, NamePath – SWLS Technician Breaks Display Applet Reason n Solutions: This error occurs when a new Siebel object is added to the standard Siebel repository but it has the same key details as a custom object that already exists in the ‘Prior Customer Repository’. This error also can be ignored.
Error Message: Failure: 161782 rows of EIM_EMPLOYEE had NULL in STATUS_CD Reason n Solutions: This error comes up when IRM process tries to populate siebel base table using interface tables. So before staring IRM process, clear all interface tables from siebel database (part of siebel best practice during repository merge or upgrade) to avoid this error. Error Message: ERROR::SBL-DEV-62102: -> aborted with error: The same values for ‘Sequence’ already exist. Reason n Solutions: When repository merge process starts to re-sequence objects automatically, this error may occur. It is an acceptable error message which doesn’t need any fix, can be ignored.
Error Message: ORA-00942: table or view does not exist Reason n Solutions: This error occurs when table/view definition exists in logical schema but not in physical schema. So run DDL sync utility to create new tables/views in physical database. Error Message: ORA-00904: “JOB_TYPE_CD”: invalid identifier Reason n Solutions: This is also because of mismatch between Siebel physical database and logical database. Here also we just need to run DDL Sync utility to sync both databases.
These are few major issues/errors that we generally face during Siebel Incremental Repository Merge in Siebel. If you have faced any other issue, please let us know. We will try our best to help you. To get more updates on recent activities, follow ‘TechOneStop‘ on Facebook/Twitter/LinkedIn or join our website as followers. Check our Youtube videos on Siebel Open UI training, you will like it.
‘Your version of the Siebel High Interactivity Framework for IE, required for use of this Siebel application, may not be current’ – this is one of the most common errors during Siebel application launch on Internet Explorer browser but good thing is that we can fix this error quite easily.
Steps to fix Siebel High Interactivity Framework for IE issue:
Navigate to browser settings > Internet Options and click on Security tab
Under the Security tab, click on ‘Trusted Sites‘ and add Siebel URL to the trusted zone Example: If the Siebel application URL looks like ‘http://localhost:8080/sales_enu’, then you just add ‘http://localhost:8080’ in the trusted site zone. Also you make sure that the checkbox for ‘Require server verification (https:) for all site in this zone’ is unchecked.
On the Security screen only, click on ‘Custom Level‘ button and verify properties like ActiveX control are enabled.
Now save all browser settings, close the browser and relaunch Siebel application. This should fix Siebel High Interactivity Framework issue.
Do you still see the same error?
Well! then you need to perform few more extra steps to launch Siebel application successfully. Sometimes the ActiveX file of Siebel high interactivity framework becomes corrupted or damaged. So you need to delete the damaged ActiveX file and download a fresh copy of ‘Siebel High Interactivity Framework’.
Extra steps to fix Siebel High Interactivity Framework for IE issue:
Navigate to browser settings > Internet Options > General and then click on ‘Settings‘ button available under ‘Browsing history’ section
On the ‘Website Data Settings’ pop up window, click on ‘View objects’ button under ‘Temporary Internet Files’ tab. It will display all downloaded program files with statuses. If you see only one file ‘Siebel High Interactivity Framework’ with ‘Damaged’ status, then just delete the file. But if there is more than one copy of ‘Siebel High Interactivity Framework’ file, then you right click on each file and change the status to ‘Damaged’ and delete.
Remember, you can only change the status of the file if you have admin rights, otherwise ask your system administrator to do it.
Then close the browser, open Siebel application and you will get a pop up asking to download a fresh copy of ActiveX file.
Still no luck!! Same message appears again and again! Please feel free to comment here and we will try to help you further.
Keep in touch, follow TechOneStop on Facebook / Twitter / LinkedIn / Goolge+.