FDT_SERVICE - Formula & Derivation Tool: Services
The following messages are stored in message class FDT_SERVICE: Formula & Derivation Tool: Services.
It is part of development package SFDT_SERVICE in software component BC-SRV-BR. This development package consists of objects that can be grouped under "BRFplus: Services".
It is part of development package SFDT_SERVICE in software component BC-SRV-BR. This development package consists of objects that can be grouped under "BRFplus: Services".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Exception Raised In Custom Application Exit (Further Information Follows) |
| 001 | Method: &1; Classname: &2 |
| 002 | Exception Class: &1 |
| 003 | Screen could not be generated correctly (control exception) |
| 004 | Only use this functionality, if recommended by BRFplus development. |
| 005 | GUI error; cannot save text |
| 006 | Text already saved |
| 007 | Transaction comments could not be read in the database |
| 008 | Choose a customizing transaction |
| 009 | Relational operator &1 is not supported |
| 011 | Data object types &1 and &2 must not be compared with operator &3 |
| 012 | Element types &1 and &2 must not be compared with operator &3 |
| 013 | Element type &1 is not supported |
| 014 | String &1 cannot be converted to a number |
| 015 | Tables of &1 with different lines must not be compared with operator &2 |
| 016 | Calculation type "&1" not possible with element types &2 and &3 |
| 017 | Calculation not possible for tables with different numbers of lines |
| 018 | Calculation not possible for data object types &1 and &2 |
| 019 | Calculation "&1" not possible for element type &2 (data object type &3) |
| 020 | Text of transaction is presently being processed |
| 021 | Text saved successfully |
| 022 | No transaction chosen |
| 023 | Unidentifiable error; cannot call up maintenance dialog correctly |
| 024 | Unofficial transaction; may only be used in an SAP system |
| 025 | Transport successful |
| 026 | Program &1 not found |
| 027 | Destination &1 for RFC does not exist |
| 030 | Invalid combination of parameters |
| 031 | Unknown element type &1 |
| 032 | Unknown data object type &1 |
| 033 | Unknown object type &1 |
| 035 | A workbench request is not supplied |
| 036 | A transport request for customizing objects is not supplied |
| 037 | Not transported applications can not contain transported objects |
| 038 | Selecting only objects that are not marked for deletion is not allowed |
| 040 | SAPscript documentation is not available for this object |
| 041 | Structures contain different fields; comparison not possible |
| 045 | Currency &1 does not exist in this system |
| 048 | Unit &1 does not exist in this system |
| 050 | Value &1 is invalid / is not supported |
| 051 | Timepoint type &1 is not supported |
| 052 | Timepoint is not valid |
| 053 | Operation &1 is not possible with timepoint type &2 |
| 054 | Invalid application id &1 |
| 060 | Application exit class &1 called with method &2 for ID &3 (type &4) |
| 061 | => Forcing copy to inactive version |
| 062 | No new version created for &1 |
| 063 | <= Copy to inactive version successful |
| 064 | Objects to deploy are inactive |
| 065 | Object &1 to deploy is missing or deleted |
| 066 | Object &1 to deploy is inactive. Check transport &2. |
| 067 | Object &1 was adapted by deployment |
| 070 | &1 objects have been modified |
| 071 | &1 no longer used objects have been deleted |
| 072 | No matching column in new version for column &1 in old version. |
| 073 | Adapting result data objects for decision table failed. |
| 075 | Inactive transports (T-tables) could not be activated ! |
| 076 | Try to deploy anyway. If not successful first check the errors here ! |
| 077 | Collision for function &1 was resolved successfully |
| 078 | Collision for function &1 could not be resolved automatically |
| 079 | Versions older than &1 days will be discarded for application &2 |
| 080 | Latest version is deployed |
| 081 | Last deployed version is inactive and may be faulty (on C-table) |
| 082 | Older version is deployed, a newer version is available |
| 083 | Function is not yet deployed |
| 084 | Function objects missing, deleted or not transported correctly |
| 085 | Latest version is deployed and has been modified |
| 086 | Older version is deployed and has been modified |
| 089 | No design-time system information available |
| 090 | Design-Time Information |
| 091 | System: &1, Client: &2, User: &3, Workspace: &4 |
| 092 | Configuration Request: &1, Transport Context: &2 |
| 093 | Deployment Summary |
| 094 | ...application is assigned to package &1 |
| 095 | Function &1 (&2) has successfully been deployed |
| 096 | BRFplus Deployment &1 &2 &3 &4 |
| 097 | &1 functions could not be activated due to collisions |
| 098 | Collisions occurred during activation of function &1 (&2) |
| 099 | ...belonging to application &1 (&2), SC: &3, AC: &4 |
| 100 | Invalid activation call; empty context object |
| 101 | Start of activation for function &1 (&2) |
| 102 | End of activation for function &1 (&2) |
| 103 | Invalid content in DB table &1; see long text for instructions |
| 104 | Wrong client; BCF content creation has to be done in client &1 |
| 105 | Error in the activation process of function &1 (&2); activation failed |
| 106 | &1&2&3&4 |
| 107 | Unsaved changes exist for &1 |
| 108 | Lock exists for &1 (ID &2 ) |
| 109 | Lock exists for client &1 |
| 110 | Collision was due to a change on &1 &2 (&3) |
| 111 | Object &1 does not exist in this system; transport is missing |
| 112 | No BCF client provided in table FDT_BCF_CLIENT |
| 113 | Object ID &1 is still locked after executing deployment exit |
| 114 | Client &1 is still locked after executing deployment |
| 115 | &1 functions have been activated successfully |
| 116 | &1 functions could not be activated |
| 117 | &1&2&3&4 |
| 118 | ------------------------------------------------------------------------- |
| 119 | More than one deployment exit class specified for function &1 |
| 120 | Exception in deployment exit &1 for function &2 |
| 121 | => Deployment exit &1 for function &2 started |
| 122 | <= Deployment exit &1 for function &2 failed |
| 123 | <= Deployment exit &1 for function &2 completed |
| 124 | => Determination of forced activation by deployment exit &1 started |
| 125 | <= Deployment exit &1 specified to force deployment of function &2 |
| 126 | <= Deployment exit &1 specified not to force deployment of function &2 |
| 127 | <= Deployment exit &1 specified skip the deployment of function &2 |
| 128 | Deployment exit &1 for function &2 registered |
| 129 | For Details use Transaction FDT_BCF_LOG in Target System &1 |
| 130 | ... with restrictions Object &1, Subobj &2, ID &3 |
| 131 | Any unsaved changes are discarded. |
| 132 | Invalid path: Business object &1 does not exist |
| 133 | Invalid path: Node &1 does not exist in the business object &2 |
| 134 | Invalid path: Attribute &1 does not exist in node &2 |
| 135 | Invalid path: Attribute &1 is not of structure type |
| 136 | Invalid path: Attribute type &1 of attribute &2 is not supported |
| 137 | ESF problem with BO ( &1 / &2 ) |
| 138 | Lock exists for application &1 |
| 140 | Deployment Exit Class &1 left the System in an inconsistent state |
| 141 | Application Exit class &1 of application &2 was called |
| 142 | Application component of class &1 is &2 |
| 143 | Processing started for objects marked for deletion |
| 144 | Processing started for executing logical deletions |
| 145 | Processing started for executing physical deletions |
| 146 | Processing of table type &1 |
| 147 | Processing for physical deletion of discarded versions was started |
| 148 | Processing started for objects marked for deletion |
| 149 | The processing of table type &1 is continued |
| 150 | Collision UI for BRFplus content objects not available |
| 151 | Processing for deleting unused objects was started |
| 153 | Versions older than &1 shall be logically discarded |
| 156 | Object index &1 - Change index &2 - GUID &3 |
| 160 | No BC connection defined for table &1 |
| 161 | Exception occurred during BC connection for table &1 |
| 162 | BC connection updated decision table &1 with data from DB table &1 |
| 163 | Foreign lock for decision table &1 - BC connector can't work |
| 164 | Activation problems during BC connector run for decision table &1 |
| 170 | Unknown BC database table &1 |
| 171 | Unknown BRFplus decision table &1 |
| 180 | Recursion error in application exit class &1 method &2 for id &3 |
| 181 | Internal error calling application exit class &1 method &2 id &3 |
| 190 | Could not lock object &2 due to user &1 |
| 191 | Could not lock application &2 due to user &1 |
| 192 | Could not lock client &1 due to user &2 |
| 193 | Could not lock all clients due to user &1 |
| 194 | |
| 195 | Could not lock object &2 for processing-relevant changes due to user &1 |
| 196 | Could not lock application &2 for proc.-relevant changes due to user &1 |
| 197 | Could not lock client &1 for processing-relevant changes due to user &2 |
| 198 | Could not lock all clients for processing-relevant changes due to user &1 |
| 199 | Wait and try to activate the changes later |
| 200 | &1: Can not delete using obj. &2 &3, it does not belong to current set |
| 201 | Object &1 cannot be deleted; it has undeleted or undeletable usages |
| 202 | &1 objects have been deleted successfully |
| 203 | No objects have to be deleted |
| 204 | &1 objects have been deleted successfully during application cleanup |
| 205 | Cannot activate object &1 due to erroneous referenced objects |
| 207 | Versions for &1 objects have been discarded successfully |
| 210 | You have no authorization to execute this functionality (category: &1) |
| 220 | String &1 cannot be converted to a quantity |
| 221 | String &1 cannot be converted to an amount |
| 260 | Name pattern '&1' matches to multiple objects |
| 270 | &1: &2 objects are fully discarded with timestamp &3 |
| 271 | &1: &2 objects are partially discarded with timestamp &3 |
| 272 | &1: &2 objects could not be discarded |
| 273 | Not selected &1 has &2 usages for the selected objects |
| 274 | Application &1 from client &2 has &3 usages for the selected objects |
| 280 | |
| 290 | |
| 295 | Provide either ID or element type |
| 296 | Provide either value or reference |
| 300 | BRFplus related status information |
| 301 | BRFplus deployment related information |
| 302 | BRFplus deployment status for specific function and client |
| 303 | Reporting deployment status to CCMS monitoring failed |
| 310 | Deployment by user &1 succeeded. |
| 311 | Deployment by user &1 failed. |
| 312 | Deployment of object &1 &2 failed |
| 313 | Deployment of object &1 &2 succeeded |
| 314 | Object &1 &2 has not been deployed |
| 315 | Object &1 &2 already deployed on latest version |
| 316 | Report problems to application component &1 |
| 317 | BRFplus application '&1' of package &2 |
| 318 | Deployment Status: &1 |
| 319 | Prior deployment status: &1 |
| 320 | Must not trigger deployment recursively |
| 321 | Must not trigger deployment in development client |
| 322 | Must specify at least 1 object to deploy |
| 323 | Must not deploy objects of different applications |
| 330 | Creation of error log failed |
| 331 | Adding message &1 &2 to error log failed |
| 332 | Saving error log failed |
| 350 | --------messages about quantities |
| 351 | The unit of measure '&1' has quantity dimension '&2', not '&3' |
| 352 | No quantity dimension defined with the given dimensions |
| 353 | Division by zero |
| 354 | Cannot add or subtract different quantity dimensions ('&1' and '&2') |
| 355 | Dimension with specific parameters not found |
| 356 | Dimension &1 does not exist |
| 357 | Product of quantities with dimensions ('&1' and '&2') is '&3', not '&4' |
| 358 | Division of quantities with dimensions ('&1' and '&2') is '&3', not '&4' |
| 359 | Quantities with dimensions ('&1' and '&2') cannot be multiplied |
| 360 | Quantities with dimensions ('&1' and '&2') cannot be divided |
| 400 | Object from table &2 does not exist in table &3: &1 |
| 401 | Messages for object &1 |
| 402 | &1 messages could not be added to the message log |
| 403 | Log for BRFPlus consistency check at &1 &2 |
| 404 | Object used by another object does not exist: &1, &2 |
| 405 | Deleted object is still used in undeleted object: &1, &2 |
| 406 | Entry for object in table &2 is incomplete: &1 |
| 407 | &1 entries from table &2 are missing in table &3: &4 |
| 408 | Deleted object is still used in &2 undeleted objects: &1, &3 |
| 409 | Application used in &2 objects does not exist: &1, &3 |
| 410 | Expression type used in &2 objects does not exist: &1, &3 |
| 411 | Application used in an object does not exist: &1, &2 |
| 412 | Expression type used in an object does not exist: &1, &2 |