How To Fix FKKEXC270 - Ext.journal trans. &3, cash desk &1/&2 set to manual processing status

SAP Error Message - Details

• Message type: E = Error

• Message class: FKKEXC - Message Class for External Payments

• Message number: 270

• Message text: Ext.journal trans. &3, cash desk &1/&2 set to manual processing status

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 FKKEXC270 - Ext.journal trans. &3, cash desk &1/&2 set to manual processing status ?

  The SAP error message FKKEXC270 indicates that an external journal transaction (identified by &3) for a specific cash desk (identified by &1 and &2) has been set to a manual processing status. This typically occurs in the context of the SAP Contract Accounts Receivable and Payable (FI-CA) module, which is used for managing customer accounts and transactions.
  Cause:
  The error can be caused by several factors, including:
  
  
  Manual Processing Status: The cash desk has been set to manual processing, which means that transactions cannot be processed automatically. This could be due to configuration settings or specific business rules that require manual intervention for certain transactions.
  
  
  Configuration Issues: There may be configuration settings in the cash desk or external journal that restrict automatic processing.
  
  
  Transaction Type Restrictions: The specific transaction type being processed may not be allowed for automatic processing in the current configuration.
  
  
  User Authorizations: The user attempting to process the transaction may not have the necessary authorizations to perform automatic processing.
  
  
  Solution:
  To resolve the error, consider the following steps:
  
  
  Check Cash Desk Settings: Review the configuration of the cash desk (transaction code: OBCM) to ensure that it is set up correctly for automatic processing. If it is intentionally set to manual processing, determine if this is appropriate for the transaction in question.
  
  
  Review External Journal Configuration: Check the settings for the external journal (transaction code: FKKJOURNAL) to ensure that it allows for automatic processing of the relevant transaction types.
  
  
  Adjust Transaction Type Settings: If the transaction type is restricted, you may need to adjust the settings to allow for automatic processing.
  
  
  User Authorizations: Ensure that the user has the necessary authorizations to process transactions automatically. This may involve checking roles and permissions in the SAP system.
  
  
  Consult Documentation: Review SAP documentation or consult with your SAP support team for specific guidance related to your system configuration and business processes.
  
  
  Manual Processing: If automatic processing is not possible or appropriate, you may need to process the transaction manually as indicated by the error message.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OBCM (Cash Desk Configuration), FKKJOURNAL (External Journal Configuration), and SU01 (User Maintenance) for checking user authorizations.
  SAP Notes: Check for any SAP Notes related to this error message for additional insights or patches that may address known issues.
  Support: If the issue persists, consider reaching out to SAP support or your internal SAP team for further assistance.
  
  By following these steps, you should be able to identify the cause of the error and implement a suitable solution.