/SAPAPO/OM_ERROR - Messages for /SAPAPO/OM_MESSAGES_LC_STORE
The following messages are stored in message class /SAPAPO/OM_ERROR: Messages for /SAPAPO/OM_MESSAGES_LC_STORE.
It is part of development package /SAPAPO/OM_TRANSLATION in software component BC-DB-LCA. This development package consists of objects that can be grouped under "LCAPPS Objects to Be Translated into All Languages".
It is part of development package /SAPAPO/OM_TRANSLATION in software component BC-DB-LCA. This development package consists of objects that can be grouped under "LCAPPS Objects to Be Translated into All Languages".
Message Nr ▲ | Message Text |
---|---|
000 | Operation performed successfully |
001 | Error &1 (&2) no longer used in Release 5.0 |
003 | Object changed since the last access |
006 | Key already exists |
010 | Only use constants from /sapapo/constants_om |
011 | Invalid time stamp |
012 | Invalid quantity at an I/O node (= 0) |
015 | Inconsistent times within an activity |
016 | Structural errors in a characteristics container |
018 | Invalid constraint type |
019 | Invalid constraint relation type (incorrect relationship) |
021 | Only use constants from /sapapo/constants ("Activity status") |
022 | Invalid value for scheduling parameter ORDER_INT_REL or ORDER_EXT_REL |
023 | Invalid value for scheduling parameter PEGGING_REL_HARD or _SOFT |
025 | Input list for the pegging area to be deleted is not empty |
026 | Output list for the pegging area to be deleted is not empty |
027 | Invalid GUID entered as key |
029 | Incorrect activity-constraint connection |
030 | Resource is not empty |
031 | Invalid date or time |
032 | Different setup keys within an operation |
033 | An operation has more than one setup activity |
034 | Incorrect methods |
042 | Invalid capacity requirement |
043 | Activity not valid |
044 | Invalid value for field CONSTR_SELECTION |
046 | Invalid value for field PEG_SELECTION |
051 | Incorrect resource type |
053 | Sub-transaction error in live cache |
054 | Order key already exists in live cache |
057 | Activity already exists in liveCache |
064 | Incorrect value for "PLANNINGMODE" scheduling parameter |
069 | Maximum nesting depth for suborders exceeded |
070 | Invalid GUID for parent_order |
071 | (Sub)order has both activities and suborders |
074 | Invalid constraint mode type |
076 | Order and suborder have different order types |
077 | Order and suborder have disjointed periods of validity |
079 | Doubled input/output nodes |
085 | No data exists for GUID |
086 | Cover not possible |
088 | An attempt was made to cover for a bucket resource |
089 | Invalid alert ID |
090 | Invalid alert object |
093 | Non-unique ATP delta anchor |
094 | No capacity demands for specified mode |
096 | Invalid value for ATP_UPDATE_MODE field |
097 | Invalid value for field IS_ATP_INFO_DELTA_MODE |
101 | Propagation range already exists |
102 | Invalid propagation range for deletion or changing |
106 | Invalid mode number ( <=0) |
107 | An activity has modes that can only be selected manually |
109 | Stock order has invalid order type |
110 | A mode covers one resource a number of times |
111 | A mode has no resource |
113 | A mode has no time stream resource |
115 | Negative value for MAX_SHORT_BREAK field |
116 | Negative processing time |
118 | Invalid pegging area |
120 | Invalid stock type |
121 | Invalid or incorrect sublocation when creating a stock |
122 | Invalid or incorrect version when creating a stock |
123 | Invalid or incorrect category when creating a stock |
127 | Invalid times |
129 | Stock cannot be created using module /sapapo/om_order_change |
131 | Value for "Maximum length of backwards pegging relationship" (<0) |
132 | Value for "Alerts from length of backward pegging relationship" (<0) |
133 | Invalid value for "Maximum length of forwards pegging relationship" (<=0) |
134 | Invalid value for characteristics type |
137 | Characteristics container does not contain class ID |
139 | Incorrect value for occur count in the characteristics table |
140 | Maximum permitted size for long characteristics was exceeded |
141 | Several entries with same indicator but different types |
142 | Incorrect value for block counter for long characteristics |
143 | A characteristics indicator is contained several times in char. container |
146 | Invalid mode for scheduling at activity |
147 | Invalid time entry for scheduler at activity |
148 | Cover flag was assigned for a secondary resource |
149 | A setup activity may not cover a secondary resource |
153 | Invalid characteristics container |
154 | A characteristics container with this GUID already exists in liveCache |
155 | Characteristics container is still being used |
156 | No data was entered for creating the characteristics container |
157 | Incompatible container data |
159 | Attempt was made to create two modes with the same number for a segment |
163 | Resource has no time stream |
164 | Read routine has no input data |
165 | Two entries in the list have the same number |
166 | An invalid mode priority was specified for a mode |
167 | Sequence-dependent setup activities not allowed in SNP orders |
168 | Invalid planning type |
169 | Invalid constraint subtype |
170 | Invalid ApoActPlanStateSel value |
171 | Invalid ApoPlanningTypeSel Value |
173 | Invalid LineProcTimeMode value (for line resources) |
174 | Invalid BucketDimension value for bucketed resources |
176 | Negative time data for this attribute |
177 | Invalid remaining shelf life < 0 for pegging area |
178 | Invalid min_tolerance for pegging area |
179 | Invalid max_tolerance for pegging area |
182 | Several scheduler parameter structures with the same priority |
183 | This activity is not part of an order to be scheduled |
184 | Follow-up error |
185 | Invalid ApoSchedMaxConstr value |
187 | Invalid ApoSchedEffectivityMode value |
189 | Invalid ApoIoNodeSel value |
193 | Mode of an SNP activity covers a resource that cannot be bucket planned |
194 | Mode of non-SNP activity covers a resource that cannot be bucket planned |
195 | An isolated constraint was found |
196 | This resource may not be used as a secondary resource |
197 | SNP activities require complete scheduler specifications |
198 | Negative processing time not allowed for scheduling |
199 | Confirmations may not be made to SNP activities |
200 | Function not yet implemented |
201 | Resource still being used in another mode |
202 | Invalid date vector |
206 | No ORDKEY entry exists for this order |
207 | Invalid value for OM_SCHED_RES_SUB_MODE1 |
208 | Invalid value for OM_SCHED_COMPACT_MODE |
209 | Planning version not allowed |
211 | ORDMAP accesses are only allowed in the active planning version |
212 | A table entry could not be found |
213 | There is already a table entry with this key |
214 | A table entry could not be locked |
215 | A table entry already exists with this secondary key |
216 | Creation of pegging areas not allowed in this planning version |
218 | Invalid value entered for the pegging strategy |
222 | Deletion of planning version failed |
223 | Stock order key does not describe a top order |
224 | Invalid value for position of order in production campaign |
225 | There is already an order in the first position of the campaign |
226 | There is already an order in the last position on the campaign |
227 | Campaigns may not contain suborders |
228 | Invalid value for OM_SCHED_RES_BLK_MODE |
229 | Invalid multilevel ATP log container |
230 | Invalid max_arc_alert_length value <= 0 |
231 | Value for max_arc_length is smaller than for max_arc_alert_length |
232 | Different ATP matrix GUIDs were given for an object |
233 | Invalid value given for om_conti_io_scheduling |
234 | Invalid value given for ApoIoOffsetRelType |
235 | Relative offsets for I/O nodes for sequence-dependent setup are forbidden |
236 | Continuous I/O nodes not allowed for sequence-dependent setup activities |
237 | Invalid value for OM_PEG_TYPE |
238 | An edge of this type already exists between the two I/O nodes |
239 | An edge of this type does not exist between the two I/O nodes |
240 | Simulations not allowed when using scheduling agreements |
241 | Invalid value for OM_HAS_CHARACTS |
242 | Inconsistent times for a constraint |
243 | Invalid value for OM_SYNC_CONTROL |
244 | Campaigns are not allowed for SNP orders |
245 | Invalid value for OM_SCHED_ACT_MODE |
246 | Storage nodes not allowed for phantom activities |
247 | Invalid value for the object type of a storage node |
248 | Invalid value for MATCO |
249 | Inconsistent storage node data |
252 | Invalid value for OM_SCHED_ORDER_MODE |
253 | Setup activity has at least one mode that does not cover |
256 | Termination (serious error) |
257 | Invalid effectivity mode |
258 | Invalid I/O node configuration |
259 | No resources and no pegging areas for propagation area |
260 | Incorrect byte alignment in the structure |
263 | Missing mode at storage nodes |
264 | Invalid value for ApoCapacitiyView |
265 | Resource used in a storage mode |
267 | Invalid value for ORDER_CONFIRMATION_STATUS |
269 | Invalid value for ApoMixResFiniteSchedType or MixResFiniteSchedType |
270 | Invalid value for ApoMixResType or MixResType |
272 | An ATP component status was specified for an output node |
273 | Incorrect change |
274 | Incorrect change |
275 | Error when calling OM_PEGID_GET_IO |
276 | Unknown ApoMixResPlanMode specified |
277 | The order given is not a stock order |
278 | A mode for a storage node possesses more than one mode item |
279 | A pegging node may have a maximum of one storage node as reference |
280 | Resource quantity must have same sign as pegging quantity |
282 | A ParentPos was given for an output node |
283 | Pegging node is relevant to iPPE and refers to an s-node |
284 | A negative storage amount was given for a storage node |
285 | Invalid conversion factor for storage quantity |
288 | Pegging area already marked for deletion |
289 | Calendar resource cannot yet be used |
290 | Invalid /SAPAPO/OM_GET_PRIM_RES value |
291 | Invalid change |
293 | Unscheudling of an order incorrect or not possible |
294 | Infringes against constraint |
295 | Invalid value for NOBREAKS field in /SAPAPO/OM_SCHED_PARAM |
297 | The resource specified is not a bucket resource |
298 | Incorrect test parameter number (COM tests) |
299 | Incorrect pegging area |
300 | This function is not implemented in this release |
301 | Invalid value for SEND_GUIDS_ONLY |
302 | Invalid value for ADD_TOPORDERS |
303 | Successor activity is a dummy activity |
305 | /SAPAPO/OM_OBJECTS_GET_ALL does not currently support this object type |
307 | Additional option not considered by COM routine PEGID_SELECT_ORDERS |
308 | Invalid value for ApoGsParFaultTolerance |
309 | Invalid value for ApoGsParUseArgMode |
310 | Invalid value for ApoGsArgTimeMode |
311 | INC_FLAG may only be entered for input nodes |
312 | Changes not adopted due to different change statuses |
313 | Invalid parameter in pegging area |
318 | Field overflow when aggregating the available capacity in the time stream |
319 | Field overflow when aggregating the capacity consumption of the resource |
320 | Field overflow when aggregating initial capacity consumption of resource |
321 | Incompatible activities for mode linkage of a constraint |
323 | Sequence-dependent setup activities reserve pure bucket resources |
325 | Pegging area to be created has time stream |
326 | ORDKEY or ORDMAP entries are only allowed to be created for top orders |
327 | The activity key specified does not agree with the I/O node given |
328 | Invalid field value for OM_SFW_NET_CTRL_EDGE |
329 | Invalid field value for OM_SFW_RES_MODE |
330 | Bucket vector header specified for non-bucket resource |
331 | Finiteness level unequal in bucket vector header and resource |
332 | Invalid field value for OM_TIMELINE_MODE |
333 | Invalid ApoTimelineMode |
334 | An RPM order is not allowed to have suborders |
335 | Incorrect parameters for scheduling framework (SFW) at GET_NEXT_SET |
336 | Incorrect input(output node type) (OM_IONODE_TYPE) |
337 | Dummy pegging area not allowed for this node type |
338 | Incorrect input/output node type for output nodes |
339 | Unexpected initial GUID in ABAP Table |
340 | Characteristic tables do not correspond to change method |
341 | Invalid max_break_plan_mode |
343 | Confirmation status requested would violate confirmation consistency |
344 | Activity with FIXED_TIMES = 'B' only with valid time entry |
345 | SNP bucket resource expected |
346 | You cannot use this pegging type for ATP |
347 | Indicator "like_avo_intern" set for external constraints |
348 | Offset not allowed for input/output nodes of SNP activities |
349 | Continuous input/output nodes not allowed for SNP activities |
350 | Continuous input/output nodes not allowed for WFM resources |
351 | WFM resources must be used for all modes of an activity |
352 | Input/output node must not be deleted |
353 | Invalid value for USE_CURRENT_MODES (retain active modes) |
354 | ATP characteristic is not allowed |
355 | Characteristic of type "special" must have a corresponding charac. ID |
356 | Invalid time stream efficiency |
357 | Invalid method, how the offsets of the I/O nodes are scheduled |
358 | Invalid selection for /sapapo/om_snp_capa_get |
359 | Inventory anchor table required but not specified |
360 | Invalid characteristic operator |
361 | Sequence-dependent setup activities on continual resource only |
362 | Invalid change made to pegging area of an input/output node |
363 | Invalid input/output offset types of an activity |
364 | Invalid confirmed start time of an activity |
365 | Invalid times for dummy activities |
366 | Invalid specification for block limit scheduling |
367 | Planned offset in I/O node is smaller than the process-based offset |
368 | Resource 'use_block_times' set in first or last block |
369 | Combined information in SNP for header orders only |
370 | Duplicate SNP order group ID |
371 | "Inactive Setup Activity" flag for sequence-depend. setup activities only |
372 | "Inactive Setup Activity" flag not for confirmed activities |
373 | Cannot change "Activity Status" and "Inactive Setup Activity" simultan. |
374 | Invalid old processing duration |
375 | Buytype_code outside value range of an UINT2 |
376 | Constraint not found |
377 | Duplicate constraint |
378 | Constraint cannot be scheduled simult. between predecessor and successor |
379 | Cover constraint for same operation only |
380 | No breaks with overlapping intervals |
381 | Aggregate if overlapping intervals exist |
382 | Invalid SFW I/O node |
383 | Neg. stock characteristic requirement from_char_value <> to_char_value |
384 | Neg. stock characteristic requirement from_quant_value <> to_quant_value |
385 | Neg. stock characteristic requirement operation <> 'I' |
386 | Storage sublocation of a storage resource cannot be changed |
387 | Sublocation of a storage resource not equal to sublocation of a stock |
388 | Setup key of an activity could not be changed |
391 | Pegging area cannot be deleted, as it is still being used by RPM matrix |
400 | Error in maintenance release |
477 | Order changed or deleted in parallel |
501 | An attempt was made to reschedule a fixed resource |
502 | No mode was specified for rescheduling an activity with modes |
503 | A mode was specified for rescheduling an activity without modes |
504 | Activity with unknown mode |
505 | This is a bucket resource |
506 | Activity has incorrect planning status |
507 | Not all activities of a cover chain are specified |
601 | Time stream is still being used by at least one resource |
612 | Time stream is empty |
613 | Time stream already exists |
614 | Overlap of stages for 'append' |
615 | Incorrect seperator for stages for 'insert' mode |
616 | Time stream must contain at least two work periods |
802 | Invalid planning version for a resource |