Message Number list used by SAP ABAP Program LENH_BADI_EDT_DEFP08 (LIF_BADI_INTERFACE)
SAP ABAP Program LENH_BADI_EDT_DEFP08 (LIF_BADI_INTERFACE) is using
# | Object Type | Object Name | Object Description | Note |
---|---|---|---|---|
1 | Message Number | SEEF_BADI - 002 | Fill out all required fields | |
2 | Message Number | SEEF_BADI - 015 | Class &1 does not implement interface &2 | |
3 | Message Number | SEEF_BADI - 016 | An example implementation with the key &1 already exists. | |
4 | Message Number | SEEF_BADI - 022 | Deletion failed. | |
5 | Message Number | SEEF_BADI - 023 | BAdI &1 successfully deleted. | |
6 | Message Number | SEEF_BADI - 027 | Enhancement was saved. | |
7 | Message Number | SEEF_BADI - 033 | Error when reading enhancement spot &1 | |
8 | Message Number | SEEF_BADI - 034 | Name of BAdI definition is invalid | |
9 | Message Number | SEEF_BADI - 087 | For BAdI &1, context set to "Not Context-Dependent" | |
10 | Message Number | SEEF_BADI - 091 | Implementations exist for BAdI definition &1: Deletion not possible | |
11 | Message Number | SEEF_BADI - 096 | BAdI &1 already exists | |
12 | Message Number | SEEF_BADI - 104 | Namespace conflict (see long text) | |
13 | Message Number | SEEF_BADI - 176 | BAdI is internal SAP; implementation in customer namespace not allowed | |
14 | Message Number | SEEF_BADI - 182 | &1 is still used as a fallback class; cannot delete class | |
15 | Message Number | SEEF_BADI - 308 | Creation of BAdI definition &1 was canceled | |
16 | Message Number | SEEF_BASE - 083 | Fill all required entry fields |