SAP ABAP Message Class PHIN (Phase In: Messages)
Basic Data
Hierarchy
☛
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
⤷
PM-EQM-THO (Application Component) Takeover/Handover of Technical Objects
⤷
PHIN (Package) Takeover/Handover of Technical Objects
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials⤷
PM-EQM-THO (Application Component) Takeover/Handover of Technical Objects⤷
PHIN (Package) Takeover/Handover of Technical Objects 
Attributes
| Message class |  |
PHIN |
| Short Description |  |
Phase In: Messages |
| Changed On |  |
20110908 |
| Last Changed At |  |
174947 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
Abend due to system error(&1 &2 &3 &4) | The short text describes the object sufficiently | |
| 2 | 001 |
You are not authorized to use handover profile &1 | The short text describes the object sufficiently | |
| 3 | 005 |
Handover for file &1 completed successfully | The short text describes the object sufficiently | |
| 4 | 006 |
Record &1 created successfully | The short text describes the object sufficiently | |
| 5 | 007 |
&1 document instance successfully created and added to the record | The short text describes the object sufficiently | |
| 6 | 008 |
URL instance successfully added to the record | The short text describes the object sufficiently | |
| 7 | 009 |
&1 document instance not created | The short text describes the object sufficiently | |
| 8 | 010 |
&1 document created but not added to the record | The short text describes the object sufficiently | |
| 9 | 011 |
Record &1 not created | The short text describes the object sufficiently | |
| 10 | 012 |
URL instance not added to the record | The short text describes the object sufficiently | |
| 11 | 013 |
&1 document instance created successfully | The short text describes the object sufficiently | |
| 12 | 014 |
Takeover table &1 does not exist | The short text describes the object sufficiently | |
| 13 | 015 |
Table PHINH; key &1 already exists | The short text describes the object sufficiently | |
| 14 | 016 |
Object &1 is already being processed by another user | The short text describes the object sufficiently | |
| 15 | 017 |
File &1 is already used/in use | The short text describes the object sufficiently | |
| 16 | 018 |
There is no material number or manufacturer part number in the file | The short text describes the object sufficiently | |
| 17 | 019 |
Error(s) occurred during handover of file &1; see error log in RMS | Space: object requires documentation | |
| 18 | 020 |
Functional location without hierarchy is not supported | The short text describes the object sufficiently | |
| 19 | 021 |
****** Messagelog for deactivation of equipments ********* | The short text describes the object sufficiently | |
| 20 | 022 |
****** Messagelog for deactivation of functional locations ********* | The short text describes the object sufficiently | |
| 21 | 023 |
****** Messagelog for deactivation of maintenance plans ********* | The short text describes the object sufficiently | |
| 22 | 024 |
****** Messagelog for status change of notifications ********* | The short text describes the object sufficiently | |
| 23 | 025 |
****** Messagelog for status change of pm/cs orders ********* | The short text describes the object sufficiently | |
| 24 | 026 |
*** &1 objects processed. *** | The short text describes the object sufficiently | |
| 25 | 027 |
****** Messagelog for completion and reopen ********* | The short text describes the object sufficiently | |
| 26 | 028 |
*** &1 objects activated. *** | The short text describes the object sufficiently | |
| 27 | 030 |
No structure exists for technical object &1 | The short text describes the object sufficiently | |
| 28 | 031 |
Error during conversion to XML; no output file created | The short text describes the object sufficiently | |
| 29 | 032 |
No handover profile defined; process is not continued | The short text describes the object sufficiently | |
| 30 | 033 |
Technical object must be the top hierarchy node | Space: object requires documentation | |
| 31 | 034 |
You are not authorized to use the handover application | Space: object requires documentation | |
| 32 | 035 |
&1 takeover executed successfully | The short text describes the object sufficiently | |
| 33 | 036 |
Locking error; &1 takeover failed | The short text describes the object sufficiently | |
| 34 | 037 |
&1 &2 is currently locked by user &3 | The short text describes the object sufficiently | |
| 35 | 038 |
&1 &2 created on &3 deleted from ToHo tables. | The short text describes the object sufficiently | |
| 36 | 039 |
Only one hierarchy with functional locations is allowed | Space: object requires documentation | |
| 37 | 100 |
&1:Timestamp assigned to target fields without conversion into local time | The short text describes the object sufficiently | |
| 38 | 101 |
&1: Timestamp could not be converted as specified time zone not available | Space: object requires documentation | |
| 39 | 102 |
Entry &1 does not exist in includes &2 or &3 (check entry) | Space: object requires documentation | |
| 40 | 103 |
Measurement time for &1 is not defined | The short text describes the object sufficiently | |
| 41 | 104 |
Measurement time/timestamp for &1 is not defined | The short text describes the object sufficiently | |
| 42 | 105 |
Document & with higher measurement time already entered | The short text describes the object sufficiently | |
| 43 | 106 |
Customizing table &1; external identification &2 not defined | The short text describes the object sufficiently | |
| 44 | 107 |
Customizing table &1; characteristic &2 to external ident &3 not defined | The short text describes the object sufficiently | |
| 45 | 108 |
Measuring point category is not defined in the takeover profile | Space: object requires documentation | |
| 46 | 109 |
Entry can not be saved. Definition is not complete | The short text describes the object sufficiently | |
| 47 | 110 |
Unit of measurement for measuring point characteristic & not defined | The short text describes the object sufficiently | |
| 48 | 111 |
Field name &1 already used | The short text describes the object sufficiently | |
| 49 | 112 |
Object number could not be found for technical object | The short text describes the object sufficiently | |
| 50 | 113 |
Document &1 for &2 already entered for the measurement time specified | The short text describes the object sufficiently | |
| 51 | 114 |
You are deleting default entries | The short text describes the object sufficiently | |
| 52 | 115 |
You do not have authorization to use the takeover application | Space: object requires documentation | |
| 53 | 116 |
Customizing table &1 not consistent; a field name appears more than once | Space: object requires documentation | |
| 54 | 117 |
Customizing table &1 must be empty. At least one entry is still defined | Space: object requires documentation | |
| 55 | 118 |
Include CI_PHINT does not exist | The short text describes the object sufficiently | |
| 56 | 119 |
No component is defined in CI_PHINT | The short text describes the object sufficiently | |
| 57 | 120 |
Field &1 does not exist in the include CI_PHINT | The short text describes the object sufficiently | |
| 58 | 121 |
&1 technical objects successfully updated | The short text describes the object sufficiently | |
| 59 | 122 |
Please select the fields to be copied | The short text describes the object sufficiently | |
| 60 | 123 |
Transaction cannot be started in client &1 | The short text describes the object sufficiently | |
| 61 | 124 |
No authorization for authorization object &1 | The short text describes the object sufficiently | |
| 62 | 125 |
Default characteristics are already copied from client &1 | The short text describes the object sufficiently | |
| 63 | 126 |
New default characteristics will be added from client &1 | The short text describes the object sufficiently | |
| 64 | 127 |
Please select more than one item to be updated | Space: object requires documentation | |
| 65 | 128 |
Measuring point in 'Transfer of' field cannot be determined automatically | Space: object requires documentation | |
| 66 | 129 |
Manually assign a transfer relationship equivalent to the template | Space: object requires documentation | |
| 67 | 130 |
Meas. point &1 in 'Transfer of' field cannot be determined automatically | Space: object requires documentation | |
| 68 | 131 |
Manually assign a transfer relationship equivalent to the template | Space: object requires documentation | |
| 69 | 132 |
Measuring point in template ignored; characteristic &1 already used | Space: object requires documentation | |
| 70 | 200 |
Update terminated in table & | The short text describes the object sufficiently | |
| 71 | 201 |
Insert terminated in table & | Space: object requires documentation | |
| 72 | 202 |
Delete terminated in table & | The short text describes the object sufficiently | |
| 73 | 300 |
Error while activating maintenance plan &; scheduling not possible | The short text describes the object sufficiently | |
| 74 | 301 |
Maint. plan &1: start counter reading &2 < actual counter reading &3 | The short text describes the object sufficiently | |
| 75 | 302 |
MP &3: Cycle start date &1 before instal. date &2 | The short text describes the object sufficiently | |
| 76 | 303 |
MP &4 Start date/time &1 &2 bef. inst date &3 | The short text describes the object sufficiently | |
| 77 | 304 |
Maintenance plan & manually created | The short text describes the object sufficiently | |
| 78 | 305 |
Maintenance plan & manually scheduled | The short text describes the object sufficiently | |
| 79 | 306 |
&1 &2 : counter needed for copying maintenance plan &3 is missing | The short text describes the object sufficiently | |
| 80 | 307 |
Enqueue for takeover/handover table not possible | The short text describes the object sufficiently | |
| 81 | 308 |
Maintenance plan &1 contains items for different objects | Space: object requires documentation | |
| 82 | 309 |
Status check; maintenance plan & active | The short text describes the object sufficiently | |
| 83 | 310 |
Status check; maintenance plan & inactive | The short text describes the object sufficiently | |
| 84 | 311 |
Status check; maintenance plan & scheduled | The short text describes the object sufficiently | |
| 85 | 312 |
Status check; maintenance plan & not scheduled | The short text describes the object sufficiently | |
| 86 | 313 |
No maintenance plans were created. | Space: object requires documentation | |
| 87 | 314 |
Activation not possible. Maintenance plan &1 is still locked | The short text describes the object sufficiently | |
| 88 | 315 |
Deactivation not possible. Maintenance plan &1 is still locked | The short text describes the object sufficiently | |
| 89 | 316 |
Maint. plan &1: No cntr readg for meas. point &2 before installation date | The short text describes the object sufficiently | |
| 90 | 317 |
Equipment &1: no maintenance plans found | The short text describes the object sufficiently | |
| 91 | 318 |
Functional location &1: no maintenance plans found | The short text describes the object sufficiently | |
| 92 | 319 |
For the specified line, no copy reference has been maintained | The short text describes the object sufficiently | |
| 93 | 320 |
Internal message: &1 &2: OBJNR missing for copying maintenance plan &3 | Space: object requires documentation | |
| 94 | 321 |
Enter a valid start counter reading for maint. plan &1: value &2 reset | The short text describes the object sufficiently | |
| 95 | 322 |
Creation of maint.plans via MPD failed->will be created from 'copy ref.' | The short text describes the object sufficiently | |
| 96 | 323 |
No maintenance plans were found | The short text describes the object sufficiently | |
| 97 | 324 |
MP &1 No countr readg entered yet for measrg point &2 unit &3 | The short text describes the object sufficiently | |
| 98 | 334 |
The short text describes the object sufficiently | ||
| 99 | 400 |
*** "Generation of Technical Objects" related messages *** | The short text describes the object sufficiently | |
| 100 | 401 |
Equipment &1 (&2/&3) successfully created | The short text describes the object sufficiently | |
| 101 | 402 |
Equipment BOM header data successfully created for equipment &1 | The short text describes the object sufficiently | |
| 102 | 403 |
Equipment BOM item &1 with qty &2 &3 successfully created for equi &4 | The short text describes the object sufficiently | |
| 103 | 404 |
Equipment &1 (&2/&3) successfully updated | The short text describes the object sufficiently | |
| 104 | 405 |
Creation of equipment (&1/&2) failed | The short text describes the object sufficiently | |
| 105 | 406 |
Update of equipment &1 (&2/&3) failed | The short text describes the object sufficiently | |
| 106 | 407 |
Installation of equipment &1 failed | The short text describes the object sufficiently | |
| 107 | 408 |
Removal of equipment &1 failed | The short text describes the object sufficiently | |
| 108 | 409 |
Installation of non-serialized material &1 failed | The short text describes the object sufficiently | |
| 109 | 410 |
Removal of non-serialized material &1 failed | The short text describes the object sufficiently | |
| 110 | 411 |
No installation location; equipment cannot be installed | The short text describes the object sufficiently | |
| 111 | 412 |
Equipment has already been assigned to superior object | The short text describes the object sufficiently | |
| 112 | 413 |
No superior object; equipment cannot be removed | The short text describes the object sufficiently | |
| 113 | 414 |
Equipment &1 has been changed; update is required | The short text describes the object sufficiently | |
| 114 | 415 |
Equipment BOM item &1 has been changed; update is required | The short text describes the object sufficiently | |
| 115 | 416 |
Material number must not be changed; update not possible | The short text describes the object sufficiently | |
| 116 | 417 |
Serial number must not be changed; update not possible | The short text describes the object sufficiently | |
| 117 | 418 |
Equipment number must not be changed; update not possible | The short text describes the object sufficiently | |
| 118 | 419 |
No installation location; material cannot be installed | The short text describes the object sufficiently | |
| 119 | 420 |
Material has been already assigned to superior object | The short text describes the object sufficiently | |
| 120 | 421 |
No superior object; BOM item cannot be removed | The short text describes the object sufficiently | |
| 121 | 422 |
BOM Item &1 successfully created in equipment BOM &2 (&3) | The short text describes the object sufficiently | |
| 122 | 423 |
BOM Item &1 has not been created in equipment BOM &2 (&3) | The short text describes the object sufficiently | |
| 123 | 424 |
BOM Item &1 successfully updated in equipment BOM &2 (&3) | The short text describes the object sufficiently | |
| 124 | 425 |
BOM Item &1 has not been updated in equipment BOM &2 (&3) | The short text describes the object sufficiently | |
| 125 | 426 |
Functional location &1 succesfully created | The short text describes the object sufficiently | |
| 126 | 427 |
Creation of functional location &1 failed | The short text describes the object sufficiently | |
| 127 | 428 |
Functional location &1 succesfully updated | The short text describes the object sufficiently | |
| 128 | 429 |
Update of functional location &1 failed | The short text describes the object sufficiently | |
| 129 | 430 |
*** "Consistency Check of Technical Objects" related messages *** | The short text describes the object sufficiently | |
| 130 | 431 |
Equipment cannot be created | The short text describes the object sufficiently | |
| 131 | 432 |
Material &1 does not exist | The short text describes the object sufficiently | |
| 132 | 433 |
Material &1 is not a serialized material. Serial profile is missing. | The short text describes the object sufficiently | |
| 133 | 434 |
Material &1 is a serialized material and cannot be used in the equi BOM | The short text describes the object sufficiently | |
| 134 | 435 |
Equipment &1 (&2/&3) does not exist | The short text describes the object sufficiently | |
| 135 | 436 |
Equipment BOM item cannot be created | The short text describes the object sufficiently | |
| 136 | 437 |
'Copy reference' equipment has not been found | The short text describes the object sufficiently | |
| 137 | 438 |
Inst. location cannot be changed if equipment has not been created | The short text describes the object sufficiently | |
| 138 | 439 |
'Copy reference' equipment (&1) does not exist; check your entries | The short text describes the object sufficiently | |
| 139 | 440 |
Parent object has not been created yet | The short text describes the object sufficiently | |
| 140 | 441 |
Record is incomplete. Maintain material, serial number, or equipment | The short text describes the object sufficiently | |
| 141 | 442 |
Consistency check has been performed successfully; update allowed | The short text describes the object sufficiently | |
| 142 | 443 |
Consistency check has failed. Equipment &1 cannot be updated | The short text describes the object sufficiently | |
| 143 | 444 |
Consistency check has been performed successfully; creation allowed | The short text describes the object sufficiently | |
| 144 | 445 |
Consistency check has failed; equipment cannot be created | The short text describes the object sufficiently | |
| 145 | 446 |
Consistence check has not yet been carried out | The short text describes the object sufficiently | |
| 146 | 447 |
'Copy reference' equipment &1 will be used for equipment creation | The short text describes the object sufficiently | |
| 147 | 448 |
'Copy reference' equipment could not be determined for the selected line | The short text describes the object sufficiently | |
| 148 | 449 |
Complete your entries and execute consistency check | The short text describes the object sufficiently | |
| 149 | 450 |
'Copy reference' equipment &1 does not exist; check your entries | The short text describes the object sufficiently | |
| 150 | 451 |
Ref. equipment BOM item for material &1 and FID &2 has not been found | The short text describes the object sufficiently | |
| 151 | 452 |
Ref. equi BOM item (&1/&2) has been found and will be used for creation | The short text describes the object sufficiently | |
| 152 | 453 |
Installation location has been changed from &1 to original value &2 | Space: object requires documentation | |
| 153 | 454 |
Serial number has not been specified. Maintain serial number | The short text describes the object sufficiently | |
| 154 | 455 |
BOM item &1 of &2 (&3) has not been changed. No action required. | The short text describes the object sufficiently | |
| 155 | 456 |
Material &1 is not serialized material | The short text describes the object sufficiently | |
| 156 | 457 |
Enter equipment category or 'copy reference' equipment | The short text describes the object sufficiently | |
| 157 | 458 |
Equipment will be created with the minimum of data | Space: object requires documentation | |
| 158 | 459 |
Functional location &1 does not exist | The short text describes the object sufficiently | |
| 159 | 460 |
Functional location &1 exists in ERP System | The short text describes the object sufficiently | |
| 160 | 461 |
Functional location &1 is not installed in &2 as recorded in takeover | The short text describes the object sufficiently | |
| 161 | 462 |
Object &1 &2 has been changed and must be updated | The short text describes the object sufficiently | |
| 162 | 463 |
Object &1 &2 must be created | The short text describes the object sufficiently | |
| 163 | 464 |
Functional location &1 must not be installed in a piece of equipment | The short text describes the object sufficiently | |
| 164 | 465 |
Copy reference for functional location found; &1 | The short text describes the object sufficiently | |
| 165 | 466 |
Not able to find copy reference for functional location | The short text describes the object sufficiently | |
| 166 | 467 |
No key has been specified for the copy reference for functional location | The short text describes the object sufficiently | |
| 167 | 468 |
No superior functional location has been specified | The short text describes the object sufficiently | |
| 168 | 469 |
Functional location &1 cannot be installed (it is still installed in &2) | The short text describes the object sufficiently | |
| 169 | 470 |
Functional location is not installed; it can therefore not be removed | The short text describes the object sufficiently | |
| 170 | 471 |
Record for BOM item is incomplete; enter material number | The short text describes the object sufficiently | |
| 171 | 472 |
BOM item &1 does not require serial number to be specified | The short text describes the object sufficiently | |
| 172 | 473 |
Equipment BOM item has been changed; update required | The short text describes the object sufficiently | |
| 173 | 474 |
Consistency check has failed. Equipment BOM item cannot be updated | The short text describes the object sufficiently | |
| 174 | 475 |
Consistency check has failed. Equipment BOM item cannot be created | The short text describes the object sufficiently | |
| 175 | 476 |
Equipment BOM item will be created with the minimum of data | Space: object requires documentation | |
| 176 | 477 |
Equipment &1 does not exist and cannot be used as installation location | The short text describes the object sufficiently | |
| 177 | 478 |
Func. location &1 does not exist and cannot be used as inst. location | The short text describes the object sufficiently | |
| 178 | 479 |
Specify only one installation location; equipment or functional location | The short text describes the object sufficiently | |
| 179 | 480 |
Equipment &1 is not equipment BOM header | The short text describes the object sufficiently | |
| 180 | 481 |
Equipment &1 does not exist and cannot be used as equipment BOM header | The short text describes the object sufficiently | |
| 181 | 482 |
Current date and time will be used for object installation | The short text describes the object sufficiently | |
| 182 | 483 |
Equipment &1 (&2/&3) has not been changed; no update required | The short text describes the object sufficiently | |
| 183 | 484 |
Maintain quantity for equipment BOM item &1 in equipment BOM &2/&3 | The short text describes the object sufficiently | |
| 184 | 485 |
No key specified for functional location | The short text describes the object sufficiently | |
| 185 | 486 |
Selected equipment &1/&2 has already been reassigned | The short text describes the object sufficiently | |
| 186 | 487 |
Functional location &1 has subobjects and cannot be deleted | The short text describes the object sufficiently | |
| 187 | 488 |
Switch Framework is not set up correctly for takeover/handover | Space: object requires documentation | |
| 188 | 489 |
Incompatibility between portal and backend | Space: object requires documentation | |
| 189 | 490 |
Selected parent object is not a functional location object | Space: object requires documentation | |
| 190 | 491 |
Status 'inactive' cannot be set for newly created functional location &1 | The short text describes the object sufficiently | |
| 191 | 492 |
Copy reference &1 for functional location &2 does not exist | The short text describes the object sufficiently | |
| 192 | 493 |
Not all equipment has been reassigned. Takeover is still not possible | The short text describes the object sufficiently | |
| 193 | 494 |
Object &1 has still not been reassigned | The short text describes the object sufficiently | |
| 194 | 495 |
Please select a functional location | The short text describes the object sufficiently | |
| 195 | 496 |
Key of functional location &1 is not compliant to structure indicator &2 | The short text describes the object sufficiently | |
| 196 | 497 |
Please enter the required data | The short text describes the object sufficiently | |
| 197 | 498 |
Consistency check failed; functional location &1 cannot be updated | The short text describes the object sufficiently | |
| 198 | 499 |
Consistency check failed; functional location cannot be created | The short text describes the object sufficiently | |
| 199 | 500 |
Functional location will be created with minimum data | The short text describes the object sufficiently | |
| 200 | 501 |
Enter structure indicator or 'copy reference' for functional location &1 | The short text describes the object sufficiently | |
| 201 | 502 |
Technical object does not exist in the master database | The short text describes the object sufficiently | |
| 202 | 503 |
Equipment &2 is supposed to be installed into functional location &1 | The short text describes the object sufficiently | |
| 203 | 504 |
Equipment &2 is supposed to be installed into equipment &1 | The short text describes the object sufficiently | |
| 204 | 505 |
Equipment &1 has to be installed after its parent has been created | The short text describes the object sufficiently | |
| 205 | 506 |
Equipment &1 is installed in &2 &3 | The short text describes the object sufficiently | |
| 206 | 507 |
Category of tech object &1 not defined; define category or copy reference | The short text describes the object sufficiently | |
| 207 | 508 |
Quantity for BOM item &1 of &2 (&3) must be greater that 0 | The short text describes the object sufficiently | |
| 208 | 509 |
Structure indicator &1 different to structure indicator &2 of copy ref.&3 | The short text describes the object sufficiently | |
| 209 | 510 |
Functional location &1 will be created with minimum data | Space: object requires documentation | |
| 210 | 511 |
Category &1 is not supported for functional locations (check entry) | The short text describes the object sufficiently | |
| 211 | 512 |
Structure indicator &1 different to struct. indicator &2 of higher obj.&3 | The short text describes the object sufficiently | |
| 212 | 513 |
Functional location &1 in ERP is not installed in &2 as recorded | The short text describes the object sufficiently | |
| 213 | 514 |
Functional location &1 will be installed into functional location &2 | The short text describes the object sufficiently | |
| 214 | 515 |
Functional loc. &1 will be created with minimum data. Description missing | The short text describes the object sufficiently | |
| 215 | 516 |
Equipment without serial no. cannot be installed during takeover process | Space: object requires documentation | |
| 216 | 517 |
Consistency check has been performed | The short text describes the object sufficiently | |
| 217 | 518 |
You must not move an object below itself | The short text describes the object sufficiently | |
| 218 | 519 |
Equi &1 is neither installed nor serialized and will not be processed | Space: object requires documentation | |
| 219 | 520 |
Only reassignment of equipment possible | The short text describes the object sufficiently | |
| 220 | 521 |
Ser.nr. (&1) of equipment &2 must match with ser.nr. &3 from the file | The short text describes the object sufficiently | |
| 221 | 522 |
Equipment &1 (&2/&3) exists | The short text describes the object sufficiently | |
| 222 | 523 |
Only deletion of functional locations possible | The short text describes the object sufficiently | |
| 223 | 524 |
Consistency check ended with warnings; creation allowed | The short text describes the object sufficiently | |
| 224 | 525 |
Func. location category is not equal with copy reference FLoc category | The short text describes the object sufficiently | |
| 225 | 526 |
Equipment BOM header number is missing for BOM item &1 | The short text describes the object sufficiently | |
| 226 | 527 |
Description of func.loc. is different in backend to takeover/handover app | The short text describes the object sufficiently | |
| 227 | 528 |
Equipment &1 does not have material number assigned | The short text describes the object sufficiently | |
| 228 | 529 |
Equipment &1 does not have serial number assigned | The short text describes the object sufficiently | |
| 229 | 530 |
Installation date &1 must be greater than equipment 'valid from' date &2 | The short text describes the object sufficiently | |
| 230 | 531 |
Equipment &1 is not available in current takeover project | The short text describes the object sufficiently | |
| 231 | 532 |
Functional location &1 is not available in current takeover project | The short text describes the object sufficiently | |
| 232 | 533 |
Equipment &2 is supposed to be removed from functional location &1 | The short text describes the object sufficiently | |
| 233 | 534 |
Equipment &2 is supposed to be removed from equipment &1 | The short text describes the object sufficiently | |
| 234 | 535 |
Configuration check cannot be executed. Top equipment is not available. | The short text describes the object sufficiently | |
| 235 | 536 |
Config. check cannot be executed. Equi &1 does not have a MPL assigned. | The short text describes the object sufficiently | |
| 236 | 537 |
BOM item &1 (&2) is supposed to be installed into equipment &3 | The short text describes the object sufficiently | |
| 237 | 538 |
BOM item &1 (&2) is supposed to be removed from equipment &3 | The short text describes the object sufficiently | |
| 238 | 539 |
Installation date &1 must be greater than item 'valid from' date &2 | The short text describes the object sufficiently | |
| 239 | 540 |
Functional location &1 has not been changed; no update required | The short text describes the object sufficiently | |
| 240 | 541 |
Classification from copy reference &2 successfully copied into object &1 | The short text describes the object sufficiently | |
| 241 | 542 |
Copy of class &1 from copy reference &2 failed | The short text describes the object sufficiently | |
| 242 | 543 |
Maint.plant of superior &1 &2 is different from maint.plant of the &3 &4 | The short text describes the object sufficiently | |
| 243 | 544 |
Maint.plant &1 of equi &2 to be inst. must match maint.plant &3 of &4 | The short text describes the object sufficiently | |
| 244 | 545 |
Maint.plant &1 of the superior &2 &3 will be inherited for new equipment | The short text describes the object sufficiently | |
| 245 | 546 |
Superior equipment &1 is not available in the current takeover project | The short text describes the object sufficiently | |
| 246 | 547 |
Superior func. location &1 is not available in current takeover project | The short text describes the object sufficiently | |
| 247 | 548 |
Maint.plant of equi &1 will be updated with maint.plant &2 from &3 &4 | The short text describes the object sufficiently | |
| 248 | 549 |
Select one single object | The short text describes the object sufficiently | |
| 249 | 550 |
You cannot insert subobjects for BOM items. Select equip./func. location | The short text describes the object sufficiently | |
| 250 | 551 |
Material number has not been specified. Maintain material number | The short text describes the object sufficiently | |
| 251 | 552 |
Configurable materials cannot be used as stock items in equipment BOM | The short text describes the object sufficiently | |
| 252 | 553 |
New functional location &1 successfully assigned to the structure | The short text describes the object sufficiently | |
| 253 | 554 |
Determination of the equipment to be removed automatically not successful | Space: object requires documentation | |
| 254 | 555 |
Equipment &1 will be removed automatically from &2 &3 in backend system | The short text describes the object sufficiently | |
| 255 | 556 |
No equipment needs to be removed automatically from backend system | The short text describes the object sufficiently | |
| 256 | 557 |
Material &1 does not allow assignment of effectivity values for new equi | The short text describes the object sufficiently | |
| 257 | 558 |
Maint. plant of &1 &2 will be overwritten with maint. plant &3 of &4 | Space: object requires documentation | |
| 258 | 559 |
Maint. plant of &1 &2 has been overwritten with maint. plant of &3 &4 | The short text describes the object sufficiently | |
| 259 | 560 |
Equipment &1 automatically removed from &2 &3 in the backend system | The short text describes the object sufficiently | |
| 260 | 561 |
Automatic removal of equipment &1 from &2 &3 in backend system failed | The short text describes the object sufficiently | |
| 261 | 562 |
Installation date/time &1 must be greater than removal date/time &2 | The short text describes the object sufficiently | |
| 262 | 563 |
Removal date/time &1 must be greater than installation date/time &2 | The short text describes the object sufficiently | |
| 263 | 564 |
Removal date &1 must be greater than equipment 'valid from' date &2 | The short text describes the object sufficiently | |
| 264 | 565 |
Removal date/time for equipment is in future | The short text describes the object sufficiently | |
| 265 | 566 |
Equipment &1 (&2/&3) has been excluded from the takeover process | The short text describes the object sufficiently | |
| 266 | 567 |
Equipment BOM item &1 has been excluded from the takeover process | The short text describes the object sufficiently | |
| 267 | 568 |
Serial number &1 of existing equipment &2 must not be deleted | The short text describes the object sufficiently | |
| 268 | 569 |
Combination of material &1 and serial number &2 exists (equipment &3) | Space: object requires documentation | |
| 269 | 570 |
Serial no. &1 does not match with the serial no. &2 of the equipment &3 | The short text describes the object sufficiently | |
| 270 | 571 |
Equipment &1 (&2/&3) is updated with the new serial number &4 | The short text describes the object sufficiently | |
| 271 | 572 |
Equipment BOM header data will be created for equipment &1 | The short text describes the object sufficiently | |
| 272 | 573 |
UII has not been specified. Maintain UII. | The short text describes the object sufficiently | |
| 273 | 574 |
Naming Convention for Functional Location &1 is not correct | Space: object requires documentation | |
| 274 | 575 |
Material &1 requires Base Unit of Measure &2 | The short text describes the object sufficiently | |
| 275 | 600 |
***** Messages for APPEND/DELETE LINE functionality ***** | The short text describes the object sufficiently | |
| 276 | 601 |
Specify functional location number | The short text describes the object sufficiently | |
| 277 | 602 |
Func. location can be inserted only under the another func. location | The short text describes the object sufficiently | |
| 278 | 603 |
&1 &2 is part of current takeover project and cannot be used | The short text describes the object sufficiently | |
| 279 | 604 |
Equipment cannot be inserted under the equipment BOM item | The short text describes the object sufficiently | |
| 280 | 605 |
Equipment BOM item can be inserted only under the equipment | The short text describes the object sufficiently | |
| 281 | 606 |
Equipment &1 cannot be inserted because its status is not 'available' | The short text describes the object sufficiently | |
| 282 | 607 |
Specify material number for BOM item | The short text describes the object sufficiently | |
| 283 | 608 |
Equipment &1 is installed in &2 &3 and cannot be deleted | The short text describes the object sufficiently | |
| 284 | 609 |
Func. location &1 is assigned to func. location &2 and cannot be deleted | The short text describes the object sufficiently | |
| 285 | 610 |
BOM item &1 is part of equipment BOM &2 (&3) and cannot be deleted | The short text describes the object sufficiently | |
| 286 | 611 |
Error occured during object deletion. For details see application log | The short text describes the object sufficiently | |
| 287 | 612 |
Object &1 &2 has been deleted successfully | The short text describes the object sufficiently | |
| 288 | 613 |
Object &1 &2 has been inserted successfully | The short text describes the object sufficiently | |
| 289 | 614 |
Equipment &1 does not exist, entry cannnot be inserted | The short text describes the object sufficiently | |
| 290 | 615 |
Object(s) deleted successfully | The short text describes the object sufficiently | |
| 291 | 616 |
Object &1 &2/&3 has been deleted successfully | The short text describes the object sufficiently | |
| 292 | 617 |
Object &1 &2/&3 has been inserted successfully | The short text describes the object sufficiently | |
| 293 | 618 |
At least one object must be selected for this operation | The short text describes the object sufficiently | |
| 294 | 619 |
Data has been changed in customer BAdI implementation | The short text describes the object sufficiently | |
| 295 | 620 |
Copy ref. object contains inactive MPs that are used for creation of MP | Space: object requires documentation | |
| 296 | 621 |
Inactive maintenance plans used for creation of new maintenance plan(s) & | The short text describes the object sufficiently | |
| 297 | 898 |
The short text describes the object sufficiently | ||
| 298 | 899 |
&1 &2 | The short text describes the object sufficiently | |
| 299 | 999 |
The short text describes the object sufficiently |
History
| Last changed on/by | |
20110908 | SAP |
| SAP Release Created in | 700 |
