Do you have any question about this error?
Message type: E = Error
Message class: KE -
Message number: 372
Message text: Costing variant stored with start of period
In Customizing for Product Costing, costing type &V2& was assigned to
costing variant &V1&. There, the costing date with which automatic
costing is to be saved is set as the start of the period.
For this reason, you must enter the relevant period in field
'Period/year' with which the system is to read the product cost
estimate.
As costing type &V2& concerns a standard cost estimate, you could,
instead of entering the period yourself, use the plan period flag from
which the system takes the relevant period from the material master.
Error message extract from SAP system. Copyright SAP SE.
KE372
- Costing variant stored with start of period ?The SAP error message KE372 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 year or period settings in the system.
- Costing Variant Configuration: The costing variant might be set up incorrectly, or it may not be valid for the current period.
- Master Data Issues: There could be issues with the master data (e.g., material master, cost center) that are causing the costing variant to be incompatible with the current period.
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 ensure they are correct and align with the current fiscal year and period.
Adjust Period Settings:
- If the costing variant is set to a specific period, consider adjusting it to match the current period or fiscal year.
- Ensure that the period settings in the controlling area are correctly defined.
Review Master Data:
- Check the relevant master data (e.g., material master, cost center) to ensure that they are correctly set up and that there are no inconsistencies that could lead to this error.
Consult Documentation:
- Review SAP documentation or help resources related to costing variants and period settings for additional guidance.
Testing:
- After making adjustments, perform a test run to ensure that the error does not reoccur.
Related Information:
If the issue persists after following these steps, it may be beneficial to consult with an SAP expert or your organization's SAP support team for further assistance.
Get instant SAP help. Start your 7-day free trial now.
KE371
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 costin...
KE370
Costing variant stored with costing date
What causes this issue? In Customizing for Product Costing, costing type &V2& is assigned to costing variant &V1&. There, this costin...
KE373
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 w...
KE374
Period flag may not be used
What causes this issue? In Customizing for CO-PC, costing type &V2& is assigned to costing variant &V1&. This costing type has not be...
Click on this link to search all SAP messages.