How To Fix FKKEXC071 - Entries for credit cards, postal remittances, and checks not allowed

SAP Error Message - Details

• Message type: E = Error

• Message class: FKKEXC - Message Class for External Payments

• Message number: 071

• Message text: Entries for credit cards, postal remittances, and checks not allowed

What causes this issue?

An <GL:445FCEB1A2E10047E10000000A155435>offline branch</> (category B)
has tried to report payments with details on credit cards, postal
remittances, and checks. The external cash desk/branch carries out
payment processing. Details on credit cards, postal remittances, and
checks are not required in Contract Accounts Receivable and Payable for
further processing the payments received by the external cash
desk/branch and are therefore rejected.

System Response

The system rejects the message. The data is not transferred to Contract
Accounts Receivable and Payable.

How to fix this error?

Make sure that the message does not contain any details on credit cards,
postal remittances, or checks.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FKKEXC071 - Entries for credit cards, postal remittances, and checks not allowed ?

  The SAP error message FKKEXC071 indicates that there are restrictions on the types of payment methods that can be used in a specific context, particularly when dealing with credit cards, postal remittances, and checks. This error typically arises in the context of contract accounts receivable and payable (FI-CA) when trying to process a payment that is not allowed for the current configuration.
  Cause:
  
  Payment Method Configuration: The payment method being used (credit card, postal remittance, or check) is not allowed for the specific transaction or account type.
  Account Type Restrictions: The account type (e.g., customer, vendor) may have restrictions on which payment methods can be used.
  Transaction Type: The specific transaction type may not support the payment method being attempted.
  Master Data Settings: The master data for the customer or vendor may not be set up to allow the specified payment method.
  
  Solution:
  
  
  Check Payment Method Configuration:
  
  Go to the configuration settings for payment methods in SAP (Transaction code: OBPM1 for payment methods in accounting).
  Ensure that the payment method you are trying to use is correctly configured and allowed for the relevant transaction type.
  
  
  
  Review Account Type Settings:
  
  Check the settings for the account type in the configuration (Transaction code: OBVC).
  Ensure that the account type allows the use of the payment method in question.
  
  
  
  Verify Transaction Type:
  
  Confirm that the transaction type you are processing supports the payment method. You may need to consult the documentation or configuration settings for the specific transaction type.
  
  
  
  Update Master Data:
  
  Review the master data for the customer or vendor involved in the transaction (Transaction code: FD03 for customers, FK03 for vendors).
  Ensure that the payment method is allowed in the master data settings.
  
  
  
  Consult with SAP Support:
  
  If the issue persists after checking the above configurations, 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 OBPM1, OBVC, FD03, and FK03 for navigating through the configuration and master data.
  Documentation: Review SAP documentation related to payment methods and account types for a deeper understanding of the configurations.
  User Roles and Authorizations: Ensure that the user attempting the transaction has the necessary authorizations to use the specified payment method.
  
  By following these steps, you should be able to identify the cause of the error and implement the necessary changes to resolve it.