Message Number list used by SAP ABAP Class CL_PACKAGE_HELPER (Auxiliary Class for Package API)
SAP ABAP Class CL_PACKAGE_HELPER (Auxiliary Class for Package API) is using
# | Object Type | Object Name | Object Description | Note |
---|---|---|---|---|
1 | Message Number | EU - 369 | Do not use any characters from &1 | |
2 | Message Number | PAK - 144 | Package name cannot contain spaces | |
3 | Message Number | PAK - 111 | Development element &1 &2 does not exist | |
4 | Message Number | PAK - 113 | Cannot change type of package interface &1 | |
5 | Message Number | PAK - 114 | Package name must start with S or TEST | |
6 | Message Number | PAK - 115 | Package name must start with A-R, U-X, or TEST | |
7 | Message Number | PAK - 116 | Application component cannot be set for local packages | |
8 | Message Number | PAK - 116 | Application component cannot be set for local packages | |
9 | Message Number | PAK - 119 | Package interfaces must not contain the character string '&1' | |
10 | Message Number | PAK - 121 | Package interface &1 does not exist | |
11 | Message Number | PAK - 122 | Package interface &1 is locked for extensions | |
12 | Message Number | PAK - 128 | Development element cannot be added to package interface | |
13 | Message Number | PAK - 129 | Package &1 has no use access to package interface &2 | |
14 | Message Number | PAK - 140 | Structure package name or main package name must start with A-S or U-X | |
15 | Message Number | PAK - 142 | Package &1 already deleted in the buffer | |
16 | Message Number | PAK - 143 | Package interface &1 is already deleted from the buffer | |
17 | Message Number | PAK - 110 | Development element type &1 is not supported | |
18 | Message Number | PAK - 150 | The package hierarchy for package &1 contains errors; check package &2 | |
19 | Message Number | PAK - 151 | You cannot make package &1 a subpackage of package &2 | |
20 | Message Number | PAK - 152 | Package interface name cannot contain spaces | |
21 | Message Number | PAK - 160 | Virtual standard package interfaces do not contain any develop. objects | |
22 | Message Number | PAK - 161 | Filter package interfaces can only contain objects of type 'PCHK' | |
23 | Message Number | PAK - 183 | &1 &2 leads to a cyclical reference and cannot be included | |
24 | Message Number | PAK - 184 | Filter package interface &1 cannot be included | |
25 | Message Number | PAK - 185 | Virtual standard package interface &1 cannot be included | |
26 | Message Number | PAK - 197 | Superpackage &1 not allowed due to switches with varying assignments | |
27 | Message Number | PAK - 198 | Superpackage &1 not allowed due to switches with varying assignments | |
28 | Message Number | PAK - 199 | Superpackage &1 not allowed due to switches with varying assignments | |
29 | Message Number | PAK - 200 | Superpackage &1 not allowed due to switches with varying assignments | |
30 | Message Number | PAK - 418 | Choose a valid application component | |
31 | Message Number | PAK - 418 | Choose a valid application component | |
32 | Message Number | PAK - 045 | Package &1 begins with an invalid character (such as a digit) | |
33 | Message Number | PAK - 010 | Application component '&1' is not allowed (see long text) | |
34 | Message Number | PAK - 010 | Application component '&1' is not allowed (see long text) | |
35 | Message Number | PAK - 013 | Internal error in &1 / &2 | |
36 | Message Number | PAK - 013 | Internal error in &1 / &2 | |
37 | Message Number | PAK - 014 | Unexpected exception in &1 / &2 | |
38 | Message Number | PAK - 014 | Unexpected exception in &1 / &2 | |
39 | Message Number | PAK - 014 | Unexpected exception in &1 / &2 | |
40 | Message Number | PAK - 018 | Package &1 is its own superpackage | |
41 | Message Number | PAK - 034 | Package interface &1 already exists | |
42 | Message Number | PAK - 040 | Package &1 does not exist | |
43 | Message Number | PAK - 042 | Package &1 already exists | |
44 | Message Number | PAK - 044 | Character string '&1' not allowed as name of a package | |
45 | Message Number | PAK - 044 | Character string '&1' not allowed as name of a package | |
46 | Message Number | PAK - 044 | Character string '&1' not allowed as name of a package | |
47 | Message Number | PAK - 111 | Development element &1 &2 does not exist | |
48 | Message Number | PAK - 045 | Package &1 begins with an invalid character (such as a digit) | |
49 | Message Number | PAK - 045 | Package &1 begins with an invalid character (such as a digit) | |
50 | Message Number | PAK - 046 | Package &1 is reserved for local SAP classes | |
51 | Message Number | PAK - 050 | Enter application component for package &1 | |
52 | Message Number | PAK - 050 | Enter application component for package &1 | |
53 | Message Number | PAK - 055 | Package interface &1 does not exist | |
54 | Message Number | PAK - 088 | Application component '&1' does not exist | |
55 | Message Number | PAK - 088 | Application component '&1' does not exist | |
56 | Message Number | PAK - 093 | Use access from package &1 to package interface &2 already exists | |
57 | Message Number | PAK - 093 | Use access from package &1 to package interface &2 already exists | |
58 | Message Number | PAK - 095 | Package interface element &1 &2 does not exist in package interface &3 | |
59 | Message Number | PAK - 096 | Development element &1 &2 already exists in package interface &3 | |
60 | Message Number | PAK - 108 | Local packages must begin with 'TEST' | |
61 | Message Number | PAK - 110 | Development element type &1 is not supported |