Implementing the Verity Search Engine

This chapter provides an overview and discusses how to:

Build the Verity search engine.
Create and update the Verity search collection.
Set up and run the Verity search update Daemon Group program.
Configure Verity search index options.
Maintain the Verity thesaurus.

Understanding the Verity Search Engine

The Verity search engine enables requesters to search using synonyms and match cases. Also, you have the option to define price range and model as search fields. The Verity search engine can be used to access items from the PeopleSoft Item Master table or other item sources, including express catalog items. Once the items are indexed into the Verity collection, they can be searched and browsed for PeopleSoft eProcurement.

The Verity search engine consists of these components:

Verity Search Collection	A collection is a language-specific directory or folder that contains multiple subdirectories that contain various kinds of files used by the Verity search engine during indexing and searching. Note. These files are created based on a snapshot of the data in the specified record/field.
Verity Field	A field indexed into a Verity collection can be searched using word searching or comparison searching. For example, if you wanted to search of items priced less that $20.00 USD, Price must be in the index as a field. The value indexed in a Verity field can be returned to an application using the Verity results framework.
Zone	A zone contains a group of words that are identified by a set of XML-like open and closed tags. For example, <DESCR> long sleeve shirt </DESCR>. A zone is indexed into the Verity collection for searching purposes only. Information indexed in a zone can't be returned to the calling application. Comparison searching can't be done in a zone. Searching within a zone proceeds faster than when using fields.
Data Object	Defines the record relationships.
Data Object Set	A set of data objects that are related to each other with level and parent-child information.

A Verity collection is a group of fields that you set up that is used by the Verity search engine to index and assist users in their search for items. You define the fields for a requester to utilize in their search for items.

You can use either batch updates and rebuild, or incremental updates to build, Verity index collections. Searches are then performed against this collection. Items loaded from a CUP process can be indexed directly into the collection by checking the Index Others check box.

The Verity collection is built using the PeopleSoft Application Engine process (PV_IDX_DATA), which is accessible from the Build Verity Collection page. This process extracts data from the item catalog tables and writes a few intermediate text files: the BIF files and the DAT files. These files are indexed into the Verity collection, which comprises multiple file folders.

To implement the Verity search engine, use the Verity Search Indexing and the Maintain Verity Information components.

Note. These PeopleSoft application utilize the Verity search engine: PeopleSoft eProcurement, PeopleSoft Order Management, and PeopleSoft Contracts. While much of the discussion in this chapter relate to PeopleSoft eProcurement, you can apply the same concepts to the other applications.

See PeopleSoft Enterprise PeopleTools 8.46 PeopleBook: Verity Collection Reference Guide for PeopleSoft

Prerequisites

Before you begin building Verity indexes, you must enable Verity as the Catalog Search Type on the eProcurement Installation Options page.

See Setting Up PeopleSoft eProcurement Installation Options.

Building the Verity Search Index

The Verity search engine is made up of multiple indexes. General setup tasks are:

Activate Verity on the Installation Options page.
Build the search index.
Run each of the Build Search Indexes processes.
(Optional) Set up the daemon to run periodically to automatically refresh the indexes.

Fields indexed into the collection are:

