How To Fix /LIME/PI_CORE147 - Document &1, item &2: New process status not passed on

SAP Error Message - Details

• Message type: E = Error

• Message class: /LIME/PI_CORE -

• Message number: 147

• Message text: Document &1, item &2: New process status not passed on

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 /LIME/PI_CORE147 - Document &1, item &2: New process status not passed on ?

  The SAP error message /LIME/PI_CORE147 Document &1, item &2: New process status not passed on typically occurs in the context of the SAP Logistics Information Management (LIM) or similar modules where document processing and status updates are involved. This error indicates that the system was unable to pass the new process status for a specific document and item combination.
  Cause:
  
  Status Update Issues: The error may arise if there is an issue with the status update logic in the system. This could be due to missing configurations or incorrect status transitions.
  Document Locking: If the document is locked by another process or user, the system may not be able to update the status.
  Data Inconsistencies: There may be inconsistencies in the data related to the document or item, preventing the status from being updated.
  Authorization Issues: The user may not have the necessary authorizations to change the status of the document.
  Custom Code or Enhancements: If there are custom developments or enhancements in the system, they may interfere with the standard processing logic.
  
  Solution:
  
  Check Document Status: Verify the current status of the document and ensure that it is in a state that allows for the new status to be applied.
  Review Configuration: Check the configuration settings related to status management in the relevant module. Ensure that all necessary status transitions are defined correctly.
  Unlock Document: If the document is locked, identify the user or process that has locked it and resolve the locking issue.
  Data Consistency Check: Perform a data consistency check to ensure that all related data is correct and complete.
  Authorization Check: Ensure that the user attempting to change the status has the necessary authorizations.
  Debugging: If the issue persists, consider debugging the process to identify where the failure occurs. This may involve checking custom code or enhancements that could be affecting the status update.
  Consult SAP Notes: Look for any relevant SAP Notes that may address this specific error message or provide guidance on similar issues.
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like SE80 (Object Navigator) or SE37 (Function Module) to analyze the related function modules or programs.
  SAP Support: If the issue cannot be resolved internally, consider reaching out to SAP Support for assistance, providing them with the error message details and any relevant logs.
  Documentation: Review the SAP documentation related to the specific module you are working with for additional insights on status management and error handling.
  
  By following these steps, you should be able to identify the root cause of the error and implement a suitable solution.