Message Number list used by SAP ABAP Class CX_CACS_PATCH_MANAGER (Exception Class for CL_CACS_PATCH_MANAGER)
SAP ABAP Class
CX_CACS_PATCH_MANAGER (Exception Class for CL_CACS_PATCH_MANAGER) is using
| # | Object Type | Object Name | Object Description | Note |
|---|---|---|---|---|
| 1 | CACSAPPL - 502 | Upgrade comparison was not yet executed for application &1 | ||
| 2 | CACSAPPL - 556 | No changes possible; upgrade is not active | ||
| 3 | CACSAPPL - 555 | Not all steps have been executed | ||
| 4 | CACSAPPL - 543 | Client settings for generation client &1/&2 is incorrect | ||
| 5 | CACSAPPL - 542 | Not all steps have been executed for preceding time-spots | ||
| 6 | CACSAPPL - 541 | Error while scheduling background processing | ||
| 7 | CACSAPPL - 540 | Incomplete parameters for job scheduling | ||
| 8 | CACSAPPL - 539 | No active upgrade for application &1 was found | ||
| 9 | CACSAPPL - 538 | Upgrade &1 for application &2 was not found | ||
| 10 | CACSAPPL - 537 | Internal error: GUID cannot be generated | ||
| 11 | CACSAPPL - 536 | Task "&1" is already being excecuted | ||
| 12 | CACSAPPL - 535 | Step &1 for patch &2 is unknown | ||
| 13 | CACSAPPL - 534 | No step "&1" was found for the task | ||
| 14 | CACSAPPL - 533 | Data for task (internal ID &1) could not be updated | ||
| 15 | CACSAPPL - 532 | Database error: Error while saving data to table &1 | ||
| 16 | CACSAPPL - 531 | An upgrade is already active for application &1 | ||
| 17 | CACSAPPL - 529 | No task (internal ID &1) cannot be found | ||
| 18 | CACSAPPL - 528 | More than one upgrade is active for application &1 | ||
| 19 | CACSAPPL - 527 | Implementing class &1 for step &2 contains errors | ||
| 20 | CACSAPPL - 526 | Processing has been terminated | ||
| 21 | CACSAPPL - 001 | Application &1 not defined | ||
| 22 | CACS_BAL - 001 | Serious error in business application log | ||
| 23 | MC - 600 | System error occurred during lock management | ||
| 24 | MC - 601 | Object requested is currently locked by user & | ||
| 25 | MC - 602 | The requested object is locked by your own transaction |