How To Fix FKKSK_MSG021 - Return reason &1 determined (tab./SAPCE/FK_PTEXT) for ext.reason &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FKKSK_MSG - Slovakia - localization message class

• Message number: 021

• Message text: Return reason &1 determined (tab./SAPCE/FK_PTEXT) for ext.reason &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 FKKSK_MSG021 - Return reason &1 determined (tab./SAPCE/FK_PTEXT) for ext.reason &2 ?

  The SAP error message FKKSK_MSG021 typically relates to issues in the contract accounts receivable and payable (FI-CA) module, specifically concerning the determination of return reasons for payment processing. This error indicates that a return reason has been determined for a specific external reason code, but there may be issues with the configuration or data that need to be addressed.
  Cause:
  
  Configuration Issues: The return reason may not be properly configured in the system. This can happen if the mapping between external reason codes and internal return reasons is not set up correctly.
  Missing Entries: There may be missing entries in the relevant tables that link external reason codes to return reasons.
  Data Inconsistencies: There could be inconsistencies in the data being processed, such as incorrect or unexpected values being passed to the system.
  
  Solution:
  
  
  Check Configuration:
  
  Navigate to the configuration settings for return reasons in the SAP system. This is usually found under the path: SPRO > Financial Accounting > Accounts Receivable and Accounts Payable > Contract Accounts Receivable and Payable > Basic Functions > Payment Processing > Define Return Reasons.
  Ensure that the external reason codes are correctly mapped to the appropriate return reasons.
  
  
  
  Review Customizing Settings:
  
  Verify that the customizing settings for payment processing are correctly defined. This includes checking the settings for payment methods and return reasons.
  
  
  
  Data Validation:
  
  Check the data being processed to ensure that the external reason code being used is valid and exists in the system.
  Use transaction codes like SE16 or SE11 to view the relevant tables (e.g., /SAPCE/FK_PTEXT) to confirm that the necessary entries are present.
  
  
  
  Testing:
  
  After making any changes, perform tests to ensure that the return reasons are now being determined correctly without triggering the error message.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to this error message for any specific guidance or updates that may apply to your version of SAP.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  FBL1N: Vendor Line Item Display
  FBL5N: Customer Line Item Display
  FBRA: Reset Cleared Items
  
  
  SAP Notes: Check for any SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Support: If the issue persists after checking the configuration and data, consider reaching out to SAP support for further assistance.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.