EJ - Formale Fehler bei ISU-IDocs
The following messages are stored in message class EJ: Formale Fehler bei ISU-IDocs.
It is part of development package EE00 in software component IS-U. This development package consists of objects that can be grouped under "IS-U: General (Domains and General Objects)".
It is part of development package EE00 in software component IS-U. This development package consists of objects that can be grouped under "IS-U: General (Domains and General Objects)".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Function module can only process one IDoc |
| 001 | Numerical field &2 contains non-numerical value or missing zeros (&1) |
| 002 | Field has initial value |
| 003 | Segment &1 can not be processed |
| 004 | Indicator must have value &1 (instead of being selected or empty) |
| 020 | Incorporation of IDocs from type: &1; IDoc number: &2 |
| 021 | Date: &1; time: &2 |
| 022 | ------------------------------------------------------------------------ |
| 023 | Parameter: &1; value: &2 |
| 030 | Order & changed, downtimes updated |
| 031 | Customer contacts for incident order & generated |
| 032 | Incident order & not updated, error: & |
| 033 | Error generating customer contacts for order & business partner & |
| 034 | Field contains invalid value & |
| 100 | A value appears double in field &1 |
| 101 | Available |
| 150 | Street route for meter reading unit &1 was changed successfully |
| 151 | Street route for meter reading unit &1 not (or only partially) changed |
| 152 | All sequences were incorporated |
| 153 | Error in one sequence: changes not carried out |
| 154 | Error in one or more sequences; changes partially carried out |
| 155 | Sequence: &1 |
| 200 | IDoc type &1, number &2: there were no valid sequences loaded |
| 250 | No entry in field & |
| 251 | &2 is an invalid entry for field &1 |