MDG_MDF - Stammdaten: Nachrichten

The following messages are stored in message class MDG_MDF: Stammdaten: Nachrichten.
It is part of development package MDG_MDF0 in software component CA-MDG-AF. This development package consists of objects that can be grouped under "Master Data".
Message Nr
Message Text
000Program error(s)
001No documentation available
003Value is not numeric
004Customizing settings are inconsistent
008Definition of Field &1 is inconsistent
015&1 is not a valid value for &2
016The value &2 is invalid for characteristic &1
017The value &2 is invalid for characteristic &1
020&1: Fixed Values cannot be changed
021&1&2&3&4
024Characteristic &3: The value is too long (&1 is greater than &2)
027The value &2 is invalid for characteristic &1 (character &3)
028Entry is required for for characteristic &1
030The value &2 is invalid for characteristic &1 (character &3)
036Unknown application: &1
037Enter a numeric value (field name &1, &2)
038Conversion not possible (field name &1, &2)
041Conversion not possible; number of decimal places does not match currency
042Conversion not possible; number of decimal places does not match unit
043
048Conversion is not possible; number of decimal places is invalid
050A general exception in the MDF layer has occured
051A general exception in the MDF DB layer has occured
052Error trying to delete data from table &1
053Error trying to delete data using condition &1 &2 &3 &4
075Field &1 is still registered and cannot be deleted
078Value &3 is invalid for &1 (&2) - ALPHA conversion
079Value &3 is invalid for &1 (&2) - wrong date
080Value &3 is invalid for &1 (&2) - wrong time
096Modify &1 setting status &2 for change request &3: sy-subrc = &4
099************ Messages for Characteristic Registration/Management ******
100Field &1 already exists under a different domain
101Field name &1 is already reserved for role &2
102Create fields with role &2 using field name &3
104Role &1 is invalid; see long text
105A data element does not exist for field &1
107DDIC structures are being regenerated
108DDIC structures are being regenerated
109DDIC structures are being regenerated
110Regenerating DDIC structures (change in role &1)
111Time stamp of imported role &1 has been raised
113Field &1 has the wrong role assignment; see long text
114In application area &4, field &1 is already linked to basis field &3
115Field &1 cannot be a node in hierarchies of characteristic &2
118The key of field &1 is too long
120Field &1 does not exist
122The background job must finish first
123An error occurred during the generation; see the log
125The area must contain the required characteristic &1
126The area uses an unknown characteristic &1
127Definition of role &1 has changed
128Definition of characteristic &1 has changed
134&4 records copied to table &3
137Unable to assign data element &1
138Key figure &1 (type &2) has no unit field
140Field &1 does not exist; see long text
141Input value &1 is invalid
145Properties of validity check have been changed for field &1
150=========== Area UGMDCHK0: 150-199 ==================================
199********** Messages for the Transport Tool *****************
200No information exists for table &1
201Characteristic &1 does not exist
202Characteristic &1 has no sub-structure &2
203Generating tables for characteristic &1
204Table &2 does not contain the SIDs for characteristic &1
205Internal error &1 &2 &3 &4
206Cannot determine SID table for characteristic &1
207Field with SID &1 does not exist
208No SID exists for the value &1 of characteristic &2
209&2: Unable to determine the value with SID &1
212Objects belonging to transport object &1 can not be maintained
213Cannot create field &1
214Field &1 created
215Could not create or determine an SID for value &1 of characteristic &2
216Cannot determine which field in the original system has the SID &1
217Field &1 does not exist
218Complex selection conditions are not supported
219Cannot determine which field in the original system has the SID &1
220Field &1 does not exist
221Unable to create the combination characteristic
224Application area &1/&2 will not be copied
225Value SID for invalid field name with SID 0
227Table &1 does not exist
228Request type &1 not supported
229Table &1 is no longer in use
237Unnamed object &1 has the name &2 in the target system
238Object name of field name &1 differs from the target system (&2 vs. &3)
239Customizing entries have been added to transport request &1
299************** Messages for Hierarchy Maintenance *****************+
300Leaf &1 belongs to type &2
301Hierarchies can only be top nodes
302No hierarchies are allowed for characteristic &1
304Hierarchy &1 has more than one root node
305Hierarchy &1 has more than one root node
306Delta leaf &1 cannot be deleted manually
308Error while saving a hierarchy and/or link attrubutes
309Data is inconsistent in hierarchy table &2
310Error while reading the metadata for database table &1
311&1 is already used in hierarchies; assignment not possible
312&1 is a delta node; assignment not possible
314Entry is invalid
315Only one hierarchy is allowed for characteristic &1
316Invalid higher-level characteristic
317Invalid entry of a higher-level characteristic
320No more entries are permitted under &1
321&1 is not a valid hierarchy entry
322&2 cannot be inserted under &1
323Node &1 is underneath itself in hierarchy &2
327Conversion of hierarchy data is necessary - see long text
328Error while writing hierarchies in system &3 - see long text
399************** Messages for ENQUEUE/DEQUEUE Method *******************
400Parameter for ENQUEUE/DEQUEUE contains an error
402Values for characteristic &2 already locked by user &1
403System error while setting the lock
404&2 &3 already locked by user &1
405DDIC structures already being generated by user &1
409**** More messages for characteristic registration/management ******
411Error while replicating data - see long text
418Field &1: Data conversion is necessary
Privacy Policy