PLM_AUDIT_CGPL - Audit: Notifs from Generic Tool with Audit Specific Text

The following messages are stored in message class PLM_AUDIT_CGPL: Audit: Notifs from Generic Tool with Audit Specific Text.
It is part of development package PLM_AUDIT_CORE in software component CA-AUD. This development package consists of objects that can be grouped under "Audit Management - General Core Functions".
Message Nr
Message Text
000***General messages for the application***
001Audit component & already exists
002Audit component & does not exist
003Enter a unique key
004Enter a new and unique key
005The key already exists
008For the key of the audit component, choose form &
009Object &1 is currently being processed by &2
010Superordinate audit component & cannot be changed
011Superordinate audit component & is not open
012Adjacent audit component & cannot be changed
013There are subordinate audit components
014Choose an end date that is after the start date
015Person responsible & does not exist
020Internal error: Function module was not called correctly
101&1 &2: You do not have authorization to make changes
102&1 &2: You do not have authorization to display
103&1 &2: You do not have authorization to delete
104&1 &2: You do not have authorization to create
201Status locked is active - changes cannot be made
202Subordinate audit component & is not yet completed
203Superordinate audit component & has already been completed
204Superordinate audit component & has not been released
205Superordinate audit component & has already been completed
206&1 &2: Starting to set the status &3
207&1 &2: Starting reset of the status &3
208&1 &2: Deletion started
209&1 &2 will be moved
210Component &1 &2 has been deleted
211&1 &2: Status &3 has been set
212&1 &2: Status &3 has been deleted
213Object &1 &2 cannot be deleted
214Object &1 is still used by object &2 and can't be deleted
215Object &1 &2 cannot be deleted because it has subnodes
300Customizing settings for long texts have not yet been maintained
700*** Messages DB accesses CGPL tables ***
701Error in parameter passing
702Entry could not be found in database
Privacy Policy