How To Fix FDT_DSM070 - Object does not exist in this system; see long text

SAP Error Message - Details

• Message type: E = Error

• Message class: FDT_DSM - BRFplus: Decision Service Manager

• Message number: 070

• Message text: Object does not exist in this system; see long text

What causes this issue?

You have tried to navigate to a BRFplus function that has been deployed
to the selected managed system. However, this function does not exist in
the design time system where you are currently logged on.
This situation can occur in the following situations:
The managed system is referred to from more than one design time system.
The list of deployments is built up from the perspective of the managed
system, while the navigation to the rule object that has been deployed
is always restricted to the design time system where the Decision
Service Manager is running. Navigation to objects originating from a
different system is not possible.
The function has been physically deleted in the design time system.

System Response

You cannot navigate to the rule object in the current system.

How to fix this error?

Depending on the root cause, proceed as follows:
Service has been deployed from a different system: In the deployment
list, check the contents of the <ZH>Source System Information</> column.
Here, you can find the system ID and the client from which the
deployment was started.
Function has been physically deleted: In this case, there is no way of
retrieving the object from the system database. The only possible
solution would be restoring the object from a system backup.

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 FDT_DSM070 - Object does not exist in this system; see long text ?

  The SAP error message FDT_DSM070 indicates that a specific object does not exist in the system. This error is often encountered in the context of SAP Fiori or SAP UI5 applications, particularly when dealing with Data Services Management (DSM) or when trying to access certain functionalities related to data models or services.
  Cause:
  
  Object Not Created: The object you are trying to access (like a data model, service, or configuration) has not been created in the system.
  Incorrect Configuration: There may be a misconfiguration in the system settings or in the application that is trying to access the object.
  Transport Issues: If the object was recently transported from another system (like Development to Quality or Production), it may not have been transported correctly or at all.
  Authorization Issues: The user may not have the necessary authorizations to access the object, leading to the perception that it does not exist.
  System Version: The object may exist in a different version of the system or in a different client.
  
  Solution:
  
  Check Object Existence: Verify if the object actually exists in the system. You can do this by navigating to the relevant transaction or using the appropriate tools to search for the object.
  Create the Object: If the object does not exist, you may need to create it. This could involve defining a new data model, service, or configuration as required.
  Review Configuration: Check the configuration settings to ensure that everything is set up correctly. This includes checking any relevant customizing settings.
  Transport Check: If the object was supposed to be transported, check the transport logs to ensure that it was included and successfully imported into the target system.
  Authorization Check: Ensure that the user has the necessary authorizations to access the object. You may need to consult with your security team to verify this.
  System Consistency: If you suspect that the object should exist but does not, consider running consistency checks or consulting with your Basis team to ensure that the system is in a stable state.
  
  Related Information:
  
  Long Text: The long text associated with the error message may provide additional context or specific instructions related to the error. Always check the long text for more detailed information.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide additional troubleshooting steps.
  Community Forums: Consider checking SAP Community forums or other user groups for similar issues and solutions shared by other users.
  
  If the issue persists after following these steps, it may be beneficial to engage with SAP support for further assistance.