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

Close

How To Fix WS113 - No settlement document list condition exists for invoicing party &


SAP Error Message - Details

  • Message type: E = Error

  • Message class: WS - Supplier Billing Document

  • Message number: 113

  • Message text: No settlement document list condition exists for invoicing party &

  • 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 WS113 - No settlement document list condition exists for invoicing party & ?

    SAP Error Message:
    WS113 - No settlement document list condition exists for invoicing party &


    Cause:

    This error occurs during the billing or settlement process in SAP when the system tries to determine the settlement document list condition for the invoicing party but cannot find any valid condition record. Essentially, the system expects a pricing condition (condition type) related to the settlement document list for the invoicing party, but none is maintained or found in the condition records.

    This typically happens in scenarios involving:

    • Settlement of internal orders, service orders, or projects where the invoicing party is involved.
    • Billing or settlement processes where the system needs to determine pricing or settlement conditions but the relevant condition records are missing.
    • Condition records for the settlement document list are not maintained for the invoicing party in the pricing procedure.

    Explanation:

    • The invoicing party is the business partner who will receive the invoice.
    • The settlement document list condition is a pricing condition that controls how settlement documents are processed and invoiced.
    • If the system cannot find a condition record for this combination, it throws WS113.

    Solution:

    1. Check Pricing Procedure:

      • Verify the pricing procedure assigned to the billing document or settlement document.
      • Ensure that the pricing procedure includes the condition type related to the settlement document list.
    2. Maintain Condition Records:

      • Use transaction VK11 (Create Condition) or VK12 (Change Condition) to maintain the required condition records.
      • The condition type related to the settlement document list (often a custom or standard condition type) must have valid records for the invoicing party.
      • Make sure the condition records are valid for the relevant sales area, customer (invoicing party), and validity dates.
    3. Check Master Data:

      • Verify the master data of the invoicing party (customer/vendor) to ensure it is correctly maintained.
      • Check if the invoicing party is correctly assigned in the settlement profile or billing document.
    4. Settlement Profile and Billing Settings:

      • Review the settlement profile settings in transaction OKO7 or relevant IMG path.
      • Ensure that the invoicing party is correctly configured in the settlement profile.
      • Check billing document types and their configuration to ensure they support the settlement process.
    5. Debugging / Logs:

      • If the above steps do not resolve the issue, debugging the billing or settlement program might be necessary to identify why the condition record is not found.
      • Check application logs (transaction SLG1) for more detailed error information.

    Related Information:

    • Transaction Codes:

      • VK11 / VK12 – Maintain pricing condition records
      • VA01 / VF01 – Create sales order / billing document
      • KO88 – Order settlement
      • OKO7 – Settlement profile configuration
      • SLG1 – Application log
    • SAP Notes / KBAs:

      • Search SAP Support Portal for notes related to WS113 or settlement document list condition.
      • Sometimes, OSS notes provide patches or detailed instructions for specific scenarios.
    • Configuration Paths:

      • IMG ? Sales and Distribution ? Basic Functions ? Pricing ? Pricing Control ? Define Pricing Procedures
      • IMG ? Controlling ? Internal Orders / Project System ? Settlement ? Define Settlement Profiles

    Summary:

    The WS113 error indicates missing pricing condition records for the invoicing party during settlement or billing. The fix involves ensuring that the pricing procedure includes the relevant condition type and that condition records exist for the invoicing party. Also, verify master data and settlement profile settings to ensure proper configuration.


    If you provide more details about the transaction or scenario where this error occurs, I can help with more specific guidance.

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