Message Number list used by SAP ABAP Class CL_PHIN_FLOC (PHIN: Functional Locations)
SAP ABAP Class CL_PHIN_FLOC (PHIN: Functional Locations) is using
# | Object Type | Object Name | Object Description | Note |
---|---|---|---|---|
1 | Message Number | PHIN - 513 | Functional location &1 in ERP is not installed in &2 as recorded | |
2 | Message Number | PHIN - 496 | Key of functional location &1 is not compliant to structure indicator &2 | |
3 | Message Number | PHIN - 498 | Consistency check failed; functional location &1 cannot be updated | |
4 | Message Number | PHIN - 499 | Consistency check failed; functional location cannot be created | |
5 | Message Number | PHIN - 501 | Enter structure indicator or 'copy reference' for functional location &1 | |
6 | Message Number | PHIN - 501 | Enter structure indicator or 'copy reference' for functional location &1 | |
7 | Message Number | PHIN - 501 | Enter structure indicator or 'copy reference' for functional location &1 | |
8 | Message Number | PHIN - 507 | Category of tech object &1 not defined; define category or copy reference | |
9 | Message Number | PHIN - 509 | Structure indicator &1 different to structure indicator &2 of copy ref.&3 | |
10 | Message Number | PHIN - 510 | Functional location &1 will be created with minimum data | |
11 | Message Number | PHIN - 511 | Category &1 is not supported for functional locations (check entry) | |
12 | Message Number | PHIN - 492 | Copy reference &1 for functional location &2 does not exist | |
13 | Message Number | PHIN - 514 | Functional location &1 will be installed into functional location &2 | |
14 | Message Number | PHIN - 515 | Functional loc. &1 will be created with minimum data. Description missing | |
15 | Message Number | PHIN - 524 | Consistency check ended with warnings; creation allowed | |
16 | Message Number | PHIN - 525 | Func. location category is not equal with copy reference FLoc category | |
17 | Message Number | PHIN - 525 | Func. location category is not equal with copy reference FLoc category | |
18 | Message Number | PHIN - 527 | Description of func.loc. is different in backend to takeover/handover app | |
19 | Message Number | PHIN - 540 | Functional location &1 has not been changed; no update required | |
20 | Message Number | PHIN - 574 | Naming Convention for Functional Location &1 is not correct | |
21 | Message Number | PHIN - 619 | Data has been changed in customer BAdI implementation | |
22 | Message Number | PHIN - 466 | Not able to find copy reference for functional location | |
23 | Message Number | PHIN - 427 | Creation of functional location &1 failed | |
24 | Message Number | PHIN - 428 | Functional location &1 succesfully updated | |
25 | Message Number | PHIN - 429 | Update of functional location &1 failed | |
26 | Message Number | PHIN - 440 | Parent object has not been created yet | |
27 | Message Number | PHIN - 442 | Consistency check has been performed successfully; update allowed | |
28 | Message Number | PHIN - 444 | Consistency check has been performed successfully; creation allowed | |
29 | Message Number | PHIN - 446 | Consistence check has not yet been carried out | |
30 | Message Number | PHIN - 461 | Functional location &1 is not installed in &2 as recorded in takeover | |
31 | Message Number | PHIN - 464 | Functional location &1 must not be installed in a piece of equipment | |
32 | Message Number | PHIN - 465 | Copy reference for functional location found; &1 | |
33 | Message Number | PHIN - 426 | Functional location &1 succesfully created | |
34 | Message Number | PHIN - 468 | No superior functional location has been specified | |
35 | Message Number | PHIN - 468 | No superior functional location has been specified | |
36 | Message Number | PHIN - 469 | Functional location &1 cannot be installed (it is still installed in &2) | |
37 | Message Number | PHIN - 470 | Functional location is not installed; it can therefore not be removed | |
38 | Message Number | PHIN - 473 | Equipment BOM item has been changed; update required | |
39 | Message Number | PHIN - 485 | No key specified for functional location | |
40 | Message Number | PHIN - 487 | Functional location &1 has subobjects and cannot be deleted | |
41 | Message Number | PHIN - 491 | Status 'inactive' cannot be set for newly created functional location &1 | |
42 | Message Number | PHIN - 492 | Copy reference &1 for functional location &2 does not exist |