Message Number list used by SAP ABAP Class CL_UR_STATUS_HANDLING (Central Class for Routines for Status Handling)
SAP ABAP Class 
CL_UR_STATUS_HANDLING (Central Class for Routines for Status Handling) is using
-
Class (54)
-
Data Element (23)
-
Table/Structure Field (317)
-
Function Module (4)
-
Message Class (25)
-
Message Number (88)
-
Class Method (92)
-
Program (1)
-
Table (40)
| # | Object Type | Object Name | Object Description | Note |
|---|---|---|---|---|
 |
|
|||
| 1 | Message Number |
UR - 420 | Run status not reset. This is not an error | |
| 2 | Message Number |
UR - 442 | No restart possible with status &2 for transaction data replication | |
| 3 | Message Number |
UR - 441 | Restart not possible with realignment run status &3 | |
| 4 | Message Number |
UR - 440 | Restart not allowed with run status &3 | |
| 5 | Message Number |
UR - 437 | Replication object delta already started. Status &1 | |
| 6 | Message Number |
UR - 436 | Replication object delta can only have BW replication status &1 | |
| 7 | Message Number |
UR - 435 | Replication object delta can only have change status &1 | |
| 8 | Message Number |
UR - 434 | Replication status set to &1 for the object delta | |
| 9 | Message Number |
UR - 421 | Rollback only possible if the realignment run was successful | |
| 10 | Message Number |
UR - 421 | Rollback only possible if the realignment run was successful | |
| 11 | Message Number |
UR - 420 | Run status not reset. This is not an error | |
| 12 | Message Number |
UR - 443 | No restart possible with status &2 for object delta replication | |
| 13 | Message Number |
UR - 420 | Run status not reset. This is not an error | |
| 14 | Message Number |
UR - 420 | Run status not reset. This is not an error | |
| 15 | Message Number |
UR - 419 | The run cannot be executed (&1) | |
| 16 | Message Number |
UR - 418 | The status of the run has been reset | |
| 17 | Message Number |
UR - 417 | Status of change reset | |
| 18 | Message Number |
UR - 411 | Run status is set to 'terminated' | |
| 19 | Message Number |
UR - 411 | Run status is set to 'terminated' | |
| 20 | Message Number |
UR - 411 | Run status is set to 'terminated' | |
| 21 | Message Number |
UR - 411 | Run status is set to 'terminated' | |
| 22 | Message Number |
UR - 410 | The run was successful | |
| 23 | Message Number |
UR - 478 | Run &1 is not active | |
| 24 | Message Number |
UR - 502 | The run can only be confirmed after reinitialization | |
| 25 | Message Number |
UR - 496 | Automatically generated runs cannot be restarted | |
| 26 | Message Number |
UR - 482 | Run &1 cannot be undone as run &2 is still active | |
| 27 | Message Number |
UR - 481 | Run &1 cannot be undone until run &2 has been undone too | |
| 28 | Message Number |
UR - 480 | Run &1 cannot be cleaned up until run &2 has been cleaned up too | |
| 29 | Message Number |
UR - 479 | Run &1 is active - the undo function cannot be used | |
| 30 | Message Number |
UR - 479 | Run &1 is active - the undo function cannot be used | |
| 31 | Message Number |
UR - 478 | Run &1 is not active | |
| 32 | Message Number |
UR - 478 | Run &1 is not active | |
| 33 | Message Number |
UR - 478 | Run &1 is not active | |
| 34 | Message Number |
UR - 410 | The run was successful | |
| 35 | Message Number |
UR - 476 | Status of the alignment run is now complete | |
| 36 | Message Number |
UR - 475 | Cleanup successful | |
| 37 | Message Number |
UR - 474 | Undo is still running - clean-up cannot be performed yet | |
| 38 | Message Number |
UR - 473 | Cleanup only possible if object replication has the status 'successful' | |
| 39 | Message Number |
UR - 472 | Cleanup only possible if the BW replication has the status 'successful' | |
| 40 | Message Number |
UR - 471 | Cleanup only possible if the changes have status 'successful' | |
| 41 | Message Number |
UR - 470 | The run can only be cleaned up if it has the status 'successful' | |
| 42 | Message Number |
UR - 446 | No restart possible with status &2 for repairs | |
| 43 | Message Number |
UR - 445 | No restart with clean-up status &2 | |
| 44 | Message Number |
UR - 444 | No restart possible with status &2 for undo | |
| 45 | Message Number |
UR - 000 | Invalid program status in the realignment tool | |
| 46 | Message Number |
UR - 401 | The overall status of the run is '&1' | |
| 47 | Message Number |
UR - 401 | The overall status of the run is '&1' | |
| 48 | Message Number |
UR - 175 | Status &2 could not be set. Extraction not possible | |
| 49 | Message Number |
UR - 175 | Status &2 could not be set. Extraction not possible | |
| 50 | Message Number |
UR - 174 | Replication not in status &2. Inconsistency, extraction not possible | |
| 51 | Message Number |
UR - 000 | Invalid program status in the realignment tool | |
| 52 | Message Number |
UR - 000 | Invalid program status in the realignment tool | |
| 53 | Message Number |
UR - 000 | Invalid program status in the realignment tool | |
| 54 | Message Number |
UR - 000 | Invalid program status in the realignment tool | |
| 55 | Message Number |
UR - 000 | Invalid program status in the realignment tool | |
| 56 | Message Number |
UR - 401 | The overall status of the run is '&1' | |
| 57 | Message Number |
UR - 000 | Invalid program status in the realignment tool | |
| 58 | Message Number |
UR - 000 | Invalid program status in the realignment tool | |
| 59 | Message Number |
UR - 000 | Invalid program status in the realignment tool | |
| 60 | Message Number |
UR - 000 | Invalid program status in the realignment tool | |
| 61 | Message Number |
UR - 000 | Invalid program status in the realignment tool | |
| 62 | Message Number |
UR - 000 | Invalid program status in the realignment tool | |
| 63 | Message Number |
UR - 000 | Invalid program status in the realignment tool | |
| 64 | Message Number |
UR - 000 | Invalid program status in the realignment tool | |
| 65 | Message Number |
UR - 000 | Invalid program status in the realignment tool | |
| 66 | Message Number |
UR - 000 | Invalid program status in the realignment tool | |
| 67 | Message Number |
UR - 406 | Already cleaned up/being cleaned up | |
| 68 | Message Number |
UR - 410 | The run was successful | |
| 69 | Message Number |
UR - 410 | The run was successful | |
| 70 | Message Number |
UR - 410 | The run was successful | |
| 71 | Message Number |
UR - 407 | Already repaired/being repaired | |
| 72 | Message Number |
UR - 407 | Already repaired/being repaired | |
| 73 | Message Number |
UR - 407 | Already repaired/being repaired | |
| 74 | Message Number |
UR - 407 | Already repaired/being repaired | |
| 75 | Message Number |
UR - 407 | Already repaired/being repaired | |
| 76 | Message Number |
UR - 406 | Already cleaned up/being cleaned up | |
| 77 | Message Number |
UR - 406 | Already cleaned up/being cleaned up | |
| 78 | Message Number |
UR - 000 | Invalid program status in the realignment tool | |
| 79 | Message Number |
UR - 406 | Already cleaned up/being cleaned up | |
| 80 | Message Number |
UR - 406 | Already cleaned up/being cleaned up | |
| 81 | Message Number |
UR - 405 | Already reversed/being reversed | |
| 82 | Message Number |
UR - 405 | Already reversed/being reversed | |
| 83 | Message Number |
UR - 405 | Already reversed/being reversed | |
| 84 | Message Number |
UR - 405 | Already reversed/being reversed | |
| 85 | Message Number |
UR - 404 | Object changes already implemented | |
| 86 | Message Number |
UR - 403 | Replication already triggered | |
| 87 | Message Number |
UR - 402 | The run must at least have been executed | |
| 88 | Message Number |
UR - 401 | The overall status of the run is '&1' |
