SAP Message CBRC_REGCHECK088 - Data record (table &1) not found (key &2 = &3)

Diagnosis
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
  • Substance Volume Tracking: Tracking of SubstanceQuantities.
    The data record does not exist. However, from a logistical point of viewthis is correct. You can ignore this error message in this case.
    The data record no longer exists. For example, you are tracking old datafrom previous years, for which some related data has been deleted. Thesubstance quantities cannot be determined without this data.
    This message appears during the validation check of planned quantitiesthat is also executed by the program Substance VolumeTracking: Tracking of Substance Quantities from SAP Note 1317261. Inthis validation check, the message has the same meaning as in theprogram Substance Volume Tracking:Checking of Planned Quantities (see below).
    The data record was not read during data determination, because it wasfiltered out by the selection criteria. Since the documents related tothis data record were read, the program expects this data record toexist too. This message serves as a warning, in case too much data isfiltered out.
    Example:
    The system determined a purchase order item. The related purchase orderheader is required. However, the data determination module did not readit, because it was filtered out by the selection criteria.
    • You are using the program Substance
    • Volume Tracking: Checking of Planned Quantities to check whetherinvalid data records for planned quantities exist in the system. Iflogistics documents for which quantities were tracked have beenphysically deleted, the planned quantities, which are now invalid, arealso deleted. This message provides information on which logisticsdocuments have been deleted. From SAP Note 1317261, this check alsotakes into account the selection criteria you entered in the IMGactivity Specify Selection Criteria forVolume Tracking. This means that planned quantities become invalidand are deleted when they no longer fulfill the selection criteria, forexample, when logistics documents are changed after substance volumetracking so that they are no longer relevant for SVT according to theselection criteria.
      Example:
      You have created a purchase order that is relevant for substance volumetracking according to the selection criteria. The programSubstance Volume Tracking: Tracking of SubstanceQuantities determines the planned quantity correctly. You then changethe purchase order so that it is no longer relevant for substance volumetracking according to the selection criteria. After this change, theplanned quantities in this purchase order are invalid and must bedeleted.

      Procedure
      Check whether the data record exists. If it does not exist, find outwhether the substance quantities can still be determined correctly.
      If the data record still exists, check whether the selection criteriafor volume tracking in Customizing are correct and meaningful. Alsocheck whether a change was made to the data record that led to the datarecord no longer being relevant for substance volume tracking.
      It may also be useful to check the modules for reading planned orconfirmed data that are specified in IMG activity Specify Scenarios
      .