Introduction
Microsoft Dynamics 365 Supply Chain Management provides robust procurement functionality for organizations that use the application. Microsoft Dynamics 365 Field Service offers similar functionality that supports the purchasing processes that are associated with the service process. The functionality in these two apps can be integrated through dual-write, and the resulting cross-functional use cases are enabled through table mappings, solution logic, views, and forms.
Integration between Dynamics 365 Supply Chain Management and Dynamics 365 Field Service allows you share procurement data bidirectionally, which allows you to make updates from both apps in near real-time. For example, your organization can create a purchase order in Supply Chain Management and then update the purchase order, such as updating the delivery or purchase order lines in Field Service. Changes that you make in either application are shared in near real-time. Additionally, you can track the purchase order status and life cycle in both applications.
The following diagram shows tables in both systems and their relationships. In Field Service, purchase orders correspond to an account row, but in Supply Chain Management, purchase orders refer to a vendor row. To resolve the integration, dual-write uses a reference to link vendor rows with account rows.
When data is integrated between Supply Chain Management and other applications, such as Dynamics 365 Field Service, you need to understand how the data can be mapped and how table relationships are created. For example, a vendor is an established concept in Supply Chain Management, while in customer engagement apps, the concept of vendors doesn't exist. To bridge this gap, you can overload the Account/Contact table to store vendor data. The integrated vendor master introduces an explicit vendor concept in customer engagement apps. You can use the new vendor design or store vendor data in the Account/Contact table. Dual-write supports both approaches. If you don't want to store your vendor data in the Account/Contact table in Microsoft Dataverse, you can set up a new vendor design.
For more information, see Vendor data flow.