QAM - Allgemeine Nachrichtenklasse f�r Quality Issue Management
 The following messages are stored in message class QAM: Allgemeine Nachrichtenklasse f�r Quality Issue Management.
It is part of development package QAM_DDIC in software component CA-IAM-QIM. This development package consists of objects that can be grouped under "QIM Data Structures".
 It is part of development package QAM_DDIC in software component CA-IAM-QIM. This development package consists of objects that can be grouped under "QIM Data Structures".
| Message Nr ▲ | Message Text | 
|---|---|
| 000 | Internal error (class &1, method &2) | 
| 001 | No mapping found for category &1 | 
| 002 | No active system connection to categories available for issues | 
| 003 | No active system connection to categories available for activities | 
| 004 | Method &1 is not supported by category &2 in system &3 | 
| 009 | No setting found for object type &1 | 
| 010 | Remote access to category &2 is not possible in system &1 | 
| 011 | Access to logical system &1 | 
| 012 | No RFC destination found for logical system &1 | 
| 013 | Structure &1 in mapping &2, step &3 is not valid | 
| 014 | Error in mapping &1, step &2 | 
| 015 | You do not have authorization for this function (authorization object &1) | 
| 016 | Structure &1 does not exist (step &2, mapping &3) | 
| 017 | Internal error: Logical system not included in structure | 
| 018 | Search result structure missing (step &1, mapping &2) | 
| 019 | Mapping &1, step &2 not unique | 
| 020 | Several target systems point to the same RFC destination &1 | 
| 023 | Category &1 is excluded from the selection (invalid criterion) | 
| 026 | No suitable Customizing entries found for category &1, system &2 | 
| 027 | Internal error; no category specified for detailed search | 
| 028 | Task &1 failed; check the system connection | 
| 029 | Search structure is not valid (&1 for mapping &2) | 
| 030 | Structure missing for mapping &1, step &2 | 
| 031 | Search structure missing for mapping &1, step &2 | 
| 032 | No implementation found for detailed search for category &1 | 
| 033 | No implementation found for search for category &1 | 
| 034 | Task &1 for reading details failed | 
| 035 | Error when reading data &1 | 
| 036 | No data found for &1 | 
| 037 | No response to &1 of &2 search queries due to timeout | 
| 038 | BAdI implementation for category &1 contains syntax errors | 
| 039 | Category &1 is not supported in the local system | 
| 040 | No active category found that fulfills the search criteria | 
| 041 | No active mapping found for detail &1 | 
| 042 | Technical error; table &1 is not part of structure | 
| 043 | Object &1 contains errors | 
| 044 | Partner &1 does not exist | 
| 045 | You are not authorized to read partner data for &1 | 
| 046 | Partner data for &1 could not be read | 
| 047 | Entries for ID and parent notification are mutually exclusive | 
| 048 | Search for items is only supported for fully specified IDs | 
| 049 | Search is supported only if code specified fully | 
| 050 | More than &1 hits in category &2 (system &3) | 
| 051 | Type &1 does not exist | 
| 052 | No entry exists in Customizing table for catalog &1 | 
| 053 | Selection option &1 is not permitted | 
| 054 | Upper interval limit &1 is not permitted | 
| 055 | Remote access to catalog &1 in system &2 is not possible | 
| 056 | Code selection &1 is not permitted (input template 'n_nnnnnnnn_nnnn') | 
| 057 | Search query for object category &1 is not supported in system &2 | 
| 058 | & | 
| 059 | Internal error; no category was specified for the search | 
| 060 | Code you are searching for cannot be interpreted | 
| 061 | ID you are searching for cannot be interpreted | 
| 062 | Invalid result structure | 
| 063 | Specify the ID in full at least up to and including the separator | 
| 064 | Internal error: No search group specified | 
| 065 | Root node of BOPF object &1 does not contain action &2 | 
| 066 | Filter value &1 is invalid | 
| 067 | Categ. &1: Search in system &2 only supported for fully specified objects | 
| 068 | Search canceled for category &1; error text: &2 | 
| 069 | Number of hits was restricted to &2 owing to settings for type &1 | 
| 070 | Search query results in more hits than the max. defined for the worklist | 
| 071 | Some search queries are not supported; see 'Logs -> Worklist' | 
| 072 | Selection for field &1 is too unspecific (&2 hits) | 
| 073 | Additional input structure of type &1 may be missing in mapping | 
| 074 | Default navigation was executed for this workflow | 
| 075 | Category &2: No valid notification type specified for search in system &1 | 
| 101 | Error during mapping call &1 | 
| 102 | Error when saving shared object memory | 
| 103 | Error when reading shared memory | 
| 104 | Error reading remote data into shared memory | 
| 105 | Master data incomplete owing to poor performance | 
| 106 | System &1 does not support access to person responsible in list | 
| 108 | Table &1 could not be read via RFC connection &2 | 
| 109 | Mapping for &1 (data element &2), list agency &3 is not possible | 
| 110 | Value &4 for &1 (data element &2), list agency &3 is not to be mapped | 
| 111 | Error when accessing object model | 
| 112 | No. of target systems for key mapping to object category &1 is not 1 | 
| 113 | BOL component set &1 is not available | 
| 121 | Use the jump to the FMEA action and navigate from there | 
| 122 | Navigation for this category from the worklist overview | 
| 130 | Activity &1 completed | 
| 131 | Activity &1 set in process | 
| 132 | Issue &1 completed | 
| 133 | Issue &1 set in process | 
| 134 | Activity &1 could not be completed | 
| 135 | Activity &1 could not be set in process | 
| 136 | Method for status change in system &1 not available | 
| 137 | Activity &1 is canceled and cannot therefore be copied | 
| 138 | Activity &1 has a valid copy &2 and cannot therefore be copied | 
| 139 | Activity &1 cannot be copied; prerequisites are not fulfilled | 
| 170 | Business partner &1 replaced by &2 in issue &3 | 
| 171 | Business partner &1 replaced by &2 in defect &3 | 
| 172 | Business partner &1 replaced by &2 in cause &3 | 
| 173 | Business partner &1 replaced by &2 in effect &3 | 
| 174 | Business partner &1 replaced by &2 in activity &3 | 
| 175 | Business partner &1 does not exist | 
| 176 | Default partner &1 replaced by &2 for issue type &3 | 
| 177 | Change entries in table for default partners | 
| 178 | Replace business partner in transaction data | 
| 179 | New business partner must not be identical to old business partner | 
| 180 | Business partner &1 was not replaced in issue &3 | 
| 181 | Business partner &1 was not replaced in defect &3 | 
| 182 | Business partner &1 was not replaced in cause &3 | 
| 183 | Business partner &1 was not replaced in effect &3 | 
| 184 | Business partner &1 was not replaced in activity &3 | 
| 185 | Default partner &1 replaced by &2 for activity template &3 | 
| 200 | Quality issue &1 is not available | 
| 201 | Quality activity &1 does not exist | 
| 202 | Subitem &1 does not exist | 
| 203 | System &1 is used in client &2 from &3 to &4 for worklist | 
| 204 | System &1 is used in client &2 from &3 to &4 for object ref. in issue | 
| 205 | System &1 is used in client &2 from &3 to &4 for object ref. in activity | 
| 206 | System &1 used in client &2 from &3 to &4 as target of follow-up action | 
| 207 | &1 belongs to issue &2; entry was corrected accordingly | 
| 208 | Defect &1 belongs to issue &2; entry was corrected accordingly | 
| 209 | Cause &1 belongs to issue &2; entry was corrected accordingly | 
| 210 | Effect &1 belongs to issue &2; entry was corrected accordingly | 
| 211 | ID &1 identifies an issue and not a subissue | 
| 248 | Simulation failed; see log | 
| 249 | Simulation successful; see log | 
| 250 | Customizing changes failed; see log | 
| 251 | Customizing changes successful; see log | 
| 252 | Reference system for object type &1 was changed to &2 | 
| 253 | Logical system &1 for object category &2 was added | 
| 254 | Wizard was executed in simulation mode | 
| 255 | Access to object type via two different object categories not permitted | 
| 256 | Reference system for object type &1 already exists in Customizing | 
| 257 | You already selected a reference system for object type &1 | 
| 258 | Error when changing the transport request &1 | 
| 259 | Transport request &1 changed | 
| 260 | Mapping type for object type &1 is not ID mapping | 
| 271 | No authorization to process issue for: &3 (issue type &1, group &2) | 
| 300 | Your request to unsubscribe was forwarded to the person responsible |