How To Fix BOS03012 - Condition type &1 does not exist in pricing procesure &2

SAP Error Message - Details

• Message type: E = Error

• Message class: BOS03 - Costing: Sales Documents with BOS

• Message number: 012

• Message text: Condition type &1 does not exist in pricing procesure &2

What causes this issue?

Condition type &V1& either does not exist in costing sheet &V2& or is
not of condition category "Q".

System Response

The calculated costs are not copied.

How to fix this error?

Check your Customizing settings under <ZK>Bill of Services</>.
Edit the costing sheet &V2& or assign condition category "Q" to
condition type &V1&.
You can find further information in Customizing for <ZK>Bill of
Services</> under
<DS:SIMG.SIMG_BOS_COND_1>Define Condition Types</>
<DS:SIMG.SIMG_BOS_COND_2>Define Costing Sheets</>

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 BOS03012 - Condition type &1 does not exist in pricing procesure &2 ?

  The SAP error message BOS03012 indicates that a specific condition type (denoted as &1) is not found in the pricing procedure (denoted as &2) that is being used in the transaction. This error typically occurs during pricing determination in sales documents, purchase orders, or other related transactions.
  Cause:
  
  Missing Condition Type: The specified condition type is not defined in the pricing procedure.
  Incorrect Pricing Procedure Assignment: The pricing procedure assigned to the document may not be the correct one for the transaction type or customer/vendor.
  Configuration Issues: There may be issues in the configuration of the pricing procedure or condition types in the SAP system.
  Transport Issues: If the pricing procedure was recently transported from another system, it may not have been fully configured in the target system.
  
  Solution:
  
  
  Check Condition Type: Verify that the condition type specified in the error message exists in the system. You can do this by navigating to the condition types configuration in SPRO:
  
  Path: SPRO -> Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control -> Define Condition Types
  
  
  
  Check Pricing Procedure: Ensure that the pricing procedure assigned to the document includes the specified condition type. You can check this in:
  
  Path: SPRO -> Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control -> Define Pricing Procedures
  Look for the pricing procedure in question and check if the condition type is included.
  
  
  
  Assign Correct Pricing Procedure: If the pricing procedure is incorrect, you may need to assign the correct pricing procedure to the relevant sales area, customer, or document type. This can be done in:
  
  Path: SPRO -> Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control -> Assign Pricing Procedures
  
  
  
  Review Configuration: If the condition type is missing, you may need to create it or add it to the pricing procedure. Ensure that all necessary condition types are configured correctly.
  
  
  Transport Check: If the issue arose after a transport, ensure that all necessary configuration settings were transported correctly. You may need to re-transport or manually configure the missing elements.
  
  
  Related Information:
  
  Transaction Codes: You can use transaction codes like VK11 (Create Condition), VK12 (Change Condition), and VK13 (Display Condition) to manage condition records.
  Debugging: If the issue persists, you may need to debug the pricing procedure determination process to identify where the failure occurs.
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide additional guidance on this error.
  
  By following these steps, you should be able to resolve the BOS03012 error and ensure that the pricing procedure is correctly configured in your SAP system.