SAP ABAP Message Class /SPE/VL (Service Parts Management: Shipping messages)
Basic Data
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷ LO-SPM-OUT (Application Component) Goods Issue Process
⤷ /SPE/VL (Package) WS-SHP: Shipping / Service Parts Managements enhancements
⤷ LO-SPM-OUT (Application Component) Goods Issue Process
⤷ /SPE/VL (Package) WS-SHP: Shipping / Service Parts Managements enhancements
Attributes
Message class | /SPE/VL | |
Short Description | Service Parts Management: Shipping messages | |
Changed On | 20140121 | |
Last Changed At | 105422 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | Delivery is unchecked; distribution to warehouse &1 is not configured | Space: object requires documentation | |
2 | 001 | Delivery &1 is unchecked | Space: object requires documentation | |
3 | 002 | Distr. of unchecked deliveries only supported with change management | Space: object requires documentation | |
4 | 003 | Delivery is distributed; no check possible | Space: object requires documentation | |
5 | 004 | Database access error in &1 for table &2, key: &3 | Space: object requires documentation | |
6 | 005 | No destination to APO system | Space: object requires documentation | |
7 | 006 | Material &1 not maintained for sales organization: &2 &3 &4 | Space: object requires documentation | |
8 | 007 | Sales document &1 is located in the system &2 and can not be displayed. | The short text describes the object sufficiently | |
9 | 008 | Material &1 is not maintained for plant &2 storage location &3 | The short text describes the object sufficiently | |
10 | 010 | Error in function &1, return code &2 | Space: object requires documentation | |
11 | 011 | Communication to ext. WM for this kind of ext. WM not supported | The short text describes the object sufficiently | |
12 | 020 | Not enough alternative identifier fields in table VEKP | Space: object requires documentation | |
13 | 028 | Role &1 is not assigned to partner procedure &2 of delivery type &3 | Space: object requires documentation | |
14 | 030 | No unique receiver could be determined in the distribution model | Space: object requires documentation | |
15 | 031 | No receiver maintained in the distribution model for warehouse &1 | Space: object requires documentation | |
16 | 032 | The quantity change request is only supported with qRFC technique | Space: object requires documentation | |
17 | 033 | The quantity change request is only supported with qRFC or eSOA technique | The short text describes the object sufficiently | |
18 | 040 | No delivery item was created for this item (delivery group &2 incomplete) | Space: object requires documentation | |
19 | 041 | Delivery split due to conflicting header data (&2); no delivery created | Space: object requires documentation | |
20 | 042 | Unchecked delivery item for this order item was deleted (critical limit) | Space: object requires documentation | |
21 | 043 | No APO integration model active for material & | Space: object requires documentation | |
22 | 044 | Scheduling failed for document &1 item &2 | Space: object requires documentation | |
23 | 045 | The unchecked delivery & does not exist | Space: object requires documentation | |
24 | 046 | The unchecked delivery &1 item &2 does not exist | Space: object requires documentation | |
25 | 047 | This function is not possible on an index list | Space: object requires documentation | |
26 | 048 | The unchecked del. &1 with predecessor &2 was not converted. (long text) | Space: object requires documentation | |
27 | 049 | Delivery can only be displayed, document is planned for distribution | The short text describes the object sufficiently | |
28 | 050 | No conversion of &1 possible because release date is in the future | Space: object requires documentation | |
29 | 051 | Kit & is not complete (kit will be deleted) | The short text describes the object sufficiently | |
30 | 052 | Exception. No document could be processed. | The short text describes the object sufficiently | |
31 | 053 | Correlation of items reduced the quantity of this item to 0. | The short text describes the object sufficiently | |
32 | 054 | Kit & is not complete (kit will not be converted) | The short text describes the object sufficiently | |
33 | 055 | Unchecked delivery not suitable for this function. | Space: object requires documentation | |
34 | 056 | No delivery due index found for STO &1 | The short text describes the object sufficiently | |
35 | 060 | No free delivery number contained within reuse buffer | Space: object requires documentation | |
36 | 061 | Delivery number &4 is not suitable for interval &2 | Space: object requires documentation | |
37 | 070 | Unique HU numbering is active, HU lean status update not possible | The short text describes the object sufficiently | |
38 | 071 | HU lean status update is active, unique HU numbering not possible | The short text describes the object sufficiently | |
39 | 072 | You cannot select both the HU lean status update and unique HU numbering | The short text describes the object sufficiently | |
40 | 080 | The Correlation Service can only be performed in one planning system. | Space: object requires documentation | |
41 | 081 | Corr. Serv. cannot be performed in &1. Integration model necessary. | Space: object requires documentation | |
42 | 085 | Item &1 of returns delivery &2 has not been completed yet. | The short text describes the object sufficiently | |
43 | 099 | Some HU data could not be found in internal tables. | Space: object requires documentation | |
44 | 105 | You cannot use number recycling and mass queues at the same time | Space: object requires documentation | |
45 | 106 | Cross delivery handling units are only supported in connection with EWM | Space: object requires documentation | |
46 | 107 | Goods movement for kit header not possible | Space: object requires documentation | |
47 | 108 | Foreign trade document &1 of inbound delivery &2 could not be updated | The short text describes the object sufficiently | |
48 | 109 | Goods movement for delivery &1 can only be posted from decentral EWM | The short text describes the object sufficiently | |
49 | 110 | Cross delivery handling units are only supported in connection with EWM | Space: object requires documentation | |
50 | 111 | Cross delivery handling units are only supported in connection with EWM | Space: object requires documentation | |
51 | 200 | No follow-on movement type could be determined for &1 &2 | The short text describes the object sufficiently | |
52 | 201 | No POD storage location assigned to plant &1 | Space: object requires documentation | |
53 | 202 | No unique POD default reason code could be determined (table TVPODG) | The short text describes the object sufficiently | |
54 | 203 | No unique exception code could be determined for POD reason code &1 | The short text describes the object sufficiently | |
55 | 204 | No unique exception code could be determined for code &1 | The short text describes the object sufficiently | |
56 | 205 | Subsequent inbound delivery could not be determined for delivery &1 | The short text describes the object sufficiently | |
57 | 250 | No billing documents found for the given outbound delivery items. | The short text describes the object sufficiently | |
58 | 251 | Calling function with empty input table. | The short text describes the object sufficiently | |
59 | 252 | Found bill has entries for outbound deliveries, which are not in list. | The short text describes the object sufficiently | |
60 | 253 | No Billing Document found. | The short text describes the object sufficiently | |
61 | 254 | Billing has not been done for a billing relevant item. | The short text describes the object sufficiently | |
62 | 255 | Item not found (VBUP). | The short text describes the object sufficiently | |
63 | 256 | Printing profile &1 not maintained for application &3 and output type &2 | The short text describes the object sufficiently | |
64 | 257 | No billing relevant items given. | The short text describes the object sufficiently | |
65 | 258 | Billing Document &1 not found. | The short text describes the object sufficiently | |
66 | 259 | No Items found for Billing Document &1. | The short text describes the object sufficiently | |
67 | 260 | Outbound Delivery &1 not found, for Position of Billing Document &2. | The short text describes the object sufficiently | |
68 | 261 | Version Number not correct Delivery &1 Item &2 Ver.&3 <> Ver.&4 | The short text describes the object sufficiently | |
69 | 262 | Requested Delivery Item not found (Delivery &1, Item &2) | The short text describes the object sufficiently | |
70 | 263 | No output found for billing document &1 | The short text describes the object sufficiently | |
71 | 264 | Bill not created for Billing relevant Outbound Delivery &1 Item &2 | The short text describes the object sufficiently | |
72 | 265 | Bill allready exists for Outbound Delivery &1. | The short text describes the object sufficiently | |
73 | 266 | Billing Indicator differs in Outbound Deliveries (&1 Ind:&2, &3 Ind: &4) | The short text describes the object sufficiently | |
74 | 267 | Outbound Delivery &1 not found! | The short text describes the object sufficiently | |
75 | 268 | Output &1 was already processed and cannot be repeated | The short text describes the object sufficiently | |
76 | 269 | Cancel of Goods Issue not allowed with existing Bill (FKART &1,VKORG &2). | The short text describes the object sufficiently | |
77 | 270 | Sales Document not found for &1. | The short text describes the object sufficiently | |
78 | 300 | Output processing has been triggered in a new task | Space: object requires documentation | |
79 | 400 | System is attempting to adjust the delivery quantity | The short text describes the object sufficiently | |
80 | 401 | Documentary batches are not supported for replenishment deliveries. | Space: object requires documentation | |
81 | 402 | Choose delivery output 'SPED' for inbound delivery creation (SIT) | The short text describes the object sufficiently |
History
Last changed on/by | 20140121 | SAP | |
SAP Release Created in | 100 |