Yasmine Hesham Hassan Zaki (Convergys International Europe B V)

When a Purchase order is pegged to a production order and has already been confirmed (meaning the vendor has acknowledged and agreed to the terms), rescheduling the related production order—either through job or operation scheduling—unexpectedly changes the PO status from Confirmed back to Approved. This is problematic because it disrupts the procurement process and can cause misalignment with vendors.

Summary:

• The vendor is not notified of the change.
• The purchaser is not automatically informed.
• Action messages (which should prompt the purchaser to review changes) are bypassed.
• The process complicates EDI, version control, and does not align with vendor expectations.

Expected Result

• Confirmed POs should remain confirmed unless the purchaser explicitly decides otherwise.
• Scheduling actions (job or operation) should not alter the status of confirmed POs.
• Purchasers should rely on action messages to decide if vendor communication is needed.

1. Improved Order Visibility

Having the header reflect the earliest or latest delivery date gives users a single point of reference. They no longer need to check each line individually, which makes it easier for customer service teams to provide accurate delivery commitments at the order level.

2. Better Planning and Coordination

This feature would help logistics teams decide whether to consolidate shipments or split deliveries. It also makes it easier for production and procurement teams to prioritize work based on the earliest or latest required date.

3. Less Manual Work

Right now, users often have to review every line and calculate the earliest or latest date themselves. Automating this process saves time and reduces the risk of errors.

4. Improved Customer Experience

Customers would receive clearer, more reliable delivery dates for their orders. This reduces confusion around partial deliveries and helps avoid disputes.

5. Alignment with Business Practices

Many companies promise delivery based on either the earliest possible date (ship as soon as possible) or the latest date (ship complete). Reflecting this at the header level supports these common strategies.

6. Foundation for Future Enhancements

Once in place, this functionality could enable automated alerts when header dates change, integration with EDI or customer portals for accurate order status, and better reporting on KPIs like OTIF (On Time In Full).

The query responsible for calculating the summation is only triggered when the user changes the view, and not when simply opening the form, regardless of which view is set as default.

In reference to fix request ID "1044123", users expect the system to stop generating Planned POs once the full requested quantity has been delivered and received across POs, even if the delivery was split across multiple lines.

Additionally, the replenishment request needs to remain linked to all related POs and stop triggering further planning once completed.

Incorrect Item number is reflected on Released product details after the creation of Production order/ SO/ Planned order after enabling the following features "Display product info in user's language" and "User specific product name and description" and activating Product information management parameters "Show specified language" and "Show user language" and defaulting a personalized View after adding new filed in the General fast tab in the Item card ex. “Created by” and “Created date and time”.

The feature could help streamline compliance, reduce manual workload, improve customer experience, and strengthen data integrity—all of which are critical for companies involved in international trade and subject to US customs regulations.

When users apply filters or personalized sorting on Accounts receivable > Orders > All sales orders, clicking New to create a sales order resets the list page context. Upon returning, all filters, sorting, and personalizations are lost, forcing users to reapply them or refresh the page. This behavior also causes the SalesTable datasource query to re‑execute, leading to noticeable form load delays. In high‑volume environments processing up to 8,000 sales orders per day, this results in significant productivity loss, increased form opening times, and user frustration, especially for customer service and order management teams who rely on filtered views to work efficiently. There is currently no workaround, and preserving the list page state would materially improve usability, system performance, and overall operational efficiency.

In Dynamics 365 Supply Chain Management, the same production job displays different start and end times between Production orders (All jobs / Production route) and the Production floor execution (PFE) interface, even when legal entity, site, and user time zones are configured identically. This discrepancy—often one hour due to daylight saving time and user time zone conversion—creates confusion for shop floor operators, supervisors, and planners, as workers see job start times in PFE that do not match the planned schedule. As a result, jobs may be started earlier or later than intended, disrupting execution sequencing, shift handovers, and schedule adherence. The inconsistency reduces user trust in the system, increases training and support effort to explain the behavior, and introduces a real risk of operational errors in manufacturing execution, especially in DST-enabled regions.