EDESK_COMM_PIO - Engineering Desktop: Partner Integration Outbound
The following messages are stored in message class EDESK_COMM_PIO: Engineering Desktop: Partner Integration Outbound.
It is part of development package EDESK_COMM in software component PLM-WUI-APP-EDK. This development package consists of objects that can be grouped under "Engineering Desktop: Communication".
It is part of development package EDESK_COMM in software component PLM-WUI-APP-EDK. This development package consists of objects that can be grouped under "Engineering Desktop: Communication".
Message Nr ▲ | Message Text |
---|---|
000 | &1&2&3&4 |
001 | Generation of logical port &1 failed |
002 | Customizing parameter &1 or URL parameter &2 is mandatory |
003 | No protocol defined in &1 |
004 | No hostname defined in &1 |
005 | Error in URL parameter &1 |
006 | Protocol &1 is not supported; choose HTTP or HTTPS |
007 | WS client proxy could not be created |
008 | Update of logical port &1 failed |
009 | Undefined error during initialization of WS partner integration |
010 | System failure in system &1 while calling WS &2 with logical port &3 |
011 | Application failure in system &1 while calling WS &2 with logical port &3 |
012 | Unknown failure in system &1 while calling WS &2 with logical port &3 |
013 | Integration type not determinable; verify URL and customizing parameter |
014 | Error during initialization of partner integration outbound |
015 | System failure in system &1 while calling RFC &2 with destination &3 |
016 | Communication failure in system &1 when RFC &2 with destination &3 called |
017 | Unknown failure in system &1 while calling RFC &2 with destination &3 |
018 | Message class &1 is not allowed as return message; message was ignored |
019 | Undefined error during initialization of RFC partner integration |
020 | RFC destination &1 already exists with connection type &2 instead of &3 |
021 | &1 parameter &2 must have a length of &3 characters instead of &4 |
022 | &1 parameter &2 contains the unallowed character &3 at position &4 |
023 | &1 parameter &2 must have a length of <= &3 characters instead of &4 |
024 | Generation of RFC destination &1 failed |
025 | Update of RFC destination &1 failed |
026 | Error while checking the RFC destination &1 |
027 | RFC destination template &1 has connection type &2 instead of &3 |
028 | RFC destination template &1 does not exist |
029 | Copying of RFC destination template &1 to RFC destination &2 failed |
030 | URL parameter &1 is mandatory |
031 | Copying of logical port template &1 to logical port &2 failed |
032 | Logical port template &1 does not exist |
033 | Logical port template &1 is not based on consumer proxy &2 |
034 | Connection to &1 failed |