Understanding the Search Framework Search Engine

The Oracle Search Framework eearch 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 Search Framework 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 Search Framework collection, they can be searched and browsed for PeopleSoft eProcurement.

The Search Framework search engine consists of these components:

Field or Control


Search Collection

A collection is a language-specific directory or folder that contains multiple subdirectories. These subdirectories contain various kinds of files used by the Search Framework search engine during indexing and searching.

Note: These files are created based on a snapshot of the data in the specified record or field.

Search Field

A field indexed into a search collection can be searched using word searching or comparison searching. For example, if you wanted to search on items priced less that $20.00 USD, Price must be in the index as a field. The value indexed in an Search Framework field can be returned to an application using the Search Framework results framework.


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 search collection for searching purposes only. Information indexed in a zone can't be returned to the calling application. Comparison searching cannot 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 collection is a group of fields that you set up that is used by the Search Framework 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 search index collections. Searches are then performed against this collection. Items loaded from a CUP process can be indexed directly into the collection by selecting the Index Items check box, or by selecting PV_CUP_ITEMS as the data source on the Build eProcurement Search Collection page.

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

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

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

See the product documentation for

PeopleTools: Search Technology

Understanding Financials and Supply Chain Search