Message Number list used by SAP ABAP Class CL_UA_METADATA (Metadata of a Costing Solution)
SAP ABAP Class CL_UA_METADATA (Metadata of a Costing Solution) is using
# | Object Type | Object Name | Object Description | Note |
---|---|---|---|---|
1 | Message Number | UAS - 102 | Field &1 is not contained in any local attribute group for object type &2 | |
2 | Message Number | UAS - 026 | No database tables for type &1 | |
3 | Message Number | UAS - 026 | No database tables for type &1 | |
4 | Message Number | UAS - 031 | Field &1 is already used in type &2 | |
5 | Message Number | UAS - 032 | Field &1 is already used by type &3 in type &2 | |
6 | Message Number | UAS - 039 | Type &1 was changed | |
7 | Message Number | UAS - 041 | Type &1 was created | |
8 | Message Number | UAS - 044 | Data basis &1 contains inconsistencies and cannot be used | |
9 | Message Number | UAS - 048 | Data loss - column &1 of type &2 still contains &3 data records | |
10 | Message Number | UAS - 055 | Field &1 is not a key figure | |
11 | Message Number | UAS - 056 | Field &1 is not contained in type &2 | |
12 | Message Number | UAS - 080 | Dependent field &1 was automatically added | |
13 | Message Number | UAS - 095 | Field name &1 is too long. A maximum of 16 characters are possible | |
14 | Message Number | UAS - 097 | Field '&1' exists in two attribute sets | |
15 | Message Number | UAS - 100 | Field '&1' is not contained in any attribute group for object type '&2' | |
16 | Message Number | UAS - 101 | Required fields missing for definition of type '&1' | |
17 | Message Number | UAS - 000 | Type &1 is unknown | |
18 | Message Number | UAS - 103 | Field '&1' exists in two local attribute groups | |
19 | Message Number | UAS - 105 | Field &1 is already used in type &2 | |
20 | Message Number | UAS - 108 | Field '&1' has different visibility from related unit field '&2' | |
21 | Message Number | UAS - 109 | Field '&1' has different visibility from higher-level field '&2' | |
22 | Message Number | UAS - 110 | Additional attribute groups were assigned to object type &1 | |
23 | Message Number | UAS - 111 | A link type requires at least one key figure in field catalog | |
24 | Message Number | UAS - 111 | A link type requires at least one key figure in field catalog | |
25 | Message Number | UAS - 131 | System setting does not allow you to add type &1 | |
26 | Message Number | UAS - 131 | System setting does not allow you to add type &1 | |
27 | Message Number | UAS - 132 | System setting does not allow you change the assignment | |
28 | Message Number | UAS - 133 | System setting does not allow the change | |
29 | Message Number | UAS - 133 | System setting does not allow the change | |
30 | Message Number | UAS - 134 | System setting does not allow the change for field &1 | |
31 | Message Number | UAS - 136 | System setting prevents changes to sender/receiver relationship | |
32 | Message Number | UAS - 136 | System setting prevents changes to sender/receiver relationship | |
33 | Message Number | UAS - 024 | Deleting type &1 results in loss of &2 data records | |
34 | Message Number | UAS - 000 | Type &1 is unknown | |
35 | Message Number | UAS - 000 | Type &1 is unknown | |
36 | Message Number | UAS - 000 | Type &1 is unknown | |
37 | Message Number | UAS - 000 | Type &1 is unknown | |
38 | Message Number | UAS - 000 | Type &1 is unknown | |
39 | Message Number | UAS - 000 | Type &1 is unknown | |
40 | Message Number | UAS - 000 | Type &1 is unknown | |
41 | Message Number | UAS - 000 | Type &1 is unknown | |
42 | Message Number | UAS - 000 | Type &1 is unknown | |
43 | Message Number | UAS - 000 | Type &1 is unknown | |
44 | Message Number | UAS - 000 | Type &1 is unknown | |
45 | Message Number | UAS - 000 | Type &1 is unknown | |
46 | Message Number | UAS - 000 | Type &1 is unknown | |
47 | Message Number | UAS - 002 | Field &1 is unknown | |
48 | Message Number | UAS - 002 | Field &1 is unknown | |
49 | Message Number | UAS - 002 | Field &1 is unknown | |
50 | Message Number | UAS - 025 | Cannot delete because tables contain data | |
51 | Message Number | UAS - 018 | Posting level cannot be changed because data already exists | |
52 | Message Number | UAS - 017 | Only one of this type can exist per data basis | |
53 | Message Number | UAS - 016 | Type &1 already exists. Choose another name | |
54 | Message Number | UAS - 012 | Not possible to change column "&1" of type "&2" | |
55 | Message Number | UAS - 009 | No BW System was yet assigned | |
56 | Message Number | UAS - 007 | Column &1 cannot be deleted | |
57 | Message Number | UAS - 005 | Internal program error: &1 | |
58 | Message Number | UAS - 005 | Internal program error: &1 | |
59 | Message Number | UAS - 005 | Internal program error: &1 | |
60 | Message Number | UAS - 005 | Internal program error: &1 | |
61 | Message Number | UAS - 005 | Internal program error: &1 | |
62 | Message Number | UAS - 002 | Field &1 is unknown | |
63 | Message Number | UAS - 002 | Field &1 is unknown | |
64 | Message Number | UXB - 001 | Not exactly specified exception &1 | |
65 | Message Number | UXB - 001 | Not exactly specified exception &1 | |
66 | Message Number | UXB - 001 | Not exactly specified exception &1 | |
67 | Message Number | UXB - 001 | Not exactly specified exception &1 | |
68 | Message Number | UXB - 001 | Not exactly specified exception &1 | |
69 | Message Number | UXB - 001 | Not exactly specified exception &1 | |
70 | Message Number | UXB - 001 | Not exactly specified exception &1 | |
71 | Message Number | UXB - 001 | Not exactly specified exception &1 |