How To Fix FARR_CONTRACT_MAIN118 - Leading POB &1 (for linked POB &2) has no main price cond.


SAP Error Message - Details

  • Message type: E = Error

  • Message class: FARR_CONTRACT_MAIN - Revenue Accounting: Contract Management

  • Message number: 118

  • Message text: Leading POB &1 (for linked POB &2) has no main price cond.

  • Show details Hide details
  • What causes this issue?

    The following configuration of performance obligations is not allowed:
    The performance obligations form a bill-of-material (BOM) structure.
    The top of the structure is a distinct performance obligation (with a
    composition type of "Distinct").
    The distinct performance obligation does not carry a pricing condition
    type that is marked as "main".

    System Response

    The system prevents you from creating or changing the performance
    obligation.

    How to fix this error?

    Make sure that the operational system specifies one pricing condition
    type as "main" when creating performance obligations.

    Procedure for System Administrators

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


    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message FARR_CONTRACT_MAIN118 - Leading POB &1 (for linked POB &2) has no main price cond. ?

    The SAP error message FARR_CONTRACT_MAIN118 indicates that there is an issue with the pricing conditions for a leading Purchase Order (POB) in a contract. Specifically, it states that the leading POB (Purchase Order Block) does not have a main price condition defined for the linked POB. This can occur in the context of contract management, particularly in the SAP module for contract and pricing management.

    Cause:

    1. Missing Main Price Condition: The leading POB does not have a main price condition set up, which is required for the linked POB to function correctly.
    2. Configuration Issues: There may be configuration issues in the pricing procedure or the condition types that are not set up correctly.
    3. Data Inconsistencies: There could be inconsistencies in the data between the leading and linked POBs, such as missing or incorrect entries in the pricing conditions.
    4. Contract Type: The type of contract being used may not support the pricing conditions required for the transaction.

    Solution:

    1. Check Pricing Conditions:

      • Go to the leading POB and check the pricing conditions. Ensure that a main price condition is defined.
      • If it is missing, you may need to create or adjust the pricing conditions accordingly.
    2. Review Configuration:

      • Check the configuration of the pricing procedure in the SAP system. Ensure that the condition types and access sequences are correctly set up.
      • Make sure that the main price condition is included in the pricing procedure for the relevant contract type.
    3. Data Consistency:

      • Verify that the data for both the leading and linked POBs is consistent. Look for any discrepancies in the condition records or other related data.
      • If necessary, update the records to ensure they match.
    4. Consult Documentation:

      • Review SAP documentation or help resources related to contract management and pricing conditions to ensure that you are following the correct procedures.
    5. Contact Support:

      • If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.

    Related Information:

    • Transaction Codes: You may need to use transaction codes such as ME33K (Display Contract) or ME32K (Change Contract) to review and modify the contract details.
    • SAP Notes: Check for any relevant SAP Notes that may address this specific error message or provide additional guidance.
    • Training and Documentation: Ensure that users involved in contract management are trained on the importance of maintaining accurate pricing conditions and the implications of missing data.

    By following these steps, you should be able to identify and resolve the issue related to the FARR_CONTRACT_MAIN118 error message in SAP.

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

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