How To Fix CTE_FND_POSTING026 - No change log(s) found for &1 &2.

SAP Error Message - Details

• Message type: E = Error

• Message class: CTE_FND_POSTING - ERP - Concur Integration: FIN Postings

• Message number: 026

• Message text: No change log(s) found for &1 &2.

What causes this issue?

No change log(s) available for &1 &2.

System Response

How to fix this error?

Check if you have accidently selected a line where the <LS>Modified
</>checkbox is not selected.
Check the date since change logs are automatically deleted after 90
days.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CTE_FND_POSTING026 - No change log(s) found for &1 &2. ?

  The SAP error message CTE_FND_POSTING026 with the description "No change log(s) found for &1 &2" typically occurs in the context of the SAP Controlling (CO) module, particularly when dealing with change logs for certain transactions or postings. This error indicates that the system is unable to find any change logs for the specified object or document.
  Cause:
  
  
  Missing Change Logs: The primary cause of this error is that the change logs for the specified object (e.g., cost center, internal order, etc.) do not exist. This can happen if:
  
  Change logging is not activated for the relevant object.
  The change logs have been deleted or not yet created.
  The object has not been modified since change logging was activated.
  
  
  
  Incorrect Object Reference: The parameters (&1 &2) may refer to an object that does not have a change log associated with it, either due to incorrect input or because the object is not eligible for change logging.
  
  
  Authorization Issues: In some cases, the user may not have the necessary authorizations to view the change logs, leading to the perception that they do not exist.
  
  
  Solution:
  
  
  Check Change Log Activation:
  
  Ensure that change logging is activated for the relevant object type in the configuration settings. This can typically be done in the customizing settings of the SAP system.
  For example, in the case of cost centers, check the settings in the Controlling area configuration.
  
  
  
  Verify Object Existence:
  
  Confirm that the object you are trying to access actually exists and is correctly referenced in your transaction or report.
  
  
  
  Review Change Log Settings:
  
  If change logging is activated, check if there are any filters or settings that might prevent the logs from being displayed.
  
  
  
  Check Authorizations:
  
  Ensure that the user has the necessary authorizations to view change logs. This may involve checking roles and permissions assigned to the user.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for specific details on how to enable change logging for the relevant objects.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance, especially if this is a production environment.
  
  
  
  Related Information:
  
  Transaction Codes: You may want to check relevant transaction codes that deal with change logs, such as SCDO (Change Document Objects) or SCDO (Change Document Display).
  SAP Notes: Look for SAP Notes related to this error message for any known issues or patches that may address the problem.
  System Logs: Check system logs (transaction SM21) for any additional error messages or warnings that may provide more context.
  
  By following these steps, you should be able to diagnose and resolve the issue related to the error message CTE_FND_POSTING026.