PPE4 - Nachrichten aus dem Einstiegsobjekt des iPPE
The following messages are stored in message class PPE4: Nachrichten aus dem Einstiegsobjekt des iPPE.
It is part of development package CPPEHDR in software component AP-PPE. This development package consists of objects that can be grouped under "Access Object for iPPE".
It is part of development package CPPEHDR in software component AP-PPE. This development package consists of objects that can be grouped under "Access Object for iPPE".
Message Nr ▲ | Message Text |
|---|---|
| 000 | ##################### General Messages ################################# |
| 001 | Module will be replaced |
| 002 | An internal error occurred |
| 003 | System locking error |
| 004 | Internal error in iPPE access object; see long text |
| 100 | Source of supply is still being used in orders |
| 101 | &1 &2 is not maintained in &3 &4 |
| 102 | &1 &2 is not maintained |
| 103 | Breakdown of &1 &2 in variant &3 is not maintained |
| 104 | iPPE access was not clearly identified |
| 105 | No changes have been made to the iPPE accesses |
| 106 | No decomposition is possible using alternative &1 at &2 node |
| 107 | Line &1 is not maintained for &3 &2 |
| 108 | Decomposition of &4 &3 is not possible using alternative &1 at node &2 |
| 109 | Alternative &1 does not exist at line &2 |
| 110 | Decomposition of &4 &3 is not possible using alternative &1 at variant &2 |
| 111 | Alternative &1 does not exist at this object |
| 112 | You must enter an alternative for assembly structures |
| 113 | Decomposition of &4 &3 is not possible using variant &2 at node &1 |
| 114 | Variant &1 does not exist |
| 115 | Node &1 does not exist |
| 116 | Node &1 for class &2 of class type &3 does not exist |
| 117 | Access is contained in the production version. Deletion not possible |
| 118 | This entry is used as a template and cannot be deleted |
| 119 | Mode &2 at activity &1 has not been maintained for the &3 &4 |
| 120 | &1 &2 does not exist in &3 &4 |
| 121 | Access already exists at node &1 &2 for variant &3 |
| 122 | &2 already exists for the external key &1 |
| 123 | No iPPE access object exists for &1 |
| 124 | An access already exists in iPPE for &1 |
| 125 | &1 and &2 must be specified |
| 126 | No iPPE access object exists for this external key |
| 127 | An iPPE access object already exists for the external key &1 |
| 128 | The iPPE access has been deleted |
| 129 | The iPPE access has been saved |
| 130 | &1 &2 does not exist |
| 131 | Error when creating or changing the production version |
| 132 | The end must not lie before the start |
| 133 | Maximum value must be greater than the minimum value |
| 134 | Error has occurred while reading the production version |
| 135 | Field &1 is not filled |
| 136 | Field &1 for object &2 is not filled |
| 137 | Combination of values &1/&2/&3 in the access is not valid |
| 138 | Object &1 from structure &2 does not match structure &3 |
| 139 | You must create the access at an alternative |
| 140 | Enter the usage of the access |
| 141 | Customizing is missing for the access usage (view &1) |
| 142 | Access type &1 is not valid |
| 143 | Access usage '&1' is invalid |
| 144 | Customizing settings do not permit combination &1/&2 |
| 145 | Access is already being edited by &1 |
| 146 | Enter a process structure |
| 147 | Enter a line structure |
| 148 | You must not enter a line structure for this process structure |
| 149 | Co-product and primary product are equal |
| 150 | Co-product and primary product belong to different nodes |
| 151 | No primary product found |
| 152 | You cannot maintain a co-product at these node due to Customizing |
| 153 | This &1 is still being used in requests |
| 154 | The access &1 is being used in the model mix &2 |
| 155 | Error deleting production version |
| 156 | Incorrect input data in module &1 &2 &3 |
| 157 | Access (&1) already exists with other ID (&2) |
| 158 | Change from &1 not possible as at least one access is maintained |
| 159 | The iPPE access &1 was saved |
| 160 | The iPPE access &1 was deleted |
| 161 | The iPPE access &1 will be created/changed when you next save |
| 162 | The iPPE access &1 will be deleted when you next save |
| 163 | Invalid time stamp change during runtime |
| 164 | There is no released time stamp for iPPE access &1 |
| 165 | &1 &2 already exists |
| 166 | &1 iPPE accesses are unchecked and unusable for operational activities |
| 167 | &1 time stamp of check for iPPE access objects will be deleted |
| 168 | Please fill in all entry fields for the by-product |
| 169 | Select a line |
| 170 | Mark a row that is not a template |
| 171 | The usage '&1' cannot be used with the access type '&2' |
| 172 | The scrap must be less than 100% |
| 173 | Action not possible as there are dependent access objects |
| 174 | The usage &3 &1 cannot be used with &2 |
| 175 | No &1 found |
| 176 | The field '&1' for object &2 must not be filled |
| 177 | &1 is still being used in &1 &2; the link must first be deleted |
| 178 | Assignment of process or line structure not allowed for Demand Planning |
| 179 | Demand Planning only allowed with assembly |
| 180 | Variant contains fixed quantities and cannot be assigned to any &1 |
| 181 | Reference to &1 of this type is not allowed |
| 182 | Validity period of &1 missing |
| 183 | Error determining routing type |
| 184 | Cost profile only allowed with SNP routing for &1 |
| 185 | &2 and &3 must be consistent for references between &1 |
| 186 | Select at least one line with &1 |
| 187 | The description &1 is already being used |
| 188 | You cannot execute this action before changes have been saved |
| 189 | Cost profile &1 does not exist |
| 190 | No PDS found |
| 191 | &1 is a key in a planning matrix and cannot be deleted |
| 192 | &1 is not a routing header. Assignment to a &2 is not possible |
| 193 | &1 &2 is not valid for Demand Planning |
| 194 | Processing of the &1 &2/&3/&4 was started |
| 195 | You cannot maintain a &1 in this system environment |
| 196 | &1 &2 is being archived and cannot be used |
| 200 | The production version &1/&2/&3 is not valid for date &4 |
| 201 | The production version &1/&2/&3 is locked (Lock &4) |
| 202 | Status '1' on production version &1/&2/&3 is not allowed |
| 203 | Unallowed status change to production version &1/&2/&3 |
| 205 | Production version &1 still being used in orders |