How To Fix BP035 - Unit costing not possible at period level.

SAP Error Message - Details

• Message type: E = Error

• Message class: BP - Budgeting and planning

• Message number: 035

• Message text: Unit costing not possible at period level.

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 BP035 - Unit costing not possible at period level. ?

  The SAP error message BP035 ("Unit costing not possible at period level") typically occurs in the context of product costing and inventory management. This error indicates that the system is unable to perform unit costing calculations at the specified period level for a particular material or product. Here are some common causes, solutions, and related information for this error:
  Causes:
  
  Missing Costing Data: The material may not have the necessary costing data maintained in the system, such as standard costs or planned costs.
  Costing Variant Issues: The costing variant used may not be configured correctly or may not be applicable for the period in question.
  Period Locking: The period for which you are trying to perform unit costing may be locked for posting, preventing any changes or calculations.
  Costing Run Not Executed: The costing run for the relevant period may not have been executed, meaning that the system does not have the updated cost information.
  Incorrect Valuation Class: The valuation class assigned to the material may not be set up correctly, leading to issues in cost calculation.
  
  Solutions:
  
  Check Costing Data: Ensure that the necessary costing data (standard costs, planned costs) is maintained for the material in question. You can do this by checking the material master record.
  Review Costing Variant: Verify that the costing variant being used is correctly configured and applicable for the period you are working with. You can check this in the configuration settings for costing variants.
  Unlock Period: If the period is locked, you may need to unlock it or perform the costing in an open period. This can be done by the finance team or through the appropriate transaction codes.
  Execute Costing Run: If the costing run has not been executed, you will need to run it for the relevant period. This can typically be done using transaction code CK40N (for costing run).
  Check Valuation Class: Ensure that the valuation class assigned to the material is correct and that it is set up to allow for unit costing.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CK11N (Create Cost Estimate), CK40N (Costing Run), and MM03 (Display Material).
  SAP Notes: Check for any SAP Notes related to this error message, as they may provide specific fixes or updates.
  Documentation: Review SAP documentation on product costing and unit costing to understand the configuration and processes involved.
  Consult with SAP Support: If the issue persists, consider reaching out to SAP support for further assistance, especially if it involves complex configurations or customizations.
  
  By addressing the above causes and implementing the suggested solutions, you should be able to resolve the BP035 error in SAP.