TN - Support Package Manager (SPAM) Meldungen
The following messages are stored in message class TN: Support Package Manager (SPAM) Meldungen.
It is part of development package SPAM in software component BC-UPG-OCS. This development package consists of objects that can be grouped under "OCS - Installation/Implementation Tools".
It is part of development package SPAM in software component BC-UPG-OCS. This development package consists of objects that can be grouped under "OCS - Installation/Implementation Tools".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Failed to connect to server for SAPNet - R/3 Frontend |
| 001 | Support Package &1 could not be inserted in the &2 buffer |
| 002 | Could not schedule RDDIMPDP as a background job |
| 003 | Could not create versions of objects in Support Package &1 |
| 004 | Invalid WHEN parameter in function module |
| 005 | Requirements for import have not been met |
| 006 | Test import of Support Package &1 terminated |
| 007 | Could not import command file for Support Package &1 |
| 008 | DDIC import of Support Package &1 terminated |
| 009 | Function SUMO_ADD_PATCH: Support Package &1 could not be inserted |
| 010 | Internal error: &1 &2 &3 &4 |
| 011 | Function &1: No entry exists / RSUMODSP has not run for &2 |
| 012 | Main import of Support Package &1 has terminated |
| 013 | Failed to insert/update Support Package &1 in PAT03 |
| 014 | Failed to insert/update Support Package &1, phase &2 in PAT01 |
| 015 | OCS Package &1 does not exist in the system |
| 016 | &1: Data file and/or cofile not in SAP transport directory |
| 017 | Import parameters of function module &1 are inconsistent |
| 018 | Could not restart import of Support Package &1 |
| 019 | Run &1 terminated by user &2 |
| 020 | Update for parcel &1 in table TEPSIN failed |
| 021 | &1 Support Packages successfully downloaded from SAPNet - R/3 Frontend |
| 022 | Support Package &1 is not in table PAT03 |
| 023 | Support Package &1 was already imported into Release &2 |
| 024 | Support Package &1 was recalled |
| 025 | Backup &1 for Support Package &2 not found |
| 026 | Import of Support Package &1 was rejected by user &2 |
| 027 | Could not determine EPS parcel for OCS Package &1 |
| 028 | Could not determine cofile name for Support Package &1 |
| 029 | Could not determine data file name for Support Package &1 |
| 030 | Disassembling cofile of Support Package &1 terminated |
| 031 | Disassembling R3trans data file of Support Package &1 terminated |
| 032 | Disassembling SDO data file of Support Package &1 terminated |
| 033 | Disassembling Support Package &1 terminated |
| 034 | Download from SAPNet - R/3 Frontend failed |
| 035 | Download from SAPNet - R/3 Frontend rejected by user &1 |
| 036 | Could not insert Support Package &1 in PAT03 |
| 037 | Support Package &1 may not be imported into Release &2 |
| 038 | Support Package &1 cannot be imported into a &2 operating system |
| 039 | Support Package &1 may not be imported into a &2 database |
| 040 | Support Package &1 is already contained in Release &2 |
| 041 | Support Package &1 does not have a valid SAP Release |
| 042 | You did not request Support Packages from the SAPNet - R/3 Frontend |
| 043 | No Support Packages found for this selection |
| 044 | Only display functions are available |
| 045 | The complete import of OCS Package &1 has not yet been confirmed |
| 046 | OCS Package &1 not yet imported completely |
| 047 | OCS Package &1 confirmed |
| 048 | Import Support Package &1 after Support Package &2 |
| 049 | OCS Package &1 has not been imported yet |
| 050 | OCS Package &1 already confirmed |
| 051 | You have no authorization for the OCS transactions |
| 052 | Backup request &1 for Support Package &2 could not be created |
| 053 | File &1 could not be deleted |
| 054 | Support Package cannot be imported during kernel switch or downtime |
| 055 | Backup &1 for Support Package &2 could not be deleted |
| 056 | Import is not possible due to locked objects |
| 057 | No add-on found |
| 058 | RFC System error &1 &2 &3 &4 |
| 059 | RFC communication error &1 &2 &3 &4 |
| 060 | Specify the target system |
| 061 | Selection criteria are not met |
| 062 | User SAP* may not import Support Packages |
| 063 | Cannot print |
| 064 | No Support Packages were downloaded |
| 065 | Deletion of backup file &1 failed |
| 066 | Cofile &1 for Support Package &2 could not be created |
| 067 | No adjustment of modifications required |
| 068 | & already has status 'New' |
| 069 | Status of & was reset |
| 070 | Do not reset status of & |
| 071 | Cofile &1 could not be opened |
| 072 | File LAST.HOT Created |
| 073 | Do not insert Support Package &1 (type &2) in the file LAST.HOT |
| 074 | Program may only run in background |
| 075 | File &1&2 could not be opened. &3&4 |
| 076 | No Support Packages were reset |
| 077 | Support Package Manager (Transaction SPAM) Date &1, Time &2 |
| 078 | Conflicts found between Support Packages (&3) and &1/&2 |
| 079 | &1 Support Package level accepted |
| 080 | ************************************************************************* |
| 081 | Invalid Release |
| 082 | No add-ons installed in system (table AVERS empty) |
| 083 | Support Packages imported into system &1: |
| 084 | Add-on &1/&2 contains Support Packages: &3-&4 |
| 085 | &1 &2 &3 &4 |
| 086 | Determine conflicts between Support Packages and add-on &1/&2 |
| 087 | No Support Packages were imported in system &1 |
| 088 | Add-on &1/&2 does not contain any Support Packages |
| 089 | No conflicts found |
| 090 | Your action: None |
| 091 | Use the Support Package Manager to import Support Packages &1-&2 |
| 092 | Use the Support Package Manager to import the corresponding CRTs |
| 093 | Unable to determine path for file &1 |
| 094 | &1 is not the Support Package that was last imported |
| 095 | Use the Support Package Manager to import &1 again |
| 096 | Generation is not faulty: RSSPAM03 is not executed |
| 097 | OCS Package &1 has incorrect status (&2) |
| 098 | You have not yet imported Support Packages &1-&2 |
| 099 | If there are conflicts, apply the corresponding CRTs with SPAM |
| 100 | Error writing log &1 |
| 101 | Table &1 is empty |
| 102 | This function has not been released yet |
| 103 | Relevant Support Package add-on ID (PAOID) does not exist |
| 104 | Import Support Package &1 first |
| 105 | Maintenance level &1 contains Support Package &2 |
| 106 | Update of table PAT05 aborted |
| 107 | Cursor is not positioned on a valid field |
| 108 | Scenario "&1" is invalid |
| 109 | Phase & is invalid |
| 110 | Selection was completed |
| 111 | Nothing was selected |
| 112 | The OCS Package Queue is empty |
| 113 | Queue is consistent |
| 114 | You have not selected anything |
| 115 | Settings were updated |
| 116 | Download &1 first |
| 117 | Support Package queue was confirmed |
| 118 | Internal error: Could not specify queue |
| 119 | Check queue first |
| 120 | Predecessor &1 of &2 does not exist |
| 121 | Status of queue reset |
| 122 | No SPAM/SAINT update found |
| 123 | SPAM/SAINT update &1 has already been imported successfully |
| 124 | Download performed |
| 125 | Support Package &1 imported successfully according to scenario '&2' |
| 126 | &1 &2 not yet imported |
| 127 | Internal error: Phase & could not be initialized |
| 128 | Phase & terminated |
| 129 | Only choose scenario 'S' or 'T' |
| 130 | Support Package &1 could not be removed from &2 buffer |
| 131 | Queue &1 imported successfully according to &2 scenario: Confirm this |
| 132 | Queue &1 - &2 imported successfully according to &3 scen.: Confirm this |
| 133 | Queue already confirmed |
| 134 | Queue set up |
| 135 | SPAM/SAINT update cannot be imported |
| 136 | First import SPAM/SAINT update &1 completely |
| 137 | &1 does not exist |
| 138 | Queue is not empty |
| 139 | EPS parcel & & is not in TEPSIN |
| 140 | Table conversions can now be started with Transaction ICNV |
| 141 | Queue is no longer in buffer &1 |
| 142 | Error calling RFC tp interface |
| 143 | Generation errors were ignored |
| 144 | No generation errors found |
| 145 | Scenario in queue was changed from '&1' to '&2' |
| 146 | &1 imported successfully according to &2 scenario: Confirm this |
| 147 | Queue &1 imported successfully according to &2 scenario |
| 148 | Queue &1 - &2 imported successfully according to &3 scenario |
| 149 | &1 &2 imported successfully |
| 150 | There are no Support Packages of the type &1 in the system |
| 151 | Program tp did not execute successfully |
| 152 | Queue is inconsistent |
| 153 | Caution: Upgrade or PREPARE is still running; import not permitted |
| 154 | Error during RFC call |
| 155 | File & does not exist |
| 156 | Main export ended with return code & |
| 157 | ADO export ended with return code & |
| 158 | Error during RFC call |
| 159 | Status of the SPAM/SAINT update has been reset |
| 160 | For Support Package type &1, an entry is missing in file &2 |
| 161 | Software component &1 with Release &2 does not exist |
| 162 | Support Package type is &1, but software component &2 does not exist |
| 163 | SPAM/SAINT update has already been confirmed |
| 164 | You may only perform this function according to scenario '&' |
| 165 | &1 &2 integrated in the upgrade |
| 166 | &1 &2 imported without the Support Package Manager |
| 167 | Target release is unknown: Run PREPARE |
| 168 | No Support Packages were found for Release & |
| 169 | Support Package & already included in the upgrade |
| 170 | Including Support Package & in the upgrade |
| 171 | Step &1: Determine EPS parcel path |
| 172 | Step &1: Determine source path of R3trans data file |
| 173 | Step &1: Determine target path of R3trans data file |
| 174 | Step &1: Determine source path of ADO data file |
| 175 | Step &1: Determine target path of ADO data file |
| 176 | Step &1: Determine source path of cofile |
| 177 | Step &1: Determine target path of cofile |
| 178 | Step &1: Skip attribute record in EPS parcel |
| 179 | Step &1: Disassemble R3trans data file |
| 180 | Step &1: Disassemble ADO data file |
| 181 | Step &1: Create cofile |
| 182 | Step &1: Copy &2 to &3 |
| 183 | Step &1: Set status to 'included' |
| 184 | Include ended successfully |
| 185 | Include terminated |
| 186 | Path = & |
| 187 | Phase &1 terminated due to reason &2 |
| 188 | There is no ADO data file |
| 189 | Restart SPAM and read the current information ('i' button) |
| 190 | &1 has an invalid Basis Release &2 |
| 191 | &1 has an invalid operating system &2 |
| 192 | &1 has an invalid database system &2 |
| 193 | SPAM/SAINT update &1 has a lower version (&2) than SPAM (&3) |
| 194 | &1 requires at least version &2 of the Support Package Manager |
| 195 | Attribute &1 for &2 is unknown. A SPAM/SAINT Update is required... |
| 196 | No OCS files were found for uploading |
| 197 | Not all Support Packages for CCRT &1 are in the queue |
| 198 | Predecessor &1 for &2 missing |
| 199 | Could not update package level for component &1 |
| 200 | System inconsistency: Incorrect &1 entry |
| 201 | Invalid combination of options for handling data files |
| 202 | Could not delete data file &1 for OCS Package &2 |
| 203 | You can no longer change the scenario |
| 204 | There are no Support Packages in step '&1' |
| 205 | Error during database update of table PAT01 |
| 206 | Test import errors ignored |
| 207 | OCS Package &1 is already in processing |
| 208 | OCS Package &1 is already applied |
| 209 | Queue contains a language package. Use transaction SMLT. |
| 210 | Queue contains an add-on installation/upgrade. Use transaction SAINT. |
| 211 | Queue contains a Preconfigured System. Use transaction SAINT. |
| 212 | No OCS Packages found for this selection |
| 213 | The OCS Package is not contained in the tree |
| 214 | . |
| 215 | You cannot continue; queue already processed |
| 216 | You cannot switch on/off the creation of versions at present |
| 217 | Package &1 is too old (data format not suitable for CHECK_FREESPACE) |
| 218 | After the import, you have to perform some follow-up activities |
| 219 | The system found conflicts for add-on &1 release &2 (see list): |
| 220 | Support Package &1 of software component &2 release &3 |
| 221 | Support Package &1 of add-on component &2 release &3 |
| 222 | Installation package &1 of add-on component &2 release &3 |
| 223 | Piece list &1 of already installed add-on component &2 release &3 |
| 224 | Unknown package &1 of type &2 |
| 225 | ... has conflicts with &1 release &2 - piece list: &3 |
| 226 | Conflict check for Add-On &1 Release &2 with |
| 227 | Check all add-ons to determine whether conflict check is necessary... |
| 228 | Conflict check for add-on &1 release &2 is not necessary |
| 229 | Conflict check for add-on &1 release &2 is necessary |
| 230 | Conflict resolution by including a CRT for &1 release &2 and &3 |
| 231 | Conflict resolution by not installing of either &1 rel.&2 or &3 rel.&4 |
| 232 | Conflict resolution by not installing of &1 release &2 |
| 233 | Unresolvable conflict (maybe error in the conflict calculation) |
| 234 | Disassemble OCS package &1 ... |
| 235 | ... Data and cofiles for OCS package &1 successfully created |
| 236 | Calculation of the installation queue of included add-ons ... |
| 237 | The following queue was calculated: |
| 238 | &1: &2 - Installation Package for &3 Release &4 |
| 239 | &1: &2 - Support Package for &3 Release &4 |
| 240 | Adding the language packages for the language vector &1 ... |
| 241 | The following language packages were added: |
| 242 | &1 for language &2 of software component &3 release &4 |
| 243 | Calculating the Support Package queue with the following input queue ... |
| 244 | No language packages were added |
| 245 | The following import prerequisites of OCS Package &1 have not been met: |
| 246 | Support Package &1 must be available or already imported in the system |
| 247 | The calculation is based on the following software component vector: |
| 248 | Component: &1 rel. &2, Support Package level: &3 (component type &4) |
| 249 | The following target vector shall be attained: |
| 250 | Start of phase: &1 |
| 251 | End of phase: &1 |
| 252 | Start date: &1 |
| 253 | Start time: &1 |
| 254 | End date: &1 |
| 255 | End time: &1 |
| 256 | You want to install the following add-on components: |
| 257 | No add-on components were specified to be installed |
| 258 | Add-on &1 release &2 must be installed in the system |
| 259 | Prerequisite &1 has to be fulfilled |
| 260 | The Installation/Upgrade Package for Add-on &1 rel. &2 is not available |
| 261 | Queue import creates the following software component vector: |
| 262 | Calculating queue part for add-on &1 rel. &2 |
| 263 | The following overall queue was calculated: |
| 264 | In the (alternatively) Requirement set &1: |
| 265 | Saving the current OCS Queue (&1, &2) |
| 266 | &1: &2 - SPAM/SAINT Update |
| 267 | Deleting the current OCS Queue (&1, &2) &3 |
| 268 | The OCS Queue is already empty -> no deletion necessary |
| 269 | Reset OCS Package &1 |
| 270 | The import of the OCS Queue is stopped in phase '&1' |
| 271 | Reset the Add-on &1 rel.&2 |
| 272 | Reset the Preconfigured System &1 rel.&2 |
| 273 | Reset the status of the current OCS Queue (&1, &2) &3 |
| 274 | The OCS Queue is empty -> no reset possible |
| 275 | The reset of the status of the OCS Queue was aborted by the user |
| 276 | Confirm the successful import of the OCS Queue (&1, &2) |
| 277 | Confirm the OCS Package &1 |
| 278 | Delete the respective data files... |
| 279 | Set the status of the PCS &1 rel.&2 to '&3' |
| 280 | Set the status of the Add-on &1 rel.&2 to '&3' |
| 281 | Set the language vector of the Add-on &1 to '&2' |
| 282 | Log '&1' was not found or is empty |
| 283 | Import of the current OCS Queue (&1, &2) |
| 284 | The current OCS Queue consists of: |
| 285 | The import is continued in phase '&1' |
| 286 | The import will not be started |
| 287 | Display notes, which should be considered before the start of the import |
| 288 | Note &1 for OCS Package &2 (Password is required) |
| 289 | Note &1 for OCS Package &2 |
| 290 | The import was cancelled by the user |
| 291 | Display note &1 in SAP Support Portal |
| 292 | Correct password for OCS Package &1, note &2 was given |
| 293 | Wrong or no password for OCS Package &1, note &2 was entered |
| 294 | Schedule the import for background processing (for immediate start) |
| 295 | Schedule the import for background processing (planned start: &1, &2) |
| 296 | The import of the queue was successfully finished (&1, &2) |
| 297 | Component &1 is locked against OCS Package imports |
| 298 | Error during Insert/Update of database table &1 |
| 299 | OCS Package &1 is a SPAM/SAINT-Update |
| 300 | You may only reset the flag if type &1 &2 has not yet been imported |
| 301 | You do not have authorization S_PTCH_ADM w/activity &1 for values &2 &3 |
| 302 | You may only set type &3 if type &1 has not terminated |
| 303 | From now: Import of types &1 &3 instead of types &2 &4 |
| 304 | From now: Import of types &2 &4 instead of types &1 &3 |
| 305 | Type &1 &2 activated. Read Note(s) &3 &4 |
| 306 | Not all conflicts were resolved. See long text |
| 307 | Import mode 'Downtime-minimized' will be deactivated |
| 308 | Import mode 'Downtime-minimized' is activated |
| 309 | Import mode 'Downtime-minimized' is deactivated |
| 310 | Browser started. Please wait ... |
| 311 | You cannot change the import mode at present |
| 312 | Abort the import due to an error situation (&1, &2) |
| 313 | Intended stop of the import (&1, &2) |
| 314 | Interrupt the import due to an error situation (&1, &2) |
| 315 | Display detailed informations concerning the error in phase '&1' |
| 316 | Repeat the import of the OCS Queue in phase '&1' |
| 317 | Skip the errors in phase '&1' and continue the import |
| 318 | The import is done with the &1 scenario |
| 319 | Import mode 'Downtime-minimized' is activated |
| 320 | Display detail informations |
| 321 | Continue the import |
| 322 | Creation of versions during import will be switched off |
| 323 | Determine which action is planned for this break point... |
| 324 | Stop the import procedure |
| 325 | The planned start time &1, &2 is greater than the max. start time &3, &4 |
| 326 | Ignore generation errors (&1, &2) |
| 327 | Ignore test import errors (&1, &2) |
| 328 | Import of the current OCS Queue in background (&1, &2) |
| 329 | The deletion of the OCS Queue was aborted by the user |
| 330 | Installation/Upgrade of the Add-on &1 rel.&2 (&3, &4) |
| 331 | Installation of the Preconfigured System &1 rel.&2 (&3, &4) |
| 332 | The Add-on &1 rel.&2 was successfully installed (&3, &4) |
| 333 | The Preconfigured System &1 rel.&2 was successfully installed (&3, &4) |
| 334 | Import phase '&1' (&2, &3) |
| 335 | Import phase '&1' was successfully finished (&2, &3) |
| 336 | Wrong scenario (&1) was changed to &2 -> start the import again |
| 337 | Import phase '&1' was already processed -> skip phase |
| 338 | Complete creation of version is switched off -> skip phase |
| 339 | &1 &2 &3 &4 |
| 340 | Error during executing the tp command 'tp &1 &2 &3 ...' |
| 341 | Error in the communication with tp |
| 342 | tp return code: '&1' , tp message: '&2' , tp output: |
| 343 | The tp buffer contains old, not completely processed OCS Packages |
| 344 | The tp parameter '&1' has a wrong value ('&2' instead of '&3') |
| 345 | tp version is too old (current: '&1', required: '&2') |
| 346 | R3trans is too old (current: '&1', required: '&2') |
| 347 | Error during disassembling the EPS parcel of OCS Package &1: '&2' |
| 348 | Details of the error situation can also be found in the import logs |
| 349 | The object list &1 is not available in the system |
| 350 | Objects are locked in open change requests |
| 351 | There are conflicts between OCS Packages and Add-ons |
| 352 | Packages in the queue don't exist in the tp buffer (e.g. &1) |
| 353 | The tp buffer contains more Packages than the queue (e.g. &1) |
| 354 | The tp buffer contains inconsistent entries (e.g. &1) |
| 355 | Wrong sequence of Packages in the tp buffer (e.g. &1) |
| 356 | The tp buffer contains no valid entries for the OCS Packages of the queue |
| 357 | Error for OCS Package &1: tp step: '&2' , tp return code: '&3' |
| 358 | Error for OCS Package &1: tp step: '&2' , not processed objects: &3 |
| 359 | Error during execution of report &1 |
| 360 | Modified objects has to be adjusted against the SAP standard |
| 361 | ABAP generation is switched off -> skip phase |
| 362 | The tp buffer still contains not completely processed OCS Packages |
| 363 | Error during reset of the FCS flag in table UVERS |
| 364 | Set the status of OCS Package &1 to '&2' |
| 365 | Consistent queue part for Add-on &1 rel.&2 was calculated |
| 366 | Conflicts may be able to be ignored -> see long text |
| 367 | The start time was adjusted to the current time (&1, &2) |
| 368 | Wrong or no given installation password for &1 |
| 369 | Unfulfilled prerequisite for &1: &2 - '&3' |
| 370 | There are unfulfilled import prerequisites for packages in the queue |
| 371 | There are open conversions in the Data Dictionary |
| 372 | System consistency: Component model with ID '&1' does not exist |
| 373 | You can ignore this error if no more follow |
| 374 | Checking the queue for upgrade-relevant OCS Package attributes... |
| 375 | Entering kernel / transport tool requirements in TOOLCHKEXE.LST |
| 376 | Queue contains no requirements for the kernel or transport tools |
| 377 | Checking and extending the control file SORTTABS.LST |
| 378 | Queue does not require control file SORTTABS.LST to be extended |
| 379 | Table &1 is already included in SORTTABS.LST -> No action required |
| 380 | Table &1 is not included in SORTTABS.LST -> Is added |
| 381 | Set the status of modification adjustment transport &1 to '&2' |
| 382 | Confirm Modification Adjustment Transport &1 |
| 383 | &1: &2 - Modification Adjustment Transport &3 |
| 384 | Reset Modification Adjustment Transport &1 |
| 385 | Support Package queue defined and saved... |
| 386 | Modification Adjustment Transports added to the Support Package queue |
| 387 | The Support Package queue was redefined... |
| 388 | The following CRTs of the Add-On &1 rel.&2 must be included as well: |
| 389 | CRT &4 for Support Package &1 of software component &2 rel.&3 |
| 390 | CRT &3 for OCS Package &1 of type &2 |
| 391 | The import will not be continued |
| 392 | Completion of modification adjustment (&3) (&1, &2) |
| 393 | Completion of modification adjustment (&1) confirmed |
| 394 | Disassemble modification adjustment transport &1 |
| 395 | Disassemble OCS package &1 |
| 396 | Use EPS package &1 with OCS file format '&2' |
| 397 | Create data file &1&2... |
| 398 | Create associated cofile... |
| 399 | -> Repeat disassembly, forced overwriting of the data file |
| 400 | No software component for Support Packages found |
| 401 | OCS locked by user &1 with transaction &2 |
| 402 | No valid queue for &1 &2 &3 |
| 403 | Add on installation/upgrade not yet complete. CRTs are required |
| 404 | No semaphore available -> Status is not set |
| 405 | Prerequisite of OCS Package &1 could not be met |
| 406 | Queue deleted |
| 407 | Queue could not be deleted |
| 408 | You first need an FCS Support Package for your system |
| 409 | There is no valid Support Package queue |
| 410 | There is no valid CRT queue for upgrading &1 &2 &3 |
| 411 | There is no valid CRT queue for the upgrade |
| 412 | Could not determine installed components (&1) |
| 413 | OCS packages are missing for a successful installation |
| 414 | Attributes for OCS Package &1 were loaded successfully |
| 415 | OCS package &1 already imported. Attributes cannot be loaded |
| 416 | Installation queue not defined |
| 417 | OCS packages are missing for a successful installation |
| 418 | Add on installation/upgrade not yet complete. CRTs are required |
| 419 | Only display functions available, since transaction &2 is locked by &1 |
| 420 | Support Package &1 successfully disassembled |
| 421 | No WWW browser available; download Note &1 manually from SAPNet |
| 422 | The system is not currently being upgraded; upgrade mode incorrect |
| 423 | Package &1: Import prerequisites are not fulfilled |
| 424 | Package &1 : &2 &3 &4 |
| 425 | Incorrect password ... |
| 426 | No currently imported SPAM/SAINT update found |
| 427 | Could not calculate a valid Support Package queue |
| 428 | OCS package &1 is corrupt. Contact the vendor |
| 429 | The queue (ID=&1) does not belong to the current change request (ID=&2) |
| 430 | The software component &1 rel.&2 is already on SP level &3 |
| 431 | Calculate the queue part for &1 rel.&2 with target SP &3 (level &4) |
| 432 | There is no Support Package for &1 rel.&2, SP level &3 available |
| 433 | Conflict resolution by including the CRT &3 for Add-On &1 rel.&2 |
| 434 | Consistent queue for Add-On &1 rel.&2 is already calculated |
| 435 | Display warning message about the dangerousness of using the "Force" mode |
| 436 | Transport request &1 should be imported before applying the OCS queue |
| 437 | Requests in the TMS import queue should be imported before the OCS queue |
| 438 | Support Package &1 is not a valid target SP for the queue calculation |
| 439 | Support Package &1 is obsolete and must not be imported |
| 440 | The test import of the queue finished with tp return code '&1' |
| 441 | Analyse the return codes of the individual packages... |
| 442 | The test import for &1 was not executed |
| 443 | The test import for &1 finished error free |
| 444 | The test import for &1 finished with the following errors: |
| 445 | The test import for &1 was aborted |
| 446 | Error while analysing the tp return code '&2' of the test import for &1 |
| 447 | The test import for &1 finished with errors which can be ignored: |
| 448 | The execution of the check steps finished successfully (&1, &2) |
| 449 | Execute check steps before scheduling the import job |
| 450 | The queue is currently being imported by a background job |
| 451 | The import of the queue is scheduled as a background job (Start: &1, &2) |
| 452 | The queue is currently being imported by user &1 |
| 453 | The queue is currently being processed by user &1 |
| 454 | The queue is defined. The import was not started yet. |
| 455 | The import of the queue was aborted because of a problem |
| 456 | The queue was imported successfully |
| 457 | The import of the queue was stopped intentionally |
| 458 | The import of the queue was aborted because of found conflicts |
| 459 | There are no current messages |
| 460 | There is no &1 queue yet. Start a queue calculation first... |
| 461 | Interrupt the import for execution of manual actions (&1, &2) |
| 462 | User &1 is locked |
| 463 | User &1 does not exist |
| 464 | Test-Installation/Test-Upgrade of Add-On &1 rel.&2 (&3, &4) |
| 465 | The 'Downtime-minimized' import mode has to be switched off |
| 466 | The note corrections have to be adjusted manually |
| 467 | An error occured while reimplementing the note corrections |
| 468 | The note &1 could not be reimplemented completely |
| 469 | The note &1 could not be reset completely |
| 470 | Modification adjustment already completed: &1 |
| 471 | Number of objects to be adjusted: &1 x DDIC (SPDD), &2 x Reposit. (SPAU) |
| 472 | Preview of objects to be adjusted: &1 x DDIC (SPDD), &2 x Reposit. (SPAU) |
| 473 | &1 repository objects were found which need to be adjusted |
| 474 | Execution of the automatic adjustment of note corrections... |
| 475 | Manual modification adjustment is neccessary |
| 476 | There are no note corrections which can be adjusted automatically |
| 477 | Note &1 will be reset |
| 478 | Note &1 will be reimplemented |
| 479 | Note &1 has to be adjusted manually |
| 480 | Inconsistency of the Support Package Tools (Table &1) |
| 481 | The import of the Support Package queue must be finished first |
| 482 | The import of the OCS Package queue must be finished first |
| 483 | The Add-On installation must be finished first |
| 484 | Add-Ons are installed which are incompatible with &1 (see long text) |
| 485 | The Industry Extension &1 rel.&2 is not installed and cannot be activated |
| 486 | Support Packages have to be imported before activating &1 |
| 487 | Add-Ons are installed which are incompatible with &1 (see following list) |
| 488 | &1 rel. &2 |
| 489 | &1 - Conflict Resolution Transport (CRT) for &2 |
| 490 | Use the Add-On installation package &1 (type &4) for Add-On &2 rel.&3 |
| 491 | Required software component &1 rel.&2 is not installed |
| 492 | Required Add-On component &1 rel.&2 is not installed |
| 493 | Not allowed software component &1 rel.&2 is installed |
| 494 | Required software component &1 is not installed with release &2 or higher |
| 495 | The Industry Extension &1 is not installed and cannot be activated |
| 496 | Open V3 update and data extraction requests were found |
| 497 | Open data extraction requests were found |
| 498 | Open V3 update requests were found |
| 499 | The warning about open V3 update and data extraction requests was ignored |
| 500 | Unknown Support Package: &1 |
| 501 | OCS file format error in: &1 |
| 502 | Call of &1 not permitted |
| 503 | Invalid condition: &1 &2 |
| 504 | OCS file for &1 cannot be opened: &2 |
| 505 | Queue is not initial |
| 506 | SPAM/SAINT version too low for Support Package: &1 |
| 507 | Could not generate SPAM/SAINT version |
| 508 | Unknown OCS file format '&1' &2; SPAM/SAINT Update required |
| 509 | You cannot reset the queue from import phase '&1' |
| 510 | Unknown software component '&1' |
| 511 | No description exists for '&1' Support Package level '&2' |
| 512 | Queue is already completely imported |
| 513 | Error when creating files for transport request &1 |
| 514 | Error when creating cofile for transport request &1 |
| 515 | Error when writing file &1&2 |
| 516 | Add-on &1 Release &2 must not be installed |
| 517 | Add-on &1 Release &2 must not be placed in the current queue |
| 518 | Add-on &1 Release &2 is not installed |
| 519 | Incompatible software component installed |
| 520 | Non-permitted release of add-on &1 installed |
| 521 | Add-on &1 is already installed |
| 522 | No add-on installation in the queue |
| 523 | Call Transaction &1 in English or German only |
| 524 | Call Transaction &1 in English or German only |
| 525 | The add-on installation queue was confirmed |
| 526 | Inconsistency in the OCS administration tables |
| 527 | Log on to the correct client |
| 528 | Inconsistency in Transaction SAINT; only display functions are available |
| 529 | Preconfigured System (PCS) is already installed in system |
| 530 | Only display functions are available in an SAP production system |
| 531 | Logon client & is protected from modifications and imports |
| 532 | Only display functions are available for user SAP* |
| 533 | A newer version of &1 (&2 version &3) is already installed |
| 534 | Import preconditions have changed -> queue is inconsistent |
| 535 | File positioning error in OCS file for &1: &2 |
| 536 | PCS &1 rel.&2 can only be installed in a client other than 000 |
| 537 | Add-on &1 rel.&2 can only be installed in client 000 |
| 538 | Incompatible Preconfigured Systems (PCS) already installed |
| 539 | Compatible Proconfigured Systems are already installed in client &2 |
| 540 | OCS package &1 requires at least Kernel Release &2 with patch number &3 |
| 541 | OCS Package &1 requires at least tp Version &2 |
| 542 | OCS Package &1 requires at least R3trans Version &2 |
| 543 | OCS package &1 does not match the current software component vector |
| 544 | Industry Extension &1 must be activated |
| 545 | Industry Extension &1 must not be activated |
| 546 | Prerequisite note corrections are not yet implemented |
| 547 | Activation of &1 requires upgrade to the following component versions |
| 548 | &1 rel.&2 - required by &3 |
| 549 | &1 rel.&2 - required by &3 (see Note &4) |
| 550 | Not all entries were expanded due to performance reasons |
| 551 | You must only enter values greater than &1 |
| 552 | It's not possible to reset the status; delete the queue completely |
| 553 | Inconsistency: Repeat the queue status reset |
| 554 | Inconsistency: Delete the queue completely and define it again |
| 555 | Specify the transport request to be searched for |
| 556 | The tp buffer &1 does not contain any modification adjustment transports |
| 557 | The SAP system has to be stopped and restarted on all application servers |
| 558 | Use the Software Update Manager (SUM) to import the queue |
| 559 | This Enhancement Package installation must be configured with a Stack XML |
| 560 | Creation of sub components for the software component &1, &2 |
| 561 | The software component &1 rel.&2 does not have the required SP level &3 |
| 562 | Not allowed software component &1 rel.&2, SP level &3 |
| 563 | Support Pack. Patch &1 is obsolete and must not be imported |
| 564 | The equivalent SP patch &4 for component &1 is missing. |
| 565 | Delete obsolete sub components of software component &1, &2 |
| 566 | The ID of the current change request was not transfered |
| 567 | Function module &1 finished with return code &2 |
| 568 | Insert/Update of Support Package &1 into PAT03_PRE aborted |
| 569 | Internal error in method &1: &2 &3 &4 |
| 570 | The loaded stack configuration does not fit to the current system state |
| 571 | There are no stack configurations available in the Maintenance Optimizer |
| 572 | The transport request &1 was marked as modification adjustment transport |
| 573 | The loaded stack configuration is not valid for system &1 |
| 574 | The stack configuration is not valid for the system &1, inst.-no. &2 |
| 575 | The stack configuration does not contain a product stack |
| 576 | The stack configuration does not contain a software feature stack |
| 577 | The stack configuration doesn't contain data for ABAP software components |
| 578 | Error in method "&1": field "&2" does not exist in structure &3 |
| 579 | Error in method "&1": invalid value "&2" for field "&3-&4" |
| 580 | Check the completeness of the target software component vector |
| 581 | Software component &1 rel.&2 is required (see note &3) |
| 582 | Software component &1 rel.&2 is required |
| 583 | Revise the selected product instances in the Maintenance Optimizer |
| 584 | Revise the selections and decisions in the phase IS_SELECT |
| 585 | Select these components for an upgrade (in phase IS_SELECT) |
| 586 | Required software component versions are missing in target comp. vector |
| 587 | The target software component vector is complete |
| 588 | Check whether the OCS Package &1 is compatible to the softw. comp. vector |
| 589 | Check whether the Add-On &1, &2 is compatible to the softw. comp. vector |
| 590 | Start of the optimization of the import queue |
| 591 | The optimization of the import queue finished successfully |
| 592 | The import queue is empty |
| 593 | &1 of &2 objects do not need to be imported (&3 %) |
| 594 | Inconsistent program state: &1 |
| 595 | The optimization of the import queue needs &1 MB memory |
| 596 | No Support Package with SP level &3 available for component &1 rel.&2 |
| 597 | Required Support Packages for component &1 are missing in the queue |
| 598 | Required Support Packages for component &1 are missing in the queue |
| 599 | &1 is not sufficient, higher Support Packages are necessary |
| 600 | Preconfigured System &1 Release &2 is already installed |
| 601 | Object list &1 for PCS &2 Release &3 does not exist |
| 602 | PCS &1 Release &2 was not initialized; No status update |
| 603 | PCS installation queue was confirmed |
| 604 | The mandatory SP Patch &4 for component &1 is missing in the queue |
| 605 | The value of the extended attribute &1 is wrongly formatted |
| 606 | The mandatory SP &4 for component &1 rel. &2 is missing in the queue |
| 607 | The import of Prepackages is not allowed in this system |
| 608 | The loaded stack configuration does not contain Add-On Install./Upgrades |
| 609 | The installation of &1 rel. &2 must be configured with a Stack XML |
| 610 | Start reading the compressed stack XML with ID &1 (&2) |
| 611 | Start reading the uncompressed stack XML with ID &1 (&2) |
| 612 | Start reading the stack XML file from the application server (&1) |
| 613 | Stack XML with ID &1 was successfully read |
| 614 | Stack XML file was successfully read from the application server |
| 615 | Start uncompressing the stack XML |
| 616 | Uncompressing the stack XML was successfully completed |
| 617 | Start evaluating the stack XML (&1) |
| 618 | Evaluating the stack XML was successfully completed |
| 619 | RFC destination to Solution Manager is not configured (application &1) |
| 620 | XML file '&1&2&3&4' does not exist or could not be opened |
| 621 | XML file '&1&2&3&4' is empty or could not be opened |
| 622 | XML stack of type "&1" was created by a planning tool with SP level &2 |
| 623 | Start the XSLT transformation '&2' (&1) |
| 624 | XSLT transformation was successfully completed |
| 625 | Read stack &1 "&2", product version &3 "&4" |
| 626 | Product version &1 "&2" "&3" was inserted into table &4 |
| 627 | Read SP feature stack "&1&2&3&4" |
| 628 | Validity check of the SP-Feature-Stack target system &1, inst.no.&2 (&3): |
| 629 | Target system ID &1 does not match the actual system ID &2 |
| 630 | Target system inst. number &1 does not match the actual inst. number &2 |
| 631 | &1 &2 of the target system matches the &1 of the actual system |
| 632 | SW feature &1 &2 was assigned to technical usage &3 |
| 633 | Read software components of SP feature stack "&1" |
| 634 | SP level &1 was determined for &2 &3 |
| 635 | Software component version &1 &2 was inserted into table &3 |
| 636 | Replaced product version &1 "&2" "&3" was inserted into table &4 |
| 637 | Software component version &1 &2 (SP level &3) was inserted in table &4 |
| 638 | Level &3 for softw. component version &1 &2 was inserted into table &4 |
| 639 | Version &2 level &3 for softw. component &1 was inserted into table &4 |
| 640 | Replaced SF feature &1 "&2" "&3" was inserted into table &4 |
| 641 | Included SW feature &1 "&2" "&3" was inserted into table &4 |
| 642 | Read information for the target system &1 (&2) |
| 643 | Read start component vector of target system &1 (&2) |
| 644 | Read initial component vector of export DVD &1 &2 (&3) |
| 645 | Read replaced products of stack &1 "&2" |
| 646 | Read SP feature stacks of stack &1 "&2" |
| 647 | Read technical usages of SW feature stack &1 |
| 648 | Stack ID &1 "&2" was inserted into table &3 |
| 649 | SW feature &1 "&2" "&3" was inserted into table &4 |
| 650 | Read replaced SW features for SW feature "&1" |
| 651 | Read included SW features for SW feature "&1" |
| 652 | The list of technical usages was transfered to table &1 |
| 653 | The target system is defined as non-ABAP system |
| 654 | The SP-Feature-Stack is not valid for the actual system |
| 655 | Check the target system &1, inst.no. &2 of the software component &3 &4 |
| 656 | The software component is not valid for the actual system |
| 657 | The list of product versions was transfered from table &1 to &2 |
| 658 | The system information is not valid for the current system |
| 659 | Read product versions for the target system &1 (&2) |
| 660 | Errors ocurred while checking the Transport Management System (STMS) |
| 661 | The non-ABAP deployment is not configured in TMS |
| 662 | The non-ABAP deplyoment web service is not configured in TMS |
| 663 | There is no deploy tool for non-ABAP deployment configured |
| 664 | The configuration of the non-ABAP deployment is incorrect |
| 665 | The Basis SP level is too low. A non-ABAP deployment is not possible yet. |
| 666 | Read software features for the target system &1 (&2) |
| 667 | Read software component vector for the target system &1 (&2) |
| 668 | The system info XML is not valid for the system &1, installation no. &2 |
| 669 | The system info XML does not contain any valid system information |
| 670 | The settings were adjusted for Version-DB systems (see long text) |
| 671 | The creation of versions cannot be switched off in Version-DB systems! |
| 672 | The system info XML contains the not installed software component &1 &2 |
| 673 | The installed softw. comp. &1 &2 is not contained in the system info XML |
| 674 | Deletion of incorrect product information: |
| 675 | There was no incorrect product information to be deleted |
| 676 | Registration of correct product information: |
| 677 | Product version: &1 - "&2" (SP stack "&3") |
| 678 | Product instance: &1 &2 - "&3" |
| 679 | Included product instance: &1 &2 - "&3" |
| 680 | Lifecycle Management processes are locked by process &1 (LM tool &2) |
| 681 | Is assigned to technical usage &1 |
| 682 | Software component &1 Release &2 is not installed |
| 683 | The SP level &3, defined for component &1 rel.&2, could not be reached |
| 684 | The imported file does not contain a valid XML |
| 685 | Precondition type "&1" is unknown. A SPAM/SAINT Update is required... |
| 686 | Package &1 has to be applied using the Software Update Manager (SUM) |
| 687 | The system is currently updated using the Software Update Manager (SUM) |
| 688 | Component &1 is already retrofitted into component version &2 rel.&3 |
| 689 | R3trans data file &1&2 does not exist |
| 690 | R3trans data file &1 is older than R3trans data file in EPS parcel &2 |
| 691 | R3trans data file in EPS parcel &1 is older than R3trans data file &2 |
| 692 | EPS parcel of &1 is too old. Upload new EPS parcel before implementation |
| 693 | Use the Software Update Manager (SUM) to import the queue |
| 694 | Process component deletion requests of OCS Package &1 |
| 695 | Component &1 is not installed -> deletion is not necessary |
| 696 | The queue cannot be deleted or resetted |
| 697 | Component &1 successfully deleted |
| 698 | The transport based corr. (TCI) &1 is obsolete and must not be imported |
| 699 | The transport based correction instruction (TCI) &1 was set to "Obsolete" |
| 700 | File selection terminated |
| 701 | Error when reading file '&1&2' |
| 702 | File '&1' is not a SAPCAR archive |
| 703 | The transport based correction instruct. (TCI) &1 was added to the queue |
| 704 | The transport based correction (TCI) &1 is missing in the current queue |
| 705 | Unknown error when writing file '&1' |
| 706 | Software installed for decompression is obsolete |
| 707 | Could not find file '&1' |
| 708 | Error when accessing the decompression software |
| 709 | Error when executing decompression software |
| 710 | Unknown error when accessing decompression software |
| 711 | Decompression of the file terminated |
| 712 | File '&1' successfully transferred and decompressed |
| 713 | File '&1' successfully transferred, decompressed, and then deleted |
| 714 | Installed software cannot process the archive |
| 715 | There is no decompression software installed on the application server |
| 716 | &3 error: &1 &2 |
| 717 | Could not interpret profile parameter &1 |
| 718 | A final parenthesis is missing in &1 |
| 719 | No authorization to delete '&1' on the application server |
| 720 | An error occurred while deleting file '&1&2' on the application server |
| 721 | No authorization to write '&1' on the application server |
| 722 | An error occurred while saving file '&1' on the application server: &2&3 |
| 723 | No authorization to read '&1' on the application server |
| 724 | An error occurred while accessing the file selection |
| 725 | Could not determine detailed information for '&1' |
| 726 | An error occurred while transferring file '&1' from the frontend computer |
| 727 | Calculated file length does not match transferred data |
| 728 | No response while accessing SAPCAR (possible program termination) |
| 729 | File '&1' was transferred and decompressed successfully but not deleted |
| 730 | File is too large. Transfer was cancelled |
| 731 | No authorization for transfer file '&1' from frontend PC |
| 732 | SAPCAR does not support displaying the content of CAR archives |
| 733 | Unable to read the table of contents of SAPCAR archive &1 |
| 734 | Cannot disassemble to DIR_EPS_ROOT/in (see long text) |
| 735 | SAPCAR error: "&1" - The archive file seems to be corrupt |
| 736 | Import preconditions of OCS Package &1 are not fullfilled |
| 737 | The modification adjustment is executed externally -> check is skipped |
| 738 | The queue contains the component version description &1; contact SAP |
| 739 | &1: &2 - Component Version Description for &3 rel. &4 |
| 740 | The RFC connection to the Solution Manager is not configured correctly |
| 741 | The RFC connection "&1" to the Solution Manager does not work |
| 742 | The component vector of the system &1 is not maintained in Sol. Manager |
| 743 | The component vector of the system &1 is not up to date in Sol. Manager |
| 744 | The Maintenance Optimizer in Sol. Manager is not configured correctly |
| 745 | The software component &1 rel.&2 is not registered in LMDB |
| 746 | The software component &1 rel.&2 is registered in LMDB with version &3 |
| 747 | The software component &1 rel.&2, registered in LMDB, is not installed |
| 748 | Add-On &1 rel. &2: Set FULLTASK to "&3", DELTATASK to "&4" |
| 749 | Add-On &1: FULLTASK "&4" was copied from version &2 to version &3 |
| 750 | Start options of subsequent modules were changed. Check them... |
| 751 | The start time is smaller than the current time. |
| 752 | The max. start time is smaller than the given start time. |
| 753 | The start options of the import modules are consistent. |
| 754 | Check and define the start options for the import modules. |
| 755 | Severe error while displaying uploaded packages |
| 756 | Not all parameters are changeable, because an OCS queue is being imported |
| 757 | Read to be uninstalled product versions |
| 758 | Product version &1 "&2" "&3" (to be uninstalled) inserted in table &4 |
| 759 | SW feature &1 "&2" "&3" (to be uninstalled) was inserted in table &4 |
| 760 | There are inactive objects in the system |
| 761 | There are inactive runtime objects in the ABAP Dictionary |
| 762 | Read software features to be uninstalled |
| 763 | The queue does not contain uninstallation packages. No action necessary. |
| 764 | The packages were reset successfully |
| 765 | Error occured while ignoring errors of import step &1 for request &2 |
| 766 | Ignored errors in import step &1 for request &2 |
| 767 | The queue does not contain CRM relevant packages -> no action necessary |
| 768 | Installed SAPCAR version does not support verification of signed archives |
| 769 | The path &1&2&3&4 contains not allowed characters |
| 770 | A status reset is not possible when using the parallel import mode |
| 771 | The path &1&2&3&4 is outside the allowed directory tree |
| 772 | The signature verification for &1 finished with warnings: &2&3&4 |
| 773 | The signature verification for &1 finished with errors: &2&3&4 |
| 774 | The archive &1 was successfully unpacked |
| 775 | OCS package &1: Import precondition &2 is not fulfilled |
| 776 | Data block does not have type &1 |
| 777 | Attribute Change Packages (ACP) cannot be disassembled |
| 778 | Backup option for Transport based Corr. Instruct. (TCI) is switched off |
| 779 | Found the following log message for import step &2 of package &1: |
| 780 | The log file path points to a file outside of the allowed "log" directory |
| 781 | Create allow file &1&2... |
| 782 | -> R3trans data file will be created |
| 783 | End of file of '&1&2' reached |
| 784 | The action log for queue "&1" does not exist |
| 785 | The archive &1 was already unpacked |
| 786 | Directory &1 could not be scanned |
| 787 | There is no signed manifest existing for OCS Package &1 (EPS file: &2) |
| 788 | The OCS Package &1 is not digitally signed (EPS file: &2) |
| 789 | Verify the digital signature of OCS Package &1 |
| 790 | The in attribute &1 named class &2 does not exist |
| 791 | The class &1 does not contain method &2 |
| 792 | Could not find any SAR archives for upload |
| 793 | Import mode 'Concurrent Version Online Import' is activated |
| 794 | Read SP stack information for the target system &1 (&2) |
| 795 | Ignore the warnings in phase '&1' and continue the import |
| 796 | The verification of the digital signature was successful |
| 797 | The verification of the digital signature is switched off |
| 798 | Signature verification not possible, SAP note 2520826 is not implemented |
| 799 | The archive &1 is not digitally signed |
| 800 | Use the special Support Package Manager for &1 (see menu Environment) |
| 801 | Use the special Add-On Manager for &1 (see menu Environment) |
| 802 | Continue by using the special Support Package Manager for &1 |
| 803 | Continue by using the special Add-On Manager for &1 |
| 804 | The system is running in tenant mode, only display functions are avail. |
| 805 | No valid maintenance certificate found (see long text) |
| 806 | A valid maintenance certificate was found for system &1 |
| 807 | The language vector used for the export contains invalid languages: &1 |
| 808 | No queue calculation because of a missing maintenance certificate |
| 809 | The maintenance certificate check requires a kernel patch level >= 145 |
| 810 | Incomplete SAP ERP 6.0 EHP4 SR1 Upgrade - please, read note 1370344! |
| 811 | Queue of test case &1 was successfully calculated |
| 812 | Queue has software components with incompatible database requirements |
| 813 | Database requirement &1 is not fullfilled |
| 814 | Incompatible database type requirement: &1 -> &2 vs. &3 -> &4 |
| 815 | The installation prerequisites of &1 are not fulfilled -> see note &2 |
| 816 | System is not running in "B4H" mode, BW/4HANA conversion is not possible |
| 817 | CRM Support Package and Add-On Manager are not necessary anymore |
| 818 | Internal error: No semaphore/PAT10 entry |
| 819 | SPAM/SAINT version is too low, at least version &1 is required |
| 820 | Support Package equivalency violation accepted by user &1 (&2 ,&3) |
| 821 | The queue with transport based correction instructions (TCI) was defined |
| 822 | All transport based correction instructions (TCI) are already imported |
| 823 | The list of transport based corrections (TCI) to be installed is empty |
| 824 | There is no transport request given |
| 825 | The transport request &1 is not changeable |
| 826 | &1 is not a transport based correction instruction (TCI) |
| 827 | The transport based correction (TCI) &1 does not contain the attribute &2 |
| 828 | The transport based correction (TCI) should not contain the attribute &1 |
| 829 | Objects of the transp. based correct. (TCI) were included on request &1 |
| 830 | The transport request &1 cannot be read |
| 831 | The transp. based corr. (TCI) &1 does'nt contain a CP_NOTE_CORR Attribute |
| 832 | A different queue is already defined |
| 833 | The transport based correction instruction (TCI) &1 is already imported |
| 834 | The development package for the transport of the TCI meta data is missing |
| 835 | The transport based correction (TCI) &1 of SAP note &2 is not available |
| 836 | Note Assistant functions are out-of-date; FM &1 does not exist |
| 837 | The queue was defined but there is no import authorization |
| 838 | The transport based corr. instructions require a modification adjustment |
| 839 | Error during the import of transport based correction instructions |
| 840 | There is no runtime analysis available for the OCS queue with ID &1 |
| 841 | The runtime analysis form could not be created |
| 842 | The runtime analysis form could not be displayed |
| 843 | Request &1 does not contain any languages |
| 844 | Correction Package &1 for component &2 rel. &3 is not available |
| 845 | No authorization to modify the SAP kernel checks |
| 846 | System is not configured as installation test system |
| 847 | System is not configured as standalone installation test system |
| 848 | Errors occured while adjusting transport based correct. instruct. (TCI) |
| 849 | Error when calling method &1: reason: &2, message: &3&4 |
| 850 | Import phase '&1' (&2, &3) started in background |
| 851 | Phase &1 was set to finished |
| 852 | Display detail information for manual actions in phase '&1' |
| 853 | Set phase &1 to finished and continue the import |
| 854 | Transport based Correction Instruction (TCI) &1 is not imported yet |
| 855 | E070-TARSYSTEM could not be set to SAP |
| 856 | E070-CLIENT could not be set to '000' |
| 857 | &1 is not known as backup transport |
| 858 | Invalid parameter (&1) |
| 859 | There is no consistent backup for this queue available |
| 860 | No data available for backup transport &1 |
| 861 | Could not determine path to data file of transport &1 |
| 862 | Backup is already restored |
| 863 | Package &1 was not applied yet; restore is not possible |
| 864 | Package &1 was not applied yet; restore failed |
| 865 | Restore queue successfully defined (&1) |
| 866 | Backup for package &1 is obsolete, because of &2 |
| 867 | Backup creation is not active |
| 868 | It's not possible to create a backup for package &1 |
| 869 | There is no valid backup for package &1 |
| 870 | A backup for package &1 exists, but cannot be restored |
| 871 | Backup for package &1 is blocked by package &2 |
| 872 | Transport based Correction Instruction &1 is not available |
| 873 | TCI &1 cannot be imported, it may be obsolete |
| 874 | The authorization to execute the SAPCAR command is missing |
| 875 | DDIC objects can now be edited |
| 876 | A queue is currently being imported in transaction SPAM or SAINT |
| 877 | Unknown OCS package : &1 |
| 878 | The BW/4HANA conversion requires the import of SAP note &2, version &3 |
| 879 | OCS Package &1 was added to the queue |
| 880 | Import procedure "&1" must not be used for system type "&2" |
| 881 | Import procedure "&1" is not valid |
| 882 | System does not run in a multi tenancy setup -> no action necessary |
| 883 | OCS Package &1 was not yet imported into the shared container |
| 884 | Version number "&1" for tables in the shared container is not valid |
| 885 | Table version "&1" does not fit to status "&2" in MTSHCONTAINER |
| 886 | The active shared container name is missing in table MTSHCONTAINER |
| 887 | The shared container name &1 does not fit to status "&2" in MTSHCONTAINER |
| 888 | The shared schema name &1 does not fit to status "&2" in MTSHCONTAINER |
| 889 | The new shared container name is missing |
| 890 | The new shared schema name is missing |
| 891 | tp parameter MT_MODE = &1 does not match the system type "&2" |
| 892 | A check of the HDI container configuration is necessary |
| 893 | A check of the HDI container configuration is not necessary |
| 894 | HDI containers are configured |
| 895 | HDI container are not configured yet |
| 896 | Read the required SPAM/SAINT Version &1 |
| 897 | The TCI queue must be finished with the Note Assistant |
| 898 | Automatic repeat of import step "&1" |
| 899 | SL Tool &1 &2, SP Level &3 inserted into Table &4 |