Dynamics 365 Supply Chain Management

Para hablar directamente con Volaris, puedes usar la página web Tuexperiencia.volaris.com para consultas, seguimiento o problemas con tu membresía v.club, suscripción v.pass o tarjeta de crédito Volaris INVEX. También puedes llamar a los números oficiales de Volaris: +52 (55) 1102 8000 para México o +1-888-279-4718(♡ ᡣ𐭩 ˚ʚ♡♡ ᡣ𐭩 ˚ʚ♡) para Estados Unidos. Para otros países, como Guatemala, Costa Rica y El Salvador, los números son +502 2301 3939, +506 4000 0229 y +503 2504 5540, respectivamente.

Para hablar con un humano en Volaris, puedes llamar al centro de atención al cliente +1-888-279-4718 ♡ ᡣ𐭩♡ ᡣ𐭩 marcando su número oficial, disponible en su sitio web. También puedes contactar a través de WhatsApp, redes sociales como Facebook o Twitter, o visitar un mostrador en el aeropuerto. Asegúrate de tener a la mano tu número de reservación o datos del vuelo para agilizar la asistencia. El servicio suele estar disponible 24/7.

how to check mistakes

Background:

Create a Purchase requisition > add an item > add Unit price > approve the PR > convert to a Purchase order using a Vendor that have intercompany enabled > this will create intercompany PO and intercompany SO > the Unit price will be carried from the PR to the IC PO and IC SO.

The Item doesn't have any base unit price, trade agreement, the unit price is manually inserted.

Scenario:

Go to the intercompany SO > update the Site and Warehouse dimension > notice that the Unit price on become blank on both IC PO and IC SO.

Expectation:

The Unit price should be remain after update the Site and Warehouse or give a pop-up for user to decide whether to keep the Unit price or not.

The system has a refresh issue where when we assign the Base document “Contract” and the CIPE and the Tender procedure identification codes to a certain value, the correct values get assigned at first. However, after some time while remaining in the All Sales order page for an hour or more then go back to check, then the system ignores the unique codes that the user assigned to each Sales order individually and assigns all the Sales orders to the codes assigned solely to the last created Sales order. Then if we leave the Accounts receivables module and go click on a form in a different module then go back to the Accounts receivables module and check the codes in the Sales orders that we created the codes will reflect as how they were intended to be for each Sales order.

So, if SO 1 has codes AAA, SO 2 has codes BBB, and SO 3 has codes CCC.

When we check all is well after these SOs are freshly created. However, if we wait for an hour or more and check again, SO 1 and SO2 and SO3 have codes CCC. Then if we choose a different form in F&O and then go back, we will see that SO 1 has codes AAA, SO 2 has codes BBB and SO 3 has codes CCC.

Expected Result

Each Sales order should have its unique CIPE and Tender procedure identification codes as per how the user assigned these codes to be without needing to leave the Sales order form and going to any other form then going back to the SO.

Same behavior was noticed in 10.0.42 – 10.0.43 – 10.0.44.

Currently, upon manually changing the Route number on versions 10.0.42 and 10.0.43 against 2 different Planned orders with the same Item number then grouping these 2 Planned orders, a new Planned order will be created, however, the manual Route number change is overlooked by the system and the old Route number get assigned to the newly created Planned order. If we proceed further to Firm this Planned order, a Production order will be created against the wrong Route number. The users wish to have the system assign the correct Route number to the Grouped Planned orders.

Dual Writes exists to link D365 F&SCM to D365 CE systems.

If try to amend an existing Customer Address that is purpose "Business" to also be purpose "Invoice" get a dual Writes error "Unable to write to data entity quotes. Writes to ProjQuotationHeaderEntity failed with error message request failed with status code Bad Request. The quote cannot be activated because it is not in DRAFT state".

NOTE - if Dual Writes does not exist then can amend the Customer Address ok to also set to purpose "Invoice".

Microsoft have confirmed this is STD system behaviour when Dual Writes exist. : "I would like to inform you that after deeper investigation and after checking the code, as well, I concluded that the system is working as per original design, so I would like to bring more clarity and provide options to overcome this or change the behavior. The behavior is the following: when the customer address is updated (either the purpose, or anything else in the address), the system will send an update to CE to all the sales orders/ sales quotations/ project quotations which include the modified address (more specific, the system is trying to update all orders/ quotes that are associated, no matter their status). This scenario was raised with Product Group, and we got confirmation that this is the original behavior when an address is being changed in FnO. "

It does not make logical sense that Dual Writes would try and update ALL Quotations on the system as those Quotations are completed / cancelled so should not being getting updated. Without Dual Writes in place it works ok so std F&SCM is clearly NOT trying to update existing Quotations.

Microsoft have advised as a partner we would have to write customisation to bypass this validation : "From 10.0.41, our Engineering Team made SalesOrderHeaderCDSEntityRecordIdSelectorLogisticsPostalAddress, SalesOrderLineCDSV2EntityRecordIdSelectorLogisticsPostalAddress and SalesOrderLineCDSEntityRecordIdSelectorLogisticsPostalAddress extensive for giving customers/ partners the option to create an extension and skip the update of all orders/ quotations. However, I could not confirm what is the class that is being triggered/ called in our scenario".

This new idea is to propose the following;

• Dual Writes should ONLY try to update existing DRAFT Quotations that have the Customer Address we are trying to amend
• this makes more logical sense as Closed quotes are completed and should not be updated (especially when the change is not a physical address change, it's just setting an existing "business" address to also be "invoice" purpose)
• having a partner/customer have to develop code extensions to correct Microsoft bad design is not a solution

Please review and implement this change in a future release.

When 2 Planned orders with the same Item number and the Status “Unprocessed” are grouped into 1 single Planned order, the system automatically changes the Status to “Approved” in version 10.0.43.

The system shouldn’t change the Status to “Approved” unless the customer actually decides to manually approve the grouped Planned orders. The problem is that when you approve a Planned order, you wouldn’t be able to delete it if you were to run the Planning optimization again.

Customer wishes to have the option to "Approve" the Planned orders and not have them automatically approved. This could happen if there was to be a toggle/parameter to give the freedom of changing the status of the Planned orders as wished.

We dont want to use some vendors - instead of deleting them we wanted to keep them and put them on hold and some users saying when they accidentaly select those vendors and getting a warning. when they are not allowed to create any future transaction why to show them when creating a purchase order. Can this be ignored ?

For distribution and manufacturing companies that have inventory located in multiple physical warehouses, the ship to address of the customer order may dictate the ship from site/warehouse if the same product is stocked across multiple locations. For example if the same item is stocked in a warehouse in Mississippi and in Oregon, if a sales order is entered with a delivery address in Washington the stock in Oregon should be used to fulfill the requirement. A single customer could have multiple ship to addresses across the country so defaulting the site and warehouse at the customer level is not ideal. In current D365 the only way to accomplish this is to have a different customer for each delivery address.

Ideally the site and warehouse would default based upon the delivery address and not the customer.