Verity Field/Zone Name	Indexing Logic	PeopleSoft Record/View
VdkVgwKey	Concatenate the following fields in this format to form a unique key: {SETID}{INV_ITEM}{VENDOR_SETID}{VENDOR_ID}	MASTER_ITEM_TBL and ITM_VENDOR
ACTIVE	Item is always active.	MASTER_ITEM_TBL
ALL_RGNS	Item is available to all regions.	PURCH_ITEM_ATTR
ALL_IV_REGIONS	Concatenate all vendor regions that are valid for an item.	Item vendor region record
IV_REGIONS	Concatenate all vendor regions that are valid for an item and a specific vendor.	Item vendor region record
IV_REGIONS_PRIO	Index the item vendor priority for each item vendor region information.	Item vendor region record
SETID	SetID.	MASTER_ITEM_TBL
VENDOR_SETID	Vendor SetID.	ITM_VENDOR
VENDOR_ID	Vendor ID.	ITM_VENDOR
CATEGORY_ID	Category ID.	MASTER_ITEM_TBL
CAT_DESCR	Category description.	ITM_CAT_TBL
ALL_CAT_ID	Concatenate all related category IDs for an item.	PV_ITM_CATEGORY
ALL_CAT_DESCR	Concatenate all related category descriptions for an item	PV_ITM_CATEGORY and PV_ITM_CAT_TBL
CURRENCY_CD	Currency code.	PURCH_ITEM_ATTR
CNV_CURRENCY_CD	Converted currency code.	PV_SRCH_RUN_CTL
CNV_PRICE	Use item vendor price for the default UOM, if exists. If not, use standard price.	ITM_VNDR_UOM_PR and PURCH_ITEM_ATTR
TREE_NAME	Concatenate all tree/catalog names into one field.	PV_CAT_TREE_TBL and MASTER_ITEM_TBL.
DESCR	Include DESCR254_MIXED. Note. This description comes from the Purchasing Attributes Long Description.	PURCH_ITM_ATTR
INV_ITEM_ID	Item ID.	MASTER_ITEM_TBL
INV_ITEM	Inventory Item Flag.	MASTER_ITEM_TBL
ITM_ID_VNDR	Vendor Item ID.	ITM_VENDOR
ITM_DT_F	Future item status date.	MASTER_ITEM_TBL
ITM_STAT_C	Current item status.	MASTER_ITEM_TBL
ITM_STAT_F	Future item status.	MASTER_ITEM_TBL
MASTER_ITEM	Set this field to Y if item is from master item record. N if from Express Catalogs.	AE PeopleCode
PREF_VENDOR_SW	Populate this field based on the item vendor priority value. If it is 1, set this flag to Y.	ITM_VENDOR
PRICE_LIST	Standard Price.	PURCH_ITEM_ATTR
PRICE_VNDR	Item vendor price.	ITM_VNDR_UOM_PR
MFG_ID	Manufacturer ID. Use Item Vendor Mfg ID if it exists. If not, use Item Mfg ID.	ITEM_MFG and ITM_VENDOR_MFG
MFG_ITM_ID	Manufacturer's item ID.	Item vendor Manufacture and Item Manufacture
MFG_NAME	Concatenate Manufacture ID and Manufacture name. (These can be separate also.) Manufacture information from item vendor level should be used if it exists. if not, use the item level information.	ITM_VENDOR_MFG and ITEM_MFG
PREF_MFG	Use the preferred manufacture flag from the item vendor manufacture record, if it exists. If not, use the item manufacture record.	ITM_VENDOR_MFG and ITEM_MFG
VNDR_NAME1	Concatenate the vendor ID and vendor name. (These can be separate also.)	ITM_VENDOR and VENDOR
MODEL	Model.	PURCH_ITEM_ATTR
UPN_ID	UPN ID (universal product number).	ITEM_MFG_UPN_FS
RETURN_VALUES	Concatenate all fields required to be displayed on the requisition into this RETURN_VALUES field.	All record relevant record fields.

Enabling the Verity Search Engine

To set up Verity searches, use the Verity Search Indexing component.

To set up the Verity search engine:

Open the application server configuration file in a text editor (psappsrv.cfg) and add the following search index path under the [Search Indexes] section: FDM_PV_ITEMCATALOL=[Collection File Path].

Note. [Collection File Path] is the directory path that the system uses to store the Verity collection files. This directory must be shared if multiple application servers are accessing the same path. There are no spaces before or after the equal sign in the search index path.
Open the process scheduler server configuration file (psprcs.cfg) in a text editor.

Copy the [Search Indexes] section from the application server configuration file and paste it near the end of the psprcs.cfg file.
Create and configure a process scheduler to run on the application server where the system runs the indexing process.
Navigate to the Build Verity Collection page and create the collection for the first time using the Create New/Rebuild Collection option and then running the process for the platform.

Note. It is important that the Update/Reload Tree Table check box is selected if this is a first-time build. Also, use this option whenever there are changes to the tree data. However, if tree data has not changed since you last ran the process, you can clear the check box to improve performance of the indexing process.

The system uses VSE to index the tree table automatically and activate the tree table PV_CAT_TREE_TBL for item browsing.

