CMS_TR - KPRO: Content Management Service (Transportanschlu�)
The following messages are stored in message class CMS_TR: KPRO: Content Management Service (Transportanschlu�).
It is part of development package SCMS in software component BC-SRV-KPR-CMS. This development package consists of objects that can be grouped under "KPRO: Content Management Service".
It is part of development package SCMS in software component BC-SRV-KPR-CMS. This development package consists of objects that can be grouped under "KPRO: Content Management Service".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Category &1 is not assigned to a repository |
| 001 | No import URL can be determined for content repository &1 (category &2) |
| 002 | No export URL can be determined for content repository &1 (category &2) |
| 003 | Content repository &1 (category &2) inaccessible |
| 004 | Export cannot be performed |
| 005 | Import cannot be performed |
| 006 | COMMUNICATION_FAILURE for RFC call &1 (destination &2): &3&4 |
| 007 | SYSTEM_FAILURE for RFC call &1 (destination &2): &3&4 |
| 008 | Error in calling KPro transport server |
| 009 | Message &1 for category &2: &3&4 |
| 010 | Message &1 for document &2: &3&4 |
| 011 | &1 messages regarding categories |
| 012 | &1 messages regarding documents |
| 013 | Error code &1 from transport server (RFC call &2, destination &3) |
| 014 | ... &1&2&3&4 |
| 015 | Content repository &1 is not assigned to a storage system |
| 016 | Internal parameter error: The file name (DATAFILE) is too long |
| 017 | Category &1 does not exist |
| 018 | Content repository &1 (category &2) cannot be imported |
| 019 | Content repository &1 (category &2) cannot be exported |
| 020 | Message &1: &3&4 |
| 021 | No import URL can be determined for content rep. &1 (cat. &2 / &3) |
| 022 | The category &1 (&2) does not exist |
| 023 | Category &1 from the transport file is imported into category &2 |