How To Fix /LIME/PI_CORE072 - Doc. &1, item &2: Inconsistent count entry (Does not start w. level 1)

SAP Error Message - Details

• Message type: E = Error

• Message class: /LIME/PI_CORE -

• Message number: 072

• Message text: Doc. &1, item &2: Inconsistent count entry (Does not start w. level 1)

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_CORE072 - Doc. &1, item &2: Inconsistent count entry (Does not start w. level 1) ?

  The SAP error message /LIME/PI_CORE072 indicates that there is an inconsistency in the count entry for a document item in the SAP system. Specifically, the error message states that the count entry does not start with level 1, which suggests that the system is expecting a certain hierarchical structure or sequence that is not being followed.
  Cause:
  
  Hierarchical Structure Violation: The error typically arises when the document items are not structured correctly according to the expected levels. For example, if the system expects a count entry to start at level 1 (the top level) but finds it starting at a different level, it will trigger this error.
  Data Entry Errors: Manual data entry errors or incorrect data uploads can lead to inconsistencies in the document structure.
  Configuration Issues: There may be configuration settings in the SAP system that dictate how document items should be structured, and if these are not set up correctly, it can lead to this error.
  
  Solution:
  
  Check Document Structure: Review the document in question to ensure that the count entries are structured correctly. Make sure that the first entry starts at level 1 and that subsequent entries follow the expected hierarchy.
  Correct Data Entry: If the error is due to manual data entry, correct the entries to ensure they conform to the expected structure.
  Review Configuration: If the issue persists, check the configuration settings related to document processing in the SAP system. Ensure that they are set up to allow for the correct hierarchical structure.
  Consult Documentation: Refer to SAP documentation or help resources for guidance on the specific document type you are working with, as there may be specific requirements for that document type.
  Use Transaction Codes: Utilize relevant transaction codes (like SE11 for data dictionary, SE37 for function modules, etc.) to analyze the underlying data structures and identify any discrepancies.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common problems.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed. Other users may have encountered the same error and can provide insights or solutions.
  Testing: After making corrections, test the document processing again to ensure that the error has been resolved and that the document can be processed without issues.
  
  If the problem persists after trying the above solutions, it may be necessary to involve your SAP support team or a consultant with expertise in SAP document processing to further investigate the issue.