How To Fix OQ_E174 - No unprocessed records found in DBT

OQ_E174 - Overview

• Message type: E = Error

• Message class: OQ_E - IS-Oil SSR : Message pool Payment Card Processing

• Message number: 174

• Message text: No unprocessed records found in DBT

What causes this issue?

Either there are no unprocessed items in the DBT for creating a fleet
card settlement, or if changing a fleet card settlement, the DBT items
have already been archived and therefore cannot be further processed or
reversed.

System Response

<AB>The system cannot process any further.</>

How to fix this error?

For creating a settlement, check that the fleet card transactions have
been uploaded either by IDOC's or manually and have not already been
settled.
For changing fleet card settlements, re-load the items into the DBT
from the archive.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message OQ_E174 - No unprocessed records found in DBT ?

  The SAP error message OQ_E174: No unprocessed records found in DBT typically occurs in the context of the SAP system when dealing with data transfer or processing tasks, particularly in the context of the Data Transfer Workbench (DTW) or similar data processing tools.
  
  Cause:
  
  
  No Records Available: The primary cause of this error is that there are no unprocessed records available in the database table (DBT) that the system is trying to access. This could happen if:
  
  All records have already been processed.
  The records have been deleted or moved.
  The selection criteria used to fetch records do not match any existing records.
  
  
  
  Data Load Issues: If you are trying to load data into the system, it may indicate that the data load process did not complete successfully, or the data was not staged correctly.
  
  
  
  Configuration Issues: There may be configuration issues in the data processing setup that prevent records from being recognized as unprocessed.
  
  
  
  Solution:
  
  
  Check Data Availability: