SAP ABAP Message Class FDT_SERVICE (Formula & Derivation Tool: Services)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-SRV-BR (Application Component) BRFplus - ABAP-Based Business Rules
⤷
SFDT_SERVICE (Package) BRFplus: Services
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SRV-BR (Application Component) BRFplus - ABAP-Based Business Rules⤷
SFDT_SERVICE (Package) BRFplus: Services 
Attributes
| Message class |  |
FDT_SERVICE |
| Short Description |  |
Formula & Derivation Tool: Services |
| Changed On |  |
20140121 |
| Last Changed At |  |
103726 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
Exception Raised In Custom Application Exit (Further Information Follows) | The short text describes the object sufficiently | |
| 2 | 001 |
Method: &1; Classname: &2 | The short text describes the object sufficiently | |
| 3 | 002 |
Exception Class: &1 | The short text describes the object sufficiently | |
| 4 | 003 |
Screen could not be generated correctly (control exception) | The short text describes the object sufficiently | |
| 5 | 004 |
Only use this functionality, if recommended by BRFplus development. | Space: object requires documentation | |
| 6 | 005 |
GUI error; cannot save text | The short text describes the object sufficiently | |
| 7 | 006 |
Text already saved | The short text describes the object sufficiently | |
| 8 | 007 |
Transaction comments could not be read in the database | The short text describes the object sufficiently | |
| 9 | 008 |
Choose a customizing transaction | The short text describes the object sufficiently | |
| 10 | 009 |
Relational operator &1 is not supported | The short text describes the object sufficiently | |
| 11 | 011 |
Data object types &1 and &2 must not be compared with operator &3 | The short text describes the object sufficiently | |
| 12 | 012 |
Element types &1 and &2 must not be compared with operator &3 | The short text describes the object sufficiently | |
| 13 | 013 |
Element type &1 is not supported | The short text describes the object sufficiently | |
| 14 | 014 |
String &1 cannot be converted to a number | The short text describes the object sufficiently | |
| 15 | 015 |
Tables of &1 with different lines must not be compared with operator &2 | The short text describes the object sufficiently | |
| 16 | 016 |
Calculation type "&1" not possible with element types &2 and &3 | The short text describes the object sufficiently | |
| 17 | 017 |
Calculation not possible for tables with different numbers of lines | The short text describes the object sufficiently | |
| 18 | 018 |
Calculation not possible for data object types &1 and &2 | The short text describes the object sufficiently | |
| 19 | 019 |
Calculation "&1" not possible for element type &2 (data object type &3) | The short text describes the object sufficiently | |
| 20 | 020 |
Text of transaction is presently being processed | The short text describes the object sufficiently | |
| 21 | 021 |
Text saved successfully | The short text describes the object sufficiently | |
| 22 | 022 |
No transaction chosen | The short text describes the object sufficiently | |
| 23 | 023 |
Unidentifiable error; cannot call up maintenance dialog correctly | The short text describes the object sufficiently | |
| 24 | 024 |
Unofficial transaction; may only be used in an SAP system | The short text describes the object sufficiently | |
| 25 | 025 |
Transport successful | The short text describes the object sufficiently | |
| 26 | 026 |
Program &1 not found | The short text describes the object sufficiently | |
| 27 | 027 |
Destination &1 for RFC does not exist | The short text describes the object sufficiently | |
| 28 | 030 |
Invalid combination of parameters | The short text describes the object sufficiently | |
| 29 | 031 |
Unknown element type &1 | The short text describes the object sufficiently | |
| 30 | 032 |
Unknown data object type &1 | The short text describes the object sufficiently | |
| 31 | 033 |
Unknown object type &1 | The short text describes the object sufficiently | |
| 32 | 035 |
A workbench request is not supplied | The short text describes the object sufficiently | |
| 33 | 036 |
A transport request for customizing objects is not supplied | The short text describes the object sufficiently | |
| 34 | 037 |
Not transported applications can not contain transported objects | The short text describes the object sufficiently | |
| 35 | 038 |
Selecting only objects that are not marked for deletion is not allowed | The short text describes the object sufficiently | |
| 36 | 040 |
SAPscript documentation is not available for this object | The short text describes the object sufficiently | |
| 37 | 041 |
Structures contain different fields; comparison not possible | The short text describes the object sufficiently | |
| 38 | 045 |
Currency &1 does not exist in this system | The short text describes the object sufficiently | |
| 39 | 048 |
Unit &1 does not exist in this system | The short text describes the object sufficiently | |
| 40 | 050 |
Value &1 is invalid / is not supported | The short text describes the object sufficiently | |
| 41 | 051 |
Timepoint type &1 is not supported | The short text describes the object sufficiently | |
| 42 | 052 |
Timepoint is not valid | The short text describes the object sufficiently | |
| 43 | 053 |
Operation &1 is not possible with timepoint type &2 | The short text describes the object sufficiently | |
| 44 | 054 |
Invalid application id &1 | The short text describes the object sufficiently | |
| 45 | 060 |
Application exit class &1 called with method &2 for ID &3 (type &4) | The short text describes the object sufficiently | |
| 46 | 061 |
=> Forcing copy to inactive version | The short text describes the object sufficiently | |
| 47 | 062 |
No new version created for &1 | The short text describes the object sufficiently | |
| 48 | 063 |
<= Copy to inactive version successful | The short text describes the object sufficiently | |
| 49 | 064 |
Objects to deploy are inactive | The short text describes the object sufficiently | |
| 50 | 065 |
Object &1 to deploy is missing or deleted | The short text describes the object sufficiently | |
| 51 | 066 |
Object &1 to deploy is inactive. Check transport &2. | The short text describes the object sufficiently | |
| 52 | 067 |
Object &1 was adapted by deployment | The short text describes the object sufficiently | |
| 53 | 070 |
&1 objects have been modified | The short text describes the object sufficiently | |
| 54 | 071 |
&1 no longer used objects have been deleted | The short text describes the object sufficiently | |
| 55 | 072 |
No matching column in new version for column &1 in old version. | Space: object requires documentation | |
| 56 | 073 |
Adapting result data objects for decision table failed. | The short text describes the object sufficiently | |
| 57 | 075 |
Inactive transports (T-tables) could not be activated ! | The short text describes the object sufficiently | |
| 58 | 076 |
Try to deploy anyway. If not successful first check the errors here ! | The short text describes the object sufficiently | |
| 59 | 077 |
Collision for function &1 was resolved successfully | The short text describes the object sufficiently | |
| 60 | 078 |
Collision for function &1 could not be resolved automatically | Space: object requires documentation | |
| 61 | 079 |
Versions older than &1 days will be discarded for application &2 | The short text describes the object sufficiently | |
| 62 | 080 |
Latest version is deployed | The short text describes the object sufficiently | |
| 63 | 081 |
Last deployed version is inactive and may be faulty (on C-table) | The short text describes the object sufficiently | |
| 64 | 082 |
Older version is deployed, a newer version is available | The short text describes the object sufficiently | |
| 65 | 083 |
Function is not yet deployed | The short text describes the object sufficiently | |
| 66 | 084 |
Function objects missing, deleted or not transported correctly | The short text describes the object sufficiently | |
| 67 | 085 |
Latest version is deployed and has been modified | The short text describes the object sufficiently | |
| 68 | 086 |
Older version is deployed and has been modified | The short text describes the object sufficiently | |
| 69 | 089 |
No design-time system information available | Space: object requires documentation | |
| 70 | 090 |
Design-Time Information | The short text describes the object sufficiently | |
| 71 | 091 |
System: &1, Client: &2, User: &3, Workspace: &4 | The short text describes the object sufficiently | |
| 72 | 092 |
Configuration Request: &1, Transport Context: &2 | The short text describes the object sufficiently | |
| 73 | 093 |
Deployment Summary | The short text describes the object sufficiently | |
| 74 | 094 |
...application is assigned to package &1 | The short text describes the object sufficiently | |
| 75 | 095 |
Function &1 (&2) has successfully been deployed | The short text describes the object sufficiently | |
| 76 | 096 |
BRFplus Deployment &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 77 | 097 |
&1 functions could not be activated due to collisions | The short text describes the object sufficiently | |
| 78 | 098 |
Collisions occurred during activation of function &1 (&2) | Space: object requires documentation | |
| 79 | 099 |
...belonging to application &1 (&2), SC: &3, AC: &4 | The short text describes the object sufficiently | |
| 80 | 100 |
Invalid activation call; empty context object | The short text describes the object sufficiently | |
| 81 | 101 |
Start of activation for function &1 (&2) | The short text describes the object sufficiently | |
| 82 | 102 |
End of activation for function &1 (&2) | The short text describes the object sufficiently | |
| 83 | 103 |
Invalid content in DB table &1; see long text for instructions | Space: object requires documentation | |
| 84 | 104 |
Wrong client; BCF content creation has to be done in client &1 | The short text describes the object sufficiently | |
| 85 | 105 |
Error in the activation process of function &1 (&2); activation failed | The short text describes the object sufficiently | |
| 86 | 106 |
&1&2&3&4 | The short text describes the object sufficiently | |
| 87 | 107 |
Unsaved changes exist for &1 | The short text describes the object sufficiently | |
| 88 | 108 |
Lock exists for &1 (ID &2 ) | The short text describes the object sufficiently | |
| 89 | 109 |
Lock exists for client &1 | The short text describes the object sufficiently | |
| 90 | 110 |
Collision was due to a change on &1 &2 (&3) | The short text describes the object sufficiently | |
| 91 | 111 |
Object &1 does not exist in this system; transport is missing | Space: object requires documentation | |
| 92 | 112 |
No BCF client provided in table FDT_BCF_CLIENT | Space: object requires documentation | |
| 93 | 113 |
Object ID &1 is still locked after executing deployment exit | The short text describes the object sufficiently | |
| 94 | 114 |
Client &1 is still locked after executing deployment | The short text describes the object sufficiently | |
| 95 | 115 |
&1 functions have been activated successfully | The short text describes the object sufficiently | |
| 96 | 116 |
&1 functions could not be activated | The short text describes the object sufficiently | |
| 97 | 117 |
&1&2&3&4 | The short text describes the object sufficiently | |
| 98 | 118 |
------------------------------------------------------------------------- | The short text describes the object sufficiently | |
| 99 | 119 |
More than one deployment exit class specified for function &1 | The short text describes the object sufficiently | |
| 100 | 120 |
Exception in deployment exit &1 for function &2 | The short text describes the object sufficiently | |
| 101 | 121 |
=> Deployment exit &1 for function &2 started | The short text describes the object sufficiently | |
| 102 | 122 |
<= Deployment exit &1 for function &2 failed | The short text describes the object sufficiently | |
| 103 | 123 |
<= Deployment exit &1 for function &2 completed | The short text describes the object sufficiently | |
| 104 | 124 |
=> Determination of forced activation by deployment exit &1 started | The short text describes the object sufficiently | |
| 105 | 125 |
<= Deployment exit &1 specified to force deployment of function &2 | The short text describes the object sufficiently | |
| 106 | 126 |
<= Deployment exit &1 specified not to force deployment of function &2 | The short text describes the object sufficiently | |
| 107 | 127 |
<= Deployment exit &1 specified skip the deployment of function &2 | The short text describes the object sufficiently | |
| 108 | 128 |
Deployment exit &1 for function &2 registered | The short text describes the object sufficiently | |
| 109 | 129 |
For Details use Transaction FDT_BCF_LOG in Target System &1 | The short text describes the object sufficiently | |
| 110 | 130 |
... with restrictions Object &1, Subobj &2, ID &3 | The short text describes the object sufficiently | |
| 111 | 131 |
Any unsaved changes are discarded. | The short text describes the object sufficiently | |
| 112 | 132 |
Invalid path: Business object &1 does not exist | The short text describes the object sufficiently | |
| 113 | 133 |
Invalid path: Node &1 does not exist in the business object &2 | The short text describes the object sufficiently | |
| 114 | 134 |
Invalid path: Attribute &1 does not exist in node &2 | The short text describes the object sufficiently | |
| 115 | 135 |
Invalid path: Attribute &1 is not of structure type | The short text describes the object sufficiently | |
| 116 | 136 |
Invalid path: Attribute type &1 of attribute &2 is not supported | The short text describes the object sufficiently | |
| 117 | 137 |
ESF problem with BO ( &1 / &2 ) | The short text describes the object sufficiently | |
| 118 | 138 |
Lock exists for application &1 | The short text describes the object sufficiently | |
| 119 | 140 |
Deployment Exit Class &1 left the System in an inconsistent state | The short text describes the object sufficiently | |
| 120 | 141 |
Application Exit class &1 of application &2 was called | The short text describes the object sufficiently | |
| 121 | 142 |
Application component of class &1 is &2 | The short text describes the object sufficiently | |
| 122 | 143 |
Processing started for objects marked for deletion | The short text describes the object sufficiently | |
| 123 | 144 |
Processing started for executing logical deletions | The short text describes the object sufficiently | |
| 124 | 145 |
Processing started for executing physical deletions | The short text describes the object sufficiently | |
| 125 | 146 |
Processing of table type &1 | The short text describes the object sufficiently | |
| 126 | 147 |
Processing for physical deletion of discarded versions was started | The short text describes the object sufficiently | |
| 127 | 148 |
Processing started for objects marked for deletion | The short text describes the object sufficiently | |
| 128 | 149 |
The processing of table type &1 is continued | The short text describes the object sufficiently | |
| 129 | 150 |
Collision UI for BRFplus content objects not available | The short text describes the object sufficiently | |
| 130 | 151 |
Processing for deleting unused objects was started | The short text describes the object sufficiently | |
| 131 | 153 |
Versions older than &1 shall be logically discarded | The short text describes the object sufficiently | |
| 132 | 156 |
Object index &1 - Change index &2 - GUID &3 | The short text describes the object sufficiently | |
| 133 | 160 |
No BC connection defined for table &1 | The short text describes the object sufficiently | |
| 134 | 161 |
Exception occurred during BC connection for table &1 | The short text describes the object sufficiently | |
| 135 | 162 |
BC connection updated decision table &1 with data from DB table &1 | The short text describes the object sufficiently | |
| 136 | 163 |
Foreign lock for decision table &1 - BC connector can't work | The short text describes the object sufficiently | |
| 137 | 164 |
Activation problems during BC connector run for decision table &1 | The short text describes the object sufficiently | |
| 138 | 170 |
Unknown BC database table &1 | The short text describes the object sufficiently | |
| 139 | 171 |
Unknown BRFplus decision table &1 | The short text describes the object sufficiently | |
| 140 | 180 |
Recursion error in application exit class &1 method &2 for id &3 | Space: object requires documentation | |
| 141 | 181 |
Internal error calling application exit class &1 method &2 id &3 | The short text describes the object sufficiently | |
| 142 | 190 |
Could not lock object &2 due to user &1 | The short text describes the object sufficiently | |
| 143 | 191 |
Could not lock application &2 due to user &1 | The short text describes the object sufficiently | |
| 144 | 192 |
Could not lock client &1 due to user &2 | The short text describes the object sufficiently | |
| 145 | 193 |
Could not lock all clients due to user &1 | The short text describes the object sufficiently | |
| 146 | 194 |
The short text describes the object sufficiently | ||
| 147 | 195 |
Could not lock object &2 for processing-relevant changes due to user &1 | The short text describes the object sufficiently | |
| 148 | 196 |
Could not lock application &2 for proc.-relevant changes due to user &1 | The short text describes the object sufficiently | |
| 149 | 197 |
Could not lock client &1 for processing-relevant changes due to user &2 | The short text describes the object sufficiently | |
| 150 | 198 |
Could not lock all clients for processing-relevant changes due to user &1 | The short text describes the object sufficiently | |
| 151 | 199 |
Wait and try to activate the changes later | The short text describes the object sufficiently | |
| 152 | 200 |
&1: Can not delete using obj. &2 &3, it does not belong to current set | The short text describes the object sufficiently | |
| 153 | 201 |
Object &1 cannot be deleted; it has undeleted or undeletable usages | The short text describes the object sufficiently | |
| 154 | 202 |
&1 objects have been deleted successfully | The short text describes the object sufficiently | |
| 155 | 203 |
No objects have to be deleted | The short text describes the object sufficiently | |
| 156 | 204 |
&1 objects have been deleted successfully during application cleanup | The short text describes the object sufficiently | |
| 157 | 205 |
Cannot activate object &1 due to erroneous referenced objects | The short text describes the object sufficiently | |
| 158 | 207 |
Versions for &1 objects have been discarded successfully | The short text describes the object sufficiently | |
| 159 | 210 |
You have no authorization to execute this functionality (category: &1) | The short text describes the object sufficiently | |
| 160 | 220 |
String &1 cannot be converted to a quantity | The short text describes the object sufficiently | |
| 161 | 221 |
String &1 cannot be converted to an amount | The short text describes the object sufficiently | |
| 162 | 260 |
Name pattern '&1' matches to multiple objects | The short text describes the object sufficiently | |
| 163 | 270 |
&1: &2 objects are fully discarded with timestamp &3 | The short text describes the object sufficiently | |
| 164 | 271 |
&1: &2 objects are partially discarded with timestamp &3 | The short text describes the object sufficiently | |
| 165 | 272 |
&1: &2 objects could not be discarded | The short text describes the object sufficiently | |
| 166 | 273 |
Not selected &1 has &2 usages for the selected objects | The short text describes the object sufficiently | |
| 167 | 274 |
Application &1 from client &2 has &3 usages for the selected objects | The short text describes the object sufficiently | |
| 168 | 280 |
The short text describes the object sufficiently | ||
| 169 | 290 |
The short text describes the object sufficiently | ||
| 170 | 295 |
Provide either ID or element type | The short text describes the object sufficiently | |
| 171 | 296 |
Provide either value or reference | The short text describes the object sufficiently | |
| 172 | 300 |
BRFplus related status information | The short text describes the object sufficiently | |
| 173 | 301 |
BRFplus deployment related information | The short text describes the object sufficiently | |
| 174 | 302 |
BRFplus deployment status for specific function and client | The short text describes the object sufficiently | |
| 175 | 303 |
Reporting deployment status to CCMS monitoring failed | The short text describes the object sufficiently | |
| 176 | 310 |
Deployment by user &1 succeeded. | The short text describes the object sufficiently | |
| 177 | 311 |
Deployment by user &1 failed. | The short text describes the object sufficiently | |
| 178 | 312 |
Deployment of object &1 &2 failed | The short text describes the object sufficiently | |
| 179 | 313 |
Deployment of object &1 &2 succeeded | The short text describes the object sufficiently | |
| 180 | 314 |
Object &1 &2 has not been deployed | The short text describes the object sufficiently | |
| 181 | 315 |
Object &1 &2 already deployed on latest version | The short text describes the object sufficiently | |
| 182 | 316 |
Report problems to application component &1 | The short text describes the object sufficiently | |
| 183 | 317 |
BRFplus application '&1' of package &2 | The short text describes the object sufficiently | |
| 184 | 318 |
Deployment Status: &1 | The short text describes the object sufficiently | |
| 185 | 319 |
Prior deployment status: &1 | The short text describes the object sufficiently | |
| 186 | 320 |
Must not trigger deployment recursively | The short text describes the object sufficiently | |
| 187 | 321 |
Must not trigger deployment in development client | The short text describes the object sufficiently | |
| 188 | 322 |
Must specify at least 1 object to deploy | The short text describes the object sufficiently | |
| 189 | 323 |
Must not deploy objects of different applications | The short text describes the object sufficiently | |
| 190 | 330 |
Creation of error log failed | The short text describes the object sufficiently | |
| 191 | 331 |
Adding message &1 &2 to error log failed | The short text describes the object sufficiently | |
| 192 | 332 |
Saving error log failed | The short text describes the object sufficiently | |
| 193 | 350 |
--------messages about quantities | The short text describes the object sufficiently | |
| 194 | 351 |
The unit of measure '&1' has quantity dimension '&2', not '&3' | The short text describes the object sufficiently | |
| 195 | 352 |
No quantity dimension defined with the given dimensions | The short text describes the object sufficiently | |
| 196 | 353 |
Division by zero | The short text describes the object sufficiently | |
| 197 | 354 |
Cannot add or subtract different quantity dimensions ('&1' and '&2') | The short text describes the object sufficiently | |
| 198 | 355 |
Dimension with specific parameters not found | The short text describes the object sufficiently | |
| 199 | 356 |
Dimension &1 does not exist | The short text describes the object sufficiently | |
| 200 | 357 |
Product of quantities with dimensions ('&1' and '&2') is '&3', not '&4' | The short text describes the object sufficiently | |
| 201 | 358 |
Division of quantities with dimensions ('&1' and '&2') is '&3', not '&4' | The short text describes the object sufficiently | |
| 202 | 359 |
Quantities with dimensions ('&1' and '&2') cannot be multiplied | The short text describes the object sufficiently | |
| 203 | 360 |
Quantities with dimensions ('&1' and '&2') cannot be divided | The short text describes the object sufficiently | |
| 204 | 400 |
Object from table &2 does not exist in table &3: &1 | The short text describes the object sufficiently | |
| 205 | 401 |
Messages for object &1 | The short text describes the object sufficiently | |
| 206 | 402 |
&1 messages could not be added to the message log | The short text describes the object sufficiently | |
| 207 | 403 |
Log for BRFPlus consistency check at &1 &2 | The short text describes the object sufficiently | |
| 208 | 404 |
Object used by another object does not exist: &1, &2 | The short text describes the object sufficiently | |
| 209 | 405 |
Deleted object is still used in undeleted object: &1, &2 | The short text describes the object sufficiently | |
| 210 | 406 |
Entry for object in table &2 is incomplete: &1 | The short text describes the object sufficiently | |
| 211 | 407 |
&1 entries from table &2 are missing in table &3: &4 | The short text describes the object sufficiently | |
| 212 | 408 |
Deleted object is still used in &2 undeleted objects: &1, &3 | The short text describes the object sufficiently | |
| 213 | 409 |
Application used in &2 objects does not exist: &1, &3 | The short text describes the object sufficiently | |
| 214 | 410 |
Expression type used in &2 objects does not exist: &1, &3 | The short text describes the object sufficiently | |
| 215 | 411 |
Application used in an object does not exist: &1, &2 | The short text describes the object sufficiently | |
| 216 | 412 |
Expression type used in an object does not exist: &1, &2 | The short text describes the object sufficiently |
History
| Last changed on/by | |
20140121 | SAP |
| SAP Release Created in | 710 |
