HRPAYDE_KGID - Nachrichtenklasse zum IdNr.-Kontrollverfahren Kindergeld

The following messages are stored in message class HRPAYDE_KGID: Nachrichtenklasse zum IdNr.-Kontrollverfahren Kindergeld.
It is part of development package P01O_KGIDNR in software component PY-DE-PS. This development package consists of objects that can be grouped under "Child Allowance ID No. Control Procedure".

Message Nr ▲	Message Text
000	Child &1 (ID No.: &2): Several notifications with the same period exist.
001	Child &1 (ID No.: &2): Two IT0118 records lead to the same not. period.
002	Child &1 (ID No.: &2): Colliding notification periods exist in IT0118.
003	Child &1 (ID No.: &2): Too many loop runs when comparing notifications
004	Child &1 (ID No.: &2): Unknown case constellation when comparing notifs
005	Child &1 (child no. &2, date of birth &3) does not have any tax ID no.
006	Notification for ID No. &1 could not be written to the database.
007	The notification status for ID No. &1 could not be updated in datebase.
008	Notification status for ID No. &1 could not be saved in the history.
009	Statistics may contain errors.
010	Infotype &1 could not be read.
011	No infotype record &1 exists on &2.
012	&1 children exist with the same ID No. &2.
013	Child &1 (ID No.: &2): Notification cancellation required not permitted.
014	The maximum number of files per day has been reached.
015	File ID &1 already exists.
016	You are not authorized to write file &1 to the file system.
017	File &1 already exists in the file system.
018	Error opening file &1
019	Error when writing file &1
020	The family equalization fund key contains errors.
021	The file structure of file &1 is invalid.
022	Invalid file name &1
023	Element ELMAHeader of file &1 is inconsistent.
024	No files were found.
025	No BZSt number and/or account ID of family equalization fund &1 exists.
026	Child &1 (ID No.: &2): New run necessary after sending file.
027	It was not possible to generate a GUID.
028	The system could not save the response to ID No. &1 to the database.
029	An error occurred when moving file &1.
030	Error while reading file &1
031	No file was found for ID No. &1.
032	Several files were found for the same File ID &1.
033	An error occurred when writing the response assignments to the database.
034	The same response has already been assigned.
035	A different response already exists for the same notification.
036	Element ELMAFEHLER of file &1 is inconsistent.
037	BZSt rejected notification file &1 with error code &2.
038	Child &1 (ID No.: &2): There are still some incorrect notifications.
039	ID No. &1: It is not possible to restore the previous notification.
040	It was not possible to change the status of the file with ID &1.
041	The inbound directory and the storage directory must be different.
042	Please specify an inbound directory.
043	Please specify a storage directory.
044	Directory &1 does not exist.
045	Please specify an outbound directory.
046	ID No. &1: The inbound status could not be updated on the database.
047	ID No. &1: Error occurred when saving the assigned response to database.
048	There are no changes to save.
049	The response status could not be updated on the database.
050	The status may not be changed from "&1" to "&2".
051	Response with specialist procedure key &1 could not be assigned.
052	No file was found.
053	More than one file was found.
054	There is no detailed view available.
055	IT0118 records for inactive period are available.
056	There is an error message from the BZSt for ID No. &1.
057	There is an overlapping notification from the BZSt for ID No. &1.
058	There's a processing note from BZSt for ID no. &1
059	There's a special notification from BZSt for ID no. &1
060	Status of the Notification Tool is initial
061	Context class for Notification Tool has not been maintained correctly
062	The file has already been rejected (File ID: &1).
063	The file has already been processed by BZSt (file ID: &1).
064	File ID &1 was not found.
065	Evaluation &1 due to prev. destruction logs