How To Fix FKKBIX636 - It was not possible to derive any posting settings

SAP Error Message - Details

• Message type: E = Error

• Message class: FKKBIX - Conv.Inv.: Billing (Invoice Preprocessing)

• Message number: 636

• Message text: It was not possible to derive any posting settings

What causes this issue?

Make sure that the <DS:SIMG._FICABI_FQ8118>posting settings</> can be
derived for the <DS:DE.DISCKEY_KK>discount/charge key</>&V1&.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Check your system settings.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FKKBIX636 - It was not possible to derive any posting settings ?

  The SAP error message FKKBIX636, which states "It was not possible to derive any posting settings," typically occurs in the context of financial accounting and can be related to various issues in the configuration or data setup. Here’s a breakdown of the potential causes, solutions, and related information:
  Causes:
  
  Missing Configuration: The posting settings for the relevant transaction or document type may not be configured correctly in the system.
  Incorrect Account Determination: The system may not be able to determine the correct accounts for posting due to missing or incorrect account determination settings.
  Missing Master Data: Required master data (like vendor, customer, or GL accounts) may be missing or incorrectly set up.
  Document Type Issues: The document type being used may not have the necessary settings defined for posting.
  Transaction Type Issues: The transaction type may not be linked to the correct posting settings in the configuration.
  Authorization Issues: The user may not have the necessary authorizations to perform the posting.
  
  Solutions:
  
  
  Check Configuration:
  
  Go to the configuration settings in SAP (transaction code SPRO) and verify the settings for account determination, document types, and transaction types.
  Ensure that the necessary posting settings are defined for the relevant transaction.
  
  
  
  Review Master Data:
  
  Check the master data for the relevant accounts (e.g., vendor, customer, GL accounts) to ensure they are correctly set up and active.
  Ensure that the accounts are assigned to the correct company code and are not blocked.
  
  
  
  Analyze the Document Type:
  
  Verify that the document type being used has the necessary settings for posting. This can be done in the configuration under Financial Accounting.
  
  
  
  Check Transaction Type:
  
  Ensure that the transaction type is correctly linked to the posting settings in the configuration.
  
  
  
  User Authorizations:
  
  Check if the user has the necessary authorizations to perform the posting. This can be done by reviewing the user roles and authorizations.
  
  
  
  Debugging:
  
  If the issue persists, consider using the debugging tools in SAP to trace the execution and identify where the posting settings are failing to derive.
  
  
  
  Related Information:
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for FKKBIX636 in the SAP Support Portal.
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  SPRO: Customizing settings
  OBYC: Automatic account determination
  FS00: Create/Change G/L account
  FK01: Create Vendor
  FD01: Create Customer
  
  
  
  Documentation: Review SAP documentation related to financial accounting and posting settings for more detailed guidance.
  
  
  If the problem continues after checking these areas, it may be beneficial to consult with your SAP support team or a consultant who specializes in SAP Financial Accounting.