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

KE371 - Overview

• Message type: E = Error

• Message class: KE -

• Message number: 371

• 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 costing date with which
manual costing is to be saved is set as the start of the period.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

For this reason, you must enter the relevant period in field
'Period/year' with which the system is to read the product cost
estimate.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

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

  The SAP error message KE371 indicates that a costing variant is stored with a start of period that is not compatible with the current settings or data in the system. This error typically arises in the context of controlling (CO) and product costing, particularly when trying to execute a costing run or when accessing cost estimates.
  
  Cause:
  
  Inconsistent Period Settings: The costing variant may have been configured with a start of period that does not align with the current fiscal period or the periods defined in the controlling area.
  Costing Variant Configuration: The costing variant might be set up incorrectly, or it may not be valid for the current period.
  Data Locking: There may be data locking issues or inconsistencies in the master data that prevent the costing variant from being used.
  
  
  Solution:
  
  
  Check Costing Variant Configuration:
  
  Go to the configuration settings for the costing variant in SAP (Transaction code OKKN).
  Verify the start of period settings and