When broker contract is set up with an amount type of "Quantity", the system does not convert units of measure correctly when sales lines are entered in a different unit. As a result, broker commission fees on sales orders are calculated based solely on the entered quantity, without validating the unit of measure. This leads to incorrect commission charges being applied, even when they should not.

When work order life cycle status is linked to a project status User defined 1,2 or 3 the project status is shown as User defined 1, 2 and 3 in the work order lines. Project statuses 'User defined' can be named with a user friendly status name, that is used in the project management and accounting module when operating the project. The same user friendly naming of the project status should be shown in the work order maintenance job instead of the system name User defined 1, 2 and 3.

When reporting progress in Production floor execution, the job card is created successfully, but the system defaults to using the resource cost rate instead of the actual worker-specific cost rate, leading to discrepancies in cost accounting.

Business scenario: multiple workers using the same resource will have the same cost rate within current design despite having different cost category set up

Expectation: system derive the actual cost from the worker, not from the resource. 

Enable the use of Service Level Agreements (SLAs) when the case category type is set to 'Collections'. This is a common business requirement, as organizations want to ensure collections cases are resolved in a timely manner and have visibility into any delays through SLA tracking.

Ref: LCS issue 425837

The system currently does not allow the creation of a Discount Trade agreement based on Line Discount Group unless the desired Line Discount Group is already assigned to at least one customer.

The Price Engine, also, does not consider the Line Discount Group specified on the Sales Order, and instead defaults to the one assigned to the customer master record, limiting flexibility for exceptional cases (e.g. large sales, agreement for the specific order, etc), generating inconsistency with the D365 logic.

The system should:

• allow the creation of Discount Trade Agreement even if the Line Discount Group is not assigned to a customer
• restore consistency with the standard logic and consider the Line Discount Group at Sales Order level

Copy vendors by using shared number sequences doesn't work as expected.

-when I try to release existing vendor to another legal entity, I get wrong number from sequence

-we have tried following mitigation in bugs 825366,287278

• -Setup shared number series for vendor accounts
• Goto the Legal entity where the new vendor account is to be created
• Click New 
• use the dropdown in the name field to find the vendor in the other company
• notice the "Existing Vendor. Copy vendor ?" toggle bar set to YES
• Select company
• Now the vendors are created with same account number 
• 
  

The address is not copied while using that way.

Appreciate if we can get the address copied, or enhancing the functionality itself to do what is required from it.

When registering Sales order there is used Item list with high number of items.

For some products if there were changed Min qty and/ or Multiply qty in Default order settings there are presented info messages like bellow:

1.You have specified a quantity of 1.00. The minimum allowed quantity is 20.00.Do you want to use 20.00 instead?

2.The order quantity must be a multiple of 12.00. Do you want to round up the order quantity to 24.00?

There is missing info about ItemId

Request:

Please add affected ItemId as a parameter presented in both info messages.

It will help to identify which items are affected.

When entering data into journal lines like RAF, Picking, Transfer, etc.; the Warehouse, Location, and Batch columns have a range dimensions option, which narrows the search based on parameters entered elsewhere on the line.

I believe it would make these entries even more efficient if this same function was added to the license plate column. If you have a batch number and/or location entered on the line, the range dimensions option makes it really easy to select your license plate without having to find it, and copy and paste it from the on-hand list.

The value (Amount) and the Amount field on the product receipt journal display the same exact value in the accounting currency, although the help text of the amount field indicates that this should be displayed in the transactional currency (which is not correct). The value of the amount field should be changed so it's displayed in the transactional currency . Currently there is no notion of the received amount in the transactional currency on the product receipt journal.

Description:

When changing the “requested ship date” on individual sales order lines, no prompt appears in the system to warn or confirm that these changes may affect item pricing. Currently, the “Update ship and receipt date” functionality only triggers at the header level of the sales order. This behavior can be especially impractical for businesses managing large orders with extensive line items, where each line may need different ship and receipt dates.

This has been addressed by the product group team in issue number 1035364 that the system functioning as intended and raise an idea to track the progress.

Proposed Idea:

Enhance the existing functionality so that whenever a “requested ship date” is altered at the line level, a prompt (or similar user confirmation mechanism) is displayed. This prompt would alert the user that pricing or other relevant calculations may be impacted by the change, allowing them to confirm or revise before finalizing. This improvement would help ensure consistency, reduce errors, and streamline the user experience for organizations working with complex or large sales orders.