Message Number list used by SAP ABAP Class CL_UC_AREA_GEN_BUILDING_PLAN (Cons Area: Generation per Cons Area)
SAP ABAP Class CL_UC_AREA_GEN_BUILDING_PLAN (Cons Area: Generation per Cons Area) is using
# | Object Type | Object Name | Object Description | Note |
---|---|---|---|---|
1 | Message Number | UCM0 - 031 | Data from table &1 must be converted to table &2 | |
2 | Message Number | UCM0 - 023 | Logical name &1 does not identify a generated structure of a cons area | |
3 | Message Number | UCM0 - 024 | Logical name &1 does not identify a generated table type of a cons area | |
4 | Message Number | UCM0 - 025 | Logical name &1 does not identify a generated view of a cons area | |
5 | Message Number | UCM0 - 026 | View &1 does not exist in the data dictionary (please check) | |
6 | Message Number | UCM0 - 027 | Consolidation area &1 is invalid (please check) | |
7 | Message Number | UCM0 - 028 | Object &1 (with object type &2) not generated for application &3 | |
8 | Message Number | UCM0 - 029 | Object &1 (with object type &2) is generated with class &4, not &3 | |
9 | Message Number | UCM0 - 030 | The format of object key &1 is invalid (please check) | |
10 | Message Number | UCM0 - 022 | Logical name &1 does not identify a generated table of a cons area | |
11 | Message Number | UCM0 - 032 | Data from tables that use structure &1 must be converted | |
12 | Message Number | UCM0 - 052 | Critical changes to object &1: | |
13 | Message Number | UCM0 - 053 | &1 &2 &3 &4 | |
14 | Message Number | UCM0 - 053 | &1 &2 &3 &4 | |
15 | Message Number | UCM0 - 077 | Table conversion in background job: Transaction will be stopped | |
16 | Message Number | UCM0 - 096 | Client/cons area &1 is currently being generated by user &2 | |
17 | Message Number | UCM0 - 106 | Table &1 converted to &2 | |
18 | Message Number | UCM0 - 151 | Database conversion may cause loss of data | |
19 | Message Number | UCM0 - 008 | The following error occurred while generating the object &1 &2 (&3): | |
20 | Message Number | UCM0 - 000 | Data basis/cons area: &1 &2 &3 &4 | |
21 | Message Number | UCM0 - 000 | Data basis/cons area: &1 &2 &3 &4 | |
22 | Message Number | UCM0 - 000 | Data basis/cons area: &1 &2 &3 &4 | |
23 | Message Number | UCM0 - 000 | Data basis/cons area: &1 &2 &3 &4 | |
24 | Message Number | UCM0 - 000 | Data basis/cons area: &1 &2 &3 &4 | |
25 | Message Number | UCM0 - 000 | Data basis/cons area: &1 &2 &3 &4 | |
26 | Message Number | UCM0 - 000 | Data basis/cons area: &1 &2 &3 &4 | |
27 | Message Number | UCM0 - 008 | The following error occurred while generating the object &1 &2 (&3): | |
28 | Message Number | UCM0 - 000 | Data basis/cons area: &1 &2 &3 &4 | |
29 | Message Number | UCM0 - 009 | Object &1 &2 was generated successfully | |
30 | Message Number | UCM0 - 009 | Object &1 &2 was generated successfully | |
31 | Message Number | UCM0 - 009 | Object &1 &2 was generated successfully | |
32 | Message Number | UCM0 - 011 | Logical name &1 does not identify a generated object of a cons area | |
33 | Message Number | UCM0 - 012 | Object with logical name &1 does not exist (see long text) | |
34 | Message Number | UCM0 - 014 | Several fields in basis table &1 of view &2 have the same check field | |
35 | Message Number | UCM0 - 018 | The transport object key &1 is invalid; see long text... | |
36 | Message Number | UCM0 - 021 | Type &1 is not a logical name (first character must be a "&2") |