Note. The PV_CAT_TREE_TBL tree table must be populated for Verity searching.
Use the Build Verity Collection page to schedule the process to periodically update or rebuild the item catalog collection.
Set the Catalog Search Type on the eProcurement Installation Options page to VSE.

Setting Up the Daemon Process

Incremental updates provide online updates for items that are added, updated, or inactivated in the Item Definition, Item Approval, Item Copy, and Purchasing Attributes components. With Verity incremental updates, you can set up a Daemon process that automatically updates index values at a specified time interval.

Use the Maintain Verity Online Update Fields page to activate or inactivate the inventory and purchasing Verity index fields. When any of the active fields specified on PV_VER_IDX_FLDS are changed in the Item Definition, Item Approval, Item Copy, or Purchasing Attributes components, data is immediately stored in staging table PV_VER_UPD_STG.

This application engine program is run at specified time intervals. It calls the Verity Indexing program (PV_SRCH_INDX) to update all data stored in the staging table.

Creating and Updating the Verity Search Collection

This section discusses how to create and update the Verity Search Collection.

Page Used to Create and Update the Verity Search Collection

Page Name	Object Name	Navigation	Usage
Build Search Index	PV_IDX_RUN_CNTL	eProcurement, Administer Procurement, Maintain Supplier Integration Click the Build eProcurement Verity Collections link on the Maintain Supplier Integration page.	Use this process to update the eProcurement FDM_PV_ITEMCATALOG catalog only. Access is limited to users with the eProcurement action role System_Admin. Use this page to define parameters for loading items into catalogs that the Verity search engine uses to search for items. If you will not be configuring the index, you need only to build a search index and run the Daemon process. Note. eProcurement delivers a set of system data of the FDM_PV_ITEMCATALOG collection. See Configuring Verity Search Indexing Options.

Page Name

Object Name

Navigation

Usage

Build Search Index

PV_IDX_RUN_CNTL

eProcurement, Administer Procurement, Maintain Supplier Integration

Click the Build eProcurement Verity Collections link on the Maintain Supplier Integration page.

Use this process to update the eProcurement FDM_PV_ITEMCATALOG catalog only. Access is limited to users with the eProcurement action role System_Admin.

Use this page to define parameters for loading items into catalogs that the Verity search engine uses to search for items. If you will not be configuring the index, you need only to build a search index and run the Daemon process.

Note. eProcurement delivers a set of system data of the FDM_PV_ITEMCATALOG collection.

See Configuring Verity Search Indexing Options.

Building Search Collections

Access the Build Search Index page.

Index Name

Enter a name for the index you are creating, or use the delivered index FDM_PV_ITEMCATALOG.

Build Option

Select the build method for the search index. The filtering criteria used depends on the method you select. The values are:

Create New/Rebuild indicates that you are creating or rebuilding an index. You can limit the data retrieval by specifying a setID.

Process Last Modified runs the process based on last modified incremental updates.

Update All Items for a Vendor enables you to limit the update to a specific Vendor SetID or Vendor ID or both.

Update Specific SetID or Items enables you to limit the update to a specific SetID or a range of Item IDs or both.

Update by Other Criteria enables you to limit the update by giving value to any or all of these additional criteria:

Source Data Object

Record Name

Field Name

Update/Reload Tree Table

Select to populate the table PV_CAT_TREE_TBL.

Source

If additional data filtering is needed, select to assign a source data object to the index.

Collection Language

Select a language code. You can index Verity for multiple languages; for example, English, Spanish, and Dutch. This makes it possible to support multiple languages in one system.

Index File Path

This display-only field is populated from the Application Configuration file.

Note. Make sure that the collection is accessible to all applications servers and to the process scheduler server running this process.

Test Index

Click this link to determine whether there are entries in the index.

To run the search index process:

On the Process Scheduler Request page, select Verity Search Indexing (PV_SRCH_INDX).

Setting Up and Running the Verity Search Update Daemon Group Program

This section discusses how to create and use a daemon group.

Understanding Daemon Groups

Daemon groups are used to periodically update Verity indexes with the most recent changes. A Daemon group is the equivalent of running a single job in the process scheduler. By using the Daemon group, you can effectively run multiple processes without having to run multiple jobs. Use the Daemon group if you are running frequent update processes. The Daemon groups are used primarily for updating changes to the Verity index, and should not be used to run an entire rebuild of your Verity index.

