SAP ABAP Message Class ICL_BRF (Messages of BRF-Related Claims Objects)
Basic Data
Hierarchy
☛
INSURANCE (Software Component) SAP Insurance
⤷ FS-CM (Application Component) Claims Management
⤷ ICL_BRF (Package) BRF in Claims Management
⤷ FS-CM (Application Component) Claims Management
⤷ ICL_BRF (Package) BRF in Claims Management
Attributes
Message class | ICL_BRF | |
Short Description | Messages of BRF-Related Claims Objects | |
Changed On | 20091125 | |
Last Changed At | 154755 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 100 | Choose a line of business first | The short text describes the object sufficiently | |
2 | 101 | No event object transferred to function module &1 | The short text describes the object sufficiently | |
3 | 102 | Module &2 cannot procure the requested structure &1 | The short text describes the object sufficiently | |
4 | 103 | Enter an existing task | Space: object requires documentation | |
5 | 104 | Activity management event &1 is not supported here | Space: object requires documentation | |
6 | 105 | &1 parameter/s expected - &2 parameter/s exist | Space: object requires documentation | |
7 | 106 | BRF Event: &1 - Field &2 of structure ICL_ACTUAL is initial | Space: object requires documentation | |
8 | 107 | Application class ICL or ICLE expected, <&1> found | Space: object requires documentation | |
9 | 108 | Error when casting event object to <&1> | Space: object requires documentation | |
10 | 109 | Enter a line of insurance | Space: object requires documentation | |
11 | 110 | Enter a date for the validity period | Space: object requires documentation | |
12 | 111 | Trigger &1 in application class &2 does not exist | Space: object requires documentation | |
13 | 112 | Enter a line of business for event &1 | Space: object requires documentation | |
14 | 113 | Enter a valid-to date that is after the valid-from date | Space: object requires documentation | |
15 | 114 | Enter a valid-from date and a valid-to date for the reference date | Space: object requires documentation | |
16 | 116 | Enter the logical operator that links the lines with one another | Space: object requires documentation | |
17 | 117 | Enter the first operand | Space: object requires documentation | |
18 | 118 | Enter the second operand | Space: object requires documentation | |
19 | 119 | Enter the comparison operator | Space: object requires documentation | |
20 | 120 | At least one target line of business already contains rules | Space: object requires documentation | |
21 | 121 | Task &1 does not exist | Space: object requires documentation | |
22 | 122 | You cannot use task &1. It is a purely manual task | Space: object requires documentation | |
23 | 123 | Rules have been found in at least one target line of business and deleted | The short text describes the object sufficiently | |
24 | 124 | Function not yet implemented | Space: object requires documentation | |
25 | 125 | Attempt to delete in table &1 was unsuccessful; sy-subrc = &2 | Space: object requires documentation | |
26 | 126 | Field &2 is missing in table &1 | Space: object requires documentation | |
27 | 127 | Prohibited attempt to access ICL_ACTUAL | Space: object requires documentation | |
28 | 128 | Transport of rule sets in application class &1 is not supported | The short text describes the object sufficiently | |
29 | 129 | Specify at least one condition | The short text describes the object sufficiently | |
30 | 130 | No event has been transferred to function module &1 | The short text describes the object sufficiently | |
31 | 131 | One target line of business is identical to source line of business &1 | The short text describes the object sufficiently | |
32 | 132 | Selection is incomplete | The short text describes the object sufficiently | |
33 | 133 | File &1 could not be opened | The short text describes the object sufficiently | |
34 | 134 | File found. Data will be imported | The short text describes the object sufficiently | |
35 | 135 | Table deleted | The short text describes the object sufficiently | |
36 | 136 | Table has not been deleted | The short text describes the object sufficiently | |
37 | 137 | Table &1 does not exist in the database | The short text describes the object sufficiently | |
38 | 138 | Data imported successfully to database table &1 | The short text describes the object sufficiently | |
39 | 139 | Data cannot be imported to database table &1 | The short text describes the object sufficiently | |
40 | 140 | Database table &1 not found | The short text describes the object sufficiently | |
41 | 141 | Select a class and object type | The short text describes the object sufficiently | |
42 | 142 | Table/s are empty. Fill them first | The short text describes the object sufficiently | |
43 | 143 | File &1 could not be opened | The short text describes the object sufficiently | |
44 | 144 | File found | The short text describes the object sufficiently | |
45 | 145 | Data imported successfully | The short text describes the object sufficiently | |
46 | 146 | There is no &1 in the table | The short text describes the object sufficiently | |
47 | 147 | No records exist in TBRF900 | The short text describes the object sufficiently | |
48 | 148 | The NAMEUPDATER may only be executed in SAP systems | The short text describes the object sufficiently | |
49 | 149 | The NAMEUPDATER has been replaced by RICL_BRF_UPDATE_OBJ_NAMES | The short text describes the object sufficiently | |
50 | 150 | No renaming orders found | The short text describes the object sufficiently | |
51 | 151 | The program in this version has not yet been released | The short text describes the object sufficiently | |
52 | 153 | This function is only permitted in SAP development systems | The short text describes the object sufficiently | |
53 | 154 | Enter at least one rule definition class | The short text describes the object sufficiently | |
54 | 157 | At least one comparison is empty - row was removed | The short text describes the object sufficiently | |
55 | 160 | Task or log entry &1 does not exist | The short text describes the object sufficiently | |
56 | 161 | Prompting text &1 does not exist | The short text describes the object sufficiently | |
57 | 163 | &1 is a log entry and not a task | The short text describes the object sufficiently | |
58 | 164 | Destination &1 found, but D, L, or P expected | The short text describes the object sufficiently | |
59 | 165 | Enter either an expression or a message variable | The short text describes the object sufficiently | |
60 | 166 | Choose at least one of the two options | The short text describes the object sufficiently | |
61 | 167 | &1 is a "purely manual task" | Space: object requires documentation | |
62 | 171 | Short text does not have any first message variable | The short text describes the object sufficiently | |
63 | 172 | Short text does not have any second message variable | The short text describes the object sufficiently | |
64 | 173 | Short text does not have any third message variable | The short text describes the object sufficiently | |
65 | 174 | Short text does not have any fourth message variable | The short text describes the object sufficiently | |
66 | 176 | Object &1 &2 already exists on the left and right side | The short text describes the object sufficiently | |
67 | 177 | Error when splitting table &1 | The short text describes the object sufficiently | |
68 | 200 | Properties of field &1 in table &2 have not been defined statically | The short text describes the object sufficiently | |
69 | 201 | Properties of field &1 in table &2 have not been defined dynamically | The short text describes the object sufficiently | |
70 | 202 | Unexpected mode (&1) of field &2 in table &3 - Possible: ANSU | The short text describes the object sufficiently | |
71 | 203 | Not all relevant fields of table &1 have mode N | The short text describes the object sufficiently | |
72 | 204 | Target expression &1 does not exist - expression will not be renamed | The short text describes the object sufficiently | |
73 | 205 | Target action &1 does not exist - action will not be renamed | The short text describes the object sufficiently | |
74 | 206 | Target rule set &1 does not exist - rule set will not be renamed | The short text describes the object sufficiently | |
75 | 500 | ICL TOUCH displays claim &1 | Space: object requires documentation | |
76 | 560 | Active object with version not matching 0000 cannot be deleted | The short text describes the object sufficiently |
History
Last changed on/by | 20091125 | SAP | |
SAP Release Created in | 471 |