How To Fix FMFG_RECON_E011 - Match at lowest detail level only when using stored results

FMFG_RECON_E011 - Overview

• Message type: E = Error

• Message class: FMFG_RECON_E - Reconciliation Tool message class

• Message number: 011

• Message text: Match at lowest detail level only when using stored results

What causes this issue?

You are using the saved results of a previous reconciliation report.
The stored results do not include the data required to drill down on
individual amounts or to perform matching at any of the subtotal levels
in the report. However, you CAN use the <ZK>Match</> function on the
detail level entries in the report to find the items that do not
reconcile.

System Response

None

How to fix this error?

Use the <ZK>Match</> function at detail level rows in the report to
examine the out of balance items.

Procedure for System Administrators

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 FMFG_RECON_E011 - Match at lowest detail level only when using stored results ?

  The SAP error message FMFG_RECON_E011 typically occurs in the context of the Funds Management (FM) module when there is a mismatch in the reconciliation process. This error indicates that the system is attempting to match data at a level of detail that is not supported due to the stored results being used.
  
  Cause:
  The error arises when:
  
  Mismatched Detail Levels: The system is trying to reconcile data that has been stored at a higher level of aggregation than what is available for matching. For example, if the stored results are summarized at a higher level (like a total for a cost center) but the reconciliation process is trying to match at a more detailed level (like individual line items).
  
  Configuration Issues: There may be configuration settings in the Funds Management module that dictate how data is stored and matched, which could lead to this error if not set up correctly.
  Data Integrity Issues: There may