/CFG/ACTIVATION -
The following messages are stored in message class /CFG/ACTIVATION: .
It is part of development package /CFG/ACTIVATION_TOOLS in software component SV-CLD-FRM-INF. This development package consists of objects that can be grouped under "Tools for Activation".
It is part of development package /CFG/ACTIVATION_TOOLS in software component SV-CLD-FRM-INF. This development package consists of objects that can be grouped under "Tools for Activation".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1 &2 &3 &4 |
| 001 | Error during determination of free resources for parallelization |
| 002 | Activation is starting sequentially |
| 003 | No package selected for processing |
| 004 | Background process could not be started (resource error) |
| 005 | Background process terminated with failure (subrc = &1) |
| 006 | Severe error in background process |
| 007 | Activation Request &1 not found |
| 008 | Wrong status &1 should be assigned to activation request &2 |
| 009 | No log handle provided |
| 010 | Activation error: Configuration entity &1 not supplied for IMG activation |
| 011 | Activation error: View &1 not found |
| 012 | Activation error: Table &1 not found |
| 013 | Activation error: Package contains multiple BC-Set's (&1 and &2) |
| 014 | Activation error: Must not swap external and internal BC set content (&1) |
| 015 | Activation error: Activty type &1 is not supported in IMG activation |
| 016 | Activation currently not possible due to parallel activation request (&1) |
| 017 | No data found for selection |
| 018 | Same package is returned multiple times (Endless loop in GET_NEXT) |
| 019 | BC Set &1 activated successfully |
| 020 | Activation started with Direct Write method |
| 021 | No Data to be written with Direct Write method |
| 022 | No Authorization for maintenance of &1 |
| 023 | Table &1 could not be written |
| 024 | Field &1 does not exist in table &2 |
| 025 | Transport for table &1 could not be written |
| 026 | Table &1 is not in whitelist |
| 027 | Entity &1 was activated successfully |
| 028 | Activity &1 is handled with Direct Write |
| 029 | Entity &1 activation failed |
| 030 | Value too long &1 |
| 031 | No eCATT supplied for activation |
| 032 | Activation History not written |
| 033 | Execution of ECATT &1 replaced by ABAP-Class &2 |
| 034 | Error writing log for class &1 |
| 035 | Activation History Timestamps not written |
| 036 | Activation status cannot be changed |
| 037 | Object &1 successfully activated |
| 038 | No object assigned to IMG activity &1 |
| 039 | Key field &1 of table &2 missing in NEXT record |
| 040 | Error writing the Activation Message Log |
| 041 | Error writing entries for Activation Message Log |
| 042 | Error writing the Activation History Log |
| 043 | Error writing entries for Activation History Log |
| 044 | No authorization to activate BC Set's |
| 045 | UUID generation error |
| 046 | See ECATT-Log: &1 |
| 047 | Illegal call of ECATT activation |
| 048 | Activation error in ECATT without message |
| 049 | BC-Set ID is initial |
| 050 | New Q2P is not switched on |
| 051 | X4 toggle is not switched on |
| 052 | BC-Set &1 does not exist |
| 053 | Error when determining BC-Set for table &1 and object type &2 |
| 054 | Error when accessing &1 (object type &2) |
| 055 | Error when accessing table &1 |
| 056 | Table &1 is not assigned to BC-Set &2 |
| 057 | Activation error: Empty mapping table |
| 058 | No transport requests available |
| 059 | Error when writing table /SMB/BB_TP_IN |
| 060 | File &1 does not exist |
| 061 | All packages are processed |
| 062 | Activation of an activity failed; Activation forced to stop |
| 063 | Field &1 of table &2 is not defined in view &3 |
| 064 | Activation error: Dataset is initial |
| 065 | Neither data element nor data type is supplied for field &1 |
| 066 | BC Set activity &1 is handled with Direct Write (Expert Mode) |
| 067 | Activity is skipped |
| 068 | Too many records provided |
| 069 | Same record must only be contained once |
| 070 | No entries found in table &1 for request &2 and activity &3 |
| 071 | No messages exists |
| 072 | No Content Items -> nothing to activate |
| 073 | Reactivation not possible |
| 074 | Direct Write as fallback for BC-Set &1, Table &2 |
| 075 | Direct Write not supported for number range objects |
| 076 | Job for Background user could not be started |
| 077 | Activation error: Please check ABAP log for details |
| 078 | Request unlocked by user &1 at &2 |
| 079 | AIM exists for object &1 and type &2 -> no direct write |
| 080 | &1 entries from table &2 deleted. |
| 081 | Simulation mode: No database changes |
| 082 | Error when calling BC Set &1 |
| 083 | eCATT &1 must be replaced by ABAP class |
| 084 | Activity &1 not found in sequence |
| 085 | Scope Item not defined for activity &1 |
| 086 | Building Block not defined for activity &1 |
| 087 | Wrong number of activities in sequence |
| 088 | Activity &1 could not be written from next to previous |
| 089 | Adapter class &1 found for processing staging data |
| 090 | Activation adapter: Activation not allowed |
| 091 | Activation adapter: Activation allowed |
| 092 | Activation adapter: Pre-processing failed. |
| 093 | Activation adapter: Pre-processing successful |
| 094 | Hash key couldn't be generated for Handling of Non transportable objects |
| 095 | Activation adapter: Post-processing failed. |
| 096 | Activation adapter: Post-processing successful. |
| 097 | Duplicate records provided. Activation history not written. |
| 098 | Staging with ID &1 does not exist |
| 099 | Adapter class found for input Dataset |
| 100 | &1 could not be activated. |
| 101 | Adapter class &1 does not exist |
| 102 | Adapter class &1 is not assigned to interface &2 |
| 103 | An activation is already running |
| 104 | Error during creation of structure for object &1. |
| 105 | Field &1 is not within the view &2 and will be ignored. |
| 106 | Language &1 is not available in the system. |
| 107 | Maintenance view is obsolete. Please use transaction &1 |
| 108 | eCATT &1 is excluded from processing |
| 109 | &1 could not be uploaded |
| 110 | Master List could not be generated |
| 111 | Overall Activity list of Activation sequence already exists |
| 112 | &1 entries created for Activity master sequence |
| 113 | TRKEY &1 has values too long for database fields: &2 = '&3' |
| 114 | Error during Record determination. |
| 115 | Resequencing exclusion list (&1 entries) with interval &2 |
| 116 | Successfully resequenced exclusion list. |
| 117 | Saving exclusion list to database |
| 118 | Error while saving exclusion list to database |
| 119 | Exclusion list was updated |
| 120 | Adding &1 entries to tranport request |
| 121 | Successfully saved updated exclusion list |
| 122 | Could not add Objects to Transport &1 |
| 123 | View &1 is already defined in exclusion list and will be skipped. |
| 124 | Adding &1 entries to exclusion list with type &2. Simultation: &3. |
| 125 | View &1 is not in master list; searching for customizing object. |
| 126 | Could not find any customizing object for view &1. View will be skipped. |
| 127 | Determining Master Sequence |
| 128 | Error: Cannot add View &1 to special block in exclusion list |
| 129 | Successfully added View &1 |
| 130 | Start adding Views to exclusion list |
| 131 | Could not add view &1. Resequencing needed. |
| 132 | Sequencing Error --> View &1 could not be added to exclusion list |
| 133 | Simulation: Changes are not saved! |
| 134 | &1 is no view or does not exist. |
| 135 | Table is already locked by another user. |
| 136 | Object &1 of Type '&2' is not allowed to be added to exclusion list. |
| 137 | Adding Object &1; SI-Seq &2; BB-Seq &3; ACT-Seq &4 |
| 138 | View &1 was skipped by User. |
| 139 | Multiple Customizing Objects found for view &1. |
| 140 | There is no view left to add. |
| 141 | User chose Customizing Object &1. |
| 142 | Could not find Object &1 in Master Sequence List. View &2 will be skipped |
| 143 | Starting AIM &1 of Object &2. |
| 144 | You are not authorized to use transaction &1 |
| 145 | Incorrect selection parameters for date and/or time |
| 146 | View &1 |
| 147 | Old assignment: SI sequence &1, BB sequence &2, Act sequence &3 |
| 148 | New assignment: SI sequence &1, BB sequence &2, Act sequence &3 |
| 149 | User did not select a customizing object. View &1 will be skipped. |
| 150 | Assignment of view to sequence in old master list not found |
| 151 | Assignment of view to sequence in new master list not found |
| 152 | Old assignment: SI &1, BB &2, Activity &3, &4 |
| 153 | New assignment: SI &1, BB &2, Activity &3, &4 |
| 154 | Identical assignment in new master not found for view as in old list |
| 155 | Popup suppressed: Searching all customizing objects (&1) in master list. |
| 156 | Searching for customizing object &1 Type &2. |
| 157 | &1 found with SI: &2; BB: &3, Act: &4 |
| 158 | Could not find objects in master list. View &1 will be skipped. |
| 159 | No authority to execute the report |
| 160 | Please enter one parameter |
| 161 | 1st entered parameter is used for selection |
| 162 | No entry found in activation history for activity &1 |
| 163 | No entry found in activation history for ABAP class &1 |
| 164 | No entry found in activation master list for type &1 and Id &2 |
| 165 | No entry in activation-history for request &1 |
| 166 | Error when calling RFC &1: &2&3&4 |
| 167 | Start processing of AIM &1 |
| 168 | End processing of AIM &1 |
| 169 | AIM is executed for object &1 and type &2 |
| 170 | AIM is executed for activity &1 |
| 171 | Error occured during formatting Data of TRKEY &1 (&2) |
| 172 | BAdI implementation class &1 is called |
| 173 | Runtime of BAdI implementation: &1 seconds |
| 174 | The following messages were raised by the BAdI implementation |
| 175 | Error raised during BAdI execution. Create incident on component &1 |
| 176 | Error raised during BAdI execution. Contact owner of class &1 |
| 177 | Exception occured during execution of BAdI implementation &1: |
| 178 | Instance for application log does not exist |
| 179 | No data found for selection criteria |
| 180 | No message for backsync to CBC found |
| 181 | Staging ID &1 was already previously activated with request &2 |
| 182 | User &1 is submitting activation job for staging ID &2 with scope '&3' |
| 183 | Could not retrive Batch User. User name changed to current user: &1. |
| 184 | Error &2 occurred during creation of activation job &1 |
| 185 | Error &3 occurred during submit of activation job &1 with job number &2 |
| 186 | Activation job &1 scheduled with job number &2 |
| 187 | Activation Request &1 created for Staging ID &2. |
| 188 | Error during creation of Activation Request |
| 189 | Creating Activation Request |
| 190 | No staging ID specified |
| 191 | Activation of staging &1 completed with request ID &2 |
| 192 | Server Group 'parallel_generators' could not be found. |
| 193 | Could not initialize server group. RC: &1 |
| 194 | Could not exlcude Server &1 from processing. RC: &2 |
| 195 | Successfully excluded Server &1 from further Activation Processing. |
| 196 | Activities will be processed on application server group '&1' |
| 197 | Activities will be processed on application server &1 with group '&2' |
| 198 | Activity &1 started on Server &2. |
| 199 | &3 of &1 provided languages have been filtered out |
| 200 | BC-Set &1 does not exist with Staging ID &2. |
| 201 | BC-Set ID can not be empty when calling Re-Activation Mode. |
| 202 | Reactivation not possible for update/upgrade content |
| 203 | Could not determine previous request |
| 204 | Re-Execute AIM &1 started at &2 |
| 205 | You are not authorized to activate the staging |
| 206 | eCATT &1 with BCSID &2 is excluded from processing. |
| 207 | Test ABAP replacement class |
| 208 | Error when calling RFC &1: &2&3&4 |
| 209 | Processing was successful |
| 210 | Creating Activation Request with Parameters: |
| 211 | Scope: &1; User: &2; |
| 212 | Lang Filter: &1; Customizing Request: &2; |
| 301 | Entry could not be inserted in table &1 |
| 302 | Entry could not be updated in table &1 |
| 303 | Data inconsisteny in table &1 |
| 304 | Activation stop is not requested in client &1 |
| 305 | BCP-Component couldn't be determined |
| 306 | Ticket can only be created if error-messages exist in log |
| 307 | Could not load actviation config data |
| 308 | Could not load activation queue id |
| 309 | No authorization to stop the activation in client &1 |
| 310 | No authorization to release the activation in client &1 |
| 311 | Activation stop is already requested in client &1 |
| 312 | Activation has been stopped with comment: "&1&2&3&4" |
| 313 | Tech Error: Activation Queue could not be unlocked in client &1 |
| 314 | Tech Error: Activation of queue &1 could not be restarted (client &2) |
| 315 | Tech Error: Activation for solution &1 could not be restarted (client &2) |
| 316 | Activation is stopped in client &1 |
| 317 | Activation is not stopped in client &1 |
| 318 | Stop request has to be triggered in client 000 |
| 319 | No RFC-destination maintained for client &1 |
| 320 | Technical error during RFC to client &1 (Calling user &2) |
| 321 | Activation stop successfully requested in client &1 |
| 322 | Activation-Stop could not be deleted in client &1 |
| 323 | Activation-Stop successfully removed in client &1 |
| 324 | No authorization to release the activation stop |
| 325 | Activation is stopped by external Stop request |
| 326 | Activation &1 is running (Solution &2, Start date: &3 ) |
| 327 | &1 entries in table /smb/bb_tp_in |
| 328 | No entries in table /smb/bb_tp_in |
| 329 | Entry in table /smb/bb_tp_in is for wrong user ( &1 ) |
| 330 | Entry &1: &2 |
| 331 | Transport request not specified |
| 332 | Default value for "Error-Handling" is used |
| 333 | Default Value for "Activation-Mode" is used |
| 334 | Activities of type &1 can't be processed by direct write |
| 335 | Activation-mode is "no direct write" |
| 336 | Objects of type "transaction" are always processed by direct write |
| 337 | Activity is in exclusion list for direct write |
| 338 | Cross-Client Tables can't be processed by direct write |
| 339 | Objects of type &1 can't be processed by direct write |
| 340 | View events exist for object &1 -> no direct write |
| 341 | Activation-mode is "determine direct write" |
| 342 | BC-Sets will not be processed with direct write |
| 343 | ABAP adapter given by caller |
| 344 | ABAP adapter determined by eCATT replacement mapping table |
| 345 | Activity &1 does not exist; eCATT &2 is not replaced |
| 346 | No direct write for tables of delivery-class 'G' |
| 347 | No direct write as object &1 of type &2 has been modified |
| 348 | Not possible to determine whehter object &1 type &2 has been modified |
| 349 | Activity &1 can't be processed by direct write |
| 350 | Only Client is table key in table &1 -> no direct write |
| 351 | Special handling for Object &1 -> always direct write |
| 352 | Activity &1 is assigned to several building blocks |
| 353 | Incomplete Message: MSGID '&1' MSGTY '&2' MSGNO '&3' |
| 354 | No direct write for tables of delivery-class 'A' |
| 355 | Status of queue for solution &1 running, but failed (Start date: &2) |
| 356 | Activity &1 (type &2) is currently activated for SI &3 and BB &4 |
| 357 | Last activated activity: &1 (type &2) |
| 358 | Building Block &1 is assigned to component &2 |
| 359 | Not a CCP Client. Customer Conversion Not Possible |
| 360 | No activation is running |
| 361 | Error when determining current activation |
| 362 | No authorization to abort activation job in client &1 |
| 363 | Status of Activation queue could not be changed |
| 364 | Activation job &1 (Name &2) is aborted in client &3 |
| 365 | Activation queue status has been changed to 'Interrupted' |
| 366 | Activation stop successfully set in client &1 |
| 367 | Activation semaphore deleted |
| 368 | Start process: Kill activation job |
| 369 | No activity found in pre-staging content for staging ID &1 |
| 370 | LCP cannot be released. |
| 371 | Scope of Activation: &1, old status of activity: &2 -> activity skipped |
| 372 | SAP internal development system: no Activation stop is needed. |
| 373 | No LCP was created |
| 374 | Activation Trigger set to '&1'. |
| 375 | Activation request &1 is set to interrupted |
| 376 | Trigger determinator: &1 |
| 377 | Scope Table Entries: &1 |
| 378 | Staging Rows Scope Information: &1; Staging Rows scoped IMGs: &2 |
| 379 | No new Scope Information |
| 380 | Error: Could not insert into START_A_PR_ACTIV |
| 381 | Added &1 lines to START_A_PR_ACTIV |
| 400 | Error |
| 401 | Record not found in DB. |
| 402 | Could not get read-BO instance. |
| 403 | Could not read cells of record via its read-BO. |
| 404 | Context Component not found |
| 405 | Could not determine cusotmizing activity for &1 |
| 406 | Could not determine img activity for &1 |
| 407 | Could not determine Base Table records for view &1 |
| 408 | Unable to generate View Record ID for &1 |
| 409 | Check Join Condition for &1 |
| 410 | No Join Conditions found for &1 |
| 411 | No Base Table found for &1 |
| 412 | Object Type not specified for &1 |
| 413 | No content sent to BC-API for &1 |
| 414 | Activation Error: Tablename in Staging Data is initial for activity &1. |
| 415 | Activation Error: TRKEY Is initial for Table &1 in Activity &2. |
| 416 | Staging ID &1 does not exist. |
| 417 | Activity ID does not exist. |
| 418 | No data to display |
| 419 | Country/region ZZ is reserved for Overall Sequence file. |
| 420 | There is no country/region &1. |
| 421 | For Overall sequence file the country/region should be ZZ. |
| 422 | File for country/region &1 already exist. |
| 423 | File for country/region &1 successfully uploaded. |
| 424 | There is no Overall sequence file. |
| 425 | File for Overall sequence successfully saved. |
| 426 | File for Overall sequence already exist. |
| 427 | Authorization missing to execute the report. |
| 428 | Processed country/region &1 |
| 429 | Number of processed Scope Items &1 |
| 430 | Number of processed Building Blocks &1 |
| 431 | Number of processed Activities &1 |
| 432 | Number of country/region records for Overall sequence &1 |
| 433 | Activation of scope dependent technical objects completed. |
| 434 | No message for Staging log. |
| 435 | Activation request ID &1 is different from expected value &2 |
| 436 | Exception occurred during activation of request ID &1 |
| 437 | Click on the distinct errors or warnings to display details |
| 438 | &1 logs found between &2 and &3 |
| 439 | The activation status has been updated. |
| 440 | There are no Activation Requests for Staging ID &1. |
| 441 | The latest Activation Request should not be manually unlocked. |
| 442 | Backsynch is not possible when the latest Activ. Request still running. |
| 443 | The latest Activation Request has Initial status. |
| 444 | The request can not be unlocked because Active job exists. |
| 445 | Activation of staging &1 with request ID &2 returned request ID &3 |