Do you have any question about this error?
Message type: E = Error
Message class: HRPAYDEMUSCHG_BV - Maternity Protection Act - Prohibited Activities
Message number: 075
Message text: Infotype 0699 must be processed manually
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.
The payroll run is terminated.
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.
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.
HRPAYDEMUSCHG_BV075
- Infotype 0699 must be processed manually ?The SAP error message HRPAYDEMUSCHG_BV075 indicates that there is an issue with processing Infotype 0699 (which is typically related to the management of employee data in the context of payroll) and that it must be handled manually. This error can arise due to various reasons, and here are some common causes, potential solutions, and related information:
Causes:
- Data Inconsistencies: There may be inconsistencies or missing data in the employee records that prevent automatic processing.
- Configuration Issues: The system configuration for Infotype 0699 may not be set up correctly, leading to processing errors.
- Authorization Issues: The user may not have the necessary authorizations to process the infotype automatically.
- Custom Logic: Custom enhancements or modifications in the payroll process may interfere with the standard processing of Infotype 0699.
- System Errors: There may be temporary system errors or issues with the payroll run that require manual intervention.
Solutions:
- Manual Processing: As the error suggests, you will need to manually process Infotype 0699. This involves reviewing the data and making necessary adjustments directly in the infotype.
- Check Data Consistency: Review the employee's data for any inconsistencies or missing fields that could be causing the error. Ensure that all required fields are filled out correctly.
- Review Configuration: Check the configuration settings for Infotype 0699 in the SAP system. Ensure that all necessary settings are correctly defined.
- Authorization Check: Verify that the user attempting to process the infotype has the appropriate authorizations. If not, contact your SAP security team to obtain the necessary permissions.
- Consult Documentation: Refer to SAP documentation or notes related to Infotype 0699 for any specific guidelines or known issues.
- Debugging: If you have access to technical resources, consider debugging the payroll process to identify where the error is occurring.
- Contact SAP Support: If the issue persists and cannot be resolved through the above steps, consider reaching out to SAP support for further assistance.
Related Information:
By following these steps, you should be able to address the error message HRPAYDEMUSCHG_BV075 and ensure that Infotype 0699 is processed correctly.
Get instant SAP help. Start your 7-day free trial now.
HRPAYDEMUSCHG_BV074
Change of SI attributes exists during maternity protection period
What causes this issue? If the SI attributes change in the period between the months used as a basis for the supplement (3 months before start of the...
HRPAYDEMUSCHG_BV073
Change of pay scale type exists during maternity protection period
What causes this issue? A change of the pay scale is determined in the period between the months used as a basis and the maternity protection period ...
HRPAYDEMUSCHG_BV076
Infotype record 0699 is relevant for period of prohibited activities
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
HRPAYDEMUSCHG_BV080
Valuation period (average valid for)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.