Note. If you have a large amount of data, you should examine the frequency of running the Daemon group. The system needs time to process all of the information within the tables.

Page Used to Set Up and Run the Verity Search Update Daemon Group Program

Page Name	Object Name	Navigation	Usage
Daemon Group	DAEMONGROUP	PeopleTools, Process Scheduler, Daemon Group	Set up and run the Verity search update Daemon Group Program.

Setting Up and Running the Daemon Group

Access the Daemon Group page.

To set up the Verity Search Update Daemon program:

Create a new Daemon group.
1. Add a new Daemon Procedure Group PVDAEMON.
2. Select the program name PV_SRCH_DAEM.
3. Save the Daemon group.
Set up the PeopleSoft Process Scheduler Server using PeopleTools, Process Scheduler, Servers.
1. Select to edit PeopleSoft Process Scheduler server.
2. On the Daemon tab, select the Daemon Group PVDAEMON.
3. Select the Daemon Enabled check box.
4. Specify the Daemon Sleep Time.
5. Save the changes.
Clear the PeopleSoft Process Scheduler cache and restart PeopleSoft Process Scheduler. The Daemon process starts automatically. You can view a log of the process on the Process Monitor - Server List page.

Configuring Verity Search Indexing Options

This section provides an overview of Verity Search Indexing options and discusses how to:

Set up and run the Daemon group.
Dynamically alter Source to Index.
Define source data objects.
Define source data object fields.
Define source data object join conditions.
Define source data object data object sets.
Enable the incremental update process.
Define search indexes.
Define search index fields.
Create a search query.
Define field labels for custom searches.
Display search results.
Define search options.

You can dynamically add or remove records and fields from the Verity search engine. The process consists of these steps:

Determine if an existing data object contains the field you need to add or remove.
If you do not have an existing data object, you must create one.
Select the field from the data object and index as a field or a zone.
Either map the Verity field/zone to the database field, or define processing logic.
Build the Verity collection.

This diagram illustrates the change order process:

Configuring the Verity collection

Dynamically Altering Source to Index

To make changes to the information source that you will index:

Define the search index fields, and either add or subtract them from the data source object.
Define new data object sets to signify the location of the data source.

Pages Used to Configure Verity Search Indexing Options

Page Name	Object Name	Navigation	Usage
Source Data Object	EOEW_SRCDO	eProcurement, Administer Procurement, Maintain Supplier Integration Click the Define Data Objects link on the Define Data Object Set page.	Identify a grouping of source records.
Fields	EOEW_SRCFIELD	eProcurement, Administer Procurement, Maintain Supplier Integration Click the Define Data Objects link on the Define Data Object Set page. Click the Fields tab.	Select fields from source records that will be used in the search index.
Join Conditions	EOEW_SRCJOIN	eProcurement, Administer Procurement, Maintain Supplier Integration Click the Define Data Objects link on the Define Data Object Set page. Click the Join Conditions tab.	Indicate how the system should put two source records and field combinations together to simplify indexing.
Build Search Index	SAC_IDX_RUN_CTRL	eProcurement, Administer Procurement, Maintain Supplier Integration Click the Build Search Indexes link on the Maintain Supplier Integration page.	If you create your own search index, you need to use this process to build the index. Access is limited to users with the eProcurement action role System_Admin.
Define Data Object Set	SAC_IDX_DO_SET	eProcurement, Administer Procurement, Maintain Supplier Integration Click the Define Data Object Set link on the Maintain Supplier Integration page.	Define the parent child relationships among the identified source data objects.
Define Search Index	SAC_IDX_DEFINE	eProcurement, Administer Procurement, Maintain Supplier Integration Click the Define Search Indexes link on the Maintain Supplier Integration page.	Identify the data object set, which contains the data source object, records, and fields. The data identified here become the search details on the requisition.
Define Search Index Fields	SAC_IDX_FIELDS	eProcurement, Administer Procurement, Maintain Supplier Integration Click the Define Search Index Fields link on the Maintain Supplier Integration page.	Specify the record fields to search.
Define Search Query	SAC_SRCH_QRY	eProcurement, Administer Procurement, Maintain Supplier Integration Click the Define Search Query link on the Maintain Supplier Integration page.	Identify how the system searches the index.
Define Search Result	SAC_SRCH_RSLT	eProcurement, Administer Procurement, Maintain Supplier Integration Click the Define Search Result link on the Maintain Supplier Integration page.	Identify how the system displays the results of the search.
Define Search Options	SAC_SRCH_OPTIONS	eProcurement, Administer Procurement, Maintain Supplier Integration Click the Define Search Options link on the Maintain Supplier Integration page.	Identify how the system reads the search request. For example case sensitivity, exact wording, or using a thesaurus.

