SEEF_BADI - Meldungen bei BAdIs
The following messages are stored in message class SEEF_BADI: Meldungen bei BAdIs.
It is part of development package SEEF_REDEFINITION_BADI in software component BC-DWB-CEX-BAD. This development package consists of objects that can be grouped under "Enhancement Framework Redefinition BAdI".
It is part of development package SEEF_REDEFINITION_BADI in software component BC-DWB-CEX-BAD. This development package consists of objects that can be grouped under "Enhancement Framework Redefinition BAdI".
Message Nr ▲ | Message Text |
---|---|
000 | Dynpro &1 &2 does not contain subscreen area &3 |
001 | Enhancement spot is not empty |
002 | Fill out all required fields |
003 | BAdI &1 does not exist |
004 | A screen enhancement with the key &1 &2 &3 already exists |
005 | A screen enhancement for BAdI &1 already exists |
006 | Critical change |
007 | A function code enhancement with the key &1 &2 already exists |
008 | A filter with the key &1 &2 already exists |
009 | Filter &1 of the type &2 does not exist |
010 | BAdI &1 already uses dynpro &2 in program &3 |
011 | A screen enhancement with the key &1 &2 &3 does not exist. |
012 | Function code enhancement &2 for image &3 in program &1 does not exist |
013 | Changing the interface can cause inconsistencies. |
014 | Changing the interface for BAdI &1 is dangerous |
015 | Class &1 does not implement interface &2 |
016 | An example implementation with the key &1 already exists. |
017 | Class or interface &1 cannot be created |
018 | No interface exists for BAdI &1 |
019 | A filter for key &1 &2 already exists. |
020 | BAdI cannot be created: Error. |
021 | BAdI &1 has dependent objects |
022 | Could not delete |
023 | BAdI &1 successfully deleted. |
024 | BAdI implementation &1 is locked |
025 | BAdI implementation &1 not found |
026 | Class/interface name &1 is not valid. |
027 | Enhancement was saved. |
028 | Interface &1 does not include interface IF_BADI_INTERFACE. |
029 | An enhancement spot must be specified for the BAdI implementation |
030 | Specification of a BAdI definition is required for BAdI implementation |
031 | Specify implementation. |
032 | You cannot select default and example implementation at the same time |
033 | Error when reading enhancement spot &1 |
034 | Name of BAdI definition is invalid |
035 | BAdI &1 is not contained in enhancement spot &2 |
036 | Select another enhancement spot |
037 | Spot &1 does not exist. |
038 | Multiple implementation not allowed, as screen/menu enhancements exist |
039 | Dynpro &2 does not exist in program &1 |
040 | Icon &1 does not exist. |
041 | BAdI &1 contains menu enhancements |
042 | Icon &1 does not exist. |
043 | Screen enhancements only possible for BAdIs with simple implementation |
044 | Menu enhancements only possible for BAdIs with simple implementation |
045 | Input of filter value without relational operator not useful |
046 | Internal error during calculation of filter condition. |
047 | Implementation name for BAdI & not specified |
048 | Call of form interpreter was generated in method &1. |
049 | Implementation &1 will be migrated (see long text for instructions) |
050 | BAdI migrated in full; change implementation enhancement & instead |
051 | Use transaction SPAU to migrate BAdI implementation &1 |
052 | BAdI implementation &1 will be migrated automatically |
053 | OR operation not possible |
054 | AND operation not possible |
055 | Comparison operator &1 is not valid. |
056 | Enhancement spot &1 migrated from the BAdI will be deleted |
057 | Enhancement &1 migrated from the implementation is deleted. |
058 | Combination of &1, &2, and comparator &3 not useful |
059 | Comparator &1 is not recommended for the filter type &2. |
060 | BAdI implementation &1 already exists in the enhancement |
061 | Menu enhancement combined with filter is not allowed |
062 | Screen enhancement location: Program/dynpro/subscreen area unknown |
063 | Menu enhancement: Program/function code unknown |
064 | The corresponding enhancement spot &1 does not exist or no longer exists |
065 | The corresponding enhancement spot &1 is not a BAdI definition |
066 | BAdI &1 is not defined in enhancement spot &2 |
067 | BAdI interface &2 is not implemented in class &1 |
068 | Screen enhancement dynpro &1 does not exist in program &2 |
069 | Migrated enhancement implementation &1 will be generated |
070 | Migrated enhancement implementation &1 was generated |
071 | Enter the default data. |
072 | Filter name &1 is invalid |
073 | Interface must be specified in BAdI definition &1 |
074 | Class missing for BAdI implementation &1 |
075 | An implementation exists for BAdI &1 |
076 | Domain &1 does not exist |
077 | &1 is a data element and not a domain |
078 | Data element &1 does not exist |
079 | &1 is a domain and not a data element |
080 | Interface IF_FILTER_CHECK_AND_F4 is not implemented in class &1 |
081 | Deletion of BAdI implementation &1 not possible |
082 | Menu enhancements exist for BAdI &1 |
083 | First choose filters from the list of available filters |
084 | Position the cursor on a BAdI implementation |
085 | First choose a program for the subscreen |
086 | First choose a valid BAdI in the tree |
087 | For BAdI &1, context set to "Not Context-Dependent" |
088 | Context settings for BAdI &1 cannot be changed |
089 | Class &1 is abstract |
090 | Interface &2 cannot be used (see long text) |
091 | Implementations exist for BAdI definition &1: Deletion not possible |
092 | Resorting dependent BAdI &1 |
093 | Lock error for BAdI &1 |
094 | BAdI &1 is an internal BAdI (see long text) |
095 | Import ENBC object (switch BAdI active/inactive): &1 |
096 | BAdI &1 already exists |
097 | BAdI definition &1 does not contain an interface yet |
098 | Invalid context settings for BAdI &1 due to screen enhancements |
099 | BAdI &1 migrated: Changing not permitted |
100 | Function not available |
101 | Changing context settings of BAdI &1 |
102 | BAdI &1 generation error: Data type with same name (&2 &3) exists |
103 | BAdI implementation &1 must still be migrated |
104 | Namespace conflict (see long text) |
105 | SPAU entry for migration of implementation &1 will be removed |
106 | Sort implementation &1 imported; resort will be started |
107 | BAdI &1 will be generated |
108 | BAdI &1 will be deleted |
109 | Specify either BAdI definition or BAdI implementation |
110 | First choose a filter combination |
111 | Create ENBC object from SXCC object due to migrated BAdI |
112 | BAdI implementation &1 not found in enhancement implementation &2 |
113 | Define an interface first |
114 | Referenced enhancement implementation &1 does not exist |
115 | ENBC object &1 has no effect and is ignored |
116 | Single character "&1" is not permitted in "&2"; use duplicate: "&3" |
117 | Not possible in the case of BAdIs with filters |
118 | Enclosing literal characters '...' or `...` are superfluous |
119 | Filter &1: Dictionary element &2 does not exist |
120 | Filter &1: Class &2 does not exist |
121 | Changing a filter for BAdI &1 is dangerous |
122 | Definition of filter &1 has filter type &3 differing from &2 |
123 | Definition of filter &1 has Dictionary reference &3 differing from &2 |
124 | Definition of filter &1 has program reference &3 differing from &2 |
125 | String filter value contains significant trailing blanks: &1 |
126 | Filter &1: Definition of filter value is incomplete |
127 | Class &1 does not exist or has errors |
128 | BAdI &1: Limited filter use collides with filter number |
129 | Selected layer is invalid |
130 | Select one filter only (limited filter use) |
131 | AND link not allowed (limited filter usage) |
132 | Filter combination required (limited filter use) |
133 | Comparator is invalid (limited filter use) |
134 | Implementation &1 already exists |
135 | Import of BAdI sorting implementation and BAdI &1 resort not possible |
136 | Navigation not yet implemented |
137 | Class name for BAdI &1 missing |
138 | This function is not yet available |
139 | No BAdI selected |
140 | Implementations of BADI_SORTER cannot be found |
141 | Select a BAdI definition |
142 | Enter an implementation name |
143 | Enter an implementation name for BAdI &1 |
144 | Implementation name &1 used more than once |
145 | BADI_SORTER Implementation &1 has filter condition that is not allowed |
146 | Error While Checking Implementation: &1 |
147 | Function code &2 in program &1 already declared in BAdI &3 |
148 | Name of BAdI implementation &1 is invalid |
150 | Creation of classic BAdIs no longer supported (see long text) |
151 | Use transaction SPAU to migrate CMOD implementation &1 |
152 | CMOD &1 for SMOD &2 has yet to be migrated |
160 | BAdI & is referenced in IMG. Check IMG and adapt if necessary |
161 | Implementation & is referenced in IMG. Adapt IMG accordingly |
162 | A customer implementation cannot be migrated to an SAP implementation |
164 | Enter at least one function text |
170 | "Switch Off Default Menu Enhancement" not possible |
171 | Implementation specifications for menu enhancement will be deleted |
175 | Implementation will be created as SAP preliminary object |
176 | BAdI is internal SAP; implementation in customer namespace not allowed |
177 | Enhancement implementation will be created as SAP Pre-Export Object |
178 | Internal SAP enhancement; no implementation allowed in customer namespace |
180 | Choose an example class |
181 | Choose a class that is not declared as "final" |
182 | &1 is still used as a fallback class; cannot delete class |
183 | Select an example implementation |
184 | Select an implementation that is not declared as "final" |
191 | Enter a class name |
192 | Enhancement implementation was saved |
193 | Enhancement implementation was activated |
200 | Data type &1 &2 already exists |
201 | &1 already exists as classic BAdI definition |
210 | BAdI implementation &1 no longer exists; SPAU entry will be deleted |
250 | Comparison of &1 and &2 not supported. Overlapping? (&3, &4) |
251 | Overlapping of comparisons &1 and &2. (&3, &4) |
252 | Conflict between adjustment &1 and &2. (&3, &4) |
253 | Implementation &3 and &4 active simultaneously |
254 | Conflict with &4: &3 has no condition for filter &1 |
255 | Empty interval: &1 (&3) |
256 | Contradictory conjunction with inequation for filter &1 (&3) |
258 | Filter &1: Data type INT8 is not supported (data element &2) |
259 | Filter &1: Data type INT8 is not supported (domain &2) |
300 | Filter &1 was deleted; filter restriction will also be deleted |
301 | Filter &1 type changed; filter restriction will be deleted |
302 | Filter &1 filter check changed; check filter settings |
303 | BAdI &1 does not exist; implementation &2 will be deleted |
304 | Class &1 does not exist |
305 | Class &1 already exists |
306 | Creation of class &1 was terminated |
307 | Creation of BAdI implementation &1 was started |
308 | Creation of BAdI definition &1 was canceled |
309 | Class &1 contains syntax errors |
310 | Class &1 is not active |
311 | Constructor of class &1 cannot have parameter |
312 | Creation of BAdI implementation was canceled |
313 | Do not specify optional parameters in the constructor of class &1 |
316 | Class &1 is an Exit Handler class; this is not allowed |
317 | Class &1 is a test class and this action is not permitted |
320 | Menu enhancements are not supported for AMDP BAdI definitions |
321 | Screen enhancements are not supported for AMDP BAdI definitions |
322 | No check class for AMDP BAdI definitions |
323 | Menu enhancements for AMDP BAdI implementations are not supported |
324 | Screen enhancements for AMDP BAdI implementations are not supported |
325 | No check class for AMDP BAdI implementations |
326 | Enhancement spot &1 does not contain any released BAdI definitions |
327 | Could not load enhancement implementation &1 |
328 | BAdI definition &1 does not match namespace '&2' of &3 |
329 | Enhancement spot contains menu enhancements |
330 | Enhancement spot contains screen enhancements |
331 | No changes can be made to migrated enhancement spot &1 in ADT |
332 | No changes can be made to migrated enhancement &1 in ADT |