Message Number list used by SAP ABAP Class CL_FDT_DSM (BRS: Desicion Service Manager)
SAP ABAP Class CL_FDT_DSM (BRS: Desicion Service Manager) is using
# | Object Type | Object Name | Object Description | Note |
---|---|---|---|---|
1 | Message Number | FDT_BRS - 009 | Newly generated source code saved without syntax errors | |
2 | Message Number | FDT_BRS - 013 | Class &1 does not exist | |
3 | Message Number | FDT_BRS - 013 | Class &1 does not exist | |
4 | Message Number | FDT_BRS - 101 | Communication failure during RFC call: &1 &2 &3 &4 | |
5 | Message Number | FDT_BRS - 101 | Communication failure during RFC call: &1 &2 &3 &4 | |
6 | Message Number | FDT_BRS - 101 | Communication failure during RFC call: &1 &2 &3 &4 | |
7 | Message Number | FDT_BRS - 101 | Communication failure during RFC call: &1 &2 &3 &4 | |
8 | Message Number | FDT_BRS - 101 | Communication failure during RFC call: &1 &2 &3 &4 | |
9 | Message Number | FDT_BRS - 101 | Communication failure during RFC call: &1 &2 &3 &4 | |
10 | Message Number | FDT_BRS - 101 | Communication failure during RFC call: &1 &2 &3 &4 | |
11 | Message Number | FDT_BRS - 101 | Communication failure during RFC call: &1 &2 &3 &4 | |
12 | Message Number | FDT_BRS - 101 | Communication failure during RFC call: &1 &2 &3 &4 | |
13 | Message Number | FDT_BRS - 101 | Communication failure during RFC call: &1 &2 &3 &4 | |
14 | Message Number | FDT_BRS - 101 | Communication failure during RFC call: &1 &2 &3 &4 | |
15 | Message Number | FDT_BRS - 101 | Communication failure during RFC call: &1 &2 &3 &4 | |
16 | Message Number | FDT_BRS - 101 | Communication failure during RFC call: &1 &2 &3 &4 | |
17 | Message Number | FDT_BRS - 101 | Communication failure during RFC call: &1 &2 &3 &4 | |
18 | Message Number | FDT_CORE - 000 | Unknown ID &1 | |
19 | Message Number | FDT_CORE - 000 | Unknown ID &1 | |
20 | Message Number | FDT_CORE - 000 | Unknown ID &1 | |
21 | Message Number | FDT_CORE - 020 | ID &1 is initial, unknown, or it does not have the correct object type | |
22 | Message Number | FDT_CORE - 111 | &1 does not have an active version | |
23 | Message Number | FDT_CORE - 350 | Enqueue failed on &1, object locked by &2 | |
24 | Message Number | FDT_CORE - 410 | Connection &1 does not refer to a SAP HANA DB - see transaction DBCO | |
25 | Message Number | FDT_CORE - 522 | Error saving generated class (sy-subrc = &1) | |
26 | Message Number | FDT_CORE - 752 | Object type &1 is not supported | |
27 | Message Number | FDT_CORE - 752 | Object type &1 is not supported | |
28 | Message Number | FDT_CORE - 752 | Object type &1 is not supported | |
29 | Message Number | FDT_CORE - 869 | Nested function &1 was not deployed | |
30 | Message Number | FDT_DSM - 000 | Error calling function module &1 | |
31 | Message Number | FDT_DSM - 000 | Error calling function module &1 | |
32 | Message Number | FDT_DSM - 000 | Error calling function module &1 | |
33 | Message Number | FDT_DSM - 000 | Error calling function module &1 | |
34 | Message Number | FDT_DSM - 000 | Error calling function module &1 | |
35 | Message Number | FDT_DSM - 000 | Error calling function module &1 | |
36 | Message Number | FDT_DSM - 000 | Error calling function module &1 | |
37 | Message Number | FDT_DSM - 000 | Error calling function module &1 | |
38 | Message Number | FDT_DSM - 000 | Error calling function module &1 | |
39 | Message Number | FDT_DSM - 000 | Error calling function module &1 | |
40 | Message Number | FDT_DSM - 000 | Error calling function module &1 | |
41 | Message Number | FDT_DSM - 000 | Error calling function module &1 | |
42 | Message Number | FDT_DSM - 000 | Error calling function module &1 | |
43 | Message Number | FDT_DSM - 000 | Error calling function module &1 | |
44 | Message Number | FDT_DSM - 001 | Communication failure using RFC connection &1 | |
45 | Message Number | FDT_DSM - 001 | Communication failure using RFC connection &1 | |
46 | Message Number | FDT_DSM - 001 | Communication failure using RFC connection &1 | |
47 | Message Number | FDT_DSM - 001 | Communication failure using RFC connection &1 | |
48 | Message Number | FDT_DSM - 001 | Communication failure using RFC connection &1 | |
49 | Message Number | FDT_DSM - 002 | RFC connection &1 does not exist | |
50 | Message Number | FDT_DSM - 002 | RFC connection &1 does not exist | |
51 | Message Number | FDT_DSM - 002 | RFC connection &1 does not exist | |
52 | Message Number | FDT_DSM - 002 | RFC connection &1 does not exist | |
53 | Message Number | FDT_DSM - 002 | RFC connection &1 does not exist | |
54 | Message Number | FDT_DSM - 003 | RFC connection &1 is not of type 'ABAP Connection' | |
55 | Message Number | FDT_DSM - 003 | RFC connection &1 is not of type 'ABAP Connection' | |
56 | Message Number | FDT_DSM - 003 | RFC connection &1 is not of type 'ABAP Connection' | |
57 | Message Number | FDT_DSM - 003 | RFC connection &1 is not of type 'ABAP Connection' | |
58 | Message Number | FDT_DSM - 003 | RFC connection &1 is not of type 'ABAP Connection' | |
59 | Message Number | FDT_DSM - 004 | System failure using RFC connection &1 | |
60 | Message Number | FDT_DSM - 004 | System failure using RFC connection &1 | |
61 | Message Number | FDT_DSM - 004 | System failure using RFC connection &1 | |
62 | Message Number | FDT_DSM - 004 | System failure using RFC connection &1 | |
63 | Message Number | FDT_DSM - 004 | System failure using RFC connection &1 | |
64 | Message Number | FDT_DSM - 005 | Exception &1 occurred while deploying service &2 | |
65 | Message Number | FDT_DSM - 006 | Managed system &1 does not exist | |
66 | Message Number | FDT_DSM - 006 | Managed system &1 does not exist | |
67 | Message Number | FDT_DSM - 007 | Missing lock on Decision Service Manager, please enqueue | |
68 | Message Number | FDT_DSM - 007 | Missing lock on Decision Service Manager, please enqueue | |
69 | Message Number | FDT_DSM - 010 | Application &1 has no managed system assigned | |
70 | Message Number | FDT_DSM - 011 | Managed system &1 does not exist | |
71 | Message Number | FDT_DSM - 012 | Managed system name &1 is already used | |
72 | Message Number | FDT_DSM - 013 | Error signing the generated code (sy-subrc &1) | |
73 | Message Number | FDT_DSM - 014 | &1 (object &2) is not allowed in decision service &3 | |
74 | Message Number | FDT_DSM - 015 | Objects of custom expression type (&1) are not deployable | |
75 | Message Number | FDT_DSM - 019 | Error transforming the source code to a neutral code page (sy-subrc &1) | |
76 | Message Number | FDT_DSM - 020 | RFC connection &1: target system without Unicode support; see long text | |
77 | Message Number | FDT_DSM - 020 | RFC connection &1: target system without Unicode support; see long text | |
78 | Message Number | FDT_DSM - 022 | Expression type &1 (object &2) is not allowed in remote services | |
79 | Message Number | FDT_DSM - 024 | &1 is already assigned to managed system &2 in client &3 | |
80 | Message Number | FDT_DSM - 025 | Add-on SAP NetWeaver Decision Service Management is not installed | |
81 | Message Number | FDT_DSM - 025 | Add-on SAP NetWeaver Decision Service Management is not installed | |
82 | Message Number | FDT_DSM - 025 | Add-on SAP NetWeaver Decision Service Management is not installed | |
83 | Message Number | FDT_DSM - 025 | Add-on SAP NetWeaver Decision Service Management is not installed | |
84 | Message Number | FDT_DSM - 026 | Managed system name cannot be an empty string | |
85 | Message Number | FDT_DSM - 029 | The DSM has unsaved changes, please save before deploying a new service | |
86 | Message Number | FDT_DSM - 030 | Managed system with RFC connection &2 already exists (&1) | |
87 | Message Number | FDT_DSM - 030 | Managed system with RFC connection &2 already exists (&1) | |
88 | Message Number | FDT_DSM - 031 | &1 entries deleted from log | |
89 | Message Number | FDT_DSM - 032 | No matches for selection criteria, no entries deleted | |
90 | Message Number | FDT_DSM - 036 | Cutoff timestamp is in the future | |
91 | Message Number | FDT_DSM - 038 | No deployment exists in selected deletion time frame | |
92 | Message Number | FDT_DSM - 039 | &1 service deployment(s) successfully deleted | |
93 | Message Number | FDT_DSM - 040 | Authorization check for deployment in managed system failed | |
94 | Message Number | FDT_DSM - 041 | Authorization check for deletion in managed system failed | |
95 | Message Number | FDT_DSM - 042 | Authorization check for discarding deployments in managed system failed | |
96 | Message Number | FDT_DSM - 043 | Authorization check for retrieving XML from managed system failed | |
97 | Message Number | FDT_DSM - 043 | Authorization check for retrieving XML from managed system failed | |
98 | Message Number | FDT_DSM - 044 | Authorization check for retrieving trace data from managed system failed | |
99 | Message Number | FDT_DSM - 044 | Authorization check for retrieving trace data from managed system failed | |
100 | Message Number | FDT_DSM - 044 | Authorization check for retrieving trace data from managed system failed | |
101 | Message Number | FDT_DSM - 045 | Authorization check for retrieving class code from managed system failed | |
102 | Message Number | FDT_DSM - 049 | Deployment of service &1 to destination &2 has failed | |
103 | Message Number | FDT_DSM - 049 | Deployment of service &1 to destination &2 has failed | |
104 | Message Number | FDT_DSM - 062 | Deployment of &1 to managed system &2 failed due to a syntax error | |
105 | Message Number | FDT_DSM - 071 | Cannot switch to edit mode - objects locked by user &1 | |
106 | Message Number | FDT_DSM - 073 | Invalid combination of importing parameters in method &1 | |
107 | Message Number | FDT_DSM - 079 | Service '&1' is not active in managed system &2 | |
108 | Message Number | FDT_DSM - 079 | Service '&1' is not active in managed system &2 | |
109 | Message Number | FDT_DSM - 080 | Deployment not possible due to usage of unit/currency exit class | |
110 | Message Number | FDT_DSM - 100 | &1 uses more than &2 rules (&3), please split the ruleset | |
111 | Message Number | FDT_DSM - 101 | &1 uses more than &2 rules (&3), please split the loop expression | |
112 | Message Number | FDT_DSM - 102 | &1 uses more than &2 rows (&3), please split the decision table | |
113 | Message Number | FDT_DSM - 103 | &1 uses more than &2 nodes (&3), please split the tree | |
114 | Message Number | FDT_DSM - 104 | Service &1 uses more than &2 rules, please split the service | |
115 | Message Number | FDT_DSM - 105 | Service &1 uses more than &2 decision table rows please split the service | |
116 | Message Number | FDT_DSM - 106 | Service &1 uses more than &2 tree nodes, please split the service | |
117 | Message Number | FDT_DSM - 110 | Function module &1 is probably not existent in the managed system | |
118 | Message Number | FDT_DSM - 110 | Function module &1 is probably not existent in the managed system | |
119 | Message Number | FDT_DSM - 110 | Function module &1 is probably not existent in the managed system | |
120 | Message Number | FDT_DSM - 110 | Function module &1 is probably not existent in the managed system | |
121 | Message Number | FDT_DSM - 110 | Function module &1 is probably not existent in the managed system | |
122 | Message Number | FDT_DSM - 110 | Function module &1 is probably not existent in the managed system | |
123 | Message Number | FDT_DSM - 110 | Function module &1 is probably not existent in the managed system | |
124 | Message Number | FDT_DSM - 110 | Function module &1 is probably not existent in the managed system | |
125 | Message Number | FDT_DSM - 122 | Exception during call of exit class &1 | |
126 | Message Number | FDT_DSM - 122 | Exception during call of exit class &1 | |
127 | Message Number | FDT_DSM - 123 | Exit class &1 not called in Decision Manager system due to non-existence | |
128 | Message Number | FDT_DSM - 123 | Exit class &1 not called in Decision Manager system due to non-existence | |
129 | Message Number | FDT_DSM - 130 | Exit class &1 does not implement interface IF_FDT_DSM_PARTNER_EXIT | |
130 | Message Number | FDT_DSM - 130 | Exit class &1 does not implement interface IF_FDT_DSM_PARTNER_EXIT | |
131 | Message Number | FDT_DSM - 131 | ABAP platforms (managed system &1) don't support partner exits | |
132 | Message Number | FDT_DSM - 131 | ABAP platforms (managed system &1) don't support partner exits | |
133 | Message Number | FDT_DSM - 133 | Partner exit class &1 does not support the deletion of deployments | |
134 | Message Number | FDT_DSM - 135 | Partner exit class &1 does not support the deployment of services | |
135 | Message Number | FDT_DSM - 136 | Deployment of service &1 was activated from &2 to &3 | |
136 | Message Number | FDT_DSM - 140 | Partner exit class &1 does not support the retrieval of traces | |
137 | Message Number | FDT_DSM - 150 | Enqueue on deployment exit not possible due to foreign lock | |
138 | Message Number | FDT_EXPRESSIONS - 030 | No valid class, &1 does not exist or does not implement interface &2 | |
139 | Message Number | FDT_EXPRESSIONS - 030 | No valid class, &1 does not exist or does not implement interface &2 | |
140 | Message Number | FDT_HANA - 010 | Could not establish database connection &1 - see transaction DBCO |