/ATL/GENERAL806 - No base date found; start date of the terms is used

SAP Error Message - Details

• Message type: E = Error

• Message class: /ATL/GENERAL -

• Message number: 806

• Message text: No base date found; start date of the terms is used

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.

AnswerBot

• What is the cause and solution for SAP error message /ATL/GENERAL806 - No base date found; start date of the terms is used ?

  The SAP error message /ATL/GENERAL806 No base date found; start date of the terms is used typically occurs in the context of the Automatic Payment Program (APP) or when dealing with payment terms in SAP. This error indicates that the system could not find a base date for the payment terms specified, and as a result, it defaults to using the start date of the payment terms.
  Cause:
  
  
  Missing Base Date: The primary cause of this error is that the system is unable to determine a base date for the payment terms associated with the transaction. This could be due to:
  
  The payment terms not being properly configured.
  The relevant document (like an invoice) not having a valid posting date or due date.
  The payment terms being set up incorrectly in the master data.
  
  
  
  Configuration Issues: There may be issues in the configuration of the payment terms in the SAP system, such as missing or incorrect settings in the payment term configuration.
  
  
  Document Type Issues: The document type being used may not be compatible with the payment terms or may not have the necessary settings.
  
  
  Solution:
  
  
  Check Payment Terms: Verify the payment terms assigned to the document. Ensure that they are correctly configured in the system and that they have a valid base date defined.
  
  
  Review Document Dates: Ensure that the document (invoice, purchase order, etc.) has valid posting dates and due dates. If the document is missing these dates, the system will not be able to calculate the payment date correctly.
  
  
  Configuration Review: If you have access to the configuration settings, check the payment terms configuration in the SAP system:
  
  Go to the configuration path: SPRO -> Financial Accounting -> Accounts Receivable and Accounts Payable -> Business Transactions -> Outgoing Payments -> Automatic Payment Transactions -> Define Payment Terms.
  Ensure that the payment terms are set up correctly, including the base date settings.
  
  
  
  Document Type Settings: Check the settings for the document type being used. Ensure that it is compatible with the payment terms and that it has the necessary configurations.
  
  
  Consult Documentation: If the issue persists, consult SAP documentation or reach out to your SAP support team for further assistance. They may have additional insights or updates regarding this error.
  
  
  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 FBZP (for payment program configuration) and FBL1N (for vendor line items) to help diagnose the issue.
  User Exits and BAdIs: If custom logic is implemented in your SAP system, check for any user exits or BAdIs that might affect payment term processing.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.