Elise De Brie

Current Limitation:

In D365FO, the only way to control automatic cycle count approval is through parameters set at the worker level. This approach is too broad and fails to account for the varying financial impact of discrepancies across different products. High-value items, for example, should be handled with much greater scrutiny than low-value items.

Proposed Enhancement:

Add functionality to set cycle count approval parameters at the released product or product variant level. This would allow businesses to define specific thresholds for automatic approval based on both quantity and value deviations tailored to each item.

Why This Matters:

• Critical Risk Management: High-value items should not be automatically approved if even minor discrepancies occur. Allowing item-level control ensures that these items are flagged for manual review, reducing financial risk.
• Operational Efficiency: For low-value items, automatic approval of minor deviations can streamline operations, freeing up resources to focus on more critical areas.
• Flexibility and Precision: Businesses can fine-tune their cycle count processes, aligning them more closely with the financial significance of their inventory, leading to more accurate and reliable inventory management.

Call to Action:

Implementing this feature would greatly enhance the control and efficiency of inventory management in D365FO, making it a valuable addition for all users. By allowing item-specific parameters, we can better manage risks, optimize resources, and improve overall accuracy in the cycle count process.

Current Limitation:

In D365FO, when creating a Sales Return Order, there is no functionality to print a receipts list like there is for standard Sales Orders. This gap presents challenges for warehouse workers who need to know exactly what goods are returning and when, especially if they do not have access to the D365FO client. Without this list, there is limited visibility into the expected returns, which can lead to inefficiencies in the return process.

Proposed Enhancement:

Add a standard SSRS report for Sales Return Orders that generates a receipts list similar to the one available for standard Sales Orders. This report should be configurable in Print Management to allow for printing when a return order is created. This would provide warehouse workers and other personnel with a clear, standardized document to identify and process incoming goods.

Why This Matters:

• Improved Visibility: By having a receipts list for Sales Return Orders, warehouse workers can anticipate incoming items and ensure they are prepared for the returns, improving operational efficiency.
• Enhanced Process Efficiency: With the report being included in Print Management, the warehouse team can operate more independently, reducing the need for access to the D365FO client and enabling faster return processing.
• Consistency in Documentation: A standardized receipts list for both Sales Orders and Sales Return Orders will ensure consistency in how incoming and outgoing goods are managed, reducing the risk of confusion or errors.

Call to Action:

Implementing this feature would provide much-needed visibility into Sales Return Orders, enhancing operational workflows, reducing delays, and supporting accurate goods identification. This functionality would be a valuable addition for any organization managing returns, improving warehouse efficiency and overall return order management.

Description:

Currently, in Dynamics 365 Finance and Operations, there is no way to enforce license plate or location confirmation during the pick step for stock movement work. This creates a risk of accidental confirmations, especially in workflows involving license plates with multiple items.

Process Description:

1. Stock movement work is created using a movement by template menu item, with 'create movement' set to "yes."
2. When executing this created movement work for a license plate containing multiple items, the items are grouped and displayed as 'multiple' on the mobile device.
3. Using a system-directed menu item to execute this work, the system skips the entire work confirmation process at the pick step. Instead, the user is immediately prompted to 'check the values and confirm,' making it easy to accidentally confirm the pick without validating or executing the work properly.

Proposed Solution:

Add an option to enforce work confirmation on the pick step during stock movement work. This could include:

• License Plate Confirmation: Require scanning or entering the license plate before confirming the pick.
• Location Confirmation: Require validation of the source location during the pick step.

Business Impact:

• Improved Accuracy: Ensures correct items are picked, reducing errors.
• Operational Control: Prevents accidental confirmations by requiring explicit validation during the pick step.
• Flexibility: Aligns system functionality with real-world warehouse workflows, particularly for scenarios involving complex license plates or items grouped under 'multiple.'

Conclusion:

By enabling work confirmation on the pick step, this enhancement will improve the accuracy and reliability of stock movement workflows, meeting the needs of businesses that require stricter validation processes during warehouse operations.

Description:

Currently, in Dynamics 365 Finance and Operations, it is not possible to seamlessly consolidate containers packed at different packing stations into a single container without encountering issues. This limitation affects scenarios where businesses need to combine items from multiple containers into one for efficiency in shipping or handling.

Scenario:

• Two containers (e.g., Container A and Container B) are packed at separate packing stations (e.g., pallets and small goods).
• The goal is to consolidate these containers into a single container (e.g., Container A) using standard warehouse processes.
• After the consolidation, the system should recognize all items from the original containers and generate accurate packed container picking work.

Current Limitation:

• When containers are consolidated, the resulting container does not retain all items from the merged containers.
• Packed container picking work generated for the consolidated container often includes only partial items or results in errors during execution.
• This limits the usability of consolidation workflows and creates inefficiencies in handling outbound shipments.

Proposed Solution:

Introduce functionality to support the consolidation of containers packed at different packing stations, ensuring:

1. All items from the original containers are accurately transferred to the consolidated container.
2. Packed container picking work is generated correctly for the new consolidated container.
3. Smooth execution of picking and put-away steps without errors.

Benefits:

• Operational Efficiency: Reduces the need for manual intervention and rework.
• Flexibility: Supports real-world workflows where goods from multiple packing stations need to be combined.
• Accuracy: Ensures that all items are accounted for in the consolidated container, minimizing errors in subsequent processes.

Business Case:

This enhancement is critical for warehouses that frequently consolidate containers to optimize space and streamline shipping processes. It aligns system functionality with practical operational needs, improving overall workflow efficiency and accuracy.

Conclusion:

By enabling the seamless consolidation of containers from different packing stations, D365FO will better support complex warehouse operations, reducing errors and improving user satisfaction.