SAP ABAP Message Class TN (Support Package Manager (SPAM) Messages)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-UPG-OCS (Application Component) Online Correction Support (Support Package and Add-On Tools)
⤷
SPAM (Package) OCS - Installation/Implementation Tools
⤷
⤷
Attributes
| Message class | TN | |
| Short Description | Support Package Manager (SPAM) Messages | |
| Changed On | 20141031 | |
| Last Changed At | 215928 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | Failed to connect to server for SAPNet - R/3 Frontend | Space: object requires documentation | ||
| 2 | Support Package &1 could not be inserted in the &2 buffer | Space: object requires documentation | ||
| 3 | Could not schedule RDDIMPDP as a background job | Space: object requires documentation | ||
| 4 | Could not create versions of objects in Support Package &1 | Space: object requires documentation | ||
| 5 | Invalid WHEN parameter in function module | Space: object requires documentation | ||
| 6 | Requirements for import have not been met | Space: object requires documentation | ||
| 7 | Test import of Support Package &1 terminated | Space: object requires documentation | ||
| 8 | Could not import command file for Support Package &1 | Space: object requires documentation | ||
| 9 | DDIC import of Support Package &1 terminated | Space: object requires documentation | ||
| 10 | Function SUMO_ADD_PATCH: Support Package &1 could not be inserted | Space: object requires documentation | ||
| 11 | Internal error: &1 &2 &3 &4 | Space: object requires documentation | ||
| 12 | Function &1: No entry exists / RSUMODSP has not run for &2 | Space: object requires documentation | ||
| 13 | Main import of Support Package &1 canceled | Space: object requires documentation | ||
| 14 | Failed to insert/update Support Package &1 in PAT03 | Space: object requires documentation | ||
| 15 | Failed to insert/update Support Package &1, phase &2 in PAT01 | Space: object requires documentation | ||
| 16 | OCS package &1 does not exist in the system | Space: object requires documentation | ||
| 17 | &1: Data file and/or cofile not in SAP transport directory | Space: object requires documentation | ||
| 18 | Import parameters of function module &1 are inconsistent | Space: object requires documentation | ||
| 19 | Could not restart import of Support Package &1 | Space: object requires documentation | ||
| 20 | &1 run canceled by user &2 | Space: object requires documentation | ||
| 21 | Update for parcel &1 in table TEPSIN failed | Space: object requires documentation | ||
| 22 | &1 Support Packages successfully downloaded from SAPNet - R/3 Frontend | Space: object requires documentation | ||
| 23 | Support Package &1 is not in table PAT03 | Space: object requires documentation | ||
| 24 | Support Package &1 was already imported into Release &2 | Space: object requires documentation | ||
| 25 | Support Package &1 was recalled | Space: object requires documentation | ||
| 26 | Backup &1 for Support Package &2 not found | Space: object requires documentation | ||
| 27 | Import of Support Package &1 was rejected by user &2 | Space: object requires documentation | ||
| 28 | Could not determine EPS parcel for Support Package &1 | Space: object requires documentation | ||
| 29 | Could not determine cofile name for Support Package &1 | Space: object requires documentation | ||
| 30 | Could not determine data file name for Support Package &1 | Space: object requires documentation | ||
| 31 | Disassembling of cofile of Support Package &1 canceled | Space: object requires documentation | ||
| 32 | Disassembling of R3trans data file of Support Package &1 canceled | Space: object requires documentation | ||
| 33 | Disassembling of SDO data file of Support Package &1 canceled | Space: object requires documentation | ||
| 34 | Disassembling of Support Package &1 canceled | Space: object requires documentation | ||
| 35 | Download from SAPNet - R/3 Frontend failed | Space: object requires documentation | ||
| 36 | Download from SAPNet - R/3 Frontend rejected by user &1 | Space: object requires documentation | ||
| 37 | Could not insert Support Package &1 in PAT03 | Space: object requires documentation | ||
| 38 | Support Package &1 may not be imported into Release &2 | Space: object requires documentation | ||
| 39 | Support Package &1 cannot be imported into a &2 operating system | Space: object requires documentation | ||
| 40 | Support Package &1 may not be imported into a &2 database | Space: object requires documentation | ||
| 41 | Support Package &1 is already contained in Release &2 | Space: object requires documentation | ||
| 42 | Support Package &1 does not have a valid SAP Release | Space: object requires documentation | ||
| 43 | You did not request Support Packages from SAPNet - R/3 Frontend | Space: object requires documentation | ||
| 44 | No Support Packages found for this selection | Space: object requires documentation | ||
| 45 | Only display functions are available | Space: object requires documentation | ||
| 46 | Complete import of OCS package &1 not yet confirmed | Space: object requires documentation | ||
| 47 | OCS package &1 not yet imported completely | Space: object requires documentation | ||
| 48 | OCS package &1 confirmed | Space: object requires documentation | ||
| 49 | Import Support Package &1 after Support Package &2 | Space: object requires documentation | ||
| 50 | OCS package &1 not imported yet | Space: object requires documentation | ||
| 51 | OCS package &1 already confirmed | Space: object requires documentation | ||
| 52 | You have no authorization for the OCS transactions | Space: object requires documentation | ||
| 53 | Backup request &1 for Support Package &2 could not be created | Space: object requires documentation | ||
| 54 | File &1 could not be deleted | Space: object requires documentation | ||
| 55 | Support Package cannot be imported during kernel switch or downtime | Space: object requires documentation | ||
| 56 | Backup &1 for Support Package &2 could not be deleted | Space: object requires documentation | ||
| 57 | Import is not possible due to locked objects | |||
| 58 | No add-on found | |||
| 59 | RFC system error &1 &2 &3 &4 | |||
| 60 | RFC communication error &1 &2 &3 &4 | |||
| 61 | Specify the target system | Space: object requires documentation | ||
| 62 | Selection criteria are not met | |||
| 63 | User SAP* may not import Support Packages | Space: object requires documentation | ||
| 64 | Cannot print | Space: object requires documentation | ||
| 65 | No Support Packages were downloaded | Space: object requires documentation | ||
| 66 | Deletion of backup file &1 failed | |||
| 67 | Cofile &1 for Support Package &2 could not be created | Space: object requires documentation | ||
| 68 | No adjustment of modifications required | |||
| 69 | & already has status 'New' | Space: object requires documentation | ||
| 70 | Status of & was reset | Space: object requires documentation | ||
| 71 | Do not reset status of & | Space: object requires documentation | ||
| 72 | Cofile &1 could not be opened | |||
| 73 | File LAST.HOT created | Space: object requires documentation | ||
| 74 | Do not insert Support Package &1 (type &2) in the file LAST.HOT | Space: object requires documentation | ||
| 75 | Program may only run in background | Space: object requires documentation | ||
| 76 | File &1 could not be opened. &2&3&4 | Space: object requires documentation | ||
| 77 | No Support Packages were reset | Space: object requires documentation | ||
| 78 | Support Package Manager (transaction SPAM) date &1, time &2 | Space: object requires documentation | ||
| 79 | Conflicts found between Support Packages (&3) and &1/&2 | Space: object requires documentation | ||
| 80 | &1 Support Package level accepted | Space: object requires documentation | ||
| 81 | ************************************************************************* | |||
| 82 | Invalid Release | |||
| 83 | No add-ons installed in system (table AVERS empty) | |||
| 84 | Support Packages imported into system &1: | Space: object requires documentation | ||
| 85 | Add-on &1/&2 contains Support Packages: &3-&4 | Space: object requires documentation | ||
| 86 | &1 &2 &3 &4 | |||
| 87 | Determine conflicts between Support Packages and add-on &1/&2 | Space: object requires documentation | ||
| 88 | No Support Packages were imported in system &1 | Space: object requires documentation | ||
| 89 | Add-on &1/&2 does not contain any Support Packages | Space: object requires documentation | ||
| 90 | No conflicts found | |||
| 91 | Your action: None | |||
| 92 | Import Support Packages &1-&2 using Support Package Manager | Space: object requires documentation | ||
| 93 | Import the relevant CRTs using Support Package Manager | Space: object requires documentation | ||
| 94 | Unable to determine path for file &1 | |||
| 95 | &1 is not the Support Package that was last imported | Space: object requires documentation | ||
| 96 | Import &1 again using Support Package Manager | Space: object requires documentation | ||
| 97 | Generation does not have errors; RSSPAM03 is not executed | Space: object requires documentation | ||
| 98 | Support Package &1 has incorrect status (&2) | Space: object requires documentation | ||
| 99 | You have not yet imported Support Packages &1-&2 | Space: object requires documentation | ||
| 100 | If there are conflicts, apply the corresponding CRTs with SPAM | Space: object requires documentation | ||
| 101 | Error writing log &1 | |||
| 102 | Table &1 is empty | |||
| 103 | This function has not been released yet | |||
| 104 | Relevant Support Package add-on ID (PAOID) does not exist | Space: object requires documentation | ||
| 105 | Import Support Package &1 first | Space: object requires documentation | ||
| 106 | Maintenance level &1 contains Support Package &2 | Space: object requires documentation | ||
| 107 | Update of table PAT05 canceled | |||
| 108 | Cursor is not positioned on a valid field | Space: object requires documentation | ||
| 109 | Scenario & is invalid | Space: object requires documentation | ||
| 110 | Phase & is invalid | Space: object requires documentation | ||
| 111 | Selection was completed | Space: object requires documentation | ||
| 112 | Nothing was selected | |||
| 113 | OCS package queue is empty | Space: object requires documentation | ||
| 114 | Queue is consistent | Space: object requires documentation | ||
| 115 | You have not selected anything | |||
| 116 | Settings were updated | |||
| 117 | Download &1 first | Space: object requires documentation | ||
| 118 | Support Package queue was confirmed | Space: object requires documentation | ||
| 119 | Internal error: Could not specify queue | Space: object requires documentation | ||
| 120 | Check queue first | Space: object requires documentation | ||
| 121 | Predecessor &1 of &2 does not exist | Space: object requires documentation | ||
| 122 | Status of queue reset | Space: object requires documentation | ||
| 123 | No SPAM/SAINT update found | Space: object requires documentation | ||
| 124 | SPAM/SAINT update &1 has already been imported successfully | Space: object requires documentation | ||
| 125 | Download performed | |||
| 126 | Support Package &1 imported successfully according to scenario '&2' | Space: object requires documentation | ||
| 127 | &1 &2 not yet imported | Space: object requires documentation | ||
| 128 | Internal error: Phase & could not be initialized | Space: object requires documentation | ||
| 129 | Phase & canceled | Space: object requires documentation | ||
| 130 | Only choose scenario 'S' or 'T' | Space: object requires documentation | ||
| 131 | Support Package &1 could not be removed from &2 buffer | Space: object requires documentation | ||
| 132 | Queue &1 imported successfully according to &2 scenario: Confirm this | Space: object requires documentation | ||
| 133 | Queue &1 - &2 imported successfully according to &3 scen.: Confirm this | Space: object requires documentation | ||
| 134 | Queue already confirmed | Space: object requires documentation | ||
| 135 | Queue set up | Space: object requires documentation | ||
| 136 | SPAM/SAINT update cannot be imported | Space: object requires documentation | ||
| 137 | First import SPAM/SAINT update &1 completely | Space: object requires documentation | ||
| 138 | &1 does not exist | Space: object requires documentation | ||
| 139 | Queue is not empty | Space: object requires documentation | ||
| 140 | EPS parcel & & is not in TEPSIN | Space: object requires documentation | ||
| 141 | Table updates can now be started using transaction ICNV | Space: object requires documentation | ||
| 142 | Queue is no longer in buffer &1 | Space: object requires documentation | ||
| 143 | Error calling RFC tp interface | Space: object requires documentation | ||
| 144 | Generation errors were ignored | Space: object requires documentation | ||
| 145 | No generation errors found | Space: object requires documentation | ||
| 146 | Scenario in queue was changed from '&1' to '&2' | Space: object requires documentation | ||
| 147 | &1 imported successfully according to &2 scenario: Confirm this | Space: object requires documentation | ||
| 148 | Queue &1 imported successfully according to &2 scenario | Space: object requires documentation | ||
| 149 | Queue &1 - &2 imported successfully according to &3 scenario | Space: object requires documentation | ||
| 150 | &1 &2 imported successfully | Space: object requires documentation | ||
| 151 | There are no Support Packages of the type &1 in the system | Space: object requires documentation | ||
| 152 | Program tp did not execute successfully | Space: object requires documentation | ||
| 153 | Queue is inconsistent | Space: object requires documentation | ||
| 154 | Caution: Upgrade or PREPARE is still running; import not permitted | Space: object requires documentation | ||
| 155 | Error during RFC call | Space: object requires documentation | ||
| 156 | File & does not exist | Space: object requires documentation | ||
| 157 | Main export ended with return code & | Space: object requires documentation | ||
| 158 | ADO export ended with return code & | Space: object requires documentation | ||
| 159 | Error during RFC call | Space: object requires documentation | ||
| 160 | Status of the SPAM/SAINT update has been reset | Space: object requires documentation | ||
| 161 | For Support Package type &1, an entry is missing in file &2 | Space: object requires documentation | ||
| 162 | Software component &1 with Release &2 does not exist | Space: object requires documentation | ||
| 163 | Support Package type is &1, but software component &2 does not exist | Space: object requires documentation | ||
| 164 | SPAM/SAINT update has already been confirmed | Space: object requires documentation | ||
| 165 | You may only perform this function according to scenario '&' | Space: object requires documentation | ||
| 166 | &1 &2 integrated in the upgrade | Space: object requires documentation | ||
| 167 | &1 &2 was imported without using Support Package Manager | Space: object requires documentation | ||
| 168 | Target release is unknown: Run PREPARE | Space: object requires documentation | ||
| 169 | No Support Packages were found for Release & | Space: object requires documentation | ||
| 170 | Support Package & already included in the upgrade | Space: object requires documentation | ||
| 171 | Including Support Package & in the upgrade | Space: object requires documentation | ||
| 172 | Step &1: Determine EPS parcel path | Space: object requires documentation | ||
| 173 | Step &1: Determine source path of R3trans data file | Space: object requires documentation | ||
| 174 | Step &1: Determine target path of R3trans data file | Space: object requires documentation | ||
| 175 | Step &1: Determine source path of ADO data file | Space: object requires documentation | ||
| 176 | Step &1: Determine target path of ADO data file | Space: object requires documentation | ||
| 177 | Step &1: Determine source path of cofile | Space: object requires documentation | ||
| 178 | Step &1: Determine target path of cofile | Space: object requires documentation | ||
| 179 | Step &1: Skip attribute record in EPS parcel | Space: object requires documentation | ||
| 180 | Step &1: Disassemble R3trans data file | Space: object requires documentation | ||
| 181 | Step &1: Disassemble ADO data file | Space: object requires documentation | ||
| 182 | Step &1: Create cofile | Space: object requires documentation | ||
| 183 | Step &1: Copy &2 to &3 | Space: object requires documentation | ||
| 184 | Step &1: Set status to 'included' | Space: object requires documentation | ||
| 185 | Include ended successfully | Space: object requires documentation | ||
| 186 | Inclusion canceled | Space: object requires documentation | ||
| 187 | Path = & | Space: object requires documentation | ||
| 188 | Phase &1 canceled due to reason &2 | Space: object requires documentation | ||
| 189 | There is no ADO data file | Space: object requires documentation | ||
| 190 | Restart SPAM and read the current information ('i' button) | Space: object requires documentation | ||
| 191 | &1 has an invalid Basis Release &2 | Space: object requires documentation | ||
| 192 | &1 has an invalid operating system &2 | Space: object requires documentation | ||
| 193 | &1 has an invalid database system &2 | Space: object requires documentation | ||
| 194 | SPAM/SAINT update &1 has a lower version (&2) than SPAM (&3) | Space: object requires documentation | ||
| 195 | &1 requires at least version &2 of Support Package Manager | Space: object requires documentation | ||
| 196 | Attribute &1 for &2 is unknown. A SPAM/SAINT Update is required... | Space: object requires documentation | ||
| 197 | No OCS files were found for uploading | Space: object requires documentation | ||
| 198 | Not all Support Packages for CCRT &1 are in the queue | Space: object requires documentation | ||
| 199 | Predecessor &1 for &2 missing | Space: object requires documentation | ||
| 200 | Could not update package level for component &1 | Space: object requires documentation | ||
| 201 | System inconsistency: Incorrect &1 entry | Space: object requires documentation | ||
| 202 | Invalid combination of options for handling data files | Space: object requires documentation | ||
| 203 | Could not delete data file &1 for Support Package &2 | Space: object requires documentation | ||
| 204 | You can no longer change the scenario | Space: object requires documentation | ||
| 205 | There are no Support Packages in step '&1' | Space: object requires documentation | ||
| 206 | Error during database update of table PAT01 | Space: object requires documentation | ||
| 207 | Test import errors ignored | Space: object requires documentation | ||
| 208 | OCS package &1 is already being processed | Space: object requires documentation | ||
| 209 | OCS package &1 already imported completely | Space: object requires documentation | ||
| 210 | Queue contains a language package. Use transaction SMLT. | Space: object requires documentation | ||
| 211 | Queue contains an add-on installation/upgrade. Use transaction SAINT. | Space: object requires documentation | ||
| 212 | Queue contains a preconfigured system; use SAINT | Space: object requires documentation | ||
| 213 | No OCS packages found for this selection | Space: object requires documentation | ||
| 214 | OCS package not in tree | Space: object requires documentation | ||
| 215 | . | Space: object requires documentation | ||
| 216 | You cannot continue; queue already processed | Space: object requires documentation | ||
| 217 | Versioning cannot be activated or deactivated at this time | Space: object requires documentation | ||
| 218 | Package &1 is too old (data format not suitable for CHECK_FREESPACE) | Space: object requires documentation | ||
| 219 | After the import, you have to perform some follow-up activities | Space: object requires documentation | ||
| 220 | The system found conflicts for add-on &1 release &2 (see list): | Space: object requires documentation | ||
| 221 | Support Package &1 of software component &2 release &3 | Space: object requires documentation | ||
| 222 | Support Package &1 of add-on component &2 release &3 | Space: object requires documentation | ||
| 223 | Installation package &1 of add-on component &2 release &3 | Space: object requires documentation | ||
| 224 | Piece list &1 of already installed add-on component &2 release &3 | Space: object requires documentation | ||
| 225 | Unknown package &1 of type &2 | Space: object requires documentation | ||
| 226 | ... has conflicts with &1 release &2 - piece list: &3 | Space: object requires documentation | ||
| 227 | Conflict check for add-on &1 Release &2 with | Space: object requires documentation | ||
| 228 | Check all add-ons to determine whether conflict check is necessary... | Space: object requires documentation | ||
| 229 | Conflict check for add-on &1 release &2 is not necessary | Space: object requires documentation | ||
| 230 | Conflict check for add-on &1 release &2 is necessary | Space: object requires documentation | ||
| 231 | Conflict resolution by including a CRT for &1 release &2 and &3 | Space: object requires documentation | ||
| 232 | Conflicts resolved by not installing &1 Release 2 or &3 Release &4 | Space: object requires documentation | ||
| 233 | Conflict resolution by not installing of &1 release &2 | Space: object requires documentation | ||
| 234 | Unresolvable conflict (maybe error in the conflict calculation) | Space: object requires documentation | ||
| 235 | Disassembling OCS package &1 ... | Space: object requires documentation | ||
| 236 | ... Data and cofiles for OCS package &1 successfully created | Space: object requires documentation | ||
| 237 | Calculation of the installation queue of included add-ons ... | Space: object requires documentation | ||
| 238 | The following queue was calculated: | Space: object requires documentation | ||
| 239 | &1: &2 - Installation Package for &3 Release &4 | Space: object requires documentation | ||
| 240 | &1: &2 - Support Package for &3 Release &4 | Space: object requires documentation | ||
| 241 | Adding the language packages for the language vector &1 ... | Space: object requires documentation | ||
| 242 | The following language packages were added: | Space: object requires documentation | ||
| 243 | &1 for language &2 of software component &3 release &4 | Space: object requires documentation | ||
| 244 | Calculating the Support Package queue with the following input queue ... | Space: object requires documentation | ||
| 245 | No language packages were added | Space: object requires documentation | ||
| 246 | The following import prerequisites of OCS package &1 are not met: | Space: object requires documentation | ||
| 247 | Support Package &1 must be available or already imported in the system | Space: object requires documentation | ||
| 248 | The calculation is based on the following software component vector: | Space: object requires documentation | ||
| 249 | Component: &1 Release &2, SP level: &3 (component type &4) | Space: object requires documentation | ||
| 250 | The following target vector is planned: | Space: object requires documentation | ||
| 251 | Start of phase: &1 | Space: object requires documentation | ||
| 252 | End of phase: &1 | Space: object requires documentation | ||
| 253 | Start date: &1 | Space: object requires documentation | ||
| 254 | Start time: &1 | Space: object requires documentation | ||
| 255 | End date: &1 | Space: object requires documentation | ||
| 256 | End time: &1 | Space: object requires documentation | ||
| 257 | You want to install the following add-on components: | Space: object requires documentation | ||
| 258 | No add-on components were specified to be installed | Space: object requires documentation | ||
| 259 | Add-on &1 release &2 must be installed in the system | Space: object requires documentation | ||
| 260 | Prerequisite &1 has to be fulfilled | Space: object requires documentation | ||
| 261 | Installation/upgrade package for add-on &1 Release &2 does not exist | Space: object requires documentation | ||
| 262 | Importing the queue generates the following software component vector: | Space: object requires documentation | ||
| 263 | Calculating queue part for add-on &1 Release &2 | Space: object requires documentation | ||
| 264 | The following overall queue was calculated: | Space: object requires documentation | ||
| 265 | In (alternative) prerequisite set &1: | Space: object requires documentation | ||
| 266 | Saving the current OCS queue (&1, &2) | Space: object requires documentation | ||
| 267 | &1: &2 - SPAM/SAINT Update | Space: object requires documentation | ||
| 268 | Deleting the current OCS queue (&1, &2) &3 | Space: object requires documentation | ||
| 269 | OCS queue is already empty; no deletion necessary | Space: object requires documentation | ||
| 270 | Resetting OCS package &1 | Space: object requires documentation | ||
| 271 | The import of the OCS queue is in phase '&1' | Space: object requires documentation | ||
| 272 | Resetting the add-on &1 Release &2 | Space: object requires documentation | ||
| 273 | Resetting the preconfigured system &1 Release &2 | Space: object requires documentation | ||
| 274 | Resetting status of the current OCS queue (&1, &2) &3 | Space: object requires documentation | ||
| 275 | OCS queue is empty -> no reset possible | Space: object requires documentation | ||
| 276 | Reset of the status of the OCS queue canceled by user | Space: object requires documentation | ||
| 277 | Confirming import of the OCS queue (&1, &2) | Space: object requires documentation | ||
| 278 | Confirming OCS package &1 | Space: object requires documentation | ||
| 279 | Deleting the associated data files... | Space: object requires documentation | ||
| 280 | Setting the status of PCS &1 Release &2 to '&3' | Space: object requires documentation | ||
| 281 | Setting the status of the add-on &1 Release &2 to '&3' | Space: object requires documentation | ||
| 282 | Setting the language vector of the add-on &1 to '&2' | Space: object requires documentation | ||
| 283 | Log '&1' was not found or is empty | Space: object requires documentation | ||
| 284 | Import of the current OCS Queue (&1, &2) | Space: object requires documentation | ||
| 285 | The current OCS Queue consists of: | Space: object requires documentation | ||
| 286 | The import is continued in phase '&1' | Space: object requires documentation | ||
| 287 | The import will not be started | Space: object requires documentation | ||
| 288 | Displaying notes to be read before the start of the import | Space: object requires documentation | ||
| 289 | Note &1 for OCS Package &2 (Password is required) | Space: object requires documentation | ||
| 290 | Note &1 for OCS Package &2 | Space: object requires documentation | ||
| 291 | The import was canceled by the user | Space: object requires documentation | ||
| 292 | Displaying note &1 in SAP Service Marketplace | Space: object requires documentation | ||
| 293 | Correct password entered for OCS package &1, note &2 | Space: object requires documentation | ||
| 294 | Incorrect password entered for OCS package &1, note &2 | Space: object requires documentation | ||
| 295 | Scheduling import in background (start immediately) | Space: object requires documentation | ||
| 296 | Scheduling import in background (planned start: &1, &2) | Space: object requires documentation | ||
| 297 | The import of the queue was successfully finished (&1, &2) | Space: object requires documentation | ||
| 298 | Component &1 is locked against OCS package imports | Space: object requires documentation | ||
| 299 | Error in insert/update on database table &1 | Space: object requires documentation | ||
| 300 | OCS package &1 is a SPAM/SAINT update | Space: object requires documentation | ||
| 301 | You may only reset the flag if type &1 &2 has not yet been imported | Space: object requires documentation | ||
| 302 | No S_PTCH_ADM authorization with activity &1 for values &2 &3 | Space: object requires documentation | ||
| 303 | You may only set type &3 if type &1 was not canceled | Space: object requires documentation | ||
| 304 | From now: Import of types &1 &3 instead of types &2 &4 | Space: object requires documentation | ||
| 305 | From now: Import of types &2 &4 instead of types &1 &3 | Space: object requires documentation | ||
| 306 | Type &1 &2 activated; read note(s) &3 &4 | Space: object requires documentation | ||
| 307 | Not all conflicts were resolved. See long text | Space: object requires documentation | ||
| 308 | Deactivating import mode 'Downtime-minimized' | Space: object requires documentation | ||
| 309 | Import mode 'Downtime-minimized' activated | Space: object requires documentation | ||
| 310 | Import mode 'Downtime-minimized' deactivated | Space: object requires documentation | ||
| 311 | Browser starting .... | Space: object requires documentation | ||
| 312 | You cannot change the import mode at present | Space: object requires documentation | ||
| 313 | Import canceled due to an error situation (&1, &2) | Space: object requires documentation | ||
| 314 | Intended stop of the import (&1, &2) | Space: object requires documentation | ||
| 315 | Interrupting import due to an error situation (&1, &2) | Space: object requires documentation | ||
| 316 | Displaying detailed information about error in phase '&1' | Space: object requires documentation | ||
| 317 | Repeating the import of the OCS queue in phase '&1' | Space: object requires documentation | ||
| 318 | Skipping the errors in phase '&1' and continuing the import | Space: object requires documentation | ||
| 319 | The import is done with the &1 scenario | Space: object requires documentation | ||
| 320 | Import mode 'Downtime-minimized' is activated | Space: object requires documentation | ||
| 321 | Displaying detail information | Space: object requires documentation | ||
| 322 | Continue the import | Space: object requires documentation | ||
| 323 | Creation of versions during import will be switched off | Space: object requires documentation | ||
| 324 | Checking which action is planned for this breakpoint... | Space: object requires documentation | ||
| 325 | Stop the import procedure | Space: object requires documentation | ||
| 326 | Planned start time &1, &2 is greater than maximum start time &3, &4 | Space: object requires documentation | ||
| 327 | Ignore generation errors (&1, &2) | Space: object requires documentation | ||
| 328 | Ignore test import errors (&1, &2) | Space: object requires documentation | ||
| 329 | Importing the current OCS queue in background (&1, &2) | Space: object requires documentation | ||
| 330 | Deletion of the OCS queue canceled by user | Space: object requires documentation | ||
| 331 | Installation/upgrade of the add-on &1 Release &2 (&3, &4) | Space: object requires documentation | ||
| 332 | Installation of the preconfigured system &1 Release &2 (&3, &4) | Space: object requires documentation | ||
| 333 | Add-on &1 Release &2 installed (&3, &4) | Space: object requires documentation | ||
| 334 | Preconfigured system &1 Release &2 (&3, &4) | Space: object requires documentation | ||
| 335 | Import phase '&1' (&2, &3) | Space: object requires documentation | ||
| 336 | Import phase '&1' was successfully finished (&2, &3) | Space: object requires documentation | ||
| 337 | Wrong scenario (&1) was changed to &2 -> start the import again | Space: object requires documentation | ||
| 338 | Import phase '&1' was already processed -> skip phase | Space: object requires documentation | ||
| 339 | Complete creation of version is switched off -> skip phase | Space: object requires documentation | ||
| 340 | &1 &2 &3 &4 | Space: object requires documentation | ||
| 341 | Error during executing the tp command 'tp &1 &2 &3 ...' | Space: object requires documentation | ||
| 342 | Error in the communication with tp | Space: object requires documentation | ||
| 343 | tp return code: '&1' , tp message: '&2' , tp output: | Space: object requires documentation | ||
| 344 | The tp buffer contains old incompletely processed OCS packages | Space: object requires documentation | ||
| 345 | The tp parameter '&1' has a wrong value ('&2' instead of '&3') | Space: object requires documentation | ||
| 346 | tp version is too old (current: '&1', required: '&2') | Space: object requires documentation | ||
| 347 | R3trans is too old (current: '&1', required: '&2') | Space: object requires documentation | ||
| 348 | Error when disassembling EPS parcel of OCS package &1: '&2' | Space: object requires documentation | ||
| 349 | Details of the error situation can also be found in the import logs | Space: object requires documentation | ||
| 350 | The object list &1 is not available in the system | Space: object requires documentation | ||
| 351 | Objects are locked in open change requests | Space: object requires documentation | ||
| 352 | There are conflicts between OCS packages and add-ons | Space: object requires documentation | ||
| 353 | Packages in queue do not exist in tp buffer (e.g. &1) | Space: object requires documentation | ||
| 354 | The tp buffer contains more Packages than the queue (e.g. &1) | Space: object requires documentation | ||
| 355 | The tp buffer contains inconsistent entries (e.g. &1) | Space: object requires documentation | ||
| 356 | Packages in the wrong order in the tp buffer (e.g. &1) | Space: object requires documentation | ||
| 357 | tp buffer does not contain any valid entries for OCS packages in queue | Space: object requires documentation | ||
| 358 | Error for OCS package &1: tp step: '&2', tp return code: '&3' | Space: object requires documentation | ||
| 359 | Error for OCS package &1: tp step: '&2', unprocessed objects: &3 | Space: object requires documentation | ||
| 360 | Error during execution of report &1 | Space: object requires documentation | ||
| 361 | Modified objects has to be adjusted against the SAP standard | Space: object requires documentation | ||
| 362 | ABAP generation is switched off -> skip phase | Space: object requires documentation | ||
| 363 | tp buffer still contains incompletely processed OCS packages | Space: object requires documentation | ||
| 364 | Error during reset of the FCS flag in table UVERS | Space: object requires documentation | ||
| 365 | Setting the status of OCS package &1 to '&2' | Space: object requires documentation | ||
| 366 | Consistent queue part calculated for add-on &1 Release &2 | Space: object requires documentation | ||
| 367 | May be possible to ignore conflicts; see long text | Space: object requires documentation | ||
| 368 | The start time was adjusted to the current time (&1, &2) | Space: object requires documentation | ||
| 369 | Incorrect installation password entered for &1 | Space: object requires documentation | ||
| 370 | Unfulfilled prerequisite for &1: &2 - '&3' | Space: object requires documentation | ||
| 371 | There are unfulfilled import prerequisites for packages in the queue | Space: object requires documentation | ||
| 372 | There are open updates in the dictionary | Space: object requires documentation | ||
| 373 | System consistency: Component model with ID '&1' does not exist | Space: object requires documentation | ||
| 374 | You can ignore this error if no more follow | Space: object requires documentation | ||
| 375 | Checking the queue for upgrade-relevant OCS package attributes... | Space: object requires documentation | ||
| 376 | Entering kernel / transport tool requirements in TOOLCHKEXE.LST | Space: object requires documentation | ||
| 377 | Queue contains no requirements for the kernel or transport tools | Space: object requires documentation | ||
| 378 | Checking and extending the control file SORTTABS.LST | Space: object requires documentation | ||
| 379 | Queue does not require control file SORTTABS.LST to be extended | Space: object requires documentation | ||
| 380 | Table &1 is already included in SORTTABS.LST -> No action required | Space: object requires documentation | ||
| 381 | Table &1 is not included in SORTTABS.LST -> Is added | Space: object requires documentation | ||
| 382 | Setting the status of modification adjustment transport &1 to '&2' | Space: object requires documentation | ||
| 383 | Confirming modification transport &1 | Space: object requires documentation | ||
| 384 | &1: &2 - Modification transport | Space: object requires documentation | ||
| 385 | Resetting modification transport &1 | Space: object requires documentation | ||
| 386 | Support Package queue defined... | Space: object requires documentation | ||
| 387 | Modification transports added to Support Package queue... | Space: object requires documentation | ||
| 388 | Support Package queue redefined... | Space: object requires documentation | ||
| 389 | The following CRTs of add-on &1 Release &2 must also be included: | Space: object requires documentation | ||
| 390 | CRT &4 for Support Package &1 of software component &2 Release &3 | The short text describes the object sufficiently | ||
| 391 | CRT &3 for OCS package &1 of type &2 | Space: object requires documentation | ||
| 392 | The import will not be continued | Space: object requires documentation | ||
| 393 | Finishing modification adjustment (&3) (&1, &2) | Space: object requires documentation | ||
| 394 | Finished modification adjustment (&1) confirmed | Space: object requires documentation | ||
| 395 | Disassembling modification adjustment transport &1 | Space: object requires documentation | ||
| 396 | Disassembling OCS package &1 | Space: object requires documentation | ||
| 397 | Use EPS package &1 with OCS file format '&2' | Space: object requires documentation | ||
| 398 | Create data file &1 | Space: object requires documentation | ||
| 399 | Create associated cofile... | Space: object requires documentation | ||
| 400 | -> Repeating disassembly, forced overwriting of the data file | Space: object requires documentation | ||
| 401 | No software component for Support Packages found | Space: object requires documentation | ||
| 402 | OCS locked by user &1 with transaction &2 | Space: object requires documentation | ||
| 403 | No valid queue for &1 &2 &3 | Space: object requires documentation | ||
| 404 | Add on installation/upgrade not yet complete. CRTs are required | Space: object requires documentation | ||
| 405 | No semaphore available -> Status is not set | Space: object requires documentation | ||
| 406 | Attribute of OCS package &1 not met | Space: object requires documentation | ||
| 407 | Queue deleted | Space: object requires documentation | ||
| 408 | Queue could not be deleted | Space: object requires documentation | ||
| 409 | You first need an FCS Support Package for your system | Space: object requires documentation | ||
| 410 | There is no valid Support Package queue | Space: object requires documentation | ||
| 411 | There is no valid CRT queue for upgrading &1 &2 &3 | Space: object requires documentation | ||
| 412 | There is no valid CRT queue for the upgrade | Space: object requires documentation | ||
| 413 | Could not determine installed components (&1) | Space: object requires documentation | ||
| 414 | OCS packages are missing for a successful installation | Space: object requires documentation | ||
| 415 | Attributes for OCS package &1 loaded | Space: object requires documentation | ||
| 416 | OCS package &1 already imported. Attributes cannot be loaded | Space: object requires documentation | ||
| 417 | Installation queue not defined | Space: object requires documentation | ||
| 418 | OCS packages are missing for a successful installation | Space: object requires documentation | ||
| 419 | Add-on installation/upgrade not yet complete; CRTs are required | Space: object requires documentation | ||
| 420 | Only display functions available, since transaction &2 is locked by &1 | Space: object requires documentation | ||
| 421 | Support Package &1 successfully disassembled | Space: object requires documentation | ||
| 422 | No WWW browser available; download note &1 manually from SAPNet | Space: object requires documentation | ||
| 423 | The system is not currently being upgraded; upgrade mode incorrect | Space: object requires documentation | ||
| 424 | Package &1: Import prerequisites are not fulfilled | Space: object requires documentation | ||
| 425 | Package &1 : &2 &3 &4 | Space: object requires documentation | ||
| 426 | Incorrect password ... | Space: object requires documentation | ||
| 427 | No currently imported SPAM/SAINT update found | Space: object requires documentation | ||
| 428 | Could not calculate a valid Support Package queue | Space: object requires documentation | ||
| 429 | OCS package &1 is corrupt. Contact the vendor | Space: object requires documentation | ||
| 430 | The queue (ID=&1) does not belong to the current change request (ID=&2) | The short text describes the object sufficiently | ||
| 431 | Software component &1 Release &2 is already on SP level &3 | The short text describes the object sufficiently | ||
| 432 | Calculating queue part for &1 Release &2 with target SP &3 (level &4) | The short text describes the object sufficiently | ||
| 433 | Support Package for &1 Release &2, SP level &3 does not exist | The short text describes the object sufficiently | ||
| 434 | Conflicts resolved by including CRT &3 for add-on &1 Release &2 | Space: object requires documentation | ||
| 435 | Consistent queue part already calculated for add-on &1 Release &2 | The short text describes the object sufficiently | ||
| 436 | Warning message about risk of resetting to "Force" mode displayed | The short text describes the object sufficiently | ||
| 437 | Import transport request &1 before the OCS queue | The short text describes the object sufficiently | ||
| 438 | Import requests in the TMS import queue before the OCS queue | The short text describes the object sufficiently | ||
| 439 | Support Package &1 is not a valid target SP for the queue calculation | Space: object requires documentation | ||
| 440 | Support Package &1 is obsolete and must not be imported | Space: object requires documentation | ||
| 441 | The test import of the queue finished with tp return code '&1' | The short text describes the object sufficiently | ||
| 442 | Analyzing the return codes of the individual packages... | The short text describes the object sufficiently | ||
| 443 | The test import for &1 was not executed | The short text describes the object sufficiently | ||
| 444 | The test import for &1 finished error free | The short text describes the object sufficiently | ||
| 445 | The test import for &1 finished with the following errors: | The short text describes the object sufficiently | ||
| 446 | Test import for &1 canceled | The short text describes the object sufficiently | ||
| 447 | Error when analyzing tp return code '&2' of test import for &1 | The short text describes the object sufficiently | ||
| 448 | The test import for &1 finished with errors which can be ignored: | The short text describes the object sufficiently | ||
| 449 | The execution of the check steps finished successfully (&1, &2) | The short text describes the object sufficiently | ||
| 450 | Execute check steps before scheduling the import job | The short text describes the object sufficiently | ||
| 451 | The queue is currently being imported by a background job | Space: object requires documentation | ||
| 452 | The import of the queue is scheduled as a background job (Start: &1, &2) | Space: object requires documentation | ||
| 453 | The queue is currently being imported by user &1 | Space: object requires documentation | ||
| 454 | The queue is currently being processed by user &1 | Space: object requires documentation | ||
| 455 | The queue is defined. The import was not started yet. | Space: object requires documentation | ||
| 456 | Import of the queue canceled because of a problem | Space: object requires documentation | ||
| 457 | The queue was imported successfully | Space: object requires documentation | ||
| 458 | The import of the queue was stopped intentionally | Space: object requires documentation | ||
| 459 | Import of the queue canceled because of conflicts | Space: object requires documentation | ||
| 460 | There are no current messages | Space: object requires documentation | ||
| 461 | No &1 queue exists yet. First start the queue calculation... | Space: object requires documentation | ||
| 462 | Interrupting import for manual actions (&1, &2) | The short text describes the object sufficiently | ||
| 463 | User &1 is locked | Space: object requires documentation | ||
| 464 | User &1 does not exist | Space: object requires documentation | ||
| 465 | Test installation/test upgrade of add-on &1 Release &2 (&3, &4) | The short text describes the object sufficiently | ||
| 466 | The 'Downtime-minimized' import mode has to be switched off | Space: object requires documentation | ||
| 467 | The note corrections have to be adjusted manually | The short text describes the object sufficiently | ||
| 468 | An error occurred while reimplementing the notes | The short text describes the object sufficiently | ||
| 469 | The note &1 could not be reimplemented completely | The short text describes the object sufficiently | ||
| 470 | The note &1 could not be reset completely | The short text describes the object sufficiently | ||
| 471 | Modification adjustment already completed: &1 | Space: object requires documentation | ||
| 472 | No. of objects to be adjusted: &1 x DDIC (SPDD), &2 x repository (SPAU) | The short text describes the object sufficiently | ||
| 473 | Preview objects to be adjusted: &1 x DDIC (SPDD), &2 x repository (SPAU) | The short text describes the object sufficiently | ||
| 474 | &1 repository objects were found which need to be adjusted | The short text describes the object sufficiently | ||
| 475 | Executing automatic adjustment of note corrections... | The short text describes the object sufficiently | ||
| 476 | Manual modification adjustment is neccessary | The short text describes the object sufficiently | ||
| 477 | There are no note corrections which can be adjusted automatically | The short text describes the object sufficiently | ||
| 478 | Resetting note &1 | The short text describes the object sufficiently | ||
| 479 | Reimplementing note &1 | The short text describes the object sufficiently | ||
| 480 | Note &1 has to be adjusted manually | The short text describes the object sufficiently | ||
| 481 | Inconsistency in Support Package tools (table &1) | Space: object requires documentation | ||
| 482 | The import of the Support Package queue must be finished first | Space: object requires documentation | ||
| 483 | Import of OCS package queue must be finished first | Space: object requires documentation | ||
| 484 | The add-on installation must be finished first | Space: object requires documentation | ||
| 485 | Add-ons are installed that are incompatible with &1 (see long text) | Space: object requires documentation | ||
| 486 | Industry extension &1, Release &2 not installed and cannot be activated | Space: object requires documentation | ||
| 487 | Support Packages have to be imported before activating &1 | Space: object requires documentation | ||
| 488 | Add-ons are installed that are incompatible with &1 (see following list) | Space: object requires documentation | ||
| 489 | &1 Release &2 | The short text describes the object sufficiently | ||
| 490 | &1 - Conflict Resolution Transport (CRT) for &2 | The short text describes the object sufficiently | ||
| 491 | Using add-on installation package &1 (type &4) for add-on &2 release &3 | The short text describes the object sufficiently | ||
| 492 | Prerequisite software component &1 Release &2 is not installed | The short text describes the object sufficiently | ||
| 493 | Prerequisite add-on component &1 Release &2 is not installed | The short text describes the object sufficiently | ||
| 494 | Invalid software component &1 Release &2 is installed | The short text describes the object sufficiently | ||
| 495 | Required software component &1 is not installed with release &2 or higher | The short text describes the object sufficiently | ||
| 496 | The Industry Extension &1 is not installed and cannot be activated | Space: object requires documentation | ||
| 497 | Open V3 update and data extraction requests were found | The short text describes the object sufficiently | ||
| 498 | Open data extraction requests were found | The short text describes the object sufficiently | ||
| 499 | Open V3 update requests were found | The short text describes the object sufficiently | ||
| 500 | The warning about open V3 update and data extraction requests was ignored | The short text describes the object sufficiently | ||
| 501 | Unknown Support Package: &1 | Space: object requires documentation | ||
| 502 | OCS file format error in: &1 | Space: object requires documentation | ||
| 503 | Call of &1 not permitted | Space: object requires documentation | ||
| 504 | Invalid condition: &1 &2 | Space: object requires documentation | ||
| 505 | OCS file for &1 cannot be opened: &2 | Space: object requires documentation | ||
| 506 | Queue is not initial | Space: object requires documentation | ||
| 507 | SPAM/SAINT version too low for Support Package: &1 | Space: object requires documentation | ||
| 508 | Could not generate SPAM/SAINT version | Space: object requires documentation | ||
| 509 | Unknown OCS file format '&1' &2; SPAM/SAINT update required | Space: object requires documentation | ||
| 510 | You cannot reset the queue from import phase '&1' | Space: object requires documentation | ||
| 511 | Unknown software component '&1' | Space: object requires documentation | ||
| 512 | No description exists for '&1' Support Package level '&2' | Space: object requires documentation | ||
| 513 | Queue is already completely imported | Space: object requires documentation | ||
| 514 | Error when creating files for transport request &1 | Space: object requires documentation | ||
| 515 | Error when creating cofile for transport request &1 | Space: object requires documentation | ||
| 516 | Error when writing file &1 | Space: object requires documentation | ||
| 517 | Add-on &1 Release &2 cannot be installed | Space: object requires documentation | ||
| 518 | Add-on &1 Release &2 cannot be placed in the current queue | Space: object requires documentation | ||
| 519 | Add-on &1 Release &2 is not installed | Space: object requires documentation | ||
| 520 | Incompatible software component installed | Space: object requires documentation | ||
| 521 | Non-permitted release of add-on &1 installed | Space: object requires documentation | ||
| 522 | Add-on &1 is already installed | Space: object requires documentation | ||
| 523 | No add-on installation in the queue | Space: object requires documentation | ||
| 524 | Call transaction &1 in English or German only | Space: object requires documentation | ||
| 525 | Call transaction &1 in English or German only | Space: object requires documentation | ||
| 526 | The add-on installation queue was confirmed | Space: object requires documentation | ||
| 527 | Inconsistency in the OCS administration tables | Space: object requires documentation | ||
| 528 | Log on to the correct client | Space: object requires documentation | ||
| 529 | Inconsistency in transaction SAINT; only display functions are available | Space: object requires documentation | ||
| 530 | Preconfigured system (PCS) is already installed in the system | Space: object requires documentation | ||
| 531 | Only display functions are available in an SAP production system | Space: object requires documentation | ||
| 532 | Logon client & is protected from modifications and imports | Space: object requires documentation | ||
| 533 | Only display functions are available for user SAP* | Space: object requires documentation | ||
| 534 | A newer version of &1 (&2 version &3) is already installed | Space: object requires documentation | ||
| 535 | Import preconditions have changed -> queue is inconsistent | Space: object requires documentation | ||
| 536 | File positioning error in OCS file for &1: &2 | Space: object requires documentation | ||
| 537 | PCS &1 Release &2 can only be installed in a client other than 000 | Space: object requires documentation | ||
| 538 | Add-on &1 Release &2 can only be installed in client 000 | Space: object requires documentation | ||
| 539 | Incompatible preconfigured systems (PCS) already installed | Space: object requires documentation | ||
| 540 | Compatible preconfigured systems already installed in client &2 | Space: object requires documentation | ||
| 541 | OCS package &1 requires at least Kernel Release &2 with patch number &3 | Space: object requires documentation | ||
| 542 | OCS package &1 requires at least tp version &2 | Space: object requires documentation | ||
| 543 | OCS package &1 requires at least R3trans version &2 | Space: object requires documentation | ||
| 544 | OCS package &1 does not match the current software component vector | Space: object requires documentation | ||
| 545 | Industry Extension &1 must be activated | Space: object requires documentation | ||
| 546 | Industry Extension &1 cannot be activated | Space: object requires documentation | ||
| 547 | Prerequisite note corrections are not yet implemented | The short text describes the object sufficiently | ||
| 548 | Activation of &1 requires upgrade to the following component versions | Space: object requires documentation | ||
| 549 | &1 Release &2 - requested by &3 | The short text describes the object sufficiently | ||
| 550 | &1 Release &2 - requested by &3 (see note &4) | The short text describes the object sufficiently | ||
| 551 | Due to performance reasons, not all entries could be expanded | Space: object requires documentation | ||
| 552 | You must only enter values greater than &1 | The short text describes the object sufficiently | ||
| 553 | Not possible to reset the status; delete the queue completely | The short text describes the object sufficiently | ||
| 554 | Inconsistency: Repeat the queue status reset | The short text describes the object sufficiently | ||
| 555 | Inconsistency: Delete the queue completely and define it again | The short text describes the object sufficiently | ||
| 556 | Specify the transport request to be searched for | The short text describes the object sufficiently | ||
| 557 | The tp buffer &1 does not contain any modification adjustment transports | The short text describes the object sufficiently | ||
| 558 | The SAP system has to be stopped and restarted on all application servers | Space: object requires documentation | ||
| 559 | Use the Software Update Manager (SUM) to import the queue | Space: object requires documentation | ||
| 560 | This enhancement package installation must be configured using stack XML | Space: object requires documentation | ||
| 561 | Creating subcomponents for software component &1, &2 | The short text describes the object sufficiently | ||
| 562 | Software component &1 Release &2 does not have required SP level &3 | The short text describes the object sufficiently | ||
| 563 | Invalid software component &1 Release &2, SP level &3 | The short text describes the object sufficiently | ||
| 564 | Support Package patch &1 is obsolete and cannot be imported | Space: object requires documentation | ||
| 565 | The equivalent SP patch &4 for component &1 is missing. | The short text describes the object sufficiently | ||
| 566 | Deleting obsolete subcomponents of software component &1, &2 | The short text describes the object sufficiently | ||
| 567 | ID of the current change request not passed | The short text describes the object sufficiently | ||
| 568 | Function module &1 finished with return code &2 | The short text describes the object sufficiently | ||
| 569 | Insert/Update of Support Package &1 into PAT03_PRE aborted | The short text describes the object sufficiently | ||
| 570 | Internal error in method &1: &2 &3 &4 | The short text describes the object sufficiently | ||
| 571 | The loaded stack configuration does not fit to the current system state | The short text describes the object sufficiently | ||
| 572 | No stack configurations available in Maintenance Optimizer | The short text describes the object sufficiently | ||
| 573 | The transport request &1 was marked as modification adjustment transport | The short text describes the object sufficiently | ||
| 574 | The loaded stack configuration is not valid for system &1 | The short text describes the object sufficiently | ||
| 575 | Stack configuration is not valid for system &1, installation number &2 | The short text describes the object sufficiently | ||
| 576 | The stack configuration does not contain a product stack | The short text describes the object sufficiently | ||
| 577 | The stack configuration does not contain a software feature stack | The short text describes the object sufficiently | ||
| 578 | Stack configuration does not contain data for ABAP software components | The short text describes the object sufficiently | ||
| 579 | Internal error in method "&1": field "&2" does not exist in structure &3 | The short text describes the object sufficiently | ||
| 580 | Internal error in method "&1": invalid value "&2" for field "&3-&4" | The short text describes the object sufficiently | ||
| 581 | Checking completeness of the target software component vector | The short text describes the object sufficiently | ||
| 582 | Software component &1 Release &2 is required (see note &3) | The short text describes the object sufficiently | ||
| 583 | Software component &1 Release &2 is required | The short text describes the object sufficiently | ||
| 584 | Revise the selected "Technical Usages" in Maintenance Optimizer | The short text describes the object sufficiently | ||
| 585 | Revise the selections and decisions in the phase IS_SELECT | The short text describes the object sufficiently | ||
| 586 | Select these components in phase IS_SELECT for upgrades | The short text describes the object sufficiently | ||
| 587 | There are upgrades to required software component versions missing | The short text describes the object sufficiently | ||
| 588 | The target software component vector is complete | The short text describes the object sufficiently | ||
| 589 | Checking whether OCS package &1 is compatible with SC vector | The short text describes the object sufficiently | ||
| 590 | Checking whether add-on &1, &2 is compatible with SC vector | The short text describes the object sufficiently | ||
| 591 | Starting optimization of the import queue | The short text describes the object sufficiently | ||
| 592 | The optimization of the import queue finished successfully | The short text describes the object sufficiently | ||
| 593 | The import queue is empty | The short text describes the object sufficiently | ||
| 594 | &1 of &2 objects do not need to be imported (&3 %) | Space: object requires documentation | ||
| 595 | Inconsistent program state: &1 | Space: object requires documentation | ||
| 596 | The optimization of the import queue needs &1 MB memory | Space: object requires documentation | ||
| 597 | No Support Package with SP level &3 available for component &1 rel.&2 | The short text describes the object sufficiently | ||
| 598 | Required Support Packages for component &1 are missing in the queue | Space: object requires documentation | ||
| 599 | Required Support Packages for component &1 are missing in the queue | Space: object requires documentation | ||
| 600 | &1 is not sufficient, higher Support Packages are necessary | Space: object requires documentation | ||
| 601 | Preconfigured system &1, Release &2 is already installed | Space: object requires documentation | ||
| 602 | Object list &1 for PCS &2 Release &3 does not exist | Space: object requires documentation | ||
| 603 | PCS &1 Release &2 was not initialized; No status update | Space: object requires documentation | ||
| 604 | PCS installation queue was confirmed | Space: object requires documentation | ||
| 605 | The mandatory SP Patch &4 for component &1 is missing in the queue | The short text describes the object sufficiently | ||
| 606 | The value of the extended attribute &1 is wrongly formatted | The short text describes the object sufficiently | ||
| 607 | The mandatory SP &4 for component &1 rel. &2 is missing in the queue | The short text describes the object sufficiently | ||
| 608 | The import of Prepackages is not allowed in this system | Space: object requires documentation | ||
| 609 | The loaded stack configuration does not contain Add-On Install./Upgrades | The short text describes the object sufficiently | ||
| 610 | The installation of &1 rel. &2 must be configured with a Stack XML | Space: object requires documentation | ||
| 611 | Reading of compressed stack XML with ID &1 (&2) started | The short text describes the object sufficiently | ||
| 612 | Reading of uncompressed stack XML with ID &1 (&2) started | The short text describes the object sufficiently | ||
| 613 | Reading of stack XML file from application server (&1) started | The short text describes the object sufficiently | ||
| 614 | Stack XML with ID &1 was successfully read | The short text describes the object sufficiently | ||
| 615 | Stack XML file was successfully read from the application server | The short text describes the object sufficiently | ||
| 616 | Decompression of stack XML started | The short text describes the object sufficiently | ||
| 617 | Uncompressing the stack XML was successfully completed | The short text describes the object sufficiently | ||
| 618 | Conversion of stack XML to OCS tables started (&1) | The short text describes the object sufficiently | ||
| 619 | Evaluating the stack XML was successfully completed | The short text describes the object sufficiently | ||
| 620 | RFC destination to Solution Manager is not configured (application &1) | The short text describes the object sufficiently | ||
| 621 | XML file '&1' does not exist or could not be opened | The short text describes the object sufficiently | ||
| 622 | XML file '&1' is empty or could not be opened | The short text describes the object sufficiently | ||
| 623 | XML stack of type &1 was created by MOPZ version &2 | The short text describes the object sufficiently | ||
| 624 | Start the XSLT transformation '&2' (&1) | The short text describes the object sufficiently | ||
| 625 | XSLT transformation was successfully completed | The short text describes the object sufficiently | ||
| 626 | Reading stack &1 "&2", product version &3 "&4" | The short text describes the object sufficiently | ||
| 627 | Product version &1 "&2" "&3" was inserted into table &4 | The short text describes the object sufficiently | ||
| 628 | Reading SP feature stack "&1&2&3&4" | The short text describes the object sufficiently | ||
| 629 | Checking validity of SP feature stack target system &1, inst. no.&2 (&3): | The short text describes the object sufficiently | ||
| 630 | Target system ID &1 does not match local system ID &2 | The short text describes the object sufficiently | ||
| 631 | Target system inst. no. &1 does not match local inst. no. &2 | The short text describes the object sufficiently | ||
| 632 | &1 &2 of target system matches &1 of local system | The short text describes the object sufficiently | ||
| 633 | SW feature &1 &2 was assigned to technical usage &3 | The short text describes the object sufficiently | ||
| 634 | Reading software components of SP feature stack "&1" | The short text describes the object sufficiently | ||
| 635 | SP level &1 was determined for &2 &3 | The short text describes the object sufficiently | ||
| 636 | Software component version &1 &2 was inserted into table &3 | The short text describes the object sufficiently | ||
| 637 | Replaced product version &1 "&2" "&3" was inserted into table &4 | The short text describes the object sufficiently | ||
| 638 | Software component version &1 &2 (SP level &3) was inserted in table &4 | The short text describes the object sufficiently | ||
| 639 | Level &3 for software component version &1 &2 inserted into table &4 | The short text describes the object sufficiently | ||
| 640 | Version &2 level &3 for software component &1 inserted into table &4 | The short text describes the object sufficiently | ||
| 641 | Replaced SF feature &1 "&2" "&3" was inserted into table &4 | The short text describes the object sufficiently | ||
| 642 | Included SW feature &1 "&2" "&3" was inserted into table &4 | The short text describes the object sufficiently | ||
| 643 | Read information for the target system &1 (&2) | The short text describes the object sufficiently | ||
| 644 | Reading start component vector in target system &1 (&2) | The short text describes the object sufficiently | ||
| 645 | Reading initial component vector of export DVD &1 &2 (&3) | The short text describes the object sufficiently | ||
| 646 | Reading replaced products of stack &1 "&2" | The short text describes the object sufficiently | ||
| 647 | Reading SP feature stacks of stack &1 "&2" | The short text describes the object sufficiently | ||
| 648 | Reading technical usages of SW feature stack &1 | The short text describes the object sufficiently | ||
| 649 | Stack ID &1 "&2" was inserted into table &3 | The short text describes the object sufficiently | ||
| 650 | SW feature &1 "&2" "&3" was inserted into table &4 | The short text describes the object sufficiently | ||
| 651 | Reading replaced features for SW feature "&1" | The short text describes the object sufficiently | ||
| 652 | Reading included features for SW feature "&1" | The short text describes the object sufficiently | ||
| 653 | List of technical usages passed to table &1 | The short text describes the object sufficiently | ||
| 654 | The target system is defined as non-ABAP system | The short text describes the object sufficiently | ||
| 655 | The SP feature stack is not valid for the current system | The short text describes the object sufficiently | ||
| 656 | Check the target system &1, inst.no. &2 of the software component &3 &4 | The short text describes the object sufficiently | ||
| 657 | The software component is not valid for the current system | The short text describes the object sufficiently | ||
| 658 | List of product versions passed from table &1 to &2 | The short text describes the object sufficiently | ||
| 659 | The system information is not valid for the current system | The short text describes the object sufficiently | ||
| 660 | Read product versions for the target system &1 (&2) | The short text describes the object sufficiently | ||
| 661 | Error in communication with Transport Management System (STMS) | The short text describes the object sufficiently | ||
| 662 | The non-ABAP deployment is not configured in TMS | The short text describes the object sufficiently | ||
| 663 | The non-ABAP deplyoment web service is not configured in TMS | The short text describes the object sufficiently | ||
| 664 | There is no deploy tool for non-ABAP deployment configured | The short text describes the object sufficiently | ||
| 665 | Error in configuration of non-ABAP deployment | The short text describes the object sufficiently | ||
| 666 | The Basis SP level is too low. A non-ABAP deployment is not possible yet. | The short text describes the object sufficiently | ||
| 667 | Read software features for the target system &1 (&2) | The short text describes the object sufficiently | ||
| 668 | Read software component vector for the target system &1 (&2) | The short text describes the object sufficiently | ||
| 669 | The system info XML is not valid for the system &1, installation no. &2 | The short text describes the object sufficiently | ||
| 670 | The system info XML does not contain any valid system information | The short text describes the object sufficiently | ||
| 671 | Settings adjusted for version database systems (see long text) | Space: object requires documentation | ||
| 672 | Versioning cannot be switched off in version database systems | Space: object requires documentation | ||
| 673 | The system info XML contains the not installed software component &1 &2 | The short text describes the object sufficiently | ||
| 674 | The installed softw. comp. &1 &2 is not contained in the system info XML | The short text describes the object sufficiently | ||
| 675 | Deletion of incorrect product information: | The short text describes the object sufficiently | ||
| 676 | There was no incorrect product information to be deleted | The short text describes the object sufficiently | ||
| 677 | Registration of correct product information: | The short text describes the object sufficiently | ||
| 678 | Product version: &1 - "&2" | The short text describes the object sufficiently | ||
| 679 | Product instance: &1 &2 - "&3" | The short text describes the object sufficiently | ||
| 680 | Included product instance: &1 &2 - "&3" | The short text describes the object sufficiently | ||
| 681 | Lifecycle Management processes are locked by process &1 (LM tool &2) | Space: object requires documentation | ||
| 682 | Is assigned to technical usage &1 | The short text describes the object sufficiently | ||
| 683 | Software component &1 Release &2 is not installed | The short text describes the object sufficiently | ||
| 684 | The SP level &3, defined for component &1 rel.&2, could not be reached | Space: object requires documentation | ||
| 685 | The imported file does not contain a valid XML | Space: object requires documentation | ||
| 686 | Precondition type "&1" is unknown. A SPAM/SAINT Update is required... | The short text describes the object sufficiently | ||
| 687 | Package &1 has to be applied using the Software Update Manager (SUM) | The short text describes the object sufficiently | ||
| 688 | Currently runs an update process started by the Software Update Manager | Space: object requires documentation | ||
| 689 | Component &1 is already retrofitted into component version &2 rel.&3 | The short text describes the object sufficiently | ||
| 690 | R3trans data file &1 does not exist | The short text describes the object sufficiently | ||
| 691 | R3trans data file &1 is older than R3trans data file in EPS parcel &2 | The short text describes the object sufficiently | ||
| 692 | R3trans data file in EPS parcel &1 is older than R3trans data file &2 | The short text describes the object sufficiently | ||
| 693 | EPS parcel of &1 is too old. Upload new EPS parcel before implementation | The short text describes the object sufficiently | ||
| 694 | Use the Software Update Manager (SUM) to import the queue | Space: object requires documentation | ||
| 695 | Process component deletion requests of OCS Package &1 | The short text describes the object sufficiently | ||
| 696 | Component &1 is not installed -> deletion is not necessary | The short text describes the object sufficiently | ||
| 697 | The queue cannot be deleted or resetted | Space: object requires documentation | ||
| 698 | Component &1 successfully deleted | The short text describes the object sufficiently | ||
| 699 | The Correction Package &1 is obsolete and must not be imported | The short text describes the object sufficiently | ||
| 700 | File selection canceled | Space: object requires documentation | ||
| 701 | Error when reading file '&1' | Space: object requires documentation | ||
| 702 | File '&1' is not a CAR or SAPCAR archive | Space: object requires documentation | ||
| 703 | Unknown error when writing file '&1' | Space: object requires documentation | ||
| 704 | Software installed for decompression is obsolete | Space: object requires documentation | ||
| 705 | Could not find file '&1' | Space: object requires documentation | ||
| 706 | Error when accessing the decompression software | Space: object requires documentation | ||
| 707 | Error when executing decompression software | Space: object requires documentation | ||
| 708 | Unknown error when accessing decompression software | Space: object requires documentation | ||
| 709 | Decompression of file canceled | Space: object requires documentation | ||
| 710 | File &1 sent and decompressed | Space: object requires documentation | ||
| 711 | File &1 sent, decompressed, and then deleted | Space: object requires documentation | ||
| 712 | Installed software cannot process the archive | Space: object requires documentation | ||
| 713 | There is no decompression software installed on the application server | Space: object requires documentation | ||
| 714 | CAR error message: &1 &2 | Space: object requires documentation | ||
| 715 | Could not interpret profile parameter &1 | Space: object requires documentation | ||
| 716 | A final parenthesis is missing in &1 | Space: object requires documentation | ||
| 717 | No authorization to delete '&1' on the application server | Space: object requires documentation | ||
| 718 | An error occurred while deleting file '&1' on the application server | Space: object requires documentation | ||
| 719 | No authorization to write '&1' on the application server | Space: object requires documentation | ||
| 720 | An error occurred while saving file '&1' on the application server | Space: object requires documentation | ||
| 721 | No authorization to read '&1' on the application server | Space: object requires documentation | ||
| 722 | An error occurred while accessing the file selection | Space: object requires documentation | ||
| 723 | Could not determine detailed information for '&1' | Space: object requires documentation | ||
| 724 | Error when passing file '&1' from the front-end computer | Space: object requires documentation | ||
| 725 | Calculated file length does not match data sent | Space: object requires documentation | ||
| 726 | No response while accessing CAR (possible program termination) | Space: object requires documentation | ||
| 727 | File &1 sent and decompressed but not deleted | Space: object requires documentation | ||
| 728 | File too big; not sent | Space: object requires documentation | ||
| 729 | You do not have authorization to send file &1 from the front-end computer | Space: object requires documentation | ||
| 730 | SAPCAR does not support displaying the content of CAR archives | Space: object requires documentation | ||
| 731 | Unable to read table of contents of CAR/SAR archive &1 | Space: object requires documentation | ||
| 732 | Cannot disassemble to DIR_EPS_ROOT/in (see long text) | Space: object requires documentation | ||
| 733 | SAPCAR error: "&1" - You need a new SAPCAR version | The short text describes the object sufficiently | ||
| 734 | The RFC connection to Solution Manager is not configured correctly | The short text describes the object sufficiently | ||
| 735 | The RFC connection "&1" to Solution Manager does not work | The short text describes the object sufficiently | ||
| 736 | Component vector of system &1 is not defined in Solution Manager | The short text describes the object sufficiently | ||
| 737 | Component vector of system &1 is not up-to-date in Solution Manager | The short text describes the object sufficiently | ||
| 738 | Maintenance Optimizer in Solution Manager is not configured correctly | The short text describes the object sufficiently | ||
| 739 | The software component &1 rel.&2 is not registered in LMDB | The short text describes the object sufficiently | ||
| 740 | The software component &1 rel.&2 is registered in LMDB with version &3 | The short text describes the object sufficiently | ||
| 741 | The software component &1 rel.&2, registered in LMDB, is not installed | The short text describes the object sufficiently | ||
| 742 | Start options of subsequent modules were changed. Check them... | Space: object requires documentation | ||
| 743 | The start time is smaller than the current time. | Space: object requires documentation | ||
| 744 | Maximum start time is lower than given start time | Space: object requires documentation | ||
| 745 | The start options of the import modules are consistent. | Space: object requires documentation | ||
| 746 | Check and define the start options for the import modules. | Space: object requires documentation | ||
| 747 | Severe error while displaying uploaded packages | Space: object requires documentation | ||
| 748 | Not all parameters are modifiable; OCS queue is being imported | The short text describes the object sufficiently | ||
| 749 | There are inactive objects in the system | The short text describes the object sufficiently | ||
| 750 | There are inactive runtime objects in the ABAP Dictionary | The short text describes the object sufficiently | ||
| 751 | A status reset is not possible when using the parallel import mode | The short text describes the object sufficiently | ||
| 752 | The log file path points to a file outside of the allowed "log" directory | The short text describes the object sufficiently | ||
| 753 | Use the special Support Package Manager for &1 (see menu Environment) | Space: object requires documentation | ||
| 754 | Use the special Add-On Manager for &1 (see menu Environment) | Space: object requires documentation | ||
| 755 | Continue by using the special Support Package Manager for &1 | Space: object requires documentation | ||
| 756 | Continue by using the special Add-On Manager for &1 | Space: object requires documentation | ||
| 757 | System is running in tenant mode; only display functions available | Space: object requires documentation | ||
| 758 | No valid maintenance certificate found (see long text) | Space: object requires documentation | ||
| 759 | A valid maintenance certificate was found for system &1 | Space: object requires documentation | ||
| 760 | The language vector used for the export contains invalid languages: &1 | Space: object requires documentation | ||
| 761 | No queue calculation because of a missing maintenance certificate | Space: object requires documentation | ||
| 762 | The maintenance certificate check requires a kernel patch level >= 145 | Space: object requires documentation | ||
| 763 | Incomplete SAP ERP 6.0 EHP4 SR1 upgrade; read SAP Note 1370344 | Space: object requires documentation | ||
| 764 | Queue of test case &1 was successfully calculated | The short text describes the object sufficiently | ||
| 765 | Queue has software components with incompatible database requirements | Space: object requires documentation | ||
| 766 | Database requirement &1 is not fullfilled | The short text describes the object sufficiently | ||
| 767 | Incompatible database type requirement: &1 -> &2 vs. &3 -> &4 | The short text describes the object sufficiently | ||
| 768 | Support Package equivalency violation accepted by user &1 (&2 ,&3) | Space: object requires documentation |
History
| Last changed on/by | 20141031 | SAP | |
| SAP Release Created in | 800 |