| /SPE/SSE_MSG000 |
No items are present in the scrap order &1 |
| /SPE/SSE_MSG001 |
The scrap qty must be > 0 for line item &1 |
| /SPE/SSE_MSG002 |
The materials to be scrapped should belong to the same warehouse |
| /SPE/SSE_MSG003 |
The value of the scrap indicator must be 'A', 'B' or 'C' |
| /SPE/SSE_MSG004 |
The warehouse &1 is not an EWM |
| /SPE/SSE_MSG005 |
No active BAdI implementation exists |
| /SPE/SSE_MSG006 |
Material is not present in line item &1 |
| /SPE/SSE_MSG007 |
Location is not present for line item &1 |
| /SPE/SSE_MSG008 |
Mismatch in APO & BAdI specified info.Schedule Line Id &1, Plnt &2 Mat &3 |
| /SPE/SSE_MSG009 |
Header data is not present in the APO scrap information |
| /SPE/SSE_MSG010 |
The scrap items must belong to the same location for order &1 |
| /SPE/SSE_MSG011 |
Stock not available for Plant &1 Sloc &2 Material &3 |
| /SPE/SSE_MSG012 |
No record found for material &1 in lt_mat_qty_col |
| /SPE/SSE_MSG013 |
No record found for material in APO item table for material &1 |
| /SPE/STO_HANDLING000 |
Outbound delivery &1 is not a replenishment delivery |
| /SPE/STO_HANDLING001 |
No inbound delivery exists for the replenishment delivery &1 |
| /SPE/STO_HANDLING002 |
No inbound delivery created for the replenishment delivery &1 |
| /SPE/STO_HANDLING003 |
Inbound delivery &1 is not getting selected |
| /SPE/STO_HANDLING004 |
Inbound delivery &1 is not deleted |
| /SPE/TPOP_QUOTE_MSG000 |
User &1 is not linked to a business partner; contact your system admin |
| /SPE/TPOP_QUOTE_MSG001 |
No records found for the given selection criteria |
| /SPE/TPOP_QUOTE_MSG002 |
Select a single record |
| /SPE/TPOP_QUOTE_MSG003 |
Enter delivery date later than the quotation deadline date |
| /SPE/TPOP_QUOTE_MSG004 |
Delivery date more than a year in the future |
| /SPE/TPOP_QUOTE_MSG005 |
Can delivery date be met? |
| /SPE/TPOP_QUOTE_MSG006 |
Enter RFQ quantity |
| /SPE/TPOP_QUOTE_MSG007 |
&1 is not assigned to the purchasing organization |
| /SPE/TPOP_QUOTE_MSG008 |
Delivery date: next workday is &1 for the item number &2 |
| /SPE/TPOP_QUOTE_MSG009 |
Enter a valid delivery date |
| /SPE/TPOP_QUOTE_MSG010 |
No item details found |
| /SPE/TPOP_QUOTE_MSG011 |
Quotation &1 is currently being edited by &2 |
| /SPE/TPOP_QUOTE_MSG012 |
Delivery date outside the period covered by the factory calendar & |
| /SPE/TPOP_QUOTE_MSG013 |
Factory calendar & does not exist |
| /SPE/VL000 |
Delivery is unchecked; distribution to warehouse &1 is not configured |
| /SPE/VL001 |
Delivery &1 is unchecked |
| /SPE/VL002 |
Distr. of unchecked deliveries only supported with change management |
| /SPE/VL003 |
Delivery is distributed; no check possible |
| /SPE/VL004 |
Database access error in &1 for table &2, key: &3 |
| /SPE/VL005 |
No destination to APO system |
| /SPE/VL006 |
Material &1 not maintained for sales organization: &2 &3 &4 |
| /SPE/VL007 |
Sales document &1 is located in the system &2 and can not be displayed. |
| /SPE/VL008 |
Material &1 is not maintained for plant &2 storage location &3 |
| /SPE/VL010 |
Error in function &1, return code &2 |
| /SPE/VL011 |
Communication to ext. WM for this kind of ext. WM not supported |
| /SPE/VL020 |
Not enough alternative identifier fields in table VEKP |
| /SPE/VL030 |
No unique receiver could be determined in the distribution model |
| /SPE/VL031 |
No receiver maintained in the distribution model for warehouse &1 |
| /SPE/VL032 |
The quantity change request is only supported with qRFC technique |
| /SPE/VL033 |
The quantity change request is only supported with qRFC or eSOA technique |
| /SPE/VL040 |
No delivery item was created for this item (delivery group &2 incomplete) |
| /SPE/VL041 |
Delivery split due to conflicting header data (&2); no delivery created |
| /SPE/VL042 |
Unchecked delivery item for this order item was deleted (critical limit) |
| /SPE/VL043 |
No APO integration model active for material & |
| /SPE/VL044 |
Scheduling failed for document &1 item &2 |
| /SPE/VL045 |
The unchecked delivery & does not exist |
| /SPE/VL046 |
The unchecked delivery &1 item &2 does not exist |
| /SPE/VL047 |
This function is not possible on an index list |
| /SPE/VL048 |
The unchecked del. &1 with predecessor &2 was not converted. (long text) |
| /SPE/VL049 |
Delivery can only be displayed, document is planned for distribution |
| /SPE/VL050 |
No conversion of &1 possible because release date is in the future |
| /SPE/VL051 |
Kit & is not complete (kit will be deleted) |
| /SPE/VL052 |
Exception. No document could be processed. |
| /SPE/VL053 |
Correlation of items reduced the quantity of this item to 0. |
| /SPE/VL054 |
Kit & is not complete (kit will not be converted) |
| /SPE/VL055 |
Unchecked delivery not suitable for this function. |
| /SPE/VL060 |
No free delivery number contained within reuse buffer |
| /SPE/VL061 |
Delivery number &4 is not suitable for interval &2 |
| /SPE/VL070 |
Unique HU numbering is active, HU lean status update not possible |
| /SPE/VL071 |
HU lean status update is active, unique HU numbering not possible |
| /SPE/VL072 |
You cannot select both the HU lean status update and unique HU numbering |
| /SPE/VL080 |
The Correlation Service can only be performed in one planning system. |
| /SPE/VL081 |
Corr. Serv. cannot be performed in &1. Integration model necessary. |
| /SPE/VL105 |
You cannot use number recycling and mass queues at the same time |
| /SPE/VL106 |
Cross delivery handling units are only supported in connection with EWM |
| /SPE/VL107 |
Goods movement for kit header not possible |
| /SPE/VL108 |
Foreign trade document &1 of inbound delivery &2 could not be updated |
| /SPE/VL109 |
Goods movement for delivery &1 can only be posted from decentral EWM |
| /SPE/VL110 |
Cross delivery handling units are only supported in connection with EWM |
| /SPE/VL111 |
Cross delivery handling units are only supported in connection with EWM |
| /SPE/VL200 |
No follow-on movement type could be determined for &1 &2 |
| /SPE/VL201 |
No POD storage location assigned to plant &1 |
| /SPE/VL202 |
No unique POD default reason code could be determined (table TVPODG) |
| /SPE/VL203 |
No unique exception code could be determined for POD reason code &1 |
| /SPE/VL204 |
No unique exception code could be determined for code &1 |
| /SPE/VL205 |
Subsequent inbound delivery could not be determined for delivery &1 |
| /SPE/VL250 |
No billing documents found for the given outbound delivery items. |
| /SPE/VL251 |
Calling function with empty input table. |
| /SPE/VL252 |
Found bill has entries for outbound deliveries, which are not in list. |
| /SPE/VL253 |
No Billing Document found. |
| /SPE/VL254 |
Billing has not been done for a billing relevant item. |
| /SPE/VL255 |
Item not found (VBUP). |
| /SPE/VL256 |
Printing profile &1 not maintained for application &3 and output type &2 |
| /SPE/VL257 |
No billing relevant items given. |
| /SPE/VL258 |
Billing Document &1 not found. |
| /SPE/VL259 |
No Items found for Billing Document &1. |
| /SPE/VL260 |
Outbound Delivery &1 not found, for Position of Billing Document &2. |
| /SPE/VL261 |
Version Number not correct Delivery &1 Item &2 Ver.&3 <> Ver.&4 |
| /SPE/VL262 |
Requested Delivery Item not found (Delivery &1, Item &2) |
| /SPE/VL263 |
No output found for billing document &1 |
| /SPE/VL264 |
Bill not created for Billing relevant Outbound Delivery &1 Item &2 |