How To Fix FI_E159 - The original baseline date &1 was set to the invoice receipt date &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FI_E - Message Class for FM English Developers

• Message number: 159

• Message text: The original baseline date &1 was set to the invoice receipt date &2

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 FI_E159 - The original baseline date &1 was set to the invoice receipt date &2 ?

  The SAP error message FI_E159 indicates that there is a discrepancy between the original baseline date and the invoice receipt date in the context of financial transactions, particularly in accounts payable. This error typically arises when the system detects that the baseline date for a payment or invoice does not align with the date the invoice was received.
  Cause:
  
  Mismatch of Dates: The original baseline date (which is often the date when the invoice is created or the date of the purchase order) does not match the invoice receipt date. This can happen if the invoice is entered into the system after the goods receipt or if there are delays in processing.
  Configuration Issues: There may be configuration settings in the SAP system that dictate how baseline dates are determined, which could lead to inconsistencies.
  Manual Entry Errors: Users may inadvertently enter incorrect dates during invoice processing.
  
  Solution:
  
  Check Dates: Review the invoice and the associated purchase order or goods receipt to ensure that the dates are correct and consistent. Make sure that the baseline date is set appropriately.
  Adjust Baseline Date: If the baseline date is incorrect, you may need to adjust it manually in the invoice or payment document. This can often be done in the transaction where the invoice is processed.
  Review Configuration: If this error occurs frequently, it may be necessary to review the configuration settings related to baseline date determination in the SAP system. This may involve consulting with your SAP FI (Financial Accounting) consultant or system administrator.
  Reprocess Invoice: If the invoice has been incorrectly processed, you may need to reverse the invoice and re-enter it with the correct dates.
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on handling this error in your version of SAP.
  
  Related Information:
  
  Transaction Codes: Common transaction codes related to invoice processing include MIRO (Invoice Verification), FB60 (Enter Incoming Invoice), and FBL1N (Vendor Line Item Display).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP Notes can provide additional context or solutions.
  User Training: Ensure that users involved in invoice processing are trained on the importance of date accuracy and the implications of date mismatches.
  
  If the issue persists after following these steps, it may be beneficial to engage with SAP support or your internal IT team for further investigation.