SAP ABAP Message Class EAMS_VB (EAMS: Visual Business)
Basic Data
Hierarchy
☛
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
⤷
PM (Application Component) Plant Maintenance
⤷
EAMS_VB (Package) VisualBusiness
⤷
⤷
Attributes
| Message class | EAMS_VB | |
| Short Description | EAMS: Visual Business | |
| Changed On | 20100310 | |
| Last Changed At | 200114 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | Message log is updated | The short text describes the object sufficiently | ||
| 2 | Field &1-&2 of ABBID &3 deleted because of missing Customizing setting | The short text describes the object sufficiently | ||
| 3 | Attribute manager lock error | The short text describes the object sufficiently | ||
| 4 | Geolocation could not be determined for technical object &1 | Space: object requires documentation | ||
| 5 | Geolocation determination of tech.obj. &1 continued using tech.obj. &2 | The short text describes the object sufficiently | ||
| 6 | Geolocation determination of technical object &1 started | The short text describes the object sufficiently | ||
| 7 | Address of technical object &1 determined using address number &2 | The short text describes the object sufficiently | ||
| 8 | Tech.obj. &1 address cannot be determined because of missing address no. | The short text describes the object sufficiently | ||
| 9 | Address number &1 passed check | The short text describes the object sufficiently | ||
| 10 | Address number &1 did not pass check | The short text describes the object sufficiently | ||
| 11 | Address of technical object &1 determined using partner &2 | The short text describes the object sufficiently | ||
| 12 | Geolocation determined internally using source &1 (accuracy: &2) | The short text describes the object sufficiently | ||
| 13 | Geolocation determined using geocode source &1 (accuracy: &2) | The short text describes the object sufficiently | ||
| 14 | Address of technical object &1 cannot be determined using partner | The short text describes the object sufficiently | ||
| 15 | Geolocation cannot be determined internally | The short text describes the object sufficiently | ||
| 16 | Geolocation cannot be determined using geocoding service | The short text describes the object sufficiently | ||
| 17 | ID mapping returned some results for technical object &1 | The short text describes the object sufficiently | ||
| 18 | ID mapping API not found | The short text describes the object sufficiently | ||
| 19 | Local business system could not be determined during ID mapping | The short text describes the object sufficiently | ||
| 20 | Invalid object type code &2 entered for technical object &1 | The short text describes the object sufficiently | ||
| 21 | Invalid ID scheme code &2 entered for technical object &1 | The short text describes the object sufficiently | ||
| 22 | No mapped IDs found in external system for technical object &1 | The short text describes the object sufficiently | ||
| 23 | BAdI execution of int./ext. ID mapping and geodatabase call failed | The short text describes the object sufficiently | ||
| 24 | Int./Ext. ID mapping failed to provide the map | The short text describes the object sufficiently | ||
| 25 | Enter a value in all required fields | The short text describes the object sufficiently | ||
| 26 | Inappropriate structure name | The short text describes the object sufficiently | ||
| 27 | Incorrect data | The short text describes the object sufficiently | ||
| 28 | Personalization cannot be locked | The short text describes the object sufficiently | ||
| 29 | Geolocation could not be determined | The short text describes the object sufficiently | ||
| 30 | Geolocation of &1 determined by parent object &2 | The short text describes the object sufficiently | ||
| 31 | Geolocation successfully determined | The short text describes the object sufficiently | ||
| 32 | &1 does not exist for technical object &2 | The short text describes the object sufficiently | ||
| 33 | Geocoordinates successfully determined for object &1 | The short text describes the object sufficiently | ||
| 34 | Missing Customizing to perform layer query to ESRI MapServer Web service | The short text describes the object sufficiently | ||
| 35 | Error occurred while HTTP sending/receiving toward ESRI Web service | The short text describes the object sufficiently | ||
| 36 | Error in query parameters while querying ESRI Web service | The short text describes the object sufficiently | ||
| 37 | Error while parsing HTTP response in JSON form with regular expressions | The short text describes the object sufficiently | ||
| 38 | Inappropriate or non-existent RFC destination | The short text describes the object sufficiently | ||
| 39 | ***** Messages on Network Display | The short text describes the object sufficiently | ||
| 40 | There is no available network for the object | The short text describes the object sufficiently | ||
| 41 | The short text describes the object sufficiently | |||
| 42 | *** Messages to object navigator | The short text describes the object sufficiently | ||
| 43 | Select at least one row | The short text describes the object sufficiently | ||
| 44 | *** Settings messages | The short text describes the object sufficiently | ||
| 45 | No icon set for object type "&1" | The short text describes the object sufficiently | ||
| 46 | No icon set for technical object type "&1", category "&2" | The short text describes the object sufficiently | ||
| 47 | The short text describes the object sufficiently |
History
| Last changed on/by | 20100310 | SAP | |
| SAP Release Created in | 605 |