How To Fix /ACCGO/CMGL_APPL218 - The selected application document was not set for split at application

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/CMGL_APPL -

• Message number: 218

• Message text: The selected application document was not set for split at application

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_APPL218 - The selected application document was not set for split at application ?

  The SAP error message /ACCGO/CMGL_APPL218 indicates that the selected application document is not configured for split at the application level. This typically occurs in the context of the SAP General Ledger (G/L) accounting, particularly when dealing with document splitting functionality.
  Cause:
  
  Document Splitting Not Configured: The application document you are trying to process is not set up to allow document splitting. This can happen if the document type or the configuration for the specific application does not support splitting.
  Missing Configuration: The necessary configuration for document splitting might not be completed in the system. This includes settings in the G/L account, document types, or the overall configuration for document splitting.
  Incorrect Document Type: The document type used for the transaction may not be configured for splitting.
  
  Solution:
  
  
  Check Document Type Configuration:
  
  Go to the transaction code OBY6 (for document types) and verify if the document type you are using is set up for document splitting.
  Ensure that the "Split Document" checkbox is selected for the relevant document type.
  
  
  
  Review G/L Account Settings:
  
  Check the G/L accounts involved in the transaction. Go to transaction code FS00 and review the account settings to ensure that they are configured for document splitting.
  
  
  
  Document Splitting Configuration:
  
  Use transaction code OB37 to check the overall document splitting configuration. Ensure that the necessary settings are in place for the application area you are working with.
  Make sure that the splitting characteristics are defined correctly in the configuration.
  
  
  
  Consult with Functional Consultant:
  
  If you are unsure about the configuration or if changes are needed, consult with your SAP functional consultant or the team responsible for financial accounting in your organization.
  
  
  
  Testing:
  
  After making any changes, perform a test transaction to ensure that the error is resolved and that document splitting works as expected.
  
  
  
  Related Information:
  
  Document Splitting: This is a feature in SAP that allows for the automatic splitting of accounting documents into multiple line items based on certain criteria, which is useful for reporting and analysis.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OB37, OBY6, and FS00 for configuration checks.
  SAP Notes: Check SAP Notes for any known issues or additional guidance related to document splitting and the specific error message.
  
  By following these steps, you should be able to identify the cause of the error and implement the necessary changes to resolve it.