SAP ABAP Message Class /IWBEP/SBOD (/IWBEP/SBOD)
Basic Data
Hierarchy
☛
SAP_GWFND (Software Component) SAP Gateway Foundation
⤷
OPU-BSE-SB (Application Component) Gateway Service Builder
⤷
/IWBEP/SB_ODATA_DM (Package) Gateway Service Builder - Domain Model Plugin
SAP_GWFND (Software Component) SAP Gateway Foundation⤷
OPU-BSE-SB (Application Component) Gateway Service Builder⤷
/IWBEP/SB_ODATA_DM (Package) Gateway Service Builder - Domain Model Plugin 
Attributes
| Message class |  |
/IWBEP/SBOD |
| Short Description |  |
|
| Changed On |  |
20141120 |
| Last Changed At |  |
212331 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
Fatal error | The short text describes the object sufficiently | |
| 2 | 001 |
Type '&1' does not exist | The short text describes the object sufficiently | |
| 3 | 002 |
Base type name '&1' is not unique | The short text describes the object sufficiently | |
| 4 | 003 |
Base type name must not reference the actual type itself | The short text describes the object sufficiently | |
| 5 | 004 |
Association must not be initial | The short text describes the object sufficiently | |
| 6 | 005 |
Cardinality must not be initial | The short text describes the object sufficiently | |
| 7 | 006 |
Principal entity name must not be initial | The short text describes the object sufficiently | |
| 8 | 007 |
Principal entity '&1' does not exist in the data model | The short text describes the object sufficiently | |
| 9 | 008 |
Dependent entity '&1' does not exist in the data model | The short text describes the object sufficiently | |
| 10 | 009 |
Invalid left cardinality '&1' specified | The short text describes the object sufficiently | |
| 11 | 010 |
Invalid right cardinality '&1' specified | The short text describes the object sufficiently | |
| 12 | 011 |
Dependent entity name must not be initial | The short text describes the object sufficiently | |
| 13 | 012 |
Name must not be initial | The short text describes the object sufficiently | |
| 14 | 013 |
Association '&1' with association end '&2' does not exist | The short text describes the object sufficiently | |
| 15 | 014 |
Navigation property '&1' is not unique | The short text describes the object sufficiently | |
| 16 | 015 |
Entity type '&1' does not exist | The short text describes the object sufficiently | |
| 17 | 016 |
Invalid EDM core type | The short text describes the object sufficiently | |
| 18 | 017 |
Association set must not be initial | The short text describes the object sufficiently | |
| 19 | 018 |
Association set '&1' already used for data model. Enter a new name. | The short text describes the object sufficiently | |
| 20 | 019 |
Left entity set is initial or contains invalid characters | The short text describes the object sufficiently | |
| 21 | 020 |
Right entity set name is initial or contains invalid characters | The short text describes the object sufficiently | |
| 22 | 021 |
'&1' is not an entity set of the principal entity of association '&2' | The short text describes the object sufficiently | |
| 23 | 022 |
Entity set '&1' does not exist in this data model | The short text describes the object sufficiently | |
| 24 | 023 |
Property '&1' does not exist | The short text describes the object sufficiently | |
| 25 | 024 |
Relationship '&1' does not exist | The short text describes the object sufficiently | |
| 26 | 025 |
Navigation property '&1' is not unique within inheritance hierarchy | The short text describes the object sufficiently | |
| 27 | 026 |
Parameter '&1' does not exist | The short text describes the object sufficiently | |
| 28 | 027 |
Entity Set '&1' does not exist | The short text describes the object sufficiently | |
| 29 | 028 |
Relationship name must not be initial | The short text describes the object sufficiently | |
| 30 | 029 |
Association '&1' does not exist in this data model | The short text describes the object sufficiently | |
| 31 | 030 |
'&1' is not an entity set of the dependent entity of association '&2' | The short text describes the object sufficiently | |
| 32 | 031 |
Principal entity '&1' does not exist in the model reference | The short text describes the object sufficiently | |
| 33 | 032 |
Dependent entity '&1' does not exist in the model reference | The short text describes the object sufficiently | |
| 34 | 033 |
Property '&1' does not exist in the Entity Type '&2' | The short text describes the object sufficiently | |
| 35 | 034 |
Property '&1' must not define a complex type recursively | The short text describes the object sufficiently | |
| 36 | 035 |
Core Type '&1' not valid | The short text describes the object sufficiently | |
| 37 | 036 |
Constant Expression Type '&1' not valid | The short text describes the object sufficiently | |
| 38 | 037 |
Qualifier: &1&2&3&4 | The short text describes the object sufficiently | |
| 39 | 038 |
ABAP type cannot be determined due to invalid facet values | The short text describes the object sufficiently | |
| 40 | 039 |
Invalid type definition due to recursive base type assignment | The short text describes the object sufficiently | |
| 41 | 050 |
Entity type name '&1' is reserved | The short text describes the object sufficiently | |
| 42 | 090 |
Entity Type '&1' defines the invalid semantic value '&2' | The short text describes the object sufficiently | |
| 43 | 091 |
Entity Set '&1' defines the invalid semantic value '&2' | The short text describes the object sufficiently | |
| 44 | 092 |
Property name '&1' is not unique in regards to the parent | The short text describes the object sufficiently | |
| 45 | 095 |
Property '&1' is a key and must set nullable to false | The short text describes the object sufficiently | |
| 46 | 100 |
Non-unique name '&1' in model | The short text describes the object sufficiently | |
| 47 | 101 |
Entity Type name '&1' is not unique | Space: object requires documentation | |
| 48 | 102 |
Complex Type name '&1' is not unique | Space: object requires documentation | |
| 49 | 103 |
Association name '&1' not unique | Space: object requires documentation | |
| 50 | 104 |
Property name '&1' not unique | The short text describes the object sufficiently | |
| 51 | 105 |
Property '&1' must define a type | The short text describes the object sufficiently | |
| 52 | 106 |
Entity Type '&1' must define at least one key property | The short text describes the object sufficiently | |
| 53 | 107 |
Entity Type '&1' defines inheritance cycle | The short text describes the object sufficiently | |
| 54 | 108 |
Complex Type '&1' defines inheritance cycle | The short text describes the object sufficiently | |
| 55 | 109 |
Property name '&1' is not unique within inheritance hierarchy | The short text describes the object sufficiently | |
| 56 | 110 |
Property '&1' has got complex type and must set nullable to false | The short text describes the object sufficiently | |
| 57 | 111 |
Entity Type '&1' defines more than one author property | The short text describes the object sufficiently | |
| 58 | 112 |
Entity Type '&1' defines more than one etag property | The short text describes the object sufficiently | |
| 59 | 113 |
Entity Type '&1' defines more than one published property | The short text describes the object sufficiently | |
| 60 | 114 |
Entity Type '&1' defines more than one title property | The short text describes the object sufficiently | |
| 61 | 115 |
Entity Type '&1' defines more than one updated property | The short text describes the object sufficiently | |
| 62 | 116 |
Property '&1' must not define add. ABAP type mapping | The short text describes the object sufficiently | |
| 63 | 117 |
Properties of complex type '&1' must not define add. ABAP type mappings | The short text describes the object sufficiently | |
| 64 | 118 |
Property ABAP type mapping of complex type '&1' is not complete | The short text describes the object sufficiently | |
| 65 | 119 |
Property '&1' ABAP type mapping is not complete | The short text describes the object sufficiently | |
| 66 | 120 |
Principal Key for Referential Constraint must not be initial | The short text describes the object sufficiently | |
| 67 | 121 |
All keys of principal entity should be mapped in referential constraint | The short text describes the object sufficiently | |
| 68 | 122 |
Principal Key '&1' for referential constraint must be a key property | The short text describes the object sufficiently | |
| 69 | 123 |
Dependent Property for referential constraint must not be initial | The short text describes the object sufficiently | |
| 70 | 124 |
Referential Constraint for principal key '&1' is not unique | The short text describes the object sufficiently | |
| 71 | 125 |
Function Import name '&1' not unique | Space: object requires documentation | |
| 72 | 126 |
Principal Entity '&1' for referential constraint does not exist | The short text describes the object sufficiently | |
| 73 | 127 |
Dependent Entity '&1' for Referential Constraint does not exist | The short text describes the object sufficiently | |
| 74 | 128 |
Principal key '&1' for Referential Constraint does not exist | The short text describes the object sufficiently | |
| 75 | 129 |
Dependent Property '&1' for Referential Constraint does not exist | The short text describes the object sufficiently | |
| 76 | 130 |
Association must not be initial | The short text describes the object sufficiently | |
| 77 | 131 |
Association does not exist | The short text describes the object sufficiently | |
| 78 | 132 |
Principal Entity Set Name must not be initial | The short text describes the object sufficiently | |
| 79 | 133 |
Entity Set does not exist | The short text describes the object sufficiently | |
| 80 | 135 |
Function Import '&1' may not specify an Entity Set | Space: object requires documentation | |
| 81 | 137 |
Function Import '&1': Entity Set not based on specified Entity Type | The short text describes the object sufficiently | |
| 82 | 140 |
Principal key type must be the same as the dependent property type | The short text describes the object sufficiently | |
| 83 | 141 |
Entity Set name '&1' not unique | Space: object requires documentation | |
| 84 | 142 |
Entity Set '&1' must define an entity type | The short text describes the object sufficiently | |
| 85 | 143 |
Association Set name '&1' is not unique | Space: object requires documentation | |
| 86 | 144 |
Property '&1' is a key and must not have a complex type | The short text describes the object sufficiently | |
| 87 | 145 |
Property '&1' must not have a negative max length | The short text describes the object sufficiently | |
| 88 | 146 |
Function Import '&1': Entity Set required | Space: object requires documentation | |
| 89 | 147 |
Function Import '&1': No return is currently not supported by the runtime | The short text describes the object sufficiently | |
| 90 | 148 |
Entity Type '&1' is mapped to an invalid ABAP structure | The short text describes the object sufficiently | |
| 91 | 149 |
Complex Type '&1' is mapped to an invalid ABAP structure | The short text describes the object sufficiently | |
| 92 | 150 |
Node name '&1' contains special characters | The short text describes the object sufficiently | |
| 93 | 151 |
Node name '&1' must start with a letter | The short text describes the object sufficiently | |
| 94 | 152 |
Principal Entity must be set | The short text describes the object sufficiently | |
| 95 | 153 |
Dependent Entity must be set | The short text describes the object sufficiently | |
| 96 | 154 |
Complex Type '&1' must define at least one property | The short text describes the object sufficiently | |
| 97 | 155 |
Dependent Entity Set must not be initial | The short text describes the object sufficiently | |
| 98 | 156 |
Function Import parameter name '&1' not unique | The short text describes the object sufficiently | |
| 99 | 157 |
Function Import parameter '&1' must not have negative max length | The short text describes the object sufficiently | |
| 100 | 158 |
Function Import parameter '&1' does not have a type assignment | The short text describes the object sufficiently | |
| 101 | 159 |
Data type '&1' does not exist | The short text describes the object sufficiently | |
| 102 | 160 |
Function Import '&1': No return type expected (check Return Type Kind) | The short text describes the object sufficiently | |
| 103 | 161 |
Function Import '&1': Return type expected (check Return Type Kind) | The short text describes the object sufficiently | |
| 104 | 162 |
Technical name '&1' contains special characters | The short text describes the object sufficiently | |
| 105 | 163 |
Technical name '&1' must start with a letter | The short text describes the object sufficiently | |
| 106 | 164 |
Technical name '&1' is not unique | The short text describes the object sufficiently | |
| 107 | 165 |
Node name '&1': No special characters and the first one must be a letter | The short text describes the object sufficiently | |
| 108 | 166 |
ABAP field name '&1' is not part of the abap structure '&2' | The short text describes the object sufficiently | |
| 109 | 167 |
ABAP field name '&1' is not unique | The short text describes the object sufficiently | |
| 110 | 168 |
Property '&1' is a complex type but ABAP field name is an element type | Space: object requires documentation | |
| 111 | 169 |
ABAP type '&1' not applicable with EDM core type '&2' | The short text describes the object sufficiently | |
| 112 | 170 |
Potential loss of data; ABAP type is more restrictive | The short text describes the object sufficiently | |
| 113 | 171 |
Potential loss of data; EDM type is more restrictive | The short text describes the object sufficiently | |
| 114 | 172 |
Potential loss of data; EDM to ABAP and ABAP to EDM | The short text describes the object sufficiently | |
| 115 | 173 |
Facet '&1' not applicable for EDM type '&2' | The short text describes the object sufficiently | |
| 116 | 174 |
Facet '&1' with invalid value | The short text describes the object sufficiently | |
| 117 | 175 |
Facet '&1' with invalid value; value has been corrected | The short text describes the object sufficiently | |
| 118 | 176 |
Input value is too long; the maximal length is '&1' | The short text describes the object sufficiently | |
| 119 | 177 |
Invalid Input | The short text describes the object sufficiently | |
| 120 | 178 |
Invalid Boolean. Please use ' ', 'X', 'TRUE', 'FALSE', '0' or '1' | The short text describes the object sufficiently | |
| 121 | 179 |
CSDL value is longer than length of dynpro field. Check the CSDL value | The short text describes the object sufficiently | |
| 122 | 180 |
The input is longer than the type of the underlying field allows | The short text describes the object sufficiently | |
| 123 | 181 |
The input is not a number | The short text describes the object sufficiently | |
| 124 | 182 |
The number is too large for the underlying field | The short text describes the object sufficiently | |
| 125 | 183 |
The number is too low for the underlying field | The short text describes the object sufficiently | |
| 126 | 184 |
The precision of '&1' is too low for the input | The short text describes the object sufficiently | |
| 127 | 185 |
The Input is invalid for type '&1' | The short text describes the object sufficiently | |
| 128 | 186 |
Invalid date format for '&1' | The short text describes the object sufficiently | |
| 129 | 187 |
Invalid date for '&1' | The short text describes the object sufficiently | |
| 130 | 188 |
Invalid time format for '&1' | The short text describes the object sufficiently | |
| 131 | 189 |
Invalid time for '&1' | The short text describes the object sufficiently | |
| 132 | 190 |
Invalid qualifier content | The short text describes the object sufficiently | |
| 133 | 191 |
Invalid qualifier attachment container | The short text describes the object sufficiently | |
| 134 | 192 |
Invalid offset format for '&1' | The short text describes the object sufficiently | |
| 135 | 193 |
Invalid offset for '&1' | The short text describes the object sufficiently | |
| 136 | 194 |
Missing offset for '&1' | The short text describes the object sufficiently | |
| 137 | 197 |
Inconsistent facet values | The short text describes the object sufficiently | |
| 138 | 198 |
Valid type mapping with further findings | The short text describes the object sufficiently | |
| 139 | 199 |
Valid type mapping; not precise, but best possible | The short text describes the object sufficiently | |
| 140 | 200 |
Conversion error possible; ABAP type is more restrictive | The short text describes the object sufficiently | |
| 141 | 201 |
Conversion error possible; EDM type is more restrictive | The short text describes the object sufficiently | |
| 142 | 202 |
Conversion error possible; ABAP to EDM and EDM to ABAP | The short text describes the object sufficiently | |
| 143 | 203 |
ABAP type is too small for the minimum requirements of &1 | The short text describes the object sufficiently | |
| 144 | 204 |
Use instead a packed number with &1 or more digits | The short text describes the object sufficiently | |
| 145 | 205 |
Only valid for the minimum requirements of type &1 | The short text describes the object sufficiently | |
| 146 | 206 |
A packed number with more digits is needed for seconds | The short text describes the object sufficiently | |
| 147 | 207 |
Use instead a packed number with more digits or less decimals | The short text describes the object sufficiently | |
| 148 | 208 |
&1 decimal places might be lost in the mapping from '&2' to ABAP | The short text describes the object sufficiently | |
| 149 | 209 |
Not valid for the full requirements of type &1 | The short text describes the object sufficiently | |
| 150 | 210 |
A packed number with more digits is needed for subseconds | The short text describes the object sufficiently | |
| 151 | 211 |
&1 decimal places might be lost in the mapping from ABAP to '&2' | The short text describes the object sufficiently | |
| 152 | 212 |
The validity has to be ensured in the ABAP conversion exit | The short text describes the object sufficiently | |
| 153 | 213 |
For currency fields the facet 'SCALE' has to be >= '&1' | The short text describes the object sufficiently | |
| 154 | 214 |
Internal ABAP type P can only be allocated in chunks of 2 digits - 1 sign | The short text describes the object sufficiently | |
| 155 | 215 |
A packed number with 1 digit less is sufficient without seconds | The short text describes the object sufficiently | |
| 156 | 216 |
Map a DDIC data element or increase the facet 'precision' by 1 | The short text describes the object sufficiently | |
| 157 | 217 |
Different decimal places allowed, because of currency value | The short text describes the object sufficiently | |
| 158 | 218 |
The type '&1' allows dates before b.c., ABAP type 'D' not. | The short text describes the object sufficiently | |
| 159 | 219 |
The facet '&1' is not valid for ODATA version '&2' | The short text describes the object sufficiently | |
| 160 | 220 |
Mapping of '&1' to '&2' needs conversion exit. | The short text describes the object sufficiently | |
| 161 | 221 |
Map '&1' to ABAP TIMESTAMP for dates b.c. and in year 0 | The short text describes the object sufficiently | |
| 162 | 222 |
Map a DDIC data element with 1 digit less alternatively | The short text describes the object sufficiently | |
| 163 | 223 |
The precision of '&1' is too low for the ABAP type | The short text describes the object sufficiently | |
| 164 | 224 |
Reduce the facet precision by '&1' | The short text describes the object sufficiently | |
| 165 | 225 |
Increase the facet precision by '&1' | The short text describes the object sufficiently | |
| 166 | 250 |
The input has to be exactly &1 characters. | The short text describes the object sufficiently | |
| 167 | 251 |
The number is too close to cero for type &1 | The short text describes the object sufficiently | |
| 168 | 252 |
The input is no hexadecimal number for type '&1' | The short text describes the object sufficiently | |
| 169 | 253 |
The number is too precise for the type '&1' | The short text describes the object sufficiently | |
| 170 | 254 |
The number of type '&1' is denormalized and therefore unprecise | The short text describes the object sufficiently | |
| 171 | 255 |
The EDM type '&1' contains date und time. | The short text describes the object sufficiently | |
| 172 | 256 |
A decimal number is not allowed for type '&1' | The short text describes the object sufficiently | |
| 173 | 257 |
The ABAP type NUMC can not handle negative signs | The short text describes the object sufficiently | |
| 174 | 258 |
Map instead to the data element '&1' | The short text describes the object sufficiently | |
| 175 | 259 |
The ABAP type is too small to cover full precision + sign. | The short text describes the object sufficiently | |
| 176 | 260 |
For unsigned ABAP values the EDM type might be too small. | The short text describes the object sufficiently | |
| 177 | 261 |
Mapping '&1' to '&2' is limited to '&3' | The short text describes the object sufficiently | |
| 178 | 262 |
ABAP '&1' is limited to a length of &2 characters | The short text describes the object sufficiently | |
| 179 | 263 |
The input is valid for '&1', but can't mapped to ABAP | The short text describes the object sufficiently | |
| 180 | 264 |
The valid max. value for '&1' is &2 | The short text describes the object sufficiently | |
| 181 | 265 |
Map instead to the ABAP type '&1' | The short text describes the object sufficiently | |
| 182 | 266 |
Map instead to a data element of type '&1' | The short text describes the object sufficiently | |
| 183 | 267 |
Only the ABAP type may contain non numerical characters | The short text describes the object sufficiently | |
| 184 | 268 |
Only the EDM type may contain non numerical characters | The short text describes the object sufficiently | |
| 185 | 269 |
The facet 'precision' has to be larger than the facet 'scale' | The short text describes the object sufficiently | |
| 186 | 270 |
The facet 'scale' can not be larger than the facet 'precision' | The short text describes the object sufficiently | |
| 187 | 271 |
A valid ABAP type, that fits to the precision, will be proposed | The short text describes the object sufficiently | |
| 188 | 272 |
ABAP FLOAT contains 1 more decimal digit than '&1' | The short text describes the object sufficiently | |
| 189 | 273 |
'&1' allows non exponential representation of values | The short text describes the object sufficiently | |
| 190 | 274 |
Facet 'Precision' has to be lower than &1 | The short text describes the object sufficiently | |
| 191 | 275 |
Facet 'Scale' has to be lower than &1 | The short text describes the object sufficiently | |
| 192 | 276 |
'&1' is limited to a length of &2 characters | The short text describes the object sufficiently | |
| 193 | 277 |
The value of ABAP '&1' might be too high for '&2' | The short text describes the object sufficiently | |
| 194 | 278 |
ABAP 'Float' is a 64 bit decimal number, '&1' is 32 bit | The short text describes the object sufficiently | |
| 195 | 279 |
The value of &1 might be too high for ABAP '&2' | The short text describes the object sufficiently | |
| 196 | 280 |
'&1' is limited to a length of &2 digits | The short text describes the object sufficiently | |
| 197 | 281 |
ABAP '&1' is a &2 bit number | The short text describes the object sufficiently | |
| 198 | 282 |
ABAP '&1' is limited to a length of &2 digits | The short text describes the object sufficiently | |
| 199 | 283 |
The ABAP type '&1' can't handle negative values | The short text describes the object sufficiently | |
| 200 | 284 |
The valid max. value for ABAP '&1' is &2 | The short text describes the object sufficiently | |
| 201 | 285 |
ABAP '&1' may have up to &2 digits more than '&3' | The short text describes the object sufficiently | |
| 202 | 286 |
'&1' may have up to &2 digits more than ABAP '&3' | The short text describes the object sufficiently | |
| 203 | 287 |
ABAP '&1' may have up to &2 integer digits more than '&3' | The short text describes the object sufficiently | |
| 204 | 288 |
'&1' may have up to &2 integer digits more than ABAP '&3' | The short text describes the object sufficiently | |
| 205 | 289 |
ABAP '&1' may have up to &2 characters more than '&3' | The short text describes the object sufficiently | |
| 206 | 290 |
'&1' may have up to &2 characters more than ABAP '&3' | The short text describes the object sufficiently | |
| 207 | 291 |
ABAP '&1' contains not only date, but also time. | The short text describes the object sufficiently | |
| 208 | 300 |
Vocabulary '&1' version '&2' imported successfully | The short text describes the object sufficiently | |
| 209 | 301 |
Vocabulary '&1' version '&2' imported with warnings | The short text describes the object sufficiently | |
| 210 | 302 |
Vocabulary '&1' version '&2' imported with errors | The short text describes the object sufficiently |
History
| Last changed on/by | |
20141120 | SAP |
| SAP Release Created in | 200 |
