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
⤷ 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 | 000 | Error calling function module &1 | The short text describes the object sufficiently | |
2 | 001 | Communication failure using RFC connection &1 | The short text describes the object sufficiently | |
3 | 002 | RFC connection &1 does not exist | The short text describes the object sufficiently | |
4 | 003 | RFC connection &1 is not of type 'ABAP Connection' | Space: object requires documentation | |
5 | 004 | System failure using RFC connection &1 | Space: object requires documentation | |
6 | 005 | Exception &1 occurred while deploying service &2 | The short text describes the object sufficiently | |
7 | 006 | Managed system &1 does not exist | The short text describes the object sufficiently | |
8 | 007 | Missing lock on Decision Service Manager, please enqueue | The short text describes the object sufficiently | |
9 | 008 | Enqueue failed on decision service manager due to a system error | The short text describes the object sufficiently | |
10 | 009 | Classname &1 from managed system could not be used, new name &2 created | The short text describes the object sufficiently | |
11 | 010 | Application &1 has no managed system assigned | The short text describes the object sufficiently | |
12 | 011 | Managed system &1 does not exist | The short text describes the object sufficiently | |
13 | 012 | Managed system name &1 is already used | The short text describes the object sufficiently | |
14 | 013 | Error signing the generated code (sy-subrc &1) | The short text describes the object sufficiently | |
15 | 014 | &1 (object &2) is not allowed in decision service &3 | The short text describes the object sufficiently | |
16 | 015 | Objects of custom expression type (&1) are not deployable | Space: object requires documentation | |
17 | 016 | Application exits are not allowed in remote services (service &1) | The short text describes the object sufficiently | |
18 | 017 | Select a service deployment first to show the &1 | The short text describes the object sufficiently | |
19 | 018 | Invalid selection; select a deployment to show the &1 | Space: object requires documentation | |
20 | 019 | Error transforming the source code to a neutral code page (sy-subrc &1) | The short text describes the object sufficiently | |
21 | 020 | RFC connection &1: target system without Unicode support; see long text | Space: object requires documentation | |
22 | 021 | Application exits are not allowed in remote services | The short text describes the object sufficiently | |
23 | 022 | Expression type &1 (object &2) is not allowed in remote services | The short text describes the object sufficiently | |
24 | 023 | Custom expression types (&1) are not allowed in remote services | The short text describes the object sufficiently | |
25 | 024 | &1 is already assigned to managed system &2 in client &3 | The short text describes the object sufficiently | |
26 | 025 | Add-on SAP NetWeaver Decision Service Management is not installed | The short text describes the object sufficiently | |
27 | 026 | Managed system name cannot be an empty string | Space: object requires documentation | |
28 | 027 | Deployment failed; Managed system &1 does not exist | The short text describes the object sufficiently | |
29 | 028 | Please select the managed system to deploy the service | The short text describes the object sufficiently | |
30 | 029 | The DSM has unsaved changes, please save before deploying a new service | The short text describes the object sufficiently | |
31 | 030 | Managed system with RFC connection &2 already exists (&1) | The short text describes the object sufficiently | |
32 | 031 | &1 entries deleted from log | The short text describes the object sufficiently | |
33 | 032 | No matches for selection criteria, no entries deleted | The short text describes the object sufficiently | |
34 | 033 | Simulation of remote service in local system may result in errors | Space: object requires documentation | |
35 | 034 | Approval workflow for service &1 started with workflow ID &2 | The short text describes the object sufficiently | |
36 | 035 | Invalid selection; no service deleted | The short text describes the object sufficiently | |
37 | 036 | Cutoff timestamp is in the future | The short text describes the object sufficiently | |
38 | 037 | Deletion workflow for service &1 started with workflow ID &2 | The short text describes the object sufficiently | |
39 | 038 | No deployment exists in selected deletion time frame | Space: object requires documentation | |
40 | 039 | &1 service deployment(s) successfully deleted | The short text describes the object sufficiently | |
41 | 040 | Authorization check for deployment in managed system failed | Space: object requires documentation | |
42 | 041 | Authorization check for deletion in managed system failed | Space: object requires documentation | |
43 | 042 | Authorization check for discarding deployments in managed system failed | Space: object requires documentation | |
44 | 043 | Authorization check for retrieving XML from managed system failed | Space: object requires documentation | |
45 | 044 | Authorization check for retrieving trace data from managed system failed | Space: object requires documentation | |
46 | 045 | Authorization check for retrieving class code from managed system failed | Space: object requires documentation | |
47 | 046 | No authorization to execute Decision Service Manager | The short text describes the object sufficiently | |
48 | 048 | Managed system &1 created successfully | The short text describes the object sufficiently | |
49 | 049 | Deployment of service &1 to destination &2 has failed | The short text describes the object sufficiently | |
50 | 050 | Managed system &1 with RFC destination &2 has been created | The short text describes the object sufficiently | |
51 | 051 | Managed system &1 has been deleted | The short text describes the object sufficiently | |
52 | 052 | RFC destination from managed system &1 has been changed from &2 to &3 | The short text describes the object sufficiently | |
53 | 053 | Description of managed system &1 has been changed from &2 to &3 | The short text describes the object sufficiently | |
54 | 054 | Application &1 has been assigned to managed system &2 | The short text describes the object sufficiently | |
55 | 055 | Application &1: assignment changed from &2 to &3 | The short text describes the object sufficiently | |
56 | 056 | Assignment of application &1 to managed system &2 has been deleted | The short text describes the object sufficiently | |
57 | 057 | Service &1 has been deployed to managed system &2 | The short text describes the object sufficiently | |
58 | 058 | Deployments from &1 to managed system &2 for service &3 have been deleted | The short text describes the object sufficiently | |
59 | 059 | Deployment: Service &1 was already up to date in managed system &2 | The short text describes the object sufficiently | |
60 | 060 | All deployments for service &1 in managed system &2 have been deleted | The short text describes the object sufficiently | |
61 | 061 | Documentation of managed system &1 has been changed | The short text describes the object sufficiently | |
62 | 062 | Deployment of &1 to managed system &2 failed due to a syntax error | The short text describes the object sufficiently | |
63 | 063 | Deployment of &1 to managed system &2 failed due to a system error | The short text describes the object sufficiently | |
64 | 064 | Deployment of &1 to managed system &2 failed due to a communication error | The short text describes the object sufficiently | |
65 | 065 | System type of managed system &1 has been changed from &2 to &3 | The short text describes the object sufficiently | |
66 | 066 | Deployment from &1 in managed system &2 for service &3 has been deleted | The short text describes the object sufficiently | |
67 | 067 | Local DSM version of service is newer than deployed version | Space: object requires documentation | |
68 | 068 | Local DSM version of service is older than deployed version | Space: object requires documentation | |
69 | 069 | Object does not exist in the current Decision Service Management system | Space: object requires documentation | |
70 | 070 | Object does not exist in this system; see long text | Space: object requires documentation | |
71 | 071 | Cannot switch to edit mode - objects locked by user &1 | Space: object requires documentation | |
72 | 072 | Service imported | The short text describes the object sufficiently | |
73 | 073 | Invalid combination of importing parameters in method &1 | The short text describes the object sufficiently | |
74 | 074 | Service was not imported | The short text describes the object sufficiently | |
75 | 075 | Application not found in DSM system; see long text | Space: object requires documentation | |
76 | 077 | XML data exported (source: &1; target: &3; RFC: &2; time: &4) | The short text describes the object sufficiently | |
77 | 079 | Service '&1' is not active in managed system &2 | Space: object requires documentation | |
78 | 080 | Deployment not possible due to usage of unit/currency exit class | Space: object requires documentation | |
79 | 082 | No object selected | Space: object requires documentation | |
80 | 086 | Enqueue failed; managed system &1 does not exist | The short text describes the object sufficiently | |
81 | 087 | Deploying services to production systems subject to license conditions | The short text describes the object sufficiently | |
82 | 088 | Select at least one managed system for deployment | The short text describes the object sufficiently | |
83 | 089 | Select at least one service for deployment | The short text describes the object sufficiently | |
84 | 090 | 50 of &1 available services are displayed | The short text describes the object sufficiently | |
85 | 091 | XML Export of &1 in remote system &2 was not succesful | The short text describes the object sufficiently | |
86 | 092 | Not all changes have been saved, please see the following messages | The short text describes the object sufficiently | |
87 | 100 | &1 uses more than &2 rules (&3), please split the ruleset | The short text describes the object sufficiently | |
88 | 101 | &1 uses more than &2 rules (&3), please split the loop expression | The short text describes the object sufficiently | |
89 | 102 | &1 uses more than &2 rows (&3), please split the decision table | The short text describes the object sufficiently | |
90 | 103 | &1 uses more than &2 nodes (&3), please split the tree | The short text describes the object sufficiently | |
91 | 104 | Service &1 uses more than &2 rules, please split the service | The short text describes the object sufficiently | |
92 | 105 | Service &1 uses more than &2 decision table rows please split the service | The short text describes the object sufficiently | |
93 | 106 | Service &1 uses more than &2 tree nodes, please split the service | The short text describes the object sufficiently | |
94 | 110 | Function module &1 is probably not existent in the managed system | The short text describes the object sufficiently | |
95 | 120 | No application or service selected; please select one from the table | The short text describes the object sufficiently | |
96 | 121 | No exit class specified; please enter exit name | The short text describes the object sufficiently | |
97 | 122 | Exception during call of exit class &1 | The short text describes the object sufficiently | |
98 | 123 | Exit class &1 not called in Decision Manager system due to non-existence | The short text describes the object sufficiently | |
99 | 130 | Exit class &1 does not implement interface IF_FDT_DSM_PARTNER_EXIT | The short text describes the object sufficiently | |
100 | 131 | ABAP platforms (managed system &1) don't support partner exits | The short text describes the object sufficiently | |
101 | 132 | Partner exit class &1 does not support the retrieval of deployments | The short text describes the object sufficiently | |
102 | 133 | Partner exit class &1 does not support the deletion of deployments | The short text describes the object sufficiently | |
103 | 134 | Partner exit class &1 does not support the testing of deployments | The short text describes the object sufficiently | |
104 | 135 | Partner exit class &1 does not support the deployment of services | The short text describes the object sufficiently | |
105 | 136 | Deployment of service &1 was activated from &2 to &3 | The short text describes the object sufficiently | |
106 | 137 | Partner exit class &1 does not support XML export from the managed system | The short text describes the object sufficiently | |
107 | 138 | Partner exit class &1 does not support the retrieval of source code | The short text describes the object sufficiently | |
108 | 139 | No managed system with active partner module type simulation available | The short text describes the object sufficiently | |
109 | 140 | Partner exit class &1 does not support the retrieval of traces | The short text describes the object sufficiently | |
110 | 150 | 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 |