MSPCIF -
The following messages are stored in message class MSPCIF: .
It is part of development package DI_MSP_CIF in software component IS-AD. This development package consists of objects that can be grouped under "Maintenance and Service Planning CIF".
It is part of development package DI_MSP_CIF in software component IS-AD. This development package consists of objects that can be grouped under "Maintenance and Service Planning CIF".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Maintenance is not permitted; Customizing entry is obsolete |
| 001 | Entries of old customizing have been copied to new customizing |
| 002 | Entries of old customizing cannot be copied to new customizing |
| 020 | Selection of call object failed |
| 021 | Maintenance and Service Planning: Processing CIF queue &1 |
| 022 | Finding next call object for call object &1/&2 failed (context: &3) |
| 023 | Cannot find call object of maint. plan &1 for demand &2 (context:&3) |
| 024 | For the given slot &1, there is no revision in ERP |
| 025 | Incoming data is inconsistent for demand &1 of maintenance plan &2 |
| 026 | Revision creation failed: Revision &1/&2 for APO slot &3 |
| 027 | Notification assignment failed: Revision &1/&2 for slot &3 |
| 028 | Revision update failed: Revision &1/&2 for APO slot &3 |
| 029 | Notification deassignment failed: Revision &1/&2 for slot &3 |
| 030 | Revision deletion failed: Revision &1/&2 for APO slot &3 |
| 031 | Call object &1/&2 for demand &3 cannot be located |
| 032 | Revision (&1/&2) cannot be changed after order generation |
| 033 | Revision (&1/&2) cannot be deleted after order generation |
| 034 | Slot number &1 violates revision number range definition &2/&3/&4 |
| 035 | Revision number range interval &1/&2/&3 not for external numbers |
| 036 | Revision number range interval &1/&2/&3 not found |
| 037 | Data transfer Customizing for plant &1 has not been maintained |
| 038 | Main. Plants (&1, &3) of slot &2 and maintenance item &4 are different |
| 039 | Maintenance plan &1 cannot be locked (being used by &2) |
| 040 | Schedule of maint. plan &1 restarted at call obj. &2 (Context: &3/&4) |
| 041 | Call object &1/&2 has been skipped, but is linked to demand &3 |
| 042 | Incoming data is inconsistent for slot &1 |
| 043 | Maintenance object &1/&2 is invalid |
| 045 | Revision &1/&2 created against APO slot &3 |
| 046 | Notification &1 is assigned to the revision &2/&3 against demand &4 |
| 047 | Call object &1/&2 is linked to revision &3/&4 |
| 048 | Call object &1/&2 is linked to demand &3 |
| 049 | Revision &1/&2 changed against APO slot &3 |
| 050 | Notification &1 is deassigned from revision &2/&3 |
| 051 | Call object &1/&2 is unlinked from demand &3 |
| 052 | Revision &1/&2 is deleted |
| 053 | Maintenance planning plant is not maintained for maintenance plant &1 |
| 054 | Saving revisions/notifications/orders to DB has failed |
| 056 | Demand number &1 violates notification number range definition &2/&3 |
| 057 | Notification number range &1/&2/&3 not found |
| 058 | Notification number range interval &1/&2/&3 not for external numbers |
| 060 | Enter a valid revision type |