Dynamics 365 Supply Chain Management

While splitting a purchase order line while registration system acts as expected and creates proper quality orders upon the item sampling set up.

However, when we do the splitting and receipt from item arrival, system does deal with each line we split as a separate entity and creates a quality order for each entry/registration line.

Given the current roles in the system warehouse team doesn't have access to the PO therefore, obligated to receive it from Item arrival. which leads to in correct quality orders generated even through item sampling is set up correctly.

On Loads form, Action pane, there is the Reverse work functionality.

This functionality works fine when there is only one Work Id linked to a Load line.

If more than one Work IDs were created for a Load line (due to work template/business requirements), Reverse work functionality returns the following error:

Cannot reverse work because loads have already been picked for the sales line. Use Reduce picked quantity instead of reversing the entire load.

Use reduce picked quantity line by line in large organizations is not an option as there might be many many lines on a load.

Currently, Planning optimization is not supporting the scenario where we have 3 parallel operations (one primary and 2 secondary), where resource assigned for primary operation has limited capacity associated to it and formula assigned on operation is Capacity while the resources associated to secondary operations have unlimited capacity.

When such situation is found, Planning optimization is generating error like "Capacity could not be found” during scheduling.

Same scenario works under legacy Master planning engine.

Scenario has been raised to Planning product group (under https://fix.lcs.dynamics.com/Issue/Details?bugId=1029575&dbType=3) and it has been deemed as being a gap in the current design of Planning optimization engine.

Below steps can be used to validate the scenario:

1. Navigate to Working time templates. Create new working time template = 1113 and set following time shifts:

Monday: From 06:00 to 24:00

Tuesday to Friday: From 00:00 to 24:00

Saturday: From 00:00 to 06:00 (Closed for pickup = Yes)

Sunday: Closed for pickup = Yes.

2. Navigate to Calendars form. Create new calendar = 1113 and calculate working times based on working time template = 1113.

3. Navigate to Route groups. Create new route group = 1113_std with Setup time = Yes and Run time = Yes under Estimation and costing. Check Activation for all job types, check Job scheduling and Working times for Setup, Process and Transport job types and check Capacity for Setup and Process job types.

- Then, created new route group = 1113_sec with Setup time = Yes and Run time = Yes under Estimation and costing and under Automatic route consumption. Also, check Report operation as finished = Yes. Check Activation, Working times and Capacity for Setup and Process job types. Note that Job scheduling is NOT checked.

4. Navigate to Resources form. Create new resource = 1113_Tool with Type = Tool, route group = 1113_std, Setup category = Polishing, Run time category = Polishing, Quantity category = Polishing. Set Capacity unit = Strokes/hour, Capacity = 3480, Batch capacity = 80. Set Finite capacity = No, Calendar = 1113 and assign resource to resource group = 1110.

- Next, still on Resources, create new resource = 1113_Mach with Type = Machine, route group = 1113_sec, Setup category = Polishing, Run time category = Polishing, Quantity category = Polishing. Set Finite capacity = No, Calendar = 1113 and assign resource to resource group = 1110.

- Next, still on Resources form, select resource = 1113 and update route group = 1113_sec, Finite capacity = No and Calendar = 1113.

- Then, click on Resource group = 1110 and, on Resource groups from, for selected resource group = 1110, assign calendar = 1113.

5. Navigate to Coverage groups form. Create new coverage group = Period45 with coverage code = period, coverage period = 45, coverage time fence = 365, negative days = 365, positive days = 365, BOM explosion time fence = 365, Capacity scheduling time fence = 365.

6. Navigate to Master plans form. Update StaticPlan and set Scheduling method = Job scheduling, Finite capacity = No. Set Coverage = Yes (365 days), Explosion = Yes (365 days) and Capacity = yes (365 days).

7. Navigate to Released product details. Create new item number = gs1113 with item model group =FIFO, item group = AudioRM, storage dimension = SiteWH, tracking dimension None. Under Plan fast-tab, set Coverage group = Period45.

8. For newly created item number gs1113, go to menu Plan – Default order setting. Set Default order type = production and, under Inventory fast tab, set Min. order quantity = 2000 and standard order quantity = 2000.

9. For newly created item number gs1113, go to menu Engineer – Route and create new route and route version with name = gs1113 on Site = 1. Add operations as follows:

- Oper. No. 10 – Primary, Operation = Assembly, Route group = 1113_std. Under Setup tab, set Formula = Capacity, Factor = 18. Under Times tab, set Setup time = 1.5 and Run time = 1 for Process quantity = 1. Under Resource requirements, set Requirement type = Resource and assign resource 1113_Tool.

- Oper. No 10 – Secondary 1, Operation = Finishing, Route group = 1113_sec. Under Resource requirements, set Requirement type = Resource and assign resource 1113_Mach (accept resource defaults).

- Oper. No. 10 – Secondary 2, Operation = Packing, Route group = 1113_sec. Under Resource requirements, set Requirement type = Resource and assign resource 1113 (accept resource defaults).

- Approve and activate the route version.

10. Navigate to All sales orders form. Create new sales order for customer account = US-001, on Site = 1, Warehouse = 11. Delivery date control = None. On Sales line, add item number = gs1113, quantity = 2000.

11. After saving the sales order, go to sales line menu Product and supply – Net requirements. On Net requirements from, submit Planning optimization for item gs1113 under StaticPlan.

12. Planning process will complete with an error.

When registering Sales order there is used Item list with high number of items.

For some products if there were changed Min qty and/ or Multiply qty in Default order settings there are presented info messages like bellow:

1.You have specified a quantity of 1.00. The minimum allowed quantity is 20.00.Do you want to use 20.00 instead?

2.The order quantity must be a multiple of 12.00. Do you want to round up the order quantity to 24.00?

There is missing info about ItemId

Request:

Please add affected ItemId as a parameter presented in both info messages.

It will help to identify which items are affected.

-Vendors not populating in purchase requisition line when a released product is selected

-We do not get the vendor list to select from even after using allow all vendors, assigning procurement category at item level and also defining the trade agreement.

-Partner wants to be able to see the vendor list to select from when entering item with procurement category in Purchase Requisition Line.

-If we default a vendor at item master level vendor automatically pops up upon selecting an Item with procurement category, but this does not work for partner as they procure material from multiple vendors.

When accessing and exiting a work order project journal in asset management, the system automatically creates an empty expense journal for the related work order despite no adjustments being made to the project journal. The expense journal can only be deleted manually.

Idea: The system should create the expense journal for the related work order only after an adjustment is being made to the project journal.

Create a feature to view the "Explosion" for all lines within a sales order or project item requirements in a single view.

This feature would allow users to see all order/project requirements and expected delays within a single view that could be exported and shared with procurement and production staff for expediting requirements. Clicking through hundreds or thousands of item requirements lines to understand project/order requirements is not feasible.

Co- and by- products are important products in process manufacturing, they have specific requirements on batch attributes and must be possible to be created in the context of a change order where a new formula or recipe is specified. Currently, co-and by- products must be created outside of the order, because it is not possible to create an engineering product category with the option co- or by- product.

I may be wrong, but it seems to me, all it takes it adding the two options to the lookup.

Title:

Enable Expiry Date Input for Auto Batch Number Group in Mobile Device Receiving

Description:

Currently, the system automatically populates the batch number when receiving items on a mobile device, and the expiration date is not required if the batch number group is set to auto batch. However, some customers have expressed the need to input an expiry date even when the batch number is auto-generated. This feature would enhance the flexibility and usability of the system for customers who need to track expiration dates for their inventory.

Problem Statement:

Customers need the ability to input an expiry date when receiving items on a mobile device, even when the batch number is automatically generated. The current system does not allow this, which can lead to challenges in inventory management and tracking for customers who rely on expiration dates.

Proposed Solution:

Introduce a feature that allows users to input an expiry date when receiving items on a mobile device, even if the batch number group is set to auto batch. This feature should be optional and configurable, so customers can choose whether or not to use it based on their specific needs.

Benefits:

• Improved inventory management and tracking for customers who need to monitor expiration dates.
• Increased flexibility and usability of the system.
• Enhanced customer satisfaction by addressing a common pain point.

Use Case:

A customer receives a shipment of perishable goods on a mobile device. The system automatically generates a batch number, but the customer also needs to input an expiry date to ensure proper inventory management. With the proposed feature, the customer can easily input the expiry date, improving their ability to track and manage their inventory.

When you run the Transfer Order Update History cleanup (InventTransferParmCleanUp*) job, there is no way to properly run it on a recurring basis. This is because the job is run based on a Created until date specified in the job parameters. As a result, if April 8, 2024 is selected and the job is scheduled to run every week, then the job will only continue to clean up the transfer order history up to that date, regardless of the fact that it is recurring weekly.

It would be much more useful to have a parameter that specifies the number of Days of history to retain. This would allow the job to delete history that exceeds the parameter each time the job is run, thus allowing a recurrence to be set.

The current functionality requires an administrator to manually schedule the job each time it needs to run for each legal entity. This is unnecessary and cumbersome, especially for organizations with many operating legal entities.