How To Fix FMCA_INCORR017 - Period key &1 and key date &2 both specified

SAP Error Message - Details

• Message type: E = Error

• Message class: FMCA_INCORR - Messages for Inbound Correspondence

• Message number: 017

• Message text: Period key &1 and key date &2 both specified

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 FMCA_INCORR017 - Period key &1 and key date &2 both specified ?

  The SAP error message FMCA_INCORR017 indicates that there is an issue with the period key and key date specified in a financial transaction or document. This error typically arises in the context of Funds Management (FM) or Controlling (CO) modules when there is a mismatch or inconsistency in the data being processed.
  Cause:
  The error occurs when both a period key and a key date are specified in a transaction, which is not allowed. The system expects either a period key or a key date, but not both at the same time. This can happen due to:
  
  Incorrect Configuration: The system configuration may not be set up to handle both parameters simultaneously.
  User Input Error: The user may have inadvertently entered both values in the transaction screen.
  Programmatic Error: If a custom program or report is being used, it may be incorrectly passing both parameters to the function module.
  
  Solution:
  To resolve the FMCA_INCORR017 error, you can take the following steps:
  
  
  Check Input Values: Review the transaction or document where the error occurred. Ensure that only one of the two fields (period key or key date) is filled in. Remove one of the values as appropriate.
  
  
  Review Configuration: If you are an administrator or have access to configuration settings, check the settings related to the Funds Management or Controlling modules to ensure they are correctly configured to handle period keys and key dates.
  
  
  Debug Custom Programs: If the error arises from a custom program or report, review the code to ensure that it is not passing both parameters to the function module. Modify the code to ensure that only one of the parameters is passed based on the business logic.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for further details on the specific transaction or function module you are working with. This can provide insights into the expected input parameters.
  
  
  Contact SAP Support: If the issue persists and you cannot identify the cause, consider reaching out to SAP support for assistance. They can provide more detailed guidance based on your specific system configuration and usage.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with the transaction codes related to Funds Management and Controlling, as they may provide additional context for the error.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error message or provide patches or updates that could resolve the issue.
  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.