TN_PROCESS - Nachrichtenklasse f�r OCS �nderungsprozesse
The following messages are stored in message class TN_PROCESS: Nachrichtenklasse f�r OCS �nderungsprozesse.
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 | Method &1 of abstract class &2 must be redefined |
| 001 | Could not create the log |
| 002 | Actual parameter &1 is not filled |
| 003 | Entry of log &1 could not be saved |
| 004 | Deletion Package &1 could not be created |
| 005 | Software component &1 Release &2 is not installed |
| 006 | Uninstalling software component &1 Release &2 (&3, &4) |
| 007 | &1: &2 - Deletion Package for &3 rel. &4 |
| 008 | Deletion Package &1 exists already |
| 009 | Deletion Package &1 successfully created |
| 010 | Dependent packages exists for &1 rel. &2. |
| 011 | Transport request &1 does not exist |
| 012 | Objects with customer modifications were found |
| 013 | The queue cannot be read from the tp buffer |
| 014 | The queue is not empty |
| 015 | OCS Package &1 does not have type &2 |
| 016 | Package type &1 is not supported |
| 017 | Serious inconsistency |
| 018 | The given phase "&1" does not match the current process phase "&2" |
| 019 | Error while deleting software component &1 rel. &2 |
| 020 | Note corrections are needed |
| 021 | The implementing class for phase &1 is missing |
| 022 | Error while calling transport tool tp |
| 023 | There are objects, which are still used |
| 024 | Error while creating the transport request &1 |
| 025 | Error while copying objects into transport request &1 |
| 026 | Error while sorting and compressing the object list &1 |
| 027 | Package &1 has the not allowed statue &2 |
| 028 | The check for locked objects aborted |
| 029 | The object list of package &1 could not be read |
| 030 | The current phase &1 is not part of the process &2 (in class &3) |
| 031 | The Deletion Package &1 could not be exported |
| 032 | The Deletion Package &1 could not be imported |
| 033 | The transport tools tp/R3trans could not establish a database connection |
| 034 | Unknown message with: &1 &2 &3 &4 |
| 035 | Unknown workbench type: &1 &2 &3 |
| 036 | Unknown change process type &1 |
| 037 | Uninstallation starts with phase &1 ( &2 ) |
| 038 | Uninstallation is continued in phase &1 ( &2 ) |
| 039 | Test uninstallation of add-on &1 Release &2 (&3, &4) |
| 040 | Set status of Deletion Package &1 to '&2' |
| 041 | Add-on uninstallation queue was confirmed |
| 042 | Confirm the Deletion Package &1 |
| 043 | Add-on &1 Release &2 was successfully uninstalled (&3, &4) |
| 044 | The Where Used list could not be determined |
| 045 | Parameter &2 is missing or initial (&1) |
| 046 | Error during coying the object list |
| 047 | Error during optimizing the object list |
| 048 | Uninstalling add-on &1 Release &2 (&3, &4) |
| 049 | The import of the queue aborted with rc &1 |
| 050 | OCS Package &1 could not be added to the tp buffer (rc: &2) |
| 051 | OCS Package &1 could not be modified in the tp buffer (rc: &2) |
| 052 | There are not further information concerning OCS process error &1 |
| 053 | Information of OCS process error &1 could not be saved |
| 054 | The OCS import process is aborted in phase &1. |
| 055 | The import step "&1" finished with error for &2 |
| 056 | The import log could not be read |
| 057 | The Deletion Package for Add-On &1 rel.&2 could not be created. |
| 058 | Resuming uninstallation of add-on &1 Release &2 (&3, &4) |
| 059 | Confirming uninstallation of add-on &1 Release &2 (&3, &4) |
| 060 | Uninstallation note &1 was read by user &2 |
| 061 | The deletion of objects of other software components is not allowed |
| 062 | There are objects in the object list, which cannot be deleted |
| 063 | The deletion piecelist contains objects with wrong object information |
| 064 | The white list of allowed objects has to be defined unambiguously. |
| 065 | Install at least tp version &1 and R3trans version &2 |
| 066 | The object list contains not deletable and modified objects |
| 067 | Object &1 &2 &3 was resolved and deleted from the object list |
| 068 | Sub object &1 &2 was aggregated into the main object &3 &4 |
| 069 | The following objects cannot be deleted: |
| 070 | The following objects belong also to a foreign software component: |
| 071 | The process was aborted due to an error |
| 072 | The editor transaction for the using object &1 is unknown |
| 073 | The editor transaction for the used object &1 is unknown |
| 074 | Add-on &1 Release &2 is not flagged as uninstallable |
| 075 | Uninstallation of &1 Release &2 requires at least SPAM/SAINT version &3 |
| 076 | Kernel release is too low (current: '&1', required: '&2') |
| 077 | The following imported OCS Packages require component &1 rel.&2: |
| 078 | The process status could not be set |
| 079 | The attribute &1 does not contain a value |
| 080 | Perform own checks and actions of Add-On &1 |
| 081 | Parameter &1 of method &2 of class &3 is initial |
| 082 | Plugin class &1 does not exist (see SAP Note &2) |
| 083 | The Add-On specific action (plugin method &1) finished with errors |
| 084 | Add-on &1 states that it cannot be uninstalled |
| 085 | The Add-On specific action (plugin method &1) finished with warnings |
| 086 | The Add-On own plugin class &1 could not be instantiated |
| 087 | The Add-On &1 does not provide own checks or actions |
| 088 | The Add-On does not provide an implementation for action "&1" |
| 089 | The call of method &1 (class &2) finished with error "&3" |
| 090 | Messages of the Add-On specific action (plugin method &1): |
| 091 | Data could not be written into table &1 |
| 092 | Attribute &1 with value "&2" was created |
| 093 | Method &1=>&2 (required for uninstallation) does not exist (see Note &3) |
| 094 | The class &1 does not exist |
| 095 | The method &1 does not exist |
| 096 | The Add-On own plugin class &1 was successfully instantiated |
| 097 | The Add-On specific action (plugin method &1) finished without errors |
| 098 | The call of method &1 finished with error "&2" |
| 099 | The plugin class &1 belongs to the application component &2 |
| 100 | &1&2&3&4 |
| 101 | Attribute &1 of package &2 does not contain a value |
| 102 | Add-on-specific checks for uninstallation |
| 103 | Export checks and actions for transport based correct. instructions (TCI) |
| 104 | The number of objects &1 differs from the number of requests &2 |
| 105 | The following object entries are missing in the transport request: |
| 106 | TCI &1: &2 &3 &4 |
| 107 | Export checks and actions finished without errors |
| 108 | Export checks and actions finished with errors |
| 109 | Missing key entries for TCI &1 and object &2 &3 &4 |
| 110 | Table key: &1 |
| 111 | There are profiles and/or roles, which are still used |
| 112 | Transport object entries are missing for the transport based corrections: |
| 113 | Transport based correction instruction (TCI): &1 |
| 114 | Objectlist entries are missing for the following transport based corr.: |
| 115 | &1 &2 is used by &3 &4 |
| 116 | Postprocessing for transport based correction instruction (TCI) |
| 117 | Postprocessing for transport based corrections finished without errors |
| 118 | Postprocessing for transport based corrections (TCI) finished with errors |
| 119 | Error while writing the data to database table &1 |
| 120 | The following objects could not be checked whether they are deletable |
| 121 | The following transport based corr.(TCI) are not completely imported yet: |
| 122 | Error while deleting transport request &1 |
| 123 | Object &1 &2 is used by &3 &4 |
| 124 | No update / upgrade process found |
| 125 | Object &1 &2 &3&4 will remain in the system |
| 126 | Objects of transport request &1 were taken over |
| 127 | The restore is continued in phase &1 ( &2 ) |
| 128 | Import prerequisite for deletion package &1 was created (&2) |
| 129 | Object &1 &2 &3&4 does not exist in the system |
| 130 | Transport object CPKM for TCI &1 could not be found |
| 131 | File &1 for Correction Package &2 could not be found |
| 132 | Package &1 could not be found in the EPS inbox |
| 134 | A SMODILOG entry for &1 exists already |
| 135 | Extended attribute CP_NOTE_CORR was not found for &1 |
| 136 | No transport based correction instruction (TCI) for &1 found in note &2 |
| 137 | The Note Assistant is not up-to-date. Please follow SAP note 1995550. |
| 138 | SMODILOG for transport based corr. instr. &1 from SAP note &2 created |
| 139 | The restore is started in phase &1 ( &2 ) |
| 140 | The following stop points were defined (&1, &2): |
| 141 | Deletion of object &1 &2 may lead to data loss in &3 &4 |
| 142 | Stop point '&1' was reached on &2 at &3 |
| 143 | The Add-On &1 provides the plugin class &2 |
| 144 | &1 uninstallation: Revert former SAP_BASIS objects |
| 145 | Version of the to be uninstalled Add-On &1 does not match the stack XML |
| 146 | The Stack XML does not contain any Add-On uninstallation for this system |
| 147 | The Stack XML contains not only Add-On uninstallations |
| 148 | The Stack XML contains also Add-On uninstallations |
| 149 | The Stack XML contains only Add-On uninstallations for this system |
| 150 | &1: Execution in dialog |
| 151 | &1: Continue manually |
| 152 | &1: Execute immediately in background |
| 153 | &1: Schedule in background |
| 154 | Start date: &1 time: &2, latest execution &3, &4 |
| 155 | Implement SAP note 2569813 before you release workbench request &1 |
| 156 | Error when activating "Concurrent Version Online Import" |
| 157 | Error when activating "Cooldown" phase of "CV Online Import" |
| 158 | Check the CVOI log with report &1 |
| 159 | Deletion package &1 does not need to be disassembled |
| 160 | Test uninstallation of add-on &1 Release &2 was successful (&3, &4) |
| 161 | Component &1 can only be uninstalled with the SUM tool. |
| 162 | Confirmation of successful uninstallation of add-ons (&1, &2) |
| 163 | Confirmation of successful test uninstallation of add-ons (&1, &2) |
| 164 | &1: &2 - Transport based correction instruction (TCI) for &3 rel.&4 |
| 165 | The restore is done for the following queue: |
| 166 | Create cofile for &1... |
| 167 | Combined Installation and Uninstallation (&1, &2) |
| 168 | Confirm the Combined Installation and Uninstallation (&1, &2) |
| 169 | Combined Add-On Installation / Uninstallation queue was confirmed |
| 170 | Initial state of the Stack XML does not match the system |
| 171 | Component &1 &2 exists in Stack XML, but not in the system |
| 172 | Component &1 &2 exists in the system, but not in the Stack XML |
| 173 | Confirm the combined test installation and test uninstallation (&1, &2) |
| 174 | Test installation of Add-On &1 rel.&2 was successful (&3, &4) |
| 175 | Combined test installation and test uninstallation (&1, &2) |
| 176 | R3trans version is too old, patch collection 1/2018 or newer is needed |
| 177 | The generation of CRM runtime objects could not be locked |
| 178 | Error message of CRM method &1: |
| 179 | The generation of CRM runtime objects was successfully locked |
| 180 | The generation of CRM runtime objects could not be unlocked |
| 181 | The generation of CRM runtime objects was successfully unlocked |
| 182 | Replication and inbound queues could not be stopped |
| 183 | Replication and inbound queues were successfully stopped |
| 184 | Basic CRM customizing is missing -> CRM specific actions are not possible |
| 185 | Execute report &1 to set the basic customizing |
| 186 | Conversion of BDoc messages is not necessary |
| 187 | Conversion of BDoc messages is necessary |
| 188 | Replication queues could not be started |
| 189 | Inbound queues could not be started |
| 190 | Replication and inbound queues were successfully started |
| 191 | Generation of CRM runtime objects was successfully scheduled |
| 192 | The generation of CRM runtime objects must be scheduled |
| 193 | Adjustment of CRM repository changes is necessary |
| 194 | Adjustment of CRM repository changes is not necessary |
| 195 | Adjustment of BDoc messages is not necessary |
| 196 | Adjustment of BDoc messages is necessary |
| 197 | Status of inconsistent BDoc messages could not be determined |
| 198 | Problems occurred during disassembling the OCS packages of the queue |
| 199 | "SAP intern" mode is switched on -> Phase "&1" is skipped |
| 200 | All parameters have to be set |
| 201 | Import preconditions are ignored for the Add-On: &1 &2 |
| 202 | The provided keyword / Add-On combination is invalid |
| 203 | The check of import preconditions remains active |
| 204 | The system must not be used productively |
| 205 | There is a queue for a different tool defined |
| 206 | There is no valid AVERS entry for Add-On &1 rel.&2 |
| 207 | The Add-On &1 rel.&2 is already marked as '&3' |
| 208 | Tables for object &1 &2 &3 not found, object will be ignored |
| 209 | Safe Online Import of the current OCS Queue (&1, &2) |
| 210 | The import starts in phase &1 ( &2 ) |
| 211 | The import is continued in phase &1 ( &2 ) |
| 212 | Safe Online Import of the current queue is not finished yet |
| 213 | The current queue is not defined for the Safe Online Import |
| 214 | The Safe Online Import queue was confirmed |
| 215 | Package &1 is not capable for CVOI, import scenario "&2" is not allowed |
| 216 | The stack XML does not contain any data |
| 217 | CVOI test activation failed, import scenario "&1" is not possible |
| 218 | The technical prerequisites to download signed SAP notes are missing |
| 219 | The configuration for downloading signed SAP notes does not exist |
| 220 | The configuration for downloading signed SAP notes is incorrect |
| 221 | The RFC communication to the SAP backbone is not allowed anymore |
| 222 | HTTP(S) communication is only supported with implemented SAP note 2928592 |
| 223 | The RFC connections to the SAP backbone (&1) do not use a S-user |
| 224 | Installed component version &1 &2 is greater than the target version &3 |
| 225 | Import into a MT tenant system stopped in tp step "MOVE NAMETABS" |
| 226 | New shared container tables are already used |
| 227 | New shared container tables are not used yet |
| 228 | -> Execute the tp step "MAIN IMPORT" |
| 229 | At least Basis Support Package &1 must already be implemented |
| 230 | Object type &1 is not deletable in Basis release &2 |
| 231 | Archive &1 does not contain OCS packages or notes, it's not extracted |
| 232 | Exception SYSTEM_FAILURE was thrown during the remote call |
| 233 | Exception COMMUNICATION_FAILURE was thrown during the remote call |
| 234 | Insufficient ressources available for parallel execution |
| 235 | The import of the queue is not finished yet |
| 236 | The object list contains objects, which belong to customer namespaces |
| 237 | The object &1 &2 &3 belongs to the customer namespace &4 |
| 238 | The object list &1 contains more than 999999 objects |
| 239 | Open V3 update and data extraction requests are ignored |
| 240 | V3 update and data extraction request check is switched off |
| 241 | The queue contains only OCS Packages of uncritical components |
| 242 | Extracted file: &1 |
| 243 | Content of SWCV &1 &2 cannot be determined, simulation is not possible |
| 244 | SAPCAR archives could not be unpacked |
| 245 | Skip the error and finish the phase '&1' (&2, &3) |
| 246 | Check the consistency between tp buffer and OCS queue (&1, &2) |
| 247 | The tp buffer is consistent with the OCS queue |
| 248 | The tp buffer is not filled yet; check is not necessary |
| 249 | Check for open V3 update and LO data extraction requests (&1, &2) |
| 250 | There are objects with an undefined uninstallation handling |
| 251 | Objects of deletion package &1: |
| 252 | There are results of the uninstallation simulation |
| 253 | Confirmation of the uninstallation simulation (&1, &2) |
| 254 | The queue of the uninstallation simulation was confirmed |
| 255 | Simulation of the uninstallation with the current OCS queue (&1, &2) |
| 256 | The simulation starts with phase &1 ( &2 ) |
| 257 | The simulation is continued in phase &1 ( &2 ) |
| 258 | Uninstallation simulation (&1, &2) |
| 259 | The uninstallation simulation of add-on &1 rel.&2 was successful (&3, &4) |
| 260 | Test of customer initiated uninstallation of Add-On &1 rel.&2 (&3, &4) |
| 261 | Customer initiated uninstallation of Add-On &1 rel.&2 (&3, &4) |
| 262 | The queue contains only uncritical OCS packages; check is not necessary |
| 263 | There are no open V3 update and data extraction requests |
| 264 | There are open requests of application "&1" in the V3 update queue |
| 265 | There are open requests of application "&1" in the RFC queue |
| 266 | There are open requests of application "&1" contained in setup tables |
| 267 | The following transport based corr. (TCI) were not transported correctly: |
| 268 | Table &2 does not contain any entries for TCI &1 |
| 269 | Transport &1 is not assigned to an OCS Package |
| 270 | OCS Package &1 has not been imported yet |
| 271 | OCS Package Queue (ID: &1) was imported without a Stack XML |
| 272 | The queue is empty. Deferring a queue is not necessary |
| 273 | The queue belongs to the platform layer. Deferring it is not allowed |
| 274 | The queue belongs to the Add-On layer. Deferring it is allowed |
| 275 | The queue belongs to an unknown layer. Deferring it is not allowed |
| 276 | Resilience functionality is not active; deferring a queue is not allowed |
| 277 | Active queue ID "&1" does not correspond to the deferred queue ID "&2" |
| 278 | Queue ID "&1" is not a deferred queue |
| 279 | The queue is compatible to the deferred queue |
| 280 | OCS package queue &1 is not contained in the deferred queue |
| 281 | There is no deferred queue |
| 282 | The queue is not compatible to the deferred queue |
| 283 | The queue was restored and cannot be reset |
| 284 | Deferring the queue finished with an error |
| 285 | A queue is defined. Restoring a deferred queue is not allowed |
| 286 | There is no queue defined |
| 287 | Deferring the current queue (&1, &2) |
| 288 | Restoring the deferred queue finished with an error |
| 289 | Restoring the deferred queue with ID &3 (&1, &2) |
| 290 | The queue contains the OCS packages of the deferred queue with ID &1 |
| 291 | System runs in a multi tenency setup. Deferring a queue is not allowed |
| 292 | Event handler is not unique (FM &1 and class &2 are defined) |
| 293 | Event handler is not defined (no FM and no class is defined) |
| 294 | Plugin class &1 is inconsistent and could not be instantiated |
| 295 | OCS Package &1 cannot be assigned to an imported OCS Package queue |
| 296 | There is no usable Inst. / Upg. Package available for Add-On &1 rel.&2 |
| 297 | Software component &1 is already created as customer own component |
| 298 | Queue contains OCS packages (&1, &2) with different MT content types |
| 299 | Tenant Only import -> no action necessary |
| 300 | The check of the classifications, provided by the plugin, failed |
| 301 | Line &1: Field &2 is not filled |
| 302 | Line &1: Only the operations 'D' and 'I' are allowed |
| 303 | Line &1: Object type 'TABU' can only be used with a table key |
| 304 | Line &1: Table keys can only be used with the object type 'TABU' |
| 305 | Line &1: Wildcards are not allowed in field &2 |
| 306 | Line &1: The wildcard can only be used right bounded |
| 307 | Entry &1 &2 &3 &4 is ignored (no generic entry exists) |
| 308 | Entry &1 &2 &3 &4 is ignored (conflict with a central entry) |
| 309 | Calculation of the content of deletion piecelist &1 for &2 rel. &3 |
| 310 | Entries of table &1 with the following keys remain in the system: |
| 311 | Key: &1&2&3 |
| 312 | Started from system/tool &1 for XML file '&2&3&4' |
| 313 | OCS package &1 requires at least HANA version &2 |
| 314 | OCS package &1 requires HANA version &2 |
| 315 | The Add-On check found at least one error |
| 316 | Error occurred while accessing the gCTS repository functions |
| 317 | &1 partner add-ons are installed; further installations are not possible |
| 400 | Name of the Add-On component &1 has more than 10 characters |
| 401 | No software component was given |
| 402 | No release for software component &1 was given |
| 403 | No AVERS entry for software component &1 found |
| 404 | No AVERS entry for software component &1 release &2 found |
| 405 | Software component &1 rel. &2 exists already, insert is not possible |
| 406 | Software component &1 rel. &2 does not exist, update is not possible |
| 407 | Insert in table AVERS_EXT for component &1 rel. &2 failed |
| 408 | Update in table AVERS_EXT for component &1 rel. &2 failed |
| 409 | No software component versions for upgrade mode &1 found |
| 410 | Upgrade mode &1 is not supported |
| 411 | Provide a stack XML or a path to a stack XML file |
| 412 | The system info XML was not saved |
| 413 | The system info XML could not be saved on the frontend PC |
| 414 | The rendering of the system info XML was aborted with an error |