/ISDFPS/LM_PM_ADDON - Nachrichtenklasse f�r LM Erweiterungen des Equipments
The following messages are stored in message class /ISDFPS/LM_PM_ADDON: Nachrichtenklasse f�r LM Erweiterungen des Equipments.
It is part of development package /ISDFPS/LM_PM_ADDON in software component IS-DFS-LM. This development package consists of objects that can be grouped under "Enhancement for Line Maintenance in PM Area".
It is part of development package /ISDFPS/LM_PM_ADDON in software component IS-DFS-LM. This development package consists of objects that can be grouped under "Enhancement for Line Maintenance in PM Area".
Message Nr ▲ | Message Text |
|---|---|
| 001 | You are not authorized to start transaction &1 |
| 002 | Internal error; check input parameters for function module &1 |
| 003 | Internal error; input parameter &1 of module &2 contains an invalid value |
| 004 | You do not have authorization for this process |
| 098 | Could not read data for flight & |
| 099 | Function possible only for orders of type "flight" |
| 100 | Duplicate entries in table for month &1 and year &2; check your entries |
| 101 | Some or all rows are empty; check your entries |
| 102 | No status profile has been assigned yet; display is not possible |
| 103 | Identifier &1 is already being used by equipment &2 |
| 104 | Internal error calling up the classification system for the confign code |
| 105 | Customizing for configuration code for model ID &1 is not available |
| 106 | No database record found for site with key &1 |
| 107 | Fill in all required entry fields |
| 108 | Enter a model ID before you assign a configuration code |
| 110 | Internal error while generating the status pushbuttons |
| 111 | Cannot set status icon &1 |
| 117 | Mission & is not available |
| 118 | Flight &1: valuation for class &2 (cl.type &3) cannot be carried out |
| 119 | Model ID &: cannot determine class and class type |
| 120 | Maintain a responsible work center |
| 121 | Maintain the plant for the responsible work center |
| 122 | Work center &1 &2 is not available in the system |
| 123 | Order type &1 is not available in the system |
| 124 | Enter a reference object and a weapon system |
| 125 | Flight no. is missing |
| 126 | Flight &1 does not exist |
| 127 | Choose the correct function |
| 128 | Enter an equipment |
| 129 | Order type &1 is not a permitted order type for flights |
| 130 | Order was saved with number & |
| 131 | Identifier does not match equipment |
| 132 | No Customizing settings have been made in table &1 for model ID &2 |
| 133 | Error in configuration code class for model ID & |
| 134 | Flight data is inconsistent |
| 135 | System: status object does not exist |
| 136 | & |
| 137 | Change the model ID; check authorized configuration |
| 138 | Configuration code & has not been defined correctly; correct the value |
| 140 | Enter order number |
| 141 | Maintain the weapon system before the configuration code |
| 142 | Model ID does not match the current reference object |
| 143 | Enter reference object |
| 144 | Enter a description for the weapon system |
| 145 | Model ID (&1) does not match the model ID of the reference object (&2) |
| 146 | Error writing the flight to the buffer |
| 147 | Arrival date is before start date |
| 148 | Arrival time must be after the start time |
| 149 | Enter the equipment |
| 150 | No master equipment is available for key &1 |
| 151 | Deployment status for object number &1 could not be found |
| 152 | Technical status for object number &1 could not be found |
| 153 | No configuration code found for equipment &1 and device type &2 |
| 154 | MPO for material number &1 could not be found |
| 155 | Internal error; input parameter is initial |
| 156 | Cannot determine force element |
| 158 | External ID & is already being used in other flights |
| 159 | Operation could not be selected |
| 160 | Update indicator "&" is not supported |
| 161 | No data records were transferred! |
| 162 | A number of data records were transferred without an order number |
| 163 | A number of control records were transferred without an order number |
| 164 | An error occurred when expanding structure & |
| 165 | Flight &: Update for field & is ignored |
| 166 | Flight &: Control record for the data record missing |
| 167 | Flight &: Data record for control record is missing |
| 168 | Flight &: Order does not exist |
| 169 | Flight &: Order cannot be locked |
| 170 | Flight &: No value has been transferred for field & |
| 171 | Flight &: Order type & is not defined |
| 172 | Flight &: Maintenance plant & is not defined |
| 173 | Flight &: Work center & / & not defined |
| 174 | Flight &: WBS element & is not defined |
| 175 | Flight &: WBS element & cannot be used |
| 176 | Flight &: Weapon system & is not defined |
| 177 | Flight &: Equipment & is not defined |
| 178 | Flight &: Weapon system & does not match WS & of reference object & |
| 179 | Flight &: Reference object is inconsistent (equipment &, ident. &) |
| 180 | Flight &: Arrival date is before start date |
| 181 | Flight &: Arrival time is before start time |
| 182 | Flight &: Duplicate data records are ignored |
| 183 | Flight &: Identifier & is not defined |
| 184 | Flight &: Configuration code & for weapon system & not defined |
| 185 | Flight &: Configuration code & was entered without a weapon system |
| 186 | Flight &: PM order has not been saved |
| 187 | Flight &: WBS element & cannot be used (it will be ignored) |
| 188 | ** Test run ** data is not saved |
| 189 | Flight & does not exist. Changes not possible |
| 190 | Flight &: Error during UPDATE! RC=& |
| 191 | Flight &: Order already exists |
| 192 | Flight &: Order number used more than once (INSERT mode) |
| 193 | Flight &: Master equipment & is not defined |
| 194 | Flight &: Internal error occurred when reading data |
| 195 | Flight &: Target configuration code not correctly converted to attributes |
| 196 | Flight &: Order can no longer be changed (owing to status) |
| 197 | Flight &: force element &1 &2 &3 is not defined |
| 198 | Flight &: force element not specified |
| 199 | Flight &: Mission "&" is not defined |
| 200 | Update termination: order &1, update indicator &2 |
| 201 | Flight must be created using transaction /ISDFPS/LMFL01 |
| 202 | Force element & not defined or not valid |
| 203 | A new force element has been entered. Mission & will be reset |
| 204 | Combination of force element/mission is invalid |
| 205 | Specify a force element or mission |
| 206 | A new mission has been entered; force element & has been adjusted |
| 207 | Force element &1 cannot be used in conjunction with mission &2 |
| 208 | Flight &1: force element &2 cannot be used with mission &3 |
| 209 | Flight &1: force element &2 has been replaced by mission &3 |
| 210 | Top equipment &1 that has been determined is not master equipment |
| 211 | Cannot determine status profile for master equip. &1 for technical status |
| 212 | Technical status only possible in conjunction with technical object |
| 213 | Model ID changed. Target configuration code has been reset (previously &) |
| 214 | Object number for flight status for flight & could not be determined |
| 215 | Flight &: Flight status & cannot be saved (RC=&) |
| 216 | Flight &: Flight status object & cannot be saved (RC=&) |
| 217 | Invalid call! Function canceled |
| 218 | Flight &: No changes necessary |
| 219 | No technical status has been entered for the operation yet |
| 220 | Error in Customizing: More than one operational status is active |
| 221 | Notification/order with technical status; do not delete equipment |
| 222 | Master equipment (&1) in document differs from new master equipment (&2) |
| 223 | Maintenance order &1 does not have free status |
| 224 | Time zone & is not defined. Processing canceled |
| 225 | Status change not possible -> technical status active |
| 226 | Status change not possible for notif. &1 -> technical status active |
| 227 | For release, the order must have the status Opened |
| 228 | Enter the unit for the planned flight duration |
| 229 | Configuration code for weapon system ID & is incorrect |
| 230 | & is not a primary unit of measurement of "time" (-> input help) |
| 231 | & is not a time unit |
| 233 | Technical status for equipment &1 is locked by &2 |
| 234 | Technical status can be changed only for open and released operations |
| 235 | Technical status of master equipment &1 cannot be changed in this system |
| 236 | Enter a value in the "Deviation" field |
| 237 | Enter a value in the "Deviation Reason" field |
| 238 | Flight &: Enter a value in the "Deviation" field |
| 239 | Flight &1: Enter a value in the 'Deviation Reason" field |
| 240 | Flight &1: Deviation &2 is not defined |
| 241 | Flight &: deviation reason & is not defined |
| 242 | Enter the takeoff and landing dates for the flight |
| 243 | Flight leg must be specified within the basic dates of the flight |
| 244 | Flight leg overlaps with existing flight leg |
| 245 | The total planned flight time of the flight legs is too large |
| 250 | Central system is currently not reachable |
| 251 | Operation with technical status exists; delete operations individually |
| 252 | Configuration code for equipment not maintained |
| 253 | Planned flight time greater than difference between takeoff/landing date |
| 254 | Equipment &1 is not defined as master equipment |
| 255 | Assign master equipment |
| 256 | Equipment &1 has the status "Inactive" or "Flagged for Deletion" |
| 257 | Flight &1: Functional location &2 is not defined |
| 258 | Master equipment could not be determined |
| 260 | Cannot check measuring point & |
| 261 | Measuring point is not part of the structure |
| 262 | Measuring point & does not have a time format |
| 263 | Enter the required mandatory partners before you save the flight |
| 264 | No site equipment exists for key &1 |
| 270 | Subequipment cannot be master equipment |
| 271 | Functional location of equipment is not highest functional location |
| 272 | No master equipment can be generated from equipment &1 |
| 273 | Master equipment &1: Installation in equipment &2 is not permitted |
| 274 | Master equip. &1: Installation at functional location &2 is not permitted |
| 275 | Equipment &1 cannot be defined as master equipment |
| 276 | Assgmt to funct. location &1 not permitted due to installed master equip. |
| 280 | Technical status equipment &1 deviates from documents &2 |
| 898 | Technical status: status profile MOBIL (&1) and back end different (&2) |
| 899 | Mobile/back-end conflict with technical status of header |