• 1

    Resolve the Discrepancy between the Totals function in Sales Order vs Purchase Order (D365F&O - SCM)

    Suggested by Stuart Hayes New  0 Comments

    In SCM, the totals function on a Purchase Order shows the value of the order irrespective of purchase order status. This can be extremely useful for Procurement teams to review purchase orders.


    The totals function for Sales Orders however reduces in value as the order is invoiced, meaning a fully invoiced order shows zero. The logic from AX was that this enabled visibility of remaining value to invoice, and users could use the Invoice Total function within the AR Invoice Journal option.


    With segregation of duties, it is common for sales order processing teams to not be allowed access to the Invoice Journal option, meaning they have no easy way of confirming total sales order value for any Invoiced order. This can cause challenges with customers, particularly those who repeat order. Without manually adding up the lines, there is no way to see total net, vat, discount given.


    Idea:

    1) Bring the Totals function for Sales Orders into line with that of Purchase Orders, whereby the Total figure does not run down as the order gets invoiced.

    2) Add new fields to the Totals section (Uninvoiced Net, Uninvoiced Tax, Uninvoiced Discount, Uninvoiced Gross) for those customers who use the Totals function for this purpose.




  • 2

    Allow "Mixed Scope" Picking or Sales Orders

    Suggested by Braiden Slavens New  1 Comments

    "Mixed" scope picking is not currently supported for Sales Order picking. This leaves a major gap for any companies that assemble large scope projects to order or order multiple items for a project from a vendor to be cross docked and shipped to the end user.


    Idea is to enable the same "mixed scope" picking process that is currently available for Purchase Orders for Sales Order picking. This will allow businesses to create a single pick line for multiple items that are contained on a single license plate for a single order. There is no need to pick the items individually as the items and quantities have already been validated and the entire LP can be picked to the order.




  • 1

    New Option in “Save Job to History” for Batch Jobs : “Last run and errors”

    Suggested by Carl Johan Bergman New  0 Comments

    We would like to request a new option under the Batch job history settings.


    Suggested Option:Ā 

    ā€œLast run and errorsā€

    Ā 

    This new option should:

    • Always save the last run of the batch job to the history
    • Also include any errors, just like the ā€œErrors onlyā€ setting


    Why This Is Needed

    Today, if we use the setting ā€œErrors onlyā€, we have no visibility if the job ran successfully — we’re completely blind unless there is an error.

    Ā 

    This new option would help us:

    • Confirm that the job ran
    • Review the last execution, even if there were no errors


    Requested Action

    Please add a new setting: ā€œLast run and errorsā€

    This will improve traceability and monitoring of batch jobs.


  • 21

    Proposal to Change Validation During Entity Import for "Costing Sheet Node Calculation Factors V2" to Reduce Manual Work

    Suggested by Moustafa Sabea New  0 Comments

    A critical issue when importing new costing sheet nodes using the "Costing sheet nodes and absorption basis" entity.


    The problem arises when parts of the costing sheet fail during import, whereas importing the full costing sheet results in the deletion of all existing costing sheets, including rates.


    Additionally, using the "Costing Sheet Node Calculation Factors V2" entity causes rates to be in a pending state, leading to the deletion of old rates, which disrupts report accuracy.


    This issue has been acknowledged by the product team and is noted as "By design" in the official documentation.


    Specifically, when importing the cost sheet node entity, the existing cost sheet is entirely deleted before the new costing sheet is saved.


    To address this, we propose changing the validation process during entity import to allow partial imports without deleting existing data. This change is crucial for maintaining data integrity and ensuring accurate financial reporting.


    Moreover, if new indirect costs or rates need to be imported, the current issue necessitates significant manual work, further complicating the process.


    It will be great to reconsider this design and implement a solution that preserves existing costing sheets and rates during the import process.


    For more details, refer to the issue highlighted by the product team:Ā https://fix.lcs.dynamics.com/Issue/Details?bugId=606746


  • 8

    Audit template ID must be available on Receive Mobile device menu items

    Suggested by Evan Aaby New  1 Comments

    It must be possible to select Audit template ID on Mobile Device menu items where Work creation process is:


    1. Purchase order receive
    2. Purchase order line receive
    3. Transfer order receive
    4. Transfer order line receive.
    5. License plate receiving


    As is today, it is only possible to select Audit template ID in connection with Putaway.


  • 6

    Possibibility to Insert columns in address dropdown or change default columns

    Suggested by Rikard Wekelius New  0 Comments

    Currently, it is not possible to insert columns in the address dropdown when selecting an address, for example during the creation of a sales order.


    The only workaround is to click "Other addresses", search for the customer, and then insert columns in that view. However, this process is inefficient, particularly for customers with many accounts, as it introduces unnecessary load times and increases the risk of selecting the wrong customer account.


    This functionality is especially important when customers have multiple addresses that appear identical, with the only difference being, for example, a building complement. In the standard dropdown, these nuances are not visible, making it impossible to distinguish between addresse. Also adjusting the address format doesn't have an affect of the displayed columns in address dropdown.


    This limitation applies not only to sales orders, but also to sales quotations, sales agreements, and other areas where address selection occurs. Interestingly in some parts of the system such as the address selection view on the customer account it is possible to insert columns, which suggests that the capability already exists but not accross all areas. Therefore, I propose adding support for inserting columns in all address dropdowns across the application to improve clarity, accuracy, and user efficiency. Users should also have the ability to save the column setup as a default view to avoid reconfiguring it each time.

    If inserting columns is not feasible, then at a minimum, the default columns shown in the address dropdown should be configurable.


  • 20

    Ability to hide the "Remaining Quantity to Pack" on the RF Device

    Suggested by Abdo Khoury New  0 Comments

    when using the PACK INVENTORY INTO CONTAINER , we would like to have the Ability to hide the "Remaining Quantity to Pack" on the RF DeviceĀ in order to change this to a blind pack. this would help us to ensure that quality is being done.


  • 3

    Error message presented when we use Stop and unpick for Production order: Cannot edit a record in Prod BOM Pool (WHSProdBOMPool). The record has never been selected.

    Suggested by Soumen Saha New  0 Comments

    There is presented error message as below when we use Stop and unpick for Production order:

    Cannot edit a record in Prod BOM Pool (WHSProdBOMPool). The record has never been selected.

    This issue happens when we use as components some products which are Warehouse management controlled and some not. We do not want the error message to be present.


  • 1

    Enable adding customer return orders/RMA to inbound load

    Suggested by Arnaud Moulard New  0 Comments

    It would be great to be able to add Customer returns/RMAs to inbound loads in order to better plan/sequence transportation.

    With RMA not being part of the TMS, it makes it more complex to organize collecting customer returns or sequence inbound/outbound loads.


    Inbound loads for RMAs would provide better visibility to the transportation team.





  • 18

    Issue with "Empty Location with No Incoming Work" Strategy for Wave Demand Replenishment

    Suggested by Moustafa Sabea New  0 Comments

    When creating work for replenishment, the put-away location is the same for two items, resulting in one pick/put work per item. This issue arises when creating multiple replenishments of the same items where the demand isn't for full pallets. Adjusting location stocking limits and changing the quantity per LP doesn't resolve the issue.


    The strategy "Empty location with no incoming work" is not evaluated as part of the replenishment work creation. Consequently, the second replenishment work with the same put location is created.


    Fix request number: 441273. Microsoft has evaluated this issue and determined it to be a feature limitation. A work item has been added to the product backlog to enhance the capabilities for this functionality.


    Enhancing the replenishment work creation process to evaluate the "Empty location with no incoming work" strategy will improve efficiency and accuracy, benefiting customers by ensuring more reliable replenishment processes.


    LCS: 441273