How To Fix KE373 - Costing variant stored with start of period

SAP Error Message - Details

• Message type: E = Error

• Message class: KE -

• Message number: 373

• Message text: Costing variant stored with start of period

What causes this issue?

In Customizing for Product Costing, costing type &V2& was
assigned to costing variant &V1&. There, the date with which manual
costing is to be saved was set as the start of the period. For this
reason, it is unnecessary to make an entry in field "Costing date".

System Response

Any entry in this field will be deleted by the system when you press
ENTER.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message KE373 - Costing variant stored with start of period ?

  The SAP error message KE373, which states "Costing variant stored with start of period," typically occurs in the context of controlling and cost accounting when there is an issue with the costing variant settings in the system. This error is often related to the configuration of the costing variant and its association with the periods in which costs are being calculated or posted.
  Cause:
  
  Costing Variant Configuration: The costing variant may not be properly configured to allow for the period in which you are trying to perform the costing. This can happen if the costing variant is set to a specific period or if it is not valid for the current period.
  Period Lock: The period you are trying to post to may be locked or closed in the system, preventing any new postings or calculations from being made.
  Incorrect Settings: There may be incorrect settings in the controlling area or the costing variant that do not align with the current fiscal period.
  
  Solution:
  
  
  Check Costing Variant Settings:
  
  Go to the configuration of the costing variant in SAP (Transaction code OKKN).
  Ensure that the costing variant is set up correctly and is valid for the current period.
  Verify that the "Start of Period" setting is appropriate for your needs.
  
  
  
  Open the Period:
  
  If the period is closed, you may need to open it for posting. This can be done in the transaction code OB52, where you can adjust the period settings for the controlling area.
  
  
  
  Review Period Settings:
  
  Check the period settings in the controlling area (Transaction code OKEQ) to ensure that they align with the costing variant and the periods you are trying to work with.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help files related to costing variants and period settings for additional guidance.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above settings, consider reaching out to SAP support for further assistance, as they can provide more specific guidance based on your system configuration.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OKKN (Costing Variants), OB52 (Open/Close Posting Periods), and OKEQ (Controlling Area Settings).
  Costing Variants: Understand the role of costing variants in SAP, which define how costs are calculated and posted in the system.
  Fiscal Year Settings: Review fiscal year settings in your SAP system to ensure they are correctly configured for your business processes.
  
  By addressing the configuration and period settings, you should be able to resolve the KE373 error and proceed with your costing activities in SAP.