M8356 - Baseline date for payment does not exist


SAP Error Message - Details

  • Message type: E = Error

  • Message class: M8 - Invoice Verification/Valuation

  • Message number: 356

  • Message text: Baseline date for payment does not exist

  • Show details Hide details
  • What causes this issue?

    You have tried to post a document without a baseline date for payment.
    The system does not allow you to do this.

    System Response

    The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

    How to fix this error?

    Check the purchase order. Either no term of payment has been entered in
    the document header or no proposal for the baseline date for payment has
    been defined in Customizing for the term of payment entered.
    If you see this error message during automatic settlement of planned
    delivery costs, maintain the term of payment in the master record
    (payment transactions for accounting) of the freight supplier or use
    Business Add-In MRM_ERS_HDAT_MODIFY to determine the term of payment.

    Procedure for System Administrators


    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message M8356 - Baseline date for payment does not exist ?

    The SAP error message M8356, "Baseline date for payment does not exist," typically occurs in the context of invoice processing or payment processing in SAP. This error indicates that the system cannot find a baseline date for the payment terms associated with a particular invoice or document. The baseline date is crucial for determining payment due dates and calculating discounts.

    Causes:

    1. Missing Baseline Date: The invoice or document does not have a baseline date set. This can happen if the invoice was created without proper payment terms or if the payment terms do not have a baseline date defined.
    2. Incorrect Payment Terms: The payment terms assigned to the invoice may not be configured correctly in the system, leading to the absence of a baseline date.
    3. Document Type Issues: The document type used for the invoice may not support baseline dates.
    4. Configuration Issues: There may be configuration issues in the Financial Accounting (FI) or Materials Management (MM) modules that affect how baseline dates are determined.

    Solutions:

    1. Check Payment Terms: Verify the payment terms assigned to the invoice. Ensure that they are correctly configured in the system and that they include a baseline date.

      • Go to the transaction code OBB8 to check and maintain payment terms.
    2. Review Invoice Details: Check the invoice for any missing information. Ensure that all necessary fields are filled out correctly, including the payment terms and any relevant dates.

      • You can use transaction codes like FB03 (Display Document) to review the invoice details.
    3. Set Baseline Date Manually: If the baseline date is missing, you may need to set it manually. This can often be done in the invoice or payment processing screen.

      • In the case of a payment run, you may need to adjust the payment proposal to include a baseline date.
    4. Configuration Check: If the issue persists, consult with your SAP configuration team to ensure that the payment terms and related settings are correctly configured in the system.

      • Check the configuration in SPRO under Financial Accounting (FI) > Accounts Payable > Payment Transactions > Define Payment Terms.
    5. Consult Documentation: Review SAP documentation or help resources for any specific notes or updates related to this error message.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as FB60 (Enter Incoming Invoice), F110 (Automatic Payment Transactions), and OBB8 (Define Payment Terms).
    • SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for notes in the SAP Support Portal.
    • User Roles: Ensure that the user has the necessary authorizations to view and edit payment terms and invoices.

    By following these steps, you should be able to identify the cause of the M8356 error and implement a solution to resolve it. If the problem persists, consider reaching out to your SAP support team for further assistance.

    Artificial intelligence solution provided by tomco.ai.
    Disclaimer
    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Feature Free Access Free Trial
Basic SAP error explanation T-Code Explanation T-Code Explanation 2
Step-by-Step Usage Guide Step-by-Step Step-by-Step 2
Interactive SAP Coach Assistance Interactive SAP Interactive SAP 2
AI Troubleshooting for T-Code Errors AI Troubleshooting AI Troubleshooting 2

Related SAP Error Messages

Click the links below to see the following related messages:


SAP messages fall into 3 different categories: Error messages (message type = E), Warnings (W) or Informational (I) messages.

An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.

Click on this link to search all SAP messages.


Rating
ERPlingo's SAP support assistant is amazing. Saves me countless hours trying to solve complex SAP issues myself. It's a real game changer!
Rate 1
Thomas Michael
SAP Consultant, Author & Speaker