How To Fix FKCHK359 - Invalid Assignment Date &

SAP Error Message - Details

• Message type: E = Error

• Message class: FKCHK - Check Repository Messages

• Message number: 359

• Message text: Invalid Assignment Date &

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 FKCHK359 - Invalid Assignment Date & ?

  The SAP error message FKCHK359 "Invalid Assignment Date" typically occurs in the context of financial transactions, particularly when dealing with asset accounting or vendor invoices. This error indicates that the date you are trying to use for an assignment (such as posting an invoice or an asset transaction) is not valid according to the system's rules or configurations.
  Causes:
  
  Date Outside of Posting Period: The assignment date may fall outside of the open posting periods defined in the system.
  Invalid Date Format: The date may not be in the correct format or may not be recognized by the system.
  Fiscal Year Settings: The fiscal year settings may not allow for transactions to be posted on that date.
  Document Type Restrictions: Certain document types may have restrictions on the dates that can be used.
  Configuration Issues: There may be configuration settings in the asset accounting or financial accounting modules that restrict the use of certain dates.
  
  Solutions:
  
  Check Posting Periods: Verify that the posting period for the date you are trying to use is open. You can do this by navigating to the transaction code OB52 to check the open and closed periods.
  Correct Date Format: Ensure that the date is entered in the correct format as expected by the system.
  Review Fiscal Year Settings: Check the fiscal year settings in the configuration to ensure that the date falls within the allowed range.
  Document Type Configuration: Review the configuration for the document type you are using to ensure that it allows for the date you are trying to assign.
  Consult with SAP Support: If the issue persists, it may be beneficial to consult with your SAP support team or refer to SAP Notes for any known issues or patches related to this error.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OB52 (for posting periods), AS01 (for asset creation), and FB60 (for vendor invoices).
  SAP Notes: Search for SAP Notes related to FKCHK359 for any specific fixes or updates that may address this error.
  Documentation: Review SAP documentation on asset accounting and financial transactions for best practices and guidelines on date assignments.
  
  By following these steps, you should be able to identify the cause of the FKCHK359 error and implement a solution to resolve it.