15 - Nachrichten der Verbuchung
The following messages are stored in message class 15: Nachrichten der Verbuchung.
It is part of development package STSK in software component BC-CST. This development package consists of objects that can be grouped under "Task Handler, Number Range, Update, Gateway and so on".
It is part of development package STSK in software component BC-CST. This development package consists of objects that can be grouped under "Task Handler, Number Range, Update, Gateway and so on".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Update successfully executed |
| 001 | V1 Update closed |
| 002 | Error inserting in VBHDR |
| 003 | Error reading VBHDR |
| 004 | Dump when executing an update request |
| 005 | Error during Commit |
| 006 | Error reading VBMOD |
| 007 | Error updating VBMOD |
| 008 | No memory received/found |
| 009 | Update canceled by a message |
| 010 | No dynpro memory received |
| 011 | Incorrect update mode |
| 012 | Update hung in state "run" |
| 013 | Update hung in state "delete" |
| 014 | Incorrect update parameters |
| 015 | No update parameters found |
| 016 | Deadlock during update |
| 017 | No update server found for context & |
| 018 | No list of servers received |
| 019 | Fehler updating VBHDR |
| 020 | Update server is not running |
| 021 | Locks deleted manually |
| 022 | The dispatcher is unable to assign the update request |
| 023 | Error sending/receiving a message |
| 024 | Error while executing COMMIT WORK |
| 025 | Error within the update control |
| 030 | Update record does not exist |
| 031 | Inconsistency in table TNMAP |
| 032 | Data is not complete; fill out all fields |
| 033 | INSERT error in table ASGRP; entry exists already |
| 034 | TH_CHANGE_PARAMETER returns error & |
| 035 | ALV reports error & |
| 036 | No locks exist |
| 037 | External transaction monitor reports ABORT |
| 038 | External COMMIT expected |
| 039 | Updating from batch input |
| 040 | Updating must not be reposted manually |
| 041 | Update cannot be reposted |
| 042 | All records were restarted |
| 043 | Not all the update records could be started |
| 100 | Update data cannot be reorganized in batch |
| 101 | Error & occurred |
| 200 | Error occurred in V2 update |
| 201 | Error in update control |
| 202 | No authorization for update administration |
| 203 | Update task debugging is only possible in the same client |
| 204 | Update request is not in state 'init' |
| 205 | Mark at least one record |
| 206 | No error found when running update request |
| 207 | The conditions can only be changed with restrictions |
| 208 | No ABAP short dump exists |
| 209 | Invalid VBPHASE & |
| 210 | Update state & not allowed for normal update |
| 211 | No program reference exists |
| 212 | No update parameters exist |
| 213 | No update request found (key: &) |
| 214 | Error reading update request; key: & |
| 215 | Update module not found; key:&, UD-ID: & |
| 216 | Error reading an update module; key:&, UB-ID: & |
| 217 | This update request cannot be carried out retrospectively; & |
| 218 | Error when updating records; number of errors: & |
| 219 | Error when saving user attributes |
| 220 | Update requests reset; number: & |
| 221 | Function not possible; no update server found for context |
| 222 | System error occurred calling SM13 on server & |
| 223 | Communication error calling SM13 on server & |
| 224 | Error calling SM13 on server & |
| 225 | V1 update not yet executed |
| 226 | & updates started; number: & |
| 227 | V1 updates started; number: & |
| 228 | No update requests found |
| 229 | V1 and V2 updates already executed |
| 230 | Only update requests with errors can be updated retrospectively |
| 231 | Reorganization ended; & incomplete update requests deleted |
| 232 | Update requests in state 'Prepared' cannot be changed |
| 233 | Update requests in state 'Aborted' cannot be changed |
| 234 | Post records: &1 started, &2 not started (UPRC), &3 not found |
| 235 | No connection to the message server; activation not currently possible |
| 236 | Update message: Test with variable part (& & & &) and end. |
| 237 | No authorization for debugging |
| 238 | Error & when displaying documentation |
| 239 | Update debugging has been triggered |
| 240 | Select a server group |
| 241 | Reorganization was not performed (see parameter rdisp/vbdelete). |
| 250 | Internal error &: & |
| 300 | Select the end of the block; start of the block is already selected |
| 301 | Select all records |
| 302 | No need to reset any update records |
| 303 | Server group & does not contain an update server |
| 304 | Server group & prevents RKS (contains only one update server) |
| 305 | Local table names are currently not supported |
| 600 | Failed to insert update header |
| 601 | Failed to read update header |
| 602 | Dump in update |
| 603 | Commit during update start failed |
| 604 | Failed to read update module header |
| 605 | Failed to change update module header |
| 606 | Memory error during update |
| 607 | No access to working memory of the update dynpro |
| 608 | Update request is not in state 'init' |
| 609 | Make a selection |
| 610 | No error found when running update request |
| 611 | The conditions can only be changed with restrictions |
| 612 | No ABAP short dump exists |
| 613 | Invalid VBPHASE & |
| 614 | Update state & not allowed for normal update |
| 615 | No program reference exists |
| 616 | No update parameters exist |
| 617 | No update request found (key: &) |
| 618 | Error reading update request; key: & |
| 619 | Update module not found; key:&, UD-ID: & |
| 620 | Error reading an update module; key:&, UB-ID: & |
| 621 | This update request cannot be carried out retrospectively |
| 622 | No update server active |
| 623 | No list of servers received |
| 624 | Update delayed; wait |
| 625 | Update delayed |
| 626 | Update data cannot be displayed; RC: & |
| 627 | No function module found |
| 700 | Warning: Error occurred when processing an update request |
| 701 | Warning: Error in update request; update key = &2 |