How To Fix KE008 - Programm error: RKE_CHECK_GENERATION called recursively

SAP Error Message - Details

• Message type: E = Error

• Message class: KE -

• Message number: 008

• Message text: Programm error: RKE_CHECK_GENERATION called recursively

What causes this issue?

A program error has occurred. Function module RKE_CHECK_GENERATION is
carried out recursively. This is not allowed.

How to fix this error?

Contact the SAP hotline. Include a copy of the dump in your problem
message, since this is needed to analyze the problem.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message KE008 - Programm error: RKE_CHECK_GENERATION called recursively ?

  The SAP error message KE008, which states "Program error: RKE_CHECK_GENERATION called recursively," typically occurs in the context of the Controlling (CO) module, particularly when dealing with cost center accounting or internal orders. This error indicates that a function or program is being called recursively in a way that is not intended, leading to a stack overflow or similar issue.
  Causes:
  
  Recursive Function Calls: The error is often caused by a recursive call in the program logic that does not have a proper exit condition, leading to infinite recursion.
  Configuration Issues: Incorrect configuration in the controlling area or cost center settings may lead to unexpected behavior in the program.
  Data Inconsistencies: Inconsistent or corrupted data in the database tables related to controlling can trigger this error.
  Custom Code: If there are custom enhancements or modifications in the standard SAP code, they might inadvertently cause recursive calls.
  
  Solutions:
  
  Check for Infinite Loops: Review the code or logic that leads to the RKE_CHECK_GENERATION function. Ensure that there are proper exit conditions to prevent infinite recursion.
  Review Configuration: Verify the configuration settings in the controlling area, cost centers, and any related settings to ensure they are set up correctly.
  Data Consistency Check: Run consistency checks on the relevant CO data to identify and correct any inconsistencies. This can often be done using transaction codes like KAH3 (for cost centers) or KSB1 (for cost center reports).
  Debugging: If you have access to the ABAP debugger, you can set breakpoints in the RKE_CHECK_GENERATION function to trace the execution flow and identify where the recursion is occurring.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates that resolve known issues.
  Consult SAP Support: If the issue persists and you cannot identify the cause, consider reaching out to SAP Support for assistance. Provide them with detailed information about the error, including transaction codes, steps to reproduce, and any relevant logs.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes in the CO module, such as KSB1 (Cost Centers: Actual Line Items), KAH3 (Display Cost Center), and KSV5 (Display Plan/Actual Comparison).
  SAP Community: Engage with the SAP Community forums where other users may have encountered similar issues and can provide insights or solutions.
  Documentation: Review SAP documentation related to the CO module for best practices in configuration and troubleshooting.
  
  By following these steps, you should be able to identify the root cause of the KE008 error and implement a solution to resolve it.