Message Number list used by SAP ABAP Class CL_FDT_FLOW (FDT: Flow)
SAP ABAP Class 
CL_FDT_FLOW (FDT: Flow) is using
-
Class (225)
-
Data Element (4)
-
Table/Structure Field (177)
-
Interface (159)
-
Message Class (24)
-
Message Number (100)
-
Class Method (244)
-
Program (5)
-
Table (25)
| # | Object Type | Object Name | Object Description | Note |
|---|---|---|---|---|
 |
|
|||
| 1 | Message Number |
FDT_CHANGE_INFO - 498 | &1 lines were added to the range table of the condition | |
| 2 | Message Number |
FDT_CHANGE_INFO - 497 | &1 lines were changed in the range table of the condition | |
| 3 | Message Number |
FDT_CHANGE_INFO - 756 | Flow created with &1 node(s) and &2 connector(s) | |
| 4 | Message Number |
FDT_CHANGE_INFO - 755 | Node &1 of type &2 created | |
| 5 | Message Number |
FDT_CHANGE_INFO - 754 | Node &1 deleted | |
| 6 | Message Number |
FDT_CHANGE_INFO - 753 | Rule &1 for activity &2 created | |
| 7 | Message Number |
FDT_CHANGE_INFO - 752 | Rule &1 for activity &2 deleted | |
| 8 | Message Number |
FDT_CHANGE_INFO - 751 | End of validity period changed from &1 to &2 (activity &3) | |
| 9 | Message Number |
FDT_CHANGE_INFO - 750 | Start of validity period changed from &1 to &2 (activity &3) | |
| 10 | Message Number |
FDT_CHANGE_INFO - 749 | Position changed from &1 to &2 (activity &3) | |
| 11 | Message Number |
FDT_CHANGE_INFO - 748 | Switch changed from &1 to &2 (activity &3) | |
| 12 | Message Number |
FDT_CHANGE_INFO - 747 | Rule &1 for activity &2 changed: | |
| 13 | Message Number |
FDT_CHANGE_INFO - 746 | Gateway condition removed at branch order &1 (gateway &2) | |
| 14 | Message Number |
FDT_CHANGE_INFO - 745 | Default branch changed from &1 to &2 (gateway &3) | |
| 15 | Message Number |
FDT_CHANGE_INFO - 744 | Connector changed from &1 to &2 (gateway &3) | |
| 16 | Message Number |
FDT_CHANGE_INFO - 742 | Condition ID &1 removed (gateway &2) | |
| 17 | Message Number |
FDT_CHANGE_INFO - 499 | &1 lines were removed from the range table of the condition | |
| 18 | Message Number |
FDT_CHANGE_INFO - 658 | Incoming parameter for condition (type range) was changed from &1 to &2 | |
| 19 | Message Number |
FDT_CHANGE_INFO - 732 | Cycle threshold set from &1 to &2 | |
| 20 | Message Number |
FDT_CHANGE_INFO - 733 | 'Exception on error' setting was set from &1 to &2 | |
| 21 | Message Number |
FDT_CHANGE_INFO - 734 | Start of connector &1 has changed from &2 to &3 | |
| 22 | Message Number |
FDT_CHANGE_INFO - 735 | End of connector &1 has changed from &2 to &3 | |
| 23 | Message Number |
FDT_CHANGE_INFO - 736 | Connector &1 was deleted | |
| 24 | Message Number |
FDT_CHANGE_INFO - 737 | Connector &1 created with start ID &2 and end ID &3 | |
| 25 | Message Number |
FDT_CHANGE_INFO - 738 | Node text changed from &1 to &2 (node &3) | |
| 26 | Message Number |
FDT_CHANGE_INFO - 739 | Node type of node &1 changed from &2 to &3 | |
| 27 | Message Number |
FDT_CHANGE_INFO - 740 | Gateway condition for branch order &1 changed (gateway &2): | |
| 28 | Message Number |
FDT_CHANGE_INFO - 741 | Condition ID &1 added (gateway &2) | |
| 29 | Message Number |
FDT_CHANGE_INFO - 743 | Condition ID changed from &1 to &2 (gateway &3) | |
| 30 | Message Number |
FDT_CORE - 006 | No active version found for &1 with timestamp &2 | |
| 31 | Message Number |
FDT_CORE - 885 | Invalid time stamps in line &1; to-value &2 smaller / equal from-value &3 | |
| 32 | Message Number |
FDT_CORE - 302 | No &1 supplied for &2 | |
| 33 | Message Number |
FDT_CORE - 002 | Version &1 does not exist | |
| 34 | Message Number |
FDT_CORE - 000 | Unknown ID &1 | |
| 35 | Message Number |
FDT_EXPRESSIONS - 368 | Activty &1 has more than 100 rules (&2) | |
| 36 | Message Number |
FDT_EXPRESSIONS - 355 | Activity node &1 has no predecessor | |
| 37 | Message Number |
FDT_EXPRESSIONS - 369 | Switch for rule on position &1 has to be of a boolean value (Activity &2) | |
| 38 | Message Number |
FDT_EXPRESSIONS - 370 | Object at rule position &1 in activity &2 is not a rule | |
| 39 | Message Number |
FDT_EXPRESSIONS - 387 | No rule ID supplied for rule (activity: &1, rule position &2) | |
| 40 | Message Number |
FDT_EXPRESSIONS - 388 | No rules are enabled in activity &1 | |
| 41 | Message Number |
FDT_EXPRESSIONS - 389 | Gateway &1 has less than 2 conditions | |
| 42 | Message Number |
FDT_EXPRESSIONS - 390 | Nodes of type &1 must not have gateway conditions (node &2) | |
| 43 | Message Number |
FDT_EXPRESSIONS - 391 | The attribute 'exception on error' has to be of type Boolean | |
| 44 | Message Number |
FDT_EXPRESSIONS - 392 | Cycle threshold has to be less than &1 (actual value: &2) | |
| 45 | Message Number |
FDT_EXPRESSIONS - 393 | Cycle threshold has to be greater than &1 (actual value: &2) | |
| 46 | Message Number |
FDT_EXPRESSIONS - 394 | Activity &1 does not exist | |
| 47 | Message Number |
FDT_EXPRESSIONS - 394 | Activity &1 does not exist | |
| 48 | Message Number |
FDT_EXPRESSIONS - 395 | Connector &1 does not exist | |
| 49 | Message Number |
FDT_EXPRESSIONS - 395 | Connector &1 does not exist | |
| 50 | Message Number |
FDT_EXPRESSIONS - 396 | Error node &1 does not exist | |
| 51 | Message Number |
FDT_EXPRESSIONS - 396 | Error node &1 does not exist | |
| 52 | Message Number |
FDT_EXPRESSIONS - 397 | Node &1 is not an error node (actual node type: &2) | |
| 53 | Message Number |
FDT_EXPRESSIONS - 397 | Node &1 is not an error node (actual node type: &2) | |
| 54 | Message Number |
FDT_EXPRESSIONS - 398 | Gateway &1 does not exist | |
| 55 | Message Number |
FDT_EXPRESSIONS - 398 | Gateway &1 does not exist | |
| 56 | Message Number |
FDT_EXPRESSIONS - 399 | Node &1 is not a gateway (actual node type: &2) | |
| 57 | Message Number |
FDT_EXPRESSIONS - 399 | Node &1 is not a gateway (actual node type: &2) | |
| 58 | Message Number |
FDT_EXPRESSIONS - 400 | Node &1 was visited &2 times, only &3 times are allowed | |
| 59 | Message Number |
FDT_EXPRESSIONS - 401 | Processing error; flow processing terminated at error node &1 | |
| 60 | Message Number |
FDT_EXPRESSIONS - 402 | Node &1 is not an activity (actual node type: &2) | |
| 61 | Message Number |
FDT_EXPRESSIONS - 402 | Node &1 is not an activity (actual node type: &2) | |
| 62 | Message Number |
FDT_EXPRESSIONS - 562 | Invalid loop condition &1; boolean type required | |
| 63 | Message Number |
FDT_EXPRESSIONS - 366 | No rule provided for activity &1 | |
| 64 | Message Number |
FDT_EXPRESSIONS - 021 | Provide exactly one operand ID or range (position &1) | |
| 65 | Message Number |
FDT_EXPRESSIONS - 340 | Only one text dependency allowed, but &1 delivered (&2) | |
| 66 | Message Number |
FDT_EXPRESSIONS - 341 | ID of connector &1 is not a valid UUID | |
| 67 | Message Number |
FDT_EXPRESSIONS - 342 | Connector &1 does not have a starting node | |
| 68 | Message Number |
FDT_EXPRESSIONS - 343 | Start node ID &1 of connector &2 is not a valid UUID | |
| 69 | Message Number |
FDT_EXPRESSIONS - 344 | Connector &1 does not have an end point | |
| 70 | Message Number |
FDT_EXPRESSIONS - 345 | End node ID &1 of connector &2 is not a valid UUID | |
| 71 | Message Number |
FDT_EXPRESSIONS - 346 | Start node &1 from connector &2 does not exist | |
| 72 | Message Number |
FDT_EXPRESSIONS - 347 | End node &1 from connector &2 does not exist | |
| 73 | Message Number |
FDT_EXPRESSIONS - 348 | End node &1 is not connected | |
| 74 | Message Number |
FDT_EXPRESSIONS - 349 | Connector &1 starts at end node &2 | |
| 75 | Message Number |
FDT_EXPRESSIONS - 350 | Error node &1 is not connected | |
| 76 | Message Number |
FDT_EXPRESSIONS - 351 | Connector &1 starts at error node &2 | |
| 77 | Message Number |
FDT_EXPRESSIONS - 353 | Multiple or no successors (&1) are not allowed for start node &2 | |
| 78 | Message Number |
FDT_EXPRESSIONS - 367 | Nodes of type &1 (Node ID &2) cannot have rules | |
| 79 | Message Number |
FDT_EXPRESSIONS - 365 | Node ID &1 is not a valid UUID | |
| 80 | Message Number |
FDT_EXPRESSIONS - 364 | Node type &1 is not a valid node type | |
| 81 | Message Number |
FDT_EXPRESSIONS - 363 | Gateway &1 does not have a default branch | |
| 82 | Message Number |
FDT_EXPRESSIONS - 362 | Gateway &1 condition at branch &2 does not have a connector | |
| 83 | Message Number |
FDT_EXPRESSIONS - 361 | Only one default branch is allowed per gateway (Gateway &1) | |
| 84 | Message Number |
FDT_EXPRESSIONS - 358 | Conn &1 at gateway &2 branch order &3 has a different starting point &4 | |
| 85 | Message Number |
FDT_EXPRESSIONS - 357 | Connector &1 at gateway &2 at branch order &3 does not exist | |
| 86 | Message Number |
FDT_EXPRESSIONS - 356 | Gateway &1 has no predecessor | |
| 87 | Message Number |
FDT_EXPRESSIONS - 354 | Multiple or no successors (&1) are not allowed for activity node &2 | |
| 88 | Message Number |
FDT_EXPRESSIONS - 352 | &1 has multiple start nodes | |
| 89 | Message Number |
FDT_EXPRESSIONS - 359 | &1 has no start node | |
| 90 | Message Number |
FDT_TRACE_INFO - 505 | Processing of flow reached an end state | |
| 91 | Message Number |
FDT_TRACE_INFO - 504 | Processing of flow reached an error state | |
| 92 | Message Number |
FDT_TRACE_INFO - 503 | Gateway branch &1 is satisfied | |
| 93 | Message Number |
FDT_TRACE_INFO - 502 | Processing gateway node &1 | |
| 94 | Message Number |
FDT_TRACE_INFO - 501 | Processing activity node &1 | |
| 95 | Message Number |
FDT_TRACE_INFO - 455 | No condition met, taking default branch | |
| 96 | Message Number |
FDT_TRACE_INFO - 454 | Condition at branch order &1 is true | |
| 97 | Message Number |
FDT_TRACE_INFO - 453 | Gateway &1 is evaluated | |
| 98 | Message Number |
FDT_TRACE_INFO - 452 | Flow ends at error node &1 | |
| 99 | Message Number |
FDT_TRACE_INFO - 451 | Flow ends at end node &1 | |
| 100 | Message Number |
FDT_TRACE_INFO - 450 | Activity &1 is evaluated |
