Master Data Inquiry (Report /TRILLIUM/TRIMDIR00) - trillium_quality - 17.1

The report /TRILLIUM/TRIMDIR00 allows you to perform address validations and duplicate checks using external data sources.

To run /TRILLIUM/TRIMDIR00

1. Run the /TRILLIUM/TRIMDIR00 report by either:

   1. Running transaction /n/trillium/mdt and clicking on “Master Data Inquiry”.

   2. Running /sa38, entering the program name /TRILLIUM/TRIMDIR00 and clicking Execute to run the program.

      The Trillium Master Data Inquiry window opens.

      Figure 1. Trillium Master Data Inquiry

         

2. Select the Business Object - Customer, Vendor, or Business Partner.

   Note: For CRM implementations, only the Business Partner business object is available.

3. The fields in your source data must be mapped to the Trillium structure fields (/TRILLIUM/MDLOGL), which is referred to as the Target field. If a mapping definition does not exist for this data, see either:

   • Creating a Mapping Definition for an SAP Database.

   • Creating a Mapping Definition for an External Data Source.

   To use an existing mapping definition for an SAP Database Data Source:

   1. Click the SAP DB Data Source tab.
   2. Enter the Table name of the database table.
   3. Click , select a mapping definition from the Define Database Mapping window, and click to return to the Trillium Master Data Inquiry window.
   4. (Optional) Define criteria for filtering the source data by entering a field name and a value or range of values to be processed. Click to select a range.

   To use an existing mapping definition for an External Data Source:

   1. Click on the External Data Source tab.
   2. Select App. Server if the file is located on an Application Server; select local if the file is located on your local desktop.
   3. Enter the Absolute file path of the file to be used as the data source.
   4. Click , select a mapping definition from the Define File System Mapping window, and click to return to the Trillium Master Data Inquiry window.

4. In the Trillium Master Data Inquiry window’s Logging area, select Create new log or Overwrite existing log and enter a Log description.

5. Select the Message logging level to indicate what level of messages should be included in the log. The log entries vary depending on the type of processing:

   • In the case of address validation, messages are:

     • Errors: Messages of type E are logged.
     • Warnings: Messages of types E and W are logged.
     • All: All messages are logged, including the type S message “000” that indicates “Address was successfully checked.”

   • In the case of duplicate checking, messages are:

     • Errors or Warnings: Entries are only created for the records that have at least one duplicate.
     • All: Entries are created for all records, even if the number of duplicates is zero. The message “0 duplicates found” should be shown.

6. In the Parameter area, select the processes to be performed:

   • Address cleansing active - Address cleansing will be performed.

     • Include original addresses - The original address (before cleansing) will be included in the report.

   • Duplicate check active - Duplicate checking (matching) will be performed.

     • Execute for incorrect addresses - Duplicate check should be performed even if the address cleansing has failed.

   • Threshold for duplicate check - Enter the level of matching that will define a duplicate. Only records matching at this level or higher will be included in the duplicate check results.

   • Display log upon completion - Indicate whether the log should be displayed when address validation and/or duplicate checking is completed. The log should be displayed in a:

     • List View (simple list), which is optimized to show the result of address validation, including display of original addresses.

     • Tree View (hierarchy), which is optimized to show the results of duplicate checks.

   • Max. records - Enter the maximum number of records to be processed.

7. Click Execute  to begin address validation and/or duplicate checking. If both processes are performed, address validation is performed before duplicate checking.The results of the job are stored in the table /TRILLIUM/MDLOGL and can be displayed upon completion of processing, or can be displayed at a later time via Display Log Files (/TRILLIUM/TRIMDIR10).