Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now

Close

How To Fix 67_PAYMENTS603 - Planned record for payment could not be built


SAP Error Message - Details

  • Message type: E = Error

  • Message class: 67_PAYMENTS - Message Class Incoming Payment / Payment Postprocessing

  • Message number: 603

  • Message text: Planned record for payment could not be built

  • 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 67_PAYMENTS603 - Planned record for payment could not be built ?

    The SAP error message 67_PAYMENTS603 ("Planned record for payment could not be built") typically occurs in the context of payment processing in SAP, particularly when dealing with payment runs. This error indicates that the system was unable to create a planned payment record for one or more items in the payment run.

    Causes:

    1. Missing Payment Information: The vendor or customer master data may be incomplete or missing necessary payment information, such as bank details or payment terms.
    2. Incorrect Payment Method: The payment method specified may not be valid for the vendor or customer, or it may not be configured correctly in the system.
    3. Payment Block: The invoice or document may be blocked for payment due to various reasons, such as disputes or holds.
    4. Currency Issues: There may be issues related to currency conversion or mismatches between the document currency and the payment currency.
    5. Configuration Issues: There may be configuration issues in the payment program settings or in the payment method settings.
    6. Document Status: The document may not be in a status that allows it to be processed for payment (e.g., it may be in a "parked" status).

    Solutions:

    1. Check Vendor/Customer Master Data: Ensure that the vendor or customer master data is complete and contains all necessary payment information, including bank details and payment terms.
    2. Review Payment Method: Verify that the payment method used is valid for the vendor or customer and is correctly configured in the system.
    3. Check Payment Blocks: Investigate if there are any payment blocks on the invoice or document that need to be resolved.
    4. Currency Configuration: Ensure that the currency settings are correct and that there are no mismatches between the document currency and the payment currency.
    5. Review Payment Program Configuration: Check the configuration of the payment program and ensure that all settings are correct and aligned with the business requirements.
    6. Document Status: Ensure that the document is in a status that allows it to be processed for payment. If it is parked or in another non-postable status, take the necessary steps to change its status.

    Related Information:

    • Transaction Codes: You may use transaction codes like F110 (Automatic Payment Transactions) to run the payment program and check for errors.
    • Logs and Traces: Check the payment run logs for detailed error messages and additional information that can help identify the root cause.
    • SAP Notes: Look for relevant SAP Notes in the SAP Support Portal that may address known issues related to this error message.
    • Consult Documentation: Review SAP documentation related to payment processing and configuration for further insights.

    If the issue persists after checking the above points, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in financial processes within SAP.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Sign up for our Free Essentials Plan.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant