Message type: E = Error
Message class: HRPAYDECI - HR: Payroll Accounting - Construction Industry
Message number: 372
Message text: Infotype for MLR YBL due to employee leaving was not created.
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
HRPAYDECI372
- Infotype for MLR YBL due to employee leaving was not created. ?The SAP error message HRPAYDECI372 typically indicates that there is an issue with the creation of an infotype related to the MLR (Monthly Leave Report) for an employee who is leaving the organization. This error can occur in the context of payroll processing or when trying to generate reports related to employee leave.
Cause: Missing Infotype Record: The infotype for MLR YBL (Yearly Balance Leave) may not have been created for the employee who is leaving. This can happen if the employee's leave records were not properly maintained or updated in the system. Incorrect Configuration: There may be configuration issues in the payroll or leave management settings that prevent the system from generating the necessary infotype. Timing Issues: The error may arise if the infotype is expected to be created at a specific time (e.g., during payroll processing) but the employee's status change (leaving) occurs before this process. Data Inconsistencies: There may be inconsistencies in
Get instant SAP help. Sign up for our Free Essentials Plan.
HRPAYDECI371
The leave was not converted from infotype 0005 to infotype 2006.
What causes this issue? The use of infotype 0005 Leave Entitlement is obsolete. Functionalities necessary for collective agreements are not supported...
HRPAYDECI370
Vacation relating to DOCNR '&1' without absence days
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
HRPAYDECI373
Remaining-leave account for current year was manually surrendered (/B90).
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
HRPAYDECI374
Wage type &1 vacation pay (APZNR '&2' ABZNR '&3') not found.
What causes this issue? The wage type with the vacation pay is the basis for calculating vacation pay and could not be found.System Response The sys...
Click on this link to search all SAP messages.