MPD - Message Class for A&D MPD
 The following messages are stored in message class MPD: Message Class for A&D MPD.
It is part of development package AD_MPD in software component IS-AD-MPD. This development package consists of objects that can be grouped under "Maintenance Program Definition".
 It is part of development package AD_MPD in software component IS-AD-MPD. This development package consists of objects that can be grouped under "Maintenance Program Definition".
| Message Nr ▲ | Message Text | 
|---|---|
| 000 | Reporting was stopped by user | 
| 001 | Entry &1 already exists | 
| 002 | Reporting table is empty | 
| 003 | No elements were selected | 
| 004 | Maintenance plan &1 does not exist | 
| 005 | No results were found; see exception log for details | 
| 006 | Select a reporting mode from the drop-down menu | 
| 007 | Task list &1/&2/&3 does not exist | 
| 008 | An error has been found; see log for details | 
| 009 | No reporting results found | 
| 010 | Enter a document number | 
| 011 | Enter a piece of equipment | 
| 012 | Enter a functional location | 
| 013 | Enter a type for the document | 
| 014 | Enter a part for the document | 
| 015 | Enter a version for the document | 
| 016 | The structure has to be loaded before reporting can be run | 
| 017 | No suitable records were found | 
| 018 | Notification type changed; please maintain priority again | 
| 020 | The following data is missing: &1, &2, &3, &4 | 
| 021 | The following errors occurred: | 
| 022 | Batch job was deleted - Job Name: &1, Job Count: &2 | 
| 023 | Date for batch job must be in the future | 
| 024 | Time for batch job must be in the future | 
| 025 | Maintenance plan &1 does not exist. Link will be deleted. | 
| 026 | There are links to maintenance plans that do not exist in the database | 
| 027 | Task list does not belong to the functional location &1 | 
| 028 | Task list does not belong to the equipment &1 | 
| 029 | No cycle data is available | 
| 030 | No maintenance plan data is available | 
| 031 | No document data is available | 
| 032 | No technical object is available | 
| 033 | MPD maintenance plan header data does not exist | 
| 034 | No task list is available for maintenance plan item no. &1 | 
| 035 | Maintenance plan ready to be created | 
| 036 | Maintenance plan already created | 
| 037 | Maintenance plan ready for update | 
| 038 | Maintenance plan ready for creation and update | 
| 039 | Maintenance plan already updated | 
| 040 | No cycle data is available for &1 &2 | 
| 041 | The technical object has no notification status | 
| 042 | No task list is available - maintain the planning and scheduling data | 
| 043 | No document with these parameters exists | 
| 044 | No functional location with this identifier exists | 
| 045 | No piece of equipment with this identifier exists | 
| 046 | Message log is empty | 
| 047 | Document status is not set to 'Released' | 
| 048 | Document has no effectivity data | 
| 049 | Maintain MP header data | 
| 050 | The functional location &1 already has a valid maintenance plan | 
| 051 | The equipment &1 already has a valid maintenance plan | 
| 052 | The status is red for functional location &1 | 
| 053 | The status is red for equipment &1 | 
| 054 | Maintenance plan creation is in process | 
| 055 | Maintenance plan creation is in process &1 | 
| 056 | Old job information was deleted | 
| 057 | Maint plant and work ctr are in different ctrlng areas for item no. &1 | 
| 058 | Maint plant and work ctr have different company codes for item no. &1 | 
| 059 | Planning plant is missing for maint. plan item no. &1 | 
| 060 | No start date and time for maint.plan object &1 | 
| 061 | No maintenance plan item data exists | 
| 064 | Batch job could not be created, please check your input, e.g. start date | 
| 065 | Batch job could not be created | 
| 066 | No start date and start time for maintenance plan &1 | 
| 067 | Maintenance plan &1 has no technical object link in the document | 
| 068 | MPD data is currently locked by user & and can only be displayed | 
| 069 | MPD MP Item data is currently locked by user & | 
| 070 | MPD maintenance plan header data does not exist | 
| 071 | MPD maintenance plan header data is currently locked by user & | 
| 072 | MPD maintenance plan header data is marked for deletion | 
| 073 | MPD cycle data does not exist | 
| 074 | MPD cycle data is currently locked by user & | 
| 075 | MPD cycle data is marked for deletion | 
| 076 | Maintenance plan is marked for deletion | 
| 077 | Maintenance plan is ready to be started | 
| 078 | Maintenance plan not started, but a batch job was planned for it | 
| 079 | Maintenance plan start in process | 
| 080 | Job &1 was successfully planned for the &2 at &3 | 
| 081 | The job log will contain the messages from the planned job | 
| 082 | Maintenance plan start batch job was aborted | 
| 083 | Maintenance plan start batch job status is unknown | 
| 084 | Maintenance plan start batch job was created, but job cannot be found | 
| 085 | Maintenance plan was not started | 
| 086 | Maintenance plan must be started first | 
| 087 | Maintenance plan ready to be restarted | 
| 088 | Maintenance plan has open call objects | 
| 089 | Maintenance plan not restarted, but a batch job was planned for it | 
| 090 | Maintenance plan restart in process | 
| 091 | Maintenance plan restart batch job was aborted | 
| 092 | Maintenance plan restart batch job status is unknown | 
| 093 | Maintenance plan restart batch job was created, but job cannot be found | 
| 094 | Maintenance plan has already been restarted | 
| 095 | Maintenance plan was restarted, but a batch job is in process | 
| 096 | Maintenance plan was restarted, but the batch job was aborted | 
| 097 | Maintenance plan was restarted, but the batch job status is unknown | 
| 098 | Document is not valid for updating maintenance plans | 
| 099 | Maintenance plan is inactive | 
| 100 | Maintenance plan was deleted | 
| 101 | Counter data has been updated successfully | 
| 102 | No measuring point information exists for equipment &1 | 
| 103 | No measuring point information exists for functional location &1 | 
| 104 | Cycle set has not been maintained; enter cycle set data | 
| 105 | Maintenance plan cannot be created | 
| 106 | Maintain all mandatory fields | 
| 107 | Select measuring point for &1 | 
| 108 | No measuring point exists for &1 for &2 &3 | 
| 109 | Maintenance plan cannot be updated | 
| 110 | Maintenance plan does not exist, so therefore cannot be updated | 
| 111 | Click the refresh button for up-to-date data | 
| 112 | Cycle set &1 does not exist; change your entry | 
| 113 | NOTE: Maintenance plan will be created with the active plan & sched data | 
| 114 | Counter data for &1 &2 | 
| 115 | Counter data '&1' has been created for &2 &3 | 
| 116 | Counter data has not been updated | 
| 117 | Counter data will be created after the current plan & sched data is saved | 
| 118 | Counter data cannot be created | 
| 119 | Transaction must be reloaded for the report to have up-to-date data | 
| 120 | Task list search cannot to be opened until a plan.plant has been selected | 
| 121 | Document is not valid to restart maintenance plans | 
| 122 | Counter &1 has no measurement documents | 
| 123 | Counter &1 has no annual estimate | 
| 124 | User &1 is locking document | 
| 125 | User &1 is locking maintance plan | 
| 130 | Data not saved; class &1 does not exist with class type &2 | 
| 131 | Field is empty | 
| 132 | BAdI filter implementation with number &1 does not exist | 
| 133 | BAdI filter implementation &1 does not exist | 
| 134 | Effectivity data has been transferred successfully | 
| 135 | Effectivity data transfer to document &1 &2 &3 &4 on save | 
| 136 | Maintain document class in Customizing first | 
| 137 | Maintain class for technical objects in Customizing first | 
| 138 | There are no characteristics to transfer in this document | 
| 139 | Target document &1 &2 &3 &4 is not MPD-relevant; execution aborted | 
| 140 | Effectivity data is locked; it will not be displayed | 
| 141 | Could not read effectivity data | 
| 142 | Effectivity data is locked; you can only view the data | 
| 143 | Effectivity data is locked; characteristics were not copied | 
| 144 | Could not edit effectivity data; characteristics were not copied | 
| 145 | Char. &1 (class &2 type &3) has multiple values; check your entries | 
| 146 | Effectivity data is locked by user & | 
| 147 | Effectivity data does not exist | 
| 148 | Effectivity data is marked for deletion | 
| 151 | Document data is not available | 
| 152 | No technical object is available | 
| 153 | No planning and scheduling data is available | 
| 154 | Wrong task list type | 
| 155 | Maintenance plan ready to be created | 
| 156 | Maintenance plan already created | 
| 157 | Choose information icon for further information | 
| 158 | Detailed information | 
| 159 | Maintenance plan ready for update | 
| 161 | Maintenance plan already updated | 
| 162 | No counter data is available | 
| 163 | functional location | 
| 164 | equipment | 
| 165 | Neither a notification status nor an order status is available | 
| 166 | Notification status: | 
| 167 | Order status: | 
| 168 | unavailable | 
| 169 | and notification and order are overdue | 
| 170 | and notification is overdue | 
| 171 | and order is overdue | 
| 172 | No maintenance plan is available | 
| 173 | Maintenance plan creation is in process | 
| 174 | Maintenance plan batch job was aborted | 
| 175 | Maintenance plan creation job finished, but a further job is in process | 
| 176 | Maintenance plan exists, but the job was aborted | 
| 177 | Maintenance plan does not exist, but a job was planned for it | 
| 178 | You can delete old job info by using the 'Delete Job Info' button | 
| 179 | Maintenance plan exists, but a batch job is in process | 
| 180 | Maintenance plan updated, but the job was aborted | 
| 181 | Maintenance plan was not updated, but a job was planned it | 
| 182 | Start date/time were not updated as MP had already been started | 
| 183 | Maintenance plan batch job status is unknown | 
| 184 | Maintenance plan creation batch job was created, but job cannot be found | 
| 185 | Maintenance plan exists, but the job status is unknown | 
| 186 | Maint.Plan update batch job finished, but maint.plan was not updated | 
| 187 | Maintenance plan update batch job still in process | 
| 188 | Maintenance plan update batch job was created, but job cannot be found | 
| 189 | Maintenance plan updated, but a batch job is in process | 
| 190 | Maintenance plan updated, but the job status is unknown | 
| 191 | Maintenance plan was started, but a batch job is in process | 
| 192 | Maintenance plan was started, but the batch job was aborted | 
| 193 | Maintenance plan was started, but the batch job status is unknown | 
| 194 | A batch job was already planned for these objects | 
| 195 | Batch job name: &1 | 
| 197 | Maintenance cannot be started because: | 
| 198 | Maintenance plan starting is in process | 
| 199 | Maintenance plan has already been started | 
| 200 | Document is not MPD-relevant | 
| 201 | Document is not the most recent released version | 
| 202 | Only one version of document and cannot be used to update maint. plans | 
| 203 | Technical object has no maintenance plan | 
| 204 | Document: &2 | 
| 205 | MP_CREATE | 
| 206 | MP_UPDATE | 
| 207 | MP_START | 
| 208 | MP_RESTART | 
| 209 | MP_EFFECTIVITY | 
| 220 | Document: | 
| 221 | Equipment: &1 | 
| 222 | Functional Location: &1 | 
| 225 | Status needs to be refreshed | 
| 226 | Do you want to deactivate MPs without affecting their call objects? | 
| 227 | MP call objects will not be affected. Proceed with MP deactivation? | 
| 228 | Main.plan &1 could not be deactivated, object link was not deleted | 
| 230 | Maintain cycle set sequence | 
| 231 | Maintain at least one technical object | 
| 232 | Maintain cycle data and technical objects first | 
| 233 | Cycle with ID &1 could not be assigned to &2 &3. Cycle unit is missing | 
| 235 | Delete batch job(s) | 
| 236 | Are you sure you want to delete the batch job(s)? | 
| 237 | Document has no maintenance plan(s) assigned to it | 
| 239 | You cannot link the current document to itself | 
| 240 | Flag could not be set to mark that maintenance plan &1 was restarted | 
| 241 | Flag could not be set to mark that maintenance plan &1 was updated | 
| 242 | Document is not marked as being relevant to update maintenance plans | 
| 243 | Maintenance plan &1 could not be deactivated | 
| 244 | These technical objects will be linked to the document when you save: | 
| 245 | Document links to the following objects will be deleted: | 
| 246 | Document links to the following objects will be added: | 
| 247 | No authorization | 
| 248 | There are multiple implementations of the BAdI for filter value & | 
| 249 | Direction of locked links will not be changed | 
| 250 | Document key is empty | 
| 251 | Selected document has no suitable object links | 
| 252 | Enter document key (type, number, version and part) first | 
| 253 | No BAdI implementation for this variant | 
| 254 | No row is selected. Please select a row first | 
| 255 | Multiple selection. Dir. will be changed for all suitable records | 
| 256 | No authorization to execute this variant of the data transfer | 
| 257 | You do not have authorization to copy object links | 
| 258 | Internal error; screen enhancement BAdI cannot be executed | 
| 259 | You are not allowed to change data on this tab | 
| 260 | Multiple implementations of the BAdI exists for this variant | 
| 261 | Select data transfer variant first | 
| 262 | Select active or passive direction | 
| 263 | Error during authority check; you cannot copy the object links | 
| 264 | Error during authority check; you are not allowed to change data | 
| 265 | Error during document status check; you will not be able to change data | 
| 266 | Status does not allow you to change certain data | 
| 267 | Value &1 of char. &2 (class &3) changed to &4 | 
| 268 | Could not read effectivity data; data transfer aborted | 
| 269 | Some characteristics were not copied; check Effectivity tab | 
| 270 | Maintain planning plant | 
| 271 | Maintain maintenance item short text | 
| 272 | Maintain work centre and its associated plant | 
| 273 | Plant &1 is not associated with the work centre &2; check your entry | 
| 274 | Work center &1 does not exist; check your entry | 
| 275 | Maintain notification type | 
| 276 | Maintenance plan text is empty (required field) | 
| 277 | Maintenance plan category is empty (required field) | 
| 278 | No task list group &1 exists with type &2 | 
| 279 | Specify both task list type and group | 
| 280 | Line &1; client is unknown | 
| 281 | Line &1; PSD ID is different from the current one | 
| 282 | Line &1; there is no technical object | 
| 283 | Line &1; equipment is not linked to the document | 
| 284 | Line &1; functional location is not linked to the document | 
| 285 | Line &1; cycle ID (counter) is empty | 
| 286 | &1; cycle set sequence is empty | 
| 287 | &1; repeat indicator is empty | 
| 288 | &1; both cycle and offset are empty | 
| 289 | &1; cycle cannot be interpreted as an integer | 
| 290 | &1; offset cannot be interpreted as an integer | 
| 291 | &1; cycle unit is empty | 
| 292 | &1; unknown cycle unit | 
| 293 | &1; counter is not assigned | 
| 294 | &1; cycle must be a multiplication of a day | 
| 295 | &1; offset must be a multiple of a day (24hrs) | 
| 296 | Cycle set sequences are different for cycle ID &1 | 
| 297 | Repeat indicators are different for cycle ID &1 | 
| 298 | Cycles are different for cycle ID &1 | 
| 299 | Cycle units are different for cycle ID &1 | 
| 300 | Cycle descriptions are different for cycle ID &1 | 
| 301 | Inactive indicators are different for cycle ID &1 | 
| 302 | Information on equipment & is missing from cycle ID &1 | 
| 303 | Information on functional location & is missing from cycle ID &1 | 
| 304 | Cycle set seq. &1 &2 &3 contains more than one purely time-based cycle | 
| 305 | No errors were found | 
| 306 | ALL counter assignments are deleted | 
| 307 | MP Item &1; there are no cycles with cycle set indicator &2 | 
| 308 | Error on Cycle tab; cycles will not be saved in this form | 
| 309 | Effectivity data is locked; data transfer aborted | 
| 310 | Cycle data is locked; data transfer aborted | 
| 311 | Error reading cycle data; data transfer aborted | 
| 312 | Cycle data is inconsistent; see log for details | 
| 313 | At least one error occurred during data check (see log); transfer aborted | 
| 314 | Error on MP items grid; MP items will not be saved | 
| 315 | None of the dates for the MP, notif. or order are in defined range | 
| 316 | Maintenance plan &1 | 
| 317 | &1 &2 &3 &3 is not the key of the current document | 
| 318 | All possible counter assignments are already done | 
| 319 | New object link for type &3 has incomplete keys | 
| 320 | Error creating item data | 
| 321 | Item data could not be changed | 
| 322 | The item you want to change does not exist in the database | 
| 323 | Item is locked; cannot change item | 
| 324 | Item is locked; cannot delete item | 
| 325 | Cannot delete item | 
| 326 | Could not read cycle data; please check the Cycle Data tab | 
| 327 | Document &1 &2 &3 &4 already exists; link will be deleted | 
| 328 | There are no cycles with cycle set indicator &1 | 
| 329 | Effectivity data &1 &2 &3 &4 could not be created | 
| 330 | Effectivity data matches and object is linked to document | 
| 331 | Effectivity data matches and object can be linked to document | 
| 332 | Effectivity does not match and object should be unlinked from document | 
| 333 | No technical objects found for these characteristics values | 
| 334 | No technical objects matching certain DIR effectivity could be found | 
| 335 | Class type &1; class &2 | 
| 336 | To search for technical objects there must be a DIR with effect.data | 
| 337 | None of the dates for the MP &1 are in defined range | 
| 340 | Document has no MPD MP header and item data; links will be deleted | 
| 341 | Error reading MPD MP header and item data; links will be deleted | 
| 342 | Error reading MPD MP item data; data will not be copied | 
| 343 | Error reading cycle data; data will not be copied | 
| 344 | Error reading effectivity data; data will not be copied | 
| 350 | The record is in the database, but the fields do not correspond | 
| 353 | This document is being used by a MPD batch job and should not be changed | 
| 354 | Compliance date is after default start date | 
| 355 | Start date &1 assigned to equipment &2 is after compliance date | 
| 360 | Errors in the MPD MP header structure | 
| 361 | Errors in MPD MP item | 
| 362 | Errors in cycle data | 
| 363 | Errors in effectivity data | 
| 364 | Errors in the object links table | 
| 365 | No start date maintained for equipment &1 | 
| 366 | No start date maintained for functional location &1 | 
| 370 | Maintain document type | 
| 371 | Maintain document number | 
| 372 | Maintain document part | 
| 373 | Maintain document version | 
| 380 | System error when trying to lock target document. | 
| 381 | Target docuement is locked by user &1. Data transfer aborted | 
| 400 | Missing implementation for BAdI &. | 
| 401 | There is no implementation for BAdI &1 with filter value &2. | 
| 500 | No MP header data available in document &1 &2 &3 &4 | 
| 501 | MP header data in document &1 &2 &3 &4 is marked for deletion | 
| 502 | MP header data in document &1 is currently locked by user &2 | 
| 503 | No MP cycle data available in document &1 &2 &3 &4 | 
| 504 | MP cycle data in document &1 &2 &3 &4 is marked for deletion | 
| 505 | MP cycle data in document &1 is currently locked by user &3 | 
| 506 | No MP item data is available in document &1 &2 &3 &4 | 
| 507 | MP item data in document &1 is currently locked by user &2 | 
| 508 | Both of equipment and functional location are filled | 
| 509 | Searching for MPD documents: | 
| 510 | Equipment &1, document &2: | 
| 511 | Functional location &1, document &2: | 
| 512 | Link exists to document &1, but doc is not MPD relevant | 
| 513 | |
| 514 | Document &1 is not the most recent released version | 
| 515 | |
| 516 | Document &1 status is not set to 'Released' | 
| 517 | |
| 518 | Document &1: data matches, or link already exists | 
| 519 | No relevant document found | 
| 520 | Cannot get measurement points of equipment &1 | 
| 521 | Error reading cycle data for PSGUID &1 | 
| 522 | Cycle ID &1 could not be assigned to equi &2. Cycle unit is missing | 
| 523 | Equipment &1 has multiple cycles with unit &2 | 
| 524 | No measuring point exists for &1 for equipment &2 | 
| 525 | No measuring point exists for &1 for functional location &2 | 
| 526 | Equipment &1 has multiple cycles with unit &2 | 
| 527 | Functional location &1 has multiple cycles with unit &2 | 
| 528 | Cycle ID &1: cycle unit is missing | 
| 529 | Equipment &1: | 
| 530 | Functional location &1: | 
| 531 | Maintenance plan &1 exists for technical object | 
| 601 | Screen layout has been changed |