How To Fix /SAPCE/FKRU309 - Invoice type &1 is not allowed for document &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPCE/FKRU -

• Message number: 309

• Message text: Invoice type &1 is not allowed for document &2

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 /SAPCE/FKRU309 - Invoice type &1 is not allowed for document &2 ?

  The SAP error message /SAPCE/FKRU309 Invoice type &1 is not allowed for document &2 typically occurs in the context of invoice processing within the SAP system, particularly when dealing with financial documents. This error indicates that the specified invoice type is not permitted for the given document type.
  Cause:
  
  
  Configuration Issues: The invoice type specified in the transaction may not be configured correctly in the system for the document type being processed. This could be due to missing or incorrect settings in the configuration of the invoice types and document types.
  
  
  Document Type Restrictions: Certain document types may have restrictions on which invoice types can be used. For example, some document types may only allow specific invoice types based on business rules or legal requirements.
  
  
  Data Entry Errors: There may be a mistake in the data entry where the wrong invoice type is selected for the document.
  
  
  Solution:
  
  
  Check Configuration: 
  
  Go to the configuration settings in SAP (transaction code SPRO) and navigate to the relevant section for invoice types and document types.
  Ensure that the invoice type you are trying to use is allowed for the document type in question. You may need to adjust the settings to allow the combination you are trying to use.
  
  
  
  Review Document Type Settings:
  
  Check the settings for the document type in question to see if there are any restrictions on the invoice types that can be used.
  If necessary, modify the settings to include the invoice type you need.
  
  
  
  Verify Data Entry:
  
  Double-check the data entry to ensure that the correct invoice type is being used for the document.
  If you find an error, correct it and try processing the document again.
  
  
  
  Consult Documentation: 
  
  Review any relevant SAP documentation or user manuals that pertain to invoice processing and document types to understand the allowed combinations.
  
  
  
  Contact SAP Support: 
  
  If the issue persists after checking the configuration and data entry, consider reaching out to SAP support for further assistance. They may provide insights specific to your system configuration.
  
  
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  SPRO: For configuration settings.
  FB60/FB70: For entering vendor/customer invoices.
  
  
  
  SAP Notes: Check for any SAP Notes related to this error message, as they may provide additional context or solutions.
  
  
  User Roles and Authorizations: Ensure that the user has the necessary authorizations to process the specific invoice type and document type.
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.