How To Fix HRPAYDEPF363 - Error occurred in SIMU_O

SAP Error Message - Details

• Message type: E = Error

• Message class: HRPAYDEPF - Error messages for German infotype module pools: garnishment

• Message number: 363

• Message text: Error occurred in SIMU_O

What causes this issue?

An error occured in the garnishment calculation in the period &v2&/&v3&.

System Response

The system outputs the message as an error message and terminates the
cleanup. The system sets the status of the case to <LS>S01 Check</>.

How to fix this error?

Open the <LS>Personnel Numbers</> node in the log for the error message.
Expand the tree structure under the corresponding personnel number
until you reach the <LS>Current Cluster Result In-Period &v3&</>node.
Double-click this node and choose the <LS>Payroll Log</> pushbutton in
the lower screen area to show the corresponding payroll log. The error
that caused the termination is shown at the end of the log.
If the error is not shown at the end of the log, contact SAP Support.

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message HRPAYDEPF363 - Error occurred in SIMU_O ?

  The SAP error message HRPAYDEPF363, which states "Error occurred in SIMU_O," typically occurs in the context of payroll processing in the SAP HR module. This error can arise during the simulation of payroll runs, particularly when there are issues with the configuration or data integrity.
  Causes:
  
  Data Issues: There may be inconsistencies or missing data in the employee master data, infotypes, or payroll results.
  Configuration Errors: Incorrect configuration in the payroll schema or rules can lead to errors during simulation.
  Authorization Issues: The user executing the payroll simulation may not have the necessary authorizations to access certain data or perform specific actions.
  Custom Code: If there are custom enhancements or modifications in the payroll process, they may not be functioning correctly.
  Technical Issues: There could be underlying technical issues, such as database problems or system performance issues.
  
  Solutions:
  
  Check Data Integrity: Review the employee master data and infotypes for completeness and correctness. Ensure that all required fields are filled out properly.
  Review Configuration: Examine the payroll schema and rules for any misconfigurations. Ensure that all necessary payroll components are correctly set up.
  Authorization Check: Verify that the user has the appropriate authorizations to execute the payroll simulation. This can be done through transaction SU53 or by checking user roles.
  Debugging: If you have access to debugging tools, you can analyze the payroll simulation process to identify where the error occurs. This may require technical expertise.
  Check Custom Code: If there are any custom enhancements, review them for errors or conflicts with standard SAP processes.
  Consult Logs: Check the application logs (transaction SLG1) for more detailed error messages that can provide insights into the root cause of the issue.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide patches or updates.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as PA30 (Maintain HR Master Data), PC00_MXX_CALC (Payroll Calculation), and SLG1 (Application Log).
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  Documentation: Review SAP documentation related to payroll processing and error handling for additional guidance.
  
  If the issue persists after trying the above solutions, it may be necessary to involve your SAP support team or consult with SAP directly for further assistance.