Index Queue Processing - trillium_quality - 17.2

Trillium Quality for SAP Reference Guide

Product type
Software
Portfolio
Verify
Product family
Trillium
Product
Trillium > Trillium Quality
Version
17.2
Language
English
Product name
Trillium Quality
Title
Trillium Quality for SAP Reference Guide
First publish date
2008
Last updated
2024-04-08
Published on
2024-04-08T11:11:33.467656

If the connection between SAP and the TS Connector is lost, you can  continue with the record create/modify processes in SAP, however the records being processed will not be postal validated and window keys will not be created. Once saved, information about these records is stored in a Trillium Quality customized table called /TRILLIUM/IDXQUE, awaiting the Index Queue program to run so that search indexes can be created for them.

You can run the /TRILLIUM/IDXQUE report at any time; however, we recommend that you schedule it to run at least once a day to ensure that the suspended records are processed for ongoing Duplicate Check and Fuzzy/Rough Search.

 

Information about suspended records is stored in the /TRILLIUM/IDXQUE table by person number and address number for the relevant application tables and fields. You can view this table via transaction /nSE11 or /nSE16.

Note: In some instances, such as when trying to run a duplicate check during External List Management (ELM), a message similar to the following will be displayed indicating that window keys were not generated for some records and the records have been written to the IDXQUE table:
Search Index for Index Pool BUT000 PARTNER not set up completely
Note:    Review the records in IDXQUE to determine whether your window key rules should be modified, then run /TRILLIUM/RSADRIDXQUE to clear the records from the IDXQUE. /TRILLIUM/RSADRIDXQUE should be run in the background.

 

Figure 1. /TRILLIUM/IDXQUE Table Entries /TRILLIUM/IDXQUE Table Entries

To initialize the search indexes queue

  1. Call the /TRILLIUM/RSADRIDXQUE program by either:

    • Using transaction /nSA38 – ABAP Editor

    • Selecting ABAP Editor from the SAP Tools menu (Tools > ABAP workbench > Development > ABAP Editor).

    The Report Calling window opens.

  2. Enter the program name /TRILLIUM/RSADRIDXQUE in the Program field and click to execute the program.

    The Search Index Queue Selection window opens.

  3. Enter the required parameters, as described in the table below.

  4. Submit the report online by clicking or submit it as a background job by selecting Program > Execute in Background.

    Figure 2. Trillium Search Index Queue Selection Window Trillium Search Index Queue Selection Window
    Table 1. Index Queue Selection Window Fields

    Field name

    Values

    Description

    Package size

    Numeric

    Number of addresses that are read from the address master and saved at any time. The package size should only be reduced if there are issues with the working memory during the process. Optional

    Produce detail listing

    Yes/No

    Default is unchecked. Check the selection to run the report to produce detail listing.

    Test mode (no updates)

    Yes/No

    Default is checked. Uncheck the selection to run and update the database table with created indexes.

  5. After the report is processed, a summary report opens. This report displays the number of rows to be updated.

    Figure 3. Trillium Search Index Queue Summary Report Trillium Search Index Queue Summary Report
  6. If you selected the Produce Detail Listing option on the report selection window, click twice to view the detail listing. The table below describes the columns that appear in the detail listing.

Figure 4. Trillium Search Index Queue Details Report Trillium Search Index Queue Details Report
Table 2. Trillium Search Index Queue Detail Report Fields

Field name

Description

Error Message

Error message text for the record listed.

Addr. No

Internal key for identifying a Business Address Services address.

Person

Internal key for identifying a person in Business Address Services.

Type

Address type (1=Organization, 2=Person, 3=Contact person).

BusPartner

Key identifying a Business Partner. The key is unique within a client.

Customer

Customer alphanumeric unique key which identifies the customer within a client.

Partner

The number that identifies the contact person.

Vendor

Vendor alphanumeric unique key which identifies the vendor within a client.

Plant

Plant alphanumeric unique key which identifies the plant within a client.