How To Fix 3O358 - Quit event of LI, NHI and NP should be reported together

SAP Error Message - Details

• Message type: E = Error

• Message class: 3O - HR: Messages for Taiwan

• Message number: 358

• Message text: Quit event of LI, NHI and NP should be reported together

Self-Explanatory Message

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.

What else can you do?

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message 3O358 - Quit event of LI, NHI and NP should be reported together ?

  The SAP error message 3O358, which states "Quit event of LI, NHI and NP should be reported together," typically occurs in the context of payroll processing, particularly when dealing with employee terminations or changes in employment status. This error indicates that the system expects certain events (like the quit event for different types of employment) to be reported simultaneously, but they are not being processed together as required.
  Cause:
  The error is usually caused by one of the following reasons:
  
  Inconsistent Reporting: The quit events for different employment types (like LI - Leave of Absence, NHI - Non-Hired Individual, NP - Non-Permanent) are not being reported together in the payroll run.
  Configuration Issues: There may be configuration settings in the payroll schema or infotype settings that are not aligned with the reporting requirements.
  Data Entry Errors: Incorrect or incomplete data entry in the relevant infotypes (like infotype 0000 for actions, infotype 0001 for organizational assignment, etc.) can lead to this error.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Infotypes: Review the infotypes related to the employee's status. Ensure that the quit events for LI, NHI, and NP are correctly entered and that they are all present in the system.
  
  
  Review Payroll Configuration: Check the payroll configuration settings to ensure that the reporting requirements for quit events are correctly set up. This may involve reviewing the payroll schema and rules.
  
  
  Simultaneous Reporting: Ensure that when processing payroll, the quit events for LI, NHI, and NP are reported together. This may involve adjusting the payroll run or the sequence of events being processed.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to this specific error message for any additional guidance or updates that may be relevant.
  
  
  Testing: After making the necessary adjustments, run a test payroll to ensure that the error does not reoccur.
  
  
  Seek Support: If the issue persists, consider reaching out to SAP support or your internal SAP team for further assistance.
  
  
  Related Information:
  
  SAP Notes: Check for any SAP Notes related to error message 3O358 for specific patches or updates that may address the issue.
  Documentation: Review SAP Help documentation for payroll processing and reporting requirements to ensure compliance with the necessary guidelines.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.