Page tree
Skip to end of metadata
Go to start of metadata


The purpose of this page is to help understand the /FLDQ/RSADRINIBM report.  


The /FLDQ/RSADRINIBM report has two major functions. 

The first is the creation of match codes.  The match code creation is used for the prevention of duplicate records being added to to the system.  When the report is run, it creates codes that are later committed to a database table for use during transactional processing of records to identify potential duplicates before they are saved to the database.  These match codes need to be in place before the system goes live.  

The report is also used to perform batch matching on all of the records selected from the index pool as they exist in the database at the time the report is run.  This will provide you with a a list of potential duplicates that already exist in the database.  

Each separate option in the report can be run individually or they can all be run at the same time.  The Commit Dup Check Match Codes is the option that requires no users on the system.

To run the report select transaction  SA38 and enter the report name: /FLDQ/RSADRINIBM

Program options

Multi-process settings based on available resources

This section is for configuring the report to either allow it to consume all the available resources or limit the resources that it uses when it runs. 

Index Creation

This section is for selecting the records from the active index pool.  This option needs to be run to build the index for use later in the report.  

The active index pools are displayed based on how they have been configured on the SAP System.  

To change the active index pool:

Use transaction SPRO to access the IMG structure. Then locate the following IMG transaction, depending on which Basis version you use:

    • SAP Web Application ServerApplication ServerBasis ServicesAddress ManagementDuplicate Check
    • SAP NetWeaverApplication ServerBasis ServicesAddress ManagementDuplicate Check

Match Code

The Match Code option of the /FLDQ/RSADRINIBM report needs to be run before the system is active.  It is designed so that all of the records in the active index pools inside of SAP are selected and passed to the data quality server for processing following the business rules defined in the configuration of the match process.  This will generate a match code, also known as a break key, for all records in the system based on the option that you select for generating the match codes. 

The Create Match Codes is the option in the report that helps configure the system for interactive processing will help you locate duplicates in your system as the business user enters new records into the system.   Without running the Create Match Codes step, when a new record is added to the SAP system, the record would not be found as a potential duplicate to any record in the system even if it is an exact duplicate.  This is because the new record will get a match code generated while it is being added, but the database or current customers would not contain a corresponding match code to be selected to be compared as a potential duplicate. 

Sometimes, during testing, users find that the record that they expected to come up as a duplicate is not found even if the match code creation was run.   If this would occur, the first thing to examine would be if the two records have the same match code.  If they do not, the report would need to be run again with an option that would give them the same match code.  If they do have the same match code, you would then need to look at the number of records that contain the same code, and likely select a new option that will give you a smaller candidate set, if the number of records with that match code is large.  

Duplicate Check (transactional) Match Code

The Commit Dup Check Match Codes is the option that takes the staged records created from the Create Match Codes section and moves them into the table that is used for transactional processing.  This commit step also has to be completed prior to your go-live.  The key configuration to be successful with this portion of the report is that it needs to be run when there are no users on the system.  The report has been broken out into the individual pieces to help shorten the system down-time.  It allows you to perform business as usual as the codes are being created and only stop the processing for this much faster process.

Batch Match

The perform batch match portion of the report will identify the duplicates that are currently existing in the SAP database, based on the Index pool selected for deduplication in the IMG settings.  There are differences in how the report is run and where and how the business rules to identify the matches are configured depending on the engine being used to process your data.  The DQM for SAP Users Guide for the engine being used for processing (HANA SDQ or Data Services) has more detail in how to configure the product to meet your business needs.  The settings for how confident the software is that a duplicate is located is a configurable setting.  

The perform batch match is not required as an initialization step, but it is recommended that the duplicates that exist in the database be resolved.  Ideally the fewer duplicates that exist in the database, the better results you will get when a user enters a record interactively.  This report will return the potential duplicates back to the SAP system, where another report (FLDQ/AD_DISPL_BATCH_MATCH) can be run to display the duplicates. 

Ideally once the existing duplicates have been resolved, the report wouldn’t need to be rerun unless there were a number of records added to the database where deduplication was not performed as they were added or the business rules were modified. 

Related Content

Related Documents  

Create Match Code Performance Considerations 

Related Notes 

  • No labels