Dynamics 365 Supply Chain Management

The data entity Purchase Requisition V2 is not usable for dual write or integrations because of validation if the worker (Preparer) is equal to the worker assigned to the user.

when you use dual write or oData to create a record, you will use an app registration. This app registration has in Dynamics 365 FnO a (generic) user connected. But this user doesn’t have a worker assigned. You want to populate the Preparer with each worker that exist in the legal entity.

The data entity validates if the worker assigned to the user is equal to the worker specified in the field “Preparer”. From a data management perspective this is very logic. You don’t want that another worker requests a purchase on your name. But from an interface perspective (oData, Dual write) this is not possible. Those will use an app registration that is related to a user that has no worker assigned. Even if you assign a dummy worker to the user, you don’t have the traceability who created the purchase requisition in the external app.

As a workaround:

Extended the Purchase requisition entity and customized the field "preparer" by disabling it's validation

Summary; This validation should only be executed for the Excel add-in or data management. But not for Dual Write or oData.

I understood that it is currently not possible to use an external scanner (e.g. wired or Bluetooth) on the asset management mobile app. There is only the option to either enter the (item) codes manually or to use the camera of the mobile device itself. Using the camera is extremely un-accurate for aiming at the correct barcode and unpractical in many cases: e.g. our customer docs the tablet onto a cart and would use the external scanner to confirm the scanned items (some of these products are stacked closely together, so aiming for the correct barcode with the device camera is a nightmare). A handheld scanner would solve many issues.

It will be great if Approvals Management mobile's UI can be customized.

Adding fields, personalize designed ...

We would like to have an option to do intercompany between 2 separate tenants.

It'd be an important perk for Big/large companies with multiple branches and departments where a department can be acquired by a different company, but we want to maintain the trade relations between them. And vice versa, we can merge 2 companies together and each of which will have its own tenant and maintaining the trade flow is required.

Currently, it's during voyage creation that the voyage AND containers are created in 1 go.

However, our customer's process is:

1. Shipment booking at forwarder
2. When shipment is done at vendor or subcontractor (for TO's) containerization is done where exact container contents (products, quantities, variants, ...) are registered.

In the landed cost voyage creation process, this is not possible since voyage lines can only be created when container is defined.

Workaround would be:

1. Create shipment + add all lines to dummy container
2. When container content is known: Delete all voyage lines and create new voyage lines with correct containers.
3. Voyage data entities can't be used, since you can't overwrite the container in the line entity (read only)

O processo de Ordem de transferencia não esta interligado ao WMS. Quando se faz a separação via WMS e faturado a nota pela localização brasleira, ao cancelar a nota, o Item e o Trabalho criado não são estornados, impossibilitando um novo faturamento.

The customer is using item substitutions (plan groups) on formulas that consist of two lines, each with its own priority. The primary and secondary formula item have corresponding item coverage setup that replenish demand with planned purchase orders at warehouse 12 and transfer this demand to warehouse 13. However, when planning is run with demand at warehouse 13 the system completely ignores plan group setup. It covers the demand with on-hand inventory and replenishes the remaining quantity only for the item with priority 1, without considering the on-hand inventory for the item with priority 2. However, if the demand is for warehouse 12 (where no transfer is required), the item substitutions work as expected, and the on-hand inventory for the item with priority 2 is considered.

My quotations go to All quotations after refresh when enable Sales quotation details performance enhancement. Customers wait to keep on My quotations page as only need to do business on my quotations.

When a purchase order is confirmed and the user subsequently requests changes—updating information in the purchase order header and resubmitting it to the workflow—the system currently confirms the PO directly without generating a new purchase order confirmation journal number. This results in the confirmation journal number being skipped.

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.