/IAM/UI - UI Message without any correlation to BO logic
The following messages are stored in message class /IAM/UI: UI Message without any correlation to BO logic.
It is part of development package /IAM/UI_QAM in software component CA-IAM-ENG. This development package consists of objects that can be grouped under "QIM Specific UI Objects in IAM Layer".
It is part of development package /IAM/UI_QAM in software component CA-IAM-ENG. This development package consists of objects that can be grouped under "QIM Specific UI Objects in IAM Layer".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Structure &1 could not be integrated into the UI structure |
| 002 | Structure &1 is not part of the UI structure |
| 003 | There is no component with position &2 in structure &1 |
| 004 | Node category &1 does not exist for root node of BOPF object &2 |
| 010 | Select at least one activity |
| 011 | Internal error on activity type change during activity creation |
| 012 | Enter a valid activity type |
| 014 | Activity category has been changed |
| 015 | Internal error: activity category is not available |
| 016 | Internal error: there is no activity type available in the UI |
| 099 | Data must be saved first |
| 100 | No changes were saved |
| 101 | Changes saved with inconsistencies |
| 102 | Save is not necessary because there are no changes |
| 103 | Error accessing attachment data |
| 104 | Attachments could not be deleted |
| 105 | Error accessing partner data |
| 106 | Error accessing reference object data |
| 107 | No access to object data |
| 109 | Cannot get a URL for attached file '&1' |
| 110 | Error accessing response value data |
| 111 | Internal error: unexpected event |
| 112 | Internal error: inconsistent data |
| 113 | Changes successfully saved |
| 114 | &1 successfully deleted |
| 115 | Text type &1 cannot be created twice (see Customizing for issue type &2) |
| 116 | Selection for field &1 is too unspecific (&2 hits) |
| 117 | Selected file &1 is empty |
| 118 | Activity &1: status changed to &2 in other session |
| 119 | Error accessing file content for attachment '&1' |
| 120 | Wrong settings for step '&1'; either activity type or template required |
| 121 | URL for newly attached file '&1' will be available after save |
| 134 | Navigation to external application not possible; object is not saved |
| 135 | There are no signatures that can be canceled |
| 136 | You must save your data before the signature process can be started |
| 137 | Deletion not possible; selection contains main reference object &1 (&2) |
| 138 | Follow-up issue &1 successfully created for defect &2 |
| 139 | Errors occurred when creating follow-up issue &1 for defect &2 |
| 140 | Follow-up issue &1 already exists for defect &2 |
| 141 | Action &1 not possible; there is no answer for the question |
| 142 | Cause already exists with ID &1 |
| 143 | Action &1 failed |
| 144 | Action '&1' not possible; conditions for issue not sufficient |
| 145 | Action '&1' executed; unsupported conditions have been skipped |
| 150 | Wiring is not configured properly |
| 151 | Internal error in class &1 / method &2 |
| 200 | Field &1 does not support display type &2 (&3) |
| 201 | Field &1 does not match display type &2 (&3) |
| 202 | Field &1 is always read-only but is configured with display type &2 (&3) |
| 204 | Feeder action &1 (&2) does not support display type &3 (&4) |
| 205 | Assign a step with an activity type or activity template assignment |
| 206 | Recipient with blocked business partner was automatically deleted |