Id | Title |
---|---|
VSMI001 | More than one info record exists for customer &1 and material &2 |
VSMI002 | Internal error in &1 with &2 &3 &4 |
VSMI003 | Required parameters where not filled by caller &1 |
VSMI004 | Table entry not found in table &1 |
VSMI005 | Active profiles &4 exist for &1 &2 &3; activation not possible |
VSMI006 | No active profile found &1 &2 &3 |
VSMI007 | Several applicable active profiles found for item & |
VSMI008 | No sales scheduling agreement found for &1 &2 &3 |
VSMI009 | Violation of the maximum stock level |
VSMI010 | Violation of the minimum stock level |
VSMI011 | Specify at least one of the profile fields &1 &2 &3 |
VSMI012 | No server group found for RFC processing |
VSMI013 | Maximum number of delivery schedules reached for &1 &2 |
VSMI014 | ARRAY op error: DB table=&1, op=&2, rc=&3, lines=&4 |
VSMI015 | Tolerances violated in period &1 of profile &2 |
VSMI016 | No delivery schedules allowed for scheduling agreement &1 |
VSMI017 | &1-&2ID field is too long; a maximum of &3 characters is allowed |
VSMI018 | Required ID & is missing |
VSMI019 | Processing of item &1 &2 &3 was canceled |
VSMI020 | Processing of item & was stopped |
VSMI021 | Unit of measurement ISO code & is unknown |
VSMI022 | The corresponding vendor ID of product & could not be determined |
VSMI023 | Scheduling agreement &(&) pertains to the material & instead of & |
VSMI024 | Processing of message & canceled; message does not contain valid items |
VSMI025 | Processing of message & canceled; header is invalid |
VSMI026 | No valid values found for the current selection |
VSMI027 | Header of message & could not be saved in the database |
VSMI028 | Item & could not be saved in the database |
VSMI029 | Internal material ID for customer ID & not found |
VSMI030 | Unable to determine replenishment strategy for item & |
VSMI031 | Replenishment processing of all items in message & failed |
VSMI032 | Replenishment processing of item & failed |
VSMI033 | Execution of business logic failed; no outbound message was sent |
VSMI034 | Sending of outbound PROACT message failed |
VSMI035 | Mandatory & information is missing |
VSMI036 | Mandatory timestamp & is missing |
VSMI037 | & internal ID and buyer ID not specified |
VSMI038 | & internal ID not specified |
VSMI039 | & buyer ID not specified |
VSMI040 | & vendor ID not specified |
VSMI041 | & unit of measurement is not specified |
VSMI042 | Received message does not contain a message ID |
VSMI043 | Building header for message ID & |
VSMI044 | Building internal mapping of product & |
VSMI045 | Calculating replenishment proposal for product & (replenish to maximum) |
VSMI046 | Calculating replenishment proposal for product & (replenish to minimum) |
VSMI047 | Calculating replenishment proposal for product & (custom algorithm) |
VSMI048 | Stop indicator of item & was set |
VSMI049 | Time zone determination failed for scheduling agreement & |
VSMI050 | Error during delivery schedule creation for agreement &1 item &2 |
VSMI051 | Unable to lock message ID &1 in the database |
VSMI052 | Unable to lock message ID &1 item ID &2 in the database |
VSMI053 | Unable to lock message ID &1 item ID &2 time series type &3 in database |
VSMI054 | Foreign lock set in database |
VSMI055 | Internal error during database locking |
VSMI056 | System failure during database locking |
VSMI057 | Sales document type &1 is not allowed |
VSMI058 | Unable to build record object of message ID &1 |
VSMI059 | Unable to build item object of material ID &1 |
VSMI060 | Unable to build time series object type &1 for material ID &2 |
VSMI061 | Error in BAdI &1 |
VSMI062 | No BAdI implementation exists for BAdI &1 |
VSMI063 | Message processing canceled; all items of message &1 have been rejected |
VSMI064 | Outbound PROACT message (&1) has been sent successfully |
VSMI065 | Item &1 vbeln: &3 posnr: &4 removed from &2 processing queue |
VSMI066 | Status of prev.reported item &1 &3 &4 from message &2 set to obsolete |
VSMI067 | Failed to raise alert &1; alert category is unknown |
VSMI068 | Failed to raise alert &1; no recipients have been specified |
VSMI069 | Failed to raise alert &1; unknown destination |
VSMI070 | Failed to raise alert &1; communication failure |
VSMI071 | Failed to raise alert &1; system failure |
VSMI072 | Successfully raised alert &1 |
VSMI073 | A newer report of item &1 exists on the database (MessageID &2) |
VSMI074 | Several profiles exist for &1; &2; &3; active='&4' |
VSMI075 | Scheduling agreement &1 item &2 is SMI relevant |
VSMI076 | Customer material in Customizing and scheduling agreement differ |
VSMI077 | Customer plant in Customizing and scheduling agreement differ |
VSMI078 | Unable to convert unit of measurement '&1' into the internal format |
VSMI079 | Unable to convert quantity field without data loss |
VSMI080 | &1: &2: exception during quantity conversion |
VSMI081 | No authority to change the scheduling agreement &1 |
VSMI082 | Unit of measurement &1 does not correspond to sales unit &2 |
VSMI083 | Error during verfication of timeseries type '&1' |
VSMI084 | Minimum limit is greater than maximum limit |
VSMI085 | Unit of Measurements &1 and &2 are not equal |
VSMI086 | Negative quantity not allowed in field &1 |
VSMI087 | Invalid period in time series type &1 |
VSMI088 | &1 : unit of measurement is missing for quantity report |
VSMI089 | Limits of item &1 have changed since the last item report |
VSMI090 | Please select only one item. |
VSMI091 | Scheduling agreement &1 &2 has a planning DS instruction assigned |
VSMI092 | Scheduling agreement &1 &2 has setup a deviation tolerance check |
VSMI093 | Please enter a value >= 0 |
VSMI094 | Message ID &1 for Customer &2 deleted |
VSMI095 | Started manual processing of item &1 vbeln: &3 posnr: &4 in message &2 |
VSMI096 | End of manual processing of item &1 vbeln: &3 posnr: &4 in message &2 |
VSMI097 | Building item report for outbound service: Item &1 &3 &4 of message &2 |
VSMI098 | Using profile &1 for item &2 vbeln &3 posnr &4 |
VSMI099 | Reference doc &1 item &2 deviates from scheduling agreement data |
VSMI100 | Any changes to the item have been reset to the last saved state |