How To Fix BK812 - System error: Pricing indicator is unknown

SAP Error Message - Details

• Message type: E = Error

• Message class: BK - Create, Display, Reverse Controlling Document

• Message number: 812

• Message text: System error: Pricing indicator is unknown

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 BK812 - System error: Pricing indicator is unknown ?

  The SAP error message BK812 ("System error: Pricing indicator is unknown") typically occurs in the context of pricing and billing processes within the SAP system. This error indicates that the system encountered an unknown or invalid pricing indicator during a transaction, which prevents it from processing the pricing correctly.
  Causes:
  
  Invalid Pricing Indicator: The pricing indicator used in the transaction does not exist in the system or is not defined correctly.
  Configuration Issues: There may be issues with the configuration of pricing procedures or condition types in the SAP system.
  Master Data Issues: The master data (such as customer or material master records) may have incorrect or missing pricing information.
  Custom Development: If there are custom developments or enhancements in the pricing logic, they may not be handling certain scenarios correctly.
  
  Solutions:
  
  Check Pricing Indicator: Verify the pricing indicator being used in the transaction. Ensure that it is valid and correctly defined in the system.
  Review Configuration: 
  
  Go to the SPRO transaction and check the configuration for pricing procedures and condition types.
  Ensure that the pricing procedure assigned to the relevant sales document type or billing document type is correctly set up.
  
  
  Master Data Verification: 
  
  Check the customer master data and material master data for any inconsistencies or missing pricing information.
  Ensure that the relevant pricing conditions are maintained for the customer and material.
  
  
  Debugging: If the issue persists, consider debugging the transaction to identify where the error is occurring in the pricing logic.
  Consult Documentation: Review SAP documentation or notes related to pricing procedures and indicators for any known issues or updates.
  Contact SAP Support: If you are unable to resolve the issue, consider reaching out to SAP support for assistance, especially if this is a production environment.
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like VK11 (Create Condition), VK12 (Change Condition), and VK13 (Display Condition) to manage pricing conditions.
  Pricing Procedure: Familiarize yourself with the pricing procedure configuration in the SAP system, as it plays a crucial role in how pricing is determined.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  By following these steps, you should be able to identify the root cause of the BK812 error and implement a solution to resolve it.