SAP ABAP Message Class MPLAN (Messages for Maintenance Plan API)
Basic Data
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷ PM-PRM-MP (Application Component) Maintenance Plans
⤷ MPLAN_API (Package) Maintenance Plan API
⤷ PM-PRM-MP (Application Component) Maintenance Plans
⤷ MPLAN_API (Package) Maintenance Plan API
Attributes
Message class | MPLAN | |
Short Description | Messages for Maintenance Plan API | |
Changed On | 20130531 | |
Last Changed At | 101218 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 001 | Unknown error | The short text describes the object sufficiently | |
2 | 002 | The log could not be initialized | The short text describes the object sufficiently | |
3 | 003 | Save canceled by customer enhancement | The short text describes the object sufficiently | |
4 | 004 | Use date format YYYYMMDD for parameter & | The short text describes the object sufficiently | |
5 | 005 | Use time format HHMMSS for parameter & | The short text describes the object sufficiently | |
6 | 006 | Only use numbers for parameter & | The short text describes the object sufficiently | |
7 | 007 | Only use values I or E (not &2) for selection option &1 | The short text describes the object sufficiently | |
8 | 008 | Selection option &1: &2 cannot be interpreted | The short text describes the object sufficiently | |
9 | 009 | Enter at least one selection criteria | The short text describes the object sufficiently | |
10 | 010 | Cannot import memory ID & | The short text describes the object sufficiently | |
11 | 011 | Nothing was selected | The short text describes the object sufficiently | |
12 | 012 | & maintenance plans were selected | The short text describes the object sufficiently | |
13 | 013 | Enter a maintenance plan number | The short text describes the object sufficiently | |
14 | 014 | & maintenance items were selected | The short text describes the object sufficiently | |
15 | 015 | Maintenance item &1 does not exist in maintenance plan template &2 | The short text describes the object sufficiently | |
16 | 016 | Activity & not defined | The short text describes the object sufficiently | |
17 | 017 | Maintenance cycle &1 does not exist in maintenance plan template &2 | The short text describes the object sufficiently | |
18 | 018 | Specify an item number | The short text describes the object sufficiently | |
19 | 019 | Activity & not allowed | The short text describes the object sufficiently | |
20 | 020 | Cannot convert "&!" into a number | The short text describes the object sufficiently | |
21 | 021 | General parameter error: & & & & | The short text describes the object sufficiently | |
22 | 022 | The following messages concern maintenance plan & | The short text describes the object sufficiently | |
23 | 023 | The following messages concern maintenance item & | The short text describes the object sufficiently | |
24 | 024 | No value for field &1 -> the value &2 was inserted | The short text describes the object sufficiently | |
25 | 025 | Field & contains administrative data and is filled automatically | The short text describes the object sufficiently | |
26 | 026 | Field & cannot be filled -> value reset | The short text describes the object sufficiently | |
27 | 027 | Data was not checked before update | The short text describes the object sufficiently | |
28 | 028 | Long texts without a key are ignored | The short text describes the object sufficiently | |
29 | 029 | Long texts for item & cannot be assigned | The short text describes the object sufficiently | |
30 | 030 | Field &1 for reference object view: &2 not possible -> value reset | The short text describes the object sufficiently | |
31 | 031 | Stability studies are not supported | The short text describes the object sufficiently | |
32 | 032 | Entry possible in only one of the following fields: & & & | The short text describes the object sufficiently | |
33 | 033 | Maintenance plan and maintenance item require the same plan category | The short text describes the object sufficiently | |
34 | 034 | Authorization group &1 does not exist | The short text describes the object sufficiently | |
35 | 100 | The maintenance plan category cannot be changed | The short text describes the object sufficiently | |
36 | 101 | Multiple counter plan does not allow a strategy (overwrite value) | The short text describes the object sufficiently | |
37 | 102 | Cannot change from: & to: & is not possible | The short text describes the object sufficiently | |
38 | 103 | User name & is not valid (maintenance plan header) | The short text describes the object sufficiently | |
39 | 104 | "Last changed By" not allowed for newly created maintenance plan | The short text describes the object sufficiently | |
40 | 105 | Creator (user name) of a maintenance plan cannot be changed | The short text describes the object sufficiently | |
41 | 106 | User name & for last changer of maintenance plan header is invalid | The short text describes the object sufficiently | |
42 | 107 | Maintenance plan number changed from &1 to &2 | The short text describes the object sufficiently | |
43 | 108 | Cannot change the maintenance strategy of the maintenance plan | The short text describes the object sufficiently | |
44 | 109 | Maintenance strategy & sets a value for the parameter & | The short text describes the object sufficiently | |
45 | 110 | Specify maintenance plan header text | The short text describes the object sufficiently | |
46 | 111 | Specify maintenance plan category | The short text describes the object sufficiently | |
47 | 112 | The maintenance plan category cannot be changed | The short text describes the object sufficiently | |
48 | 113 | Reverse deactivation for maintenance plan & | The short text describes the object sufficiently | |
49 | 114 | Deletion flag for maintenance plan & reset | The short text describes the object sufficiently | |
50 | 115 | Administrative maintenance plan parameter & -> entry not considered | The short text describes the object sufficiently | |
51 | 116 | Scheduling type: & does not match maintenance strategy: & | The short text describes the object sufficiently | |
52 | 117 | Field &1 of maintenance plan &2 cannot be changed -> value reset | The short text describes the object sufficiently | |
53 | 118 | Maintenance plan & is already inactive | The short text describes the object sufficiently | |
54 | 119 | Maintenance plan & is already active | The short text describes the object sufficiently | |
55 | 201 | Functional location &1 does not correspond with equipment &2 | The short text describes the object sufficiently | |
56 | 202 | Cannot read ILOA data &1 | The short text describes the object sufficiently | |
57 | 203 | Maintenance plan must have at least one maintenance item | The short text describes the object sufficiently | |
58 | 204 | Maintenance item & was transferred more than once | The short text describes the object sufficiently | |
59 | 205 | Value of maintenance plan item for maintenance item set from & to & | Space: object requires documentation | |
60 | 206 | Maintenance plan cetagory & sets a value for parameter & | The short text describes the object sufficiently | |
61 | 207 | Maintenance strategy & transferred to maintenance item | The short text describes the object sufficiently | |
62 | 208 | Task list factor is 0 | Space: object requires documentation | |
63 | 209 | User name & is not valid (maintenance plan item) | The short text describes the object sufficiently | |
64 | 210 | "Last Changed By" is not allowed for newly created maintenance item | The short text describes the object sufficiently | |
65 | 211 | You are not allowed to change the creator (user name) of a maint. item | The short text describes the object sufficiently | |
66 | 212 | User name & for last changer of maintenance item is invalid | The short text describes the object sufficiently | |
67 | 213 | Cannot delete new maintenance plans created by Wpos | The short text describes the object sufficiently | |
68 | 214 | Obligatory parameter & of maintenance item is not filled | The short text describes the object sufficiently | |
69 | 215 | Maintenance planning plant for the maintenance item is invalid | The short text describes the object sufficiently | |
70 | 216 | No autorization for transaction code: & category: & field: & | The short text describes the object sufficiently | |
71 | 217 | Creation of settlement rule not supported | The short text describes the object sufficiently | |
72 | 218 | Maintenance activity type & is not valid | The short text describes the object sufficiently | |
73 | 219 | Business area transferred from maintenance object | The short text describes the object sufficiently | |
74 | 220 | Cannot read table 399J | The short text describes the object sufficiently | |
75 | 221 | Change of order type in maintenance item & | The short text describes the object sufficiently | |
76 | 222 | Error when reading the equipment & | The short text describes the object sufficiently | |
77 | 223 | Error when reading functional location & | The short text describes the object sufficiently | |
78 | 224 | Error when determining controlling area & | The short text describes the object sufficiently | |
79 | 225 | Error when determining customer order: & item: & | The short text describes the object sufficiently | |
80 | 226 | Maintenance item & cannot be created again since it already exists | The short text describes the object sufficiently | |
81 | 227 | Error when reading the maintenance planning plant & | The short text describes the object sufficiently | |
82 | 228 | Error when reading notification type & | The short text describes the object sufficiently | |
83 | 229 | Error when checking physical sample & | The short text describes the object sufficiently | |
84 | 230 | Error when checking inspection plan parameters PLNTY: & PLNNR: & PLNAL: & | The short text describes the object sufficiently | |
85 | 231 | Error during authorization check for equipment / functional location | The short text describes the object sufficiently | |
86 | 232 | Existing data for maintenance item & is not available | The short text describes the object sufficiently | |
87 | 233 | Cannot process maintenance item without maintenance plan reference | The short text describes the object sufficiently | |
88 | 234 | Maintenance item was assigned to the maintenance plan | The short text describes the object sufficiently | |
89 | 235 | Invalid activity & -> maintenance item is ignored | The short text describes the object sufficiently | |
90 | 236 | Activity invalid for maintenance item -> Activity changed to create | The short text describes the object sufficiently | |
91 | 237 | Assignment of maintenance item to maintenance plan removed | The short text describes the object sufficiently | |
92 | 238 | Stability study only possible in connection with task list category Q | The short text describes the object sufficiently | |
93 | 239 | Material number or serial number is missing! | The short text describes the object sufficiently | |
94 | 240 | View of reference object & is not available | The short text describes the object sufficiently | |
95 | 241 | View of reference object & is not valid for maintenance items | The short text describes the object sufficiently | |
96 | 242 | Reference object for parameter(s) & & is not available | The short text describes the object sufficiently | |
97 | 243 | Value of parameter & is not permitted. Value & was inserted | The short text describes the object sufficiently | |
98 | 244 | No / invalid parameter value for stability study inspection type | The short text describes the object sufficiently | |
99 | 245 | System condition & not available -> value reset | The short text describes the object sufficiently | |
100 | 246 | Maintenance play category Service Procurement is not supported | The short text describes the object sufficiently | |
101 | 247 | Material number & is invalid -> value reset | The short text describes the object sufficiently | |
102 | 248 | Serial number & for material & is invalid -> both values reset | The short text describes the object sufficiently | |
103 | 249 | Item & is not assigned to a maintenance plan | The short text describes the object sufficiently | |
104 | 250 | Error when reading the work center: & | The short text describes the object sufficiently | |
105 | 251 | Selection by field name & is not supported for the maintenance item | The short text describes the object sufficiently | |
106 | 252 | For selection of the maint. plan category, MPTYP was replaced by MITYP | The short text describes the object sufficiently | |
107 | 300 | More than one maintenance cycle was transferred with the same number | The short text describes the object sufficiently | |
108 | 301 | Maintenance plan &1 was already scheduled. Dimension change not possible | The short text describes the object sufficiently | |
109 | 302 | Activity invalid for maintenance cycle -> activity changed to create | The short text describes the object sufficiently | |
110 | 303 | Error during dimension comparison counter & and maintenance cycle unit & | The short text describes the object sufficiently | |
111 | 304 | Cycle & is not time-dependent and needs at least one counter | Space: object requires documentation | |
112 | 305 | Counter plans that are not multiple can only contain max. one cycle | The short text describes the object sufficiently | |
113 | 306 | Maintenance plan must contain at least one cycle | The short text describes the object sufficiently | |
114 | 307 | Maintenance plan does not contain a unit for cycle & | The short text describes the object sufficiently | |
115 | 308 | Activity scheduling does not permit time-dependent counters (&1) | The short text describes the object sufficiently | |
116 | 309 | Cycle length of cycle & must be a multiple of one day | The short text describes the object sufficiently | |
117 | 310 | Offset length for cycle & must be a multiple of one day | The short text describes the object sufficiently | |
118 | 311 | Cycle & does not have a cycle or a offset | The short text describes the object sufficiently | |
119 | 312 | Cycle & is already scheduled. Changed plan date is ignored | The short text describes the object sufficiently | |
120 | 313 | Cycle & is already scheduled. Changed planned counter reading is ignored | The short text describes the object sufficiently | |
121 | 314 | Cycle & is not available. Cannot change/delete | The short text describes the object sufficiently | |
122 | 315 | Action & that is to be carried out for cycle & is not valid / recognized | The short text describes the object sufficiently | |
123 | 316 | Maintenance cycle & is already scheduled | The short text describes the object sufficiently | |
124 | 317 | Maintenance plan sorting & is not available | The short text describes the object sufficiently | |
125 | 318 | Error when reading the counter: & | The short text describes the object sufficiently | |
126 | 319 | Counter reading for counter & cannot be negative! | The short text describes the object sufficiently | |
127 | 320 | Check not possible: maintenance plan does not have key date schedule | The short text describes the object sufficiently | |
128 | 321 | Cycle set sequence of cycle & cannot be changed | The short text describes the object sufficiently | |
129 | 322 | Invalid maintenance cycle activity & -> cycle & is ignored | The short text describes the object sufficiently | |
130 | 323 | Maintenance cycle & does not have a counter | The short text describes the object sufficiently | |
131 | 324 | Time dimension of maintenance plan must be bigger than/equal to day | The short text describes the object sufficiently | |
132 | 325 | Entered factory calendar was ignored | The short text describes the object sufficiently | |
133 | 326 | Maintenance plan contains cycle with the number 00 | The short text describes the object sufficiently | |
134 | 327 | Maintenance plan does not contain a counter or a counter unit | The short text describes the object sufficiently | |
135 | 328 | Maintenance cycle & does not contain a counter or a counter unit | The short text describes the object sufficiently | |
136 | 329 | There are is no maintenance cycle data -> cannot change | The short text describes the object sufficiently | |
137 | 330 | Counter for maint. cycle & changed. Start counter reading not changed. | The short text describes the object sufficiently | |
138 | 331 | Varying recurrence rates for cycles in cycle set & | The short text describes the object sufficiently | |
139 | 332 | Specify a cycle number | The short text describes the object sufficiently | |
140 | 333 | A strategy plan cannot contain more than one cycle | The short text describes the object sufficiently | |
141 | 334 | Cannot delete strategy plan cycles | The short text describes the object sufficiently | |
142 | 335 | Time-based strategy plan does not allow maintenance cycles | The short text describes the object sufficiently | |
143 | 336 | Cycle for counter-based strategy plan requires a counter | The short text describes the object sufficiently | |
144 | 401 | Tests started | The short text describes the object sufficiently | |
145 | 402 | Single test | The short text describes the object sufficiently | |
146 | 403 | Mass test | The short text describes the object sufficiently | |
147 | 404 | Runtime &1 | The short text describes the object sufficiently | |
148 | 405 | Maintenance plan &1 not selected during mass selection | The short text describes the object sufficiently | |
149 | 406 | Number of entries is different: &1, &2 | The short text describes the object sufficiently | |
150 | 407 | Consistency checks | The short text describes the object sufficiently | |
151 | 408 | Difference in &1 (&2)(&3) | The short text describes the object sufficiently | |
152 | 409 | Internal error: DDIC structure & not found. | The short text describes the object sufficiently | |
153 | 410 | Check &1 | The short text describes the object sufficiently | |
154 | 411 | &1 &2 not selected during mass selection | The short text describes the object sufficiently | |
155 | 412 | Check maintence plan &1 | The short text describes the object sufficiently | |
156 | 413 | &1 &2 not selected when reading item | The short text describes the object sufficiently | |
157 | 414 | &1 &2 &3 &4 | The short text describes the object sufficiently | |
158 | 415 | Position &1 does not have any ILOA data | The short text describes the object sufficiently | |
159 | 501 | Maintenance plan &1: function &2 not executable - still without calls | The short text describes the object sufficiently | |
160 | 502 | Maintenance plan &1: enter cycle start for counter reading | The short text describes the object sufficiently | |
161 | 503 | Maintenance plan &1: inconsistency - call without history | The short text describes the object sufficiently | |
162 | 504 | Maintenance plan &1: only the following functions are allowed: &2 | The short text describes the object sufficiently | |
163 | 505 | No entry found in table MMPT for cycle set seq. &1 and rep. factor &2 | The short text describes the object sufficiently | |
164 | 506 | Setting &1 to &2 | The short text describes the object sufficiently | |
165 | 507 | Enter a call number | The short text describes the object sufficiently | |
166 | 508 | Specified call number &1 does not exist in maintenance plan &2 | The short text describes the object sufficiently | |
167 | 509 | Enter package counter: maintenance plan &1 | The short text describes the object sufficiently | |
168 | 510 | No entry for package &1 and strategy &2 found in T351X | The short text describes the object sufficiently | |
169 | 511 | Scheduling could not be executed: maintenance plan &1 | The short text describes the object sufficiently | |
170 | 512 | Maintenance plan &1: method &2 not executable - multiple counter plan | The short text describes the object sufficiently | |
171 | 513 | Maintenance plan &1 does not have a call number &2 | The short text describes the object sufficiently | |
172 | 514 | No entry in &1 found for &2 | The short text describes the object sufficiently | |
173 | 515 | Performance-based plans and multiple counter plans cannot be fixed | The short text describes the object sufficiently | |
174 | 516 | Enter the next planned date | The short text describes the object sufficiently | |
175 | 517 | Start of scheduling for maintenance plan &1 function &2 | The short text describes the object sufficiently | |
176 | 518 | Call number &1 is already skipped | The short text describes the object sufficiently | |
177 | 519 | Unit of measurement &1 not in table MMPT | The short text describes the object sufficiently | |
178 | 520 | Maintenance plan &1 - method &2 not executable - single cycle plan | The short text describes the object sufficiently | |
179 | 521 | Inconsistency - there are gaps in the sequence of call numbers | The short text describes the object sufficiently | |
180 | 522 | Maintenance plan &1 is time dependent; do not enter counter readings | The short text describes the object sufficiently | |
181 | 523 | See transaction IP03 for significance of both fields | The short text describes the object sufficiently | |
182 | 524 | Maintenance plan &1 call number &2 released | The short text describes the object sufficiently | |
183 | 525 | Maintenance plan &1 call number &2 fixed | The short text describes the object sufficiently | |
184 | 526 | Maintenance plan &1 call number &2 skipped | The short text describes the object sufficiently | |
185 | 527 | Maintenance plan &1 manual call number &2 added | The short text describes the object sufficiently | |
186 | 528 | Maintenance plan &2 call number &2 completed | The short text describes the object sufficiently | |
187 | 529 | Error when reading text for field &1 &2 | The short text describes the object sufficiently | |
188 | 530 | Counter reading entry not relevant for this maintenance plan category &1 | The short text describes the object sufficiently | |
189 | 531 | Time/date entry not relevant for this maintenance plan category &1 | The short text describes the object sufficiently | |
190 | 532 | Only the following fields are read for maintenance plan category &1: | The short text describes the object sufficiently | |
191 | 533 | &1 | The short text describes the object sufficiently | |
192 | 534 | Entries in other fields will be ignored | The short text describes the object sufficiently | |
193 | 550 | The fields of the call horizon (&1, &2, &3) are inconsistent | Space: object requires documentation | |
194 | 551 | Field &1 is not supported | Space: object requires documentation | |
195 | 552 | The multiple counter plan does not support a call horizon in days | The short text describes the object sufficiently | |
196 | 553 | You cannot deactivate business function LOG_EAM_CI_6 | Space: object requires documentation | |
197 | 554 | A function of this BF is restricted in a distributed system landscape | Space: object requires documentation | |
198 | 555 | Define the call horizon in percent | The short text describes the object sufficiently |
History
Last changed on/by | 20130531 | SAP | |
SAP Release Created in | 700 |