How To Fix FKK_ID_AR087 - The last day of the period is different to the last day of the month.

SAP Error Message - Details

• Message type: E = Error

• Message class: FKK_ID_AR - ARGENTINA: Legal report message class

• Message number: 087

• Message text: The last day of the period is different to the last day of the month.

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 FKK_ID_AR087 - The last day of the period is different to the last day of the month. ?

  The SAP error message FKK_ID_AR087 indicates that there is a discrepancy between the last day of the period being processed and the last day of the month. This error typically occurs in the context of contract accounts receivable and payable (FI-CA) when trying to post or process transactions that involve date-related calculations.
  Cause:
  
  Period-End Closing Issues: The error often arises during period-end closing activities when the system expects the last day of the period to align with the last day of the month.
  Incorrect Configuration: The fiscal year variant or period settings may not be configured correctly, leading to mismatches.
  Posting Date Issues: The posting date of the transaction may fall outside the expected range for the period being processed.
  Custom Logic: If there are custom developments or enhancements in the system, they might be causing the date mismatch.
  
  Solution:
  
  
  Check Period Settings: Verify the period settings in the configuration. Ensure that the last day of the period aligns with the last day of the month.
  
  Navigate to SPRO ? Financial Accounting ? Accounts Receivable and Accounts Payable ? Periodic Processing ? Define Posting Periods.
  
  
  
  Review Posting Dates: Ensure that the posting date of the transaction is correct and falls within the expected period. Adjust the posting date if necessary.
  
  
  Fiscal Year Variant: Check the fiscal year variant settings to ensure they are correctly defined. This can be done in:
  
  SPRO ? Financial Accounting ? Financial Accounting Global Settings ? Fiscal Year ? Define Fiscal Year Variant.
  
  
  
  Transaction Data: Review the transaction data for any inconsistencies. If the transaction is related to a specific contract or account, check the details for that account.
  
  
  Custom Code Review: If there are any custom developments, review the code to ensure that it does not interfere with the standard date calculations.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to this error message for any specific guidance or patches that may be available.
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Transaction Codes: Familiarize yourself with transaction codes like FBL1N, FBL3N, and FBL5N for reviewing account balances and transactions.
  Support: If the issue persists after checking the above points, 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.