TN_UNINST - Nachrichten f�r Add-On Deinstallation
The following messages are stored in message class TN_UNINST: Nachrichten f�r Add-On Deinstallation.
It is part of development package SPAM_UNINST in software component BC-UPG-OCS-SPA. This development package consists of objects that can be grouped under "".
It is part of development package SPAM_UNINST in software component BC-UPG-OCS-SPA. This development package consists of objects that can be grouped under "".
Message Nr ▲ | Message Text |
---|---|
001 | The defined queue is not a simulation queue. |
002 | No Add-On selected for the simulation |
003 | The simulation of the uninstallation of add-on &1 rel.&2 was finished |
004 | No SPAM/SAINT authorization, only display functions are available! |
005 | The simulation is not finished yet |
006 | The simulation run was finished, check the results |
007 | There is no GTABKEY entry for table &1, key &2 |
008 | There is no maintenance tool available for object &1 |
009 | The GTABKEY entry for table &1, key &2 cannot be displayed |
010 | Internal error: &1 &2 &3 &4 |
011 | &1&2&3&4 |
012 | No Add-On was selected |
013 | The simulation run finished with errors. Check the action log. |
014 | Action cancelled by user |
015 | Select at least one transport type |
016 | Changes for the Transport Configuration &1 were not saved |
017 | No Transports found with the Selection Criteria |
018 | Attribute &1 for SWCV &1 &3 could not be stored |
019 | Class &1 is not a valid uninstallation plugin class |
020 | Wrong combination of proposal ("&1") and object handling ("&2") |
021 | The object type &1 &2 is not yet supported |
022 | The object type &1 &2 is already supported |
023 | The handling of the object type &1 &2 is defined with operation "&3" |
024 | The object type &1 &2 is not yet supported |
025 | The object type &1 &2 is not yet supported |
026 | The handling of this object is defined with the operation "&1" |
027 | The handling of this object is not yet supported |
028 | The handling of this object is not yet supported |
029 | The handling of this object is defined with the operation "Ignore" |
030 | The handling of this table content is not yet defined |
031 | The handling of this table content is already defined |
032 | The handling of this table content is already defined |
033 | The handling of this table content may be adjusted |
034 | The handling of this table content is not yet defined |
035 | The handling of this table content is not yet defined |
036 | The handling of this table content should be adjusted |
037 | The handling of this object is defined with the operation "Delete" |
040 | The configuration was successfully included into request/task &1 |