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

SAP Error Message - Details

• Message type: E = Error

• Message class: KE -

• Message number: 378

• Message text: Costing variant stored with start of period

What causes this issue?

In Customizing for Product Costing, costing type &V2& is
assigned to costing variant &V1&. There, the costing type was set to be
saved with the start of the period for automatic costing. It is,
therefore, not necessary to make an entry in field "Costing date".

System Response

Any entries in this field will be deleted by the system after 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 KE378 - Costing variant stored with start of period ?

  The SAP error message KE378 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 the settings may not be appropriate for the current scenario.
  Data Locking: There may be data locking issues if the period is already closed for posting or if there are other transactions that prevent the costing from being executed.
  
  Solution:
  
  
  Check Costing Variant Configuration:
  
  Go to the configuration settings for the costing variant in transaction code OKKN (Costing Variants).
  Verify the settings for the start of the period and ensure they are correct and align with the current fiscal year and period.
  
  
  
  Adjust Period Settings:
  
  If the start of the period is incorrect, you may need to adjust it to match the current period or the period you intend to work with.
  Ensure that the fiscal year variant and periods are correctly defined in the controlling area.
  
  
  
  Review Period Status:
  
  Check the status of the fiscal periods in transaction code OB52 (Open and Close Posting Periods) to ensure that the period you are trying to use is open for posting.
  If the period is closed, you may need to open it temporarily to perform the costing run.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help resources for specific details on the costing variant and its configuration.
  
  
  
  Testing:
  
  After making changes, perform a test costing run to ensure that the error is resolved.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  OKKN: Costing Variants Configuration
  OB52: Open and Close Posting Periods
  CK11N: Create Cost Estimate with Quantity Structure
  CK40N: Execute Costing Run
  
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
  
  
  User Roles: Ensure that you have the necessary authorizations to make changes to the costing variant and period settings.
  
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in controlling and product costing.