Defining Source Data Objects

To set up source data objects, use the Define Data Object Set component.

Access the Source Data Object page.

To define a source data object:

Define the source records that the system uses to retrieve data.

For example, item data can be retrieved from MASER_ITEM_TBL, PURCH_ITEM_ATTR, and ITM_VENDOR.
Define fields for each record, which are used to index as Verity Fields and/or Verity Zones.
Define the join conditions that tell the system how multiple records and fields work together.

Subject Area	Used to group translations sets, transformations, map rules, and map definitions.
Description	The description you use to identify the specific source data object.
Source Record	Tables where you store fields within the PeopleSoft system, and where you want to define a relationship. For example, you may want to identify a relationship between the INV_ITEM_ID in the Vendor Item Table and the Vendor Location Item Table.

Defining Source Data Object Fields

Access the Fields page to identify fields needed from the source record tables.

Select the fields from within the source record that you want to utilize within the source data object. These fields can be utilized with any search index that has this specific source data object as part of the search.

Source Field Name	Fields specific to the source record selected.
Field Alias	Using the Field Alias field, you can rename the field if you choose.
Synchronize Fields	This button is not used for PeopleSoft eProcurement. It is used with PeopleTools integration to Verity.

Defining Source Data Object Join Conditions

Access the Join Conditions page.

Use this page to join records and fields. If you have two source records identified within the object, you need to tell the system how the two work together. For example, if the you identify the VENDOR table and the ITM_VENDOR table, you need to identify that the two VENDOR_ID fields are the same.

Record Name	Define the source record value for the each of the tables you want the system to recognize as the same. The selection values are determined by the source records identified on the Source Data Objects page.
Field Name	Define the fields for the specific records that are equal to the field to the related record. The fields are selected on the Fields page.

Defining Source Data Object Sets

Access the Define Data Object Set page.

Use the Define Data Object Sets page to identify one source record on level 0 as the master source record that drives the indexing process. You can also define multiple levels of source records and their processing sequence.

Data Object Set Name	A unique identification for a data set object.
Seq (Sequence)	The processing sequence.
Level	The level number of the source data object. The master data object level is level 0. a subsequent level indicated that the data object is either a child or a peer data object of its parent data object.
Source Data Object	The name of the source data object.
Parent Data Object	The parent data object for the specific source data object.
Root Package	The application package that defines how each field selected from the index will be indexed.
App Class Path (application class path)	The application class that defines how each field selected from the source data objects will be indexed. Note. The application class defined must be an extension to the source data object class and should have an override to the CustomMapFields() method. By default AnyDataObj application class will be used.
Index Key	Identifies the source data objects that have key fields to drive the indexing process. Note. The index keys are defined on the Define Search Index page.
For Staging	Identifies source data objects that will be used as a staging table during the incremental update process.

Note. To enable incremental updates, a staging table and data object need to be created. The staging data object will be used in place of the master data object during the incremental update.

Enabling the Incremental Update Process

The staging table must satisfy these requirements:

It must contain the same key fields as the master driving table.
It must contain one more key field: DTTM_STAMP

The staging data object must satisfy these requirements:

It must contain a join between the common key fields of the staging table and all the tables available in the master data object.
It must contain the same number of fields as the master data object. All field aliases should be the same as the field name.

Defining Search Indexes

To define search indexes, use the Define Search Index component.

Access the Define Search Index page.

Use this page to create new search index and assign a specific source data object set for use with the search index.

