How To Fix /LIME/PI_CORE136 - Document &1, item &2: Line &3: No check indicators passed on

SAP Error Message - Details

• Message type: E = Error

• Message class: /LIME/PI_CORE -

• Message number: 136

• Message text: Document &1, item &2: Line &3: No check indicators 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_CORE136 - Document &1, item &2: Line &3: No check indicators passed on ?

  The SAP error message /LIME/PI_CORE136 typically indicates that there is an issue with the check indicators for a specific document and item in the system. This error is often encountered in the context of logistics or procurement processes, particularly when dealing with purchase orders, invoices, or similar documents.
  Cause:
  The error message "No check indicators passed on" suggests that the system is unable to find valid check indicators for the specified line item in the document. This can occur due to several reasons, including:
  
  Missing Configuration: The check indicators may not be properly configured in the system for the relevant document type or item category.
  Data Inconsistencies: There may be inconsistencies or missing data in the document that prevent the system from processing it correctly.
  Authorization Issues: The user may not have the necessary authorizations to perform the checks on the document.
  Custom Logic: If there are custom enhancements or modifications in the system, they may interfere with the standard processing of check indicators.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Configuration:
  
  Verify the configuration settings for the document type and item category in the relevant customizing transactions (e.g., SPRO).
  Ensure that the check indicators are defined and activated for the relevant processes.
  
  
  
  Review Document Data:
  
  Check the document (e.g., purchase order, invoice) for any missing or incorrect data.
  Ensure that all required fields are filled out correctly and that there are no inconsistencies.
  
  
  
  Authorization Check:
  
  Ensure that the user has the necessary authorizations to perform the checks on the document.
  Review the user roles and authorizations in the system.
  
  
  
  Debugging:
  
  If the issue persists, consider debugging the process to identify where the check indicators are being evaluated and why they are not being passed.
  Look for any custom code or enhancements that may be affecting the standard behavior.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to the specific error message for additional insights or known issues.
  
  
  
  Contact SAP Support:
  
  If you are unable to resolve the issue, consider reaching out to SAP support for assistance. Provide them with the error message details and any relevant context.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like ME23N (Display Purchase Order), MIRO (Enter Incoming Invoice), or others depending on the context of the error.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Community Forums: Consider searching or posting in SAP community forums for insights from other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.