How To Fix BOS03008 - Cost transfer not possible; cond. types missing in pricing procedure &1

BOS03008 - Overview

• Message type: E = Error

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

• Message number: 008

• Message text: Cost transfer not possible; cond. types missing in pricing procedure &1

What causes this issue?

You have called <SE><LS>Easy Cost Planning</></> and exited it with
<LS>Save</> or <LS>Back</>.
The system attempts to copy the values for the condition items to the
service lines conditions. However, no condition type of condition
category <LB>Q</> could be found in pricing procedure &V1& to where the
calculated costs can be copied.

System Response

Processing is terminated.

How to fix this error?

Complete pricing procedure &V1& for the service conditions in the
customer BOS. Use condition types of category <LB>Q</>.
You can find further information in Customizing for <ZK>Bill of Service
</> under
<ZK>Pricing in BOS</>-> <DS:SIMG.SIMG_BOS_COND_1>Define Condition Types
</>
<ZK>Pricing in BOS</>-> <DS:SIMG.SIMG_BOS_COND_2>Define Pricing
Procedures</>

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 BOS03008 - Cost transfer not possible; cond. types missing in pricing procedure &1 ?

  The SAP error message BOS03008 indicates that a cost transfer is not possible because certain condition types are missing in the pricing procedure specified in the message. This typically occurs in the context of billing or invoice processing, where the system expects certain pricing conditions to be defined in the pricing procedure for the transaction to proceed.
  
  Cause:
  
  Missing Condition Types: The pricing procedure defined for the transaction does not include the necessary condition types that are required for cost transfer.
  Incorrect Configuration: The pricing procedure may not be correctly configured to handle the specific transaction type or scenario.
  Transaction Type Mismatch: The transaction type being processed may not align with the pricing procedure that is currently set up.
  Changes in Configuration: Recent changes in the pricing procedure or condition types may have led to the current configuration being incomplete.
  
  
  Solution:
  
  
  Check Pricing Procedure:
  
  Go to the transaction code V/08 (Maintain Pricing Procedures) and verify the pricing procedure