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

Close

How To Fix W_CB353 - Condition types with Condition ID subsequent settlement are not supported


SAP Error Message - Details

  • Message type: E = Error

  • Message class: W_CB -

  • Message number: 353

  • Message text: Condition types with Condition ID subsequent settlement are not supported

  • 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 W_CB353 - Condition types with Condition ID subsequent settlement are not supported ?

    Certainly! Here's a detailed explanation regarding the SAP error message:


    SAP Error Message:

    W_CB353 Condition types with Condition ID subsequent settlement are not supported


    Cause:

    This warning message occurs in SAP Contract Accounts Receivable and Payable (FI-CA) when you try to use condition types that have the Condition ID set to "Subsequent Settlement" in a context where such condition types are not supported.

    • Condition ID "Subsequent Settlement" is a special classification used in FI-CA for condition types that are intended to be applied during subsequent settlement processes (e.g., adjustments, corrections, or settlements after the initial billing).
    • The system does not allow these condition types to be used in certain pricing or settlement procedures because they are designed specifically for subsequent settlement scenarios.
    • This message typically appears during pricing or settlement runs when the system detects that a condition type with this ID is being processed in an unsupported context.

    When does it occur?

    • During contract or billing document processing in FI-CA.
    • When condition types with Condition ID "Subsequent Settlement" are assigned to pricing procedures or settlement rules that do not support them.
    • When customizing or master data incorrectly assigns these condition types in contexts other than subsequent settlement.

    Solution:

    1. Check Condition Type Configuration:

      • Go to transaction SPRO ? SAP Reference IMG ? Contract Accounts Receivable and Payable ? Basic Functions ? Pricing ? Define Condition Types.
      • Identify the condition types that have the Condition ID set to "Subsequent Settlement".
      • Verify if these condition types are assigned to pricing or settlement procedures where they are not supported.
    2. Adjust Pricing or Settlement Procedure:

      • Remove or replace the condition types with Condition ID "Subsequent Settlement" from pricing or settlement procedures where they are not allowed.
      • Use appropriate condition types that are supported in the given context.
    3. Review Business Process:

      • Ensure that condition types intended for subsequent settlement are only used in subsequent settlement runs or processes.
      • If you need to apply similar conditions in initial billing or other processes, create separate condition types without the "Subsequent Settlement" ID.
    4. Testing:

      • After adjustments, test the billing or settlement process to confirm that the warning no longer appears and that pricing/settlement behaves as expected.

    Related Information:

    • FI-CA Pricing and Settlement:
      Condition types in FI-CA are used to calculate amounts during billing and settlement. The Condition ID categorizes condition types for different purposes (e.g., initial billing, subsequent settlement, interest calculation).

    • Condition ID "Subsequent Settlement":
      This ID is specifically for conditions applied during subsequent settlement runs, such as corrections or adjustments after the initial invoice.

    • SAP Notes and Documentation:
      Check SAP Notes related to FI-CA pricing and settlement for any updates or known issues regarding condition types and Condition IDs.

    • Transaction Codes:

      • SPRO – Customizing
      • FPAYH – Subsequent Settlement Processing
      • FPCJ – Contract Accounts Receivable and Payable: Condition Types

    Summary:

    Aspect Details
    Cause Condition types with Condition ID "Subsequent Settlement" used in unsupported context.
    Effect Warning message W_CB353 during pricing or settlement processing.
    Solution Remove or replace these condition types from unsupported procedures; use correct types.
    Where to Check FI-CA condition type configuration in SPRO.
    Additional Info Condition ID categorizes condition types for specific processes in FI-CA.

    If you need further assistance, please provide details about the transaction or process where the message occurs, and the condition types involved.

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