Infotype 0699 must be processed manually

Message type: E = Error

Message class: HRPAYDEMUSCHG_BV - Maternity Protection Act - Prohibited Activities

Message number: 075

Message text: Infotype 0699 must be processed manually



What causes this issue?

The adjustment amount for employer supplementary benefits for the
company pension scheme (wage type <LS>/6H5</> (Adjust. Amt
Co.Pens.Sch.)) is not specified correctly in the following cases:
If prohibited activities start or end in the middle of a month, or if
there is more than one period of prohibited activities in the same
month.
If additional employer payments are made at the same time (wage types
<LS>/5R1</>, <LS>/5R2</> or <LS>/5R3</>) due to infotype record <LS>
German Pension Reform D</> (0699), and infotype record <LS>0699</> has
not been correctly delimited for partial months in which there are
prohibited activities.
This problem may also occur if employer contributions are converted to
capital formation savings payments (wage type <LS>/57F</> (Capital
Formation, Employer?s Contribution AVmG)) using infotype <LS>0699</>.
This problem is due to the fact that employer supplementary benefits in
infotype <LS>0699 </> are usually only valid for one whole calendar
month and are, therefore, assigned to the last split period. In the
fictitious run for prohibited activities, the employer supplementary
benefits for the company pension scheme must be available exactly
according to the split when the payroll function <LS>DAAG LPE</> is
called. Due to missing information (for example, mid-month change to
capacity utilization level), it is generally not possible to do this at
a later stage or to automatically distribute it correctly for the
fictitious run only.


System Response

The payroll run is terminated.


How to fix this error?

To ensure the payroll is run correctly, delimit the data record at the
start or end of the split periods in accordance with the prohibited
activities in infotype <LS>German Pension Reform D</> (0699). The field
<DS:DE.OBJPS>Sequential Number</> (OBJPS) must be different for the
different data records within the calendar month. The amounts for these
mid-month periods must also be adjusted accordingly to ensure that the
overall total for the full period is correct again.
Example:
Payroll month September 2013
There is exactly one data record of infotype <LS>0699 </> from December
1, 2012 to December 31, 9999.
There is a case of prohibited activities (without employment) in the
period from September 12, 2013 to March 10, 2014.
Subapplication 'MGBU' must be valid at the start of the payroll period.
<ZH>Solution:</> In infotype <LS>German Pension Reform D</> (0699),
delimit the data record at the start of the split periods in accordance
with the prohibited activities:
One data record of infotype <LS>0699 </>valid from December 01, 2012
until August 31, 2013 with the original amount
One data record of infotype <LS>0699 </>valid from September 01, 2013
until September 11, 2013. Sequential number may be the original number
(for example, 01) and amounts must be adjusted accordingly for this
period.
One data record of infotype 0699 valid from September 12, 2013 until
September 30, 2013. A number that has not yet been used for this
investment type and this calendar month must be chosen as the sequential
number. It is important that different numbers are used if there is more
than one record within a month.
One data record of infotype <LS>0699 </>valid from October 01, 2013
until December 31, 9999. Sequential number remains the same as the
original number (for example, 01). The original amount must be used
again as the amount.


Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.


Error message extract from SAP system. Copyright SAP SE.