How To Fix BOS01175 - In service conds: service PCKG_NO &1,LINE_NO &2 basic price missing

SAP Error Message - Details

• Message type: E = Error

• Message class: BOS01 - Customer BOS Processing

• Message number: 175

• Message text: In service conds: service PCKG_NO &1,LINE_NO &2 basic price missing

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 BOS01175 - In service conds: service PCKG_NO &1,LINE_NO &2 basic price missing ?

  The SAP error message BOS01175 indicates that there is a missing basic price for a service condition in a pricing procedure. This error typically occurs in the context of service-related transactions, such as service orders or service contracts, where pricing conditions are defined for services.
  Cause:
  
  Missing Basic Price: The primary cause of this error is that the basic price for the specified service package (PCKG_NO) and line number (LINE_NO) is not maintained in the system.
  Incorrect Configuration: The pricing procedure may not be correctly configured to include the necessary condition types for the service.
  Data Inconsistency: There may be inconsistencies in the master data or transaction data that lead to the absence of the required pricing information.
  Condition Records Not Created: Condition records for the service may not have been created or may have been deleted.
  
  Solution:
  
  
  Check Condition Records:
  
  Go to the transaction code VK11 (Create Condition) or VK12 (Change Condition) to check if the condition records for the service in question exist.
  Ensure that the basic price condition type is maintained for the relevant service package and line number.
  
  
  
  Maintain Pricing Conditions:
  
  If the condition records are missing, create them by entering the necessary details, including the service package number and the basic price.
  
  
  
  Review Pricing Procedure:
  
  Check the pricing procedure assigned to the service order or contract. Ensure that it includes the necessary condition types for pricing.
  You can review the pricing procedure in the configuration settings (transaction code SPRO).
  
  
  
  Check Master Data:
  
  Verify that the service master data is correctly maintained and that all relevant fields are filled out, including pricing information.
  
  
  
  Consult Documentation:
  
  If you are unsure about the configuration or the required condition types, refer to SAP documentation or consult with your SAP functional consultant.
  
  
  
  Testing:
  
  After making the necessary changes, test the transaction again to ensure that the error is resolved.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  VK11, VK12: For maintaining condition records.
  SPRO: For accessing the configuration settings.
  
  
  Condition Types: Familiarize yourself with the condition types used in your pricing procedure, as they determine how prices are calculated.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message.
  
  If the issue persists after following these steps, it may be beneficial to engage with your SAP support team or consult SAP's support portal for further assistance.