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
⤷ 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 | 000 | Message log is updated | The short text describes the object sufficiently | |
2 | 001 | Field &1-&2 of ABBID &3 deleted because of missing Customizing setting | The short text describes the object sufficiently | |
3 | 002 | Attribute manager lock error | The short text describes the object sufficiently | |
4 | 003 | Geolocation could not be determined for technical object &1 | Space: object requires documentation | |
5 | 004 | Geolocation determination of tech.obj. &1 continued using tech.obj. &2 | The short text describes the object sufficiently | |
6 | 005 | Geolocation determination of technical object &1 started | The short text describes the object sufficiently | |
7 | 006 | Address of technical object &1 determined using address number &2 | The short text describes the object sufficiently | |
8 | 007 | Tech.obj. &1 address cannot be determined because of missing address no. | The short text describes the object sufficiently | |
9 | 008 | Address number &1 passed check | The short text describes the object sufficiently | |
10 | 009 | Address number &1 did not pass check | The short text describes the object sufficiently | |
11 | 010 | Address of technical object &1 determined using partner &2 | The short text describes the object sufficiently | |
12 | 011 | Geolocation determined internally using source &1 (accuracy: &2) | The short text describes the object sufficiently | |
13 | 012 | Geolocation determined using geocode source &1 (accuracy: &2) | The short text describes the object sufficiently | |
14 | 013 | Address of technical object &1 cannot be determined using partner | The short text describes the object sufficiently | |
15 | 014 | Geolocation cannot be determined internally | The short text describes the object sufficiently | |
16 | 015 | Geolocation cannot be determined using geocoding service | The short text describes the object sufficiently | |
17 | 016 | ID mapping returned some results for technical object &1 | The short text describes the object sufficiently | |
18 | 017 | ID mapping API not found | The short text describes the object sufficiently | |
19 | 018 | Local business system could not be determined during ID mapping | The short text describes the object sufficiently | |
20 | 019 | Invalid object type code &2 entered for technical object &1 | The short text describes the object sufficiently | |
21 | 020 | Invalid ID scheme code &2 entered for technical object &1 | The short text describes the object sufficiently | |
22 | 021 | No mapped IDs found in external system for technical object &1 | The short text describes the object sufficiently | |
23 | 022 | BAdI execution of int./ext. ID mapping and geodatabase call failed | The short text describes the object sufficiently | |
24 | 023 | Int./Ext. ID mapping failed to provide the map | The short text describes the object sufficiently | |
25 | 024 | Enter a value in all required fields | The short text describes the object sufficiently | |
26 | 025 | Inappropriate structure name | The short text describes the object sufficiently | |
27 | 026 | Incorrect data | The short text describes the object sufficiently | |
28 | 027 | Personalization cannot be locked | The short text describes the object sufficiently | |
29 | 028 | Geolocation could not be determined | The short text describes the object sufficiently | |
30 | 029 | Geolocation of &1 determined by parent object &2 | The short text describes the object sufficiently | |
31 | 030 | Geolocation successfully determined | The short text describes the object sufficiently | |
32 | 031 | &1 does not exist for technical object &2 | The short text describes the object sufficiently | |
33 | 032 | Geocoordinates successfully determined for object &1 | The short text describes the object sufficiently | |
34 | 040 | Missing Customizing to perform layer query to ESRI MapServer Web service | The short text describes the object sufficiently | |
35 | 041 | Error occurred while HTTP sending/receiving toward ESRI Web service | The short text describes the object sufficiently | |
36 | 042 | Error in query parameters while querying ESRI Web service | The short text describes the object sufficiently | |
37 | 043 | Error while parsing HTTP response in JSON form with regular expressions | The short text describes the object sufficiently | |
38 | 044 | Inappropriate or non-existent RFC destination | The short text describes the object sufficiently | |
39 | 050 | ***** Messages on Network Display | The short text describes the object sufficiently | |
40 | 051 | There is no available network for the object | The short text describes the object sufficiently | |
41 | 060 | The short text describes the object sufficiently | ||
42 | 070 | *** Messages to object navigator | The short text describes the object sufficiently | |
43 | 071 | Select at least one row | The short text describes the object sufficiently | |
44 | 080 | *** Settings messages | The short text describes the object sufficiently | |
45 | 081 | No icon set for object type "&1" | The short text describes the object sufficiently | |
46 | 082 | No icon set for technical object type "&1", category "&2" | The short text describes the object sufficiently | |
47 | 083 | The short text describes the object sufficiently |
History
Last changed on/by | 20100310 | SAP | |
SAP Release Created in | 605 |