How To Fix CBRC_REGCHECK088 - Data record (table &1) not found (key &2 = &3)

SAP Error Message - Details

• Message type: E = Error

• Message class: CBRC_REGCHECK - Messages for Substance-Related Regulation Check

• Message number: 088

• Message text: Data record (table &1) not found (key &2 = &3)

What causes this issue?

No data records were found for key &V2& = &V3& in table &V1&.
There are several possible causes:
You are tracking substance quantities with the program
<DS:RE.RREGCH_VT>Substance Volume Tracking: Tracking of Substance
Quantities.</>
The data record does not exist. However, from a logistical point of view
this is correct. You can ignore this error message in this case.
The data record no longer exists. For example, you are tracking old data
from previous years, for which some related data has been deleted. The
substance quantities cannot be determined without this data.
This message appears during the validation check of planned quantities
that is also executed by the program
<DS:RE.RREGCH_VT>Substance Volume Tracking: Tracking of Substance
Quantities</>. In this validation check, the message has the same
meaning as in the program
<DS:RE.RREGCH_PLAN_QUANT_CHECK>Substance Volume Tracking: Checking of
Planned Quantities</> (see below).
The data record was not read during data determination, because it was
filtered out by the selection criteria. Since the documents related to
this data record were read, the program expects this data record to
exist too. This message serves as a warning, in case too much data is
filtered out.
&EXAMPLE&:
The system determined a purchase order item. The related purchase order
header is required. However, the data determination module did not read
it, because it was filtered out by the selection criteria.
You are using the program
<DS:RE.RREGCH_PLAN_QUANT_CHECK>Substance Volume Tracking: Checking of
Planned Quantities</> to check whether invalid data records for planned
quantities exist in the system. If logistics documents for which
quantities were tracked have been physically deleted, the planned
quantities, which are now invalid, are also deleted. This message
provides information on which logistics documents have been deleted.
This check also takes into account the selection criteria you entered in
the IMG activity
<DS:SIMG.CBRC_SELECT_CRITERIA>Specify Selection Criteria for Volume
Tracking</>. This means that planned quantities become invalid and are
deleted when they no longer fulfill the selection criteria, for example,
when logistics documents are changed after substance volume tracking so
that they are no longer relevant for SVT according to the selection
criteria.
&EXAMPLE&:
You have created a purchase order that is relevant for substance volume
tracking according to the selection criteria. The program
<DS:RE.RREGCH_VT>Substance Volume Tracking: Tracking of Substance
Quantities</> determines the planned quantity correctly. You then change
the purchase order so that it is no longer relevant for substance volume
tracking according to the selection criteria. After this change, the
planned quantities in this purchase order are invalid and must be
deleted.

System Response

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

How to fix this error?

Check whether the data record exists. If it does not exist, find out
whether the substance quantities can still be determined correctly.
If the data record still exists, check whether the selection criteria
for volume tracking in Customizing are correct and meaningful. Also
check whether a change was made to the data record that led to the data
record no longer being relevant for substance volume tracking.
It may also be useful to check the modules for reading planned or
confirmed data that are specified in IMG activity <ZK>Specify Scenarios
</>.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CBRC_REGCHECK088 - Data record (table &1) not found (key &2 = &3) ?

  The SAP error message CBRC_REGCHECK088 indicates that a data record in a specified table could not be found using the provided key. This error typically arises in the context of SAP's Convergent Charging (CC) or Convergent Invoicing (CI) modules, where specific data records are required for processing.
  Cause:
  The error message is triggered when the system attempts to access a record in a database table (denoted by &1) using a key (denoted by &2 and &3), but the record does not exist. Common causes include:
  
  Data Deletion: The record may have been deleted or not created due to a previous error in the data processing workflow.
  Incorrect Key Values: The key values provided may be incorrect or not matching any existing records in the specified table.
  Configuration Issues: There may be issues with the configuration of the relevant module, leading to missing or incorrect data.
  Data Migration Issues: If data was migrated from another system, some records may not have been transferred correctly.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  Verify Key Values: Check the key values (&2 and &3) being used in the transaction or process. Ensure they are correct and correspond to existing records.
  Check Table Data: Use transaction codes like SE11 (Data Dictionary) or SE16 (Data Browser) to look up the specified table (&1) and see if the record exists. If it does not, you may need to create it or investigate why it is missing.
  Review Configuration: Ensure that the configuration settings for the relevant module are correct and that all necessary data has been set up properly.
  Data Consistency Checks: Run any available consistency checks or reports that can help identify missing or inconsistent data.
  Consult Logs: Check application logs (transaction SLG1) for any related error messages that might provide more context on why the record is missing.
  Contact Support: If the issue persists and you cannot identify the cause, consider reaching out to SAP support or your internal SAP team for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE11, SE16, SLG1, and others that can help you investigate the issue.
  Documentation: Review SAP documentation related to the specific module (Convergent Charging or Invoicing) for any known issues or additional troubleshooting steps.
  User Forums: Check SAP community forums or user groups for similar issues and solutions shared by other users.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.