/IWBEP/SBOD -
The following messages are stored in message class /IWBEP/SBOD: .
It is part of development package /IWBEP/SB_ODATA_DM in software component OPU-BSE-SB. This development package consists of objects that can be grouped under "SAP Gateway Service Builder - Domain Model Plugin".
It is part of development package /IWBEP/SB_ODATA_DM in software component OPU-BSE-SB. This development package consists of objects that can be grouped under "SAP Gateway Service Builder - Domain Model Plugin".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Fatal error |
| 001 | Type '&1&2&3' does not exist |
| 002 | Base type name '&1' is not unique |
| 003 | Base type name must not reference the actual type itself |
| 004 | Association must not be initial |
| 005 | Cardinality must not be initial |
| 006 | Principal entity name must not be initial |
| 007 | Principal entity '&1' does not exist in the data model |
| 008 | Dependent entity '&1' does not exist in the data model |
| 009 | Invalid left cardinality '&1' specified |
| 010 | Invalid right cardinality '&1' specified |
| 011 | Dependent entity name must not be initial |
| 012 | Name must not be initial |
| 013 | Association '&1' with association end '&2' does not exist |
| 014 | Navigation property name '&1&2&3' is not unique |
| 015 | Entity type '&1&2&3' does not exist |
| 016 | Invalid EDM core type |
| 017 | Association set must not be initial |
| 018 | Association set '&1' already used for data model. Enter a new name. |
| 019 | Left entity set is initial or contains invalid characters |
| 020 | Right entity set name is initial or contains invalid characters |
| 021 | '&1' is not an entity set of the principal entity of association '&2' |
| 022 | Entity set '&1' does not exist in this data model |
| 023 | Property '&1&2&3' does not exist |
| 024 | Relationship '&1' does not exist |
| 025 | Navigation property '&1' is not unique within inheritance hierarchy |
| 026 | Parameter '&1' does not exist |
| 027 | Entity Set '&1' does not exist |
| 028 | Relationship name must not be initial |
| 029 | Association '&1' does not exist in this data model |
| 030 | '&1' is not an entity set of the dependent entity of association '&2' |
| 031 | Principal entity '&1' does not exist in the model reference |
| 032 | Dependent entity '&1' does not exist in the model reference |
| 033 | Property '&1' does not exist in the Entity Type '&2' |
| 034 | Property '&1&2&3' must not define a complex type recursively |
| 035 | Core Type '&1' not valid |
| 036 | Constant Expression Type '&1' not valid |
| 037 | Qualifier: &1&2&3&4 |
| 038 | ABAP type cannot be determined due to invalid facet values |
| 039 | Invalid type definition due to recursive base type assignment |
| 040 | XSD ABAP data types are not supported |
| 041 | Both Principal and Dependent Entity cannot be from Data Source References |
| 042 | Principal and Dependent Entity Sets cannot be from Data Source References |
| 043 | Facets and SAP Annotations will be fetched from base service |
| 050 | Entity type name '&1' is reserved |
| 090 | Entity Type '&1' defines the invalid semantic value '&2' |
| 091 | Entity Set '&1' defines the invalid semantic value '&2' |
| 092 | Property name '&1&2&3' is not unique in regards to the parent |
| 095 | Property '&1&2&3' is a key and must set nullable to false |
| 100 | Non-unique name '&1' in model |
| 101 | Entity Type name '&1' is not unique |
| 102 | Complex Type name '&1' is not unique |
| 103 | Association name '&1' not unique |
| 104 | Property name '&1&2&3' not unique |
| 105 | Property '&1&2&3' must define a Data Type |
| 106 | Entity Type '&1&2&3' must define at least one key property |
| 107 | Entity Type '&1' defines inheritance cycle |
| 108 | Complex Type '&1&2&3' defines inheritance cycle |
| 109 | Property name '&1' is not unique within inheritance hierarchy |
| 110 | Property '&1&2&3' has got complex type and must set nullable to false |
| 111 | Entity Type '&1' defines more than one author property |
| 112 | Entity Type '&1&2&3' defines more than one etag property |
| 113 | Entity Type '&1' defines more than one published property |
| 114 | Entity Type '&1' defines more than one title property |
| 115 | Entity Type '&1' defines more than one updated property |
| 116 | Property '&1' must not define add. ABAP type mapping |
| 117 | Properties of complex type '&1' must not define add. ABAP type mappings |
| 118 | Property ABAP type mapping of complex type '&1' is not complete |
| 119 | Property '&1' ABAP type mapping is not complete |
| 120 | Principal Key for Referential Constraint must not be initial |
| 121 | All keys of principal entity should be mapped in referential constraint |
| 122 | Principal Key '&1' for referential constraint must be a key property |
| 123 | Dependent Property for referential constraint must not be initial |
| 124 | Referential Constraint for principal key '&1' is not unique |
| 125 | Function Import name '&1' not unique |
| 126 | Principal Entity '&1' for referential constraint does not exist |
| 127 | Dependent Entity '&1' for Referential Constraint does not exist |
| 128 | Principal key '&1' for Referential Constraint does not exist |
| 129 | Dependent Property '&1' for Referential Constraint does not exist |
| 130 | Association must not be initial |
| 131 | Association does not exist |
| 132 | Principal Entity Set Name must not be initial |
| 133 | Entity Set does not exist |
| 135 | Function Import '&1' may not specify an Entity Set |
| 137 | Function Import '&1': Entity Set not based on specified Entity Type |
| 138 | Function Import '&1': Key of type Edm.Date*/Edm.Guid not allowed for 0..1 |
| 139 | Function Import '&1': Return Cardinality 0..1 is not recommended |
| 140 | Principal key type must be the same as the dependent property type |
| 141 | Entity Set name '&1' not unique |
| 142 | Entity Set '&1&2&3' must define an entity type |
| 143 | Association Set name '&1' is not unique |
| 144 | Property '&1&2&3' is a key and must not have a complex type |
| 145 | Property '&1&2&3' must not have a negative max length |
| 146 | Function Import '&1': Entity Set required |
| 147 | Function Import '&1': No return is currently not supported by the runtime |
| 148 | Entity Type '&1&2&3' is mapped to an invalid ABAP structure |
| 149 | Complex Type '&1&2&3' is mapped to an invalid ABAP structure |
| 150 | Node name '&1' contains special characters |
| 151 | Node name '&1' must start with a letter |
| 152 | Principal Entity must be set |
| 153 | Dependent Entity must be set |
| 154 | Complex Type '&1&2&3' must define at least one property |
| 155 | Dependent Entity Set must not be initial |
| 156 | Function Import parameter name '&1' not unique |
| 157 | Function Import parameter '&1' must not have negative max length |
| 158 | Function Import parameter '&1' does not have a type assignment |
| 159 | Data type '&1' does not exist |
| 160 | Function Import '&1': No return type expected (check Return Type Kind) |
| 161 | Function Import '&1': Return type expected (check Return Type Kind) |
| 162 | ABAP Field name '&1' contains special characters |
| 163 | ABAP Field name '&1' must start with a letter |
| 164 | ABAP Field name '&1' is not unique |
| 165 | Invalid Name '&1' |
| 166 | ABAP field name '&1' is not part of the ABAP structure '&2&3&4' |
| 167 | ABAP field name '&1' is not unique |
| 168 | Property '&1' is a complex type but ABAP field name is an element type |
| 169 | ABAP type '&1' not applicable to EDM Core Type '&2' |
| 170 | Potential loss of data; ABAP type is more restrictive |
| 171 | Potential loss of data; EDM type is more restrictive |
| 172 | Potential loss of data; EDM to ABAP and ABAP to EDM |
| 173 | Facet '&1' not applicable for EDM type '&2' |
| 174 | Facet '&1' with invalid value |
| 175 | Facet '&1' with invalid value; value has been corrected |
| 176 | Input value is too long; the maximal length is '&1' |
| 177 | Invalid Input |
| 178 | Invalid Boolean. Please use ' ', 'X', 'TRUE', 'FALSE', '0' or '1' |
| 179 | CSDL value is longer than length of dynpro field. Check the CSDL value |
| 180 | The input is longer than the type of the underlying field allows |
| 181 | The input is not a number |
| 182 | The number is too large for the underlying field |
| 183 | The number is too low for the underlying field |
| 184 | The precision of '&1' is too low for the input |
| 185 | The Input is invalid for type '&1' |
| 186 | Invalid date format for '&1' |
| 187 | Invalid date for '&1' |
| 188 | Invalid time format for '&1' |
| 189 | Invalid time for '&1' |
| 190 | Invalid qualifier content |
| 191 | Invalid qualifier attachment container |
| 192 | Invalid offset format for '&1' |
| 193 | Invalid offset for '&1' |
| 194 | Missing offset for '&1' |
| 195 | Enter the string without quotes |
| 197 | Inconsistent facet values |
| 198 | Valid type mapping with further findings |
| 199 | Valid type mapping; not precise, but best possible |
| 200 | Conversion error possible; ABAP type is more restrictive |
| 201 | Conversion error possible; EDM type is more restrictive |
| 202 | Conversion error possible; ABAP to EDM and EDM to ABAP |
| 203 | ABAP type is too small for the minimum requirements of &1 |
| 204 | Use instead a packed number with &1 or more digits |
| 205 | Only valid for the minimum requirements of type &1 |
| 206 | A packed number with more digits is needed for seconds |
| 207 | Use instead a packed number with more digits or less decimals |
| 208 | &1 decimal places might be lost in the mapping from '&2' to ABAP |
| 209 | Not valid for the full requirements of type &1 |
| 210 | A packed number with more digits is needed for subseconds |
| 211 | &1 decimal places might be lost in the mapping from ABAP to '&2' |
| 212 | The validity has to be ensured in the ABAP conversion exit |
| 213 | For currency fields the facet 'SCALE' has to be >= '&1' |
| 214 | Internal ABAP type P can only be allocated in chunks of 2 digits - 1 sign |
| 215 | A packed number with 1 digit less is sufficient without seconds |
| 216 | Map a DDIC data element or increase the facet 'precision' by 1 |
| 217 | Different decimal places allowed, because of currency value |
| 218 | ABAP Data Type 'DATE' does not allow B.C. date, Year 00 or negative year |
| 219 | The facet '&1' is not valid for ODATA version '&2' |
| 220 | Mapping of '&1' to '&2' needs conversion exit. |
| 221 | Map '&1' to ABAP TIMESTAMP for dates b.c. and in year 0 |
| 222 | Map a DDIC data element with 1 digit less alternatively |
| 223 | The precision of '&1' is too low for the ABAP type |
| 224 | Reduce the facet precision by '&1' |
| 225 | Increase the facet precision by '&1' |
| 227 | Invalid Name '&1' |
| 250 | The input has to be exactly &1 characters. |
| 251 | The number is too close to cero for type &1 |
| 252 | The input is no hexadecimal number for type '&1' |
| 253 | The number is too precise for the type '&1' |
| 254 | The number of type '&1' is denormalized and therefore unprecise |
| 255 | The EDM type '&1' contains date und time. |
| 256 | A decimal number is not allowed for type '&1' |
| 257 | The ABAP type NUMC can not handle negative signs |
| 258 | Map instead to the data element '&1' |
| 259 | The ABAP type is too small to cover full precision + sign. |
| 260 | For unsigned ABAP values the EDM type might be too small. |
| 261 | Mapping '&1' to '&2' is limited to '&3' |
| 262 | ABAP '&1' is limited to a length of &2 characters |
| 263 | The input is valid for '&1', but can't mapped to ABAP |
| 264 | The valid max. value for '&1' is &2 |
| 265 | Map instead to the ABAP type '&1' |
| 266 | Map instead to a data element of type '&1' |
| 267 | Only the ABAP type may contain non numerical characters |
| 268 | Only the EDM type may contain non numerical characters |
| 269 | The facet 'precision' has to be larger than the facet 'scale' |
| 270 | The facet 'scale' can not be larger than the facet 'precision' |
| 271 | A valid ABAP type, that fits to the precision, will be proposed |
| 272 | ABAP FLOAT contains 1 more decimal digit than '&1' |
| 273 | '&1' allows non exponential representation of values |
| 274 | Facet 'Precision' has to be lower than &1 |
| 275 | Facet 'Scale' has to be lower than &1 |
| 276 | '&1' is limited to a length of &2 characters |
| 277 | The value of ABAP '&1' might be too high for '&2' |
| 278 | ABAP 'Float' is a 64 bit decimal number, '&1' is 32 bit |
| 279 | The value of &1 might be too high for ABAP '&2' |
| 280 | '&1' is limited to a length of &2 digits |
| 281 | ABAP '&1' is a &2 bit number |
| 282 | ABAP '&1' is limited to a length of &2 digits |
| 283 | The ABAP type '&1' can't handle negative values |
| 284 | The valid max. value for ABAP '&1' is &2 |
| 285 | ABAP '&1' may have up to &2 digits more than '&3' |
| 286 | '&1' may have up to &2 digits more than ABAP '&3' |
| 287 | ABAP '&1' may have up to &2 integer digits more than '&3' |
| 288 | '&1' may have up to &2 integer digits more than ABAP '&3' |
| 289 | ABAP '&1' may have up to &2 characters more than '&3' |
| 290 | '&1' may have up to &2 characters more than ABAP '&3' |
| 291 | ABAP '&1' contains not only date, but also time. |
| 292 | ABAP Type '&1' for property '&2' is not supported |
| 293 | Precision must not be initial for Edm.Decimal Data Type |
| 300 | Vocabulary '&1' version '&2' imported successfully |
| 301 | Vocabulary '&1' version '&2' imported with warnings |
| 302 | Vocabulary '&1' version '&2' imported with errors |
| 303 | In ABAP '&1� Output Length is more than Max length |
| 304 | In ABAP '&1� Max Length is more than Output length |
| 305 | Assign Output Length of Domain '&1' to Max Length |
| 306 | Facet values are invalid for Edm.Int type |
| 311 | Property with Unit Property assignment cannot be marked as key |
| 312 | Could not assign RFC destination |
| 313 | Select a model reference |
| 314 | RFC destination assigned successfully; reload the transaction |
| 315 | Select one model reference at a time |
| 316 | &1 &2 &3 &4 |
| 317 | RFC Destination does not exist. |
| 318 | RFC Destination does not exist, data saved |
| 319 | ETag Property &1 is not valid |
| 320 | Structure based annotation not allowed for &1 as it has no ABAP Structure |
| 321 | Assign an ABAP Field Name for DDIC based Auto Annotation |
| 322 | Field &1 does not exist in &2 |
| 323 | Scale &1 cannot be used along with Variable Scale |
| 324 | Enter an ABAP Field Name |
| 325 | Invalid Unit Property Name '&1&2&3' |
| 326 | Entity Type name '&1&2&3' is not unique |
| 327 | Entity Set name '&1&2&3' is not unique |
| 328 | Complex Type Internal Name '&1' is not unique |
| 329 | Entity Type Internal Name '&1' is not unique |
| 330 | Entity Set Internal Name '&1' is not unique |
| 331 | Navigation Property Internal name '&1&2&3' is not unique |
| 350 | Data source reference name '&1' not unique |
| 351 | Dependent Property &1 for referential constraint must not be complex type |
| 352 | ABAP field name '&1' is not unique |
| 400 | Invalid name '&1&2&3'; prefix 'SAP__' is reserved |
| 401 | Invalid internal name '&1'; prefix 'SAP__' is reserved |
| 402 | Invalid Internal Name '&1' |
| 403 | Key Property cannot be of type '&1' |
| 404 | Invalid target multiplicity '&1' specified |
| 405 | Enter a Target Type for Navigation Property '&1&2&3' |
| 406 | Invalid name '&1&2&3' |
| 407 | Entity Type '&1&2&3' is not mapped to any ABAP structure |
| 408 | Invalid Partner '&1&2&3' |
| 409 | Property Path must not be initial |
| 410 | Referenced Property Path must not be initial |
| 411 | Navigation Property Path must not be initial |
| 412 | Target Entity Set must not be initial |
| 413 | Nullable and Collection flag must not be selected together |
| 414 | Property '&1' does not exist in Entity Type '&2' |
| 415 | Referenced Property Path:Enter Target Type in Navigation Property'&1&2&3' |
| 416 | Enter a valid Navigation Property |
| 417 | Entity Type of parent Entity Set '&1&2&3' is empty |
| 418 | Enter a valid Entity Set |
| 419 | Partner '&1' must have '&2' or an empty Partner |
| 420 | �&1� cannot be the Partner of �&2� |
| 421 | Property Path '&1&2&3' is not unique |
| 422 | Invalid Target Entity Set '&1&2&3' |
| 423 | Edm. type of Property Path and Referenced Property Path must be same |
| 424 | Selected Property '&1' is not from Entity Type '&2' |
| 425 | Navigation Property '&1' already used for binding in Entity Set '&2' |
| 426 | Complex Type '&1&2&3' is not mapped to any ABAP structure |
| 427 | Collection Navigation Property '&1' must not have Referential Constraint |
| 428 | Complex Type name '&1&2&3' is not unique |
| 429 | Invalid Name '&1&2&3' |
| 430 | Property does not exist |
| 431 | Complex Property is not supported for Referential Constraint |
| 432 | Complex Type '&1&2&3' defines recursive cycle |
| 433 | Entity Type '&1&2&3' defines recursive cycle |
| 434 | Invalid Selection. Select Property |
| 435 | Property �&1&2&3� does not exist in parent Entity Type |
| 436 | Facets are not applicable for Complex Property '&1&2&3' |
| 437 | Set Nullable to false for Complex Property '&1&2&3' |
| 438 | Key Property '&1&2&3' must be of Core Type |
| 439 | No Navigation Property Binding exists for Navigation Property '&1&2&3' |
| 440 | Nullable flag of artifacts in Referential Constraint does not match |
| 441 | Service Reference Internal Name '&1' is not unique |
| 442 | Type Kind Core Type cannot have structure '&1' as ABAP Field |
| 443 | Property '&1&2&3' does not exist in parent property |
| 444 | Complex Property not allowed. Select Primitive Property |
| 445 | Only Flat Structure are allowed. |
| 446 | Property Path must end with a primitive property |
| 447 | Referenced Property Path must end with a primitive property |
| 448 | DDIC Auto Annotation is not applicable for Property '&1&2&3' |
| 449 | Schema Alias '&1' is not unique |
| 450 | Property '&1&2&3' having ABAP Type as Currency cannot be a Key Property. |
| 451 | Multilevel inheritance is not supported |
| 452 | Function import name &1 is already Entity/Association/Complex name |