Tamer Fawzy Mohamed Support Engineer

When accessing and exiting a work order project journal in asset management, the system automatically creates an empty expense journal for the related work order despite no adjustments being made to the project journal. The expense journal can only be deleted manually.

Idea: The system should create the expense journal for the related work order only after an adjustment is being made to the project journal.

When a packing slip is posted for a non-stocked service item on a sales order line where "Prevent partial delivery" is enabled, you cannot subsequently reverse the posted packing slip quantity. Because the posted quantity is locked by "Prevent partial delivery, users are unable to make corrections or reverse quantities. However, some business scenarios require packing slips to be reversed. The only workaround is to disable the "Prevent partial delivery" parameter, which is not a feasible option considering business requirements. Hence, there should be an acceptable way to reverse the packing slip quantity, while also having the "Prevent partial delivery" enabled.

When creating a purchase order for a specific warehouse and then attempting to create an item arrival journal for a different warehouse, the system currently blocks this action due to insufficient transactions with the status ordered/registered on both the UI and the warehouse mobile app. It would be beneficial to have a feature that allows for changing the inbound warehouse, as shipping containers may need to be rerouted to different warehouses based on various business factors.

When we configure purchase requisition permissions to allow a user to prepare a purchase requisition on behalf of another user, the system permits the preparer to edit and adjust the PR, and the authorization is passed. However, these authorizations are not considered when using standard data entities like Purchase requisition header and lines and Purchase requisition V2. If the user attempts to edit from the data entity, an error is encountered: 'Write failed for table row of type 'PurchaseRequisitionLineV2Entity'. Infolog: Warning: Current user is not authorized to request on behalf of requester with personnel number XX; Error: validateWrite failed on data source 'PurchReqLine'.'

This error occurs despite the purchase requisition permissions being configured. The expected behavior is that the user should be able to edit the PR as they are authorized and have already done so through the UI.

If the setup for Landed Cost Tracking Control Center has been done in the language EN-US, a user with a different language cannot update the tracking control center due to the following error: "The Start date field does not exist."

It would be beneficial to ensure that the Landed Cost Tracking Control Center is fully compatible with multiple language settings. This would help users avoid errors related to language-specific configurations.

When activating a new standard cost for items in d365, the system posts adjustments that split the inventory transactions into separate line with varying quantities for the corresponding items and results in created date and time alteration.

As a consequence, the system modifies the original "created date and time" of the inventory transactions. This alteration can disrupt item traceability for customers who rely on the original creation timestamp for traceability and compliance purposes.

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.