Microsoft Dynamics 365
Specifically add at least two fields for Incoterm support.
Field 1: 3 letter incoterm designation (i.e. FCA, DDP, EXW) to be selected per transaction
Field 2: Named Location to be selected per transaction.
Optional: Add third text field designating Incoterm Reference as (i.e. Incoterms 2020) to be set up in configuration.
These fields shoudl appear on all sales and purchase documentation (BOL, Invoices, Packing Lists, etc.)
I see too many work-arounds to force fit this where it does not belong. If properly implemented, it can help companies manage the terms, promote compliance to policy, and determine risk exposure for insurance purposes.
For cross border or transactions in or out of Free Trade Zones, the International transaction is governed by Incoterms. Dynamics is currently structured for DOMESTIC ONLY.
Incoterms are NOT THE SAME as the transport terms (i.e. prepaid freight, etc.) or payment terms. Incoterms are a 2 or 3 part term. The first part is the 3 letter designation from the International Chamber of Commerce. The second is the location reference. The third, as optional best practice, is a reference to the revision of incoterms (i.e. Incoterms 2020). The first two must be on purchase or sales documentation.
We ususally get a little bit less from our vendor than we orderd (inter company). We would really need a straight forward way to flag an order position as "fully delivered" even though 0,5-1% is still missing.
We usually reduce the original order amout, which costs us a lot of time.
Note from online-help version 209 and 2013:
A purchase order createdas a special order for a sales order is automatically linked to the salesorder by a reservation. The planning system respects this link as it balancesdemand and supply. That is, the purchase order (supply) remains linkedto the sales order (demand), even if that purchase order could supplyanother earlier demand.
Without this functionality it seems that Special Order functionality is obsolete.
In NAV this functionality (source code + source number) exits. GF is currently converting from NAV->BC and it is quite disappointing to loose this kind of functionality. No one told us in advance. With updated SW our expections were to get more in stead of less. So please add :-)
Das Entfalten der Stücklisten bis hin zur untersten Ebene ist eine sehr zeitintensive Aufgabe und könnte vereinfacht werden. Dazu kommt folgendes Problem:
Wenn mit Montagestücklisten gearbeitet wird und eine Baugruppe (ggf. mit mehreren Strukturebenen) eingekauft und nicht hergestellt wird, also mit Beschaffungsmethode "Einkauf", wird mir durch anzeigen "Montagestückliste" vorhanden immer vorgegaukelt dass ich mich um die Stückliste kümmern muss, obwohl sie eingekauft wird.
Vendor item number can be linked to a Sales order but not to a purchase order and invoice. Why??? I believe someone made a mistake, or forgot to add this.
Currently GF is in the conversion proces from NAV-> BC (latest and greatest?), but are loosing this kind of functionality. This can be very frustrating. So please add.
An excellent idea. We have staff ranks that we use for costing and it would be appropriate at the quotation stage to use ranks instead of named resources.
Agree entirely that all businesses have expenses so this is a fundamental missing piece for Business Central.
This would be perfect for our company with a structure of parent opportunities and child bids and projects.