How To Fix CMM_TRM_DEND086 - After changing the default snapshot time run TA CMM_SNAPSHOT_PREP

CMM_TRM_DEND086 - Overview

• Message type: E = Error

• Message class: CMM_TRM_DEND - CMM TRM EoD processing alignment

• Message number: 086

• Message text: After changing the default snapshot time run TA CMM_SNAPSHOT_PREP

What causes this issue?

You change the default snapshot time for a selected portfolio hierarchy
node.

System Response

If you adjust the default snapshot time, the snapshot definition
changes, whereas entries for the daily snapshot time in table
CMM_DEND_RUN remain unchanged.

How to fix this error?

To adjust entries for the daily snapshot time in table <AB>CMM_DEND_RUN
</>, you must run transaction <AB>CMM_SNAPSHOT_PREP</>.

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 CMM_TRM_DEND086 - After changing the default snapshot time run TA CMM_SNAPSHOT_PREP ?

  The SAP error message CMM_TRM_DEND086 typically indicates an issue related to the configuration of the snapshot time in the SAP system, particularly in the context of the Change Management Module (CMM). This error often arises after changing the default snapshot time, which can affect how data is processed and displayed in the system.
  
  Cause:
  The error message CMM_TRM_DEND086 is generally triggered when the system is unable to process the snapshot due to inconsistencies or misconfigurations following the change in the default snapshot time. This can happen for several reasons, including:
  
  Inconsistent Data: The data that the system is trying to process may not align with the new snapshot time settings.
  
  Configuration Issues: The change in the default snapshot time may not have been properly configured or saved in the system.
  Pending Processes: There may be ongoing processes or transactions that are conflicting with the new snapshot time settings.
  
  
  Solution:
  To resolve the error, you can follow these