Message Number list used by SAP ABAP Class CL_FDT_ACTN_MESSAGE (FDT: Abstract Message Action)
SAP ABAP Class CL_FDT_ACTN_MESSAGE (FDT: Abstract Message Action) is using
# Object Type Object Name Object Description Note
     
1 Message Number  FDT_BRS - 101 Communication failure during RFC call: &1 &2 &3 &4
2 Message Number  FDT_BRS - 101 Communication failure during RFC call: &1 &2 &3 &4
3 Message Number  FDT_CORE - 828 Message contains invalid message variable
4 Message Number  FDT_CORE - 816 Maximum length for the message almost reached; message may be truncated
5 Message Number  FDT_CORE - 820 Message text does not have a first message variable
6 Message Number  FDT_CORE - 821 Message text does not have a second message variable
7 Message Number  FDT_CORE - 822 Message text does not have a third message variable
8 Message Number  FDT_CORE - 823 Message text does not have a fourth message variable
9 Message Number  FDT_CORE - 824 Message text requires a first message variable
10 Message Number  FDT_CORE - 825 Message text requires a second message variable
11 Message Number  FDT_CORE - 826 Message text requires a third message variable
12 Message Number  FDT_CORE - 827 Message text requires a fourth message variable
13 Message Number  FDT_CORE - 845 Different number of placeholders for message &1(&2) in language &3 and &4
14 Message Number  FDT_CORE - 829 Message number &1 in message class &2 does not exist for language &3
15 Message Number  FDT_CORE - 830 Message &1 &2 can contain only up to 4 placeholders
16 Message Number  FDT_CORE - 831 Enter the placeholders in right order
17 Message Number  FDT_CORE - 834 Message number &1 in message class &2 does not exist for any language
18 Message Number  FDT_CORE - 835 Message type '&1' (message &2) is not allowed in this application
19 Message Number  FDT_CORE - 835 Message type '&1' (message &2) is not allowed in this application
20 Message Number  FDT_CORE - 838 Supply either a free text or a predefined message for message number &1
21 Message Number  FDT_CORE - 839 Action definition incomplete (no message defined)
22 Message Number  FDT_CORE - 840 Message text for message &1 exceeds maximum length (255 characters)
23 Message Number  FDT_CORE - 814 Either supply free text or a T100 message for message, but not both
24 Message Number  FDT_CORE - 002 Version &1 does not exist
25 Message Number  FDT_CORE - 006 No active version found for &1 with timestamp &2
26 Message Number  FDT_CORE - 799 Message class &1 does not exist
27 Message Number  FDT_CORE - 800 No message found
28 Message Number  FDT_CORE - 800 No message found
29 Message Number  FDT_CORE - 801 Invalid variable &1
30 Message Number  FDT_CORE - 801 Invalid variable &1
31 Message Number  FDT_CORE - 802 Message number &1 in message class &2 does not exist
32 Message Number  FDT_CORE - 807 Message text of &1(&2) requires a first message variable
33 Message Number  FDT_CORE - 808 Message text of &1(&2) requires a second message variable
34 Message Number  FDT_CORE - 809 Message text of &1(&2) requires a third message variable
35 Message Number  FDT_CORE - 810 Message text of &1(&2) requires a fourth message variable
36 Message Number  FDT_CORE - 811 Variable &1 cannot be converted into text
37 Message Number  FDT_CORE - 811 Variable &1 cannot be converted into text
38 Message Number  FDT_CORE - 812 No check for variable &1 possible; data-dependent conversion into text
39 Message Number  FDT_CORE - 812 No check for variable &1 possible; data-dependent conversion into text
40 Message Number  FDT_CORE - 813 Either supply ID or text for a message variable &1, but not both
41 Message Number  FDT_CORE - 814 Either supply free text or a T100 message for message, but not both
42 Message Number  FDT_CORE - 815 Wrong message type set.
43 Message Number  FDT_DSM - 000 Error calling function module &1
44 Message Number  FDT_DSM - 000 Error calling function module &1