How To Fix DPR_FIN_GECCO026 - Error occurred in accounting - check the costing in the SAP S/4 system

SAP Error Message - Details

• Message type: E = Error

• Message class: DPR_FIN_GECCO - Messages for Accounting Integration

• Message number: 026

• Message text: Error occurred in accounting - check the costing in the SAP S/4 system

What causes this issue?

Errors occurred in costing in the SAP S/4HANA system.

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?

Check the costing log for costing in the SAP S/4HANA system:
Call costing:
If it is preliminary costing, the hyperlink for calling the <LS>ad hoc
cost estimate</> can be found in the <LS>Costing</> view.
If it is costing for an account assignment object (after transfer), the
hyperlink for calling <LS>Easy Cost Planning</> can be found in the
<LS>Services</> view.
In costing, choose <LS>Revaluate All Items</>. The costing log is then
generated with the error messages.

Procedure for System Administrators

This message has the number DPR_FIN_GECCO026.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message DPR_FIN_GECCO026 - Error occurred in accounting - check the costing in the SAP S/4 system ?

  The SAP error message DPR_FIN_GECCO026 indicates that there is an issue with the accounting process related to project costing in the SAP S/4HANA system. This error typically arises during the execution of financial transactions or when trying to post costs to a project.
  Cause:
  
  Costing Issues: The error may occur if there are inconsistencies or errors in the cost planning or actual costing for the project. This could be due to incorrect cost elements, missing cost estimates, or issues with the assignment of costs to the project.
  Master Data Issues: Problems with master data, such as incorrect project definitions, cost centers, or internal orders, can lead to this error.
  Configuration Issues: Incorrect configuration settings in the controlling (CO) module or project system (PS) module can also trigger this error.
  Authorization Issues: Lack of proper authorizations for the user trying to perform the transaction can lead to this error.
  Integration Issues: If there are issues with the integration between different modules (e.g., between Project System and Controlling), it can result in this error.
  
  Solution:
  
  Check Costing Data: Review the costing data for the project. Ensure that all necessary cost estimates are in place and that they are correctly assigned to the project.
  Review Master Data: Verify the master data related to the project, including project definitions, cost centers, and internal orders. Ensure that all relevant data is correctly maintained.
  Configuration Review: Check the configuration settings in the CO and PS modules. Ensure that all necessary settings are correctly configured for project costing.
  Authorization Check: Ensure that the user has the necessary authorizations to perform the transaction. If not, work with your SAP security team to grant the required permissions.
  Error Logs: Check the system logs for any additional error messages or details that can provide more context about the issue. Use transaction codes like SLG1 (Application Log) to find relevant logs.
  Consult Documentation: Refer to SAP documentation or notes related to the error message for any specific guidance or patches that may address the issue.
  Testing: If changes are made, conduct thorough testing to ensure that the issue is resolved and that no new issues are introduced.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CJ20N (Project Builder), CJI3 (Actual Cost Line Items), and KP06 (Cost Center Planning) to analyze and manage project costs.
  SAP Notes: Search for SAP Notes related to the error message DPR_FIN_GECCO026 in the SAP Support Portal for any known issues or fixes.
  Community Forums: Engage with SAP community forums or user groups to see if others have encountered similar issues and what solutions they found effective.
  
  If the issue persists after following these steps, it may be necessary to involve your SAP support team or consult with an SAP expert for further investigation.