How To Fix SLS_LO_OIF205 - Pricing type &1 (&2) might not be available (BAdI BADI_SLS_LO_OIF_COND)

SLS_LO_OIF205 - Overview

• Message type: E = Error

• Message class: SLS_LO_OIF - Messages for FPM LORD UI

• Message number: 205

• Message text: Pricing type &1 (&2) might not be available (BAdI BADI_SLS_LO_OIF_COND)

What causes this issue?

The following four pricing types are set up as the standard types within
the UI:
Pricing Type ID,,Pricing Type
B,,Carry out new pricing
C,,Copy manual pricing elements and redetermine the others
G,,Copy pricing elements unchanged and redetermine taxes
I,,Redetermine rebate conditions
You configured an additional pricing type &V1& (&V2&) in your toolbar
layout, however. This pricing type is only visible in your application
UI if you have implemented the BADI_SLS_LO_OIF_COND BAdI
(ES_BADI_SLS_LO_O
See the BAdI documentation for details.

System Response

The system issues a warning to draw your attention to this.

How to fix this error?

Check the above BAdI and align its implementation so that it matches
your current toolbar configuration.

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.

&HINTS&
One of the parameters this BAdI provides is CALLER_ID. If you use this
parameter, the visible set of pricing types may be different (depending
on the CALLER_ID with which you actually run the application).
Because the CALLER_ID parameter is not present when the system is
configured, all possible pricing types are provided here.

Error message extract from SAP system. Copyright SAP SE.

SLS_LO_OIF205 - Details

• The SAP error message SLS_LO_OIF205 indicates that a specific pricing type might not be available in the context of a sales order or pricing condition. This error is related to the Business Add-In (BAdI) BADI_SLS_LO_OIF_COND, which is used for enhancing the pricing logic in the SAP system.
  
  Cause:
  The error typically arises due to one of the following reasons:
  
  
  Missing Configuration: The pricing type specified in the error message is not configured correctly in the system. This could be due to missing entries in the pricing procedure or condition records.
  
  
  BAdI Implementation: The BAdI BADI_SLS_LO_OIF_COND may not be implemented correctly or may not be activated. If the BAdI is not implemented, the system may not be able to determine the appropriate pricing type.
  
  
  Data Inconsistencies: There may be inconsistencies in the master data or transaction data that prevent the system from finding the correct pricing type.
  
  
  Authorization Issues: Sometimes, authorization issues can prevent the system from