SAP ABAP Message Class SRFAC_IMPL (Refactoring messages)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-DWB-AIE-REF (Application Component) Tools for Refactoring ABAP Artifacts
⤷ SRFAC_IMPL (Package) Implementation of new refactoring
⤷ BC-DWB-AIE-REF (Application Component) Tools for Refactoring ABAP Artifacts
⤷ SRFAC_IMPL (Package) Implementation of new refactoring
Attributes
Message class | SRFAC_IMPL | |
Short Description | Refactoring messages | |
Changed On | 20141121 | |
Last Changed At | 124018 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | &1&2&3&4 | The short text describes the object sufficiently | |
2 | 001 | Refactoring is not supported if element is used inside macro | The short text describes the object sufficiently | |
3 | 002 | Parameter &1 out of bounds: &2 | The short text describes the object sufficiently | |
4 | 003 | Parameter start > end: &1 > &2 | The short text describes the object sufficiently | |
5 | 004 | Parameter previous end >= next start: &1 >= &2 | The short text describes the object sufficiently | |
6 | 005 | Old content of region (start=&1, end=&2) not as expected | The short text describes the object sufficiently | |
7 | 006 | Maximum line length exceeded: &1 > &2 | The short text describes the object sufficiently | |
8 | 007 | Error when replacing &1. Details: &2&3&4 | The short text describes the object sufficiently | |
9 | 008 | Error when replacing &1. Object perhaps outdated. Details: &2&3&4 | The short text describes the object sufficiently | |
10 | 009 | Syntax error in &1: &2&3&4 | The short text describes the object sufficiently | |
11 | 010 | Refactoring in multiple main programs is not supported: &1 <> &2 | The short text describes the object sufficiently | |
12 | 011 | Refactoring in function modules is currently not supported | The short text describes the object sufficiently | |
13 | 012 | Refactoring in other programs is currently not supported | The short text describes the object sufficiently | |
14 | 013 | Refactoring of global types is currently not supported | The short text describes the object sufficiently | |
15 | 014 | Refactoring of redefined methods is currently not supported | The short text describes the object sufficiently | |
16 | 015 | Renaming of interface methods must start from their definition | The short text describes the object sufficiently | |
17 | 016 | Selected area exceeds include boundaries. | The short text describes the object sufficiently | |
18 | 017 | Invalid source position supplied. | The short text describes the object sufficiently | |
19 | 018 | No selection supplied. | The short text describes the object sufficiently | |
20 | 019 | Selection contains incomplete ABAP statements. | The short text describes the object sufficiently | |
21 | 020 | Selection contains ABAP statement &1 which has no corresponding end. | The short text describes the object sufficiently | |
22 | 021 | Selection contains ABAP statement &1 which has no corresponding start. | The short text describes the object sufficiently | |
23 | 022 | Selection can't be extracted to a new method. | The short text describes the object sufficiently | |
24 | 023 | ABAP Compiler error! Please ensure that the source code is error-free. | The short text describes the object sufficiently | |
25 | 024 | Selection is not within a valid ABAP method implementation. | The short text describes the object sufficiently | |
26 | 025 | Extraction of locally defined types is currently not supported. | The short text describes the object sufficiently | |
27 | 026 | Source contains changes to field symbols! Extraction is impossible. | The short text describes the object sufficiently | |
28 | 027 | Unknown value for parameter transfer direction: &1 | The short text describes the object sufficiently | |
29 | 028 | Only one returning parameter allowed | The short text describes the object sufficiently | |
30 | 029 | Definition of class &1 can not be found | The short text describes the object sufficiently | |
31 | 030 | Implementation of class &1 can not be found | The short text describes the object sufficiently | |
32 | 031 | Refactoring impossible. Method has already been declared. | The short text describes the object sufficiently | |
33 | 032 | Parameter conversion of inline declarations is currently not supported. | The short text describes the object sufficiently | |
34 | 033 | Syntax error in &1: Resolve errors and execute operation again. | The short text describes the object sufficiently | |
35 | 034 | Global refactorings can be triggered from the defining source unit only. | Space: object requires documentation | |
36 | 035 | Renaming of objects of type &1 is currently not supported. | The short text describes the object sufficiently | |
37 | 036 | ABAP Compiler reference does not represent a method. | The short text describes the object sufficiently | |
38 | 037 | ABAP Compiler reference does not represent a parameter. | The short text describes the object sufficiently | |
39 | 038 | Refactoring operation &1 is not supported. | The short text describes the object sufficiently | |
40 | 039 | Include &1 was not found. | The short text describes the object sufficiently | |
41 | 040 | Frontend and Backend position were set inconsistent - cursor vs. range | The short text describes the object sufficiently | |
42 | 041 | Frontend and Backend position were set inconsistent - includes differ | The short text describes the object sufficiently | |
43 | 042 | References in Web Dynpro objects found. Refactoring is impossible. | The short text describes the object sufficiently | |
44 | 043 | References in BSP objects found. Refactoring is impossible. | The short text describes the object sufficiently | |
45 | 044 | References in &1 found. Refactoring is impossible. | The short text describes the object sufficiently | |
46 | 045 | Fullname could not be determined in include &1 at column &2 of line &3 | The short text describes the object sufficiently | |
47 | 046 | References in Enhancements found. Refactoring is impossible. | The short text describes the object sufficiently | |
48 | 047 | The local definition of &1 refers to &2 &3 which is only visible locally. | The short text describes the object sufficiently | |
49 | 048 | A member with name &1 is already declared in &2 | The short text describes the object sufficiently | |
50 | 049 | Reserved name ME can't be renamed. | The short text describes the object sufficiently | |
51 | 050 | References in function module interf. found. Refactoring is impossible. | The short text describes the object sufficiently | |
52 | 051 | Call does_statement_match( ) first to calculate match result | The short text describes the object sufficiently | |
53 | 052 | Predefined types or fields can't be renamed. | The short text describes the object sufficiently | |
54 | 053 | New &1 used as actual parameter, type compatibility is not guaranteed. | The short text describes the object sufficiently | |
55 | 054 | New &1 used for generic parameter, type compatibility is not guaranteed. | The short text describes the object sufficiently | |
56 | 055 | Constant &1 declared after intended usage, manual adjustment required. | The short text describes the object sufficiently |
History
Last changed on/by | 20141121 | SAP | |
SAP Release Created in | 740 |