How To Fix /PM0/ALB_FND_MSG073 - Price &1 price category &2 does not have all calculated prices

SAP Error Message - Details

• Message type: E = Error

• Message class: /PM0/ALB_FND_MSG -

• Message number: 073

• Message text: Price &1 price category &2 does not have all calculated prices

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 /PM0/ALB_FND_MSG073 - Price &1 price category &2 does not have all calculated prices ?

  The SAP error message /PM0/ALB_FND_MSG073 indicates that there is an issue with the pricing configuration for a specific price category in the system. This error typically arises when the system expects certain calculated prices to be available for a given price category, but they are missing or not properly configured.
  Cause:
  
  Missing Price Calculations: The price category specified in the error message does not have all the required calculated prices defined in the system.
  Configuration Issues: There may be a misconfiguration in the pricing procedure or the price determination process.
  Data Inconsistencies: There could be inconsistencies in the master data or transactional data that lead to the absence of expected prices.
  Custom Logic: If there are custom enhancements or modifications in the pricing logic, they might not be functioning as intended.
  
  Solution:
  
  
  Check Price Configuration:
  
  Go to the pricing configuration settings in SAP (Transaction code: SPRO).
  Navigate to the relevant pricing procedure and ensure that all necessary price calculations are defined for the specified price category.
  
  
  
  Review Master Data:
  
  Check the master data for the material or service related to the price category. Ensure that all relevant pricing information is correctly maintained.
  Verify that the condition records for the price category are created and active.
  
  
  
  Analyze Pricing Procedure:
  
  Review the pricing procedure assigned to the relevant sales document or purchasing document. Ensure that it includes all necessary condition types and calculations.
  
  
  
  Check for Custom Enhancements:
  
  If there are any custom developments or enhancements related to pricing, review them to ensure they are functioning correctly and not causing the issue.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to pricing issues for additional guidance and troubleshooting steps.
  
  
  
  Testing:
  
  After making any changes, perform tests to ensure that the issue is resolved and that the expected prices are now being calculated correctly.
  
  
  
  Related Information:
  
  
  Transaction Codes: 
  
  SPRO (Customizing)
  VK11 (Create Condition)
  VK12 (Change Condition)
  VK13 (Display Condition)
  
  
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional insights.
  
  
  Support: If the issue persists after checking the above points, consider reaching out to SAP support or your internal SAP team for further assistance.
  
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.