Comments
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
Dear Mircrosoft Adminstrator!
How can something like that be "currently this is not in our roadmap"?
In order to be business conform it is important to have the proper list code filled automatically.
This cannot be done manually if you have lots of intercompany transactions every day.
For me this is a bug and not an idea.
Thank you very much!
We do need the "Post in batch" function in Fixed Asse Journals. It's a bit silly when users are prompted to post in batch, but the option is not being made available. Instead, we have to use the "Post journals' function, which itself has a defect where you must use the "Select" query instead of ticking (selecting) the lines that you wanted to post as the system will ignore your selection here and post all the journals listed instead
There should be no need for a vote for this as this should have been made available when feature is turned-on by default