How To Fix FMCA_ISR_EN170 - ***170-200 reversed for correspondences

SAP Error Message - Details

• Message type: E = Error

• Message class: FMCA_ISR_EN -

• Message number: 170

• Message text: ***170-200 reversed for correspondences

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 FMCA_ISR_EN170 - ***170-200 reversed for correspondences ?

  The SAP error message FMCA_ISR_EN170, which states "***170-200 reversed for correspondences," typically occurs in the context of the SAP Financial Management (FM) module, particularly when dealing with budgetary control and correspondence management.
  Cause:
  This error usually indicates that there is a mismatch or inconsistency in the correspondence settings or configurations between the budgetary items (170) and the actual items (200). It can occur due to:
  
  Incorrect Configuration: The settings for budgetary control or correspondence types may not be properly configured.
  Data Entry Errors: There may be incorrect entries in the budget or actual postings that lead to this inconsistency.
  Missing Correspondence: The system may be expecting a correspondence that has not been set up or is missing.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Configuration:
  
  Review the configuration settings for budgetary control and correspondence types in the SAP system. Ensure that the settings for the budget (170) and actual (200) correspondences are correctly defined.
  Use transaction codes like SPRO to access the configuration settings.
  
  
  
  Review Data Entries:
  
  Check the entries related to the budget and actual postings. Ensure that they are correctly entered and that there are no discrepancies.
  Use transaction codes like FMBB (for budget entries) and FMAVCR01 (for actuals) to review the relevant data.
  
  
  
  Check Correspondence Settings:
  
  Ensure that the correspondence types are correctly defined and that there are no missing links between the budget and actual items.
  You can check the correspondence settings using transaction codes like FMC1 (for correspondence types).
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for specific guidance on the error message and its implications.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. They may provide insights based on the specific configuration and version of your SAP system.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FMBB, FMAVCR01, FMC1, and SPRO for configuration and data review.
  SAP Notes: Check for any SAP Notes related to this error message, as they may provide patches or additional guidance.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.