M! - Update Check in LIS
The following messages are stored in message class M!: Update Check in LIS.
It is part of development package MCS in software component LO-LIS-DC. This development package consists of objects that can be grouped under "R/3 application development: Logistics Information Warehouse".
It is part of development package MCS in software component LO-LIS-DC. This development package consists of objects that can be grouped under "R/3 application development: Logistics Information Warehouse".
Message Nr ▲ | Message Text |
|---|---|
| 001 | This field must be used for billing |
| 002 | Caution: updating is only possible in specific circumstances |
| 003 | This field is not filled when a credit memo is requested |
| 004 | Client &1 has status 'not modifiable' |
| 005 | SAP System has status 'not modifiable' |
| 050 | ********** 050...099 reserved for general notifications ********** |
| 051 | &1: &2-&3 were not filled for event &4 |
| 052 | &1: &2-&3 were not built for event &4 |
| 053 | &1: Date &2-&3 were not filled for event &4 |
| 054 | &1: Date &2-&3 were not build for event &4 |
| 055 | &1: &2-&3 have been updated according to data transport |
| 056 | The summarization indicatior has not been set for field &1 |
| 057 | The summarization indicator has been set for field &1 |
| 058 | The characteristic &2 was not used |
| 059 | Checks of standard information structures can display warnings |
| 060 | &1: &2-&3 have not been filled by the source field and formula/program |
| 061 | &1: &2-&3 should be filled by a user exit |
| 062 | &1: &2-&3 has been built restrictively for event &4 |
| 063 | &1: Date &2-&3 is restrictively built for event &4 |
| 064 | &1: &2-&3 are updated according to data transport and conditions |
| 065 | Unit &1 should not be used as a key figure |
| 066 | You are using unit &1 and unit &2 in an info structure |
| 067 | &1: &2 is not filled for event &4 |
| 068 | &1: &2 is not set up for event &4 |
| 069 | &1: &2 is set up restrictively fro event &4 |
| 070 | &1: &2 &3 use SELECT |
| 071 | &1: &2 &3 use PERFORM |
| 072 | &1: &2 &3 use CALL FUNCTION |
| 073 | &1: The characteristic rules vary |
| 074 | &1: Cumulative update without summation indicator |
| 075 | &1: Update using data transport despite summation indicator |
| 076 | &1: &2 &3 uses IMPORT/EXPORT |
| 077 | The domain for field &1 has the output attribute 'Without +/- Sign' |
| 100 | ********** 100...124 reserved for application 04 (PPIS) ********** |
| 101 | &1: &2-&3 is not filled |
| 102 | Update rule for &1 &2 &4 does not exist, but exists for &3 |
| 103 | You are using MCAFVG, MCCOMP und MCKALK in an info structure |
| 104 | You are using unit &1 |
| 105 | &1: &2-&3 is updated for the period |
| 125 | ********** 125...149 reserved for application 03 (BCO) ********** |
| 126 | &1: Instead of using MCBEST-&2 use MCBEST-&3 |
| 127 | &1: MCBEST-&2 rather use a formula |
| 128 | You are using values from the storage location |
| 129 | &1: &2-&3 are updated only be event &4 |
| 130 | MCMSEG should not be accessed in the stock info structures |
| 200 | ********** 200...249 is reserved for application 01 (VIS) ********** |
| 201 | &1: Status fields &2-&3 have been changed without triggering &4 |
| 202 | &1: Conversion from &2 to &3 to &4 during set up is not possible |
| 203 | &1: Date &2-&3 is INITIAL as long as no other changes have been made |
| 204 | &1: Date &2-&3 is INITIAL as long as no other goods issue has been posted |
| 205 | &1: Date &2-&3 is INITIAL if the schedule line has not been confirmed |
| 206 | &1: Source field &2-&3 has not been filled for event VD |
| 207 | &1: Updating in unit &2 creates problems |
| 208 | &1: Updating with date field VDATU can be set up restrictively only |
| 209 | WARNING: Changing the statistics currency causes data inconsistency |