How To Fix FKKCM104 - Interval &1 to &2 not updated

SAP Error Message - Details

• Message type: E = Error

• Message class: FKKCM - Credit Management

• Message number: 104

• Message text: Interval &1 to &2 not updated

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 FKKCM104 - Interval &1 to &2 not updated ?

  The SAP error message FKKCM104, which states "Interval &1 to &2 not updated," typically occurs in the context of contract accounts receivable and payable (FI-CA) when there is an issue with updating the specified interval in the system. This error can arise due to various reasons, including data inconsistencies, incorrect configurations, or issues with the underlying business processes.
  Causes:
  
  Data Inconsistencies: There may be inconsistencies in the data that prevent the system from updating the specified interval.
  Incorrect Configuration: The configuration settings for the contract accounts may not be set up correctly, leading to issues when trying to update intervals.
  Missing Authorizations: The user may not have the necessary authorizations to perform the update.
  Locked Records: The records that need to be updated might be locked by another process or user.
  Technical Issues: There could be underlying technical issues, such as database locks or system errors.
  
  Solutions:
  
  Check Data Consistency: Review the data related to the contract accounts and ensure that there are no inconsistencies. You can use transaction codes like SARA or SDBA to check for inconsistencies.
  Review Configuration: Verify the configuration settings in the FI-CA module to ensure they are set up correctly. This may involve checking the settings for the relevant contract accounts and intervals.
  User Authorizations: Ensure that the user attempting to perform the update has the necessary authorizations. You can check this in the user roles and profiles.
  Unlock Records: If records are locked, identify the user or process that has locked them and resolve the issue. You can use transaction code SM12 to view and manage locked entries.
  Check for Technical Issues: Review system logs and error messages for any underlying technical issues. You can use transaction codes like SM21 for system logs and ST22 for dump analysis.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message. There may be patches or updates available that resolve the issue.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FBL5N (Customer Line Item Display), FBL1N (Vendor Line Item Display), and SARA (Archive Administration) for managing data.
  Documentation: Review SAP documentation related to FI-CA for more detailed information on contract accounts and their management.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  
  If the issue persists after trying the above solutions, it may be necessary to involve your SAP Basis or technical team for further investigation.