SAP ABAP Message Class FDT_DSM (BRFplus: Decision Service Manager)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-SRV-BR (Application Component) BRFplus - ABAP-Based Business Rules
⤷
SFDT_BRS_DSM (Package) Business Rule Services: Decision Service Manager

⤷

⤷

Attributes
Message class | ![]() |
FDT_DSM |
Short Description | ![]() |
BRFplus: Decision Service Manager |
Changed On | ![]() |
20141121 |
Last Changed At | ![]() |
124013 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | ![]() |
Error calling function module &1 | The short text describes the object sufficiently | |
2 | ![]() |
Communication failure using RFC connection &1 | The short text describes the object sufficiently | |
3 | ![]() |
RFC connection &1 does not exist | The short text describes the object sufficiently | |
4 | ![]() |
RFC connection &1 is not of type 'ABAP Connection' | Space: object requires documentation | |
5 | ![]() |
System failure using RFC connection &1 | Space: object requires documentation | |
6 | ![]() |
Exception &1 occurred while deploying service &2 | The short text describes the object sufficiently | |
7 | ![]() |
Managed system &1 does not exist | The short text describes the object sufficiently | |
8 | ![]() |
Missing lock on Decision Service Manager, please enqueue | The short text describes the object sufficiently | |
9 | ![]() |
Enqueue failed on decision service manager due to a system error | The short text describes the object sufficiently | |
10 | ![]() |
Classname &1 from managed system could not be used, new name &2 created | The short text describes the object sufficiently | |
11 | ![]() |
Application &1 has no managed system assigned | The short text describes the object sufficiently | |
12 | ![]() |
Managed system &1 does not exist | The short text describes the object sufficiently | |
13 | ![]() |
Managed system name &1 is already used | The short text describes the object sufficiently | |
14 | ![]() |
Error signing the generated code (sy-subrc &1) | The short text describes the object sufficiently | |
15 | ![]() |
&1 (object &2) is not allowed in decision service &3 | The short text describes the object sufficiently | |
16 | ![]() |
Objects of custom expression type (&1) are not deployable | Space: object requires documentation | |
17 | ![]() |
Application exits are not allowed in remote services (service &1) | The short text describes the object sufficiently | |
18 | ![]() |
Select a service deployment first to show the &1 | The short text describes the object sufficiently | |
19 | ![]() |
Invalid selection; select a deployment to show the &1 | Space: object requires documentation | |
20 | ![]() |
Error transforming the source code to a neutral code page (sy-subrc &1) | The short text describes the object sufficiently | |
21 | ![]() |
RFC connection &1: target system without Unicode support; see long text | Space: object requires documentation | |
22 | ![]() |
Application exits are not allowed in remote services | The short text describes the object sufficiently | |
23 | ![]() |
Expression type &1 (object &2) is not allowed in remote services | The short text describes the object sufficiently | |
24 | ![]() |
Custom expression types (&1) are not allowed in remote services | The short text describes the object sufficiently | |
25 | ![]() |
&1 is already assigned to managed system &2 in client &3 | The short text describes the object sufficiently | |
26 | ![]() |
Add-on SAP NetWeaver Decision Service Management is not installed | The short text describes the object sufficiently | |
27 | ![]() |
Managed system name cannot be an empty string | Space: object requires documentation | |
28 | ![]() |
Deployment failed; Managed system &1 does not exist | The short text describes the object sufficiently | |
29 | ![]() |
Please select the managed system to deploy the service | The short text describes the object sufficiently | |
30 | ![]() |
The DSM has unsaved changes, please save before deploying a new service | The short text describes the object sufficiently | |
31 | ![]() |
Managed system with RFC connection &2 already exists (&1) | The short text describes the object sufficiently | |
32 | ![]() |
&1 entries deleted from log | The short text describes the object sufficiently | |
33 | ![]() |
No matches for selection criteria, no entries deleted | The short text describes the object sufficiently | |
34 | ![]() |
Simulation of remote service in local system may result in errors | Space: object requires documentation | |
35 | ![]() |
Approval workflow for service &1 started with workflow ID &2 | The short text describes the object sufficiently | |
36 | ![]() |
Invalid selection; no service deleted | The short text describes the object sufficiently | |
37 | ![]() |
Cutoff timestamp is in the future | The short text describes the object sufficiently | |
38 | ![]() |
Deletion workflow for service &1 started with workflow ID &2 | The short text describes the object sufficiently | |
39 | ![]() |
No deployment exists in selected deletion time frame | Space: object requires documentation | |
40 | ![]() |
&1 service deployment(s) successfully deleted | The short text describes the object sufficiently | |
41 | ![]() |
Authorization check for deployment in managed system failed | Space: object requires documentation | |
42 | ![]() |
Authorization check for deletion in managed system failed | Space: object requires documentation | |
43 | ![]() |
Authorization check for discarding deployments in managed system failed | Space: object requires documentation | |
44 | ![]() |
Authorization check for retrieving XML from managed system failed | Space: object requires documentation | |
45 | ![]() |
Authorization check for retrieving trace data from managed system failed | Space: object requires documentation | |
46 | ![]() |
Authorization check for retrieving class code from managed system failed | Space: object requires documentation | |
47 | ![]() |
No authorization to execute Decision Service Manager | The short text describes the object sufficiently | |
48 | ![]() |
Managed system &1 created successfully | The short text describes the object sufficiently | |
49 | ![]() |
Deployment of service &1 to destination &2 has failed | The short text describes the object sufficiently | |
50 | ![]() |
Managed system &1 with RFC destination &2 has been created | The short text describes the object sufficiently | |
51 | ![]() |
Managed system &1 has been deleted | The short text describes the object sufficiently | |
52 | ![]() |
RFC destination from managed system &1 has been changed from &2 to &3 | The short text describes the object sufficiently | |
53 | ![]() |
Description of managed system &1 has been changed from &2 to &3 | The short text describes the object sufficiently | |
54 | ![]() |
Application &1 has been assigned to managed system &2 | The short text describes the object sufficiently | |
55 | ![]() |
Application &1: assignment changed from &2 to &3 | The short text describes the object sufficiently | |
56 | ![]() |
Assignment of application &1 to managed system &2 has been deleted | The short text describes the object sufficiently | |
57 | ![]() |
Service &1 has been deployed to managed system &2 | The short text describes the object sufficiently | |
58 | ![]() |
Deployments from &1 to managed system &2 for service &3 have been deleted | The short text describes the object sufficiently | |
59 | ![]() |
Deployment: Service &1 was already up to date in managed system &2 | The short text describes the object sufficiently | |
60 | ![]() |
All deployments for service &1 in managed system &2 have been deleted | The short text describes the object sufficiently | |
61 | ![]() |
Documentation of managed system &1 has been changed | The short text describes the object sufficiently | |
62 | ![]() |
Deployment of &1 to managed system &2 failed due to a syntax error | The short text describes the object sufficiently | |
63 | ![]() |
Deployment of &1 to managed system &2 failed due to a system error | The short text describes the object sufficiently | |
64 | ![]() |
Deployment of &1 to managed system &2 failed due to a communication error | The short text describes the object sufficiently | |
65 | ![]() |
System type of managed system &1 has been changed from &2 to &3 | The short text describes the object sufficiently | |
66 | ![]() |
Deployment from &1 in managed system &2 for service &3 has been deleted | The short text describes the object sufficiently | |
67 | ![]() |
Local DSM version of service is newer than deployed version | Space: object requires documentation | |
68 | ![]() |
Local DSM version of service is older than deployed version | Space: object requires documentation | |
69 | ![]() |
Object does not exist in the current Decision Service Management system | Space: object requires documentation | |
70 | ![]() |
Object does not exist in this system; see long text | Space: object requires documentation | |
71 | ![]() |
Cannot switch to edit mode - objects locked by user &1 | Space: object requires documentation | |
72 | ![]() |
Service imported | The short text describes the object sufficiently | |
73 | ![]() |
Invalid combination of importing parameters in method &1 | The short text describes the object sufficiently | |
74 | ![]() |
Service was not imported | The short text describes the object sufficiently | |
75 | ![]() |
Application not found in DSM system; see long text | Space: object requires documentation | |
76 | ![]() |
XML data exported (source: &1; target: &3; RFC: &2; time: &4) | The short text describes the object sufficiently | |
77 | ![]() |
Service '&1' is not active in managed system &2 | Space: object requires documentation | |
78 | ![]() |
Deployment not possible due to usage of unit/currency exit class | Space: object requires documentation | |
79 | ![]() |
No object selected | Space: object requires documentation | |
80 | ![]() |
Enqueue failed; managed system &1 does not exist | The short text describes the object sufficiently | |
81 | ![]() |
Deploying services to production systems subject to license conditions | The short text describes the object sufficiently | |
82 | ![]() |
Select at least one managed system for deployment | The short text describes the object sufficiently | |
83 | ![]() |
Select at least one service for deployment | The short text describes the object sufficiently | |
84 | ![]() |
50 of &1 available services are displayed | The short text describes the object sufficiently | |
85 | ![]() |
XML Export of &1 in remote system &2 was not succesful | The short text describes the object sufficiently | |
86 | ![]() |
Not all changes have been saved, please see the following messages | The short text describes the object sufficiently | |
87 | ![]() |
&1 uses more than &2 rules (&3), please split the ruleset | The short text describes the object sufficiently | |
88 | ![]() |
&1 uses more than &2 rules (&3), please split the loop expression | The short text describes the object sufficiently | |
89 | ![]() |
&1 uses more than &2 rows (&3), please split the decision table | The short text describes the object sufficiently | |
90 | ![]() |
&1 uses more than &2 nodes (&3), please split the tree | The short text describes the object sufficiently | |
91 | ![]() |
Service &1 uses more than &2 rules, please split the service | The short text describes the object sufficiently | |
92 | ![]() |
Service &1 uses more than &2 decision table rows please split the service | The short text describes the object sufficiently | |
93 | ![]() |
Service &1 uses more than &2 tree nodes, please split the service | The short text describes the object sufficiently | |
94 | ![]() |
Function module &1 is probably not existent in the managed system | The short text describes the object sufficiently | |
95 | ![]() |
No application or service selected; please select one from the table | The short text describes the object sufficiently | |
96 | ![]() |
No exit class specified; please enter exit name | The short text describes the object sufficiently | |
97 | ![]() |
Exception during call of exit class &1 | The short text describes the object sufficiently | |
98 | ![]() |
Exit class &1 not called in Decision Manager system due to non-existence | The short text describes the object sufficiently | |
99 | ![]() |
Exit class &1 does not implement interface IF_FDT_DSM_PARTNER_EXIT | The short text describes the object sufficiently | |
100 | ![]() |
ABAP platforms (managed system &1) don't support partner exits | The short text describes the object sufficiently | |
101 | ![]() |
Partner exit class &1 does not support the retrieval of deployments | The short text describes the object sufficiently | |
102 | ![]() |
Partner exit class &1 does not support the deletion of deployments | The short text describes the object sufficiently | |
103 | ![]() |
Partner exit class &1 does not support the testing of deployments | The short text describes the object sufficiently | |
104 | ![]() |
Partner exit class &1 does not support the deployment of services | The short text describes the object sufficiently | |
105 | ![]() |
Deployment of service &1 was activated from &2 to &3 | The short text describes the object sufficiently | |
106 | ![]() |
Partner exit class &1 does not support XML export from the managed system | The short text describes the object sufficiently | |
107 | ![]() |
Partner exit class &1 does not support the retrieval of source code | The short text describes the object sufficiently | |
108 | ![]() |
No managed system with active partner module type simulation available | The short text describes the object sufficiently | |
109 | ![]() |
Partner exit class &1 does not support the retrieval of traces | The short text describes the object sufficiently | |
110 | ![]() |
Enqueue on deployment exit not possible due to foreign lock | The short text describes the object sufficiently |
History
Last changed on/by | ![]() |
20141121 | SAP |
SAP Release Created in | 732 |