Message Number list used by SAP ABAP Class CL_FDT_RULESET (FDT: Ruleset)
SAP ABAP Class CL_FDT_RULESET (FDT: Ruleset) is using
# Object Type Object Name Object Description Note
     
1 Message Number  FDT_CHANGE_INFO - 292 &1 rules were deleted from the ruleset
2 Message Number  FDT_CHANGE_INFO - 291 &1 new rules were added in the ruleset
3 Message Number  FDT_CHANGE_INFO - 658 Incoming parameter for condition (type range) was changed from &1 to &2
4 Message Number  FDT_CHANGE_INFO - 643 Expr initializations were changed in the ruleset
5 Message Number  FDT_CHANGE_INFO - 642 &1 expression initializations were deleted from the ruleset
6 Message Number  FDT_CHANGE_INFO - 641 &1 new expression initializations were added in the ruleset
7 Message Number  FDT_CHANGE_INFO - 499 &1 lines were removed from the range table of the condition
8 Message Number  FDT_CHANGE_INFO - 498 &1 lines were added to the range table of the condition
9 Message Number  FDT_CHANGE_INFO - 497 &1 lines were changed in the range table of the condition
10 Message Number  FDT_CHANGE_INFO - 397 A new ruleset was created with &1 rules, &2 expr inits and &3 vars
11 Message Number  FDT_CHANGE_INFO - 305 Variables were changed in the ruleset
12 Message Number  FDT_CHANGE_INFO - 304 &1 variables were deleted from the ruleset
13 Message Number  FDT_CHANGE_INFO - 302 Ruleset priority changed from &1 to &2
14 Message Number  FDT_CHANGE_INFO - 303 &1 new variables were added in the ruleset
15 Message Number  FDT_CHANGE_INFO - 293 Rules were changed in the ruleset
16 Message Number  FDT_CHANGE_INFO - 294 Ruleset restriction was set to &1
17 Message Number  FDT_CHANGE_INFO - 295 Ruleset restriction was removed
18 Message Number  FDT_CHANGE_INFO - 296 Ruleset restriction was changed from &1 to &2
19 Message Number  FDT_CHANGE_INFO - 297 Ruleset condition was set to &1
20 Message Number  FDT_CHANGE_INFO - 298 Ruleset condition was removed
21 Message Number  FDT_CHANGE_INFO - 299 Ruleset condition was changed from &1 to &2
22 Message Number  FDT_CHANGE_INFO - 300 Ruleset switch was set to OFF
23 Message Number  FDT_CHANGE_INFO - 301 Ruleset switch was set to ON
24 Message Number  FDT_CORE - 883 Either provide rule or ruleset exit but not both (position &1)
25 Message Number  FDT_CORE - 882 Missing condition for ruleset exit (position &1)
26 Message Number  FDT_CORE - 881 Invalid condition; &1 does not have a boolean value
27 Message Number  FDT_CORE - 880 Conflict with rule set function restriction in line &1
28 Message Number  FDT_CORE - 879 Ruleset &1 is disabled
29 Message Number  FDT_CORE - 878 Invalid object &1; expression or data object needed
30 Message Number  FDT_CORE - 877 &1 occurs multiple times in the ruleset variables list
31 Message Number  FDT_CORE - 876 Error in initialization with &1
32 Message Number  FDT_CORE - 875 Rule &1 at position &2 is disabled
33 Message Number  FDT_CORE - 874 Exit condition at position &1 is disabled
34 Message Number  FDT_CORE - 872 Not more than 255 rules are allowed in a ruleset
35 Message Number  FDT_CORE - 871 Not more than 255 variables are allowed in a ruleset
36 Message Number  FDT_CORE - 867 No function assigned to ruleset &1
37 Message Number  FDT_CORE - 884 Invalid state of switch in line &1 (only "X" and " " are possible values)
38 Message Number  FDT_CORE - 885 Invalid time stamps in line &1; to-value &2 smaller / equal from-value &3
39 Message Number  FDT_CORE - 886 No rule provided at position &1
40 Message Number  FDT_CORE - 887 Invalid rule &2 at position &1
41 Message Number  FDT_CORE - 888 Function &1 used in rule(s) but does not support event mode
42 Message Number  FDT_CORE - 889 Invalid state of rule set switch (only "X" and " " are possible values)
43 Message Number  FDT_CORE - 892 Invalid change mode in line &1 (only " " and "I" are possible values)
44 Message Number  FDT_CORE - 894 No rules provided
45 Message Number  FDT_CORE - 895 &1 is used twice in the ruleset initialization
46 Message Number  FDT_CORE - 896 &1 is not a data object (position &2)
47 Message Number  FDT_CORE - 897 No object set at position &1
48 Message Number  FDT_CORE - 897 No object set at position &1
49 Message Number  FDT_CORE - 899 Restart options are only allowed for a ruleset exit (position &1)
50 Message Number  FDT_CORE - 866 Exception occured while checking the context for ruleset &1.
51 Message Number  FDT_CORE - 000 Unknown ID &1
52 Message Number  FDT_CORE - 002 Version &1 does not exist
53 Message Number  FDT_CORE - 006 No active version found for &1 with timestamp &2
54 Message Number  FDT_CORE - 087 Invalid node &1; ID does not exist or has the wrong object type
55 Message Number  FDT_CORE - 302 No &1 supplied for &2
56 Message Number  FDT_CORE - 380 Could not process function &2 in event mode; see longtext
57 Message Number  FDT_CORE - 417 &1 (used by ruleset precondition) is missing in the function context
58 Message Number  FDT_CORE - 482 Ruleset condition cannot be determined (unknown ID: &1)
59 Message Number  FDT_CORE - 483 Invalid object &1 set as ruleset condition
60 Message Number  FDT_CORE - 484 Rule condition cannot be determined (unknown ID: &1)
61 Message Number  FDT_CORE - 485 Invalid object &1 set as rule condition
62 Message Number  FDT_CORE - 853 Data object ID &1 from Initialize variable is missing in ruleset context
63 Message Number  FDT_CORE - 855 Temporary ruleset variable &1 needs a name (Pos&2)
64 Message Number  FDT_CORE - 856 Temporary ruleset variable &1 needs to have a unique name
65 Message Number  FDT_CORE - 857 Temporary ruleset variable &1 is not unique within the function context
66 Message Number  FDT_CORE - 858 Condition ID &1 from rule (pos &2) is missing in the ruleset context
67 Message Number  FDT_CORE - 859 ID &1 in range from rule (pos &2) is missing in the ruleset context
68 Message Number  FDT_CORE - 860 Data object ID &1 from rule (pos &2) is missing in the ruleset context
69 Message Number  FDT_CORE - 861 &1 (ruleset precondition) is missing in the function context
70 Message Number  FDT_CORE - 862 ID &1 in ruleset condition range is missing in the ruleset context
71 Message Number  FDT_CORE - 863 Condition &1 from rule (pos &2) is missing in the ruleset context
72 Message Number  FDT_CORE - 864 Data object &1 from rule (pos &2) is missing in the ruleset context
73 Message Number  FDT_CORE - 868 Neither ruleset &1 nor any of its rules has a function assigned
74 Message Number  FDT_CORE - 854 Data object &1 from Initialize variable is missing in the ruleset context
75 Message Number  FDT_CORE2 - 008 No rules are enabled in the ruleset
76 Message Number  FDT_CORE2 - 009 Restart option defined (position &1) but not supported by application
77 Message Number  FDT_EXPRESSIONS - 021 Provide exactly one operand ID or range (position &1)
78 Message Number  FDT_EXPRESSIONS - 021 Provide exactly one operand ID or range (position &1)
79 Message Number  FDT_EXPRESSIONS - 021 Provide exactly one operand ID or range (position &1)
80 Message Number  FDT_TRACE_INFO - 356 Precondition not fulfilled, skip the processing of current rule
81 Message Number  FDT_TRACE_INFO - 355 Exit condition not fulfilled, continue with ruleset processing
82 Message Number  FDT_TRACE_INFO - 354 Exit condition fulfilled, exit from ruleset processing
83 Message Number  FDT_TRACE_INFO - 353 Precondition fulfilled, triggering rule
84 Message Number  FDT_TRACE_INFO - 278 Ruleset initialization
85 Message Number  FDT_TRACE_INFO - 277 Rule processing: &1 (position &2)
86 Message Number  FDT_TRACE_INFO - 276 Precondition not satisfied; rule will not be processed
87 Message Number  FDT_TRACE_INFO - 275 Precondition satisfied; rule will be processed
88 Message Number  FDT_TRACE_INFO - 274 Ruleset exit condition not satisfied; processing continues
89 Message Number  FDT_TRACE_INFO - 273 Ruleset exit condition satisfied; exiting ruleset
90 Message Number  FDT_TRACE_INFO - 272 Ruleset condition satisfied; rule processing for &1 begins
91 Message Number  FDT_TRACE_INFO - 272 Ruleset condition satisfied; rule processing for &1 begins
92 Message Number  FDT_TRACE_INFO - 271 Ruleset condition not satisfied; rules will not be processed for &1
93 Message Number  FDT_TRACE_INFO - 271 Ruleset condition not satisfied; rules will not be processed for &1
94 Message Number  FDT_TRACE_INFO - 270 Evaluating precondition &1 for ruleset &2