How To Fix UCF6870 - Matching of activity numbers cannot be executed

SAP Error Message - Details

• Message type: E = Error

• Message class: UCF6 - Messages for Consolidation of Investments

• Message number: 870

• Message text: Matching of activity numbers cannot be executed

What causes this issue?

Matching of activity numbers cannot be executed because the customizing
settings in the location of values for consolidation of investments are
set so that the investment or equity data is read from the totals
database.
The totals database does not contain the activity number. If the
investment or equity data is read from totals data, matching of activity
numbers is not necessary.
If the investment data is located in the additional financial data and
the equity data is read from both the totals database and the additional
financial data, you can run matching of activity numbers for those
activities that are triggered by additional financial data.

System Response

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

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 UCF6870 - Matching of activity numbers cannot be executed ?

  The SAP error message UCF6870, which states "Matching of activity numbers cannot be executed," typically occurs in the context of SAP's Controlling (CO) module, particularly when dealing with activity-based costing or internal orders. This error indicates that there is an issue with the matching of activity numbers, which can arise from various reasons.
  Causes:
  
  Missing Activity Types: The activity type you are trying to match may not be defined in the system or may not be assigned to the relevant cost center or internal order.
  Incorrect Configuration: There may be configuration issues in the controlling area or the cost center settings that prevent the matching process.
  Data Inconsistencies: There could be inconsistencies in the master data, such as missing or incorrect entries in the activity type or cost center master records.
  Period Closing: If the period is closed, it may prevent any further postings or matching activities.
  Authorization Issues: The user may not have the necessary authorizations to perform the matching operation.
  
  Solutions:
  
  Check Activity Types: Ensure that the activity types you are trying to use are correctly defined and assigned to the relevant cost centers or internal orders.
  Review Configuration: Go through the configuration settings in the Controlling module to ensure that everything is set up correctly. This includes checking the assignment of activity types to cost centers and ensuring that the controlling area settings are correct.
  Validate Master Data: Check the master data for any inconsistencies. Ensure that all necessary entries are complete and correct.
  Open Periods: If the error is related to period closing, check if the period is open for posting. If necessary, consult with your finance team to open the period.
  Check Authorizations: Verify that the user has the necessary authorizations to perform the matching operation. If not, contact your SAP security team to adjust the authorizations.
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like KP26 (Activity Type Planning) or KSU5 (Actual Activity Allocation) to review and adjust settings.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Documentation: Refer to SAP documentation for detailed information on activity-based costing and internal order management.
  
  If the issue persists after checking the above points, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.