SRFAC_IMPL - Refactoring messages
The following messages are stored in message class SRFAC_IMPL: Refactoring messages.
It is part of development package SRFAC_IMPL in software component BC-DWB-AIE-REF. This development package consists of objects that can be grouped under "Implementation of new refactoring".
It is part of development package SRFAC_IMPL in software component BC-DWB-AIE-REF. This development package consists of objects that can be grouped under "Implementation of new refactoring".
Message Nr ▲ | Message Text |
---|---|
000 | &1&2&3&4 |
001 | Refactoring is not supported if element is used inside macro |
002 | Parameter &1 out of bounds: &2 |
003 | Parameter start > end: &1 > &2 |
004 | Parameter previous end >= next start: &1 >= &2 |
005 | Old content of region (start=&1, end=&2) not as expected |
006 | Maximum line length exceeded: &1 > &2 |
007 | Error when replacing &1. Details: &2&3&4 |
008 | Error when replacing &1. Object perhaps outdated. Details: &2&3&4 |
009 | Syntax error in &1: &2&3&4 |
010 | Refactoring in multiple main programs is not supported: &1 <> &2 |
011 | Refactoring in function modules is currently not supported |
012 | Refactoring in other programs is currently not supported |
013 | Refactoring of global types is currently not supported |
014 | Refactoring of redefined methods is currently not supported |
015 | Renaming of interface methods must start from their definition |
016 | Selected area exceeds include boundaries. |
017 | Invalid source position supplied. |
018 | No selection supplied. |
019 | Selection contains incomplete ABAP statements. |
020 | Selection contains a control structure which is not selected completely. |
021 | Selection contains ABAP statement &1 which has no corresponding start. |
022 | Selection can't be extracted to a new method. |
023 | ABAP Compiler error! Please ensure that the source code is error-free. |
024 | Selection is not within a valid ABAP method implementation. |
025 | Extraction of locally defined types is currently not supported. |
026 | Source contains assigns to field symbols! Extraction is impossible. |
027 | Unknown value for parameter transfer direction: &1 |
028 | Only one returning parameter allowed |
029 | Definition of class &1 can not be found |
030 | Implementation of class &1 can not be found |
031 | Refactoring impossible. Method has already been declared. |
032 | Parameter conversion of inline declarations is currently not supported. |
033 | Syntax error in &1: Resolve errors and execute operation again. |
034 | Global refactorings can be triggered from the defining source unit only. |
035 | Renaming of objects of type &1 is currently not supported. |
036 | ABAP Compiler reference does not represent a method. |
037 | ABAP Compiler reference does not represent a parameter. |
038 | Refactoring operation &1 is not supported. |
039 | Include &1 was not found. |
040 | Frontend and Backend position were set inconsistent - cursor vs. range |
041 | Frontend and Backend position were set inconsistent - includes differ |
042 | References in Web Dynpro objects found. Refactoring is impossible. |
043 | References in BSP objects found. Refactoring is impossible. |
044 | References in &1 found. Refactoring is impossible. |
045 | Fullname could not be determined in include &1 at column &2 of line &3 |
046 | References in Enhancements found. Refactoring is impossible. |
047 | The local definition of &1 refers to &2 &3 which is only visible locally. |
048 | A member with name &1 is already declared in &2 |
049 | Reserved name ME can't be renamed. |
050 | References in function module interf. found. Refactoring is impossible. |
051 | Call does_statement_match( ) first to calculate match result |
052 | Predefined types or fields can't be renamed. |
053 | New &1 used as actual parameter, type compatibility is not guaranteed. |
054 | New &1 used for generic parameter, type compatibility is not guaranteed. |
055 | Constant &1 declared after intended usage, manual adjustment required. |
056 | Source contains program flow change by &1. Refactoring is not possible. |
057 | Field &1 uses complex LIKE reference. Refactoring is not possible. |
058 | Type of field &1 is created in source method. Refactoring is impossible. |
059 | The &1 &2 refers to &3 &4 which will not be pulled up. |
060 | The &1 &2 refers to other members which will not be pulled up. |
061 | The object &1 of type &2 belongs to SAP or a partner and can't be renamed |
062 | Can't rename constant at this usage position - try at definition instead. |