SWDP_CCP_WD - Messages for Objects from Package SWDP_CCP_WD_API
The following messages are stored in message class SWDP_CCP_WD: Messages for Objects from Package SWDP_CCP_WD_API.
It is part of development package SWDP_CCP_WD_API in software component BC-WD-ABA-PB. This development package consists of objects that can be grouped under "Web Dynpro ABAP: WDA Page Builder WD Integration API".
It is part of development package SWDP_CCP_WD_API in software component BC-WD-ABA-PB. This development package consists of objects that can be grouped under "Web Dynpro ABAP: WDA Page Builder WD Integration API".
Message Nr ▲ | Message Text |
|---|---|
| 000 | ** [001-010] Messages for Web Dynpro WIRING UI |
| 001 | No inport: CHIP &1 |
| 002 | Inport: '&1' has no parameters |
| 003 | Outport: '&1' has no parameters |
| 004 | Error in configuration of '&1' |
| 005 | Connected &1 |
| 006 | Not connected |
| 007 | Connection saved |
| 008 | Connection not saved |
| 009 | Connection removed |
| 010 | No connection |
| 011 | No outport |
| 012 | Connection locked by user '&2' |
| 013 | Connection locked in transport request '&2' |
| 014 | Automatic: CHIP &1 |
| 015 | Container width is not valid |
| 016 | Maximum container width 100% reached |
| 017 | In page configuration '&1' a layout error has occurred |
| 018 | Invalid URL syntax; change the URL in the configuration |
| 019 | Entry '&1' occurs more than once; change the configuration |
| 020 | Navigation target cannot be opened in a new window |
| 021 | Entry '&1' already exists; it cannot be added |
| 022 | CHIP name could not be ascertained |
| 023 | CHIP &1 does not exist, or authorizations for this are missing |
| 024 | Catalog favorites deleted |
| 025 | Missing input: role, instance, and folder ID must be specified |
| 026 | POWL application &1 does not exist |
| 027 | User &1 is not assigned to role &2 or the role does not exist |
| 028 | Role &1 does not contain node ID &2 |
| 029 | Web Dynpro context tagging "&1" is not unique |
| 030 | Web Dynpro context tagging "&1" is not correct |
| 031 | Mandatory parameter "&1" is empty |
| 032 | In configuration &1 no OBN target is defined for application &2 |
| 033 | Function is not supported by the current client |