VSMI - Message for Development Class VSMI
The following messages are stored in message class VSMI: Message for Development Class VSMI.
It is part of development package VSMI in software component SD-BF-SMI. This development package consists of objects that can be grouped under "".
It is part of development package VSMI in software component SD-BF-SMI. This development package consists of objects that can be grouped under "".
Message Nr ▲ | Message Text |
|---|---|
| 000 | & & & & |
| 001 | More than one info record exists for customer &1 and material &2 |
| 002 | Internal error in &1 with &2 &3 &4 |
| 003 | Required parameters where not filled by caller &1 |
| 004 | Table entry not found in table &1 |
| 005 | Active profiles &4 exist for &1 &2 &3; activation not possible |
| 006 | No active profile found &1 &2 &3 |
| 007 | Several applicable active profiles found for item & |
| 008 | No sales scheduling agreement found for &1 &2 &3 |
| 009 | Violation of the maximum stock level |
| 010 | Violation of the minimum stock level |
| 011 | Specify at least one of the profile fields &1 &2 &3 |
| 012 | No server group found for RFC processing |
| 013 | Maximum number of delivery schedules reached for &1 &2 |
| 014 | ARRAY op error: DB table=&1, op=&2, rc=&3, lines=&4 |
| 015 | Tolerances violated in period &1 of profile &2 |
| 016 | No delivery schedules allowed for scheduling agreement &1 |
| 017 | &1-&2ID field is too long; a maximum of &3 characters is allowed |
| 018 | Required ID & is missing |
| 019 | Processing of item &1 &2 &3 was canceled |
| 020 | Processing of item & was stopped |
| 021 | Unit of measurement ISO code & is unknown |
| 022 | The corresponding supplier ID of product & could not be determined |
| 023 | Scheduling agreement &(&) pertains to the material & instead of & |
| 024 | Processing of message & canceled; message does not contain valid items |
| 025 | Processing of message & canceled; header is invalid |
| 026 | No valid values found for the current selection |
| 027 | Header of message & could not be saved in the database |
| 028 | Item & could not be saved in the database |
| 029 | Internal material ID for customer ID & not found |
| 030 | Unable to determine replenishment strategy for item & |
| 031 | Replenishment processing of all items in message & failed |
| 032 | Replenishment processing of item & failed |
| 033 | Execution of business logic failed; no outbound message was sent |
| 034 | Sending of outbound PROACT message failed |
| 035 | Mandatory & information is missing |
| 036 | Mandatory timestamp & is missing |
| 037 | & internal ID and buyer ID not specified |
| 038 | & internal ID not specified |
| 039 | & buyer ID not specified |
| 040 | & supplier ID not specified |
| 041 | & unit of measurement is not specified |
| 042 | Received message does not contain a message ID |
| 043 | Building header for message ID & |
| 044 | Building internal mapping of product & |
| 045 | Calculating replenishment proposal for product & (replenish to maximum) |
| 046 | Calculating replenishment proposal for product & (replenish to minimum) |
| 047 | Calculating replenishment proposal for product & (custom algorithm) |
| 048 | Stop indicator of item & was set |
| 049 | Time zone determination failed for scheduling agreement & |
| 050 | Error during delivery schedule creation for agreement &1 item &2 |
| 051 | Unable to lock message ID &1 in the database |
| 052 | Unable to lock message ID &1 item ID &2 in the database |
| 053 | Unable to lock message ID &1 item ID &2 time series type &3 in database |
| 054 | Foreign lock set in database |
| 055 | Internal error during database locking |
| 056 | System failure during database locking |
| 057 | Sales document type &1 is not allowed |
| 058 | Unable to build record object of message ID &1 |
| 059 | Unable to build item object of material ID &1 |
| 060 | Unable to build time series object type &1 for material ID &2 |
| 061 | Error in BAdI &1 |
| 062 | No BAdI implementation exists for BAdI &1 |
| 063 | Message processing canceled; all items of message &1 have been rejected |
| 064 | Outbound PROACT message (&1) has been sent successfully |
| 065 | Item &1 vbeln: &3 posnr: &4 removed from &2 processing queue |
| 066 | Status of prev.reported item &1 &3 &4 from message &2 set to obsolete |
| 067 | Failed to raise alert &1; alert category is unknown |
| 068 | Failed to raise alert &1; no recipients have been specified |
| 069 | Failed to raise alert &1; unknown destination |
| 070 | Failed to raise alert &1; communication failure |
| 071 | Failed to raise alert &1; system failure |
| 072 | Successfully raised alert &1 |
| 073 | A newer report of item &1 exists on the database (MessageID &2) |
| 074 | Several profiles exist for &1; &2; &3; active='&4' |
| 075 | Scheduling agreement &1 item &2 is SMI relevant |
| 076 | Customer material in Customizing and scheduling agreement differ |
| 077 | Customer plant in Customizing and scheduling agreement differ |
| 078 | Unable to convert unit of measurement '&1' into the internal format |
| 079 | Unable to convert quantity field without data loss |
| 080 | &1: &2: exception during quantity conversion |
| 081 | No authority to change the scheduling agreement &1 |
| 082 | Unit of measurement &1 does not correspond to sales unit &2 |
| 083 | Error during verfication of timeseries type '&1' |
| 084 | Minimum limit is greater than maximum limit |
| 085 | Unit of Measurements &1 and &2 are not equal |
| 086 | Negative quantity not allowed in field &1 |
| 087 | Invalid period in time series type &1 |
| 088 | &1 : unit of measurement is missing for quantity report |
| 089 | Limits of item &1 have changed since the last item report |
| 090 | Please select only one item. |
| 091 | Scheduling agreement &1 &2 has a planning DS instruction assigned |
| 092 | Scheduling agreement &1 &2 has setup a deviation tolerance check |
| 093 | Please enter a value >= 0 |
| 094 | Message ID &1 for Customer &2 deleted |
| 095 | Started manual processing of item &1 vbeln: &3 posnr: &4 in message &2 |
| 096 | End of manual processing of item &1 vbeln: &3 posnr: &4 in message &2 |
| 097 | Building item report for outbound service: Item &1 &3 &4 of message &2 |
| 098 | Using profile &1 for item &2 vbeln &3 posnr &4 |
| 099 | Reference doc &1 item &2 deviates from scheduling agreement data |
| 100 | Any changes to the item have been reset to the last saved state |
| 101 | ForecastDeliverySchedule has been created and item has been saved. |
| 102 | Item is currently marked as "obsolete". Please create the FDS first |
| 103 | Replenishment logic has not been executed. Please create a FDS first |
| 104 | Item has been reported in a previous message. Please create a FDS first |
| 105 | Item has been saved |
| 106 | Replenishment proposal has been calculated |
| 107 | Replenishment simulation has been executed |
| 108 | Parameters missing when calling Application. XMLGUID:&1 Mat.:&2 Doc.:&3 |
| 109 | Enter only values with a maximum of &1 decimal(s) |
| 110 | Processing of message &1 and all contained items was canceled. |
| 111 | Maximum value for timeseries quantity violated |
| 112 | Safety quantity field has been cleared |