/SMB/TRANSP_INFRA - Solution Builder Transport Infrastructure
The following messages are stored in message class /SMB/TRANSP_INFRA: Solution Builder Transport Infrastructure.
It is part of development package /SMB/TI_UTILITY in software component SV-CLD-FRM-INF. This development package consists of objects that can be grouped under "Transport Infrastructure: Utilities".
It is part of development package /SMB/TI_UTILITY in software component SV-CLD-FRM-INF. This development package consists of objects that can be grouped under "Transport Infrastructure: Utilities".
Message Nr ▲ | Message Text |
---|---|
000 | &1&2&3&4 |
001 | Could not update database table &1 |
002 | Could not find object &1 &2 &3 in database table &4 |
003 | Inactive customer content object &1 &2 already exists |
004 | Inactive reference content object &1 &2 already exists |
005 | Unknown content type &1 |
006 | Inactive customer content object &1 &2 does not exist |
007 | Inactive reference content object &1 &2 does not exist |
008 | Customer content object &1 &2 deleted |
009 | Reference content object &1 &2 deleted |
010 | Customer content object &1 &2 saved |
011 | Reference content object &1 &2 saved |
012 | Cannot use parameter &1 |
013 | Invalid file structure |
014 | Content object(s) assigned to transport request &1 |
015 | Content selection only possible in dialog mode |
016 | Provide the content ID |
017 | Enter solution file in a valid format |
018 | Cannot find installation data for solution &1, it has no attributes |
019 | No installation data found in inactive content for solution &1 |
020 | Multiple installation data sets in inactive content for solution &1 |
021 | Could not create &1 Transport Request |
022 | Could not create new task in Transport Request &1 |
023 | Saving of the correction solution to the archive failed. |
024 | Object could not be created, /FTI/ namespace is missing. |
025 | Correction procedure was not found in procedure framework, cancelling. |
026 | No correction change package found |
027 | Solution &1 already exists |
028 | Multiple customer solutions in the system |
029 | RFC &1 destination not reachable.&2&3&4 |
030 | Technical error executing RFC &1.&2&3&4 |
031 | Specify a log handle to be deleted |
032 | New application log could not be created |
033 | Application log was not found |
034 | No application log to be saved |
035 | Processing client &1 |
036 | Processing client &1 finished successfully |
037 | Parallel run started |
038 | Job started |
039 | Package started |
040 | Parallel run completed |
041 | Job completed |
042 | Package completed |
043 | Package creation by intervals is not supported |
044 | Package creation by calculation is not supported |
045 | Client &1 is not or no longer valid and will be skipped |
046 | Beginn Job: Last attempt = &1; retry nr. = &2 |
047 | Update of client &1 failed due to a content error |
048 | Update of client &1 failed due to a technical error |
049 | Implementation fault.Update of client &1 returned with no result |
050 | Transport contains no relevant content |
051 | Start of log: after import methods for solution builder content |
052 | End of log: after import methods for solution builder content |
053 | Object type not supported in this context. |
054 | Unknown content category |
055 | Local after import manager in client &1: |
056 | Everything is wrong with Solution &1 |
057 | No system language, maintain system parameter zcsa/system_language. |
058 | Solution &1 is not activated |
059 | Local After Import Manager |
060 | Local After Import Manager finished |
061 | Transport Request &1 contains no relevant objects |
062 | &1 Solution(s) found for Content Lifecycle Procedure |
063 | Starting Update of Solution &1 |
064 | Update of Solution &1 finished |
065 | Applying Correction Change Package(s) |
066 | Correction Change Package(s) applied |
067 | &1 relevant Correction Change Package(s) found |
068 | &1 Correction Change Package(s) not yet applied |
069 | Starting Determination of Correction Change Packages |
070 | Determination of Correction Change Packages finished |
071 | Checking Change Package(s) already applied |
072 | Checking Change Package(s) finished |
073 | Importing and Applying Change Package(s) |
074 | Importing and Applying Change Package(s) finished |
075 | Change Package '&1' loaded from Inactive Content |
076 | Change Package '&1' already uploaded into Solution &2 |
077 | Change Package '&1' is applied in Force Mode |
078 | Change Package '&1' is applied in Standard Mode |
079 | Change Group '&1' created for applying Change Package |
080 | Change Group '&1' applied |
081 | Change Group '&1' saved |
082 | Error creating Change Package '&1' |
083 | Error creating Change Group |
084 | Solution is activated (Status = &1) |
085 | Solution is not activated |
086 | Solution is Customer Solution |
087 | Solution is not Customer Solution |
088 | Applying Customer Adaptation Change Package(s) |
089 | Customer Adaptation Change Package(s) applied |
090 | Starting Determination of Customer Adaptation Change Packages |
091 | Determination of Customer Adaptation Change Packages finished |
092 | &1 Customer Adaptation Change Package(s) found |
093 | Change Package '&1' |
094 | Change Package '&1' finished |
095 | Transformation of solution data to XML failed. |
096 | Error during XML generation |
097 | Starting Correction Procedure |
098 | Correction Procedure finished |
099 | Target Solution: &1 |
100 | Correction solution already existed on the DB, archiving and deleting... |
101 | Starting Solution Activation |
102 | Solution Activation finished |
103 | Determining Settings for Activation |
104 | Activation Settings Determination finished |
105 | No language provided, using system language &1 for activation |
106 | Archiving the correction solution failed, reason: |
107 | Archiving finished, starting resetting of activation status |
108 | Resetting of activation status finished, deleting installation data |
109 | Deleting installation data finished, deleting solution |
110 | Deleting solution finished |
111 | Error occured on deleting, starting deleting in hard mode |
112 | Deleting in hard mode finished |
113 | Using existing Change Group '&1' for applying Change Package |
114 | Errors occured during Content Lifecycle operation on Solution &1: |
115 | Content Lifecycle operations finished successfully |
116 | Application Log with External ID '&1&2' created on &3 at &4 |
117 | Solution Activation not started as Correction Procedure failed |
118 | Manual rework required |
119 | Change Package &1 contains broken chain for File &2 VarID &3 Parameter &4 |
120 | An error occurred during activation of Solution &1 |
121 | Solution &1 does not exist |
122 | Could not parse file &1 for save of correction solution: |
123 | Fake download for internal to binary format conversion failed for file &1 |
124 | Solution Activation not necessary |
125 | AfterImport Method finished sucessfully |
126 | AfterImport Method returned errors |
127 | Filename is too long (max. 40 characters) |
128 | Manual Update of Solution (Report &1) |
129 | Manual Update of Solution finished |
130 | &1 change(s) can be applied flawlessly |
131 | &1 broken chain(s) in Change Package |
132 | &1 change(s) can't be applied in Standard Mode |
133 | Change Package '&1' is already applied to Solution &2 |
134 | &1 change(s) will be applied in Force Mode |
135 | Error during db insert. Record exists already. |
136 | no active Change Group for Customer Solution found |
137 | Importing Reference Content |
138 | Starting Import of Business Organization Extension History |
139 | Import of Business Organization Extension History finished |
140 | Importing Business Organization Extension History |
141 | Business Organization Extension History imported |
142 | Starting Determination of Business Org Extensions in Customer Content |
143 | Determination of Business Org Extensions in Customer Content finished |
144 | Import of customer content completed successfully for client &1 |
145 | No Business Organization Extensions in Customer Content found |
146 | Saving Business Organization Extensions |
147 | Business Organization Extensions saved |
148 | Importing Customer Content |
149 | Determination of Lifecycle Operations for Solution &1 (Phase &2) |
150 | Solution Update |
151 | Import of Business Organization Extension History |
152 | Errors occured during Content Lifecycle operation: |
153 | Manual Import of Business Org Extensions (Report /SMB/IMPORT_BUS_ORG_EXT) |
154 | Manual Import of Business Org Extensions finished |
155 | Change Group '&1' for active Customer Adaptations |
156 | Change Group '&1' for Corrections to Business Organization Extensions |
157 | Determination of Solution independent Lifecycle Operations (Phase &1) |
158 | &1 Business Organization Extension Entities written to the Database |
159 | &1 Business Organization Extension Variants written to the Database |
160 | Importing Customer Content ID '&1' into Business Org Extension History |
161 | No Solution specific Lifecycle Operations (Phase &1) |
162 | No Solution independent Lifecycle Operations in Phase &1 |
163 | An obligatory parameter was not provided |
164 | Solution Activation not started as Upgrade Procedure failed |
165 | Improvement of solution &1 finished |
166 | &1 Business Organization Extension Combined Types written to the Database |
167 | &1 Business Org. Ext. Additional Relations written to the Database |
168 | Solution Improvement |
169 | Starting Improvement of Solution &1 |
170 | Starting import of new reference solutions |
171 | Import of new reference solutions finished |
172 | No product/version attributes of source solutions found |
173 | Product/version attributes of source solution(s) are |
174 | Solution ID = &1, Package ID = &2, Country/Region = &3, ... |
175 | ..., Product = &1, Product Version = &2, Content Version = &3, ... |
176 | Determination of new reference solutions |
177 | Processing source solution: &1 |
178 | No matching solution found in inactive content |
179 | Internal error: Matching solution has no BDM attributes |
180 | Product/version attributes of latest reference solution are |
181 | Internal error: BDM attributes do not match |
182 | New solution has a new product version |
183 | New solution has a new content version and same product version |
184 | Current solution is already the latest, nothing to do |
185 | Only an older version than the current was found |
186 | Determination of matching installation data |
187 | No matching installation data found |
188 | Matching installation data found: &1 |
189 | Error, &1 sets of matching installation data found |
190 | Improvement found: solution &1, installation data &2 |
191 | Errors occurred, process stopped |
192 | No possible improvements found |
193 | Improvements were found, process continues |
194 | Uploading new source solutions |
195 | Processing content ID &1 |
196 | An error occurred during the solution upload |
197 | Uploading new installation data (only latest per country/region) |
198 | Updating languages of target solution |
199 | An error occurred during the installation data upload |
200 | Installation data upload finished |
201 | Solution is not Customer Solution. Improvement not possible |
202 | Executing After-Import-Method for target client &1 |
203 | Executing After-Import-Method (no target client specified ) |
204 | Local client &1 does not fit target client &2 |
205 | Manual Improvement of Cust. Solution (Rep./SMB/IMPROVE_CUSTOMER_SOLUTION) |
206 | No customer solution in the system |
207 | Manual Improvement of Customer Solution finished |
208 | Inconsistencies in Runtime PME table detected |
209 | Product Line &1 |
210 | Valid from &1 to &2 |
211 | Software Component &1 &2 |
212 | Delivery &1 &2 |
213 | Export Timestamp &1 |
214 | Create Timestamp &1 |
215 | Solution Context |
216 | Apply Customer Adaptations |
217 | &1 change(s) in mode 'edit' |
218 | No changes of &1 are needed, nothing applied |
219 | No changes imported |
220 | Starting Import of Customer Adaptations of Solution &1 |
221 | Import of Customer Adaptations of Solution &1 finished |
222 | More than one active change group listed in solution &1 |
223 | Importing Solution from Reference Content, Content ID '&1' |
224 | Deleting Solution &1 |
225 | -> Importing Solution &1 |
226 | Previous correction/upgrade solutions not activated, start new activation |
227 | -> Transport Request &1 |
228 | Content Category: &1 |
229 | Content Type: &1 |
230 | Could not determine activation settings of solution &1 |
231 | Activation error in Building Block &1 |
232 | Activity that raised the error: &1 (&2) - &3 |
233 | Create a BCP internal incident on component &1 |
234 | Solution Activation not started as Upgrade Procedure failed |
235 | Manual Application of Customer Adaptations (Report &1) |
236 | Manual Application of Customer Adaptations finished |
237 | Error during last activation of Solution &1 -> No Lifecycle possible |
238 | Messages from the Activation Request Handler |
239 | Content object could not be assigned to transport request |
240 | Lifecycle Operation Removed due to Priority |
241 | Manual Improvement of Solution (Report &1) |
242 | ... same product version and same content version |
243 | Transport Request &1 contains Reference as well as Customer Content |
244 | Transport Request &1 contains neither Reference nor Customer Content |
245 | ..., Delivery Year = &1, Delivery Number = &2 |
246 | Improvement found in Buffer, see log of Solution &1 |
247 | New solution &1 is already uploaded |
248 | Import of customer content rejected.Target client has not been specified |
249 | Processing content of transport &1 |
250 | Starting Upgrade Procedure |
251 | Language &1 (&2) is currently used and not available anymore |
252 | Language &1 (&2) newly added |
253 | Solution import error due to wrong language settings |
254 | Errors occurred during language update |
255 | The current client is not configured to run lifecycle processor '&1' |
256 | The current client &1 is not configured for content lifecycle |
257 | Uploading files |
258 | File uploaded successfully |
259 | File not uploaded. Using existing object. |
260 | Starting Content Lifecycle operations |
261 | Current solution is already the latest, but force improvement is used |
262 | ID Management preparation failed |
263 | ID Clash Resolution failed |
264 | Repeating import due to previous result in Import History |
265 | Error in source solution determination |
266 | A source solution might have been deleted, which is not allowed |
267 | -> Change Group ID &1 |
268 | -> Activation Log &1 |
269 | Clients to be worked on: |
270 | No matching installation data for &1 |
271 | Solution Improvement: &1 &2 &3 &4 |
272 | Upgrade Procedure finished |
273 | Solution ID &1 |
274 | Transport Log |
275 | -> Procedure Log |
276 | Import A3C Solution |
277 | Starting Import of A3C Solution &1 |
278 | Import A3C Solution finished |
279 | A3C Solution was imported |
280 | An error occurred during the A3C Solution Import |
281 | No A3C solution in this client |
282 | More than one A3C solution in this client |
283 | Path is too long (max. 214 characters) |
284 | Removing empty Files/Activities from A3C Solution |
285 | Removing Activity &1 from Building Block &2 as File &3 is empty. |
286 | Removing empty File &3 from Activity &1/Subobj &4 in Building Block &2. |
287 | No Changes performed on A3C Solution. |
288 | Removing IMG Activity &1 from Building Block &2 as no File is assigned |
289 | Installation Data Export |
290 | Installation Data Import |
291 | Reading Solution &1 |
292 | Reading Installation Data |
293 | Creating Content Objects |
294 | Starting import of new A3C solution |
295 | Archiving Solution &1 |
296 | Importing installation data for Solution &1 |
297 | Import of A3C solution finished |
298 | Performing Solution independent Lifecycle Operations (Phase &1) |
299 | Content Lifecycle operations or Scoping in progress (User &1). |
300 | Release of Customer Scope Information |
301 | Error when activating object & &. Please create a ticket for component &. |
302 | Error stack: & & |
303 | Installation data consistency check |
304 | Installation data references of solution &1 are inconsistent |
305 | Processing solution &1 (phase &2) |
306 | See application log "&1" in &2.&3 for details |
307 | Correction procedure failed |
308 | Upgrade procedure failed |
309 | Solution &1 generated as marker for next import |
310 | Solution Country/Region |
311 | Solution is not activated, no further steps required |
312 | No changes applied to solution, no further steps required |
313 | ..., Delivery Year = &1, Delivery Number = &2 |
314 | New solution has a new year, ... |
315 | ... same product version and same content version |
316 | New solution has a new delivery number, same delivery year, ... |
317 | Creating marker solution &1 for next import. Do not delete or activate! |
318 | Lifecycle processor '&1' is not to be executed in client of type &2 '&3' |
319 | Do nothing - no processor in phase &1 |
320 | Tenant Business Type not set |
321 | Activation queue is blocked with error in activation of Solution &1 |
322 | An error occurred during the Improvement |
323 | An error occurred during the Update |
324 | &1 changes cannot be applied, target variant ID does not exist |
325 | System context could not be determined |
326 | Illegal change: Scope Item &1 was part of &2 and is not part of &3. |
327 | Due to previous import status, Improvement switched to force mode |
328 | Installation Data Upload for Improvement, see /SMB/TRANS_LOG |
329 | -> Importing Installation Data &1 from &2 |
330 | No Import Information about transport &1 in system &2 client &3 |
331 | Starting Import of Customer Scope Information |
332 | Import of Customer Scope Information finished |
333 | Import of Customer Scope Information |
334 | Importing Customer Scope Information |
335 | Customer Scope Information imported |
336 | Starting Determination of Customer Scope Information in Customer Content |
337 | Determination of Customer Scope Information in Customer Content finished |
338 | No Customer Scope Information in Customer Content found |
339 | Saving Customer Scope Information |
340 | Customer Scope Information saved |
341 | Release of Customer Solution Structure |
342 | Release of Data Changes and Org Extensions |
343 | Importing Customer Content ID '&1' into Customer Scope Information |
344 | Scoping: Customer Solution written to the Database |
345 | Scoping: Assignm. of Scope Item/Source Solution 2 Sol. written to DB |
346 | Inconsistency in Q2P function switch detected. |
347 | Customer Scope is unchanged: DB update not necessary |
348 | Forbidden change or deletion of scope |
349 | Country/region &1 solution &2 will be added to customer scope |
350 | Country/region &1 solution &2 will be deleted from customer scope |
351 | Country/region &1 Solution &2 will be changed to &3 |
352 | Scope item &1 will be added to solution &2 |
353 | Scope item &1 solution &2: source solution will be changed from &3 to &4. |
354 | Scope item &1 will be deleted from solution &2 |
355 | Starting Import of Customer Solution Structure |
356 | Import of Customer Solution Structure finished |
357 | Importing Customer Solution Structure |
358 | Customer Solution Structure imported |
359 | No Customer Solution Structure in Customer Content found |
360 | Importing Customer Content ID '&1' into Customer Solution Structure |
361 | Starting Determination of Customer Solution Structure in Customer Content |
362 | Determination of Customer Solution Structure in Customer Content finished |
363 | Saving Customer Solution Structure |
364 | Customer Solution Structure saved |
365 | Customer Soution Structure is unchanged: DB update not necessary |
366 | Table /SMB/BB_PRJ_SCO written to the Database |
367 | Table /SMB/BB_PRJ_ET02 written to the Database |
368 | Table /SMB/BB_PRJ_ET01 written to the Database |
369 | Table /SMB/BB_PRJ_H written to the Database |
370 | Table /SMB/BB_PRJ_HT written to the Database |
371 | Table /SMB/BB_AAE written to the Database |
372 | Table /SMB/BB_AAE_T written to the Database |
373 | Table /SMB/BB_AAE_ASG written to the Database |
374 | Table /SMB/DOC_MT_MODE written to the Database |
375 | Table /SMB/BBPR_ET02 written to the Database |
376 | Change Records of files which are not in the solution anymore |
377 | File &1 is not in scope of the solution anymore |
378 | The definition of the file &1 was changed incompatibly |
379 | Reference &1 cannot be used anymore in parameter &2 |
380 | Customer Adaptations require a different definition |
381 | Create an incident on BCP component &1 (file &2 in Building Block &3) |
382 | Create an incident on BCP component &1 (solution &2 - edition &3) |
383 | Installation Data is not fully uploaded, force mode required |
384 | An error occurred during Import of Customer Adaptations |
385 | Previous import status is in process, force mode enabled to fix this |
386 | Customer Adaptations were imported for Solution &1 |
387 | Import of Customer Adaptations: Always upload latest solution again |
388 | Processor is set to force a new upload |
389 | Processor is set to skip procedure and activation |
390 | Processor is set to skip activation |
391 | Processor is set to use the procedure: &1 |
392 | If no batch jobs are available, upload will continue in dialogue process |
393 | If no batch jobs are available, a popup will be shown |
394 | If no batch jobs are available, upload will wait for batch jobs |
395 | Starting Procedure: &1 |
396 | Procedure &1 is not supported |
397 | Procedure finished: &1 |
398 | Creating a backup of the current installation data |
399 | Backup of installation data not needed anymore, deleted |
400 | Solution Activation Settings of &1 not found |
401 | Solution import error due to missing installation data |
402 | Solution was improved |
403 | After Import Manager Version: 1511 CE no hotfix |
404 | Local lock is active, lifecycle process skipped for client &1 |
405 | Global lock is active, lifecycle processes skipped. |
406 | Restoring the installation data from backup |
407 | Previous processor still in process in upload phase |
408 | No backup found for solution &1, cannot restore |
409 | Previous processor failed in installation data upload, restore backup |
410 | Solutions considered in release |
411 | No business change project found, nothing to release |
412 | Releasing task &1/&2 of &3 |
413 | All lifecycle relevant Solutions are activated |
414 | At least one lifecycle relevant Solution is not activated |
415 | Solution &1 needs to be activated manually |
416 | BO Mapping copied from &1 to &2 |
417 | All changes to IMG have been removed |
418 | IMG contains same settings as before the activation has been started |
419 | Activation started from SSC-UI |
420 | &1 is no allowed attribute |
421 | Task Activation History |
422 | Runtime PME |
423 | Change Records |
424 | Flex Org History |
425 | Applying Content Restructuring &1 |
426 | Content Restructuring &1 applied |
427 | &1 records created in table &2 |
428 | &1 records deleted from table &2 |
429 | Archiving db records |
430 | Repeating import with Add Language due to previous result in Imp. History |
431 | Processor is set to skip add language due to skip of procedure/activation |
432 | New Languages in solution &1 are active |
433 | Failed to set new language in solution &1 to status active |
434 | Object requested is locked by user &2. Retry at a later timepoint. |
435 | Error at determination of new languages |
436 | All available Reference Content objects were previously processed |
437 | New languages are assigned to the solution |
438 | File &1 is not uploaded |
439 | Consistency check stopped after &1 errors |
440 | Error when checking &1 in file &2 - variant &3 parameter &4 |
441 | Cannot find definition for file &1 |
442 | Consistency check successful |
443 | An error occurred while checking file upload status |
444 | Files are not uploaded - possible deletions of reference content |
445 | File &1 is not uploaded or its content was deleted by finetuning |
446 | Starting Post-Processing Steps |
447 | Cannot resolve reference &1 in file &2 variant &3 parameter &4 |
448 | Solution status is &1 (activation status &2) |
449 | Content Lifecycle is currently prohibited (Global lock set by SPC) |
450 | Content Restructuring |
451 | Starting Content Restructuring |
452 | Content Restructuring finished |
453 | An error occurred during Content Restructuring |
454 | Solution &1 will be activated after SPC releases Content Framework Lock |
455 | No changes determined for solution &1, setting it to activated |
456 | Special handling for interrupted solution in initial activation |
457 | Solution &1 has no changes |
458 | Activation continues after SPC releases Content Framework Lock |
459 | Solution &1 is in Scope Extension or Add New Country/Region |
460 | Lifecycle is not allowed for this solution |
461 | You must manually regenerate the Scope Extension or Add Ctry/Reg solution |
462 | Follow the Admin Guide steps to ensure completion of Add New Language |
463 | The Content Framework lock is not set anymore - no automatic continuation |
464 | Errors when setting the delta solution to be activated to &1 |
465 | Check solution &1 and manually start its activation |
466 | Solution &1 will not be activated after SPC releases Content Framew. Lock |
467 | Errors when releasing the Content Framework Lock for Lifecycle |
468 | Content Framework Lock cannot be released in client &1 |
469 | Content Framework Lock is set, releasing for Lifecycle |
470 | Content Framework Lock released for Lifecycle |
471 | Errors occurred when setting solution &1 to activated |
472 | No Content Lifecycle in Clean Client &1 |
473 | Lifecycle Client &1 is not yet usable |
474 | No Customer Solution scoped -> No Content Lifecycle in client &1 |
475 | Follow-on activies required for Solution &1 |
476 | Improvement of Solution &1 didn't finish successfully (CL Import History) |
477 | Invalid Lifecycle Processor &1 |
478 | Lifecycle Processor &1 could not be enabled |
479 | Lifecycle Processor &1 is already enabled |
480 | Lifecycle Processor &1 enabled |
481 | Lifecycle Processor &1 is already disabled |
482 | Lifecycle Processor &1 disabled |
483 | Lifecycle Processor &1 could not be disabled |
484 | Client &1: Invalid Business Type |
485 | Content Lifecycle operations in progress (Client &1) |
486 | Previous processor failed in ID clash resolution, restore backup |
487 | Cross-client lock not set: parallel lifecycle in multi clients possible |
488 | Source Solution misssing for Solution &1 |
489 | Package Id missing for Solution &1 |
490 | Solution Builder Cleanup |
491 | Starting Solution Builder Cleanup |
492 | Solution Builder Cleanup finished |
493 | An error occurred during Solution Builder Cleanup |
494 | &1 (not activated) Reference Solutions in Solution Builder |
495 | &1 Source Solutions in scoped Customer Solutions |
496 | &1 Reference Solutions will be deleted |
497 | Content Lifecycle completeness check |
498 | Content Lifecycle is not complete -> Solution Builder Cleanup aborted |
499 | Number of entries which meet the selection criteria: &1 |
500 | Starting to read all TDC record for LC relevant solutions |
501 | Read all TDC record for LC relevant solutions |
502 | Starting TDC ID resolution for new TDs |
503 | TDC Id &1 resolved to &2 for parameter &3 for file &4 |
504 | Updated new TDC id in PME records |
505 | Recorded changes in new Resolve ID change group |
506 | TDC ID resolution completed |
507 | There is no clash in TDC IDs |
508 | Starting to read all TDC records for LC solutions from DEV Client for Q2P |
509 | No Data found in Dev Client |
510 | TDC ID &1 resolved in Dev Client |
511 | Data retrieved sucessfully from Dev Client |
512 | Content Lifecycle is complete |
513 | Content Lifecycle is not complete |
514 | Follow-on activities (SCE/ANC) are required |
515 | No follow-on activities (SCE/ANC) are required |
516 | Reorganizing Reference Solutions in Solution Builder |
517 | Reorganizing APPLIED Change Groups from Customer Solutions |
518 | Deleting &1 APPLIED Change Groups |
519 | Change Group &1 of Solution &2 (Type: &3, ID: &4) deleted |
520 | Lifecycle processor '&1' is only to be executed in standard cloud system |
521 | Reorganizing Building Block Versions |
522 | &1 Building Block Versions available in the archive |
523 | Testrun: Lifecycle completeness check ignored |
524 | Testrun: No Solution will be deleted |
525 | Testrun: No Change Group deleted |
526 | &1 Building Block Versions will be deleted from the archive |
527 | BB ID: &1, Created: &4, Version: &2, Assign ID: &3 deleted |
528 | Testrun: No Building Block Version will be deleted |
529 | &1 entries found matching your criteria |
530 | Working on files: |
531 | File &1 ignored as activity &2 &3 is no IMG activity |
532 | File &1 ignored as no parameter of type NUMC was adapted |
533 | Checking installation data status of Customer Solutions |
534 | Installation data OK |
535 | -> Content Restructuring in Content Lifecycle, see /SMB/TRANS_LOG |
536 | -> Importing and applying Content Restructuring &1 |
537 | No design time or runtime data to convert |
538 | -> Importing and applying Content Restructuring &1 |
539 | Starting Dynamic Content Restructuring (XPRA) |
540 | Dynamic Content Restructuring (XPRA) finished |
541 | An error occurred during Dynamic Content Restructuring (XPRA) |
542 | Profile Parameters |
543 | Value of the profile parameter '&1' could not be determined |
544 | Value of the profile parameter '&1' is '&2' (min. &3) |
545 | Finished successfully working on &1 |
546 | Create an incident on BCP component &1 (Xpra for Cont. Restructuring &2) |
547 | Repeating Content Restructuring due to previous result in Import History |
548 | &1 change(s) are not needed |
549 | Skipped some basic checks not required in P system of new Q2P environment |
550 | Activation status '&1' of Solution &2 is not consistent |
551 | -> Log of Flex Org Replay |
552 | Flex Org Replay completed, changes executed |
553 | Flex Org Replay completed without changes |
554 | Flex Org Replay |
555 | -> Importing and applying Content Restructuring &1 in Solution &2 |
556 | -> Log of Solution Builder Cleanup |
557 | -> SB Cleanup in Content Lifecycle, see /SMB/TRANS_LOG |
558 | Starting TDC conflict repair |
559 | No remaining conflicts, TDCs are consistent |
560 | Conflicts remaining |
561 | Activation settings taken from solution &1 - activate with demo data |
562 | Activation settings taken from solution &1 - activate without demo data |
563 | Wrong system setup, newer content uploaded than in reference content |
564 | Migrate Data |
565 | Errors occurred in data migration, stopping content lifecycle |
566 | Create an incident on component &1 |
567 | Content Restructuring |
568 | Scope Bundle &1 ctry/reg. &2 will be added to customer selected scope |
569 | Bundle &1 Scope Item &2 will be added to customer selected scope items |
570 | Scope Bundle &1 ctry/reg. &2 will be deleted from customer selected scope |
571 | Scope Bundle &1 ctry/reg. &2 will be updated in customer selected scope |
572 | Bundle &1 Scope Item &2 will be deleted frm customer selected scope items |
573 | Bundle &1 Scope Item &2 will be updated in customer selected scope items |
574 | Scoping: customer selected scope written to DB |
575 | Improvement or Scoping of Solution &1 didn't finish successfully |
576 | Not all Content Lifecycle processors are enabled in this client |
577 | Finetuning Infrastructure (table /FTI/BCO) is not available in the system |
578 | This is no S/4HANA or cloud system |
579 | This is no ABAP Platform Cloud system |
580 | CBC is active in this system |
581 | &1 change(s) don't need to be applied |
582 | Scheduling report /SMB99/TECH_OBJ_ACT |
600 | Starting flex org replay for solution &1 |
601 | Flex org replay finished for solution &1 |
602 | Flex org replay failed for solution &1 |
603 | Reusing source id from history if source id not passed during replay. |
604 | Reusing variant ID from history during cdata entry in case of replay. |
605 | LC:Improvement,allowing cdata entry only in improvement in flexorg replay |
606 | Copying PME records. |
607 | Suppressing global entity cascading in flex org replay mode. |
608 | Saving in history newly created standard type entity and its activities. |
609 | Saving in history newly created additional relation and its activities. |
610 | Saving in history newly created combined type entity and its activities. |
611 | Fetching all timestamps from orgext history table for this solution. |
612 | Fetching all customer adaptation change packages relevant for flex org. |
613 | Fetching all active change groups relevant for flex org. |
614 | Replaying creation of standard type org entity &1:&2. |
615 | Replaying creation of standard type org entity successful. |
616 | Replaying creation of standard type org entity failed. |
617 | Variant ID not available for target entity(Type - &1 ,ID - &2) for reuse. |
618 | &1 &2 is not a valid flex org extention case. |
619 | Replaying creation of additional relation |
620 | Replaying creation of additional relation failed. |
621 | Changes to history table saved. |
622 | Suppressing activation in flex org replay mode. |
623 | Creating instance of class failed. |
624 | Replaying creation of combined type org entity |
625 | Conversion from inner to combined ID failed. |
626 | Replaying creation of combined type org entity successful. |
627 | Replaying creation of additional relation successful. |
628 | Replaying creation of combined type org entity failed. |
629 | Replaying import and applying of change package failed. |
630 | Replaying applying of change group started. |
631 | Replaying applying of change group finished. |
632 | Replaying applying of change group failed. |
633 | Replaying creation of additional relation between &1:&2 - &3:&4 |
634 | Replaying creation of combined type org entity &1:&2 |
635 | Failed to identity the combined type involved in additional relation. |
636 | Flex org replay not done as there was no improvement applied to solution |
637 | Solution &1 product attributes changed from &2 to &3 |
638 | Performing automatic migration |
639 | Error: Email cannot be sent |
640 | New Q2P is active |
641 | Old Q2P is active |
642 | Business type of current client &3 is &1 (&2) |
643 | Project client &1 is leading client |
644 | Lifecycle client &1 is leading client |
645 | Business Change Project has status &1 (&2) in client &3 |
646 | Lifecycle Project has status &1 (&2) |
647 | Status of Business Change Project |
648 | Status of Lifecycle Project changed to &1 (&2) |
649 | Status of Business Change Project changed to &1 (&2) in client &3 |
650 | Lifecycle Project &1 created |
651 | Lifecycle Project |
652 | Error during creation of Lifecycle Project |
653 | Error during status change of Lifecycle Project |
654 | Error during status change of Business Change Project |
655 | Current Client is Lifecycle Client |
656 | Current Client is Project Client |
657 | Release Lifecycle Project |
658 | Q2P Project Manager |
659 | Error in Q2P Project Manager |
660 | Project/Maintenance client: &1 |
661 | Lifecycle client: &1 |
662 | Business Change Project |
663 | Lifecycle Project |
664 | New Q2P Configuration: Client Business Type cannot be determined |
665 | Activation for Solution &1 from Lifecycle |
666 | Activation for Solution &1 from Expert Configuration |
667 | Activation for Solution &1 from Flex-Org |
668 | Activation for Solution &1 from Implementation Assistant |
669 | Activation for Solution &1 from SSC-UI |
670 | Downloaded CR-Mapping &1 successfully. |
671 | Downloaded CR-Mapping &1 not successfully. |
672 | Imported CR-Mapping &1 successfully. |
673 | Imported CR-Mapping &1 not successfully. |
674 | Consistency Check for CR-Mapping &1 succeeded. |
675 | CONTREST_2_XML during exporting CR-Mapping &1 is successful. |
676 | Exported CR-Mapping &1 successfully. |
677 | Exported CR-Mapping &1 not successfully. |
678 | Select local file failed. |
679 | Upload local file (&1) failed. |
680 | Imported CR-Mapping failed. Please see details in the application log. |
681 | Imported CR-Mapping successfully. |
682 | Exported CR-Mapping failed. Please see details in the application log. |
683 | Exported &1 CR-Mappings successfully. |
684 | Execute Consistency Check |
685 | Consistency Check for CR-Mapping &1 failed |
686 | Exported CR-Mapping &1 successfully |
687 | Don't execute Consistency Check |
688 | According to File State no changed files found |
689 | According to File State &1 changed files found |
690 | No Content Lifecycle in unknown Client Business Type &1 '&2' |
691 | &1 is considered for File Import. |
700 | Implementation Phase should be set to Realize In Progress. |
701 | Solution &1 is not active for Content Lifecycle operations. |
702 | Updated global timestamps to orgext history table for this solution. |
703 | Variant-Id: &1 Filename: &2 |
704 | File downloaded successfully |
705 | Error in downloading the file |
706 | Report execution cancelled. |
707 | Foreign key check results |
708 | Table: &1 |
709 | Table Key: &1 Field: &2 Value: &3 Checktable: &4 |
710 | Transport request contains foreign key errors - Cannot be released |
711 | Transport: &1 |
712 | No Data in file for TDC |
713 | Reading Fine-Tuning Change Groups |
714 | Error in getting adaptation change packages from solution &1 |
715 | Error in getting active change groups from solution &1 |
716 | Post report &2 started successfully for solution &1 |
717 | Processor is set to skip ANC due to skip of procedure/activation |
718 | BDM attributes of solution &1 and its ANC solution are different |
719 | BDM attributes of solution &1 and its SCE solution are different |
720 | Status &1 is not processed in method &2 |
721 | Check whether mapping of G/L Account is required |
722 | File &1 is missing and therefore to be processed |
724 | Solution &1 is successfully created again |
725 | Failed to create solution &1 again |
726 | File &1 has been changed |
727 | File &1 has not been changed |
728 | Calculate Delta-Based Content Lifecycle for solution &1 |
729 | &1 files are checked for changes |
730 | Start working on reference changes |
731 | Reference change for object id &1 |
732 | No file was found for object &1 |
733 | Number of change records modified: &1 |
734 | File State: Change group is cloned with filter (&1 files) |
735 | Upload of installation data is not required |
736 | File State for file &1 found |
737 | File State has not changed (to be processed: &1) |
738 | New File State for file &1 |
739 | File State for file &1 has changed. File &1 has to be processed |
740 | File State for file &1 has been reset to initial |
741 | Generate File State for Solution &1 |
742 | -> Generation of File State for Solution &1 is successful |
743 | Reset File State for Solution &1 |
744 | Number of change records going to be modified: &1 |
745 | -> Generation of File State for Solution &1 failed |
746 | Synchronizing of Central data files begin |
747 | Synchronizing of Central data files failed.Manual treatment is necessary. |
748 | End of Central data files synchronization. |
749 | Design time installation data contains entry with invalid value '&1' |
750 | Start creating new references for solution &1 |
751 | &1 records need to be processed |
752 | Start creating new references for field &1 &2 &3 |
753 | Field is not part of the installation data |
754 | &1 records were processed succesfully |
755 | Creating new references for solution &1 was successful |
756 | Errors occured during creating new references for solution &1 |
757 | Field was processed successfully |
758 | An occurred an error while processing the field |
759 | Dereferenced installation data value differs from expected one. Ignore! |
760 | Added new value '&1' to centraldata file. New reference is &2 |
761 | Creating new reference in installation data is prepared |
762 | Installation data entry '&1' not contained in new centraldata file |
763 | Entry &1 is contained in new centraldata file already, reference is &2 |
764 | Start creating new references for Content Restructuring ID &1 |
765 | An error occurred during content restructuring 'Reference Change' |
766 | File &1 does not exist in solution &2 |
767 | Start referencing change reccords |
768 | Start referencing runtime PME |
769 | Process file &1, parameter &2 and hash &3 |
770 | Not all change records for file referenced yet. Stop processing |
771 | Start referencing runtime PME for Content Restructuring ID &1 |
772 | &1 records are updated in runtime PME |
773 | For this field no entry could be found in runtime PME |
774 | Installation data value '&1' not contained in TDC &2 for parameter &3 |
775 | There is no entry for PME value &1 for parameter &2 in TDC &3 |
776 | Updated runtime PME entry with new reference &1 and id &2 |
777 | -> Apply content restructurings of type 'Ref Change' for solution &1 |
778 | This field has no TDC reference. No further processing is needed |
779 | No change records need to be referenced. No further processing is needed |
780 | No RT PME entries need to be referenced. No further processing is needed |
781 | ID &1 for &2 is resolved in prev soln,so activated IDs check is skipped |
782 | Reference &1 could not be dereferenced. |
783 | The original reference &1 can not be dereferenced |
784 | This field refers to a reference change of type delete. Nothing to do |
785 | File &1 is not part of any customer solution. Finished |
786 | No inconsistent TDC-related entries found. |
787 | Reference &1 on DT PME was not deleted for file &2. Replace by value '&3' |
788 | Remaining references in DT PME could not be modified. Rework is required |
789 | Force mode: Delete File State of Solution &1 |
790 | Processing not ok: File State of solution &1 is adjusted |
791 | Country/Region &1 not found in Inactive Reference Content |
792 | Unexpected reference &1 found on DT PME for file &2 |
793 | Start Report to fix missing TDC references |
794 | Running ANC transfer report for solution &1 |
795 | The report is obsolete starting SAP S/4HANA Cloud 2002 Release |
796 | -> ANC transfer report for solution &1 |
797 | Failed saving automatic correction of TDC inconsistencies |
798 | Fixed: Cannot resolve reference &1 in file &2 variant &3 parameter &4 |
799 | AIM is not active: no processing of Solution Builder Content |
800 | Empty filename was found in ZIP: &1. |
801 | Filename &1 is used by solution &2 but not within ZIP &3. |
802 | Get files for File State Calculation |
803 | Number of runtime PME records going to be modified: &1 |
804 | Installation data value is initial and doesn't need to be referenced |
805 | Delta-Based Content Lifecycle manually suppressed |
806 | Error in file state calculation, delta-based Content Lifecycle suppressed |
807 | Prev. upgrade sol. not activated, no delta-based Cont. LC in UPG proc. |
808 | Not activated org. entity found, no delta-based Content LC in UPG proc. |
809 | Delta-Based Content Lifecycle |
810 | Delta-Based Content Lifecycle suppressed due to issues |