Siebel Tools - Version: 8.0 SIA [20405] and later [Release: V8 and later ]
Information in this document applies to any platform.
Symptoms
The customer is using Siebel Find only and no Search functionality. The standard configuration shows these two dropdown items:
File System
Smart Answer
The customer would like to remove the Search File System Lookin dropdown item and the Smart Answer Lookin dropdown item.
The following steps will remove these dropdown items as documented in the following document.
Disabling "File System" & "Smart Answer" from the "Look In" drop-down list (Doc ID 560274.1)
To remove the “Smart Answer” from the “Look-In” drop down list, please try the following steps.
1.) Login to the Application
2.) Go to Administration – Data > List of Values
3.) Search for Type “SEARCH_SMART_ANSWER”
4.) Disable the LOV by setting the Active flag to FALSE.
5.) Logout and login again
To remove the “File System” from the “Look-In” drop down list, please try the following steps.
1.) Login to the Application
2.) Go to "Search Definition Categories View", set the "Default flg" of the "Search Definition" that is usedby the application.
Site Map > Administration - Search > Search Definition
3.) Go to "Search Indices Admin View.
Site Map > Administration - Search > Search Index Settings
4.) Delete the record with Name = “Common Files” and Data Source = “File System”.
But the customer could not get to the Search Administration view 'Search Index Setting'. That failed with this error.
Error getting XML from file 'CHANGE_ME (Ex: \\searchserver\shared\SSC_Field-Mappings.xml)'. (SBL-EAI-04261) The cause of this error when navigating to the Search Index Settings view is because the search set up is incomplete.
Cause
If you set the Search Administration Search Engine Settings FileName parameter for the default Search Engine to the correct FieldMappings.xml file, then the view will work. Use the SIA_SSC_Field-Mappings.xml or SSC_Field-Mappings.xml in the Bin directories in the dedicated web client and the siebsrvr directories.
Change request 12-1PBVE8B was raised as a product defect to note that if you do not have the Search Setup complete, you cannot get to the Search Index Settings view to remove the File System Search Lookin Dropdown item. This is a common request especially for customers who do not use Search.
Change request 12-1PBVE95 is an enhancement request asking for a consistent way to control the Search Lookin dropdown items.
Currently, there are three different ways to remove the different items that show up in the Search/Find dropdown list.
1. Modify the find objects in the srf and the Application Repository Find records in the current rdbms repository tables.
2. Remove the search categories from the Search Administration Search Index Settings view. This assumes that you have the Search parameters set up so that you can get to these views. (Need to have the filename parameter point to the SSC_Field-Mappings.xml file.)
3. A List of Values value controls the Smart Answer Search Lookin dropdown behavior. Set the list of values value to false for the lov type SEARCH_SMART_ANSWER
.
Even though the Search Lookin dropdown list is a combination of Find and Search items, it is confusing to have different ways to control what shows up in the dropdown.
Solution
The steps to remove the “File System” from the “Look-In” drop down list, can error out with SBL-EAI-04261.
If that error occurs, the solution is to specify the FieldMappings.xml file for the Administration Search Search Engine Settings view's default Search Engine's FileName setting.
Then you can navigate to the Search Administration Search Index Settings and remove the File System record, which will remove it from the Search Lookin dropdown list.
Oracle Siebel Support
Applies to:
Product Release: V7 (Professional)
Version: 7.7.2 [18325]
Database: Microsoft SQL Server 7.0 SP 2
Application Server OS: Microsoft Windows 2000 Server SP 2
Database Server OS: Microsoft Windows 2000 Server SP 2
This document was previously published as Siebel SR 38-1876932687.
Symptoms
SBL-EAI-04261
Hi,
I am trying to Deploy from file in out UAT environment and get the error
We detected an Error which may have occurred for one or more of the following reasons:
Error getting XML from file '\\gbuatsbl201\siebsrvr\ADMExports\1-19OIT_PDQ.xml'. (SBL-EAI-04261)
I use the following file path
\\gbuatsbl201\siebsrvr\ADMExports\1-19OIT_PDQ.xml
I can sucessfully import the file into our DEV environment but not UAT. Can you tell me what may be causing this?
I have seen the SR# 38-1824812962 and the TEMP directory is present on the UAT Server.
Regards,
Sat Gainda
Solution
Message 1
Hello Sat,
Thank you for using the Siebel SupportWeb.
For the benefit of other readers, an error was reported when attempting to select a file in Application Deployment Manager > Deployment Sessions > Menu > Deploy from File :-
Error getting XML from file '\\servername\siebsrvr\ADMExports\file.xml'. (SBL-EAI-04261)
However, using an explicit path name for a mapped drive allowed the file to be processed as expected :-
e:\apps\sea77\siebsrvr\ADMExports\file.xml
The file reference entered initially was \\servername\siebsrvr\ADMExports\file.xml. This is a referencing a share directory on \\servername. As this did not work, but the explicit mapping of e:\apps\sea77\siebsrvr\ADMExports\ did work, it indicated that appropriate permissions did not exist to the share for the operating system running the deploy session, i.e. for web client, the user running the Siebel service (though this was not confirmed in this case).
Change request 12-VWI0LA has been logged to request that a dialog box be provided to allow the selection of the required file, instead of having to type in the full file path and name directly.
Applies to:
Product Release: V7 (Professional)
Version: 7.8.2.4 [19224] FRA
Database: Oracle 10.2.0.1
Application Server OS: IBM AIX 5L 5.3
Database Server OS: IBM AIX 5L 5.3
This document was previously published as Siebel SR 38-3336702721.
Symptoms
Hi,
I'm trying to import admin data (PDQ, views, state-models) with the ADM. But I get the following errors.
(filetransport.cpp (461)) SBL-EAI-04224: Impossible d'ouvrir le fichier '/script/siebint3/livraison/rt-data/ADM/1-1TQBO_LOV.xml
SBL-EAI-04261: Erreur lors de l'obtention XML du fichier '/script/siebint3/livraison/rt-data/ADM/1-1TQBO_LOV.xml
(stepexec.cpp (803)) SBL-BPR-00162: Erreur de mise en œuvre du service 'EAI XML Read from File', méthode 'ReadXMLHier' à l"étape 'Read from File'.
Erreur de mise en œuvre du service 'EAI XML Read from File', méthode 'ReadXMLHier' à l"étape 'Read from File'.(SBL-BPR-00162)
(stepexec.cpp (803)) SBL-BPR-00162: Erreur de mise en œuvre du service 'UDA Service', méthode 'Import File' à l"étape 'Import File'.
Erreur resignalisée depuis le gestionnaire d'objets: ([1] Erreur lors de l'obtention XML du fichier '/script/siebint3/livraison/rt-data/ADM/1-1TQBO_LOV.xml'.(SBL-EAI-04261) (IDS_EAI_ERR_XMLPRT_FILE_READ_ERR))
Erreur resignalisée depuis le gestionnaire d'objets: ([2] Impossible d'ouvrir le fichier '/script/siebint3/livraison/rt-data/ADM/1-1TQBO_LOV.xml
'(SBL-EAI-04224) (0x8085))
( (0) err=4300107 sys=32901) SBL-OMS-00107: Erreur resignalisée depuis le gestionnaire d'objets: ([2] Impossible d'ouvrir le fichier '/script/siebint3/livraison/rt-data/ADM/1-1TQBO_LOV.xml
'(SBL-EAI-04224) (0x8085))
( (0) err=4300107 sys=33405) SBL-OMS-00107: Erreur resignalisée depuis le gestionnaire d'objets: ([1] Erreur lors de l'obtention XML du fichier '/script/siebint3/livraison/rt-data/ADM/1-1TQBO_LOV.xml
'.(SBL-EAI-04261) (IDS_EAI_ERR_XMLPRT_FILE_READ_ERR))
( (0) err=4300107 sys=32984) SBL-OMS-00107: Erreur resignalisée depuis le gestionnaire d'objets: ([0] Erreur de mise en œuvre du service 'EAI XML Read from File', méthode 'ReadXMLHier' à l"étape 'Read from File'.(SBL-BPR-00162) (0x80d8))
(bsvcmgr.cpp (364) err=4300203 sys=0) SBL-OMS-00203: Erreur 32984 d'appel de la méthode "RunProcess" pour le service commercial "Wor...
Solution
Message 1
Customer was imporgting data with ADM but was encountering various errors indicating file access issues..
Such as
SBL-EAI-04224, SBL-EAI-0426, SBL-BPR-00162
Customer found hat the issue was caused due to control character " ^M" at the end of of lines in the .ini files. Typically occurs when transfer files from windows to unix
keywords:
SBL-EAI-04224, SBL-EAI-0426, SBL-BPR-00162,filetransport.cpp,ADM,import,unix,control,character
Applies to:
Siebel Tools - Version: 8.0 [20405] to 8.1.1.2[21215] - Release: V8 to V8
Information in this document applies to any platform.
Purpose
The Find functionality allows users to quickly execute queries on common fields and then drill down on those records. The Search and Find functionality use the same user interface model and they both are invoked with the Binoculars icon.
There were significant changes with the Find Functionality in the earlier Siebel 8 releases. It is recommended to use Siebel 8.0.0.5 or 8.1.1.2 or higher if using the Find functionality. Those versions provided ACR 439 which replaces ACR 367.
Siebel
Find Support?
ACR
8.0
No
8.0.0.2
Yes
ACR 367
8.0.0.5
Yes
ACR 439
8.1.1
Yes
ACR 367
8.1.1.1
Yes
ACR 439
Find functionality is only available with Siebel 8.0.0.2 and 8.1.1 and higher. The Find user interface is slightly different for Siebel versions that provide ACR 367 or ACR 439. ACR 439 replaces ACR 367, therefore it is recommended to install a Siebel version that supports ACR 439. The Find functionality is the same with both ACRs, but the user interface with ACR 439 is more like Siebel 7's search user interface. Review the screen shots below to see the different screen layout for the different versions. The main difference was that ACR 367 Siebel Search user interface displayed the search results in the main window and the user did not see the current view. Note, that the Find search and results applets search frame has moved from the left to the right side of the screen with Siebel 8. This was intended for a better user interface. This is controlled by the standard web templates.
Siebel Search user interface 7.8
Siebel Search user interface 8.0.0.2 or 8.1.1 (ACR 367)
Siebel Search user interface 8.0.0.5 or 8.1.1.1 (ACR 439)
Questions and Answers
Questions
Installing ACR 367 Find issues.
This is the only version of Find supported with earlier Siebel 8 versions. Note that the later versions will change the Siebel Search user interface.
Maintenance Release Guide ACR 367 Configuration
Where are the ACR 367 installation instructions now that ACR 439 has replaced ACR 367 in the Maintenance Release Guide?
The Post Maintenance Release installation instructions for ACR 367 are from the earlier version Siebel maintenance release guides and can be found in this document.
Find Functionality Is Now Supported in Siebel Fix Pack Version 8.0.0.2 with ACR 367. ACR 367 includes Configuration Instructions.
SBL-DBC-00110 errors when importing FindAttach.sif file
The FindAttach80.sif tools archive file is failing to import into Siebel Tools with with SBL-DBC-00110 errors. The FindAttach80.sif that is provided in the Siebel Tools 8.0.0.2 or 8.1.1 REPPATCH directory has symbolic strings for all shipped languages. If the database is not unicode, then importing the sif file with fail with SBL-DBC-00110 errors. Please contact support if you need a Language specific version of this sif file.
Common Find issues reported with ACR 367 or ACR 439.
Why are there duplicate find objects?
One of the more common issues is that the find objects appear in duplicate. This is because the Siebel 8.0 find uses a select statement to show the find object dropdown list. The sql does not restrict the query to one repository. Therefore if your database has multiple repositories, the find sql finds the find objects across different repositories.
'Look In' dropdown in Find object shows duplicates, the find objects are out of sequence and some columns are null?
Find Objects not displayed for Partner Portal and Duplicate Find Objects in the Dropdown List.
Why do users get this error when drilling down on a find result?
The selected search result cannot be found.(SBL-SRH-00167).
SBL-SRH-00167 error when drill down on binocular search on Contacts
8.0.0.2 SIA + ACR 367 - Find drilldown does not work correctly
How to remove different objects from the Find dropdown like SmartAnswer or File System?
Disabling "File System" & "Smart Answer" from the "Look In" drop-down list
How to "File System" value in the Look In drop down? Error getting XML from file 'CHANGE_ME' SBL-EAI-04261
How to increase the width of the Find or Search frame user property document?
How to increase the search results window size in the Binocular search result?
How to have the find results be displayed in the drilldown view in the main view and skip the Find Results applet?
Can you configure the Find Results to go directly to the drilldown view and not the Find Results applet?
How come resizing the find applet to be thinner leaves some of the screen blank?
Resizing the Search and Find frame to be thinner causes "blank white space" between the Search frame and the main window frame.
Is it possible to move the Find / Search apple back to the Left side of the screen?
Changes with Search and Find after upgrading to 8.1 from 7.5, Find is on the Right side and the Find Applet does not Automatically Close. (
References
NOTE:1186995.1 - Changes with Search and Find after upgrading to 8.1 from 7.5, Find is on the Right side and the Find Applet does not Automatically Close.
NOTE:475394.1 - Find Functionality Is Now Supported in Siebel Fix Pack Version 8.0.0.2 with ACR 367. ACR 367 includes Configuration Instructions.
NOTE:531195.1 - Can you configure the Find Results to go directly to the drilldown view and not the Find Results applet?
NOTE:555931.1 - 'Look In' dropdown in Find object shows duplicates, the find objects are out of sequence and some columns are null?
NOTE:560274.1 - Disabling "File System" & "Smart Answer" from the "Look In" drop-down list
NOTE:560762.1 - 8.0.0.2 SIA + ACR 367 - Find drilldown does not work correctly
NOTE:727967.1 - How to remove "File System" value in the Look In drop down? Error getting XML from file 'CHANGE_ME' SBL-EAI-04261
NOTE:742736.1 - Find Objects not displayed for Partner Portal and Duplicate Find Objects in the Dropdown List.
NOTE:799154.1 - SBL-SRH-00167 error when drill down on binocular search on Contacts
NOTE:862146.1 - How to increase the search results window size in the Binocular search result?
NOTE:867522.1 - Resizing the Search and Find frame to be thinner causes "blank white space" between the Search frame and the main window frame
Applies to:
Siebel Tools - Version: 8.0.0.3 SIA [20416] - Release: V8
Information in this document applies to any platform.
Symptoms
The customer installed Siebel application 8.0.0.3 SIA with FRA language only, and wanted to enable the Find functionality. For that they followed the "Configuration Instructions for ACR 367" (discussed in Note 475394.1 and in Maintenance Release Guide, Siebel CRM version 8.0) but the Find feature didn't work: In the "Look In" drop-down list of the Search Center the Find objects were not available. Only "Smart Answer" was visible.
Cause
This behavior has been reproduced using Siebel Communications application and addressed by BUG 10553779. The root cause is the mismatch between the Search Definition specified in the application CFG file (for the dedicated client) and at application OM level (for the web client) and those available in view Site Map > Administration - Search > Search Definition.
Indeed the FRA scomm.cfg file has this parameter:
- - -
SearchDefName = Call Center Definition
- - -
and the Search - Definition Name parameter at OM level has the same value.
However this value does not exist in view Site Map > Administration - Search > Search Definition. The definitions available are:
- -
Définition de centre d'appels
Définition de vente
- -
NOTE: The first value is the FRA translation for "Call Center Definition"
> If you change it to "Call Center Definition" the Find objects appear in the drop-down list as expected for both dedicated and web clients.
Additional researches have revealed that the Search Definition Names that appear in view Site Map > Administration - Search > Search Definition shouldn't be translated. That means the names should be:
- - -
Call Center Definition
Sales Definition
…
- - -
and not:
- - -
Définition de centre d'appels
Définition de vente
…
- - -
Bug 12-1MQ80BU has already been logged to address this issue.
On the other hand as the SearchDefName CFG parameter and the Search - Definition Name OM parameter are used by the Search feature, not the Find feature, a Search Definition mismatch shouldn't have any impact on the Find feature. BUG 10553783 has been logged to address this matter.
Solution
The SearchDefName and Search - Definition Name parameters are used for the Search feature in Siebel application, not the Find feature. If you don't plan to use the Search feature in your environment a possible solution is to set to null (blank) these parameters. Note that is not possible to directly set the Search - Definition Name OM parameter to a blank value. You need to use the Delete Parameter Override feature, available in the applet menu and via the command-line interface. This feature is documented in the Bookshelf:
Siebel System Administration Guide
Configuring Siebel Servers
Advanced Configuration Tasks
Deleting System Parameter Overrides
Siebel System Administration Guide
Using the Siebel Server Manager Command-Line Interface
Siebel Server Manager Commands
Parameter Management Commands
The other solution is to correct the Search Definition Names in view Site Map > Administration - Search > Search Definition .
If in Siebel application you cannot access this view because you get the following error (in ENU):
- - -
Error getting XML from file 'CHANGE_ME (Ex: \\searchserver\shared\SSC_Field-Mappings.xml)'. (SBL-EAI-04261)
- - -
then to prevent this error you need to access the 'Search Admin' view (Site Map > Administration - Search > Search Engine Settings) and specify the path to the SSC_Field-Mappings.xml file by setting the Filename search engine parameter.
If you cannot access the 'Search Admin' view (because of your license keys) then a possible solution to prevent the error and access the view 'Search Definition Categories View' is to temporarily inactivate the child applet 'Search Definition Categories'. In case you have no access to the 'Search Admin' view (because of your license keys) then the solution is to copy the view and add the new view as screen view in screen 'Search Admin View Screen'. Then in Siebel application you will have to declare the new view and associate it to the appropriate responsibilities.
References
NOTE:475394.1 - Find Functionality Is Now Supported in Siebel Fix Pack Version 8.0.0.2
BUG:10553779 - 8.0.0.3 + ACR 367: IN FRA APPLICATION THE FIND OBJECTS DO NOT APPEAR IN THE "LOOK IN" DROP-DOWN LIST
BUG:10553783 - 8.0.0.3 + ACR 367: UNEXPECTED SEARCH DEFINITION DEPENDENCY FOR FIND FEATURE
Applies to:
Siebel Tools - Version: 8.0.0.5 SIA [20420] and later [Release: V8 and later ]
Information in this document applies to any platform.
Goal
We are using Siebel Financial Services application.
We need to remove some of the application find child objects via Siebel Tools in order to reduce the list of find or search objects with the Find Look In dropdown options. These are the options shown when the user clicks over the Search button (the Binoculars icon from the Application level toolbar).
There are two Application find child objects that I need to remove: "File System" and "Smart Answer", but they are not presented as a child Find object to the Application object "Siebel Financial Services" in Siebel Tools.
Please, inform me where can I find them and inactivate.
Solution
These documents explain how to get remove these two objects from the Find Look In drop down.
Find Functionality User Interface differences with for Siebel Search with ACR 367 and ACR 439. (Doc ID 1107293.1)
See the section with this title, "How to remove different objects from the Find drop down like SmartAnswer or File System?".
Disabling "File System" & "Smart Answer" from the "Look In" drop-down list
How to "File System" value in the Look In drop down? Error getting XML from file 'CHANGE_ME' SBL-EAI-04261
Note, that performing the steps documented for removing "Smart Answer" from the Find drop down were still not working in the thin client environment.
The customer found that these steps did remove the "Smart Answer" from the Find Look In drop down in the server thin client environment.
It is possible to disable Smart Answers on the server now after performing the following steps.
1. Go to List Of Values View, query for "SEARCH_SMART_ANSWER" and change Active=N, Translation=N, Multilingual=N
Then clear the LOV cache with the button of the menu option.
2.Go to List Of Values Explorer View and for "SEARCH_SMART_ANSWER" type change Translate=N, Multilingual=N.
3.Log out and Log in to the thin client.
The "Smart Answer" option was finally removed after deactivating the LOV Type and then the LOV values and also removing the flag for Multilingual column.
Note, that for the Smart Answer to be removed in a thin client environment, it requires that the LOV type and the LOV values for SEARCH_SMART_ANSWER are inactive and that the Translate and Multilingual flags are also inactive.
No comments:
Post a Comment