How To Fix /GSINS/INSH_MSG138 - No items selected. Posting run could not be created.

SAP Error Message - Details

• Message type: E = Error

• Message class: /GSINS/INSH_MSG -

• Message number: 138

• Message text: No items selected. Posting run could not be created.

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 /GSINS/INSH_MSG138 - No items selected. Posting run could not be created. ?

  The SAP error message /GSINS/INSH_MSG138 No items selected. Posting run could not be created typically occurs in the context of the SAP Inventory Management or Logistics modules, particularly when trying to create a posting run for inventory documents or similar transactions. Here’s a breakdown of the potential causes, solutions, and related information for this error:
  Causes:
  
  
  No Selected Items: The most straightforward cause is that there are no items selected for the posting run. This can happen if the selection criteria do not match any existing documents or if the documents have already been processed.
  
  
  Incorrect Selection Criteria: The parameters or filters used to select items for the posting run may be too restrictive or incorrectly set, leading to no items being found.
  
  
  Document Status: The documents you are trying to process may already be in a status that does not allow them to be included in a posting run (e.g., already posted, canceled, etc.).
  
  
  Authorization Issues: Lack of proper authorizations to view or process certain documents can also lead to this error.
  
  
  System Configuration: There may be configuration issues in the system that prevent the selection of items for the posting run.
  
  
  Solutions:
  
  
  Check Selection Criteria: Review the selection criteria you are using to ensure they are correct and not overly restrictive. Adjust the filters to include a broader range of items.
  
  
  Verify Document Status: Check the status of the documents you are trying to include in the posting run. Ensure they are in a valid state for processing.
  
  
  Select Items Manually: If applicable, try to manually select items for the posting run to see if the issue persists.
  
  
  Review Authorizations: Ensure that you have the necessary authorizations to access and process the documents in question.
  
  
  Consult with SAP Basis or Functional Team: If the issue persists, it may be necessary to consult with your SAP Basis or functional team to check for any configuration issues or system errors.
  
  
  Check for Updates or Notes: Look for any SAP Notes or updates related to this error message. Sometimes, SAP releases patches or notes that address specific issues.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes that may be involved in the posting run process, such as MB1A, MB1B, or MB1C for inventory postings.
  SAP Documentation: Refer to SAP Help documentation for detailed information on the posting run process and related configuration settings.
  Community Forums: Check SAP Community forums or other user groups for similar issues and solutions shared by other users.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it. If the problem continues, consider reaching out to SAP support for further assistance.