MFLE_CHANGEDOC -
The following messages are stored in message class MFLE_CHANGEDOC: .
It is part of development package MFLE_CHANGEDOC in software component LO-MD-MM. This development package consists of objects that can be grouped under "Tools for change doc access".
It is part of development package MFLE_CHANGEDOC in software component LO-MD-MM. This development package consists of objects that can be grouped under "Tools for change doc access".
Message Nr ▲ | Message Text |
---|---|
000 | Split by conversion date: old and new objectclass must be identical |
001 | Old and new objectclass cannot be identical |
002 | Old and new structure cannot be identical, SPACE if no conversion needed |
003 | Name of material field must be entered when structures are specified |
004 | Old OBJECTCLASS &1 is also in new OBJECTCLASS, this is not possible |
005 | New OBJECTCLASS &1 is also in old OBJECTCLASS, this is not possible |
006 | Name of material field cannot be entered when no structures are specified |
007 | When conversion is needed, both old and new structure must be filled |
008 | No structures can be specified if single field is to be converted |
009 | Found orphaned tabkey metadata without header entry |
010 | Found orphaned field metadata without tabkey entry |
011 | Error during final data check before saving |
012 | Objectclas missing in metadata header |
013 | Old objectclas missing in metadata header |
014 | Obsolete metadata header: no conversion on any level defined |
015 | Header is inconsistent, tabkey level cannot be evaluated |
016 | Tabkey is inconsistent, field level cannot be evaluated |
017 | Obsolete tabkey metadata: no conversion on any level defined |
018 | Obsolete field metadata: no conversion defined |
019 | Old and new structures do not have similar list of fields |
020 | Inconsistent metadata: &1 &2 &3 |
021 | Named application specific adapter does not implement needed interface |
022 | Switched to long is not valid when no structures are specified |
023 | Specific adapter required (structure not character like/noot in DDIC) |
024 | Table name missing in metadata for table keys |
025 | Field name missing in metadata for field values |
026 | TABNAME must be a table with key, new structure must contain this key |