| # |
Message |
Message Short Text |
Documentation status |
Authorization check |
| 1 |
000 |
Invalid connector type |
The short text describes the object sufficiently |
|
| 2 |
001 |
Connector definition not found |
The short text describes the object sufficiently |
|
| 3 |
002 |
Pinging remote system failed |
The short text describes the object sufficiently |
|
| 4 |
003 |
Communication failure with remote system &1 |
The short text describes the object sufficiently |
|
| 5 |
004 |
Script not found |
The short text describes the object sufficiently |
|
| 6 |
005 |
Variable is invalid |
The short text describes the object sufficiently |
|
| 7 |
006 |
No class found according to the search criteria |
The short text describes the object sufficiently |
|
| 8 |
007 |
Class '&1' is not a valid class for variable |
The short text describes the object sufficiently |
|
| 9 |
008 |
Creating Web Service proxy instance failed |
The short text describes the object sufficiently |
|
| 10 |
009 |
Web Service call failed |
The short text describes the object sufficiently |
|
| 11 |
010 |
BW queries with mandatory parameters are not supported |
The short text describes the object sufficiently |
|
| 12 |
011 |
Error when processing SAP query data string |
The short text describes the object sufficiently |
|
| 13 |
012 |
|
The short text describes the object sufficiently |
|
| 14 |
013 |
Web Service method '&1' returns error |
The short text describes the object sufficiently |
|
| 15 |
014 |
Web Service method '&1' processing error in remote side |
The short text describes the object sufficiently |
|
| 16 |
015 |
Parameter not found |
The short text describes the object sufficiently |
|
| 17 |
016 |
|
The short text describes the object sufficiently |
|
| 18 |
050 |
User group '&1' does not exist in connector &2 |
The short text describes the object sufficiently |
|
| 19 |
051 |
Query '&1' does not exist in connector &2 |
The short text describes the object sufficiently |
|
| 20 |
052 |
Query '&1' is locked, connector '&2' |
The short text describes the object sufficiently |
|
| 21 |
053 |
Query generation cancelled, connector '&1' |
The short text describes the object sufficiently |
|
| 22 |
054 |
All mandatory selection parameters have to be supplied, connector '&1' |
The short text describes the object sufficiently |
|
| 23 |
055 |
Variant '&1' does not exist in connector '&2' |
The short text describes the object sufficiently |
|
| 24 |
056 |
Query '&1' cannot be executed without variant, connector '&2' |
The short text describes the object sufficiently |
|
| 25 |
057 |
No authorization to execute query '&1', connector '&2' |
The short text describes the object sufficiently |
|
| 26 |
058 |
No data selected, connector '&1' |
The short text describes the object sufficiently |
|
| 27 |
059 |
Data export to memory failed, connector '&1' |
The short text describes the object sufficiently |
|
| 28 |
060 |
Retrieving selection options failed, connector '&2' |
The short text describes the object sufficiently |
|
| 29 |
061 |
Retrieving field list failed |
The short text describes the object sufficiently |
|
| 30 |
062 |
Functional area '&1' does not exist, connector '&2' |
The short text describes the object sufficiently |
|
| 31 |
063 |
Query '&1' does not exist in connector '&2' |
The short text describes the object sufficiently |
|
| 32 |
064 |
Variant '&1' does not exist in connector '&2' |
The short text describes the object sufficiently |
|
| 33 |
065 |
RFC does not exist in remote system '&1' |
The short text describes the object sufficiently |
|
| 34 |
066 |
Communication failure with remote system &1 &2 |
The short text describes the object sufficiently |
|
| 35 |
067 |
User group '&1' does not exist in connector '&2' |
The short text describes the object sufficiently |
|
| 36 |
068 |
System failure with remote system &1 &2 |
The short text describes the object sufficiently |
|
| 37 |
069 |
Storage type not found |
The short text describes the object sufficiently |
|
| 38 |
070 |
Query contains no data. Empty queries are not supported. |
The short text describes the object sufficiently |
|
| 39 |
071 |
No authorization to execute query |
The short text describes the object sufficiently |
|
| 40 |
072 |
Invalid selection values provided for query |
The short text describes the object sufficiently |
|
| 41 |
073 |
Connector-Grp connectiontype and connector connectiontype should be same |
The short text describes the object sufficiently |
|
| 42 |
074 |
Time stamp not found for query &1, connector &2 |
The short text describes the object sufficiently |
|
| 43 |
075 |
User language not installed in connector &1 |
The short text describes the object sufficiently |
|
| 44 |
076 |
Database table &1 does not exist in connector &2 |
The short text describes the object sufficiently |
|
| 45 |
077 |
Invalid variant '&1' in connector '&2' |
The short text describes the object sufficiently |
|
| 46 |
078 |
Application failure with webservice in connector &1 |
The short text describes the object sufficiently |
|
| 47 |
079 |
Job ID '&1' is invalid when obtaining business rule usage |
The short text describes the object sufficiently |
|
| 48 |
080 |
Only one deficient field is allowed for Web service based monitoring |
The short text describes the object sufficiently |
|
| 49 |
081 |
Not authorized to perform ad hoc query |
The short text describes the object sufficiently |
|
| 50 |
082 |
Logon &1 by Query Designer to verify &2 exists or not |
The short text describes the object sufficiently |
|
| 51 |
100 |
Metadata '&1' in usage '&2' does not exist |
The short text describes the object sufficiently |
|
| 52 |
101 |
Error retrieving value for metadata '&1' in usage '&2' |
The short text describes the object sufficiently |
|
| 53 |
102 |
Cannot load metadata repository usage |
The short text describes the object sufficiently |
|
| 54 |
103 |
Context for metadata '&1' in usage '&2' is invalid, contact administrator |
The short text describes the object sufficiently |
|
| 55 |
104 |
Context '&2' for metadata '&1' is missing, contact administrator |
The short text describes the object sufficiently |
|
| 56 |
105 |
Invalid context for method '&1', contact administrator |
The short text describes the object sufficiently |
|
| 57 |
106 |
Context is invalid, contact administrator |
The short text describes the object sufficiently |
|
| 58 |
107 |
Cannot get datasource for business rule'&1' |
The short text describes the object sufficiently |
|
| 59 |
150 |
Invalid Proxy |
The short text describes the object sufficiently |
|
| 60 |
151 |
Connector is required |
The short text describes the object sufficiently |
|
| 61 |
200 |
************************* Sub Scenario - Config ****************** |
The short text describes the object sufficiently |
|
| 62 |
201 |
Data not found, connector &1 |
The short text describes the object sufficiently |
|
| 63 |
202 |
Invalid timeframe or year |
The short text describes the object sufficiently |
|
| 64 |
203 |
Redundant Join Conditions proposed; manual maintenance required |
The short text describes the object sufficiently |
|
| 65 |
500 |
************************Event Monitoring*************************** |
The short text describes the object sufficiently |
|
| 66 |
501 |
Event not supported by system |
The short text describes the object sufficiently |
|
| 67 |
502 |
Check type '&1' is not valid |
The short text describes the object sufficiently |
|
| 68 |
503 |
No data in event |
The short text describes the object sufficiently |
|
| 69 |
504 |
Field '&1' is not valid |
The short text describes the object sufficiently |
|
| 70 |
505 |
Invalid cardinality for field '&1' in event definition |
The short text describes the object sufficiently |
|
| 71 |
506 |
Field '&1' does not match cardinality |
The short text describes the object sufficiently |
|
| 72 |
507 |
&1 of '&2' |
The short text describes the object sufficiently |
|
| 73 |
508 |
No processor found for event |
The short text describes the object sufficiently |
|
| 74 |
509 |
An unexpected error occurred |
The short text describes the object sufficiently |
|
| 75 |
510 |
An error occurred when processing event |
The short text describes the object sufficiently |
|
| 76 |
511 |
An error occurred when creating event |
The short text describes the object sufficiently |
|
| 77 |
512 |
Enter the processor |
The short text describes the object sufficiently |
|
| 78 |
513 |
Enter the check type |
The short text describes the object sufficiently |
|
| 79 |
514 |
Enter the cardinality |
The short text describes the object sufficiently |
|
| 80 |
515 |
Enter the aggregation method for field with cardinality '0..n' or '1..n' |
The short text describes the object sufficiently |
|
| 81 |
516 |
Aggregation not applicable for field with cardinality '1..1' or '0..1' |
The short text describes the object sufficiently |
|
| 82 |
517 |
Field '&1' not of type '&2' |
The short text describes the object sufficiently |
|
| 83 |
518 |
Field '&1' does not cover pattern '&2' |
The short text describes the object sufficiently |
|
| 84 |
519 |
Configuration Scenario Link is not configured for connector &1 |
The short text describes the object sufficiently |
|
| 85 |
520 |
CCI Connector is not configured for connector &1 |
The short text describes the object sufficiently |
|
| 86 |
521 |
CCI Connector information not found for scenario link &1 |
The short text describes the object sufficiently |
|