How To Fix GLE_MCA613 - Position/equivalent account &1 &2 is not marked as 'post automatically'

SAP Error Message - Details

• Message type: E = Error

• Message class: GLE_MCA - Multicurrency Accounting

• Message number: 613

• Message text: Position/equivalent account &1 &2 is not marked as 'post automatically'

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 GLE_MCA613 - Position/equivalent account &1 &2 is not marked as 'post automatically' ?

  The SAP error message GLE_MCA613 indicates that a specific position or equivalent account is not marked for automatic posting. This error typically arises in the context of financial accounting, particularly when dealing with automatic postings in the General Ledger (GL) or during the execution of certain transactions that require automatic posting capabilities.
  Cause:
  The error occurs when:
  
  An account that is supposed to be used for automatic postings is not configured correctly in the system.
  The account is not marked as "post automatically" in the account settings.
  There may be a configuration issue in the financial accounting settings or in the specific transaction being executed.
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check Account Configuration:
  
  Go to the transaction code FS00 (G/L Account Master Record) to check the account settings.
  Enter the account number and the company code, then check the settings in the "Control Data" tab.
  Ensure that the "Post Automatically" checkbox is selected for the relevant account.
  
  
  
  Review Account Type:
  
  Ensure that the account type is appropriate for the transactions you are trying to execute. For example, certain accounts may not be suitable for automatic postings.
  
  
  
  Check Transaction Settings:
  
  If the error occurs during a specific transaction, review the configuration for that transaction. Ensure that it is set up to allow for automatic postings.
  
  
  
  Consult with a Financial Consultant:
  
  If you are unsure about the settings or the implications of changing them, consult with a financial consultant or an SAP expert who can provide guidance based on your specific configuration and business processes.
  
  
  
  Testing:
  
  After making the necessary changes, perform a test transaction to ensure that the error has been resolved.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  FS00: G/L Account Master Record
  OBY6: Define Automatic Account Determination
  OBD2: Define Document Types
  
  
  
  SAP Notes and Documentation:
  
  Check SAP Notes for any known issues or additional guidance related to this error message.
  Review SAP Help documentation for detailed information on account settings and automatic postings.
  
  
  
  User Roles and Authorizations:
  
  Ensure that the user executing the transaction has the necessary authorizations to make changes to account settings.
  
  
  
  By following these steps, you should be able to identify the cause of the error and implement the necessary changes to resolve it.