SAP ABAP Message Class SC2M (C2 Server: Meta-Data Repository)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-CFG-RT (Application Component) Business Configuration Tools: Runtime
⤷ SC2_META_REP (Package) C2 Server Meta-Data Repository
⤷ BC-CFG-RT (Application Component) Business Configuration Tools: Runtime
⤷ SC2_META_REP (Package) C2 Server Meta-Data Repository
Attributes
Message class | SC2M | |
Short Description | C2 Server: Meta-Data Repository | |
Changed On | 20041208 | |
Last Changed At | 183204 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | Business object &1 does not exist (&2) | The short text describes the object sufficiently | |
2 | 001 | Business configuration object &1 does not exist | The short text describes the object sufficiently | |
3 | 002 | You cannot use nodes in foreign business objects | The short text describes the object sufficiently | |
4 | 003 | Property &1 is not defined (&2, &3, &4) | The short text describes the object sufficiently | |
5 | 004 | Exit &1 is not defined (&2, &3, &4) | The short text describes the object sufficiently | |
6 | 005 | No authorization (Object &1, Object type &2, Object name &3, Activity &4) | The short text describes the object sufficiently | |
7 | 006 | Invalid value &1 for property &2 (&3 &4) | The short text describes the object sufficiently | |
8 | 007 | Business configuration object &1 is inconsistent | The short text describes the object sufficiently | |
9 | 008 | Class &1 does not have interface &2 | The short text describes the object sufficiently | |
10 | 009 | No interface is defined (&2, &3) for Exit &1 | The short text describes the object sufficiently | |
11 | 010 | No active Nametab for &1 | The short text describes the object sufficiently | |
12 | 011 | Association &1 is uonknown (&2, &3, &4) | The short text describes the object sufficiently | |
13 | 012 | Field &1 has invalid value &2 for the include/exclude attribute | The short text describes the object sufficiently | |
14 | 013 | Field &1 has invalid value &2 for the operator | The short text describes the object sufficiently | |
15 | 014 | Only the first value can be set in a field &1 with operator &2 | The short text describes the object sufficiently | |
16 | 015 | The field &1 is not known at node &2 | The short text describes the object sufficiently | |
17 | 016 | Two values must be set in field &1 with operator &2 | The short text describes the object sufficiently | |
18 | 017 | The first value must be set in field &1 with operator &2 | The short text describes the object sufficiently | |
19 | 018 | Field &1 uses the undefined parameter &2 | The short text describes the object sufficiently | |
20 | 019 | Field &1 uses the parameter &2, but it belongs to field &3 | The short text describes the object sufficiently | |
21 | 020 | Unknown Query Type &1 | The short text describes the object sufficiently | |
22 | 021 | Class '&1' &2 instantiation error | The short text describes the object sufficiently | |
23 | 022 | Parameter '&1' was not filled | The short text describes the object sufficiently | |
24 | 023 | Operator '&1' is not known | The short text describes the object sufficiently | |
25 | 024 | The requested structure type could not be created: &1 | The short text describes the object sufficiently | |
26 | 025 | Type &1 was not found | The short text describes the object sufficiently | |
27 | 026 | Text fields are not allowed in the condition (field &1 at node &2) | The short text describes the object sufficiently | |
28 | 027 | The requested table type could not be created: &1 | The short text describes the object sufficiently | |
29 | 028 | Node &1 must either be a code or have key fields | The short text describes the object sufficiently | |
30 | 029 | Parameter &2 was used twice in field &1 | The short text describes the object sufficiently | |
31 | 030 | Spaces are not allowed in the name: '&1' | The short text describes the object sufficiently | |
32 | 031 | Parameter names cannot be lower case: '&1' | The short text describes the object sufficiently | |
33 | 032 | Special characters are not allowed in the name: '&1' | The short text describes the object sufficiently | |
34 | 033 | Parameter name cannot start with a numeral: '&1' | The short text describes the object sufficiently | |
35 | 034 | The parameter name is not allowed: '&1' | The short text describes the object sufficiently | |
36 | 035 | The parameter name is too long: '&1' | The short text describes the object sufficiently | |
37 | 036 | Class '&1' does not exist | The short text describes the object sufficiently | |
38 | 037 | &1 is not a class | The short text describes the object sufficiently | |
39 | 038 | Key fields cannot be strings: &1 | The short text describes the object sufficiently | |
40 | 039 | Field name '&1' is too long (maximum length &2 characters) | The short text describes the object sufficiently | |
41 | 040 | Unknown Time-Dependency Type '&1' | The short text describes the object sufficiently | |
42 | 041 | No start date field name for time-dependent access | The short text describes the object sufficiently | |
43 | 042 | No end date field name for time-dependent access | The short text describes the object sufficiently | |
44 | 043 | No start date parameter name for time-dependent access | The short text describes the object sufficiently | |
45 | 044 | Text field (&1) cannot be used as a term | The short text describes the object sufficiently | |
46 | 045 | Key field (&1) cannot be used as a term | The short text describes the object sufficiently | |
47 | 046 | You cannot create terms in time-dependent nodes | The short text describes the object sufficiently | |
48 | 047 | Field (&1) cannot be used as term (not character type) | The short text describes the object sufficiently | |
49 | 048 | Time-dependent node &1 has &2 field(s) for the start value, instead of &3 | The short text describes the object sufficiently | |
50 | 049 | The time-dependent node &1 has &2 field(s) for the end value, not &3 | The short text describes the object sufficiently | |
51 | 050 | Field (&1) can only be time-dependent if the node is time-dependent | The short text describes the object sufficiently | |
52 | 051 | Default value not allowed for field &1, it is not a key field | The short text describes the object sufficiently | |
53 | 052 | Default value not allowed for field &1, because &2 has no default value | The short text describes the object sufficiently | |
54 | 053 | Parameter &1 already exists in field &2 | The short text describes the object sufficiently | |
55 | 054 | Node &1 must contain the key fields of its parent node &2 | The short text describes the object sufficiently | |
56 | 055 | The type of key field &1 at node &2 does not match parent &3 | The short text describes the object sufficiently | |
57 | 100 | One or more configuration objects in request are not active | Space: object requires documentation | |
58 | 101 | Configuration object & is not active | The short text describes the object sufficiently |
History
Last changed on/by | 20041208 | SAP | |
SAP Release Created in | 700 |