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
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.
You cannot navigate to the rule object in the current system.
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.
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.
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
Get instant SAP help. Sign up for our Free Essentials Plan.
FDT_DSM069
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 ...
FDT_DSM068
Local DSM version of service is older than deployed version
What causes this issue? The system has determined that the service is already present in the managed system. Moreover, the service version in the man...
FDT_DSM071
Cannot switch to edit mode - objects locked by user &1
What causes this issue? You have tried to switch the Decision Service Manager to edit mode. However, user &v1& is already using the system in...
FDT_DSM072
Service imported
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.