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)
⤷
⤷
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 | & & & & | The short text describes the object sufficiently | ||
| 2 | More than one info record exists for customer &1 and material &2 | The short text describes the object sufficiently | ||
| 3 | Internal error in &1 with &2 &3 &4 | Space: object requires documentation | ||
| 4 | Required parameters where not filled by caller &1 | The short text describes the object sufficiently | ||
| 5 | Table entry not found in table &1 | The short text describes the object sufficiently | ||
| 6 | Active profiles &4 exist for &1 &2 &3; activation not possible | Space: object requires documentation | ||
| 7 | No active profile found &1 &2 &3 | Space: object requires documentation | ||
| 8 | Several applicable active profiles found for item & | Space: object requires documentation | ||
| 9 | No sales scheduling agreement found for &1 &2 &3 | Space: object requires documentation | ||
| 10 | Violation of the maximum stock level | Space: object requires documentation | ||
| 11 | Violation of the minimum stock level | Space: object requires documentation | ||
| 12 | Specify at least one of the profile fields &1 &2 &3 | Space: object requires documentation | ||
| 13 | No server group found for RFC processing | Space: object requires documentation | ||
| 14 | Maximum number of delivery schedules reached for &1 &2 | Space: object requires documentation | ||
| 15 | ARRAY op error: DB table=&1, op=&2, rc=&3, lines=&4 | The short text describes the object sufficiently | ||
| 16 | Tolerances violated in period &1 of profile &2 | Space: object requires documentation | ||
| 17 | No delivery schedules allowed for scheduling agreement &1 | The short text describes the object sufficiently | ||
| 18 | &1-&2ID field is too long; a maximum of &3 characters is allowed | The short text describes the object sufficiently | ||
| 19 | Required ID & is missing | The short text describes the object sufficiently | ||
| 20 | Processing of item &1 &2 &3 was canceled | The short text describes the object sufficiently | ||
| 21 | Processing of item & was stopped | The short text describes the object sufficiently | ||
| 22 | Unit of measurement ISO code & is unknown | The short text describes the object sufficiently | ||
| 23 | The corresponding vendor ID of product & could not be determined | The short text describes the object sufficiently | ||
| 24 | Scheduling agreement &(&) pertains to the material & instead of & | The short text describes the object sufficiently | ||
| 25 | Processing of message & canceled; message does not contain valid items | The short text describes the object sufficiently | ||
| 26 | Processing of message & canceled; header is invalid | The short text describes the object sufficiently | ||
| 27 | No valid values found for the current selection | The short text describes the object sufficiently | ||
| 28 | Header of message & could not be saved in the database | The short text describes the object sufficiently | ||
| 29 | Item & could not be saved in the database | The short text describes the object sufficiently | ||
| 30 | Internal material ID for customer ID & not found | The short text describes the object sufficiently | ||
| 31 | Unable to determine replenishment strategy for item & | The short text describes the object sufficiently | ||
| 32 | Replenishment processing of all items in message & failed | The short text describes the object sufficiently | ||
| 33 | Replenishment processing of item & failed | The short text describes the object sufficiently | ||
| 34 | Execution of business logic failed; no outbound message was sent | The short text describes the object sufficiently | ||
| 35 | Sending of outbound PROACT message failed | The short text describes the object sufficiently | ||
| 36 | Mandatory & information is missing | The short text describes the object sufficiently | ||
| 37 | Mandatory timestamp & is missing | The short text describes the object sufficiently | ||
| 38 | & internal ID and buyer ID not specified | The short text describes the object sufficiently | ||
| 39 | & internal ID not specified | The short text describes the object sufficiently | ||
| 40 | & buyer ID not specified | The short text describes the object sufficiently | ||
| 41 | & vendor ID not specified | The short text describes the object sufficiently | ||
| 42 | & unit of measurement is not specified | The short text describes the object sufficiently | ||
| 43 | Received message does not contain a message ID | The short text describes the object sufficiently | ||
| 44 | Building header for message ID & | The short text describes the object sufficiently | ||
| 45 | Building internal mapping of product & | The short text describes the object sufficiently | ||
| 46 | Calculating replenishment proposal for product & (replenish to maximum) | The short text describes the object sufficiently | ||
| 47 | Calculating replenishment proposal for product & (replenish to minimum) | The short text describes the object sufficiently | ||
| 48 | Calculating replenishment proposal for product & (custom algorithm) | The short text describes the object sufficiently | ||
| 49 | Stop indicator of item & was set | The short text describes the object sufficiently | ||
| 50 | Time zone determination failed for scheduling agreement & | The short text describes the object sufficiently | ||
| 51 | Error during delivery schedule creation for agreement &1 item &2 | The short text describes the object sufficiently | ||
| 52 | Unable to lock message ID &1 in the database | The short text describes the object sufficiently | ||
| 53 | Unable to lock message ID &1 item ID &2 in the database | The short text describes the object sufficiently | ||
| 54 | Unable to lock message ID &1 item ID &2 time series type &3 in database | The short text describes the object sufficiently | ||
| 55 | Foreign lock set in database | The short text describes the object sufficiently | ||
| 56 | Internal error during database locking | The short text describes the object sufficiently | ||
| 57 | System failure during database locking | The short text describes the object sufficiently | ||
| 58 | Sales document type &1 is not allowed | Space: object requires documentation | ||
| 59 | Unable to build record object of message ID &1 | The short text describes the object sufficiently | ||
| 60 | Unable to build item object of material ID &1 | The short text describes the object sufficiently | ||
| 61 | Unable to build time series object type &1 for material ID &2 | The short text describes the object sufficiently | ||
| 62 | Error in BAdI &1 | The short text describes the object sufficiently | ||
| 63 | No BAdI implementation exists for BAdI &1 | Space: object requires documentation | ||
| 64 | Message processing canceled; all items of message &1 have been rejected | The short text describes the object sufficiently | ||
| 65 | Outbound PROACT message (&1) has been sent successfully | The short text describes the object sufficiently | ||
| 66 | Item &1 vbeln: &3 posnr: &4 removed from &2 processing queue | The short text describes the object sufficiently | ||
| 67 | Status of prev.reported item &1 &3 &4 from message &2 set to obsolete | The short text describes the object sufficiently | ||
| 68 | Failed to raise alert &1; alert category is unknown | The short text describes the object sufficiently | ||
| 69 | Failed to raise alert &1; no recipients have been specified | The short text describes the object sufficiently | ||
| 70 | Failed to raise alert &1; unknown destination | The short text describes the object sufficiently | ||
| 71 | Failed to raise alert &1; communication failure | The short text describes the object sufficiently | ||
| 72 | Failed to raise alert &1; system failure | The short text describes the object sufficiently | ||
| 73 | Successfully raised alert &1 | The short text describes the object sufficiently | ||
| 74 | A newer report of item &1 exists on the database (MessageID &2) | The short text describes the object sufficiently | ||
| 75 | Several profiles exist for &1; &2; &3; active='&4' | The short text describes the object sufficiently | ||
| 76 | Scheduling agreement &1 item &2 is SMI relevant | The short text describes the object sufficiently | ||
| 77 | Customer material in Customizing and scheduling agreement differ | Space: object requires documentation | ||
| 78 | Customer plant in Customizing and scheduling agreement differ | Space: object requires documentation | ||
| 79 | Unable to convert unit of measurement '&1' into the internal format | The short text describes the object sufficiently | ||
| 80 | Unable to convert quantity field without data loss | The short text describes the object sufficiently | ||
| 81 | &1: &2: exception during quantity conversion | The short text describes the object sufficiently | ||
| 82 | No authority to change the scheduling agreement &1 | The short text describes the object sufficiently | ||
| 83 | Unit of measurement &1 does not correspond to sales unit &2 | The short text describes the object sufficiently | ||
| 84 | Error during verfication of timeseries type '&1' | The short text describes the object sufficiently | ||
| 85 | Minimum limit is greater than maximum limit | The short text describes the object sufficiently | ||
| 86 | Unit of Measurements &1 and &2 are not equal | The short text describes the object sufficiently | ||
| 87 | Negative quantity not allowed in field &1 | The short text describes the object sufficiently | ||
| 88 | Invalid period in time series type &1 | Space: object requires documentation | ||
| 89 | &1 : unit of measurement is missing for quantity report | The short text describes the object sufficiently | ||
| 90 | Limits of item &1 have changed since the last item report | The short text describes the object sufficiently | ||
| 91 | Please select only one item. | The short text describes the object sufficiently | ||
| 92 | Scheduling agreement &1 &2 has a planning DS instruction assigned | Space: object requires documentation | ||
| 93 | Scheduling agreement &1 &2 has setup a deviation tolerance check | Space: object requires documentation | ||
| 94 | Please enter a value >= 0 | The short text describes the object sufficiently | ||
| 95 | Message ID &1 for Customer &2 deleted | The short text describes the object sufficiently | ||
| 96 | Started manual processing of item &1 vbeln: &3 posnr: &4 in message &2 | The short text describes the object sufficiently | ||
| 97 | End of manual processing of item &1 vbeln: &3 posnr: &4 in message &2 | The short text describes the object sufficiently | ||
| 98 | Building item report for outbound service: Item &1 &3 &4 of message &2 | The short text describes the object sufficiently | ||
| 99 | Using profile &1 for item &2 vbeln &3 posnr &4 | The short text describes the object sufficiently | ||
| 100 | Reference doc &1 item &2 deviates from scheduling agreement data | Space: object requires documentation | ||
| 101 | Any changes to the item have been reset to the last saved state | The short text describes the object sufficiently | ||
| 102 | ForecastDeliverySchedule has been created and item has been saved. | The short text describes the object sufficiently | ||
| 103 | Item is currently marked as "obsolete". Please create the FDS first | The short text describes the object sufficiently | ||
| 104 | Replenishment logic has not been executed. Please create a FDS first | The short text describes the object sufficiently | ||
| 105 | Item has been reported in a previous message. Please create a FDS first | The short text describes the object sufficiently | ||
| 106 | Item has been saved | The short text describes the object sufficiently | ||
| 107 | Replenishment proposal has been calculated | The short text describes the object sufficiently | ||
| 108 | Replenishment simulation has been executed | The short text describes the object sufficiently | ||
| 109 | Parameters missing when calling Application. XMLGUID:&1 Mat.:&2 Doc.:&3 | The short text describes the object sufficiently | ||
| 110 | Enter only values with a maximum of &1 decimal(s) | The short text describes the object sufficiently | ||
| 111 | Processing of message &1 and all contained items was canceled. | The short text describes the object sufficiently | ||
| 112 | Maximum value for timeseries quantity violated | The short text describes the object sufficiently | ||
| 113 | Safety quantity field has been cleared | Space: object requires documentation |
History
| Last changed on/by | 20100310 | SAP | |
| SAP Release Created in | 604 |