# |
Message |
Message Short Text |
Documentation status |
Authorization check |
1 |
000 |
(to) |
The short text describes the object sufficiently |
|
2 |
001 |
&1 &2 &3 &4 |
The short text describes the object sufficiently |
|
3 |
002 |
Canceled by user |
The short text describes the object sufficiently |
|
4 |
003 |
&1 |
The short text describes the object sufficiently |
|
5 |
004 |
Traces started |
The short text describes the object sufficiently |
|
6 |
005 |
All |
The short text describes the object sufficiently |
|
7 |
006 |
Traces of function module &1 started |
The short text describes the object sufficiently |
|
8 |
007 |
Traces of function module &1 ended |
The short text describes the object sufficiently |
|
9 |
009 |
Traces of method &1 started |
The short text describes the object sufficiently |
|
10 |
010 |
Traces of method &1 ended |
The short text describes the object sufficiently |
|
11 |
012 |
Traces ended |
The short text describes the object sufficiently |
|
12 |
013 |
Error while reading OLAP message handler |
The short text describes the object sufficiently |
|
13 |
014 |
Playing the trace &1 |
The short text describes the object sufficiently |
|
14 |
015 |
Processing of traces &1 started |
The short text describes the object sufficiently |
|
15 |
016 |
Execution of function module &1 |
The short text describes the object sufficiently |
|
16 |
017 |
Processing of function module &1 started |
The short text describes the object sufficiently |
|
17 |
018 |
Processing of function module &1 ended |
The short text describes the object sufficiently |
|
18 |
019 |
Execution of method &1 |
The short text describes the object sufficiently |
|
19 |
020 |
Processing of method &1 started |
The short text describes the object sufficiently |
|
20 |
021 |
Processing of method &1 ended |
The short text describes the object sufficiently |
|
21 |
022 |
OLAP message handler messages |
The short text describes the object sufficiently |
|
22 |
023 |
Processing ended |
The short text describes the object sufficiently |
|
23 |
024 |
Cancel because no trace loaded |
The short text describes the object sufficiently |
|
24 |
025 |
Error in basic module |
The short text describes the object sufficiently |
|
25 |
026 |
Function module &1 (item &2) was not ended correctly |
The short text describes the object sufficiently |
|
26 |
027 |
Module &1 (position &2) triggered an exception with number &3 |
The short text describes the object sufficiently |
|
27 |
028 |
Module &1 (position &2) executed successfully |
The short text describes the object sufficiently |
|
28 |
029 |
Critical errors: Function cannot be executed |
The short text describes the object sufficiently |
|
29 |
030 |
Internal error in &1; reason/SUBRC: &2 |
Space: object requires documentation |
|
30 |
031 |
No trace selected |
The short text describes the object sufficiently |
|
31 |
032 |
Trace ID already exists |
The short text describes the object sufficiently |
|
32 |
033 |
No results found |
The short text describes the object sufficiently |
|
33 |
034 |
Trace deleted |
The short text describes the object sufficiently |
|
34 |
035 |
Trace not found |
The short text describes the object sufficiently |
|
35 |
036 |
Unexpected answer |
The short text describes the object sufficiently |
|
36 |
037 |
Trace saved |
The short text describes the object sufficiently |
|
37 |
038 |
Memory error |
The short text describes the object sufficiently |
|
38 |
039 |
Error during trace conversion - function terminated |
The short text describes the object sufficiently |
|
39 |
040 |
Only traces of type CATT (or more specific) can be processed |
The short text describes the object sufficiently |
|
40 |
041 |
Tree display could not be created |
The short text describes the object sufficiently |
|
41 |
042 |
Tree display could not be adapted |
The short text describes the object sufficiently |
|
42 |
043 |
Save not possible, trace reference does not exist |
The short text describes the object sufficiently |
|
43 |
044 |
Save not possible, package reference does not exist |
The short text describes the object sufficiently |
|
44 |
045 |
Trace could not be loaded |
The short text describes the object sufficiently |
|
45 |
046 |
Invalid entry for call position |
The short text describes the object sufficiently |
|
46 |
047 |
Invalid entry for check position |
The short text describes the object sufficiently |
|
47 |
048 |
The package could not be deleted due to an error |
The short text describes the object sufficiently |
|
48 |
049 |
Package deleted successfully |
The short text describes the object sufficiently |
|
49 |
050 |
You are not authorized for this action (&1, object &2, aktivity &3) |
The short text describes the object sufficiently |
|
50 |
051 |
Trace &1 is locked |
The short text describes the object sufficiently |
|
51 |
052 |
Test package &1 is currently locked |
The short text describes the object sufficiently |
|
52 |
053 |
Test job &1 is currently locked |
The short text describes the object sufficiently |
|
53 |
054 |
Test package ID already exists |
The short text describes the object sufficiently |
|
54 |
055 |
Test job ID already exists |
The short text describes the object sufficiently |
|
55 |
056 |
Unable to save; job reference does not exist |
The short text describes the object sufficiently |
|
56 |
057 |
You are not authorized to jump to this transaction |
The short text describes the object sufficiently |
|
57 |
058 |
Only CATT traces can be edited |
The short text describes the object sufficiently |
|
58 |
059 |
Only standard traces cannot be edited with the wizard |
The short text describes the object sufficiently |
|
59 |
060 |
User does not exist |
The short text describes the object sufficiently |
|
60 |
061 |
Executing (authorization) user does not exist |
The short text describes the object sufficiently |
|
61 |
062 |
User already activated |
The short text describes the object sufficiently |
|
62 |
063 |
User '&1' is activated for trace recording |
The short text describes the object sufficiently |
|
63 |
064 |
User '&1' was deactivated for trace recording |
The short text describes the object sufficiently |
|
64 |
065 |
User '&1' is not activated for trace recording |
The short text describes the object sufficiently |
|
65 |
066 |
Row &1 |
The short text describes the object sufficiently |
|
66 |
067 |
Content of '&1' |
The short text describes the object sufficiently |
|
67 |
068 |
User '&1' activated |
The short text describes the object sufficiently |
|
68 |
069 |
User '&1' does not have authorization to record traces |
The short text describes the object sufficiently |
|
69 |
070 |
Header data for the trace '&1' saved succesfully |
The short text describes the object sufficiently |
|
70 |
071 |
Saving the header data of the trace '&1' failed |
The short text describes the object sufficiently |
|
71 |
072 |
Description of trace '&1' saved successfully |
The short text describes the object sufficiently |
|
72 |
073 |
Save of description of trace '&1' incorrect |
The short text describes the object sufficiently |
|
73 |
074 |
Sequence descriptions (number &1) of trace '&2' saved successfully |
The short text describes the object sufficiently |
|
74 |
075 |
Save of sequence descriptions of trace '&1' incorrect |
The short text describes the object sufficiently |
|
75 |
076 |
Header data of CATT trace '&1' saved successfully |
The short text describes the object sufficiently |
|
76 |
077 |
Save of header data for CATT trace '&1' incorrect |
The short text describes the object sufficiently |
|
77 |
078 |
Test topics (number &1) of trace '&2' saved successfully |
The short text describes the object sufficiently |
|
78 |
079 |
Save of test topics for trace '&1' incorrect |
The short text describes the object sufficiently |
|
79 |
080 |
Data objects for checking the trace '&1' saved successfully |
The short text describes the object sufficiently |
|
80 |
081 |
Save of data objects for check of trace '&1' incorrect |
The short text describes the object sufficiently |
|
81 |
082 |
Test reference data of trace '&1' (variant &2) saved successfully |
The short text describes the object sufficiently |
|
82 |
083 |
Save of test reference data for trace '&1' (variant &2) incorrect |
The short text describes the object sufficiently |
|
83 |
084 |
Check instance not connected |
The short text describes the object sufficiently |
|
84 |
085 |
Context of program object or CATT trace does not exist |
The short text describes the object sufficiently |
|
85 |
086 |
Position number of check for program module '&1' not found |
The short text describes the object sufficiently |
|
86 |
087 |
No parameter for checking found at position &1 |
The short text describes the object sufficiently |
|
87 |
088 |
Test reference data for check position &1 loaded successfully |
The short text describes the object sufficiently |
|
88 |
089 |
Test reference data for variant '&1' loaded successfully |
The short text describes the object sufficiently |
|
89 |
090 |
Test reference data for variant '&1' loaded with errors |
The short text describes the object sufficiently |
|
90 |
091 |
Check instance is bound |
The short text describes the object sufficiently |
|
91 |
092 |
Test package saved |
The short text describes the object sufficiently |
|
92 |
093 |
Test job saved |
The short text describes the object sufficiently |
|
93 |
094 |
Sequence descriptions are possibly inconsistent |
The short text describes the object sufficiently |
|
94 |
095 |
Test job with no assigned test package cannot be saved |
The short text describes the object sufficiently |
|
95 |
096 |
Unable to process function module &1 (&2) due to invalid interface |
The short text describes the object sufficiently |
|
96 |
097 |
Unable to process method &1 (&2) due to invalid interface |
The short text describes the object sufficiently |
|
97 |
098 |
Reference data variant already exists |
The short text describes the object sufficiently |
|
98 |
099 |
Select a row |
The short text describes the object sufficiently |
|
99 |
100 |
Test objects of trace '&1' ('&2') locked. Execution postponed |
The short text describes the object sufficiently |
|
100 |
101 |
Problems while locking the test objects of trace '&1' ('&2') |
The short text describes the object sufficiently |
|
101 |
102 |
Execution of trace '&1' (play variant '&2') started |
The short text describes the object sufficiently |
|
102 |
103 |
Execution of trace '&1' (play variant '&2') finished successfully |
The short text describes the object sufficiently |
|
103 |
104 |
Problems while executing trace '&1' (play variant '&2') |
The short text describes the object sufficiently |
|
104 |
105 |
Test objects of trace '&1' ('&2') locked successfully |
The short text describes the object sufficiently |
|
105 |
106 |
Trace job '&1' started |
The short text describes the object sufficiently |
|
106 |
107 |
Trace '&1' (play variant '&2') executed successfully |
The short text describes the object sufficiently |
|
107 |
108 |
Trace '&1' (play variant '&2') temporarily postponed |
The short text describes the object sufficiently |
|
108 |
109 |
Trace '&1' (play variant '&2') terminated! |
The short text describes the object sufficiently |
|
109 |
110 |
Error during asynchronous RFC call of trace '&1' ('&2') |
The short text describes the object sufficiently |
|
110 |
111 |
Session terminated while executing of trace '&1' ('&2') |
The short text describes the object sufficiently |
|
111 |
112 |
Result parameter of test not set! |
The short text describes the object sufficiently |
|
112 |
113 |
User '&1' is not authorized to execute traces |
The short text describes the object sufficiently |
|
113 |
114 |
Trace is cannot be interpreted as CATT trace. Processing terminated |
The short text describes the object sufficiently |
|
114 |
115 |
No test reference data for variant '&1' present at test position &2 |
The short text describes the object sufficiently |
|
115 |
116 |
Position number of check for call position &1 not found! |
The short text describes the object sufficiently |
|
116 |
117 |
Problems while unlocking of test objects for trace '&1' ('&2') |
The short text describes the object sufficiently |
|
117 |
118 |
No trace package selected |
The short text describes the object sufficiently |
|
118 |
119 |
Trace package &1 does not yet exist |
The short text describes the object sufficiently |
|
119 |
120 |
Trace package &1 exists |
The short text describes the object sufficiently |
|
120 |
121 |
Test results (number '&1') succesfully saved |
The short text describes the object sufficiently |
|
121 |
122 |
Error occurred while saving the test results |
The short text describes the object sufficiently |
|
122 |
123 |
Trace is not interpretable as OLAP trace; processing terminated |
The short text describes the object sufficiently |
|
123 |
124 |
Position number is invalid |
The short text describes the object sufficiently |
|
124 |
125 |
Replacement value missing, function cannot be performed |
The short text describes the object sufficiently |
|
125 |
126 |
Dispay for complex structures not possible |
The short text describes the object sufficiently |
|
126 |
127 |
Data object or parameter not found in tree |
The short text describes the object sufficiently |
|
127 |
128 |
No data object created, no data can be displayed |
The short text describes the object sufficiently |
|
128 |
130 |
Mode terminated during execution |
The short text describes the object sufficiently |
|
129 |
131 |
Test of CATT trace was successful |
The short text describes the object sufficiently |
|
130 |
132 |
No reference data for test exists |
The short text describes the object sufficiently |
|
131 |
133 |
Position number of check not found |
The short text describes the object sufficiently |
|
132 |
134 |
Data structures for test position &1 |
The short text describes the object sufficiently |
|
133 |
135 |
&1 - Test of CATT trace '&2' ('&3') started |
The short text describes the object sufficiently |
|
134 |
136 |
&1 - Test of CATT trace '&2' ('&3') ended |
The short text describes the object sufficiently |
|
135 |
137 |
Test run of trace job '&1' started; number of tests: &2 |
The short text describes the object sufficiently |
|
136 |
138 |
Test not successful; data contents changed |
The short text describes the object sufficiently |
|
137 |
139 |
Log GUID: &1 |
The short text describes the object sufficiently |
|
138 |
140 |
Trace with ID '&1' deleted successfully |
The short text describes the object sufficiently |
|
139 |
141 |
Errors occurred during processing; unable to delete trace with ID '&1' |
The short text describes the object sufficiently |
|
140 |
142 |
Select a valid element |
The short text describes the object sufficiently |
|
141 |
143 |
Element '&1' is not intended for a selection |
The short text describes the object sufficiently |
|
142 |
144 |
Copying of trace '&1' successful |
The short text describes the object sufficiently |
|
143 |
145 |
Error occurred while copying trace '&1'. Process terminated |
The short text describes the object sufficiently |
|
144 |
146 |
Test reference data variant '&1' already exists |
The short text describes the object sufficiently |
|
145 |
147 |
Test reference data variant '&1' saved successfully |
The short text describes the object sufficiently |
|
146 |
148 |
Trace '&1' saved successfully |
The short text describes the object sufficiently |
|
147 |
149 |
Errors occurred while saving trace '&1'. Action terminated |
The short text describes the object sufficiently |
|
148 |
150 |
Data structure '&1' contains no data |
The short text describes the object sufficiently |
|
149 |
151 |
Error while saving variant '&1' |
The short text describes the object sufficiently |
|
150 |
153 |
Parameter table for object display empty |
The short text describes the object sufficiently |
|
151 |
154 |
Data object of check not available, &1 table cannot be created |
The short text describes the object sufficiently |
|
152 |
155 |
Warnings occurred while checking trace '&1' |
The short text describes the object sufficiently |
|
153 |
156 |
Copying of trace not possible. Trace &1 already exists |
The short text describes the object sufficiently |
|
154 |
157 |
Internal error occurred during action for item '&1' |
The short text describes the object sufficiently |
|
155 |
158 |
Error during verification: item &1, ID &2, cell (&3, &4) |
The short text describes the object sufficiently |
|
156 |
159 |
Successful verification of &1 data cells for item '&2' |
The short text describes the object sufficiently |
|
157 |
160 |
OLAP trace header data updated successfully |
The short text describes the object sufficiently |
|
158 |
161 |
OLAP trace verification data updated successfully |
The short text describes the object sufficiently |
|
159 |
162 |
Transformation from internal to reporting structure contains errors |
The short text describes the object sufficiently |
|
160 |
163 |
Test run for trace '&1' started. Trace mode: &2 |
The short text describes the object sufficiently |
|
161 |
164 |
&1 entries in InfoProvider '&2' enhanced or updated |
The short text describes the object sufficiently |
|
162 |
165 |
Trace '&1' terminated during verification run |
The short text describes the object sufficiently |
|
163 |
166 |
Trace '&1' ended verification run |
The short text describes the object sufficiently |
|
164 |
167 |
Verification run of trace '&1' with REF variant '&2' started |
The short text describes the object sufficiently |
|
165 |
168 |
Verification of item &1 |
The short text describes the object sufficiently |
|
166 |
169 |
Cells for item &1 verified successfully |
The short text describes the object sufficiently |
|
167 |
170 |
Verification query at cell (&1;&2) terminated |
The short text describes the object sufficiently |
|
168 |
171 |
Termination: Verification run of trace '&1' not executable due to errors |
The short text describes the object sufficiently |
|
169 |
172 |
Trace '&1' exported successfully |
The short text describes the object sufficiently |
|
170 |
173 |
Error while exporting trace '&1' |
The short text describes the object sufficiently |
|
171 |
174 |
Directory '&1' is not permitted |
The short text describes the object sufficiently |
|
172 |
175 |
Error during serialization |
The short text describes the object sufficiently |
|
173 |
176 |
Test object &1 (&2) of type &3 does not exist actively in system |
The short text describes the object sufficiently |
|
174 |
177 |
Trace ID '&1' is not unique; ID will be replaced by '&2' |
The short text describes the object sufficiently |
|
175 |
178 |
Error while saving call table |
The short text describes the object sufficiently |
|
176 |
179 |
Error while saving check table |
The short text describes the object sufficiently |
|
177 |
180 |
Export of trace '&1' |
The short text describes the object sufficiently |
|
178 |
181 |
Import of trace '&1' |
The short text describes the object sufficiently |
|
179 |
182 |
Trace '&1' imported successfully |
The short text describes the object sufficiently |
|
180 |
183 |
Error during import |
The short text describes the object sufficiently |
|
181 |
184 |
Trace file saved successfully with file name '&1' |
The short text describes the object sufficiently |
|
182 |
185 |
Trace serialized successfully |
The short text describes the object sufficiently |
|
183 |
186 |
Error during deserialization |
The short text describes the object sufficiently |
|
184 |
187 |
Trace deserialized successfully |
The short text describes the object sufficiently |
|
185 |
188 |
Trace (&1) to be imported already exists in system; no import performed |
The short text describes the object sufficiently |
|
186 |
189 |
Error while saving trace '&1' |
The short text describes the object sufficiently |
|
187 |
190 |
Application area: &1 |
The short text describes the object sufficiently |
|
188 |
191 |
Multiple selection for &1 |
The short text describes the object sufficiently |
|
189 |
192 |
&1 - Execution of trace '&2' ('&3') started |
The short text describes the object sufficiently |
|
190 |
193 |
&1 - Execution of trace '&2' ('&3') ended |
The short text describes the object sufficiently |
|
191 |
194 |
Restricted user &1 does not exist; execution ended |
The short text describes the object sufficiently |
|
192 |
195 |
Reference data recorded |
The short text describes the object sufficiently |
|
193 |
196 |
Error recording reference data |
The short text describes the object sufficiently |
|
194 |
200 |
Test of CATT trace '&1' (with run variant '&2') successful |
The short text describes the object sufficiently |
|
195 |
201 |
Test of CATT trace '&1' (with run variant '&2') not successful |
The short text describes the object sufficiently |
|
196 |
202 |
Check for step '&1' on &2 '&3' (position '&4') successful |
The short text describes the object sufficiently |
|
197 |
203 |
Check for step '&1' at &2 '&3' (position '&4') returns deviations |
The short text describes the object sufficiently |
|
198 |
204 |
Execution of step '&1' at &2 '&3' was incorrect |
The short text describes the object sufficiently |
|
199 |
205 |
Check of parameter '&1' shows no deviations |
The short text describes the object sufficiently |
|
200 |
206 |
Content of parameter &1 is different to reference data |
The short text describes the object sufficiently |
|
201 |
207 |
Component '&1' with ID '&2' returns '&3' deviations |
The short text describes the object sufficiently |
|
202 |
208 |
Component '&2' with ID '&2' returns a deviation |
The short text describes the object sufficiently |
|
203 |
209 |
Component '&1' with ID '&2' returns multiple deviations |
The short text describes the object sufficiently |
|
204 |
210 |
Row '&1' has different result values |
The short text describes the object sufficiently |
|
205 |
211 |
Parameter '&1' has at least one component with varying number of rows |
The short text describes the object sufficiently |
|
206 |
212 |
Component '&1': Current value (CATT) '&2' against reference va (REF) '&3' |
The short text describes the object sufficiently |
|
207 |
220 |
Error ID '&1' is invalid |
The short text describes the object sufficiently |
|
208 |
221 |
Attributes of error ID '&1' saved successfully |
The short text describes the object sufficiently |
|
209 |
222 |
Errors while saving error ID '&1' |
The short text describes the object sufficiently |
|
210 |
223 |
Error ID '&1' is locked by user '&2' |
The short text describes the object sufficiently |
|
211 |
224 |
Error ID '&1' does not exist |
The short text describes the object sufficiently |
|
212 |
225 |
Error ID '&1' already exists |
The short text describes the object sufficiently |
|
213 |
226 |
&1 entries enchanced in message archive |
The short text describes the object sufficiently |
|
214 |
227 |
&1 active errors determined and stored for test job '&2' |
The short text describes the object sufficiently |
|
215 |
228 |
&1 new errors enhanced and archived for reporting |
The short text describes the object sufficiently |
|
216 |
229 |
Evaluation entries (amount: &1) saved successfully |
The short text describes the object sufficiently |
|
217 |
230 |
No entries enhanced in message archive |
The short text describes the object sufficiently |
|
218 |
231 |
No active errors determined |
The short text describes the object sufficiently |
|
219 |
232 |
No new errors enhanced |
The short text describes the object sufficiently |
|
220 |
233 |
Internal error while saving evaluation entries |
The short text describes the object sufficiently |
|
221 |
234 |
Evaluation terminated: DataStore object '&1' does not exist actively |
The short text describes the object sufficiently |
|
222 |
235 |
Saving not possible: Evaluation did not complete fully |
The short text describes the object sufficiently |
|
223 |
236 |
No test unit for error assignment selected |
The short text describes the object sufficiently |
|
224 |
237 |
Database problem |
The short text describes the object sufficiently |
|
225 |
238 |
Internal termination at test item &1 |
The short text describes the object sufficiently |
|
226 |
239 |
Initial check structures for test item &1 |
The short text describes the object sufficiently |
|
227 |
240 |
CATT structure not fixed for test item &1 |
The short text describes the object sufficiently |
|
228 |
241 |
Reference structure not fixed for test item &1 |
The short text describes the object sufficiently |
|
229 |
242 |
Checking data consistency of trace '&1' |
The short text describes the object sufficiently |
|
230 |
243 |
Executing trace '&1' |
The short text describes the object sufficiently |
|
231 |
244 |
Item &1: CATT data and reference data are consistent |
The short text describes the object sufficiently |
|
232 |
245 |
Item &1: CATT data and reference data are not consistent |
The short text describes the object sufficiently |
|
233 |
246 |
Texts for characteristic &1 loaded successfully |
The short text describes the object sufficiently |
|
234 |
247 |
BI object '&1' is not active in the system |
The short text describes the object sufficiently |
|
235 |
248 |
It is not necessary to update the data in BI object '&1' |
The short text describes the object sufficiently |
|
236 |
249 |
Test evaluation for test run '&1' saved successfully |
The short text describes the object sufficiently |
|
237 |
250 |
Activation of evaluation of test run '&1' scheduled successfully |
The short text describes the object sufficiently |
|
238 |
251 |
Evaluation of test run '&1' not yet complete |
The short text describes the object sufficiently |
|
239 |
252 |
Activation of test run '&1' is in progress |
The short text describes the object sufficiently |
|
240 |
253 |
Activation of test run '&1' finished with errors |
The short text describes the object sufficiently |
|
241 |
254 |
Activation of test run '&1' finished successfully |
The short text describes the object sufficiently |
|
242 |
255 |
Activation of test run '&1' scheduled |
The short text describes the object sufficiently |
|
243 |
256 |
Activation of test run '&1' released |
The short text describes the object sufficiently |
|
244 |
257 |
Activation of test run '&1' terminated |
The short text describes the object sufficiently |
|
245 |
258 |
Activation of test run '&1' ready |
The short text describes the object sufficiently |
|
246 |
259 |
Cannot activate test run '&1'; version does not exist |
The short text describes the object sufficiently |
|
247 |
260 |
&1 text entries for characteristic '&2' have to be updated |
The short text describes the object sufficiently |
|
248 |
261 |
&1 attribute entries for characteristic '&2' have to be updated |
The short text describes the object sufficiently |
|
249 |
262 |
Temporary store of test run '&1' deleted successfully |
The short text describes the object sufficiently |
|
250 |
263 |
Test run is already being evaluated by user '&1' |
The short text describes the object sufficiently |
|
251 |
264 |
Test run '&1' locked successfully |
The short text describes the object sufficiently |
|
252 |
265 |
Test run '&1' unlocked successfully |
The short text describes the object sufficiently |
|
253 |
266 |
Test run '&1' successfully loaded from temporary store |
The short text describes the object sufficiently |
|
254 |
267 |
Cell (&1,&2) for item &3 (data provider &1) verified successfully |
The short text describes the object sufficiently |
|
255 |
268 |
Verification problems for cell (&1,&2) for item &3 (data provider &1) |
The short text describes the object sufficiently |
|
256 |
269 |
Number of new requests collected: &1 |
The short text describes the object sufficiently |
|
257 |
270 |
Number of transported objects determined: &1 |
The short text describes the object sufficiently |
|
258 |
271 |
InfoCube &1 is not compatible with standard InfoCube 0RSTT_C04 |
The short text describes the object sufficiently |
|
259 |
272 |
SCOV variant &1 does not exist |
The short text describes the object sufficiently |
|
260 |
273 |
InfoCube 0RSTT_C04 cannot be used for this evaluation variant |
The short text describes the object sufficiently |
|
261 |
274 |
Use copy of InfoCube 0RSTT_C04 |
The short text describes the object sufficiently |
|
262 |
275 |
&1 evaluation entries successfully updated to InfoCube &2 |
The short text describes the object sufficiently |
|
263 |
276 |
No new evaluation entries found |
The short text describes the object sufficiently |
|
264 |
277 |
Error while updating data to BW object &1 |
The short text describes the object sufficiently |
|
265 |
278 |
Time details for job scheduling are invalid; scheduling will not occur |
The short text describes the object sufficiently |
|
266 |
297 |
&1 is not a valid read mode |
The short text describes the object sufficiently |
|
267 |
298 |
&1 is not a valid cache mode |
The short text describes the object sufficiently |
|
268 |
299 |
&1 is not a valid aggregate mode |
The short text describes the object sufficiently |
|
269 |
300 |
Test package ID already exists |
The short text describes the object sufficiently |
|
270 |
301 |
Test package not found |
The short text describes the object sufficiently |
|
271 |
307 |
No test job selected |
The short text describes the object sufficiently |
|
272 |
308 |
Unable to delete job due to error |
The short text describes the object sufficiently |
|
273 |
309 |
Job deleted successfully |
The short text describes the object sufficiently |
|
274 |
310 |
Test job ID already exists |
The short text describes the object sufficiently |
|
275 |
311 |
Test job not found |
The short text describes the object sufficiently |
|
276 |
312 |
Test job &1 does not yet exist |
The short text describes the object sufficiently |
|
277 |
313 |
Test job &1 exists |
The short text describes the object sufficiently |
|
278 |
314 |
Test job &1 saved and scheduled successfully |
The short text describes the object sufficiently |
|
279 |
315 |
Test job &1 saved successfully |
The short text describes the object sufficiently |
|
280 |
316 |
Unable to save test job &1 successfully |
The short text describes the object sufficiently |
|
281 |
317 |
Test job &1 is not permitted |
The short text describes the object sufficiently |
|
282 |
318 |
Trace type &1 not permitted for this processing |
The short text describes the object sufficiently |
|
283 |
319 |
Job definition terminated; unable to create job |
The short text describes the object sufficiently |
|
284 |
320 |
Job definition terminated; illegal job parameter |
The short text describes the object sufficiently |
|
285 |
321 |
Job definition terminated; illegal job name |
The short text describes the object sufficiently |
|
286 |
322 |
Error during job scheduling |
The short text describes the object sufficiently |
|
287 |
323 |
Error while ending job definition |
The short text describes the object sufficiently |
|
288 |
324 |
Error while deleting batch job '&1' (number '&2'); job is active |
The short text describes the object sufficiently |
|
289 |
325 |
Error while deleting batch job '&1' (number '&2') |
The short text describes the object sufficiently |
|
290 |
326 |
Batch job '&1' (number '&2') deleted successfully |
The short text describes the object sufficiently |
|
291 |
327 |
Batch job '&1' (number '&2') released successfully |
The short text describes the object sufficiently |
|
292 |
328 |
Error while deleting trace job |
The short text describes the object sufficiently |
|
293 |
329 |
Trace job (including batch job) deleted successfully |
The short text describes the object sufficiently |
|
294 |
330 |
Saving of header data of test job failed |
The short text describes the object sufficiently |
|
295 |
331 |
Test job '&1' (number '&2') successfully released for batch |
The short text describes the object sufficiently |
|
296 |
332 |
Test run with log GUID '&1' already analyzed |
The short text describes the object sufficiently |
|
297 |
333 |
Texts for characteristic &1 loaded successfully |
The short text describes the object sufficiently |
|
298 |
334 |
Error while loading texts for characteristic &1 |
The short text describes the object sufficiently |
|
299 |
335 |
Invalid input parameters |
The short text describes the object sufficiently |
|
300 |
336 |
Attributes for characteristic &1 loaded successfully |
The short text describes the object sufficiently |
|
301 |
337 |
Error while loading attributes for characteristic &1 |
The short text describes the object sufficiently |
|
302 |
338 |
Test request &1 cannot be deleted; no authorization |
The short text describes the object sufficiently |
|
303 |
339 |
Test request &1 deleted successfully |
The short text describes the object sufficiently |
|
304 |
340 |
Error job &1 already exists |
The short text describes the object sufficiently |
|
305 |
341 |
Error job &1 created successfully |
The short text describes the object sufficiently |
|
306 |
342 |
Invalid process mode |
The short text describes the object sufficiently |
|
307 |
343 |
Trace job &1 currently contains no traces |
The short text describes the object sufficiently |
|
308 |
350 |
No error parameters changed |
The short text describes the object sufficiently |
|
309 |
351 |
Error ID '&1' locked by user '&2' |
The short text describes the object sufficiently |
|
310 |
352 |
New error saved successfully with ID '&1' |
The short text describes the object sufficiently |
|
311 |
353 |
Error with ID '&1' saved successfully |
The short text describes the object sufficiently |
|
312 |
360 |
Test request with ID '&1' saved successfully |
The short text describes the object sufficiently |
|
313 |
361 |
Error while saving test request with ID '&1' |
The short text describes the object sufficiently |
|
314 |
362 |
Test request with ID '&1' is being edited by user &2 |
The short text describes the object sufficiently |
|
315 |
363 |
Assigning ID '&1' to test request |
The short text describes the object sufficiently |
|
316 |
364 |
Header data for test request updated successfully |
The short text describes the object sufficiently |
|
317 |
365 |
Texts for test request updated successfully |
The short text describes the object sufficiently |
|
318 |
366 |
No attributes changed |
The short text describes the object sufficiently |
|
319 |
367 |
Test request with ID '&1' does not exist |
The short text describes the object sufficiently |
|
320 |
368 |
Status of test request '&1' changed to 'Completed' |
The short text describes the object sufficiently |
|
321 |
369 |
Status of test request '&1' changed to 'In Processing' |
The short text describes the object sufficiently |
|
322 |
370 |
Test request with ID '&1' is already being edited by user &2 |
The short text describes the object sufficiently |
|
323 |
371 |
Analysis run for test coverage started. Number of individual analyses: &1 |
The short text describes the object sufficiently |
|
324 |
372 |
No trace available for analysis |
The short text describes the object sufficiently |
|
325 |
373 |
Analysis of test coverage is currently locked by user '&1' |
The short text describes the object sufficiently |
|
326 |
374 |
Analysis run for test coverage locked successfully |
The short text describes the object sufficiently |
|
327 |
375 |
Basis coverage analysis is not fully configured |
The short text describes the object sufficiently |
|
328 |
376 |
Analysis terminated; errors in basis coverage analysis |
The short text describes the object sufficiently |
|
329 |
377 |
&1/&2: Test coverage analysis started: trace '&3' - play variant '&4' |
The short text describes the object sufficiently |
|
330 |
378 |
Test coverage analysis terminated: trace '&1' - play variant '&2' |
The short text describes the object sufficiently |
|
331 |
379 |
Test coverage analysis executed: trace '&1' - play variant '&2' |
The short text describes the object sufficiently |
|
332 |
380 |
Number of updated analysis versions for trace: &1 |
The short text describes the object sufficiently |
|
333 |
381 |
Number of updated program object entries: &1 |
The short text describes the object sufficiently |
|
334 |
382 |
Trace package: &1 |
The short text describes the object sufficiently |
|
335 |
383 |
Analysis run for test coverage unlocked successfully |
The short text describes the object sufficiently |
|
336 |
384 |
Trace tool has not yet been assigned a test group |
The short text describes the object sufficiently |
|
337 |
385 |
Test group &1 set up in trace tool is not active |
The short text describes the object sufficiently |
|
338 |
386 |
Test group &1 has not been assigned users |
The short text describes the object sufficiently |
|
339 |
387 |
Coverage analysis configured fully |
The short text describes the object sufficiently |
|
340 |
388 |
Test group &1 assigned successfully to trace tool |
The short text describes the object sufficiently |
|
341 |
389 |
Trace: &1 |
The short text describes the object sufficiently |
|
342 |
390 |
&1 entries successfully added to evaluation archive for test coverage |
The short text describes the object sufficiently |
|
343 |
391 |
Processing terminated; too many failed attempts |
The short text describes the object sufficiently |
|
344 |
392 |
Internal error during document processing of characteristic value &1 (&2) |
The short text describes the object sufficiently |
|
345 |
393 |
&1 documents from characteristic &2 updated successfully |
The short text describes the object sufficiently |
|
346 |
394 |
Update run for object &1 terminated |
The short text describes the object sufficiently |
|
347 |
395 |
No object selected |
The short text describes the object sufficiently |
|
348 |
396 |
Release job for update run |
The short text describes the object sufficiently |
|
349 |
397 |
No tests available; status changed to 'in Processing' |
The short text describes the object sufficiently |
|
350 |
398 |
Support package information updated |
The short text describes the object sufficiently |
|
351 |
399 |
Buffer test request statuses locked; additions not possible |
The short text describes the object sufficiently |
|
352 |
400 |
Buffer for test request statuses modified successfully |
The short text describes the object sufficiently |
|
353 |
401 |
&1 entries deleted successfully from buffer for test request statuses |
The short text describes the object sufficiently |
|
354 |
402 |
Cannot serialize hierarchy &1 for characteristic &2 |
The short text describes the object sufficiently |
|
355 |
403 |
Hierarchy &1 for characteristic &2 serialized successfully |
The short text describes the object sufficiently |
|
356 |
404 |
Texts for characteristic &1 serialized successfully |
The short text describes the object sufficiently |
|
357 |
405 |
Attributes for characteristic &1 serialized successfully |
The short text describes the object sufficiently |
|
358 |
406 |
Cannot serialize texts for characteristic &2 |
The short text describes the object sufficiently |
|
359 |
407 |
Cannot serialized attributes for characteristic &2 |
The short text describes the object sufficiently |
|
360 |
408 |
Transaction data for InfoProvider &1 serialized successfully |
The short text describes the object sufficiently |
|
361 |
409 |
Cannot serialize transaction data for InfoProvider &1 |
The short text describes the object sufficiently |
|
362 |
410 |
Cannot deserialize hierarchy &1 for characteristic &2 |
The short text describes the object sufficiently |
|
363 |
411 |
Hierarchy &1 for characteristic &2 deserialized successfully |
The short text describes the object sufficiently |
|
364 |
412 |
Texts for characteristic &1 deserialized successfully |
The short text describes the object sufficiently |
|
365 |
413 |
Attributes for characteristic &1 deserialized successfully |
The short text describes the object sufficiently |
|
366 |
414 |
Cannot deserialize texts for characteristic &2 |
The short text describes the object sufficiently |
|
367 |
415 |
Cannot deserialize attributes for characteristic &2 |
The short text describes the object sufficiently |
|
368 |
416 |
Transaction data for InfoProvider &1 deserialized successfully |
The short text describes the object sufficiently |
|
369 |
417 |
Cannot deserialize transaction data for InfoProvider &1 |
The short text describes the object sufficiently |
|
370 |
418 |
Data for InfoProvider &1 exported successfully |
The short text describes the object sufficiently |
|
371 |
419 |
Error while exporting data for InfoProvider &1 |
The short text describes the object sufficiently |
|
372 |
420 |
Data for InfoProvider &1 imported successfully |
The short text describes the object sufficiently |
|
373 |
421 |
Error while importing data for InfoProvider &1 |
The short text describes the object sufficiently |
|
374 |
422 |
Structure to be imported from object &1 is not compatible |
The short text describes the object sufficiently |
|
375 |
423 |
Hierarchy &1 for characteristic &1 already exsits. No data loaded |
The short text describes the object sufficiently |
|
376 |
424 |
Structure to be imported from object &1 (&2) is not compatible |
The short text describes the object sufficiently |
|
377 |
425 |
Only standard traces with activation for test generation can be edited |
The short text describes the object sufficiently |
|
378 |
426 |
Internal error: cannot save file &1 |
The short text describes the object sufficiently |
|
379 |
427 |
Internal error: cannot load file &1 |
The short text describes the object sufficiently |
|
380 |
428 |
Error during serialization of check data from position &1 (&2) |
The short text describes the object sufficiently |
|
381 |
429 |
Error during serialization of check parameters from position &1 (&2) |
The short text describes the object sufficiently |
|
382 |
430 |
Export of test data from position &1 failed |
The short text describes the object sufficiently |
|
383 |
431 |
Export of check parameters from position &1 failed |
The short text describes the object sufficiently |
|
384 |
432 |
Export of trace parameters for trace &1 failed |
The short text describes the object sufficiently |
|
385 |
433 |
Import of check data from position &1 failed |
The short text describes the object sufficiently |
|
386 |
434 |
Import of check parameters from position &1 failed |
The short text describes the object sufficiently |
|
387 |
435 |
Import of trace parameters failed |
The short text describes the object sufficiently |
|
388 |
436 |
Deserialization of check data from position &1 (&2) failed |
The short text describes the object sufficiently |
|
389 |
437 |
Deserialization of check parameters from position &1 (&2) failed |
The short text describes the object sufficiently |
|
390 |
438 |
Export of test reference data failed |
The short text describes the object sufficiently |
|
391 |
439 |
Import of test reference data failed |
The short text describes the object sufficiently |
|
392 |
440 |
Trace &1 cannot be executed on portal |
The short text describes the object sufficiently |
|
393 |
441 |
No execution authorization for restricted user &1 |
The short text describes the object sufficiently |
|
394 |
442 |
&1 error IDs updated to status 'Corrected' |
The short text describes the object sufficiently |
|
395 |
443 |
&1 error IDs updated to status 'In Processing' |
The short text describes the object sufficiently |
|
396 |
444 |
Responsible person with user name '&1' does not exist |
The short text describes the object sufficiently |
|
397 |
445 |
Export error for object &1 (&2); error code: &3 |
The short text describes the object sufficiently |
|
398 |
446 |
Object &1 (&2) exported successfully |
The short text describes the object sufficiently |
|
399 |
447 |
Import error for object &1 (&2); error code: &3 |
The short text describes the object sufficiently |
|
400 |
448 |
Object &1 (&2) imported successfully |
The short text describes the object sufficiently |
|
401 |
449 |
Test object &1 (&2) saved successfully |
The short text describes the object sufficiently |
|
402 |
450 |
Could not save test object &1 (&2) |
The short text describes the object sufficiently |
|
403 |
451 |
Data for test object &1 (&2) loaded successfully |
The short text describes the object sufficiently |
|
404 |
452 |
Could not load data for test object &1 (&2) |
The short text describes the object sufficiently |
|
405 |
453 |
Current state of test object &1 (&2) is inconsistent |
The short text describes the object sufficiently |
|
406 |
454 |
Data for test object &1 (&2) already stored; skip action |
The short text describes the object sufficiently |
|
407 |
455 |
Data for test object &1 (&2) not found |
The short text describes the object sufficiently |
|
408 |
456 |
Data for test object written successfully to request &1 |
The short text describes the object sufficiently |
|
409 |
457 |
Error while writing data for test object to request &1 |
The short text describes the object sufficiently |
|
410 |
458 |
You are not authorized to generate archive entries for test data |
The short text describes the object sufficiently |
|
411 |
459 |
Invalid transport request type |
The short text describes the object sufficiently |
|
412 |
460 |
Data for test object &1 (&2) not found; action terminated |
The short text describes the object sufficiently |
|
413 |
461 |
Data for test object &1 (&2) rolled up successfully |
The short text describes the object sufficiently |
|
414 |
462 |
Could not roll up data for test object &1 (&2) |
The short text describes the object sufficiently |
|
415 |
463 |
Data for test object &1 (&2) compressed successfully |
The short text describes the object sufficiently |
|
416 |
464 |
Could not compress data for test object &1 (&2) |
The short text describes the object sufficiently |
|
417 |
465 |
Data already exists for test object &1 (&2); data will not be saved |
The short text describes the object sufficiently |
|
418 |
466 |
Data for test object &1 (&2) overwritten successfully |
The short text describes the object sufficiently |
|
419 |
467 |
Test data type &1 has no data type assignment; processing ended |
The short text describes the object sufficiently |
|
420 |
468 |
Data for test object &1 (&2) was overwritten successfully |
The short text describes the object sufficiently |
|
421 |
469 |
Central test data folder '&1' not found; processing terminated |
The short text describes the object sufficiently |
|
422 |
470 |
File for test data for object &1 (&2) not found |
The short text describes the object sufficiently |
|
423 |
471 |
Could not switch load status of InfoCube &1 to '&2' |
The short text describes the object sufficiently |
|
424 |
472 |
Header data for test sequence '&1' updated |
The short text describes the object sufficiently |
|
425 |
473 |
Data object for &1 (&2) cannot be used for testing; no status stored |
The short text describes the object sufficiently |
|
426 |
474 |
Data object testing for &1 (&2) unsuccessful; no status stored |
The short text describes the object sufficiently |
|
427 |
475 |
You are not authorized to create data for test object &1 (&2) |
The short text describes the object sufficiently |
|
428 |
476 |
Format of test data for object &1 (&2) has changed; no processing |
The short text describes the object sufficiently |
|
429 |
477 |
Parameter values for testing match |
The short text describes the object sufficiently |
|
430 |
478 |
Expected floating point number &1 differs significantly from &2 |
The short text describes the object sufficiently |
|
431 |
479 |
Pattern &1 not found in expression &2 |
The short text describes the object sufficiently |
|
432 |
480 |
Pattern &1 found in expression &2 |
The short text describes the object sufficiently |
|
433 |
481 |
Return code &1 does not match code &2 |
The short text describes the object sufficiently |
|
434 |
482 |
Check parameter is initial |
The short text describes the object sufficiently |
|
435 |
483 |
Check parameter is not initial |
The short text describes the object sufficiently |
|
436 |
484 |
Test sequence &1 created successfully |
The short text describes the object sufficiently |
|
437 |
485 |
Test sequence &1 saved successfully |
The short text describes the object sufficiently |
|
438 |
486 |
&1 MIME objects removed successfully from store |
The short text describes the object sufficiently |
|
439 |
487 |
&1 MIME objects added successfully to store |
The short text describes the object sufficiently |
|
440 |
488 |
&1 links stored successfully |
The short text describes the object sufficiently |
|
441 |
489 |
Maximum test run time &1 (in seconds) is invalid |
The short text describes the object sufficiently |
|
442 |
490 |
Collective job for test results with job number &1 released |
The short text describes the object sufficiently |
|
443 |
491 |
Collective job for test results with job number &1 contains errors |
The short text describes the object sufficiently |
|
444 |
492 |
Test run &1 not found |
The short text describes the object sufficiently |
|
445 |
493 |
Collection for test run &1 started on test object &2 (&3) |
The short text describes the object sufficiently |
|
446 |
494 |
Collection for test run &1 on test object &2 (&3 entries) ended |
The short text describes the object sufficiently |
|
447 |
495 |
Mandatory parameter (&1) for test sequence not set. No data saved |
The short text describes the object sufficiently |
|
448 |
496 |
Object &1 not yet saved |
The short text describes the object sufficiently |
|
449 |
497 |
All unsaved changes will be lost when you quit |
The short text describes the object sufficiently |
|
450 |
498 |
ID for test run (BW test result repository): &1 |
The short text describes the object sufficiently |
|
451 |
499 |
Object &1 (&2) is locked by user '&3' |
The short text describes the object sufficiently |
|
452 |
500 |
Changes have been made to the object. Do you want to save these changes? |
The short text describes the object sufficiently |
|
453 |
501 |
Report &1 does not have an active version |
The short text describes the object sufficiently |
|
454 |
502 |
Trace processing in source system &1 |
The short text describes the object sufficiently |
|
455 |
503 |
The traces (&1) are not compatible |
The short text describes the object sufficiently |
|
456 |
504 |
No data inconsistencies occurred during the regression test |
The short text describes the object sufficiently |
|
457 |
505 |
Data inconsistencies occurred during the regression test |
The short text describes the object sufficiently |
|
458 |
506 |
Execute trace '&1' with play variant '&2' |
The short text describes the object sufficiently |
|
459 |
507 |
Amount of data transferred (for metadata): & bytes |
The short text describes the object sufficiently |
|
460 |
508 |
Amount of data transferred (for test data): & bytes |
The short text describes the object sufficiently |
|
461 |
509 |
&1 test instances must be transferred |
The short text describes the object sufficiently |
|
462 |
510 |
Portal trace &1 played from JAVA Web runtime |
The short text describes the object sufficiently |
|
463 |
511 |
Error while playing portal trace &1 |
The short text describes the object sufficiently |
|
464 |
512 |
The start time must be in the future |
The short text describes the object sufficiently |
|
465 |
513 |
The end time cannot be more than one year after the present time |
The short text describes the object sufficiently |
|
466 |
514 |
Job ID &1 already exists |
The short text describes the object sufficiently |
|
467 |
515 |
The job ID is not valid |
The short text describes the object sufficiently |
|
468 |
516 |
Processing is blocked |
The short text describes the object sufficiently |
|
469 |
517 |
&1 - Test sequence '&2' started |
The short text describes the object sufficiently |
|
470 |
518 |
Test run started for job '&1'. Number of test sequences: &2 |
The short text describes the object sufficiently |
|
471 |
519 |
No processes are currently available to run object &1 |
The short text describes the object sufficiently |
|
472 |
520 |
Activation currently not possible due to locked objects |
The short text describes the object sufficiently |
|
473 |
521 |
No test data instances needs to be transferred |
The short text describes the object sufficiently |
|
474 |
522 |
&1 is a pure meta object. No test data needs to be transferred |
The short text describes the object sufficiently |
|
475 |
523 |
Database statistics built successfully for InfoCube &1 |
The short text describes the object sufficiently |
|
476 |
524 |
Unable to create database statistics for InfoCube &1 |
The short text describes the object sufficiently |
|
477 |
525 |
Object &1 will be deleted indefinitely. Do you want to proceed? |
The short text describes the object sufficiently |
|
478 |
526 |
Transfer for object type &1 (&2) not supported |
The short text describes the object sufficiently |
|
479 |
527 |
Application instance &1 updated |
The short text describes the object sufficiently |
|
480 |
528 |
BW object &1 (&2) does not exist in an active version |
The short text describes the object sufficiently |
|
481 |
529 |
Application instance &1 (&2) is not completely maintained |
The short text describes the object sufficiently |
|
482 |
530 |
Work package information for test run &1 (&2) updated |
The short text describes the object sufficiently |
|
483 |
531 |
Test analysis for test run &1 (&2) updated |
The short text describes the object sufficiently |
|
484 |
532 |
Object &1 has not changed. It does not need to be saved |
The short text describes the object sufficiently |
|
485 |
533 |
Status of extraction for instance &1 (sequence &2): &3 (&4 entries) |
The short text describes the object sufficiently |
|
486 |
534 |
Status of BW publishing for instance &1 (sequence &2): &3 (&4 entries) |
The short text describes the object sufficiently |
|
487 |
535 |
Status of delta update for instance &1 (sequence &2): &3 (&4 entries) |
The short text describes the object sufficiently |
|
488 |
536 |
Extraction job &1 released with job number &2 |
The short text describes the object sufficiently |
|
489 |
537 |
Welcome to &2 &1 |
The short text describes the object sufficiently |
|
490 |
538 |
Variant &1 saved |
The short text describes the object sufficiently |
|
491 |
539 |
Error. Variant &1 could not be saved. |
The short text describes the object sufficiently |
|
492 |
540 |
Query GUID modification (call): &1 to &2. Number of replacements: &3 |
The short text describes the object sufficiently |
|
493 |
541 |
Query GUID modification (ref. data): &1 to &2. Number of replacements: &3 |
The short text describes the object sufficiently |
|
494 |
542 |
Instance &1 (&2) of class &3 has not been registered correctly |
The short text describes the object sufficiently |
|