How To Fix /EACC/MSG_ABSTR_JRNL015 - Internal error: Selection according to &2 not allowed with read format &1

SAP Error Message - Details

• Message type: E = Error

• Message class: /EACC/MSG_ABSTR_JRNL -

• Message number: 015

• Message text: Internal error: Selection according to &2 not allowed with read format &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 /EACC/MSG_ABSTR_JRNL015 - Internal error: Selection according to &2 not allowed with read format &1 ?

  The SAP error message /EACC/MSG_ABSTR_JRNL015 Internal error: Selection according to &2 not allowed with read format &1 typically indicates an issue related to the selection criteria used in a report or transaction that is not compatible with the specified read format. This error is often encountered in the context of financial accounting or journal entries in SAP.
  Cause:
  
  Incompatible Selection Criteria: The error suggests that the selection criteria (indicated by &2) you are trying to use is not allowed with the specified read format (indicated by &1). This can happen if the selection fields are not supported for the type of data retrieval being performed.
  Configuration Issues: There may be configuration settings in the system that restrict certain types of selections based on the read format.
  Data Model Changes: If there have been recent changes to the data model or the underlying tables, it may lead to inconsistencies in how data can be accessed.
  
  Solution:
  
  Review Selection Criteria: Check the selection criteria you are using in the report or transaction. Ensure that they are compatible with the read format specified. You may need to adjust the fields you are using for selection.
  Consult Documentation: Refer to the SAP documentation or help files related to the specific transaction or report you are using. This may provide insights into valid selection criteria.
  Check Configuration: If you have access, review the configuration settings related to the report or transaction. Ensure that the settings allow for the selection criteria you are trying to use.
  Contact SAP Support: If the issue persists and you cannot identify the cause, consider reaching out to SAP support for assistance. They may have additional insights or patches available for known issues.
  
  Related Information:
  
  Transaction Codes: Identify the specific transaction code or report that triggered the error. This can help in troubleshooting.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error message or provide guidance on similar issues.
  System Logs: Check system logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
  User Forums: Consider checking SAP community forums or user groups for discussions related to this error, as other users may have encountered and resolved similar issues.
  
  By following these steps, you should be able to diagnose and potentially resolve the error message you are encountering in SAP.