SAP ABAP Message Class FDT_HANA (BRFplus: HANA Integration)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-SRV-BR (Application Component) BRFplus - ABAP-Based Business Rules
⤷ SFDT_HANA (Package) BRFplus: HANA Integration
⤷ BC-SRV-BR (Application Component) BRFplus - ABAP-Based Business Rules
⤷ SFDT_HANA (Package) BRFplus: HANA Integration
Attributes
Message class | FDT_HANA | |
Short Description | BRFplus: HANA Integration | |
Changed On | 20141121 | |
Last Changed At | 124013 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | &1 &2 &3 &4 | The short text describes the object sufficiently | |
2 | 010 | Could not establish database connection &1 - see transaction DBCO | The short text describes the object sufficiently | |
3 | 011 | Failed to read &1 &2 (&3) | The short text describes the object sufficiently | |
4 | 012 | Failed to write &1 &2 (&3) | The short text describes the object sufficiently | |
5 | 013 | Failed to search for &1 (&2) | The short text describes the object sufficiently | |
6 | 014 | Failed to delete &1 &2 (&3) | The short text describes the object sufficiently | |
7 | 015 | Failed to activate &1 &2 (&3) | The short text describes the object sufficiently | |
8 | 016 | Could not find &1 &2 (&3) | The short text describes the object sufficiently | |
9 | 017 | An exception occured during the serialization of the meta data for &1 | The short text describes the object sufficiently | |
10 | 018 | Can not convert timepoint type &1 to HANA data object | The short text describes the object sufficiently | |
11 | 019 | Can not convert element type &1 to HANA data object | The short text describes the object sufficiently | |
12 | 020 | A SQL exception occured during the execution of a HANA catalog query | The short text describes the object sufficiently | |
13 | 021 | Catalog object &1 does not exist in schema &2 | The short text describes the object sufficiently | |
14 | 022 | Assign DB connection 'DEFAULT' or secondary DB connection to application | The short text describes the object sufficiently | |
15 | 023 | Schema &1 does not exist. | The short text describes the object sufficiently | |
16 | 024 | &2 '&3' is inconsistent with database connection &1: | The short text describes the object sufficiently | |
17 | 025 | Failed to create package &1 | The short text describes the object sufficiently | |
18 | 026 | Failed to check the existence of package &1 | The short text describes the object sufficiently | |
19 | 027 | Failed to list package(s) &1 | The short text describes the object sufficiently | |
20 | 100 | Condition column &1 is not of type data object | The short text describes the object sufficiently | |
21 | 101 | Row &1 column &2: The low value must not be a data object or expression | The short text describes the object sufficiently | |
22 | 102 | Row &1 column &2: The high value must not be a data object or expression | The short text describes the object sufficiently | |
23 | 103 | Row &1 in result column &2: The cell must not refer to an expression | The short text describes the object sufficiently | |
24 | 104 | &1 cannot be used for dynamic database views: | The short text describes the object sufficiently | |
25 | 105 | HANA database type &1 cannot not be mapped to an ABAP type | The short text describes the object sufficiently | |
26 | 106 | &1: HANA database type &2 cannot not be mapped to an ABAP type | The short text describes the object sufficiently | |
27 | 149 | Content object &1 in package &2 is not active | The short text describes the object sufficiently | |
28 | 150 | &1 is not a valid source type | The short text describes the object sufficiently | |
29 | 151 | Objects of type &1 are no catalog objects | The short text describes the object sufficiently | |
30 | 152 | Objects of type &1 are no content objects | The short text describes the object sufficiently | |
31 | 153 | Package &1 does not exist | The short text describes the object sufficiently | |
32 | 154 | Content object &1 does not exist in package &2 | The short text describes the object sufficiently | |
33 | 155 | Provide either a content object or a catalog object | The short text describes the object sufficiently | |
34 | 156 | Invalid source field mapping for &1: | The short text describes the object sufficiently | |
35 | 157 | &1: The source field name is not specified | The short text describes the object sufficiently | |
36 | 158 | &1: The BRFplus data element is not specified | The short text describes the object sufficiently | |
37 | 159 | &2 and &3: The same source field name &1 is used | The short text describes the object sufficiently | |
38 | 160 | &2 and &3: The source fields are mapped to the same element &1 | The short text describes the object sufficiently | |
39 | 161 | &2: &1 is unknown or deleted | The short text describes the object sufficiently | |
40 | 162 | &2: Object &1 is no data element | The short text describes the object sufficiently | |
41 | 163 | &1 and &2: The data elements share the same name &3 | The short text describes the object sufficiently | |
42 | 164 | &1: Field &2 does not exist in the source | The short text describes the object sufficiently | |
43 | 165 | &3: The type of DB field &1 is not convertible to the mapped element &2 | The short text describes the object sufficiently | |
44 | 166 | &3: The mapped element &2 is not convertible to the type of DB field &1 | The short text describes the object sufficiently | |
45 | 167 | No database field mapping has been defined | The short text describes the object sufficiently | |
46 | 168 | &2: Parameter &1 has not been defined | The short text describes the object sufficiently | |
47 | 169 | &2: Parameter &1 is not mapped to a result column | The short text describes the object sufficiently | |
48 | 170 | Invalid parameter definition for &1: | The short text describes the object sufficiently | |
49 | 171 | &2: Element ID &1 is used also for source field mapping (&3) | The short text describes the object sufficiently | |
50 | 172 | &2 and &3: Both use the same parameter ID &1 | The short text describes the object sufficiently | |
51 | 173 | &2: Name &1 is used also for source field mapping (&3) | The short text describes the object sufficiently | |
52 | 174 | &2 and &3: Both use the same parameter name &1 | The short text describes the object sufficiently | |
53 | 175 | &2: Parameters must not be of type amount or quantity | The short text describes the object sufficiently | |
54 | 176 | &2: Data object &1 must not be of type amount or quantity. | The short text describes the object sufficiently | |
55 | 177 | &2: Name &1 is used also for &3 | The short text describes the object sufficiently | |
56 | 178 | &2: Element ID &1 is used also for &3 | The short text describes the object sufficiently | |
57 | 180 | Invalid result view definition for &1: | The short text describes the object sufficiently | |
58 | 181 | &2 and &3: The same result view field name &1 occurs twice | Space: object requires documentation | |
59 | 182 | &2: Object &1 is no decision table | The short text describes the object sufficiently | |
60 | 183 | &1: &2 is no result element of expression &3 | The short text describes the object sufficiently | |
61 | 184 | &1: Expression &2 has no result of type element | The short text describes the object sufficiently | |
62 | 185 | &1: Choose an element of the result structure of expression &2 | The short text describes the object sufficiently | |
63 | 186 | &1 and &2: More than one expression is used for result calculation | The short text describes the object sufficiently | |
64 | 187 | &1: Different names for mapped field (&2) and result field (&3) | The short text describes the object sufficiently | |
65 | 188 | &1: The result field needs to be specified in each line | The short text describes the object sufficiently | |
66 | 189 | &1: Specify a source field or an expression or a parameter | The short text describes the object sufficiently | |
67 | 190 | &1: Source field must not be used with expression or parameter | The short text describes the object sufficiently | |
68 | 191 | No database fields have been defined | Space: object requires documentation | |
69 | 192 | &1: Different names for result field &2 and expression result &3 | The short text describes the object sufficiently | |
70 | 193 | &1: Parameter must not be used with expression or source field | The short text describes the object sufficiently | |
71 | 194 | &1: Expression must not be used with parameter or source field | The short text describes the object sufficiently | |
72 | 195 | &3: Expression &1 uses &2 which is no database field and no parameter | The short text describes the object sufficiently | |
73 | 196 | &1: Result data object &2 needs to be calculated by an expression | The short text describes the object sufficiently | |
74 | 197 | &2: Expression &1 must not have a result of type amount or quantity | The short text describes the object sufficiently | |
75 | 198 | &2 and source field &3: Both use the same parameter ID &1 | The short text describes the object sufficiently | |
76 | 199 | &2 and source field &3: Both use the same parameter name &1 | The short text describes the object sufficiently | |
77 | 200 | Specify exactly one field | The short text describes the object sufficiently | |
78 | 201 | &1 is no result field of the dynamic database view. | The short text describes the object sufficiently | |
79 | 202 | Insufficient configuration of the dynamic database view | The short text describes the object sufficiently | |
80 | 203 | &1: A renaming of fields is only allowed in comb. with calculated columns | The short text describes the object sufficiently | |
81 | 205 | Provide a &1 | The short text describes the object sufficiently | |
82 | 206 | &2: "CLIENT" is a reserved name that must not be used | The short text describes the object sufficiently | |
83 | 208 | Warnings in source field mapping for &1: | The short text describes the object sufficiently | |
84 | 209 | &3: Data from DB field &1 might not be convertible to mapped element &2 | The short text describes the object sufficiently | |
85 | 293 | &1 cannot be generated in rules on HANA. &1 has no calculated columns | The short text describes the object sufficiently | |
86 | 300 | Row &1 column &2: "Not Between" is not allowed | The short text describes the object sufficiently | |
87 | 301 | Row &1 column &2: "Between" is only allowed for time and number fields | The short text describes the object sufficiently | |
88 | 302 | Row &1 column &2: Invalid option "&3" | The short text describes the object sufficiently | |
89 | 303 | Row &1 column &2: Only single value enumerations are allowed | The short text describes the object sufficiently | |
90 | 304 | Column &2: Amount and quantity columns are not allowed | The short text describes the object sufficiently | |
91 | 305 | Invalid object type &1 | The short text describes the object sufficiently |
History
Last changed on/by | 20141121 | SAP | |
SAP Release Created in | 740 |