How To Fix FR682 - Reclassification reset only poss. for each object type/account/currency

SAP Error Message - Details

• Message type: E = Error

• Message class: FR - Messages for FI Reporting

• Message number: 682

• Message text: Reclassification reset only poss. for each object type/account/currency

What causes this issue?

You run the program to reset the reclassification. The selection
parameters "Identifier of the Valuation Object" and/or "Identifier of
the Valuation Subobject" are filled in the selection variant.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

In the reclassification reset mode, the original documents of the
reclassification run are selected and reversed based on their history.
In this context, it is not possible to perform a reversal for individual
valuation objects because the documents of the reclassification run are
created for each object type, foreign currency, and G/L account. A
reclassification document can therefore contain the amounts of multiple
valuation objects.

System Response

When the reclassification is reset, the selection parameters for
selecting individual valuation objects (identifier of the valuation
object) are not considered. The reclassification reset and associated
reversal take place at the level of the original reclassification
document and, therefore, for each object type, foreign currency key, and
G/L account.

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FR682 - Reclassification reset only poss. for each object type/account/currency ?

  The SAP error message FR682 ("Reclassification reset only possible for each object type/account/currency") typically occurs in the context of financial accounting and controlling when attempting to perform a reclassification of financial data. This error indicates that the system is unable to process the reclassification because it is not set up to handle multiple object types, accounts, or currencies simultaneously.
  Cause:
  
  Object Type/Account/Currency Mismatch: The reclassification process is being attempted on multiple object types, accounts, or currencies at the same time, which is not allowed.
  Incorrect Configuration: The configuration settings in the SAP system may not allow for the reclassification of certain combinations of object types, accounts, or currencies.
  Data Integrity Issues: There may be inconsistencies or issues with the data that prevent the reclassification from being processed correctly.
  
  Solution:
  
  Single Object Type/Account/Currency: Ensure that the reclassification is being performed for a single object type, account, and currency. If you need to reclassify multiple items, do so one at a time.
  Check Configuration: Review the configuration settings in the SAP system related to reclassification. Ensure that they are set up correctly to allow for the types of reclassification you are attempting.
  Data Validation: Validate the data you are trying to reclassify. Ensure that there are no inconsistencies or errors in the data that could be causing the issue.
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on the reclassification process and any limitations that may apply.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error message or provide additional guidance on resolving it.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with the relevant transaction codes used for reclassification in SAP, such as transaction codes for financial accounting (FI) or controlling (CO).
  User Roles and Authorizations: Ensure that the user attempting the reclassification has the necessary roles and authorizations to perform the action.
  SAP Support: If the issue persists, consider reaching out to SAP support or your internal SAP support team for further assistance.
  
  By following these steps, you should be able to identify the cause of the FR682 error and implement a solution to resolve it.