How To Fix >4736 - Date specification missing - collection will be made at due date


SAP Error Message - Details

  • Message type: E = Error

  • Message class: >4 - SAP File Transfer Protocol

  • Message number: 736

  • Message text: Date specification missing - collection will be made at due date

  • Show details Hide details


  • 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 >4736 - Date specification missing - collection will be made at due date ?

    The SAP error message "4736 Date specification missing - collection will be made at due date" typically occurs in the context of accounts receivable or accounts payable when a date for a collection or payment is not specified. This can happen in various scenarios, such as when processing invoices, payment requests, or collections.

    Cause:

    1. Missing Date Specification: The primary cause of this error is that the system expects a specific date for the collection or payment, but it has not been provided. This could be due to:

      • Incorrect or incomplete data entry.
      • Missing configuration settings in the payment terms or collection process.
      • A system error or oversight in the transaction processing.
    2. Configuration Issues: Sometimes, the configuration settings in the financial module may not be set up correctly, leading to the system not being able to determine the appropriate date for the collection.

    Solution:

    1. Check Data Entry: Review the transaction or document that triggered the error. Ensure that all required fields, especially those related to dates (like due date, payment date, etc.), are filled in correctly.

    2. Review Payment Terms: Check the payment terms associated with the transaction. Ensure that they are correctly defined and that they include the necessary date specifications.

    3. Configuration Settings: If the issue persists, consult with your SAP configuration team to review the settings related to collections and payments. Ensure that the relevant parameters are set up correctly in the system.

    4. Manual Override: If the system allows, you may be able to manually specify the collection date to bypass the error temporarily. However, this should be done with caution and in accordance with your organization's policies.

    5. Consult Documentation: Refer to SAP documentation or help resources for more detailed guidance on the specific transaction or module you are working with.

    6. Contact Support: If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting with SAP support for further assistance.

    Related Information:

    • SAP Notes: Check for any relevant SAP Notes that might address this specific error message or provide additional context.
    • Transaction Codes: Familiarize yourself with the transaction codes related to accounts receivable and payable, as they may help you navigate the system more effectively.
    • User Training: Ensure that users involved in data entry and transaction processing are adequately trained to minimize the occurrence of such errors in the future.

    By addressing the root cause of the missing date specification, you can resolve the error and ensure that collections are processed correctly.

    • 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.


Related SAP Error Messages

Click the links below to see the following related messages:
  • >4735 Specify due date
    Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...

  • >4734 Run &1 &2 already exists
    trados = docu -> fi -> ficaWhat causes this issue? Note that the payment run (<LS>FPY1</>) and debit memo notification UK (<LS&...

  • >4737 Specify the business partner
    Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...

  • >4738 Contract account &1 does not exist
    Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...

Click on this link to search all SAP messages.


Rating
The AI Support Assistant is great. It provides comprehensive assistance even on the most difficult issues. I highly recommend this service.
Rate 1
John Jordan
SAP Consultant & Author