/MSG/4_PM_MESSAGE - PM.Connection Nachrichten
The following messages are stored in message class /MSG/4_PM_MESSAGE: PM.Connection Nachrichten.
It is part of development package /MSG/4_PM_CORE in software component FS-MPM-CPM. This development package consists of objects that can be grouped under "PM.Connection Core".
It is part of development package /MSG/4_PM_CORE in software component FS-MPM-CPM. This development package consists of objects that can be grouped under "PM.Connection Core".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Customizing for application '&1' incomplete |
| 005 | Assigned PM data type for data type "&1" could not be determined |
| 012 | Not authorized for the action to be performed |
| 013 | Client is locked |
| 014 | This client is locked against customizing changes |
| 017 | Import of include '&1' failed |
| 019 | Please complete all required mandatory fields |
| 020 | Product data are currently locked against changes |
| 030 | Creation of application log failed |
| 031 | Adding data to the application log failed |
| 032 | Saving data in the application log failed |
| 040 | Product library for export ID "&1" does not exist |
| 041 | Binary data for "&1" (&2) does not exist in the data cluster |
| 042 | Binary file "&1" for "&2" (&3) does not exist in the data cluster |
| 043 | Binary data section &1-&2 of "&3" (&4) does not exist in the data cluster |
| 048 | PM.Connection binary data transfer: transfer &1 of &2 kilobytes |
| 050 | Customizing of the PM.Runtime versions for component '&1' incomplete |
| 051 | System or communication error '&1&2' at RFC destination '&3' |
| 052 | Valid RFC destination is required |
| 053 | Invalid destination category '&1' instead '&2' for RFC destination '&3' |
| 054 | Sending using HTTP destination '&3' failed: '&1&2' |
| 055 | Receiving HTTP destination '&3' failed: '&1&2' |
| 056 | Transformation between tables and JSON failed: '&1&2' |
| 057 | Unsuccessful status from call to HTTP destination '&3': rc='&1': '&2' |
| 060 | PM.Runtime Scheduler customizing incomplete |
| 061 | Enqueuing of RFC destination '&1' by PM.Runtime Scheduling failed |
| 062 | No further destinations available through PM.Runtime Scheduling |
| 063 | RFC destination '&1' not available |
| 064 | Activation type not allowed for RFC destination '&1' |
| 065 | Dequeuing of RFC destination '&1' by PM.Runtime Scheduling failed |
| 070 | PM.Connection data access layer: data record for '&1' does not exist |
| 072 | PM.Connection data access layer: unknown search method '&1' |
| 075 | PM.Connection data access layer: write access failed |
| 078 | PM.Connection data access layer: data record deletion failed |
| 080 | PM.Connection data access layer: enqueue product library '&1 &2' |
| 082 | PM.Connection data access layer: error while accessing data cluster |
| 100 | &1&2&3&4 |
| 101 | Object creation: &1|&2|&3|&4 |
| 102 | Method execution: &1|&2|&3|&4 |
| 103 | Object export: &1|&2|&3|&4 |
| 104 | Verification export: &1|&2|&3|&4 |