Search Index Name	Name of the search index.
Description	Description of the search index.
Component ID	Run control that is used to create/update this collection.
Staging Record for Updates	The record that stores the keys for incremental updates. Note. This table must share the same key structure as the master table.
Root Package ID	Identifies the application package used for indexing.
Create/Rebuilding	The application class extending the AppSearchIndex class that handles creating/rebuilding a new search index.
Update via Master Data Obj. (Update via Master Data Object)	The application class extending the AppSearchIndex class that handles updating the search index based on selection criteria on the master table.
Update via Other Data Objs. (Update via Other Data Objects)	The application class extending the AppSearchIndex class that handles updating the search index based on selection criteria on other tables.
Data Object Set	Select a registered data object set to limit data retrieval.
Active	Select Active for all source data object sets that the system can use for this index.
Default	Select Default to tell the system which data object set should be used to display by default when the user goes to the Build Search Index page.
Datetime Stamp	Identifies the field as a date/time stamp filed. This is used to compare date/time when updating last modified.

For each source data object set, you create a group of source data objects. In the Optional Source Field Setup section of the Search Index page, you can limit the amount of data that is retrieved from each source data object by creating criterion. Set these limits by using the one of the following values:

Defining the search criterion:

<	Less than.
<=	Less than or equal to.
<>	Less or greater than.
=	Equal to.
>	Greater than.
>=	Greater than or equal to.
Between	Between two entries.
LIKE	Similar to.

Stating the values of the specific field search criterion.

Defining Search Index Fields

Access the Define Search Index Fields page.

From the Define Search Index Fields page, you define specific fields that are stored in the search index file.

Data Object	Name of the source data object as defined in the data object set assigned to this search index.
Field Name	Name of the data object field.
Index Field Name	Name of the search index field to be indexed into the collection. This name is defaulted to be the same as the record field name.
Field Type	Indexed as a Verity field and/or zone.
Priority	Identifies how the system determines which field values to utilize when two or more records contain the same field.
Index Key	Indicates fields to drive the indexing process.
Translate	Select if the field needs related language processing.

Example: Adding a New Simple Field

These steps extend the search index.

Insert a new field to the source data object used by the search index.
Identify the new field to be used for Verity indexing on the Search Index Field page.
This new field will be picked up in the Verity indexing engine for direct mapping.

Example: Adding a New Field that Requires Customized Processing

These steps allow you to customize the search.

Insert a new field to the source data object used by the search index.
Identify the new field to be used for Verity indexing on the Search Index Field page.
Extend the appropriate source data object class to include special processing.

Example: Adding a New Field from a New Record

These steps include another record in the search index.

Add a new record to the appropriate source data object used by the search index.
Identify and insert the new fields from this record in the Data Object Definition page.
In the Define Data Object Set page, use the AnyDataObject application class to provide default direct mapping from the data object fields to Verity fields.
Identify the new field to be used for Verity indexing on the Search Index Field page.
Extend the appropriate source data object class to include special processing.

Creating a Search Query

To create Verity searches, use the Define Search Query component.

Access the Define Search Query page.

Use the Define Search Query page to define a group of fields for display as users search fields on the transaction search page.

Search Query Id	ID for this search query definition.
Description	Description for this search query definition.
Root Package	The application package that handles the search query mapping.
App Class (application class)	The application class extending the Format class that controls the formatting logic for the field.
Search Indexes	Use the link to define which search indexes to associate with the result set of this query. You can select more than one index.
Index	Defines the specific index the query utilizes for the search.
Index Field Name	Fields available for the search indexes associate with the selected search indexes.
Record Name	Record names for the work record used in the transaction search scroll.
Field Name	Work record fields that are used to enter search criteria when requesters are performing a search. This can also be fields that the system uses to populate search criterion in the background, for example SetID.
Constant	Search criteria that must always equal a specific, non-changing, value.
Range	Identifies that the search can be given a range. For example, Price can equal any where from $20.00 USD to $25.00 USD.
Display	Specify whether the field is a background search criterion or a user-defined search criterion.

Defining Field Labels for Custom Searches

Access the Define Search Query: Field Labels and App Class page.

If you are creating a new query, you have two options to display search fields on the query page. You can either hard-code each field using Application Designer, or you can dynamically populate the searchable fields. The Field Labels and App Class tab is where you use messages to define field labels when the work grid is dynamically populated.

Msg Set (message set)	Message set displayed as the search field label.
Msg # (message number)	Message number displayed as the search field label.
Root Package ID	Application package ID for the specific field label.
App Class Path (application class path)	Application class for the specific field label.

