/SAPCND/SY_CONFIG - Meldungen f�r System-Konfiguration

The following messages are stored in message class /SAPCND/SY_CONFIG: Meldungen f�r System-Konfiguration.
 It is part of development package /SAPCND/SYSTEM_CONFIGURATION in software component AP-PRC-CON. This development package consists of objects that can be grouped under "SAP Internal: System Configuration for Condition Technique".
Message Nr ▲
Message Text
000* Field Check API Usage *
001Field value for field &1 in structure &2 (usage &3) is obsolete or legacy
002Field name &1 for usage &2 does not exist in the global field catalog
003Attribute type for field name &1 in usage &2 must be 'Usage'
004Usage field &1 references nonexistent usage &2
005Field item for field &1 of usage &2 is not unique
006Specify a data element name for field &1 for usage &2
007Field SCALE_TYPE is not a part of scale for usage &1
008Data fields for field &1, usage &2 must remain empty
009Number of exernal fields must be >= 1 (usage &1, scale base type &2)
010Variables scale field &1 (usage &2) unknown
011Field SCALE_TYPE does not have data element /SAPCND/SCALE_TYPE
012Field name &1 (usage &2) may have a maximum of 16 characters
013Data field &1 for key field &2, usage &3 has no valid value
014Adapt all condition tables for usage &1
015The required enhancement/change of usage &1 is not possible
016Usage &1 has &2 dim. scales and no scale fields
017Usage &1 has &2 dim. scales and no scale base types
018Usage &1 has no scales but has scale fields
019Usage &1 has no scales but has scale base types
020Usage field &1 has no usage assigned
021Usage &1 is still registered with application &2
050* Field Check API Application *
051Field value for field &1 in structure &2 (appl. &3) is obsolete or legacy
052STRUCT_NOT_USED = ' ' for application &1 is only supported as legacy
053Field value SUPER_KAPPL = 'SUP' in appl. &1 only supported as legacy
054Field &1 is still registered for application &2
055Registered task &1 still exists for application &2
056GEN_OBJ_INFO = ' ' in /SAPCND/T681A for Application &1 is legacy
100* Field Check API Task *
101SCALEEVL_EXIST <> ' ' for &1 &2 is only supported as legacy
102Field value for field &1 in structure &2 (&3 &4) is obsolete or legacy
103Field DET_ENGINE_TYPE (&1 &2) should not be initial
104Field USE_NAMESPACE (&1 &2) should be flagged
105Signature for task (&1 &2) must be filled with two digits
106Condition table ID &1 still exists for task &2
107ABAP determination for &1 &2 is now only supported as legacy
150* Field Check API Global Field Catalog *
151Attribute type for field name &1 must be &2
152Field name &1 may have a maximum of 16 characters
153Data field &1 for key field &2 does not have a valid value
154Field value for field &1 in structure &2 is obsolete or legacy
155Data element &1 for field &2 is not registered in the field catalog
156Data element &1 does not exist actively in the DDIC
157Field name for data element &1 does not exist in the global field catalog
158Data element &1 from dependecy relationship is not registered globally
159Field name &1 from relationship relation is not registered globally
160Data element &1 cannot be in a dependency relationship
161External/internal relationship of field &1 to field &2 is not possible
162Dependeny of data element &1 (fields &2 &3) is not possible
163Dependency of data element &1 to application (fields &2 &3) questionable
164Field name &1 cannot be changed as application field in this environment
165Field name &1 cannot be changed as usage field in this environment
166Field &1 is a condition technqiue field
167Data element &1 is still being used in application &2
168Data element &1 is still being used in usage &2
169Data element &1 is used for condition technique fields
170Field &1 is still being used as an application field for application &2
200* Authorization Check *
201No change authorization (see SU53)
202Condition technique configuration cannot be changed here
250* TADIR Registration *
251Object &1 &2 &3 is already registered (OSS Note 687921)
Privacy Policy