HRPAYAT_MBGM -

The following messages are stored in message class HRPAYAT_MBGM: .
It is part of development package PC03 in software component PY-AT. This development package consists of objects that can be grouped under "HR Payroll: Austria".

Message Nr ▲	Message Text
000	**000-099: mBGM general
001	Test notification &1 &2 &3 &4
002	Test notification LT &1 &2 &3 &4
009	Evaluation date &1 is before the mBGM key date &2
010	Error reading the payroll results for personnel number &1
011	No payroll results for personnel number &1 available
012	ELDA status already confirmed. No mBGM generated.
013	Payroll for payroll area &1 and period &2 not yet completed
014	Control record for &1 period &2 cannot be checked
016	& & & &
017	First start report RPUGMBA0_TB
018	Payroll results exist: No mBGM generated
019	mBGM(RT) and mBGM(ORT) are different!
020	Limit of &1 nodes to be displayed has been reached
021	Status for &1 mBGMs &2 set, &3 errors
022	Status for mBGM on &1 : &2
031	Table &1 is locked by user &2
032	Table &1 is locked by user &2 for personnel number &3.
033	Internal error from enqueue server with user &1 for PerNo &2.
035	Authorization lacking to read mBGM for specific pers. no.
100	**100-199: Specific to TARGET Generator
101	TARGET generator reports from &1 node &2
102	Difference between contrib. and contrib. wage type exceeds tolerance val.
103	The mBGM time period is outside of the defined period &1
104	Undefined amount within a clearing basis
105	No employer account number found: SI body &1/&2 payroll office &3
106	Technical error occurred when determining the clearing basis
107	CCS: &1 - (cum. wage type, source field) in V_T5AMBGM_VBL is not useful
108	Undefined percentage within a clearing item
109	SI number and reference number of request have not been filled
110	Personnel Number &1 Rejected with BAdI Method
111	More than &1 pay scale blocks are not possible
112	SI contributions without SI period but BV contributions with BV period
113	Check VERG = 5 (value is questionable from the perspective of the GKK)
114	Last name or first name is not filled
115	The mBGM field &1 contains unallowed characters: "&2"
200	**200-249: Specific to target/actual comparison
201	Please enter a status confirmation for data medium number &1
202	Target mBGM for in-period &2 still exists.
203	ACTUAL mBGM for in-period &2 without data medium number still exists.
204	Data medium number &1 not found in T5A1P; please check
205	Reversal rec. &1 w/o corresponding new notification &2 in ACTUAL balance
250	**250-299: File-generator-specific
251	Total RSUM (VP) does not match VSUM (mBGM), reference value &1
252	&1 &2 &3 field &4 must not be initial
253	&1 &2 field &3 missing in ELDA structure
254	Reference value could not be determined &1 &2 &3 &4
255	Default mapping used for &1 &2 &3 &4
256	&1 &2 field &3 has invalid property "&4"
257	Maximum number of package splits &1 exceeded
258	&1 - &2 assignment of GUID &3 to ref. no. missing
259	&1 - &2 assignment of package ref. no. &3 is missing
260	&1 - &2 assignment of reference no. &3 is missing
261	&1 - &2 assignment of data medium &3 is missing
300	**300-349: Messages for manual correction
350	**350-399: Messages for status confirmations
400	**400-449: Messages for Posting Transfer
401	Difference EUR &2 between RT and mBGM larger than tolerance value
402	The posting period can either be set or emptied.
403	Only mBGMs with 410 and 411 are valuated in a productive posting run.
404	Live posting run not performed successfully
405	No suitable ACTUAL mBGM found for personnel number &1 and period &2.
406	&1 - SOLL-GUID &2 missing for Pernr &3
407	&1 - HASH is missing for GUID &2 and Pernr &3
408	&1 - missing assignment mBGM vs RT &2