How To Fix FKKINFCO020 - Specify a save type

SAP Error Message - Details

• Message type: E = Error

• Message class: FKKINFCO - Information Container

• Message number: 020

• Message text: Specify a save type

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 FKKINFCO020 - Specify a save type ?

  The SAP error message FKKINFCO020: "Specify a save type" typically occurs in the context of the Contract Accounts Receivable and Payable (FI-CA) module when a user is trying to save a transaction or document without specifying a required save type. This error can arise in various scenarios, such as when processing incoming payments, creating invoices, or managing customer accounts.
  Cause:
  The error is generally caused by one of the following reasons:
  
  Missing Save Type: The system requires a specific save type to be defined for the transaction you are trying to execute. This could be due to configuration settings or missing parameters in the transaction.
  Custom Development: If there are custom programs or enhancements in place, they may not be correctly handling the save type, leading to this error.
  User Input: The user may not have filled in all the necessary fields or parameters required for the transaction.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Configuration:
  
  Ensure that the configuration for the relevant transaction is set up correctly in the SAP system. This may involve checking the settings in the FI-CA module related to the specific transaction you are trying to perform.
  
  
  
  Specify Save Type:
  
  If the transaction screen has a field for specifying the save type, make sure to fill it in. The save type could be options like "Save", "Post", or other relevant types depending on the context.
  
  
  
  Review User Input:
  
  Double-check all the fields you have filled out in the transaction. Ensure that all mandatory fields are completed and that there are no missing values.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help files related to the specific transaction you are working with. This can provide insights into what save types are available and how to specify them.
  
  
  
  Debugging:
  
  If you have access to debugging tools, you can analyze the program flow to see where the save type is being set or expected. This can help identify if there is a coding issue or a missing configuration.
  
  
  
  Contact Support:
  
  If the issue persists after trying the above steps, consider reaching out to your SAP support team or consulting with an SAP expert who can provide more tailored assistance based on your specific system configuration.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes in the FI-CA module that may be related to the error.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.