[Paul Pollock]

Up

0

Down

::

Agreed!

[Paul Pollock]

Up

0

Down

::

From my knowledge, you can cancel remaining quantities on partially invoiced POs or finalize the PO. Finalizing releases any associated budge reservations, which is useful if you’re utilizing budget control for example.

[Paul Pollock]

Up

0

Down

::

Changing a project’s status to “Completed” or “Closed” does not automatically cancel or close associated open Purchase Orders (POs). Project status changes primarily affect project accounting and reporting, but they do not directly impact the status of related POs.

[Paul Pollock]

Up

0

Down

::

When a project is finalized, it’s essential to address any open POs linked to it. Finalizing a project without resolving open POs can lead to discrepancies in financial records and hinder procurement processes.

Best Practices:

1. Close Open Purchase Orders Before Finalizing the Project:

   • Review and Close POs: Ensure all POs related to the project are either fully received, invoiced, or canceled if no longer needed. This practice prevents issues such as budget encumbrances and ensures that financial commitments are accurately reflected.
   • Utilize the Finalize Function (optional): In D365FO, the ‘Finalize’ function on a PO prevents any further changes and releases any remaining budget reservations. This is particularly useful for locking the PO and ensuring no additional modifications are made.

2. Implement Change Management Processes:

   • Enable Change Management: Activating change management for POs ensures that any modifications undergo an approval workflow, maintaining control over procurement activities. This is especially important in project scenarios to manage changes systematically.

3. Regularly Monitor Purchase Order Statuses:

   • Utilize Workspaces: D365FO provides workspaces like ‘Confirmed purchase orders with changes’ to monitor and manage POs effectively. These tools help in identifying and addressing any pending actions on POs, ensuring they are appropriately closed or finalized.

[Paul Pollock]

Up

0

Down

::

Have you reviewed Batch Number Group configuration? This sounds like “Per qty” is setup and maybe you need to investigate using “Only for inventory transactions”. When enabled, a single batch number is generated for the entire inventory transaction, regardless of the quantity. This means that even if you receive items in multiple registrations, they will share the same batch number.

[Paul Pollock]

Up

0

Down

::

I submitted an idea for ‘Enable Reassignment of Clusters in Warehouse Management’ and I would appreciate your vote.

D365 Application Idea: https://experience.dynamics.com/ideas/idea/?ideaid=00f92a61-ba3f-ef11-b4ad-000d3adde37b

I propose a new functionality within Dynamics 365 to streamline this process. The system should allow administrators or managers to:

1. Remove an Employee from an Assigned Cluster: This feature would enable the removal of an employee from a cluster, making it available for reassignment. This ensures the fulfillment process continues smoothly without depending on a single user’s availability.
2. Reassign a Cluster to Another User: This functionality would allow for the direct reassignment of a cluster to another user, enabling the new user to pick up and complete the tasks without any interruptions.

Benefits:

• Improved Operational Efficiency: By allowing clusters to be reassigned seamlessly, the warehouse team can maintain continuous operations and avoid bottlenecks.
• Enhanced Customer Service: Minimizing delays in the fulfillment process leads to better customer satisfaction as orders are processed and delivered on time.
• Greater Flexibility: This feature provides teams with the flexibility to adapt to unexpected changes, such as an employee’s sudden unavailability.

[Paul Pollock]

Up

1

Down

::

This kind of information would be soooo beneficial!!

[Paul Pollock]

Up

0

Down

::

Also manually recreated the workflow in each environment after the import process produced the error message.

[Paul Pollock]

Up

0

Down

::

Yes, all other workflows were deleted and still get the error message.

[Paul Pollock]

Up

0

Down

::

All parts of the workflow were reviewed and confirmed to be configured correctly.

[Paul Pollock]

Up

0

Down

::

Importing the workflow into environment where it was created was also attempted and the workflow and purchase requisition process worked as expected

[Paul Pollock]

Up

0

Down

::

I look forward to seeing your article. We are putting the solution through some test cases as well.

How the Total Quantity on the Current allocation form is calculated was a little confusing as first. It represents the vendor’s total quantity during the current period, but the current period is influenced by the Balance period (days) and if the policy has a Valid from and Valid to input.

“Total Quantity” Example 1:

Balance period: 180 days

Valid from: blank

Valid to: blank

Today’s date: January 30, 2024

The time period would be 180 days back from today, which is August 4, 2023 to January 30, 2024

“Total Quantity” Example 2:

Balance period: 180 days

Valid from: January 1, 2024

Valid to: December 31, 2025

Today’s date: January 30, 2024

The time period would start on January 1, 2024 (valid from date) and extend 180 days back from any given date up to December 31, 2025 (valid to date).

So, for today’s date of January 30, 2024, the time period would be July 4, 2023 to January 30, 2024.