SAP ABAP Message Class CHIP_API (Messages for Generic CHIP Framework)
Basic Data
Hierarchy
☛
SAP_UI (Software Component) User Interface Technology
⤷
BC-WD-ABA-PB (Application Component) WD ABAP Page Builder
⤷
SWDP_CCP_API (Package) Web Dynpro ABAP: CCP Integration API
⤷
⤷
Attributes
| Message class | CHIP_API | |
| Short Description | Messages for Generic CHIP Framework | |
| Changed On | 20110908 | |
| Last Changed At | 153109 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | & | The short text describes the object sufficiently | ||
| 2 | CHIP instance &1 does not exist | The short text describes the object sufficiently | ||
| 3 | Outport &1 of CHIP instance &2 does not exist | The short text describes the object sufficiently | ||
| 4 | Inport &1 of CHIP instance &2 does not exist | The short text describes the object sufficiently | ||
| 5 | Mandatory parameter &1 of inport &2 is not bound | The short text describes the object sufficiently | ||
| 6 | Parameter &1 of inport &2 specified in the wiring does not exist | The short text describes the object sufficiently | ||
| 7 | Type of constant value &1 not compatible with parameter &2 of inport &3 | The short text describes the object sufficiently | ||
| 8 | Parameter &1 of outport &2 specified in the wiring does not exist | The short text describes the object sufficiently | ||
| 9 | The SY &1 specified in the wiring does not exist | The short text describes the object sufficiently | ||
| 10 | Determines automatic wiring of CHIP &1 to CHIP &2 | The short text describes the object sufficiently | ||
| 11 | Determines proposal starting from outport &1 | The short text describes the object sufficiently | ||
| 12 | Determines proposal of outport &1 to inport &2 | The short text describes the object sufficiently | ||
| 13 | Multiplicity of ports is different; proposal would have less quality | The short text describes the object sufficiently | ||
| 14 | Multiplicity of ports is different; combination skipped | The short text describes the object sufficiently | ||
| 15 | Multiple proposals of poor quality, therefore no proposal created | The short text describes the object sufficiently | ||
| 16 | No suitable proposal found | The short text describes the object sufficiently | ||
| 17 | Several proposals with same multiplicity; therefore no proposal | The short text describes the object sufficiently | ||
| 18 | Proposal with multiplicity created, ignore poor quality | The short text describes the object sufficiently | ||
| 19 | Multiple proposals of poor quality, ignore poor quality as of now | The short text describes the object sufficiently | ||
| 20 | Determines suitable outport parameter for inport parameter & | The short text describes the object sufficiently | ||
| 21 | Outport parameter &1 has only &2 suitable tags and will be rejected | The short text describes the object sufficiently | ||
| 22 | Outport parameter &1 of same name witht &2 suitable tags is a candidate | The short text describes the object sufficiently | ||
| 23 | Outport parameter &1 also has &2 suitable tags, also rejects candidates | The short text describes the object sufficiently | ||
| 24 | Different-named outport parameter &1 with &2 matching tags is a candidate | The short text describes the object sufficiently | ||
| 25 | No proposal for outport &1 inport &2 because of mandatory parameter &3 | The short text describes the object sufficiently | ||
| 26 | Inport parameter & remains without a value in the proposal | The short text describes the object sufficiently | ||
| 27 | Outport parameter &1 is assigned to inport parameter &2 in the proposal | The short text describes the object sufficiently | ||
| 28 | Multiple assignments possible for parameter &; therefore no proposal | The short text describes the object sufficiently |
History
| Last changed on/by | 20110908 | SAP | |
| SAP Release Created in | 720 |