Building an Index

To submit a search definition to be indexed, or built, use the Schedule Search Index page (PeopleTools, Search Framework, Administration, Schedule Search Index). Assign a name that reflects the index you are building. If more than one user is building a particular index, each person must create their own run control.

From the Build Search Index run control page:

  • The Search Definition field, lookup option, lists only search definitions that have been deployed.

  • The indexing type must be selected:

    • A full index is a complete rebuild of an index that removes old data and applies completely new data to the index.

      For performance reasons, full indexes should not occur where there are large amounts of data.

    • An incremental index is used to update an existing index, remove old obsolete records, and add new records that were modified or added since the last index build.

      The indexed document retains a date and time at the header level, which is updated from various pages, transactions, and batch jobs each time the header or child record changes. If a previous build of the index has occurred, information pertaining to the last build is displayed on the run control page. Incremental indexes are typically more efficient than a full index when there is a large amount of data.

      Note: As of FSCM Update Image 54, the Incremental Index process picks up changes to setup tables and all support tables that are effective dated.

  • When search results change often, incremental index builds should be run nightly or whenever the system is lightly used.

    Note:

    As of Update image 55, PeopleSoft applications delivered data to support the Tools Automatic Incremental Indexing process which helps you set and forget your incremental builds. This process is supported in Tools 8.62 and above. For additional information about PeopleSoft Search, see My Oracle Support Doc ID 2205540.2, tracking group PeopleTools Features / Auto Incremental Indexing for Tools 8.62 and above.

    This keeps the search data current. However, there are some exceptions that require the index to be rebuilt. This can include:

    • Related data changes, such as a buyer’s name, which is not updated in locations where the buyer ID is stored.

    • Effective dated information where correction mode is used against an existing date and no new effective date is created.

Note:

With the advent of Real Time Indexing you may not need to use incremental builds. See Understanding Real Time Indexing in FSCM to see if a delivered search definition is certified for use with RTI.

For more information about the Build Search Index page, see the PeopleTools: PeopleSoft Search Technology, Administering PeopleSoft Search Framework, Working with Search Indexes.