Moustafa Sabea

Multiple customers have recently highlighted a critical requirement: the ability to add items, approved via purchase requisitions (PRs), to an existing released purchase order (PO). This need arises due to frequent modifications occurring during the PO process, which currently cannot be accommodated efficiently. 

To address this, I propose a feature enhancement that allows users to modify a released purchase order by adding new items, specifically those that have already been approved through a purchase requisition. This functionality would ensure a streamlined and traceable procurement process, adapting to real-world business dynamics.

Implementing this feature will significantly enhance the efficiency and adaptability of procurement processes. It will empower users to manage their procurement needs more effectively while ensuring proper governance and control over purchased items. This enhancement addresses the pressing requirements of multiple customers, further emphasizing its critical importance.

In a business scenario where a retail company (Company 1) and a manufacturing company (Company 2) are dealing with intercompany orders for chilled items, the confirmation process is causing significant issues.

When Company 1 confirms a sales order (SO) or purchase order (PO), the intercompany sales order in Company 2 remains unconfirmed, disrupting production and leading to potential revenue loss. To address this, an Auto-confirmation Intercompany Order Confirmation System is proposed.

This system will ensure real-time synchronization of order statuses between the two companies, automatically updating the intercompany SO status in Company 2 when the original SO and PO are confirmed in Company 1.

Key features include real-time status updates, integration with existing ERP systems, a notification system, an audit trail, and scalability to handle 300-400 orders daily for the production company.

This solution will improve production planning, reduce revenue loss, enhance communication, and increase efficiency.

Intercompany and Direct Delivery orders are significantly contributing to the growth of customer's database, leading to usage overruns beyond the threshold.

Currently, there is no functionality to archive or clean up these types of orders, which limits customer's ability to manage database size effectively.

To address this, a propose developing a feature that allows for the archiving or clean-up of Intercompany and Direct Delivery orders. This feature should include criteria for archiving orders, such as orders older than a certain date or orders that have been fully processed and closed alongside the Inventory archival and not being allowed for data archival with intercompany chain linked to sales orders.

Additionally, an automated process should be implemented to periodically archive orders based on the defined criteria, along with a manual archiving option for users. It is also essential to ensure that archived orders can be easily retrieved if necessary for auditing or reference purposes.

Furthermore, a clean-up function may be developed to remove unnecessary data from the database, reducing its size and improving performance.

Implementing this archiving and clean-up function will help manage database growth, improve system performance, and ensure compliance with data retention policies.

However, it is important to note that addressing this issue will require additional resources and an increase in system resource requirements.

The impact of this issue is particularly significant for retail operations, where efficient database management is crucial for smooth functioning.

In the current version of the warehouse mobile application, there is a feature limitation related to label printing. Specifically, users are unable to change the current or specific User ID associated with the Reprint Label menu item. 

This restriction can impact the efficiency of warehouse operations, as it prevents the reassignment of damaged labels to different users when necessary. 

For instance, if a label needs to be reassigned due to a change in personnel or task allocation, the inability to update the user ID can lead to confusion and delays. 

This limitation is particularly challenging in dynamic warehouse environments where roles and responsibilities frequently shift. Additionally, if labels become damaged and need to be reprinted, the inability to change the user ID can further complicate the process, causing additional delays and inefficiencies. 

Addressing this limitation would enhance the flexibility and functionality of the application, allowing for smoother and more adaptable warehouse management processes. Implementing a solution to this issue would not only improve operational efficiency but also ensure that the application meets the evolving needs of warehouse staff.

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

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