SAP ABAP Message Class VSMI (Message for Development Class VSMI)
Basic Data
Hierarchy
☛
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
⤷ SD-BF-SMI (Application Component) Supplier Managed Inventory
⤷ VSMI (Package) Supplier-Managed Inventory (SNC-ERP)
⤷ SD-BF-SMI (Application Component) Supplier Managed Inventory
⤷ VSMI (Package) Supplier-Managed Inventory (SNC-ERP)
Attributes
Message class | VSMI | |
Short Description | Message for Development Class VSMI | |
Changed On | 20100310 | |
Last Changed At | 155918 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | & & & & | The short text describes the object sufficiently | |
2 | 001 | More than one info record exists for customer &1 and material &2 | The short text describes the object sufficiently | |
3 | 002 | Internal error in &1 with &2 &3 &4 | Space: object requires documentation | |
4 | 003 | Required parameters where not filled by caller &1 | The short text describes the object sufficiently | |
5 | 004 | Table entry not found in table &1 | The short text describes the object sufficiently | |
6 | 005 | Active profiles &4 exist for &1 &2 &3; activation not possible | Space: object requires documentation | |
7 | 006 | No active profile found &1 &2 &3 | Space: object requires documentation | |
8 | 007 | Several applicable active profiles found for item & | Space: object requires documentation | |
9 | 008 | No sales scheduling agreement found for &1 &2 &3 | Space: object requires documentation | |
10 | 009 | Violation of the maximum stock level | Space: object requires documentation | |
11 | 010 | Violation of the minimum stock level | Space: object requires documentation | |
12 | 011 | Specify at least one of the profile fields &1 &2 &3 | Space: object requires documentation | |
13 | 012 | No server group found for RFC processing | Space: object requires documentation | |
14 | 013 | Maximum number of delivery schedules reached for &1 &2 | Space: object requires documentation | |
15 | 014 | ARRAY op error: DB table=&1, op=&2, rc=&3, lines=&4 | The short text describes the object sufficiently | |
16 | 015 | Tolerances violated in period &1 of profile &2 | Space: object requires documentation | |
17 | 016 | No delivery schedules allowed for scheduling agreement &1 | The short text describes the object sufficiently | |
18 | 017 | &1-&2ID field is too long; a maximum of &3 characters is allowed | The short text describes the object sufficiently | |
19 | 018 | Required ID & is missing | The short text describes the object sufficiently | |
20 | 019 | Processing of item &1 &2 &3 was canceled | The short text describes the object sufficiently | |
21 | 020 | Processing of item & was stopped | The short text describes the object sufficiently | |
22 | 021 | Unit of measurement ISO code & is unknown | The short text describes the object sufficiently | |
23 | 022 | The corresponding vendor ID of product & could not be determined | The short text describes the object sufficiently | |
24 | 023 | Scheduling agreement &(&) pertains to the material & instead of & | The short text describes the object sufficiently | |
25 | 024 | Processing of message & canceled; message does not contain valid items | The short text describes the object sufficiently | |
26 | 025 | Processing of message & canceled; header is invalid | The short text describes the object sufficiently | |
27 | 026 | No valid values found for the current selection | The short text describes the object sufficiently | |
28 | 027 | Header of message & could not be saved in the database | The short text describes the object sufficiently | |
29 | 028 | Item & could not be saved in the database | The short text describes the object sufficiently | |
30 | 029 | Internal material ID for customer ID & not found | The short text describes the object sufficiently | |
31 | 030 | Unable to determine replenishment strategy for item & | The short text describes the object sufficiently | |
32 | 031 | Replenishment processing of all items in message & failed | The short text describes the object sufficiently | |
33 | 032 | Replenishment processing of item & failed | The short text describes the object sufficiently | |
34 | 033 | Execution of business logic failed; no outbound message was sent | The short text describes the object sufficiently | |
35 | 034 | Sending of outbound PROACT message failed | The short text describes the object sufficiently | |
36 | 035 | Mandatory & information is missing | The short text describes the object sufficiently | |
37 | 036 | Mandatory timestamp & is missing | The short text describes the object sufficiently | |
38 | 037 | & internal ID and buyer ID not specified | The short text describes the object sufficiently | |
39 | 038 | & internal ID not specified | The short text describes the object sufficiently | |
40 | 039 | & buyer ID not specified | The short text describes the object sufficiently | |
41 | 040 | & vendor ID not specified | The short text describes the object sufficiently | |
42 | 041 | & unit of measurement is not specified | The short text describes the object sufficiently | |
43 | 042 | Received message does not contain a message ID | The short text describes the object sufficiently | |
44 | 043 | Building header for message ID & | The short text describes the object sufficiently | |
45 | 044 | Building internal mapping of product & | The short text describes the object sufficiently | |
46 | 045 | Calculating replenishment proposal for product & (replenish to maximum) | The short text describes the object sufficiently | |
47 | 046 | Calculating replenishment proposal for product & (replenish to minimum) | The short text describes the object sufficiently | |
48 | 047 | Calculating replenishment proposal for product & (custom algorithm) | The short text describes the object sufficiently | |
49 | 048 | Stop indicator of item & was set | The short text describes the object sufficiently | |
50 | 049 | Time zone determination failed for scheduling agreement & | The short text describes the object sufficiently | |
51 | 050 | Error during delivery schedule creation for agreement &1 item &2 | The short text describes the object sufficiently | |
52 | 051 | Unable to lock message ID &1 in the database | The short text describes the object sufficiently | |
53 | 052 | Unable to lock message ID &1 item ID &2 in the database | The short text describes the object sufficiently | |
54 | 053 | Unable to lock message ID &1 item ID &2 time series type &3 in database | The short text describes the object sufficiently | |
55 | 054 | Foreign lock set in database | The short text describes the object sufficiently | |
56 | 055 | Internal error during database locking | The short text describes the object sufficiently | |
57 | 056 | System failure during database locking | The short text describes the object sufficiently | |
58 | 057 | Sales document type &1 is not allowed | Space: object requires documentation | |
59 | 058 | Unable to build record object of message ID &1 | The short text describes the object sufficiently | |
60 | 059 | Unable to build item object of material ID &1 | The short text describes the object sufficiently | |
61 | 060 | Unable to build time series object type &1 for material ID &2 | The short text describes the object sufficiently | |
62 | 061 | Error in BAdI &1 | The short text describes the object sufficiently | |
63 | 062 | No BAdI implementation exists for BAdI &1 | Space: object requires documentation | |
64 | 063 | Message processing canceled; all items of message &1 have been rejected | The short text describes the object sufficiently | |
65 | 064 | Outbound PROACT message (&1) has been sent successfully | The short text describes the object sufficiently | |
66 | 065 | Item &1 vbeln: &3 posnr: &4 removed from &2 processing queue | The short text describes the object sufficiently | |
67 | 066 | Status of prev.reported item &1 &3 &4 from message &2 set to obsolete | The short text describes the object sufficiently | |
68 | 067 | Failed to raise alert &1; alert category is unknown | The short text describes the object sufficiently | |
69 | 068 | Failed to raise alert &1; no recipients have been specified | The short text describes the object sufficiently | |
70 | 069 | Failed to raise alert &1; unknown destination | The short text describes the object sufficiently | |
71 | 070 | Failed to raise alert &1; communication failure | The short text describes the object sufficiently | |
72 | 071 | Failed to raise alert &1; system failure | The short text describes the object sufficiently | |
73 | 072 | Successfully raised alert &1 | The short text describes the object sufficiently | |
74 | 073 | A newer report of item &1 exists on the database (MessageID &2) | The short text describes the object sufficiently | |
75 | 074 | Several profiles exist for &1; &2; &3; active='&4' | The short text describes the object sufficiently | |
76 | 075 | Scheduling agreement &1 item &2 is SMI relevant | The short text describes the object sufficiently | |
77 | 076 | Customer material in Customizing and scheduling agreement differ | Space: object requires documentation | |
78 | 077 | Customer plant in Customizing and scheduling agreement differ | Space: object requires documentation | |
79 | 078 | Unable to convert unit of measurement '&1' into the internal format | The short text describes the object sufficiently | |
80 | 079 | Unable to convert quantity field without data loss | The short text describes the object sufficiently | |
81 | 080 | &1: &2: exception during quantity conversion | The short text describes the object sufficiently | |
82 | 081 | No authority to change the scheduling agreement &1 | The short text describes the object sufficiently | |
83 | 082 | Unit of measurement &1 does not correspond to sales unit &2 | The short text describes the object sufficiently | |
84 | 083 | Error during verfication of timeseries type '&1' | The short text describes the object sufficiently | |
85 | 084 | Minimum limit is greater than maximum limit | The short text describes the object sufficiently | |
86 | 085 | Unit of Measurements &1 and &2 are not equal | The short text describes the object sufficiently | |
87 | 086 | Negative quantity not allowed in field &1 | The short text describes the object sufficiently | |
88 | 087 | Invalid period in time series type &1 | Space: object requires documentation | |
89 | 088 | &1 : unit of measurement is missing for quantity report | The short text describes the object sufficiently | |
90 | 089 | Limits of item &1 have changed since the last item report | The short text describes the object sufficiently | |
91 | 090 | Please select only one item. | The short text describes the object sufficiently | |
92 | 091 | Scheduling agreement &1 &2 has a planning DS instruction assigned | Space: object requires documentation | |
93 | 092 | Scheduling agreement &1 &2 has setup a deviation tolerance check | Space: object requires documentation | |
94 | 093 | Please enter a value >= 0 | The short text describes the object sufficiently | |
95 | 094 | Message ID &1 for Customer &2 deleted | The short text describes the object sufficiently | |
96 | 095 | Started manual processing of item &1 vbeln: &3 posnr: &4 in message &2 | The short text describes the object sufficiently | |
97 | 096 | End of manual processing of item &1 vbeln: &3 posnr: &4 in message &2 | The short text describes the object sufficiently | |
98 | 097 | Building item report for outbound service: Item &1 &3 &4 of message &2 | The short text describes the object sufficiently | |
99 | 098 | Using profile &1 for item &2 vbeln &3 posnr &4 | The short text describes the object sufficiently | |
100 | 099 | Reference doc &1 item &2 deviates from scheduling agreement data | Space: object requires documentation | |
101 | 100 | Any changes to the item have been reset to the last saved state | The short text describes the object sufficiently | |
102 | 101 | ForecastDeliverySchedule has been created and item has been saved. | The short text describes the object sufficiently | |
103 | 102 | Item is currently marked as "obsolete". Please create the FDS first | The short text describes the object sufficiently | |
104 | 103 | Replenishment logic has not been executed. Please create a FDS first | The short text describes the object sufficiently | |
105 | 104 | Item has been reported in a previous message. Please create a FDS first | The short text describes the object sufficiently | |
106 | 105 | Item has been saved | The short text describes the object sufficiently | |
107 | 106 | Replenishment proposal has been calculated | The short text describes the object sufficiently | |
108 | 107 | Replenishment simulation has been executed | The short text describes the object sufficiently | |
109 | 108 | Parameters missing when calling Application. XMLGUID:&1 Mat.:&2 Doc.:&3 | The short text describes the object sufficiently | |
110 | 109 | Enter only values with a maximum of &1 decimal(s) | The short text describes the object sufficiently | |
111 | 110 | Processing of message &1 and all contained items was canceled. | The short text describes the object sufficiently | |
112 | 111 | Maximum value for timeseries quantity violated | The short text describes the object sufficiently | |
113 | 112 | Safety quantity field has been cleared | Space: object requires documentation |
History
Last changed on/by | 20100310 | SAP | |
SAP Release Created in | 604 |