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