How To Fix FMCA_INCORR122 - Reversed request already exists for contract object &1 for period &2

FMCA_INCORR122 - Overview

• Message type: E = Error

• Message class: FMCA_INCORR - Messages for Inbound Correspondence

• Message number: 122

• Message text: Reversed request already exists for contract object &1 for period &2

What causes this issue?

An inbound correspondence request already exists for business partner
&V3&, contract account &V2&, and contract object &V1& for period &V2&.
This inbound correspondence request has been reversed.

System Response

If a reversed request exists, you cannot create a new inbound
correspondence request using the <LS>Generate Inbound Correspondences</>
mass activity (transaction FMCAM1).

How to fix this error?

Choose one of the following alternatives:
Create a new inbound correspondence request manually using transaction
PSOBWORK or FMCAINCOH.
Reset the reversal in transaction PSOBWORK or FMCAINCOH.

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.

FMCA_INCORR122 - Details

• The SAP error message FMCA_INCORR122 indicates that there is an issue with a reversed request that already exists for a specific contract object and period. This error typically arises in the context of contract management or financial transactions where a reversal of a request (like a payment or a commitment) is being attempted, but the system has detected that a reversal for that same contract and period has already been processed.
  
  Cause:
  
  Duplicate Reversal Request: The most common cause is that a reversal request for the same contract object and period has already been executed. This could happen if the user attempts to reverse a transaction that has already been reversed.
  Data Integrity Issues: There may be inconsistencies in the data, such as incorrect entries or missing records that lead to the system recognizing a reversal that should not exist.
  Timing Issues: If multiple users are processing transactions simultaneously, one user may have already