S_LMCFG_CORE_TASK_QC - Technical Configuration Core Task Messages
The following messages are stored in message class S_LMCFG_CORE_TASK_QC: Technical Configuration Core Task Messages.
It is part of development package S_LMCFG_CORE_TASKS_QC in software component BC-INS-TC-CNT. This development package consists of objects that can be grouped under "Technical Configuration Quality Checks".
It is part of development package S_LMCFG_CORE_TASKS_QC in software component BC-INS-TC-CNT. This development package consists of objects that can be grouped under "Technical Configuration Quality Checks".
Message Nr ▲ | Message Text |
---|---|
000 | &1 &2 &3 &4 |
001 | Call to &1 failed; return code &2 |
002 | Parameter &1 is missing |
003 | Transaction &1 is locked |
004 | Lock transaction &1; system failure occured |
005 | Check successful |
006 | Logon group &1 updated |
007 | Logon group &1 created |
008 | RFC server group &1 updated |
009 | RFC server group &1 created |
010 | Enter a valid instance name |
011 | Enter a valid group type |
012 | Operation mode &1 created |
013 | Create operation mode failed; return code &1 |
014 | Operation mode &1 already exists |
015 | Authority &1 is missing |
016 | Operation mode &1 assigned to time table |
017 | Operation mode &1 assigned to application server instance |
018 | Logon group &1 already exists |
019 | RFC server group &1 already exists |
020 | Call SAPICC error in test number &1 |
021 | System &1 checked; no error reported by SICK |
022 | System &1 checked; error reported by SICK |
023 | Job RDDIMPDP scheduled in client &1 |
024 | Function &1 is not available; refer to SAP Note &2 |
025 | Configuration successful |
026 | Passwords are not stored; re-enter in dialog |
027 | Secure store entry check successful |
028 | Secure store entry check; &1 errors in total |
029 | SAP standard jobs scheduled |
030 | ABAP load generation prepared; continue with transaction SGEN manually |
031 | ABAP load generation prepared |
032 | ABAP load generation finished |
033 | Secure store entry check; &1 key or undefined error |
034 | Secure store entry check; &1 migration required |
035 | Remote connection test successful |
036 | Enter a numeric client number |
037 | RFC destination &1 created |
038 | RFC connection &1 test failed |
039 | TMS configured as domain controller |
040 | TMS configuration already exists |
041 | Internal error from enqueue server occured |
042 | Job &1(&2) started for &3 objects |
043 | Job &1(&2) for machine type &3 has still &4 objects to process |
044 | Job &1(&2) is aborted; could not complete generation |
045 | Force mode is not allowed in SAP internal landscape |
046 | RFC destination &1 already exists |
047 | Configure TMS only in client 000 |
048 | SLD Access Data entry already exists |
049 | Submit failed for job &1; return code &2 |
050 | DBMS &1 is not supported |
051 | To overwrite existing setting, select force mode |
052 | Force mode selected to overwrite existing setting |
053 | Cannot overwrite existing setting since force mode is not set |
054 | Configuration is overwritten since force mode is set |
055 | Standard jobs for DBA planning calendar scheduled |
056 | MSSQL scripts successfully executed |
057 | TMS is not configured; check failed |
058 | Calling function &1 |
059 | No valid path &1 |
060 | PSE (&1/&2) uploaded |
061 | PSE (&1/&2) already exists |
062 | &1 restart of ICM server &2 successful |
063 | &1 restart of ICM server &2 failed; return code &3 |
064 | ICM notification successful |
065 | ICM notification failed |
066 | Error occurred |
067 | File &1 |
068 | SSLS application created |
069 | PSE (&1/&2) created or updated |
070 | Certificate for PSE (&1/&2) uploaded |
071 | PSE (&1/&2) does not exist |
072 | Transaction STRUST is locked by user &1 |
073 | HDB migration activities are only allowed on a HDB based system |
074 | Do not use user &1 as this creates a security risk |
075 | Illegal usage by &1 |
076 | Enter a target client <> &1 |
077 | Not supported RFC destination &1 |
078 | RFC destination &1 deleted |
079 | Directory &1 found |
080 | File &1 found |
081 | No Job matches the selection criteria |
082 | High availability license &1 installed |
083 | Installation of &1 |
084 | Standard license &1 installed |
085 | Error while reading licences; return code &1&2 |
086 | License &1 for installation number &2 deleted |
087 | Error while deleting licence ( SID &1 Hardware &2 Product &3 ) |
088 | Error while deleting licence ( Hardware &1 Product &2 ) |
089 | Could not find directory &1 |
090 | RFC destination &1 generated |
091 | No such file or directory &1&2 &3 |
092 | Could not install license &1&2; check license file |
093 | Could not delete license |
094 | HTTP Services activation: &1 successful, &2 failed (see details) |
095 | Action canceled by user |
096 | ZLOGIN_SCREEN_INFO already exists |
097 | ZLOGIN_SCREEN_INFO updated |
098 | ZLOGIN_SCREEN_INFO created |
099 | RFC destination &1 creation failed |
100 | User &1 already exists |
101 | &1&2&3&4 |
102 | HTTP Service &1 activated |
103 | HTTP Service &1 activation failed: &2 |
104 | INSTANCE &4; Check &3 (Expected: &1 -> Found: &2) |
105 | Check Service failed: &1 |
106 | User &1 does not exist |
107 | Log for Profile assignment: |
108 | Log for Role assignment: |
109 | Supervisor Destination &1 and User &2 created |
110 | A Supervisor Destination already exists |
111 | Checks for bgRFC executed |
112 | RFC destination &1 already exists, execution will overwrite |
113 | HTTP Service &1 with subsequent nodes activated |
114 | Only numeric values accepted |
115 | Password field empty |
116 | Inbound Destination &1 with Prefixes &2 defined |
117 | Inbound Destination &1 scheduled |
118 | HTTP Service &1&2 check failed: &3 |
119 | Connection RFC Destination &1 checked |
120 | DB connection &1 already exists |
121 | Create trusted task should not run before create RFC destination |
122 | RFC destination &1 does not exist |
123 | Logical System &1 already exists |
124 | Required Predecessor Task &1 not available. |
125 | Cross-Client changes are not allowed (SCC4) |
126 | Logical System &1 created |
127 | One of the following tasks is as predecessor required: |
128 | Only one of the following tasks can be predecessor of this task: |
129 | SAP System Alias &1 created |
130 | SAP System Alias '&1' already exists |
131 | Login to RFC Destination &1 not possible |
132 | Request &1 does not exists |
133 | System Alias &1 already exists |
134 | RFC Destination &1 is Type &2. Expected Type: &3 |
135 | RFC Destination &1 is not configured as Trusted Relationship |
136 | RFC Destination &1 is not configured for Login with Current User |
137 | RFC Destination &1 checked |
138 | Call to &1 failed; return code &2 |
139 | Profile Parameter &1 = &2 needs to be set |
140 | Profile Parameter &1 = &2 is set |
141 | Profile Parameter &1 = &2 is already set |
142 | &1 added to Certificate List and Logon Ticket added to ACL |
143 | ACL entry for &1 already exists |
144 | Certificate for &1 already exists |
145 | Certificate for &1 received |
146 | RFC Destination parameter is missing |
147 | System &1 is already trusted |
148 | Trusted Relationship for SAP Gateway &1 created |
149 | RFC Destination &1 selected |
150 | Client-specific changes are not allowed (SCC4) |
151 | Selected Request &1 |
152 | Created Request &1 with Task &2 for &3 |
153 | Create Request failed |
154 | Client-specific changes are allowed (SCC4) |
155 | Cross-Client changes are allowed (SCC4) |
156 | File &1 available |
157 | File &1 not available |
158 | Parameter &1=&2 |
159 | Wrong value: &1=&2 |
160 | ICM is active |
161 | ICM is not active |
162 | ICM status error |
163 | Server &1:ICM HTTPS port not configured |
164 | Server &1:ICM HTTPS &2 port not active |
165 | Server &1:ICM HTTPS port &2 active |
166 | &1 PSE check on server &2 : |
167 | &1 PSE does not exist on server &2 |
168 | OData Service &1 (Version: &2) is already active |
169 | OData Service &1 (Version: &2) is activated |
170 | Activating OData Service &1 (Version: &2) failed |
171 | Try to activate service with transaction /IWFND/MAINT_SERVICE manually |
172 | Profile parameter &1 does not exist |
173 | API Function module &1 is available |
174 | ODATA Service fallback activation for Fiori launchpad started |
175 | HTTP service group &1 does exist |
176 | HTTP service group &1 does not exist, fallback activation started |
177 | HTTP service fallback activation started |
178 | Certificate is self-signed |
179 | Validity of certificate less then &1 days |
180 | Validity of certificate checked |
181 | Validity of certificate expired |
182 | Profile parameter check on server &1 : |
183 | SAP Cryptographic file check on server &1: |
184 | Full qualified domain not found |
185 | SAP User Menu -> Favorites: &1 URL added |
186 | No active HTTPS port found |
187 | No authority for execution (Activity &1 Authority Object &2) |
188 | Task requires execution in Dialog |
189 | Parameter check for &1 failed; Target Value: &2 &3; Actual Value: &4 |
190 | Field is empty; Enter a value |
191 | Operand &2 cannot be applied for target value &1 |
192 | Parameter check for &1 successful; Target Value: &2 &3; Actual Value: &4 |
193 | Node &1 already exists |
194 | Node &1 creation failed |
195 | Node &1 created |
196 | Creation of Default domain &1 failed |
197 | Default Domain &1 created |
198 | Default Domain &1 overwritten with &2 |
199 | Background Send Job &1 scheduled |
200 | Background Send Job &1 scheduling failed |
201 | Address type is missing |
202 | Default Domain &1 unchanged |
203 | Passwords are not identical |
204 | Set profile parameter &1 |
205 | to value &1 |
206 | Parameter &1 is erroneous |
207 | Permanent license already installed |
208 | Logical system &1 is already used by another client |
209 | Client &1 already exists |
210 | Default logical system name &1 is already used by another client |
211 | INSTANCE &1; Parameter does not exist |
212 | INSTANCE &1; Target Value: &2 &3; Actual Value: &4 |
213 | RESULT &1 |
214 | ----------------------------------------------------------------------&1 |
215 | Currency &1 does not exists |
216 | Client number is not numeric |
217 | OData Service &1 (Version: &2) is activated / Alias 'LOCAL' assigned |
218 | Failed to set Profile Parameters in &1; RC &2; Class &3; Method &4 |
219 | Operand &1 is not valid; Valid operands are =, <>, <=, >=, CS |
220 | Enable 'Changes to Repository and cross-client Customizing allowed' |
221 | Enable 'Automatic recording of changes' |
222 | Indicator 'Protection against SAP upgrade' only allowed for test client |
223 | No application servers |
224 | No such file or directory &1&2 &3 |
225 | Directory is missing |
226 | File name is missing |
227 | Enter Number of the request or task |
228 | Different settings of supplementation language |
229 | &1: &2 = &3; Parameter created |
230 | &1: Restart required |
231 | &1: &2 = &3; Changed |
232 | &1: No restart required |
233 | ICF Services saved |
234 | &1: &2 = &3; Could not be applied |
235 | &1: &2 = &3; Unchanged |
236 | &1: &2 = &3; Switched dynamically |
237 | Job &1 is scheduled |
238 | Job &1 is not scheduled |
239 | Parameter &1 has double entries for the application server |
240 | &1: Parameter &2 was tried to be set several times |
241 | &1: Parameter &2 was tried to be set several times |
242 | &1: Parameter &2 was tried to be set several times |
243 | INSTANCE &1; is unknown in this system |
244 | Check failed |
245 | Parameter &1 not set |
246 | &1: Restart of the whole system required |
247 | &1: No restart required |
248 | RFC Logon Test successful |
249 | Job &1 does not exist |
250 | No valid license installed |
251 | No permanent license installed |
252 | ------------------------------------------------- |
253 | Valid License for system &1 available: |
254 | Hardware Key: &1 |
255 | Product: &1 |
256 | Limit: &1 |
257 | Valid from: &1 |
258 | Valid to: &1 |
259 | License Type: &1 |
260 | Installation Number: &1 |
261 | System Number: &1 |
262 | No maintenance license installed |
263 | >>>> License check failed: |
264 | >>>> License check OK |
265 | INSTANCE &1; Logon group &2 available |
266 | INSTANCE &1; Server group &2 available |
267 | INSTANCE &1; No logon groups available |
268 | INSTANCE &1; No server groups available |
269 | &1 shutdown of ICM server &2 started |
270 | Could not &1 shutdown ICM server &2; return code &3 |
271 | Task ready to be executed |
272 | PSE is valid and expires in &1 days |
273 | PSE does not exist |
274 | Serial number; Target value = &1; Actual value = &2 |
275 | Key type: Target value = &1; Actual value = &2 |
276 | Key length: Target value = &1; Actual value = &2 |
277 | PSE is valid; Expiration date = &1 |
278 | PSE is invalid; Expiration date = &1 |
279 | Validation of &1 |
280 | PSE exists |
281 | No operation mode available |
282 | INSTANCE &1; No operation mode in timetable |
283 | INSTANCE &2; Operation mode &1 active |
284 | Specify at least one profile or role |
285 | External Alias &1 created |
286 | External Alias &1 already exists |
287 | Batch job &1 already scheduled |
288 | Batch job &1 released |
289 | Batch job &1 finished (see details) |
290 | Batch job &1 not released |
291 | TMS not configured |
292 | TMS not active |
293 | Patch level not checked; release is different |
294 | Patch level cannot be checked; specify release |
295 | SLD Data Supplier already exists |
296 | SAP Cryptographic library call successful, see details |
297 | Enter System Alias Name |
298 | No supplementation language defined for language &1 |
299 | User company address missing; default entry will be created |
300 | &1&2&3&4 |
301 | Batchjob &1 not found |
302 | SAP Load Generator (SGEN) batchjob not found |
303 | SGEN batchjob &1 (ID &2) found |
304 | SAP Load Generator (SGEN) job status finished |
305 | SAP Load Generator (SGEN) job status aborted |
306 | SAP Load Generator (SGEN) job status unknown, check manually in SM37 |
307 | Supplementation of &1 with &2; &3 tables to be supplemented |
308 | Call failed; Class &1; Method &2; Return Code &3 |
309 | &1 of &2 tables supplemented |
310 | No language installed; Supplementation not possible (SAP Note 42305) |
311 | Different settings of supplementation language |
312 | Supplementation of &1 with &2; finished successfully; &3 (see SM37) |
313 | Supplementation of &1 with &2; started; &3 (see SM37) |
314 | No supplementation language defined for language &1 |
315 | Supplementation of &1 with &2; Language package not installed for &3 |
316 | Supplementation is supported for language EN and DE only |
317 | Supplementation of &1 with &2; is currently running (see SMLT) |
318 | Installed Languages: &1 |
319 | Secure store check all failed; resolve in transaction SECSTORE |
320 | Secure store error to be migrated; resolve in transaction SECSTORE |
321 | Secure store key missing; resolve in transaction SECSTORE |
322 | Secure store legacy key missing; resolve in transaction SECSTORE |
323 | Key ID &1 |
324 | Key Value &1 |
325 | User company address created |
326 | New key generated and activated for all entries; backup is recommended |
327 | Kernel release information not found |
328 | Operating system information not found |
329 | INSTACE &1; Kernel release information not found |
330 | Operating system release information not found |
331 | INSTANCE &1; Kernel patch level information not found |
332 | INSTANCE &1; Kernel information not found |
333 | Instances have different kernel releases |
334 | Instances have different kernel patch levels |
335 | Instances have the same kernel releases |
336 | Instances have the same kernel patch levels |
337 | SAP Load Generator (SGEN) job status unknown, not finished |
338 | INSTANCE &1; Logon group PUBLIC is not assigned; found &2 |
339 | INSTANCE &1; Server group PUBLIC is not assigned found &2 |
340 | INSTANCE &1; operation mode &2 not configured |
341 | Client &1 exists |
342 | Client &1 does not exist |
343 | No clients specified |
344 | Language Supplementation for language &1 |
345 | Supplementation of &1 with &2; ended with status &3; &4 (see SM37) |
346 | RFC Connection test successful |
347 | RFC Connection test failed, Error Message: |
348 | RFC Logon Test failed, Error Message: |
349 | Supplementation of &1 with &2; Call to &3 failed; return code &4 |
350 | HTTP Error Code: &1 |
351 | Jobname could not be created |
352 | Operation mode needs adaption in transaction RZ04 |
353 | INSTANCE &1; Operation mode 'Daymode' not configured |
354 | SAP System Alias &1 created |
355 | SAP System Alias &1 already exists |
356 | Customer System Alias &1 created |
357 | Customer System Alias &1 already exists |
358 | System Alias Mapping &1 created |
359 | System Alias Mapping &1 already exists |
360 | SGEN &1 objects to be regenerated, use report RSGENINVLASM |
361 | Check &3 (Expected: &1 -> Found: &2) |
362 | Import from memory failed |
363 | Client: &1 User: &2 &3 &4 |
364 | Wrong setting for client &1: |
365 | Changes and Transports for Client-Specific Objects |
366 | Cross-Client Object Changes |
367 | User &1 has authorization profile SAP_ALL |
368 | No user with authorization profile SAP_ALL |
369 | System Change Option, Global Setting: &1 |
370 | &1: No changes to repos./cross-client cust.obj. |
371 | &1: No changes allowed |
372 | Check client settings for client &1: |
373 | Does not exists; &1 |
374 | Active SLD URL; &1 |
375 | No active SLD URL found |
376 | SLD URL host or port not found for; &1 |
414 | Client &1 is not permitted |
415 | Client Copy from &1 to &2 finished |
416 | Client Copy from &1 to &2 failed, check transaction SCC3 |
423 | Profile Parameter &1 set to &2 in &3 profile; Restart required |
424 | Parameter content: |
426 | Profile Parameter &1 already set to &2; No restart required |
427 | Call to method failed; RC &1; Class &2; Method &3 |