How To Fix /ACCGO/CMGL_APPL164 - Selected application documents have different storage settlement types

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/CMGL_APPL -

• Message number: 164

• Message text: Selected application documents have different storage settlement types

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 /ACCGO/CMGL_APPL164 - Selected application documents have different storage settlement types ?

  The SAP error message /ACCGO/CMGL_APPL164 indicates that there is a mismatch in the storage settlement types of the selected application documents. This typically occurs in the context of managing materials and inventory in SAP, particularly when dealing with the settlement of costs related to materials or production.
  Cause:
  The error arises when you attempt to process multiple application documents (such as invoices, purchase orders, or production orders) that have different storage settlement types. Storage settlement types define how costs are allocated and settled for inventory items, and if the documents involved do not share the same type, the system will not allow the operation to proceed.
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Identify the Documents: Determine which application documents are causing the issue. You may need to review the documents selected for processing to see their respective storage settlement types.
  
  
  Check Storage Settlement Types: For each document, check the storage settlement type. You can do this by navigating to the relevant transaction (e.g., ME23N for purchase orders, MB03 for material documents) and reviewing the details.
  
  
  Standardize Storage Settlement Types: Ensure that all selected documents have the same storage settlement type. If they do not, you may need to:
  
  Exclude some documents from the selection.
  Change the storage settlement type of the documents (if applicable and permissible) to match the others.
  
  
  
  Reprocess the Documents: After ensuring that all selected documents have the same storage settlement type, attempt to process them again.
  
  
  Consult Documentation: If you are unsure about the implications of changing storage settlement types, consult your SAP documentation or reach out to your SAP support team for guidance.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME23N (Display Purchase Order), MB03 (Display Material Document), and others that may help you in reviewing the documents.
  SAP Notes: Check for any SAP Notes related to this error message, as they may provide additional insights or patches that could resolve the issue.
  User Roles and Permissions: Ensure that you have the necessary permissions to view and modify the documents in question, as restrictions may prevent you from making changes.
  
  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 persists, consider reaching out to your SAP support team for further assistance.