Comments
We have the same issue here, as the banks may calculate the 1st period interest only for the remaining days of the month, when the contracts start from the middle of the month.
It is hard to find a walkaround for this. Appreciate if someone can also share some ideas on how to handle this discrepancy.
Our requirement is a little simpler in that we only need Master Planning to consider inventory storage capacity. In particular, our production warehouses have very limited space and must be cleared daily of completed production orders. In addition the available space for material is limited, so we need the production facilities to be limited by how much material we can hold at any one time.
Value proposition:
This change would improve the functionality of pricing management by making them compatible with price units other than 1. This is particularly important for:
Managing decimals beyond two digits: Allows for greater precision in pricing, especially for low-value items.
Alignment with existing practices: Maintains consistency with existing functionalities used in Supply Chain Management (SCM) pricing.
Current limitation:
Enabling "Pricing management features" in Sales Trade Agreements currently disables the ability to use a price unit != 1. This leads to:
Loss of functionality: Users can no longer manage decimals beyond two digits.
Potential regression: May deter customers from adopting new pricing features due to limitations.
Technical feasibility:
Since the price engine already accommodates calculations with more than two decimals (for discounts etc.), extending this capability to pricing management should be technically feasible