Current Behavior: 

When setting up a recurring batch job for item price calculations, the Calculation date is stored as a static value from the time the batch job is created. For each subsequent execution of the recurring batch job, the system continues to use the original calculation date rather than the current execution date. The Calculation date field does not support dynamic values such as system date, execution date, or relative date expressions. 

Issue: 

This behavior causes recurring price calculations to be performed using an outdated calculation date. As costs, cost versions, exchange rates, and other pricing-related data may change over time, the calculated item prices can become inaccurate when based on a historical date. The only available workaround is to manually update or recreate the batch job with a new calculation date, which reduces the value of automation and increases the risk of user error. 

Business Impact: 

Incorrect item cost and price calculations. Increased manual maintenance of recurring batch jobs. Higher risk of operational errors due to forgotten updates. Reduced trust in automated costing and pricing processes. 

Suggested options: 

System date (Today) – Uses the date when the batch job executes. Batch execution date – Automatically populated at runtime. Ability to select whether the calculation date should remain fixed or be dynamically evaluated during execution. 

This enhancement would: 

Improve the accuracy of automated item price calculations. Reduce manual maintenance. Eliminate the need to recreate recurring batch jobs. Increase reliability and usability of batch automation within Cost Management.