Id | Title |
---|---|
TPDA514 | First enter a Web Dynpro component |
TPDA515 | Specified controller &1 does not exist. |
TPDA516 | Specified controller has no method |
TPDA517 | No active version of the component specified exists |
TPDA518 | No active controller exists for the value specified |
TPDA520 | Data for the table key selected is outdated |
TPDA521 | Flush not possible - data concerning table key selected is inconsistent |
TPDA522 | The table key selected does not exist |
TPDA523 | Internal error in the table tool: Invalid table key |
TPDA524 | Internal error in the table tool: Table key is not up to date |
TPDA525 | Internal error in the table tool: Invalid table name |
TPDA527 | Object set &1 accessed |
TPDA528 | Multiple object sets accessed: &1, &2, &3, &4 |
TPDA529 | Object set &1 exited |
TPDA530 | Multiple object sets exited (&1, &2, &3, &4 ) |
TPDA531 | Access to object set &1 / exit from object set &2 |
TPDA532 | Multiple object sets were accessed and exited |
TPDA534 | Message number &1 is invalid, only numerical characters are permitted |
TPDA535 | Message number &1 does not exist for message ID &2 |
TPDA536 | Message ID &1 does not exist |
TPDA537 | Selected object set was entered |
TPDA600 | Internal error in ABAP Debugging Interface |
TPDA609 | Only the layout of the user-specific desktop was saved. |
TPDA610 | The selected file &1 is not a Debugger layout file |
TPDA611 | Error downloading the file &1 (sy-subrc = &2) |
TPDA612 | Error uploading the file &1 (sy-subrc = &2) |
TPDA613 | The layout settings for file &1 are inconsistent |
TPDA614 | Error in file selection; you did not select exactly one file |
TPDA615 | Specify the name of the Debugger session |
TPDA616 | Specify the file name |
TPDA617 | You have not chosen any components for the debug session |
TPDA618 | Specify the relevant user for the debug session |
TPDA619 | Debug session could not be saved |
TPDA620 | Debugger session &1 for user &2 does not exist (yet) |
TPDA621 | Debug session &1 saved successfully |
TPDA622 | The special session &1 is used every time the Debugger is started |
TPDA623 | No debug session was selected |
TPDA624 | Debug sessions deleted successfully |
TPDA625 | No debug session was deleted |
TPDA626 | No debug session matching the selection was found |
TPDA627 | Error uploading file &1 |
TPDA628 | Inconsistent debug session (settings) |
TPDA629 | Session could not be saved: Inconsistent breakpoints |
TPDA630 | Components of session &1/&2 could not be loaded |
TPDA631 | Table &1 does not exist |
TPDA632 | Table &1 does not yet contain any rows |
TPDA633 | Debug session of file &1 contains inconsistent layout elements |
TPDA634 | Inconsistent debug session in file &1 (settings) |
TPDA635 | Debug session &1 / user = &2 contains no desktop specifications |
TPDA636 | Debug session file = &1 contains no desktop specifications |
TPDA637 | Obsolete, renamed debug sessions were also deleted |
TPDA638 | Inconsistent debug session (options) |
TPDA639 | A BSP page was reached |
TPDA640 | A breakpoint was reached and the ABAP trace was deactivated |
TPDA650 | Error opening the file &1 (&2) |
TPDA660 | The terminal ID &1 was set for outgoing requests. |
TPDA661 | A terminal ID for outgoing requests could not be set. |
TPDA700 | Action cancelled by user |
TPDA701 | Checkpoint entries cannot be deleted but only deactivated |
TPDA703 | Error uploading the table (RC = &1) |
TPDA704 | In &1 table rows, errors occurred during upload |
TPDA705 | The source table had fewer columns than the target table |
TPDA706 | The target table had fewer columns than the source table |
TPDA710 | At least one breakpoint in the current program could not be set |
TPDA711 | Error reading the current breakpoints |
TPDA712 | Breakpoint condition cannot be evaluated at position &1 |
TPDA713 | Breakpoint condition was deleted |
TPDA714 | Breakpoint condition was created |
TPDA715 | Breakpoint condition was changed |
TPDA716 | Method is in implemented in class &1 |
TPDA725 | It was not possible to navigate to the current stack level |
TPDA732 | The &2 exception occurred in the &1 script |
TPDA750 | &1 &2 |
TPDA751 | Error: &1 &2 &3 &4 |
TPDA790 | &1 variants were deleted |
TPDA791 | &1 variants were deleted (&2 variants: deletion refused) |
TPDA800 | Editor tool: Internal error in edit control |
TPDA801 | The current source code was reloaded |
TPDA810 | The requested tool is not (yet) Diff-compatible |
TPDA811 | The two variables are not compatible for a comparison (DIFF) |
TPDA812 | No Diff-service is available for data type & (yet) |
TPDA813 | The data types are not compatible for a comparison |
TPDA814 | No differences were found in the variables &1, &2 |
TPDA815 | The two variables for the comparison are identical |
TPDA816 | Change in variable &1: Diff results may be obsolete |
TPDA817 | Step in Debugger: Diff results may be obsolete |
TPDA818 | Stack navigation: Diff results may be obsolete |
TPDA819 | Diff tool: A variable is unknown (&1/&2) |
TPDA820 | Diff tool: A variable type is unknown (&1/&2) |
TPDA821 | Internal error in Diff tool: Scan error for variable &1 (&2) |
TPDA822 | Maximum hit number could not be changed |
TPDA823 | Maximum hit number changed successfully |
TPDA824 | Only 36 different scripts can be started per debug session |
TPDA825 | Internal error: Generated source is too wide |
TPDA826 | Internal error: Script source could not be generated |
TPDA827 | The script (program) &1 does not exist |
TPDA828 | The trace file &1 could not be opened (reason: &2) |
TPDA829 | No data exists |
TPDA830 | At least one of the selected variables does not exist |
TPDA840 | Watchpoints deleted |