HRGB_LGPS - HR: Messages for LGPS
The following messages are stored in message class HRGB_LGPS: HR: Messages for LGPS.
It is part of development package PC08 in software component PY-GB. This development package consists of objects that can be grouped under "HR accounting: GB".
It is part of development package PC08 in software component PY-GB. This development package consists of objects that can be grouped under "HR accounting: GB".
Message Nr ▲ | Message Text |
|---|---|
| 001 | LGPS: Contribution rate changed: &1 &2 &3 &4 |
| 002 | LGPS: No LGPS schemes defined |
| 003 | LGPS: Previous calculation of this pay period missing |
| 004 | LGPS: Calculation of the previous pay period missing |
| 005 | LGPS: Dates BADI has forced no re-assessment |
| 006 | LGPS: Dates BADI has forced re-assessment |
| 007 | LGPS: T5GPBSP_UNP entry missing (Sch/Date/PenPay &1 &2 &3) |
| 008 | LGPS: T5GPBSP_PRO entry missing (Sch/Date &1 &2) |
| 009 | LGPS: Wage Type Group &1 contains no Wage Types (Table T52D7) |
| 010 | GBLGP Error: If Parameter &1 is set to &2, Parameter &3 must be set to &4 |
| 011 | GBLGP Error: If Parameter &1 is set to &2 |
| 012 | LGPS: 1st payroll in year flag overridden |
| 013 | LGPS: WPBP and PENS must be kept in-sync if pro-ration is necessary |
| 014 | LGPS: Protected Pay (IT0052) wage type missing (Table T539S &1 &2 &3 &4) |
| 015 | All Absences are processed under new TinA rules |
| 016 | LGPS: After 01.04.2012 pension schemes must be defined in T5GPBSP_PSCH &1 |
| 017 | LGPS: LGPS pension schemes cannot overlap |
| 018 | LGPS: Re-instatement from "O" result failed for Scheme Id &1 |
| 019 | LGPS: Re-instatement from "P" result failed for Scheme Id &1 |
| 050 | *********************** LGPS 2014 ********************************** |
| 051 | Do not use this field until April 1st 2014 |
| 052 | Currently only the Full Scheme and the 50/50 Scheme are available |
| 053 | Do not use this field for non-LGPS schemes |
| 054 | Joining the 50/50 Scheme has an impact of additional pension contracts |
| 055 | Changes between Main and 50/50 schemes must be at the start of a period |
| 056 | LGPS Error: Continued Nil Pay (&1 - &2) while in the 50/50 section |
| 057 | LGPS Warning: /161 is being reduced. This is unusual. |
| 058 | LGPS Warning: Annual APP derivation failed. Please use APX0. |
| 059 | LGPS Error: &1 is not date format DD.MM.YYYY (T5GPBS_ALL:08/LGPS/ERGL) |
| 060 | LGPS 2014: Invalid Percentage (On &1, &2 section: &3) |
| 061 | LGPS Warning: RFSL absence &1 (&2 - &3) has APP value &4 |
| 062 | LGPS Warning: /160 (&1) increased by E160 (&2) to &3 |
| 063 | LGPS Warning: /161 (&1) increased by E161 (&2) to &3 |
| 064 | Do not use this field until April 1st 2015 |
| 065 | LGPS 2015: Invalid Percentage (On &1, &2 section: &3) |
| 066 | LGPS Error: Employee is in BOTH &1 and &2 |
| 067 | LGPS Error: Councillors are not allowed in the 50/50 scheme |
| 068 | LGPS Error: Feature GBLG2 returned &1 (only "X" or " " allowed) |
| 069 | LGPS Error: GBLGP Go Live Date must be defined (T5GPBSP_SCH: Scheme &1) |
| 100 | No LGPS Pension Schemes exist (Table T5GPBSP_SCH) |
| 101 | Employee Omitted (not in an LGPS Scheme between &1 and &2) |
| 102 | File Format &1 has non-character fields. Flat File output not allowed. |
| 103 | File Format &1 does not exist. (i.e. it is not a structure in SE11) |
| 104 | Employee has retrospectively changed section during month &1 |
| 105 | Employee has retrospectively changed percentage during month &1 |
| 106 | Employee has retrospectively changed assessment date during month &1 |
| 107 | LGPS: LGPS Final Pay rules for &1 must be defined in T5GPBSP_PSCH on &2 |
| 108 | LGPS Error; Overlapping records in IT0071 |
| 109 | &1 Error; Employee joined scheme &2 on &3 before their 16th birthday &4 |
| 110 | &1 Error; Employee still in scheme &2 on &3 after their 75th birthday &4 |
| 111 | LGPS Error; T5GPBS_ALL constant missing (Keys &1) |
| 112 | LGPS Error; T5GPBS_ALL constant &1 must be format DD.MM.YYYY (Keys &2) |
| 113 | LGPS Error; Employee must move back to "Main" section on &1 (CARD on &2) |
| 114 | LGPS Error; GBCHG Node 009 must be active (See Note 2475286) |