When the transaction search page is displayed, the following information is populated on the page:

Work record used for the search fields.

For example, the user sees description.
Work record used for the search fields by range, if any.

For example, the user can enter a price range.
Work record used for the search options grid.

For example, the user can elect to use exact words or synonyms.

Note. Other fields, such as Currency in the case or price range, need to be manually created.

Displaying Search Results

To display search results, use the Define Search Results component.

Access the Define Search Result page.

Based on how you elect to display your search results, the values returned from the Verity search index are mapped to the appropriate component record fields.

Search Result	ID for this search result definition.
Description	Description for this search result definition.
Root Package	The application package that handles the search result mapping.
App Class (application class)	The application class that handles the search result mapping.
Search Queries	Identifies the search queried that are associated with this result set.
Index	Defines the specific index the query utilizes for the search.
Index Field Name	Fields available for the search indexes associate with the selected search indexes.
Record Name	Record names for the work record used in the transaction search result scroll.
Field Name	Work record fields that are used to store values of an index field returned after executing a search.

Defining Search Options

Access the Define Search Options page.

Use the Define Search Options page to enable users to search using these options:

CASE	Activate CASE if you require the search to be case sensitive.
EXACT	Activate EXACT if you require the user to have the exact word match.
THES	Activate THES if using the thesaurus.

Maintaining the Verity Thesaurus

This section discusses how to maintain the Verity thesaurus.

Page Used to Maintain the Verity Thesaurus

Page Name	Object Name	Navigation	Usage
Maintain Verity Thesaurus	SAC_SRCH_THESAURUS	eProcurement, Administer Procurement, Maintain Supplier Integration Click the Maintain Verity Thesaurus link on the Maintain Supplier Integration page.	Create a new thesaurus or modify the existing thesaurus for item search.

Page Name

Object Name

Navigation

Usage

Maintain Verity Thesaurus

SAC_SRCH_THESAURUS

eProcurement, Administer Procurement, Maintain Supplier Integration

Click the Maintain Verity Thesaurus link on the Maintain Supplier Integration page.

Create a new thesaurus or modify the existing thesaurus for item search.

Maintaining the Verity Thesaurus

Access the Maintain Verity Thesaurus page.

Verity delivers a default thesaurus for each language. Each language has a file named VDk30.syd.

Append to Exiting Thesaurus	Add your own synonyms to the default thesaurus.
Replace Existing Thesaurus	Remove the existing copy of the default thesaurus, and replace it with your own.
Online Synonym List	Add a list of synonyms.
Custom Control File	When you have a large amount of synonyms to add, you can create a file instead of typing each one into the synonym list online.
More Info	Formatting instructions for the Online Synonym List and the Custom Control File.
Index Name	Identify the index using the thesaurus.
Language Code	Each language is delivered with its own default thesaurus. The language selected here identifies which default thesaurus is updated.
File Path	If you are using Custom Control Files, identify the file location here.
Synonym List	Enter the online list of synonyms.

Index Name	Enter a name for the index you are creating, or use the delivered index FDM_PV_ITEMCATALOG.
Build Option	Select the build method for the search index. The filtering criteria used depends on the method you select. The values are: Create New/Rebuild indicates that you are creating or rebuilding an index. You can limit the data retrieval by specifying a setID. Process Last Modified runs the process based on last modified incremental updates. Update All Items for a Vendor enables you to limit the update to a specific Vendor SetID or Vendor ID or both. Update Specific SetID or Items enables you to limit the update to a specific SetID or a range of Item IDs or both. Update by Other Criteria enables you to limit the update by giving value to any or all of these additional criteria: Source Data Object Record Name Field Name
Update/Reload Tree Table	Select to populate the table PV_CAT_TREE_TBL.
Source	If additional data filtering is needed, select to assign a source data object to the index.
Collection Language	Select a language code. You can index Verity for multiple languages; for example, English, Spanish, and Dutch. This makes it possible to support multiple languages in one system.
Index File Path	This display-only field is populated from the Application Configuration file. Note. Make sure that the collection is accessible to all applications servers and to the process scheduler server running this process.
Test Index	Click this link to determine whether there are entries in the index.