| SMOE_MESSAGE250 |
Internal table &1 is not assigned |
| SMOE_MESSAGE251 |
Internal table &1 is initial |
| SMOE_MESSAGE252 |
Object does not exist in database |
| SMOE_MESSAGE253 |
Action cancelled by user |
| SMOE_MESSAGE254 |
Extract not possible for inactive sites. Automatic extract on activation |
| SMOE_MESSAGE255 |
For publ. &1 with key &2 corres. repl. obj. not found. See note 495807 |
| SMOE_MESSAGE256 |
Repl. obj. del. or of wrong type for publ. &1 (key &2). See note 495807 |
| SMOE_MESSAGE257 |
Repository inconsistency: Replication object with SHORT_ID &1 missing |
| SMOE_MESSAGE258 |
Object type unknown. Object cannot be created in Administration Console |
| SMOE_MESSAGE259 |
Deletion of &1 cannot be performed: Object not found (already deleted?) |
| SMOE_MESSAGE260 |
Error: No scheduling dates |
| SMOE_MESSAGE261 |
Error: Illegal scheduling interval: End date is before start date |
| SMOE_MESSAGE262 |
Error: Scheduling date lies in the past |
| SMOE_MESSAGE263 |
Error: Scheduling: No site specified |
| SMOE_MESSAGE264 |
Error: Scheduling: Site does not exist |
| SMOE_MESSAGE265 |
Error: Scheduling: Destination site does not exist |
| SMOE_MESSAGE266 |
Error: Scheduling: Destination site has a different site type |
| SMOE_MESSAGE267 |
Error: Scheduling: No actions specified |
| SMOE_MESSAGE268 |
Error: Others: Internal error while processing scheduling data (&1) |
| SMOE_MESSAGE269 |
Combination of criteria fields are already available in publication &1&2 |
| SMOE_MESSAGE270 |
Error: Scheduling: Invalid site deactivation mode |
| SMOE_MESSAGE271 |
Error: Scheduling: Invalid site reactivation mode |
| SMOE_MESSAGE272 |
Error: Scheduling: Invalid subscription rerouting mode |
| SMOE_MESSAGE273 |
Warning: Scheduling interval overlaps with other scheduling intervals |
| SMOE_MESSAGE274 |
Error: Scheduling: No or illegal site type specification for scheduling |
| SMOE_MESSAGE275 |
Error: Illegal selection operator for scheduling dates |
| SMOE_MESSAGE276 |
Error: Others: Unspecified error while processing scheduling data (&1) |
| SMOE_MESSAGE277 |
Error: Others: Data consistency error (Subscription scheduling tables) |
| SMOE_MESSAGE278 |
Error: Scheduling destination site equals origin site |
| SMOE_MESSAGE279 |
Error: No/invalid scheduling entry selected |
| SMOE_MESSAGE280 |
Error: No/invalid exception entry for subscription specified |
| SMOE_MESSAGE281 |
Error: Selecting destination sites from database table SMOHSITEID |
| SMOE_MESSAGE282 |
Error: Exception for subscription schedul.: Missing/invalid subscription |
| SMOE_MESSAGE283 |
Error: Exception for subscription scheduling: Missing/invalid assignment |
| SMOE_MESSAGE284 |
Error: No/invalid destination site entry specified |
| SMOE_MESSAGE285 |
Information: Update of a running scheduling object |
| SMOE_MESSAGE286 |
Warning: Update of a running scheduling object - running actions changed |
| SMOE_MESSAGE287 |
Success: Selected scheduling object successfully updated |
| SMOE_MESSAGE288 |
Error: Error updating selected scheduling object - action not supported |
| SMOE_MESSAGE289 |
Error: Cannot save entry to table &1 - object key already exists |
| SMOE_MESSAGE290 |
Success: New scheduling entry successfully created - activation on 'Save' |
| SMOE_MESSAGE291 |
Success: Scheduling entry successfully deleted - activation on 'Save' |
| SMOE_MESSAGE292 |
Success: Scheduling entry successfully updated - activation on 'Save' |
| SMOE_MESSAGE293 |
Success: Destination site successfully added - activation on 'Save' |
| SMOE_MESSAGE294 |
Success: Destination site successfully removed - activation on 'Save' |
| SMOE_MESSAGE295 |
Success: Subscription rerouting successfully added - activation on 'Save' |
| SMOE_MESSAGE296 |
Success: Subscription rerouting successfully removed - activate on 'Save' |
| SMOE_MESSAGE297 |
Warning: Running interval - this will trigger immediate start of actions |
| SMOE_MESSAGE298 |
Scheduling is running:Status changed to Deleted when actions are finished |
| SMOE_MESSAGE299 |
Warning: Removal of destination sites will trigger immediate actions |
| SMOE_MESSAGE300 |
Error: Start date of running scheduling object cannot be altered |
| SMOE_MESSAGE301 |
Warning: Setting end date to current date will end scheduling interval |
| SMOE_MESSAGE302 |
Warning: Activation status change for a running scheduling entry |
| SMOE_MESSAGE303 |
Warning: Setting start date to current date will start scheduling |
| SMOE_MESSAGE304 |
Warning: Adding of destination sites will trigger immediate actions |
| SMOE_MESSAGE305 |
Uniqueness Error: Object already exists ( Tab. &1 ) - Creation impossible |
| SMOE_MESSAGE306 |
Authorization Error: 'View' Mode - Object modification not allowed |
| SMOE_MESSAGE307 |
Error: Job feedback update failure ( trying to set feedback to &1 ) |
| SMOE_MESSAGE308 |
Error: Failure to log scheduled actions to table SMOESTLOG |
| SMOE_MESSAGE309 |
Error: Subscription not found |
| SMOE_MESSAGE310 |
Subscriptions successfully assigned to replacement sites |
| SMOE_MESSAGE311 |
Successful update of exceptions for subscription |
| SMOE_MESSAGE312 |
Subscription exceptions successfully reset to original state |
| SMOE_MESSAGE313 |
Site successfully deactivated |
| SMOE_MESSAGE314 |
Site successfully reactivated - Extracts written for changed objects |
| SMOE_MESSAGE315 |
Site activation status not specified - activation/deactivation impossible |
| SMOE_MESSAGE316 |
Site status is Initially Inactive: Schedul. mechanisms cannot be applied |
| SMOE_MESSAGE317 |
Error: Site activation / deactivation - Site does not exist |
| SMOE_MESSAGE318 |
Error: Site activation - Site already active |
| SMOE_MESSAGE319 |
Site status is Initially Inactive. Use appropriate tools for activation |
| SMOE_MESSAGE320 |
Error: Others: Unspecified error during site activation / deactivation |
| SMOE_MESSAGE321 |
Site activation status update not necessary |
| SMOE_MESSAGE322 |
Site activation status update: &1 entries updated |
| SMOE_MESSAGE323 |
Error: Site activation status update failed: &1 entries not updated |
| SMOE_MESSAGE324 |
Activation not successful - extracts rolled back, no database update |
| SMOE_MESSAGE325 |
Activation not allowed for all sites-Successful activation where possible |
| SMOE_MESSAGE326 |
Selected sites successfully activated - Extracts written for &1 objects |
| SMOE_MESSAGE327 |
Deactivation not successful - action rolled back |
| SMOE_MESSAGE328 |
Deactivation not allowed for all sites - Deactivation where possible |
| SMOE_MESSAGE329 |
Selected sites successfully deactivated |
| SMOE_MESSAGE330 |
Deactivation not supported for site type &1 |
| SMOE_MESSAGE331 |
Error: Site deactivation - Site already inactive (initially or temp.) |
| SMOE_MESSAGE332 |
Site &1 cannot be set to 'Initial State' |
| SMOE_MESSAGE333 |
Background job ( &1 ) locked - Job cannot run more than once in parallel |
| SMOE_MESSAGE334 |
Function Module &1 called with invalid action parameter |
| SMOE_MESSAGE335 |
Site Activation/Deactivation: No sites provided |
| SMOE_MESSAGE336 |
Nothing to execute - No entry selected |
| SMOE_MESSAGE337 |
No authorization to view site scheduling job log |
| SMOE_MESSAGE338 |
User &1 does not have authorization to execute scheduling job |
| SMOE_MESSAGE339 |
Nothing to execute |
| SMOE_MESSAGE340 |
Error: ACREQ-Flag update failure ( trying to set ACREQ-Flag to &1 ) |
| SMOE_MESSAGE341 |
&1 - Execution has been skipped - end date is in the past |
| SMOE_MESSAGE342 |
Temporary subscription assignments: No actions to execute |
| SMOE_MESSAGE343 |
Resetting subscriptions: Nothing to reset-Original state reestablished |
| SMOE_MESSAGE344 |
Background job for execution of program &1 is not planned |
| SMOE_MESSAGE345 |
Error in background job maintenance: Function module returning error: &1 |
| SMOE_MESSAGE346 |
Background job successfully created. Job name and execution time: &1 |
| SMOE_MESSAGE347 |
Scheduling Templates: Template name missing - Specify a name |
| SMOE_MESSAGE348 |
Scheduling Templates: Template name is not unique |
| SMOE_MESSAGE349 |
Scheduling Templates: No actions specified |