RMPS_POST_API - PRO Meldungen f�r das Posteingangsst�ck
The following messages are stored in message class RMPS_POST_API: PRO Meldungen f�r das Posteingangsst�ck.
It is part of development package RMPS_SP_POST in software component CA-GTF-RCM. This development package consists of objects that can be grouped under "Incoming Post Item".
It is part of development package RMPS_SP_POST in software component CA-GTF-RCM. This development package consists of objects that can be grouped under "Incoming Post Item".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1 &2 &3 &4 |
| 001 | No basic settings for incoming post maintained for document type &1 |
| 002 | Active linkage entry of object &1 and document type &2 are missing |
| 003 | Uploading and storing of file &1 in archive &2 failed |
| 004 | &1 attribute/s could not be set |
| 005 | Linkage of original (&1) with incoming post item (&2) failed |
| 006 | Global document type customizing for &1 contains errors |
| 007 | Originals of type &1 are not supported by the incoming post item |
| 008 | Agent &1 does not exist |
| 009 | Process route &1 does not exist in activity area &2 |
| 010 | Agent type &1 for activity area &2 is not allowed |
| 011 | Type &1 of activity &2 is different to type &3 of agent &4 |
| 012 | Activity &1 for activity area &2 not allowed |
| 013 | Incoming post item not found |
| 014 | Deletion of incoming post item failed |
| 015 | Incoming post item deleted successfully |
| 016 | The declare function is not supported by the service provider |
| 017 | Value &1 is invalid for parameter &2 |
| 018 | Access to e-mail failed |
| 019 | Uploading of file &1 failed (&2) |
| 020 | Creation of attachment from file no. &1; &2 failed |
| 021 | Adding attachment from file no. &1 failed |
| 022 | Creation of SAP mail failed (&1) |
| 023 | Creation of SAP Mail from text table failed (&1) |
| 024 | Loading of incoming post item failed (&1) |
| 025 | Changing of attributes failed (&1) |
| 030 | No status profile maintained in Customizing for element type &1 |
| 031 | Initial status of status profile &1 could not be determined |
| 032 | Error when reading status information on current status &1 |
| 033 | Error when determining follow-on statuses for statuses &1 (profile &2) |