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

SAP Error Message - Details

• 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.

Smart SAP Assistant

• What is the cause and solution for SAP error message FMCA_INCORR122 - Reversed request already exists for contract object &1 for period &2 ?

  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 reversed the request while another is attempting to do the same.
  
  Solution:
  
  Check Existing Reversals: Review the contract object and the specified period to confirm if a reversal has already been processed. You can do this by checking the transaction history or logs related to the contract.
  Avoid Duplicate Actions: Ensure that you are not attempting to reverse a transaction that has already been reversed. If a reversal is needed, confirm the status of the previous reversal.
  Consult with Finance Team: If you are unsure about the status of the transactions, consult with your finance or accounting team to verify the correct state of the contract and any related transactions.
  Error Handling: If you believe this error is incorrect (e.g., if you have not reversed the transaction), you may need to investigate further into the system logs or consult SAP support for assistance in resolving potential data integrity issues.
  Transaction Codes: Use relevant transaction codes (like FMCA or others related to contract management) to navigate and check the status of the contract and its transactions.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common errors.
  Documentation: Review SAP documentation related to contract management and financial transactions to understand the processes and how reversals are handled.
  User Forums: Engage with SAP user communities or forums where similar issues may have been discussed, and solutions shared.
  
  If the problem persists after following these steps, it may be necessary to escalate the issue to your SAP support team or consult with SAP directly for more in-depth troubleshooting.