SAP ABAP Message Class /SAPCND/SY_CONFIG (Messages for System Configuration)
Basic Data
Hierarchy
☛ SAP_AP (Software Component) SAP Application Platform
   ⤷ AP-PRC-CON (Application Component) Condition Technique
     ⤷ /SAPCND/SYSTEM_CONFIGURATION (Package) SAP Internal: System Configuration for Condition Technique
Attributes
Message class /SAPCND/SY_CONFIG
Short Description Messages for System Configuration  
Changed On 20080626 
Last Changed At 095056 
Messages
# Message Message Short Text Documentation status Authorization check
1 000 * Field Check API Usage * The short text describes the object sufficiently
2 001 Field value for field &1 in structure &2 (usage &3) is obsolete or legacy The short text describes the object sufficiently
3 002 Field name &1 for usage &2 does not exist in the global field catalog The short text describes the object sufficiently
4 003 Attribute type for field name &1 in usage &2 must be 'Usage' The short text describes the object sufficiently
5 004 Usage field &1 references nonexistent usage &2 The short text describes the object sufficiently
6 005 Field item for field &1 of usage &2 is not unique The short text describes the object sufficiently
7 006 Specify a data element name for field &1 for usage &2 The short text describes the object sufficiently
8 007 Field SCALE_TYPE is not a part of scale for usage &1 The short text describes the object sufficiently
9 008 Data fields for field &1, usage &2 must remain empty The short text describes the object sufficiently
10 009 Number of exernal fields must be >= 1 (usage &1, scale base type &2) The short text describes the object sufficiently
11 010 Variables scale field &1 (usage &2) unknown The short text describes the object sufficiently
12 011 Field SCALE_TYPE does not have data element /SAPCND/SCALE_TYPE The short text describes the object sufficiently
13 012 Field name &1 (usage &2) may have a maximum of 16 characters The short text describes the object sufficiently
14 013 Data field &1 for key field &2, usage &3 has no valid value The short text describes the object sufficiently
15 014 Adapt all condition tables for usage &1 Space: object requires documentation
16 015 The required enhancement/change of usage &1 is not possible Space: object requires documentation
17 016 Usage &1 has &2 dim. scales and no scale fields The short text describes the object sufficiently
18 017 Usage &1 has &2 dim. scales and no scale base types The short text describes the object sufficiently
19 018 Usage &1 has no scales but has scale fields The short text describes the object sufficiently
20 019 Usage &1 has no scales but has scale base types The short text describes the object sufficiently
21 020 Usage field &1 has no usage assigned The short text describes the object sufficiently
22 021 Usage &1 is still registered with application &2 The short text describes the object sufficiently
23 050 * Field Check API Application * The short text describes the object sufficiently
24 051 Field value for field &1 in structure &2 (appl. &3) is obsolete or legacy The short text describes the object sufficiently
25 052 STRUCT_NOT_USED = ' ' for application &1 is only supported as legacy The short text describes the object sufficiently
26 053 Field value SUPER_KAPPL = 'SUP' in appl. &1 only supported as legacy The short text describes the object sufficiently
27 054 Field &1 is still registered for application &2 The short text describes the object sufficiently
28 055 Registered task &1 still exists for application &2 The short text describes the object sufficiently
29 100 * Field Check API Task * The short text describes the object sufficiently
30 101 SCALEEVL_EXIST <> ' ' for &1 &2 is only supported as legacy The short text describes the object sufficiently
31 102 Field value for field &1 in structure &2 (&3 &4) is obsolete or legacy The short text describes the object sufficiently
32 103 Field DET_ENGINE_TYPE (&1 &2) should not be initial The short text describes the object sufficiently
33 104 Field USE_NAMESPACE (&1 &2) should be flagged The short text describes the object sufficiently
34 105 Signature for task (&1 &2) must be filled with two digits The short text describes the object sufficiently
35 106 Condition table ID &1 still exists for task &2 The short text describes the object sufficiently
36 107 ABAP determination for &1 &2 is now only supported as legacy The short text describes the object sufficiently
37 150 * Field Check API Global Field Catalog * The short text describes the object sufficiently
38 151 Attribute type for field name &1 must be &2 The short text describes the object sufficiently
39 152 Field name &1 may have a maximum of 16 characters The short text describes the object sufficiently
40 153 Data field &1 for key field &2 does not have a valid value The short text describes the object sufficiently
41 154 Field value for field &1 in structure &2 is obsolete or legacy The short text describes the object sufficiently
42 155 Data element &1 for field &2 is not registered in the field catalog The short text describes the object sufficiently
43 156 Data element &1 does not exist actively in the DDIC The short text describes the object sufficiently
44 157 Field name for data element &1 does not exist in the global field catalog The short text describes the object sufficiently
45 158 Data element &1 from dependecy relationship is not registered globally The short text describes the object sufficiently
46 159 Field name &1 from relationship relation is not registered globally The short text describes the object sufficiently
47 160 Data element &1 cannot be in a dependency relationship The short text describes the object sufficiently
48 161 External/internal relationship of field &1 to field &2 is not possible The short text describes the object sufficiently
49 162 Dependeny of data element &1 (fields &2 &3) is not possible The short text describes the object sufficiently
50 163 Dependency of data element &1 to application (fields &2 &3) questionable The short text describes the object sufficiently
51 164 Field name &1 cannot be changed as application field in this environment The short text describes the object sufficiently
52 165 Field name &1 cannot be changed as usage field in this environment The short text describes the object sufficiently
53 166 Field &1 is a condition technqiue field The short text describes the object sufficiently
54 167 Data element &1 is still being used in application &2 The short text describes the object sufficiently
55 168 Data element &1 is still being used in usage &2 The short text describes the object sufficiently
56 169 Data element &1 is used for condition technique fields The short text describes the object sufficiently
57 170 Field &1 is still being used as an application field for application &2 The short text describes the object sufficiently
58 200 * Authorization Check * The short text describes the object sufficiently
59 201 No change authorization (see SU53) The short text describes the object sufficiently
60 202 Condition technique configuration cannot be changed here The short text describes the object sufficiently
61 250 * TADIR Registration * The short text describes the object sufficiently
62 251 Object &1 &2 &3 is already registered (OSS Note 687921) The short text describes the object sufficiently
History
Last changed on/by 20080626  SAP 
SAP Release Created in   500