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


The product offers the flexibility of multiple engines for processing, to give the user the ability to determine what processing engine should be called in what situation.  What can end up happening is that the engine configuration is not set the way it needs to be set to function as expected, causing errors in the error log.   For example, you will see error in the error log for RFC servers or an error on an unexpected Engine class.  


Understanding the configuration of the /FLDQ/DQ_ENGINES table:


Simplest configuration

For a environment where processing is expected to be performed only on HANA using SAP HANA Smart Data Quality engine, the DQ Engines (/FLDQ/DQ_ENGINES) table would be configured with a single line.

The Country would be blank, indicating all countries. 

The DQ Operation would be blank indication all operations

and the DQ_ENGINE would contain /FLDQ/CL_DQ_ENGINE_HANA_TASK


Valid entries:

Other combinations are valid, if a hybrid situation is being used.  

Valid entries for the DQ Engines section of the table are:

  • /FLDQ/CL_DQ_ENGINE_DQAAS is the DQMmicroservice for Location Data engine
  • /FLDQ/CL_DQ_ENGINE_HANA_TASK is the HANA engine
  • /FLDQ/CL_DQ_ENGINE_DS is the Data Services engine



Valid entries for the DQ Operation are:

  • GEO - for Geocoding process
  • MATCH - for Deduplication functionality also known as DES in SAP
  • NAME - for Firm and Name cleansing
  • PV - for Postal Validation
  • PV_BATCH for Batch Postal validation for the DQMMicroservice engine


Complex configuration:

The screenshot below is an example of  how multiple engines can be configured.    When you see more than one entry in the table, its important to understand what is being called.    This screenshot, will only call the HANA TASK engine for Postal Validation for both transactional and batch processes for all countries.  Note that the blank DQ_OPERATION has the DQ_ENGINE set to /FLDQ/CL_DQ_ENGINES_DS along with the MATCH and NAME operations.  These will throw errors in an environment where all processing is expected to be performed on HANA, as typically the Data Services configuration has not been completed.  This configuration is not common as most processing is done all on HANA or all on Data Services.  The most common hybrid configuration involves the use of the Microservice engine (/FLDQ/CL_DQ_ENGINE_DQAAS)  for postal validation and geocoding for specific countries.  

To change this table to process everything on HANA, you would run transaction SM30, on the table /FLDQ/DQ_ENGINES.  Delete the entries with the DQ_OPERATIONS populated.   This will leave you with just the single entry with the blank DQ_OPERATION (applies to all).  Maintain that entry and change the DQ_ENGINE TO /FLDQ/CL_DQ_ENGINES_HANA_TASK 



  • No labels