RECNNT - K�ndigung
The following messages are stored in message class RECNNT: K�ndigung.
It is part of development package RE_CN_NT in software component RE-FX-CN. This development package consists of objects that can be grouped under "RE: Notice".
It is part of development package RE_CN_NT in software component RE-FX-CN. This development package consists of objects that can be grouped under "RE: Notice".
Message Nr ▲ | Message Text |
---|---|
001 | Notice &1 &2 does not exist |
002 | Giving notice is allowed only for active contracts |
003 | Giving notice is not allowed in create mode |
004 | &1 &2 is already assigned to notice &3 |
005 | &1 &2 is already assigned to notice &4 by means of object group &3 |
006 | &1 &2 is already assigned to notice &4 by means of object group &3 |
007 | An object from object group &1 is already assigned to notice &2 |
008 | There are no assigned objects in notice &1 |
009 | Object &1 was not found in the list of assigned objects |
010 | Assigning of objects is not allowed for this notice type |
011 | Notice is active - you are not allowed to change object assignments |
012 | Activating makes no sense - no objects have been assigned |
013 | Object &1 is not assigned to the contact |
014 | Notice date is not in validity period of object &1 |
015 | &1: notice is already active |
016 | &1: there are no active notices |
017 | The date "Notice on" must be between contract start and contract end |
018 | It is not possible to activate a rejected notice |
019 | The notice period was not adhered to |
020 | You are not allowed to delete an active notice |
021 | Not possible to activate notice if it was rescinded |
022 | Notice was given on &1 on &2 - assignment &3 not possible |
023 | Caution: there is a memo for the notice rule |
024 | Notice date &1 is before requested notice date &2 |
025 | Requested notice date &1 is before contract start date &2 |
026 | Reason for notice &1 (&2) is obsolete |
027 | Reason for rejection &1 (&2) is obsolete |