APO_BAPI - Message Class for APO BAPIs
The following messages are stored in message class APO_BAPI: Message Class for APO BAPIs.
It is part of development package MSCMB_BAPI_CORE in software component SCM-BAS-INT-EXT. This development package consists of objects that can be grouped under "MSCMB_BAPI_CORE".
It is part of development package MSCMB_BAPI_CORE in software component SCM-BAS-INT-EXT. This development package consists of objects that can be grouped under "MSCMB_BAPI_CORE".
Message Nr ▲ | Message Text |
---|---|
001 | Error in creation of response IDoc to CALLID &1 IDoc &2 / &3 |
002 | Processing terminated: Errors in initialization of application log |
003 | Update excuted despite errors (see long text) |
004 | Rollback executed (see long text) |
005 | No mapping entry for external location &1 type &2 exists |
006 | Invalid entry combination. Stock type cannot be uniquely assigned |
007 | Error in recipient determination. RFQ responses not sent |
008 | Business system group &1 does not exist |
009 | Filter objects for object &1, method &2 have errors |
010 | Error in ALE customizing for object &1, method &2 |
011 | RFC destination for object &1, method &2 not maintained |
012 | Order type &1 is not permitted for business object &2 |
013 | Planning result could not be sent to logical system &1 |
014 | Error in creation of response IDoc for logical system &1 |
015 | Language key &1 is not valid for maintaining a short text |
016 | Unit &1 not valid for maintaining an alternative unit of quantity |
017 | Characteristics are not changed in relative (delta) stock changes |
018 | Specify a valid period for the selection |
019 | Specify an OUTPUT node with the key &1 for the INPUT node |
020 | No mapping entries exist for external product &1 |
021 | Location product cannot be determined for product &1 location &2 type &3 |
022 | No stock found for key: &1 |
023 | Order with external number &1, object type &2 does not exist |
024 | Pegging has not changed as no node is available |
025 | Pegging has not changed, as internal error &1 occurred |
026 | Resource &1, external location &2, type &3 does not exist |
027 | An error occurred in data selection |
028 | Pegging has not changed, as errors occurred reading pegging data |
029 | Stock with key &1 could not be changed |
030 | Pegging information could not be read. Source of error: &1 |
031 | Component not clearly specified |
032 | Component (&2) could not be determined automatically |
033 | SCM internal order &1 does not exist |
034 | Location &1 does not exist in system group &2 |
035 | Resource &1 does not exist in system group &2 |
036 | Product &1 does not exist in system group &2 |
037 | Order &1 does not exist in system group &2 |
038 | Char. requirements for INPUT nodes from order &1 type &2 are inconsistent |
039 | Char. evaluations for OUTPUT nodes from order &1 type &2 are inconsistent |
040 | Char. evaluations for activities from order &1 type &2 are inconsistent |
041 | APO local orders (BUS10505) may not be created externally |
042 | The specified setup key &1 does not exist in the location |
043 | Block &1 is not defined in the resource |
044 | Sales order with GUID &1 does not exist |
045 | External number assignment: Use order number instead of GUID &1 |
046 | External number assignment: Invalid order type 'APO local order' |
047 | Order creation with external number (no GUID) only for active Version |
048 | Specify start time for forward scheduling |
049 | Specify end time for backward scheduling |
050 | Messages or errors have occurred for scheduling |
051 | Entry was not processed because there is no changing parameter available |
052 | Specify start and end time |
053 | GUID32 &1 could not be converted. |
054 | GUID &1 could not be converted to GUID32 |
055 | Order/schedule line does not exist and will not be created automatically |
056 | The given end date &1 is not in the valid time interval |
057 | No valid source of supply could be found &1 &2 &3 |
058 | Block &1 is invalid |
059 | Rule &1 is invalid |
060 | Resource &1 already exists (mapping error occurred) |
061 | PLAN-ID (GUID) could not be found |
062 | It is not possible to create a resource without a name (only with GUID) |
063 | Error &1 occurred while calling up function &2 |
064 | Invalid value &2 transferred in parameter/field &1 |
065 | No valid plan could be found |
066 | Status does not allow orders to be changed (&1) |
067 | Order change with external name (no GUID) only for active version |
068 | Activity status does not allow activities to be changed |
069 | Component ID (GUID) could not be determined |
070 | Order of type &1 cannot be changed using this interface |
071 | Invalid combination of selection criteria |
072 | &2 entries in selection tables exceed Maximum Number (&1) |
073 | Planning version &1 cannot be used. Specify valid value |
074 | Enter a valid order number |
075 | Mapping entry for order &1 already exists |
076 | SNP cost function could not be selected |
077 | No valid Location could be found |
078 | No valid resource could be found |
079 | Characteristics could not be processed because of inconsistencies |
080 | Characteristics evaluations for stock (&1 &2 &3) are inconsistent. |
081 | No mapping entry for GUID &1 |
082 | The selection contains too many produkt/location combinations |
083 | Location is assigned to material / resource or model |
084 | Deletion flag could not be set |
085 | Location is assigned to ATP or set up group/set up key |
086 | No capacity requirements could be determined for this activity |
087 | No material could be selected |
088 | No location could be selected |
089 | Order &1 &2 &3 already exists |
090 | Location cannot be deleted, because Transportzone is maintained |
091 | Location cannot be deleted because of existing TSP assignment |
092 | Only demand priorities 1, 5 and 6 are supported |
093 | Error when creating/changing blocks |
094 | A different planning version is being used |
095 | Another transactional simulation is currently being used |
096 | Data has not been entered in all required fields for the key assignment |
097 | Different external key assignment for the same object |
098 | No mapping entry for PRODID &1 and LOCID &2 could be found |
099 | Invalid location type &1 for this function |
100 | No variant for available capacity has been specified |
101 | Bid does not exist |
102 | Status of bid is invalid |
103 | Bid already exists |
104 | Bid already exists |
105 | Status of bid invitation is invalid |
106 | No valid product could be found |
107 | Unit of measure could not be converted |
108 | For demand element &1 &2 there is no corresponding receipt element |
109 | Value &1 is not defined for this parameter |
110 | Catagory &1 is not defined for catagory type &2 or R/3 object &3 |
111 | No selection ID could be detemined for the selected selection |
112 | Enter a selection for the planning book |
113 | No valid planning area could be determined for the planning book |
114 | For specified selection ID no selection could be determined |
115 | No planning book called &1 could be found |
116 | No authorization for planning book called &1 |
117 | For time series ID &1 there is no entry in TimeSeries Table |
118 | Characteristics combination for ID &1 does not exist in planning book |
119 | Consumption against contract &1 / &2 only in oper. plng version &3 poss. |
120 | Parameter &1 cannot be used for order type &2 |
121 | Field &1 is not supported in this release |
122 | Locking planning area for planning book &1 has failed |
123 | Order &1 and/or schedule line &2 &3 does not exist |
124 | Missing characteristic combinations or grouping |
125 | XML tag &1 with value &2 is ignored. &3 |
126 | XML tag &1 is incorrect here. &2 |
127 | XML tag &1 is missing. &2 |
128 | Incorrect or multiple components have been defined as main products |
129 | Edit XML tag &1 with value &2 |
130 | End XML tag &1 |
131 | Syntax error in XML data stream in transaction ID &1 |
132 | No trading partner is mainintained in the marketplace for partner &1 |
133 | System crash in RFC destination &1 |
134 | Problem with setup of connection in RFC destination &1 |
135 | RFC function &1 in destination &2 not found |
136 | Unknown error when calling up RFC function &1 with destination &2 |
137 | Document &1 of type &2 was rendered successfully |
138 | Document &1 with TID &2 was sent |
139 | Document &1 of type &3 with transaction ID &2 was successfully parsed |
140 | Document &1 with TID &2 was sucessfully transferred to the application |
141 | Error when rendering document &1 of type &2 |
142 | Error when parsing document &1 of type &3 with TID &2 |
143 | Attribute &1 is missing. |
144 | Parser was called up with wrong document type. &1 should be &2. |
145 | Document sender &1 and turnover sender &2 are different |
146 | Error in system in RFC destination &1 (see application log) |
147 | Unknown partner &1. |
148 | Document recipient &1 and turnover recipient &2 are different |
149 | External product name for ID &1 can not be defined clearly |
150 | No plan could be determined for key &1 |
151 | No activity could be determined for actid &1 |
152 | The tables Logical_Component and Comp_Product are not index synchronized |
153 | No logical component could be determined for key &1 |
154 | No PPM could be determined for key &1 |
155 | No mode could be determined for key &1 |
156 | The field CP_DATE_TO must be transmitted for SNP/DP plans |
157 | Document with TID &1 is not available or was deleted |
158 | Collaboration partner &1 is not assigned to scenario &2 |
159 | Location dependent and independent characteristics not allowed for stocks |
160 | Field/parameter &1 is not currently being used |
161 | Plan &1 (internal key) does not exist in system network &2 |
162 | Faulty data: Characteristics combination could not be created |
163 | Processing of SNP planning area not possible |
164 | Field &1 is not currently supported |
165 | Plan &1, PPM &2 is not of the type required for template PPMs |
166 | The value for field &1 can no longer be changed |
167 | The location product does not exist in the system group &4 |
168 | The PPM &1 (internal key) does not exist in system group &2 |
169 | &1 &2 is not contained in table &3 |
170 | Associated characteristics combination could not be determined |
171 | Characteristics selection is only possible for one class |
172 | Log. system & for APO not permitted when using external number assignment |
173 | For characteristic &1 in class &2 you can only select for one value |
174 | Order creation wither ext. number assignment and events is not allowed |
175 | Associated promotion header data has errors |
176 | Doubled entries in parameter &1 |
177 | The BAPI for &1 cannot be used together with &2 in this scenario |
178 | No transactional simulations are open |
179 | The BAPI may not be used in an update process |
180 | Application log for object &1 could not be opened |
181 | No authorization to execute this method |
182 | External transaction control is not permitted for order/schedule line |
183 | Use packeting because > &1 objects are read or written |
184 | A mapping entry could not be determined for resource &1 |
185 | Function or parameter &1 is not supported for planning version &2 |
186 | Location does not exist with internal key specified |
187 | Objects are from different business system groups |
188 | Configurations only read with receipt or requirement elements |
189 | Configuration and object reference may not be used together |
190 | Configuration &1 only possible together with account assignment data |
191 | The configuration can only be used for the active planning version |
192 | Fields &1 &2 &3 &4 may not be empty when they are used |
193 | Pegging not possible because receipt and req. elements are different |
194 | No corresponding entry found for field &1 in parameter &2 &3 |
195 | Unknown error when calling DM function |
196 | Product does not exist with specified internal key |
197 | A corresponding entry for parameter &1 does not exist in parameter &2 |
198 | Data can only currently be saved on a planning-version-independent basis |
199 | Data entered for several planning versions |
200 | Fields &1 &2 and &3 &4 cannot be used together |
201 | System group of product and reference product is not the same |
202 | A client group currency could not be determined |
203 | Error occurred in price conversion |
204 | Location &1 has to be in the same system group as location &2 |
205 | Versions (batches) are only allowed to be location-independent |
206 | The selection given cannot be processed |
207 | Double entries were made for &3 &4 for parameter/field &1 &2 |
208 | Order &1 cannot be changed (due to error &2 - see long text) |
209 | Subsequent configuration is not allowed |
210 | Object already configured with a different class type (&1) |
211 | Time &1 &3 is not permitted and has been changed to &2 |
212 | Location product could not be determined |
213 | Enter a valid selection: &1 &2 &3 &4 |
214 | Maintain either partner products or partner categories, not both |
215 | Internal error, line number &1 of the matrix is unknown |
216 | Internal error, column number &1 of the matrix is unknown |
217 | Data transfer was started |
218 | Data transfer ended successfully |
219 | Function or parameter &1 &2 is not supported for &3 &4 |
220 | Errors occurred, check parameter &1 |
221 | Char. selection by req. element only possible for individual values |
222 | An RFC destination must be specified for the remote call |
223 | Maximum number of fields (&1) exceeded |
224 | Selected parameters contain &1 field(s) |
225 | Exception &2 occurred when function module &1 was called |
226 | Error occurred in code generation |
227 | System &1 is marked as an SAP (R/3) system; deletion is problematic |
228 | Data read from the worksheet |
229 | Function module called |
230 | Data written to worksheet |
231 | Configuration is not supported for order type &1 |
232 | All cells still have to be manually formatted with category &1 |
233 | Only absolute promotions can be processed |
234 | Parameter &1 was set to default value &2 |
235 | Product &1 is not configurable |
236 | Object key was not fully specified |
237 | Different key categories were used |
238 | Call of method (BAPI) &1 &2 &3 &4 |
239 | Method call &1 &2 ended; &3 messages were issued |
240 | Error in user exit or BADI &1 |
241 | &1 stocks were selected |
242 | &1 planned independent requirements selected |
243 | &1 orders or &2 items/schedule lines were selected |
244 | The following &1 objects were not deleted |
245 | The following &1 objects were deleted |
246 | Maximum number of faulty packages has been reached (&1) |
247 | &1 stocks were deleted (duration &2) |
248 | &1 planned independent requirements were deleted (duration &2) |
249 | SAP APO system &1 has been declared as an SAP R/3 system |
250 | The following &1 objects were contained in the faulty package/call |
251 | No objects (stocks, orders, and so on) processed |
252 | Processing completed |
253 | Start of processing |
254 | &1 sales orders/deliveries were deleted (duration &2) |
255 | &1 external procurement orders deleted (duration &2) |
256 | &1 in-house production orders deleted (duration &2) |
257 | The following objects (orders, stocks, and so on) were filtered out |
258 | A PPM could not be found |
259 | Data was changed in BAdI implementation &1 |
260 | Processing ended/terminated by user |
261 | Error occurred during transfer of the customer enhancement for table &1 |
262 | A key figure was not given for characteristics combination &1 |
263 | No values were given for key figure &1 |
264 | Data for characteristics combination &1 could not be processed |
265 | Kwy figure &1 does not exist in data view &2 of planning book &3 |
266 | Time series objects still exist for planning area &1 that is being used |
267 | Date successfully saved to the database |
268 | User-specific data saved successfully |
269 | Time period &1 to &2 does not exist or cannot be changed |
270 | Key figure &1 does not exist in planning book &2 or data view &3 |
271 | Characteristics combination &1 could not be locked |
272 | Selection parameters used |
273 | &1 orders/items/schedule lines transferred to middleware |
274 | For detailed selection, the planning version must be given separately |
275 | The specified evaluation time could not be determined |
276 | The specified business year variant does not exist |
277 | Error occurred when reading the time series data |
278 | No time intervals were selected |
279 | No key figures were selected |
280 | &1 in-house production orders transferred to middleware (duration &2) |
281 | &1 external procurement orders transferred to middleware (duration &2) |
282 | &1 sales orders transferred to middleware (duration &2) |
283 | &1 stocks transferred to middleware (duration &2) |
284 | &1 planned independ. requirements transferred to middleware (duration &2) |
285 | &1 requirement/receipt elements transferred to middleware (duration &2) |
286 | &1 receiving system(s) maintained for object &2 method &3 |
287 | The mapping for external time series &1 could not be determined |
288 | Data for multiple planning areas was transferred |
289 | Application data not transferred or an error occurred during transfer |
290 | Application data transferred despite application messages |
291 | Key figure &1 is not included in planning area &2 |
292 | Package &1 was transferred |
293 | Start of messages for package &1 |
294 | End of messages for package &1 |
295 | No data was processed |
296 | Order combination orders were filtered out, since they cannot be deleted |
297 | Time stamps &1 were not converted |
298 | &1 (order) headers ( &2 IO nodes; &3 receipts; &4 requirements) selected |
299 | Error importing data from database |
300 | Worksheet is not empty |
301 | Only select. acc. to individ. value (=) allowed (no intervals/exclusions) |
302 | Invalid value &4 for field (&3) of parameter &1 in row &2 |
303 | No worksheet has been opened |
304 | No authorization for object &1 and action &2 |
305 | No authorization for object &1, system &2, and action &3 |
306 | Transferred requirmts strategy &1 diff. from strategy &2 in prod. master |
307 | Requirements strategy changed in product: Not possible to change order |
308 | Data for parameter &1 could not be read |
309 | Characteristic &1 is not available in planning area &2 |
310 | Characteristic &1 is not available in planning book &2 |
311 | Initialization error: processing terminated |
312 | IDoc &1 was generated |
313 | &1 location(s) selected |
314 | &1 IDoc(s) generated |
315 | Processing terminated by user, no transfer occurred |
316 | &1 product(s) selected |
317 | No objects were selected for transfer |
318 | Messages occurred in BAdI &1 |
319 | Processing ended/terminated by BAdI &1 |
320 | &1 tRFC(s) generated |
321 | Processing was terminated in accordance with the settings |
322 | &1 location(s) transferred to middleware (duration &2) |
323 | &1 product(s) transferred to middleware (duration &2) |
324 | &1 resource(s) transferred to middleware (duration &2) |
325 | &1 plans transferred to middleware (duration &2) |
326 | &1 transportation lane(s) transferred to middleware (duration &2) |
327 | &1 quota arrangement(s) transferred to middleware (duration &2) |
328 | &1 resource(s) selected |
329 | &1 plans selected |
330 | &1 transportation lane(s) selected |
331 | &1 quota arrangement(s) selected |
332 | ------------------------- Selection Start ------------------------------ |
333 | ------------------------ Selection Ended ----------------------------- |
334 | Profile not found |
335 | Field &1 is not part of parameter &2 |
336 | No inheritence can be defined for field &1 |
337 | Processing was terminated; no data was transferred |
338 | Error occurred when exporting data |
339 | Unknown target system &1 |
340 | Unknown sending mode &1 |
341 | You cannot create an order with more than one item and events |
342 | Events are supported only for purchase requisitions |
343 | You cannot create a purchase order with this method |
344 | No valid location product hierarchy could be found |
345 | &1 production data structure(s) selected |
346 | &1 production data structure(s) transferred to middleware (duration &2) |
347 | Key figure &1 does not support distinc. btw. null value and initial value |
348 | Error occurred when creating or changing order &1 |
349 | Fill all mandatory fields |
350 | Internal processing termination; see long text |
351 | Source of supply category specified is not currently supported |
352 | No valid product hierarchy could be found |
353 | Key figure &1 cannot be fixed |
354 | Change mode &1 cannot be used |
355 | Obligatory parameter &1 was not transferred or was transferred blank |
356 | &1 characteristics combination(s) selected |
357 | Data for production data structure &1 is not processed |
358 | Data for &1 charact. combination(s) transf. to middleware (duration &2) |
359 | Start date is greater than end date |
360 | Specify the period type |
361 | &1 key figure(s) selected |
362 | Logical system &1 is unknown |
363 | Specify a name for the planning book |
364 | Specify a name for the data view |
365 | Enter a planning version |
366 | &1 product hierarchy/hierarchies selected |
367 | &1 location product hierarchy/hierarchies selected |
368 | &1 product hierarchy/hierarchies transferred to middleware (duration &2) |
369 | &1 loc. prod. hierarchy/hierarchies transfrd to middleware (duration &2) |
370 | &1 location determination schema(s) selected |
371 | & product substitution schema(s) selected |
372 | &1 location product substitution schema(s) selected |
373 | &1 PPM substitution schema(s) selected |
374 | &1 substitution rules(s) selected |
375 | &1 loc. determination schema(s) transferred to middleware (duration &2) |
376 | &1 product substitution schema(s) transferred to middleware (duration &2) |
377 | &1 loc. prod. subst. schema(s) transferred to middleware (duration &2) |
378 | &1 PPM substitution schema(s) transferred to middleware (duration &2) |
379 | &1 substitution rule(s) transferred to middleware (duration &2) |
380 | &1 promotion(s) selected |
381 | &1 promotion(s) transferred to middleware (duration &2) |
382 | Specified source of supply &1 could not be found |
383 | Duration could not be converted |
384 | You cannot use the template PPM and the template PDS at the same time |
385 | Application log &1 is not open yet |
386 | Production data structure &1 does not exist |
387 | Missing calculation method for operation quantity for template PPM/PDS |
388 | Error occurred when exploding template PDS |
389 | Invalid planning version &1 |
390 | Invalid transactional simulation version &1 |
391 | Unexpected order categories were found |
392 | You cannot create order with order category &1 for business object &2 |
393 | No authorization for business object &1 (function group: &2) |
394 | Errors occurred when determining object keys |
395 | Negative values are not permitted for key figure &1 |
396 | Null values could not be fixed for key figure &1 |
397 | Seasonal planning is not supported via BAPI |
398 | Variant &1 does not exist |
399 | Log for planning run has number &1 |
400 | Transportation zone could not be created or changed |
401 | Transportation zone: Missing mandatory field &1 |
402 | Planning run ended successfully |
403 | Product category &1 is not supported for parameter &2 |
404 | Use of different business system groups |
405 | Product category &1 is not supported |
406 | Planning mode usage is already set and is being adopted |
407 | Missing Grouping Condition |
408 | Selection Cannot be Converted |
409 | Characteristics-based forecasting is not supported via BAPI |
410 | Error while reading resource |
411 | Field &1 is currently not used for TMS resources |
412 | Header data for partner-dep. purch. doc.: mandatory field &1 not filled |
413 | Values for field &1 must be greater than zero |
414 | Partner-dependent purchasing document: mandatory field &1 is not filled |
415 | Measurement started |
416 | Unable to set flag for administration tables |
417 | Unable to release flag for administration tables |
418 | Administration tables in runtime analysis cannot access shared memory |
419 | Internal error (&): Error passing parameters |
420 | Unable to stop the measurement |
421 | Error when opening the measurement data file (&1) |
422 | Internal error: Runtime analysis has not been initialized |
423 | There are too many measurement data files |
424 | Profile parameter 'abap/atrapath' does not exist |
425 | Unable to write to the measurement data file |
426 | There is already a measurement running in the specified session |
427 | There are already 10 measurements running |
428 | Unable to set a position in the measurement data file |
429 | No more roll memory available |
430 | Missing data; time stamp was converted to UTC |
431 | Invalid coordinates |
432 | Product &1 is unknown |
433 | Product &1 and location &2 does not exist in model &3. |
434 | Characteristic Combination &1 &2 not found in planning book for ID &3. |
436 | Security Error |
437 | Involved location is blocked, no display allowed |
438 | Involved location is blocked, no usage allowed |
439 | Some orders can not be displayed due to missing authorization |
440 | Some entries have been omitted due to blocked locations |
453 | Product &1 is locked. |
454 | Error while reading locations |
455 | No suitable transportation lanes exist |
456 | Error during conversion of the dimension / unit |
457 | System could not find mode for version & |
458 | No entries could be selected for the selection specified |
459 | Invalid IO node |
460 | No means of transport exists |
461 | No valid Location &1 could be found |
500 | Processing cancelled. This BAPI is obsolete. Use &1 instead. |
501 | Processing cancelled. This BAPI is obsolete. |
502 | Processing cancelled. This BAPI is obsolete |