How To Fix FDT_DSM069 - Object does not exist in the current Decision Service Management system

SAP Error Message - Details

• Message type: E = Error

• Message class: FDT_DSM - BRFplus: Decision Service Manager

• Message number: 069

• Message text: Object does not exist in the current Decision Service Management system

What causes this issue?

The system has determined that the currently selected service in the
managed system is based on a BRFplus function that does not exist in the
current DSM system.
This is not necessarily an error. For example, the respective function
may exist in a different DSM system, and the service may have been
deployed from that system to the managed system. However, for the sake
of consistency, it is not recommended to have different DSM systems in
place because this makes it hard to decide which system contains correct
data and which not.

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?

Depending on the situation, choose one of the following alternatives:
Check your system landscape to find out if there is more than one DSM
system in place. If that is the case, consider to redesign the system
landscape so that only one DSM system remains that can act as the
'single source of truth'.
If the current DSM system is the only DSM system in your landscape, the
fact that the function in question is missing may indicate a data loss.
In that case, contact your system administrator. If you need to restore
the function, you can accomplish this by importing the XML
representation of the deployed service into the DSM system.

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 FDT_DSM069 - Object does not exist in the current Decision Service Management system ?

  The SAP error message FDT_DSM069 indicates that a specific object (such as a decision table, rule, or other decision service artifacts) does not exist in the current Decision Service Management (DSM) system. This error typically arises when there is an attempt to access or reference an object that has either been deleted, not created, or is not available in the current context.
  Causes:
  
  Object Deletion: The object you are trying to access may have been deleted from the DSM.
  Incorrect Object Name: There may be a typo or incorrect naming in the reference to the object.
  Wrong Environment: The object might exist in a different environment (e.g., development vs. production) and is not available in the current one.
  Transport Issues: If the object was supposed to be transported from one system to another, it may not have been successfully transported.
  Authorization Issues: The user may not have the necessary permissions to view or access the object.
  
  Solutions:
  
  Verify Object Existence: Check the DSM to confirm whether the object exists. If it has been deleted, you may need to recreate it.
  Check Naming: Ensure that the name of the object you are trying to access is correct and matches exactly with what is in the DSM.
  Environment Check: Make sure you are working in the correct environment where the object is supposed to exist.
  Transport Logs: If the object was supposed to be transported, check the transport logs to ensure that the transport was successful and that the object is present in the target system.
  User Permissions: Verify that the user has the necessary permissions to access the object. If not, you may need to adjust the user roles or permissions.
  Consult Documentation: Refer to SAP documentation or support for any specific guidelines related to the Decision Service Management system.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  System Logs: Review system logs for any additional error messages or warnings that might provide more context about the issue.
  
  If the problem persists after trying the above solutions, consider reaching out to SAP support for further assistance.