Do you have any question about this error?
Message type: E = Error
Message class: HRPAYBEPS - Message Class for Belgian Public Sector
Message number: 006
Message text: Infotype 0016/0109 does not exist, statute taken from feature BPSNS
Infotype "Contract Elements Belgium" (0016/ view 0109) does not exist.
The default value for the Personnel Statute was taken from feature
BPSNS: The old one before the date from BPSNS, the new one after that
date
In case the employee chose to stay with the old Personnel Statute after
the date of the switch between old and new statute defined in feature
BPSNS, create/change infotype "Contract elements" and set the
corresponding Public Sector flag.
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.
HRPAYBEPS006
- Infotype 0016/0109 does not exist, statute taken from feature BPSNS ?The SAP error message HRPAYBEPS006 indicates that there is an issue with the infotype 0016 (Basic Pay) or 0109 (Additional Payments) in the context of the Belgian Payroll system. The error specifically states that the infotype does not exist, and it is related to the statute being taken from the feature BPSNS.
Cause:
- Missing Infotype: The infotype 0016 or 0109 may not be created or may not have been properly maintained for the employee in question.
- Incorrect Configuration: The feature BPSNS may not be configured correctly, leading to the system not being able to retrieve the necessary data for the infotype.
- Data Inconsistency: There may be inconsistencies in the employee's master data or payroll data that prevent the system from processing the infotype correctly.
- Authorization Issues: The user may not have the necessary authorizations to view or maintain the infotype.
Solution:
- Check Infotype Existence: Verify that the infotype 0016 and 0109 exist for the employee in question. You can do this by using transaction code PA30 (Maintain HR Master Data) and checking the infotypes for the employee.
- Maintain Infotype: If the infotype does not exist, you may need to create it or maintain it with the necessary data.
- Review Feature BPSNS: Check the configuration of feature BPSNS in transaction code PE03 (Feature Maintenance). Ensure that it is set up correctly and that it points to the correct infotypes and values.
- Check for Data Consistency: Review the employee's master data for any inconsistencies or missing information that could affect the payroll processing.
- Authorization Check: Ensure that the user has the necessary authorizations to access and maintain the infotypes.
Related Information:
If the issue persists after checking the above points, it may be necessary to consult with your SAP HR module support team or a technical consultant for further investigation and resolution.
Get instant SAP help. Start your 7-day free trial now.
HRPAYBEPS005
A new number (&1) is suggested for the allowance receiver
The system suggests a new number for the allowance receiver, but you still have the possibility to use an existing allowance receiver. You simply hav...
HRPAYBEPS004
The Maximun number of hours by week is & (this value is substituted)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
HRPAYBEPS008
No fields flagged as node
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
HRPAYBEPS009
Position is not set as Last Node
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.