CHIP_API - Messages for Generic CHIP Framework
The following messages are stored in message class CHIP_API: Messages for Generic CHIP Framework.
It is part of development package SWDP_CCP_API in software component BC-WD-ABA-PB. This development package consists of objects that can be grouped under "Web Dynpro ABAP: CCP Integration API".
It is part of development package SWDP_CCP_API in software component BC-WD-ABA-PB. This development package consists of objects that can be grouped under "Web Dynpro ABAP: CCP Integration API".
Message Nr ▲ | Message Text |
|---|---|
| 001 | & |
| 101 | CHIP instance &1 does not exist |
| 102 | Outport &1 of CHIP instance &2 does not exist |
| 103 | Inport &1 of CHIP instance &2 does not exist |
| 601 | Mandatory parameter &1 of inport &2 is not bound |
| 602 | Parameter &1 of inport &2 specified in the wiring does not exist |
| 603 | Type of constant value &1 not compatible with parameter &2 of inport &3 |
| 604 | Parameter &1 of outport &2 specified in the wiring does not exist |
| 605 | The SY &1 specified in the wiring does not exist |
| 651 | Determines automatic wiring of CHIP &1 to CHIP &2 |
| 652 | Determines proposal starting from outport &1 |
| 653 | Determines proposal of outport &1 to inport &2 |
| 654 | Multiplicity of ports is different; proposal would have less quality |
| 655 | Multiplicity of ports is different; combination skipped |
| 656 | Multiple proposals of poor quality, therefore no proposal created |
| 657 | No suitable proposal found |
| 658 | Mulitple proposals with the same multiplicity; therefore no proposal |
| 659 | Proposal with multiplicity created, ignore poor quality |
| 660 | Multiple proposals of poor quality, ignore poor quality as of now |
| 661 | Determines suitable outport parameter for inport parameter & |
| 662 | Outport parameter &1 has only &2 suitable tags and will be rejected |
| 663 | Outport parameter &1 of same name witht &2 suitable tags is a candidate |
| 664 | Outport parameter &1 also has &2 suitable tags, also rejects candidates |
| 665 | Different-named outport parameter &1 with &2 matching tags is a candidate |
| 666 | No proposal for outport &1 inport &2 because of mandatory parameter &3 |
| 667 | Inport parameter & remains without a value in the proposal |
| 668 | Outport parameter &1 is assigned to inport parameter &2 in the proposal |
| 669 | Multiple assignments possible for parameter &; therefore no proposal |