SAFF_CORE - Message class for SAFF_CORE
The following messages are stored in message class SAFF_CORE: Message class for SAFF_CORE.
It is part of development package SAFF_CORE in software component BC-DWB-TOO. This development package consists of objects that can be grouped under "ABAP file formats: core functionality".
It is part of development package SAFF_CORE in software component BC-DWB-TOO. This development package consists of objects that can be grouped under "ABAP file formats: core functionality".
Message Nr ▲ | Message Text |
---|---|
000 | &1&2&3&4 |
001 | An error has occurred in the AFF framework |
002 | Object not found in system |
010 | Object handler &1 can not handle object &2 (&3) |
011 | Object &1 of type &2 doesn't exist in the system |
012 | File name &1 doesn't match the pattern &2 |
013 | Object &1 (&2) of type &3 (&4) doesn't exist in the system |
014 | File with name &1 was already serialized for object &2 (&3) |
015 | Object &1 of type &2 doesn't exist in table TADIR |
016 | No object handler found for type &1 |
017 | Object type &1 (&2) is not supported from object handler &3 |
018 | No object handler found for type &1 (&2) |
019 | Could not deserialize sub files. Root object &1 of type &2 doesn't exist |
020 | Devclass is initial for object &1 of type &2 |
021 | Devclass &1 doesn't exists in the system |
022 | File name for object &1 of type &2 could not be determined |
023 | Could not find a sub object handler for sub type &1 in handler &2 |
024 | Could not find a R3TR object of type &1 for the object &2 (&3) |
025 | Object Directory Entry &1 will be ignored |
026 | Serialization for R3TR &1 &2 started |
027 | Serialization for R3TR &1 &2 ended |
028 | Deserialization for R3TR &1 &2 started |
029 | Deserialization for R3TR &1 &2 ended |
030 | Sub objects are supplied but the object &1 doesn't support sub objects |
031 | Deletion for R3TR &1 &2 started |
032 | Deletion for R3TR &1 &2 ended |
033 | Could not read master language. Object &1(&2) doesn't exist in tadir |
034 | Could not save translations. Object &1 of type &2 doesn't exist |
100 | The type &1 is not supported by the generator |
101 | The node &1 is not supported by the generator |
102 | The JSON type &1 is not supported by the XSLT writer |
200 | Could not read the content for object &1 of type &2 |
201 | Could not deserialize textelement |
300 | Translations not yet implemented for object type &1 |