0
Category:
STATUS DETAILS

Comments

Tick tock - still waiting - this would be a huge solution - thanks!

Category:

We need this Field Please

Category:

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.

Category:

This is an absolute must. Approval by senior management needs more efficiency in processing. Having to go through countless journals and approve each and everyone instead of only one creates a lot of waist in regards to time spent on this task.

Category:

<

<


>

>

Category:

"al.FindEventName": "al.FindEventName": "\"%ObjectName%_%EventName%\""

Category:

Awesome! This site stripped everything important from this suggestion, so now I will use this reply as a sandbox. Lesson learned, don't trust Microsoft Ideas to work.


"al.FindEventName": "al.FindEventName": "\"\_\\""

Category:

We have this same requirement and will need to do some development for it soon to make the receiving process more efficient for our users.

Category:

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

Category:

Missed to add that the Form notes group field should also be added to the Customer/Vendor group to be able set a default value.

Category:

  • 1
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 500