# |
Message |
Message Short Text |
Documentation status |
Authorization check |
1 |
000 |
Reporting was stopped by user |
The short text describes the object sufficiently |
|
2 |
001 |
Entry &1 already exists |
Space: object requires documentation |
|
3 |
002 |
Reporting table is empty |
The short text describes the object sufficiently |
|
4 |
003 |
No elements were selected |
The short text describes the object sufficiently |
|
5 |
004 |
Maintenance plan &1 does not exist |
The short text describes the object sufficiently |
|
6 |
005 |
No results were found |
The short text describes the object sufficiently |
|
7 |
006 |
Select a reporting mode from the drop-down menu |
The short text describes the object sufficiently |
|
8 |
007 |
Task list &1/&2/&3 does not exist |
The short text describes the object sufficiently |
|
9 |
010 |
Enter a document number |
The short text describes the object sufficiently |
|
10 |
011 |
Enter a piece of equipment |
The short text describes the object sufficiently |
|
11 |
012 |
Enter a functional location |
The short text describes the object sufficiently |
|
12 |
013 |
Enter a type for the document |
The short text describes the object sufficiently |
|
13 |
014 |
Enter a part for the document |
The short text describes the object sufficiently |
|
14 |
015 |
Enter a version for the document |
The short text describes the object sufficiently |
|
15 |
016 |
The structure has to be loaded before reporting can be run |
The short text describes the object sufficiently |
|
16 |
020 |
The following data is missing: &1, &2, &3, &4 |
Space: object requires documentation |
|
17 |
027 |
Task list does not belong to the functional location &1 |
The short text describes the object sufficiently |
|
18 |
028 |
Task list does not belong to the equipment &1 |
The short text describes the object sufficiently |
|
19 |
029 |
No counter data is available |
The short text describes the object sufficiently |
|
20 |
030 |
No maintenance plan data is available |
The short text describes the object sufficiently |
|
21 |
031 |
No document data is available |
The short text describes the object sufficiently |
|
22 |
032 |
No technical object is available |
The short text describes the object sufficiently |
|
23 |
033 |
No planning and scheduling data is available |
The short text describes the object sufficiently |
|
24 |
034 |
No task list is available |
The short text describes the object sufficiently |
|
25 |
035 |
Maintenance plan ready to be created |
The short text describes the object sufficiently |
|
26 |
036 |
Maintenance plan already created |
The short text describes the object sufficiently |
|
27 |
037 |
Maintenance plan ready for update |
The short text describes the object sufficiently |
|
28 |
038 |
Maintenance plan ready for creation and update |
The short text describes the object sufficiently |
|
29 |
039 |
Maintenance plan already updated |
The short text describes the object sufficiently |
|
30 |
040 |
No counter data is available for &1 &2 |
Space: object requires documentation |
|
31 |
041 |
The technical object has no notification status |
The short text describes the object sufficiently |
|
32 |
042 |
No task list is available - maintain the planning and scheduling data |
The short text describes the object sufficiently |
|
33 |
043 |
No document with these parameters exists |
The short text describes the object sufficiently |
|
34 |
044 |
No functional location with this identifier exists |
The short text describes the object sufficiently |
|
35 |
045 |
No piece of equipment with this identifier exists |
The short text describes the object sufficiently |
|
36 |
046 |
Message log is empty |
The short text describes the object sufficiently |
|
37 |
047 |
Document status is not set to 'Released' |
The short text describes the object sufficiently |
|
38 |
050 |
The functional location &1 already has a valid maintenance plan |
The short text describes the object sufficiently |
|
39 |
051 |
The equipment &1 already has a valid maintenance plan |
The short text describes the object sufficiently |
|
40 |
052 |
The status is red for functional location &1 |
The short text describes the object sufficiently |
|
41 |
053 |
The status is red for equipment &1 |
The short text describes the object sufficiently |
|
42 |
054 |
Maintenance plan creation is in process |
The short text describes the object sufficiently |
|
43 |
055 |
There is no old job data for selected record |
The short text describes the object sufficiently |
|
44 |
056 |
Old job data was deleted |
The short text describes the object sufficiently |
|
45 |
057 |
MaintPlant & and WorkCtr plant & are in different CtrlngAreas |
The short text describes the object sufficiently |
|
46 |
058 |
MaintPlant & and work center plant & have different company codes |
The short text describes the object sufficiently |
|
47 |
059 |
Planning plant is missing |
The short text describes the object sufficiently |
|
48 |
070 |
Planning and scheduling data does not exist |
The short text describes the object sufficiently |
|
49 |
071 |
Planning and scheduling data is currently locked |
The short text describes the object sufficiently |
|
50 |
072 |
Planning and scheduling data is marked for deletion |
The short text describes the object sufficiently |
|
51 |
073 |
Counter data does not exist |
The short text describes the object sufficiently |
|
52 |
074 |
Counter data is currently locked |
The short text describes the object sufficiently |
|
53 |
075 |
Counter data is marked for deletion |
The short text describes the object sufficiently |
|
54 |
080 |
Job &1 was successfully planned for the &2 at &3 |
The short text describes the object sufficiently |
|
55 |
081 |
The job log will contain the messages from the planned job |
The short text describes the object sufficiently |
|
56 |
101 |
Counter data has been updated successfully |
The short text describes the object sufficiently |
|
57 |
102 |
No measuring point information exists for equipment &1 |
The short text describes the object sufficiently |
|
58 |
103 |
No measuring point information exists for functional location &1 |
The short text describes the object sufficiently |
|
59 |
104 |
Cycle set has not been maintained. Enter cycle set data. |
The short text describes the object sufficiently |
|
60 |
105 |
Maintenance plan cannot be created |
The short text describes the object sufficiently |
|
61 |
106 |
Maintain all mandatory fields |
The short text describes the object sufficiently |
|
62 |
107 |
Select measuring point for &1 |
The short text describes the object sufficiently |
|
63 |
108 |
No measuring point exists for &1 for &2 &3 |
The short text describes the object sufficiently |
|
64 |
109 |
Maintenance plan cannot be updated |
The short text describes the object sufficiently |
|
65 |
110 |
Maintenance plan does not exist, so therefore cannot be updated |
The short text describes the object sufficiently |
|
66 |
111 |
Click the refresh button for up-to-date data |
The short text describes the object sufficiently |
|
67 |
112 |
Cycle set &1 does not exist. Change your entry. |
The short text describes the object sufficiently |
|
68 |
113 |
NOTE: Maintenance plan will be created with the active plan & sched data |
The short text describes the object sufficiently |
|
69 |
114 |
Counter data for &1 &2 |
The short text describes the object sufficiently |
|
70 |
115 |
Counter data '&1' has been created for &2 &3 |
The short text describes the object sufficiently |
|
71 |
116 |
Counter data has not been updated |
The short text describes the object sufficiently |
|
72 |
117 |
Counter data will be created after the current plan & sched data is saved |
The short text describes the object sufficiently |
|
73 |
118 |
Counter data cannot be created |
The short text describes the object sufficiently |
|
74 |
119 |
Transaction must be reloaded for the report to have up-to-date data |
The short text describes the object sufficiently |
|
75 |
120 |
Task list search cannot to be opened until a plan.plant has been selected |
The short text describes the object sufficiently |
|
76 |
150 |
|
The short text describes the object sufficiently |
|
77 |
151 |
Document data is not available |
The short text describes the object sufficiently |
|
78 |
152 |
No technical object is available |
The short text describes the object sufficiently |
|
79 |
153 |
No planning and scheduling data is available |
The short text describes the object sufficiently |
|
80 |
154 |
No task list is available |
The short text describes the object sufficiently |
|
81 |
155 |
Maintenance plan ready to be created |
The short text describes the object sufficiently |
|
82 |
156 |
Maintenance plan already created |
The short text describes the object sufficiently |
|
83 |
157 |
Click info. icon for further information |
The short text describes the object sufficiently |
|
84 |
158 |
Detailed information |
The short text describes the object sufficiently |
|
85 |
159 |
Maintenance plan ready for update |
The short text describes the object sufficiently |
|
86 |
160 |
|
The short text describes the object sufficiently |
|
87 |
161 |
Maintenance plan already updated |
The short text describes the object sufficiently |
|
88 |
162 |
No counter data is available |
The short text describes the object sufficiently |
|
89 |
163 |
functional location |
The short text describes the object sufficiently |
|
90 |
164 |
equipment |
The short text describes the object sufficiently |
|
91 |
165 |
Neither a notification status nor an order status is available |
The short text describes the object sufficiently |
|
92 |
166 |
Notification status: |
The short text describes the object sufficiently |
|
93 |
167 |
Order status: |
The short text describes the object sufficiently |
|
94 |
168 |
unavailable |
The short text describes the object sufficiently |
|
95 |
169 |
and notification and order are overdue |
The short text describes the object sufficiently |
|
96 |
170 |
and notification is overdue |
The short text describes the object sufficiently |
|
97 |
171 |
and order is overdue |
The short text describes the object sufficiently |
|
98 |
172 |
No maintenance plan is available |
The short text describes the object sufficiently |
|
99 |
173 |
Maintenance plan creation is in process: Job &1 |
The short text describes the object sufficiently |
|
100 |
174 |
Maintenance plan creation job was aborted or the status is unknown |
The short text describes the object sufficiently |
|
101 |
175 |
Maintenance plan creation job finished, but a further job is in process |
The short text describes the object sufficiently |
|
102 |
176 |
Maintenance plan exists, but the job was aborted or the status is unknown |
The short text describes the object sufficiently |
|
103 |
177 |
Maintenance plan does not exist, but a job was planned for it: Job &1 |
The short text describes the object sufficiently |
|
104 |
178 |
You can delete old job data by using the 'Delete Job Data' button |
The short text describes the object sufficiently |
|
105 |
179 |
Maintenance plan update job finished, but a further job is in process |
The short text describes the object sufficiently |
|
106 |
180 |
Maint. plan updated, but the job was aborted or the status is unknown |
The short text describes the object sufficiently |
|
107 |
181 |
Maintenance plan was not updated, but a job was planned for it: Job &1 |
The short text describes the object sufficiently |
|
108 |
182 |
Start date time were not updated, as Maint.Plan was previously started |
The short text describes the object sufficiently |
|