How To Fix FDM_MIRROR061 - Dunning block for substitute system has been created


SAP Error Message - Details

  • Message type: E = Error

  • Message class: FDM_MIRROR - Mirror System Messages

  • Message number: 061

  • Message text: Dunning block for substitute system has been created

  • Show details Hide details


  • Self-Explanatory Message

    Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

    To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

    Unfortunately, there isn't any extra information in this error notice.



    What else can you do?

    First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

    Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

    You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.


Smart SAP Assistant

  • What is the cause and solution for SAP error message FDM_MIRROR061 - Dunning block for substitute system has been created ?

    The SAP error message FDM_MIRROR061 indicates that a dunning block has been created for a substitute system. This typically occurs in the context of financial accounting and dunning processes within SAP, particularly when dealing with accounts receivable and the management of overdue invoices.

    Cause:

    1. Dunning Block Configuration: The dunning block may have been configured in the system for specific customers or accounts. This can happen if the customer has a dispute, is under negotiation, or if there are other reasons for not pursuing dunning.
    2. Substitute System: The error specifically mentions a "substitute system," which may refer to a scenario where a customer account is being processed in a different system (e.g., a subsidiary or a different company code) that has its own dunning rules or blocks.
    3. Data Synchronization Issues: If there are issues with data synchronization between the main system and the substitute system, it may lead to the creation of dunning blocks that are not intended.

    Solution:

    1. Review Dunning Block Settings: Check the dunning block settings for the specific customer or account in question. You can do this by navigating to the customer master data and reviewing the dunning information.
    2. Check Substitute System Configuration: If the account is linked to a substitute system, ensure that the dunning settings in that system are correctly configured and aligned with the main system.
    3. Remove Dunning Block: If the dunning block is no longer applicable, you can remove it manually. This can typically be done in the customer account settings or through the dunning run transaction.
    4. Consult with Finance Team: If you are unsure about the implications of removing a dunning block, consult with your finance or accounting team to ensure that it aligns with company policies.
    5. System Logs and Monitoring: Check system logs for any additional error messages or warnings that may provide more context about why the dunning block was created.

    Related Information:

    • Dunning Process: Understand the dunning process in SAP, which involves sending reminders to customers for overdue payments. Familiarize yourself with the dunning levels and how they are configured.
    • Customer Master Data: Review the customer master data to ensure that all relevant information is accurate and up to date.
    • SAP Notes and Documentation: Look for SAP Notes related to the error message or the dunning process for any patches or updates that may address known issues.
    • Transaction Codes: Familiarize yourself with relevant transaction codes such as FD10N (Display Customer Balance), F150 (Dunning), and FD02 (Change Customer) to manage customer accounts and dunning processes effectively.

    If the issue persists after following these steps, consider reaching out to SAP support for further assistance.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant